Starting and stopping the software containers

This topic describes the tasks that are required to start and stop the software containers for IBM Z® Resource Discovery Data Service solutions.

Procedure

The instructions in this procedure use dockerManageZoa.sh as an example. If you are a Podman user, use podmanManageZoa.sh instead.

Start all services that are provided by the installed software containers by running the following command in a Linux® terminal session:
```
cd <ZOA_HOME>
./bin/dockerManageZoa.sh up
```

Verify that the services started successfully by running the following command in a Linux terminal session: ./bin/dockerManageZoa.sh ps.

For a deployment in which only ZRDDS and the Z Operational Analytics common services are installed, you should see a list similar to the following:

NAME           […] CREATED          STATUS                 […]
zoa-auth                    9 minutes ago    Up 9 minutes                    
zoa-gateway                 11 minutes ago   Up 11 minutes
zoa-kafkabroker             5 minutes ago    Up 5 minutes
zoa-kafkacontroller         5 minutes ago    Up 5 minutes
zoa-service-discovery       11 minutes ago   Up 11 minutes
zrdds-core                  4 minutes ago    Up 4 minutes (healthy)
zrdds-api                   4 minutes ago    Up 4 minutes (healthy)
zrdds-orientdb              4 minutes ago    Up 4 minutes (healthy) 
zrdds-postgresql            4 minutes ago    Up 4 minutes (healthy)
zrdds-kafkaconnect          4 minutes ago    Up 4 minutes
zrdds-kafkabridge           4 minutes ago    Up 4 minutes

Verify that the software containers start automatically after system startup.

Action Instructions

If the Docker container tool is used

Action	Instructions
If the Docker container tool is used	When the Docker daemon is started, all previously running software containers will be started automatically. To ensure that the services start automatically after system startup, configure the Docker service to be launched automatically by the service manager (typically, systemd) at system startup. If the following conditions are met, the software containers are automatically started at system startup: The Docker service is enabled in systemd to automatically start at system startup. In the `-docker-compose.yml` files, all services are set to restart: always*, which is the default setting. Do not change this setting unless you are instructed to do so by IBM® Support. The Docker daemon is allowed to control the shutdown of the software containers. If you run `./bin/dockerManageZoa.sh down` before restarting the system, the services will not automatically start. If you allow the docker daemon to shut down the services as the system reboots, the services will automatically start. For more information about how to launch a service at system boot time, see the documentation for your Linux distribution.
If the Podman container tool is used	Because Podman is a daemon-less tool, it does not provide automatic integration with Linux system service management. To have the container-based services start automatically at system startup, use either of the following methods: Create a systemd service configuration file for the `podmanManageZoa.sh` script, and manage this script via the service manager for your system. A sample implementation is provided in the `<ZOA_HOME>/samples/systemd` directory. If you do not have administrative privileges on the Linux system, define a cron job for `podmanManageZoa.sh up`, with the @reboot instruction.

When the Docker daemon is started, all previously running software containers will be started automatically. To ensure that the services start automatically after system startup, configure the Docker service to be launched automatically by the service manager (typically, systemd) at system startup.

If the following conditions are met, the software containers are automatically started at system startup:

The Docker service is enabled in systemd to automatically start at system startup.
In the *-docker-compose.yml files, all services are set to restart: always, which is the default setting. Do not change this setting unless you are instructed to do so by IBM® Support.
The Docker daemon is allowed to control the shutdown of the software containers. If you run ./bin/dockerManageZoa.sh down before restarting the system, the services will not automatically start. If you allow the docker daemon to shut down the services as the system reboots, the services will automatically start.

For more information about how to launch a service at system boot time, see the documentation for your Linux distribution.

If the Podman container tool is used

Because Podman is a daemon-less tool, it does not provide automatic integration with Linux system service management.

To have the container-based services start automatically at system startup, use either of the following methods:

Create a systemd service configuration file for the podmanManageZoa.sh script, and manage this script via the service manager for your system. A sample implementation is provided in the <ZOA_HOME>/samples/systemd directory.
If you do not have administrative privileges on the Linux system, define a cron job for podmanManageZoa.sh up, with the @reboot instruction.

Manage security for the software containers, as described in Managing data encryption in transfer.
Configure logging for the software containers, as described in Logging for the software containers.