Optional: Changing the IP addresses and host names in the IBM MQ configuration

The IBM® MQ configuration might have IP addresses and host names specified. In some situations these can remain, while in other situations they need to be updated.

Before you begin

This task assumes that you have configured LDAP.

About this task

Do I need to do this?

First, determine if you have any IP addresses or host names specified, apart from the LDAP configuration defined in the previous section. To do this, run the following command:


grep 'CONNAME\|LOCLADDR\|IPADDRV' -B 3  backup.mqsc

Sample output:


****************************************************
DEFINE AUTHINFO(USE.LDAP) + 
   AUTHTYPE(IDPWLDAP) + 
   CONNAME('ldap-service.ldap(389)') + 
--
DEFINE AUTHINFO('SYSTEM.DEFAULT.AUTHINFO.IDPWLDAP') +
   AUTHTYPE(IDPWLDAP) +
   ADOPTCTX(YES) +
   CONNAME(' ') +
--
   REPLACE
DEFINE AUTHINFO('SYSTEM.DEFAULT.AUTHINFO.CRLLDAP') +
   AUTHTYPE(CRLLDAP) +
   CONNAME(' ') +

In this example the search returns three results. One result corresponds to the LDAP configuration defined previously. This can be ignored, because the hostname of the LDAP server is remaining the same. The other two results are empty connection entries, so these can be ignored as well. If you do not have any additional entries, you can skip the remainder of this topic.

Procedure

Understand the entries returned.
IBM MQ can include IP addresses, host names and ports within many aspects of the configuration. We can classify these into two categories:
1. This queue manager location: Location information that the queue manager uses or publishes, that others within an IBM MQ network can use for connectivity.
2. Location of queue manager dependencies: The locations of other queue managers or systems that this queue manager needs to be aware of.
Because this scenario is focused only on the changes to this queue manager configuration, we only handle the configuration updates for category (a). However, if this queue manager location is referenced by other queue managers or applications, their configurations might need updating to match this queue manager's new location.

There are two key objects that might contain information that needs to be updated:
- Listeners: These represent the network address that IBM MQ is listening on.
- CLUSTER RECEIVER channel: If the queue manager is part of an IBM MQ cluster, then this object exists. It specifies the network address that other queue managers can connect to.
In the original output from the grep 'CONNAME\|LOCLADDR\|IPADDRV' -B 3 backup.mqsc command, identify if any CLUSTER RECEIVER channels are defined. If so,update the IP addresses.
To identify if any CLUSTER RECEIVER channels are defined, find any entries with CHLTYPE(CLUSRCVR) in the original output:
```
DEFINE CHANNEL(ANY_NAME) +
   CHLTYPE(CLUSRCVR) +
```
If entries do exist, update the CONNAME with the IBM MQ OpenShift® Route. This value is based on the OpenShift environment and uses a predictable syntax:
```
queue_manager_resource_name-ibm-mq-qm-openshift_project_name.openshift_app_route_hostname
```
For example, if the queue manager deployment is named qm1 within the cp4i namespace, and the openshift_app_route_hostname is apps.callumj.icp4i.com, then the route URL is this:
```
qm1-ibm-mq-qm-cp4i.apps.callumj.icp4i.com
```
The port number for the route is typically 443. Unless your OpenShift Administrator tells you differently, this is normally the correct value. Using this information, update the CONNAME fields. For example:
```
CONNAME('qm1-ibm-mq-qm-cp4i.apps.callumj.icp4i.com(443)')
```
In the original output from the grep 'CONNAME\|LOCLADDR\|IPADDRV' -B 3 backup.mqsc command, verify if any entries exist for LOCLADDR or IPADDRV. If they do, delete them. They are not relevant in a container environment.

What to do next

You are now ready to update the queue manager configuration for a container environment.