Identifying the proxy listening port

To connect to the IBM® Tivoli® Netcool®/OMNIbus Object Server pair from outside the OpenShift® cluster with Transport Layer Security (TLS) encryption, you must identify the externally accessible port where the proxy listens for connections.

About this task

The proxy defines a Kubernetes service, called release_name-proxy, where release_name is the name of the custom resource for your deployment. The release_name-proxy service defines the ports that clients must use when connecting to the Object Server pair.

1. Describe the proxy service by running the following command:

   kubectl get service -o yaml release_name-proxy -n namespace

   Where

   • <release_name> is the name of your deployment, as specified by the value used for name (Operator Lifecycle Manager UI Form view), or name in the metadata section of the noi.ibm.com_noihybrids_cr.yaml or noi.ibm.com_nois_cr.yaml files (YAML view).
   • namespace is the name of the namespace in which Operations Management is installed.
2. Identify the ports from the command output, for example:

     ports:
     - name: aggp-proxy-port
       port: 6001
       protocol: TCP
       targetPort: 6001
     - name: aggb-proxy-port
       port: 6002
       protocol: TCP
       targetPort: 6002
   

   In the example, the port for the primary Object Server is 6001 and the port for the backup Object Server is 6002.

   When NodePort service types are deployed, the NodePort value is used, for example:

     ports:
     - name: aggp-proxy-port
       nodePort: 30135
       port: 6001
       protocol: TCP
       targetPort: 6001
     - name: aggb-proxy-port
       nodePort: 30456
       port: 6002
       protocol: TCP
       targetPort: 6002
   

   In the example, the port for the primary ObjectServer is 30135 and the port for the backup ObjectServer is 30456.

Results

Make a note of the ports that you identified. Refer to these ports as follows:

• ${AGGP_PROXY_PORT} for the primary aggregation ObjectServer.
• ${AGGB_PROXY_PORT} for the backup aggregation ObjectServer.

This information is required when configuring the client's Transport Layer Security (TLS) connection.