Configure Liberty profile servers

After creating a middleware server representation of a Liberty profile server, update the configuration settings so that they match the Liberty profile installation.

Federate the node running the Liberty profile server, and create a representation of the server.

If we installed the Liberty profile in a location other than $WAS_INSTALL_ROOT/wlp, and if you modified the WLP_USER_DIR or the WLP_OUTPUT_DIR location for the Liberty profile, update the WebSphere variables to point to the appropriate directories.

Update the WebSphere variables so that they match the settings on the node running the Liberty profile server. Follow the procedures in the topic on modifying variables to edit the following variables:

WLP_INSTALL_DIR

Home directory of the Liberty profile installation. Default values are set at the cell scope level:

${WAS_INSTALL_ROOT}/wlp

If the home directory is different on different nodes in our configuration, create the WLP_INSTALL_DIR variable for a specific node.

WLP_USER_DIR

usr directory for the Liberty profile installation. Typically, the default value does not need to be changed. Default values are set at the cell scope level:

${WLP_INSTALL_DIR}/usr

If the usr directory for the Liberty profile installation is different on different nodes in the configuration, create the WLP_USER_DIR variable for a specific node.

WLP_OUTPUT_DIR

output directory for the Liberty profile installation. Typically, the default value does not need to be changed. Default values are set at the cell scope level:

${WLP_USER_DIR}/servers

If the output directory for the Liberty profile servers is different on different nodes in the configuration, create the WLP_OUTPUT_DIR variable for a specific node.

JAVA_HOME

Directory of the Java Development Kit (JDK) installation. If not set in the environment of the node, define the cell scope or at the node scope.

Start and stop the Liberty profile servers.

Run wsadmin with a user name and password so that we can start and stop server operations. Follow the directions in the topic on starting the wsadmin scripting client.

Update the HTTP and HTTPS ports for the servers. The default ports are 9080 and 9443. If the Liberty profile server is configured to use a value other than the default, change the port in the representation.

Use the modifyForeignServerProperty command in the middleware server management administrative tasks to change the ports.

If the server will be part of a dynamic cluster, the port value in the representation must match the port in the Liberty profile server configuration in order for the on demand router to route traffic to the server. Configure the Liberty profile server to listen to HTTP traffic on an external virtual host. By default, the Liberty profile server monitors traffic on the local host. Update the Liberty server configuration so that the HTTP endpoint listens to the fully qualified
domain name of the host, or enter * to monitor all virtual hosts.

What to do next

To use this configuration on other Liberty profile servers, create a server template of the current Liberty profile server.

View the log files for the Liberty profile server. Use the administrative console, or check on the hosting computer.

Edit configuration files for the Liberty server through the administrative console or on the hosting computer.

After creating representations of all the Liberty profile servers, we can add the representations to a dynamic cluster.