General Pre-Migration Steps for Platform Nodes

Before you start the migration of CloudBlue Commerce platform nodes to Azure cloud, perform the following preparatory steps for each platform node:

1. Make sure that there is enough free space to store the backed-up data.
2. Apply a workaround for the PPM redeployment.
3. Deploy the destination nodes according to Hardware Requirements.
4. Make sure that the firewall requirements are satisfied.

5. Assign a temporary IP address to the destination node.

   Important: The network interface names must be the same for the corresponding source and destination hosts. For example, if the BackNet IP address of a source node is bound to the eth0 interface, the same binding must be configured on the destination node. For instructions on how to update the network interface name of a host, please refer to KB 132165.

6. To reload the Billing encryption keys after the migration, make sure that they are available.
7. Make sure that the operating system on the destination node is up to date. To update the OS on the destination node, run the yum update command.

8. Check to make sure that CloudBlue Commerce Central YUM Repository is accessible from the destination node by executing the following command:

   curl -LI http://download.platform.cloudblue.com/cb/20.5/repo/RHEL/7/repodata/repomd.xml

   After executing this command, the system must return the HTTP 200 code.

9. Make sure that the EPEL repository is not enabled on the destination host. Make sure that CentOS repositories base, updates, and extras are enabled and available. To check it, run the following command:

    yum repolist -v and fix

10. Make sure that the hostname of the source node is resolved to the backnet IP address of the source node. To do so:

    1. Check the hostname IP address:

       hostname -i

    2. Set the hostname:

       hostnamectl set-hostname <NAME>

11. Check to make sure that the destination node has no PostgreSQL RPMs installed by executing this command:

    yum list installed postgresql*. To remove the unnecessary postgresql RPMs, run the command yum remove postgresql*.

12. Check to make sure that the destination node has no OpenJDK RPMs installed by executing this command:

    yum list installed *openjdk*

    To remove the unnecessary packages, run the following command:

    yum remove *openjdk*

A Workaround for the PPM Redeployment

To fix PPM redeployment issues for CloudBlue Commerce 20.5, apply the following workaround:

1. Log in to Operations Management Node as root.
2. Download the core-ear.ear artifact to the /root/ directory.

3. Enter Jboss CLI using this bash command:

    /usr/local/pem/wildfly-11.0.0.Final/bin/jboss-cli.sh --connect

4. Obtain the current list of library deployments in Wildfly:

   deployment-info

5. Disable all deployments (by undeploying all of them while keeping content):

   undeploy --keep-content *

6. Redeploy and enable core-ear.ear with the artifact downloaded above:

   deploy /root/core-ear.ear --force --enabled

7. Enable the remaining deployments in the following order:

   Important: If any of the artifacts below was not listed in step 4, do not deploy it. If in step 4 there were other artifacts not listed below, deploy them after bss-war.war:

   1. deploy --enabled --name=pui-war.war
   2. deploy --enabled --name=whl-endpoint-war.war
   3. deploy --enabled --name=exchange-war.war
   4. deploy --enabled --name=bss-war.war

8. Check the deployment statuses with this command:

   deployment-info

   All the statuses must be OK.