Deploying containers with Docker
How to deploy the current version of HCL Workload Automation using Docker containers.
About this task
This chapter describes how to deploy the current version of HCL Workload Automation using Docker containers.
The available Docker containers are:
- HCL Workload Automation Server, containing the master domain manager and backup master domain manager images for UNIX, Windows, and Linux on Z operating systems.
- HCL Workload Automation Console, containing the Dynamic Workload Console image for UNIX, Windows, Linux on Z operating systems, and the IBM z/OS Container Extensions (zCX) feature.
- HCL Workload Automation dynamic agent and the image of the agent with the machine learning engine, containing the Agent image for UNIX, Windows, Linux on Z operating systems. and the IBM z/OS Container Extensions (zCX) feature.
- HCL Workload Automation z-centric agent, containing the Agent image for UNIX, Windows, Linux on Z operating systems. and the IBM z/OS Container Extensions (zCX) feature.
Each container package includes also a docker-compose.yml
file
to configure your installation.
The dynamic agent component (also the one included in the HCL Workload Automation Server container) is deployed and configured with a gateway.
You can choose to deploy all product containers with a single command,
or you can deploy each product component container individually.
- Deploying all product component containers with a single command
- The following readme file contains all the steps required to deploy all product components at the same time: HCL Workload Automation
- Deploying each product component container individually
-
If you want to install server, console and agent containers individually, see the related readme files :
- HCL Workload Automation Server
- HCL Workload Automation Console
- HCL Workload Automation dynamic agent
- HCL Workload Automation z-centric agent
Note: The database is always external to the Docker engine and is not available as a container
Note: When deploying the server (master domain manager) container, the database
schema is automatically created at the container start. If you are planning to install
both the HCL Workload Automation
server master domain manager and backup master domain manager, ensure that you run the
command for one component at a time. To avoid database conflicts, start the second
component only when the first component has completed successfully.