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.

1. Go to the bin directory of the remote Liberty server.

   By default, the bin directory is in the /opt/ibm/wlp directory.

2. To access your remote Liberty server in a Docker container, use the following command from the bin directory of the remote Liberty server:

   docker exec -i  ContainerID configUtility install remoteAdministration --vadminUser=Username --vadminPassword=Password --vkeystorePassword=KeystorePassword

   Remember: To find the container ID, use the docker ps command.

   For more information, see the configUtility command documentation.

3. When the script displays the configuration snippet, copy it into the server.xml file.
4. Specify the <remoteFileAccess> parameter in the server.xml file by replacing its contents with the following text:

   <writeDir>${server.output.dir}</writeDir>
       <writeDir>${wlp.user.dir}</writeDir>

5. Optional: To secure your remote Liberty server in a Docker container, change the keystore property.
   By default, the keystore property is the following element:

   <!-- TODO: Set the SSL keystore password -->
   <keyStore id="defaultKeyStore" password="Liberty" />

   1. To change the keystore property, enter the following command from the bin directory of the remote Liberty server:

      docker exec -i ContainerID securityUtility createSSLCertificate --server=ServerName --password=keystorePassword 

      If the keystore password was previously set, then delete the LibertyInstallDirectory/usr/servers/ServerName/resources/security/key.p12 file and use the securityUtility command again.

      Through 19.0.0.2, if the keystore password was previously set, then delete the LibertyInstallDirectory/usr/servers/ServerName/resources/security/key.jks file and use the securityUtility command again.

   2. When the script displays the security element, copy it to your clipboard.
   3. Replace the keystore element in the server.xml file with the security element that you copied.
6. Save the server.xml file.