Migrating to Connect:Direct® for UNIX using Certified Container Software
Follow the steps given below to create a backup and restore IBM Connect:Direct for Unix using
Certified Container Software:
- Create a backupTo create a backup of configuration data and other information such as stats and TCQ, present in the persistent volume, follow the steps given below:
- Go to mount path of Persistent Volume.
- Make copy of the following directories and store them at a secured location:
- WORK
- SECURITY
- CFG
- SECPLUS
- PROCESS
- FACONFIG
- FALOGNote:
- Update the various values in
initparm.cfg
,netmap.cfg
andndmapi.cfg
for the C:D installation path, hostname/IP and port numbers. The installation path is `/opt/cdunix/` , hostname would be <helm-release-name>-ibm-connect-direct-0 and client port is 1363 and server port is 1364. -
The nodename of Connect:Direct for Unix running on traditional system should be same while migrating it inside container.
- If Connect:Direct for UNIX is installed in a conventional mode, create a backup of the following
directories:
- <install_dir>/work
- <install_dir>/ndm/security
- <install_dir>/ndm/cfg
- <install_dir>/ndm/secure+
- <install_dir>/process
- <install_dir>/file_agent/config
- <install_dir>/file_agent/logA file must be created in a work directory before taking backup. The file can be created by invoking the following command:
<path to cdunix install directory>/etc/cdver > <path to cdunix install directory>/work/saved_cdunix_version
- Update the various values in
- Restore the data in a new deploymentTo restore data in a new deployment, follow the steps given below:
- Create a Persistent Volume.
- Copy all the backed-up directories to the mount path of Persistent Volume.
- For other prerequisites such as secrets see, Pre-installation tasks.
- Upgrade to Certified Container SoftwareCreate a new instance of chart using the following helm CLI command:Helm version 2
helm install --name <release-name> --set license=true,image.repository=<reponame> image.tag=<image tag>,cdArgs.crtName=<certificate name>,image.imageSecrets=<image pull secret>,secret.secretName=<C:D secret name> ibm-connect-direct-1.1.x.tgz
Helm version 3helm install <release-name> --set license=true,image.repository=<reponame> image.tag=<image tag>,cdArgs.crtName=<certificate name>,image.imageSecrets=<image pull secret>,secret.secretName=<C:D secret name> ibm-connect-direct-1.1.x.tgz
Note: The nodename of Connect:Direct for Unix running on traditional system should be same for
migration to IBM Certified Container Software. Configure the nodename using "cdArgs.nodeName"
parameter.