After you create a middleware server representation of
a Liberty profile server, update the configuration settings so that
they match your Liberty profile installation.
Before you begin
Federate the node that is running the Liberty profile server,
and create a representation of the server.
About this task
If you 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.
Procedure
- Update the WebSphere variables
so that they match the settings on the node that is running the Liberty
profile server. Follow the procedures in the topic on modifying variables
using wsadmin scripting to edit the following variables:
- WLP_INSTALL_DIR
- Specifies the home directory of your Liberty profile installation.
- Default values are set at the cell scope level:
![[Windows]](../images/windows.gif)
${WAS_INSTALL_ROOT}/wlp
- If the home directory is different on different nodes in your
configuration, create the WLP_INSTALL_DIR variable
for a specific node.
- WLP_USER_DIR
- Specifies the 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:
![[Windows]](../images/windows.gif)
${WLP_INSTALL_DIR}/usr
- If the usr directory for the Liberty profile
installation is different on different nodes in your configuration,
create the WLP_USER_DIR variable for a specific
node.
- WLP_OUTPUT_DIR
- Specifies the 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:
![[Windows]](../images/windows.gif)
${WLP_USER_DIR}/servers
- If the output directory for the Liberty profile servers is different
on different nodes in your configuration, create the WLP_OUTPUT_DIR variable
for a specific node.
- JAVA_HOME
- Specifies the directory of your Java Development Kit (JDK) installation.
- If the JAVA_HOME variable is not set in the
environment of the node, define the JAVA_HOME variable
at the cell scope or at the node scope.
- Start and stop the Liberty profile servers.
- Run the wsadmin command with a user name
and password so that you can start and stop server operations. Follow
the directions in the topic on starting the wsadmin scripting
client.
- In the administrative console, click .
- Update the HTTP and HTTPS ports for your 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.
- In the administrative console, click . Edit HTTP connector or HTTPS
connector. Click OK, and save and
synchronize your changes.
- 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 your current Liberty profile server.
- View the log files for your Liberty profile server. Use the administrative
console, or check on the hosting computer.
- Edit configuration files for your Liberty server through the administrative
console or on the hosting computer.
- After you create representations of all the Liberty profile servers,
you can add the representations to a dynamic cluster.