[8.5.5.8 or later]
This topic applies to WebSphere Application Server Liberty V8.5.5.9 and earlier. For the latest Liberty topics, see the WebSphere Application Server Liberty documentation.

Accessing a remote Liberty server in a Docker container by using developer tools

You can set up your remote Liberty server in a Docker container so that you can access it by using WebSphere Developer Tools. After you complete this setup, you can use WebSphere Developer Tools to configure and start your remote Liberty server.

Before you begin

  1. Install Docker, Cloud Foundry Command Line Interface (CLI), and the Cloud Foundry plug-in for IBM Containers.

    For more information about installation, see IBM Containers plug-in.

  2. Log in to your Bluemix account, choose your organization and space, and then log in to your IBM Containers service.

    For more information about logging in to your accounts, see Logging into the CLI.

    Tip: You can either run cf ic commands or docker commands to set up a Liberty server in a Docker container. For more information about cf ic commands and docker commands, see the Step 5 section of Logging into the CLI.

Procedure

  1. To access your remote Liberty server in a Docker container, use the following command:
    docker exec -i  ContainerID LibertyInstallDirectory/bin configUtility install remoteAdministration --vadminUser=Username --vadminPassword=Password --vkeystorePassword=KeystorePassword
    Remember: To find the container ID, use the docker ps command. By default, the KeystorePassword value is Liberty.

    Also, by default the LibertyInstallDirectory value is /opt/ibm/wlp, and the bin directory is in the /opt/ibm/wlp directory.

    For more information about the configUtility command, see Liberty: configUtility command.

  2. When the script displays the configuration snippet, copy it into the remoteAdministration.xml file.

    The remoteAdministration.xml file is in the LibertyInstallDirectory/usr/servers/serverName/configDropins/defaults directory. If this directory and file do not exist, create the directory and then create the file.

  3. Specify the <remoteFileAccess> parameter in the remoteAdministration.xml file by replacing its contents with the following text:
    <writeDir>${server.config.dir}</writeDir>
    <writeDir>${server.output.dir}</writeDir>
    <writeDir>${wlp.user.dir}</writeDir>
  4. Save the remoteAdministration.xml file.

What to do next

You can configure and start a remote Liberty server that is in a Docker container.

For more information about how to configure and start a remote Liberty server, see Creating a remote Liberty server by using developer tools.


Icon that indicates the type of topic Task topic



Timestamp icon Last updated: Tuesday, 12 December 2017
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-libcore-mp&topic=t_docker_remote_server
File name: t_docker_remote_server.html