Installing IBM Z Resource Discovery Data Service on IBM z/OS Container Extensions (zCX)

This topic provides instructions for installing IBM Z® Resource Discovery Data Service on an IBM® Container Extensions (zCX) instance.

Before you begin

To install IBM Z Resource Discovery Data Service on IBM z/OS Container Extensions (zCX), ensure that the zCX instance meets the following resource requirements:
- Recommended requirements: 6 vCPUs, 16 GB reserved memory, and 100 GB total disk space.
- Minimum requirements: 4 vCPUs, 8 GB reserved memory, and 50 GB total disk space.
Obtain the IP address of the target zCX instance. This information is required during the installation and configuration process.
Ensure that you are using Z Operational Analytics common Fix Pack version 25 (FP25). Earlier versions do not support zCX deployments.

About this task

IBM z/OS Container Extensions (zCX) enables you to run Linux on IBM Z applications directly within the z/OS environment using standard Docker containers. By eliminating the need for a separate Linux server, zCX simplifies infrastructure management and enables modern cloud-native workloads to run alongside traditional z/OS applications. IBM Z Resource Discovery Data Service supports deployment on zCX, providing a containerized runtime environment within z/OS.

Procedure

Transfer the IBM Z Resource Discovery Data Service and Z Operational Analytics common installation tar files to the zCX instance, and then extract both the files.
Go to the zoacommon subdirectory:
```
cd install_dir/zoacommon    
```
Start the installation process by using following command:
```
./dockerDeployZoa.sh --install
```
Note: If you see the following warning during the deployment process, you can ignore it, as it does not affect the zCX deployment: WARNING >> 'host' utility is recommended, but could not be found in the system path.
If the following prompt is displayed, enter N (No):

IP address '<ip_address in range 172.16.x.x to 172.31.x.x>' is not in a routable address space and therefore not reachable from other networks. Do you want to use it anyway? (y/N).

Note: Do not use the non-routable IP address that is automatically detected. Instead, use the IP address of your zCX instance.
When prompted, enter the IP address of your zCX instance.
After the installation completes, verify that the following configuration settings contain the zCX instance IP address that you provided during installation:
- ZOA_HOME folder > zoa_env.config file > ZAIOPS_KAFKA_BOOTSTRAP_SERVER_HOST.
- ZOA_HOME folder > zoa_factory.config file > ZAIOPS_KEYCLOAK_HOST.
- ZOA_HOME folder > zoa_factory.config file > EXTERNAL_GATEWAY_HOST.
- ZOA_HOME folder > zoa_factory.config file > ZAIOPS_KEYCLOAK_IP.
Note: These configuration settings are updated automatically during installation. If any of these settings do not contain the zCX instance IP address, update them manually with the correct zCX instance IP address before proceeding.
Run the following command to regenerate the TLS certificates so that the Subject Alternative Name (SAN) matches your zCX instance IP address.
```
cd <ZOA_HOME>
./bin/dockerManageZoa.sh config-certificates generate
```
Run the following command to generate the TLS certificate that is required to establish secure communication between Kafka and the ServiceNow MID Server:
```
cd <ZOA_HOME>
./bin/dockerManageZoa.sh config-certificates export
```
In IBM Z Resource Discovery Agent, perform the following steps to update the ZRDDS_HOST_NAME value with the IP address of your zCX instance:
1. Run the following command to access the configuration file.
```
cd discovery-agent-<version>/config
```
2. In the discovery-agent-<version>/config/CONFIG.YML configuration file, update the ZRDDS_HOST_NAME value with the IP address of your zCX instance.
In ServiceNow, perform the following steps to update the Kafka connections to use the zCX instance IP address:
1. In ServiceNow, search for Kafka Instances.
  The following Kafka instances are displayed. Open and update each instance one at a time:
  - IBM_Z_JCL_Group1
  - IBM_Z_CI_Group1
  - IBM_Z_Reference_Group1
2. In the Kafka instance record, locate the Kafka Connection field.
  - If no connection is associated, click the Search icon and create a HTTP(s) connection.
  - If a connection is already associated, hover over the i icon and click Open Record.
3. On the HTTP(s) Connection page, update the Connection URL to use the zCX instance IP address in the following format: https://<zcx_ip_address>:8085.
4. Verify that the Connection alias is x_ibmg3_ibm_zsyste.IBM_Z_Discovery_Kafka_Connection_Alias_1.
5. Click Update.
Ensure that you repeat this procedure for all three Kafka instances to use the zCX instance IP address.