Starting and stopping the software containers

Edit online

This topic describes how to start and stop the container-based services such as the Z Data Analytics Platform and the Problem Insights server.

About this task

To initiate all the container-based services, run the following commands from a Linux® terminal session:
```
cd <ZOA_HOME>
./bin/dockerManageZoa.sh up
```
To terminate all the container-based services, run the following commands from a Linux terminal session:
```
cd <ZOA_HOME>
./bin/dockerManageZoa.sh down
```
To view the log output from service containers, for example, in the case of a service failure, run the following commands from a Linux terminal session:
```
cd <ZOA_HOME>
./bin/dockerManageZoa.sh logs SERVICE
```
If you do not specify the SERVICE, the command will provide the log output from all the available service containers.
To view the status of service containers, run the following commands from a Linux terminal session.
```
cd <ZOA_HOME>
./bin/dockerManageZoa.sh ps SERVICE SERVICE ...
```
If you do not specify the SERVICE, the command will provide the status of all the services.
To stop running containers, run the following commands from a Linux terminal session.
```
cd <ZOA_HOME>
./bin/dockerManageZoa.sh stop SERVICE SERVICE ...
```
If you do not specify the SERVICE, the command will stop all the services.
To start stopped containers, run the following commands from a Linux terminal session.
```
cd <ZOA_HOME>
./bin/dockerManageZoa.sh start SERVICE SERVICE ...
```
If you do not specify the SERVICE, the command will start all the stopped services.
To restart running containers, run the following commands from a Linux terminal session.
```
cd <ZOA_HOME>
./bin/dockerManageZoa.sh restart SERVICE SERVICE ...
```
If you do not specify the SERVICE, the command will restart all the running services.
To gather must-have documentation for IBM® Software Support, run the following commands from a Linux terminal session:
```
cd <ZOA_HOME>
./bin/dockerManageZoa.sh gather
```

Note: The stop, start and restart commands will not result in a reinitialization of service containers in case configuration parameters have changed. To allow configuration changes to take effect, you must terminate all the services with the down command and reinitialize them with the up command. To allow the configuration changes for a single service to take effect, you can run the following command:

./bin/dockerManageZoa.sh up SERVICE

If you are a Podman user, configuration changes cannot be picked up through a single command. Instead, run the following sequence of commands to update configuration changes for a single service:

./bin/podmanManageZoa.sh stop SERVICE
podman rm zdap-SERVICE
./bin/podmanManageZoa.sh up SERVICE

Results

After you install and initialize the container-based services, you can verify that all services started successfully. To verify that all services started successfully, run the following command:

cd <ZOA_HOME>
./bin/dockerManageZoa.sh ps

If you use the default environment settings, you will see output similar to the following:

NAME                    IMAGE                                              COMMAND                  SERVICE                 CREATED             STATUS              PORTS
zdap-dashboards         ibm-zaiops/zdap-dashboards:5.1.1-10-x86_64         "/tini -- /usr/local…"   dashboards              47 hours ago        Up 47 hours         5601/tcp
zdap-gateway            ibm-zaiops/zdap-gateway:5.1.1-10-x86_64            "/usr/local/bin/dock…"   zdapgw                  47 hours ago        Up 47 hours         8085/tcp, 0.0.0.0:8086->8086/tcp
zdap-oauth2             ibm-zaiops/zdap-oauth2:5.1.1-10-x86_64             "/bin/docker-entrypo…"   oauth2                  47 hours ago        Up 47 hours         
zdap-parser             ibm-zaiops/zdap-parser:5.1.1-10-x86_64             "/usr/local/bin/dock…"   parser                  47 hours ago        Up 47 hours         5044/tcp, 9600/tcp
zoa-datastore           ibm-zaiops/zoa-datastore:5.1.1-10-x86_64           "/tini -- /usr/local…"   datastore               47 hours ago        Up 47 hours         9200/tcp, 9300/tcp
zoa-gateway             ibm-zaiops/zoa-gateway:5.1.1-10-x86_64             "./main.sh"              gateway                 47 hours ago        Up 47 hours         0.0.0.0:8085->8085/tcp
zoa-kafkabroker         ibm-zaiops/zoa-kafkabroker:5.1.1-10-x86_64         "docker-entrypoint.sh"   kafkabroker             47 hours ago        Up 47 hours         0.0.0.0:9092-9093->9092-9093/tcp
zoa-keycloak            ibm-zaiops/zoa-keycloak:12.0.4-x86_64              "/opt/jboss/tools/do…"   keycloak                47 hours ago        Up 47 hours         8080/tcp, 0.0.0.0:8443->8443/tcp
zoa-piserver            ibm-zaiops/zoa-piserver:5.1.1-10-x86_64            "docker-entrypoint.sh"   piserver                47 hours ago        Up 47 hours         
zoa-rulesengine         ibm-zaiops/zoa-rulesengine:5.1.1-10-x86_64         "./main.sh"              rulesengine             47 hours ago        Up 47 hours         
zoa-service-discovery   ibm-zaiops/zoa-service-discovery:5.1.1-10-x86_64   "/usr/local/bin/dock…"   discovery               47 hours ago        Up 47 hours         
zoa-zookeeper           ibm-zaiops/zoa-zookeeper:5.1.1-10-x86_64           "docker-entrypoint.s…"   zookeeper               47 hours ago        Up 47 hours

Ensure that the STATUS column shows Up for all containers.