6.5 Starting Remote Loader Instances Automatically With Remote Loader Container Deployment

If you want to start the Remote Loader instances automatically once the Remote Loader container is deployed, perform the following steps:

  1. On your Docker host, navigate to the shared directory. For example, data.

  2. Create the rdxml directory.

    NOTE:This applies only when you are deploying containers for the first time. In other words, if you are updating the containers and have already created the rdxml directory before, skip this step.

  3. Navigate to the rdxml directory.

  4. In the rdxml directory, create the driverconf directory.

    NOTE:If you have multiple configuration files running with different Remote Loader instances, copy all the files.

  5. Copy all the required configuration files to the driverconf directory. For example, config8000.txt.

  6. In the rdxml directory, create the keystore directory.

  7. Copy all the required keystore files and certificates to the keystore directory.

  8. In the rdxml directory, create a new .txt file. For example, StartupRL.txt.

  9. In the StartupRL.txt file, specify the required content in the following format:

    <Remote Loader configuration file> -sp <driver password> <Remote Loader password>

    For example:

    config8000.txt -sp dirxml dirxml

    Alternatively, you can also specify the entries in the following format:

    <Remote Loader configuration file> -ksp <keystore password> -kp <key password>

    For example:

    config8000.txt -ksp dirxml -kp dirxml

  10. Deploy the Remote Loader container by passing the RL_DRIVER_STARTUP environment variable in the docker run command. For example, -e RL_DRIVER_STARTUP="StartupRL.txt".

    For more information, see Deploying Remote Loader Container.