Upgrading from a non-container application to a container model

To enable the upgrade mode, ensure that the old runtime folder is accessible within the base container. You can upgrade from a single-schema runtime to a containerized single-schema cpq-ifs-base container or a multi-schema runtime to a containerized multi-schema cpq-ifs-base container.

To upgrade from a non-container application to a container application, complete the following steps:

1. Access an old runtime from a container.
2. Prepare an ifs-base container for upgrade.
3. Complete either single-schema or multi-schema upgrade.
4. Activate the multi-schema mode.
5. Complete upgrade.
6. Validate your upgrade.
7. Complete post migration tasks.

If you cannot view the contents of the destination directory, ensure that all permissions are granted to your previous runtime and its respective mounted directory on your container. You can change the file permissions of a directory and its sub-directories by using a recursive chmod command as follows:

• To grant full permission to ifs-host, from host machine, run the following command:
  chmod -R 777 /opt/IBM/Sterling95
• To grant full permission to ifs-95, from cpq-ifs-base, run the following command:
  chmod -R 777 /opt/ssfs/shared

Before you upgrade, ensure that your database properties are updated in the sandbox.cfgfile of ifs-10 upgrade environment by specifying the database properties during installation, after installation, or during container creation. In the example provided for creating cpq-ifs-base, the sandbox.cfg file is created without specifying the necessary database properties. Therefore, you must add the necessary database properties such that ifs-10 can connect to the database. Confirm the values of the following database properties in /opt/ssfs/runtime/properties/sandbox.cfg:

• DB_PASS
• DB_USER
• DB_SCHEMA_OWNER
• DB_DATA
• DB_PORT
• YANTRA_DB_PASS
• YANTRA_DB_USER

For Oracle:

• ORA_PASS
• ORA_HOST
• ORA_USER

For Db2:

• DB2_PASS
• DB2_HOST
• DB2_USER

To activate the changes you make, run the following command.

./setupfiles.sh

To upgrade from a single-schema instance, complete the following steps:

1. If your IBM Field Sales (INSTALL_DIR_SS) instance is present in a Docker container, you might not be able to access your old runtime files (INSTALL_DIR_SS_OLD). To access your old runtime files, mount the INSTALL_DIR_SS_OLD to the Docker container where INSTALL_DIR_SS is located. When you mount the old runtime to the runtime of a new container, create a destination folder for your old runtime and grant full permissions to the destination folder.
2. Run the following Docker command to mount INSTALL_DIR_SS_OLD to the newly created folder:
   docker run -ti --privileged -e LICENSE=accept -v <path_of_the_old_runtime>:<path_of_the old_runtime_inside_the_container> <cpq-ifs-base>
   Browse to the destination folder and verify the contents of INSTALL_DIR_SS_OLD.

   Note: If you cannot access the destination folder, ensure that full permissions are granted.

To upgrade from a multi-schema instance, complete the following steps:

1. Set the following properties in the INSTALL_DIR_MS/sandbox.cfg file.
   • multischema.enabled=true
   • multischema.version=10.0
   • multischema.file= <set the value to a valid 10.0 version colony.xml>. For more information, see Sample silent addColony.xml file.
     Note: During installation, if you create colonies, you need not set the value for multischema.file.
2. If your IBM Field Sales (INSTALL_DIR_MS) instance is present in a Docker container, you might not be able to access your old runtime files (INSTALL_DIR_MS_OLD). To access your old runtime files, mount the INSTALL_DIR_MS_OLD to the Docker container where INSTALL_DIR_MS is located. When you mount the old runtime to the runtime of a new container, create a destination folder for your old runtime and grant full permissions to the destination folder.
3. Run the following command:
   INSTALL_DIR_MS/bin/setupfiles.sh/.cmd
4. Run the following Docker command to mount INSTALL_DIR_MS_OLD to the newly created folder:
   docker run -ti --privileged -e LICENSE=accept -v <path_of_the_old_multischema_runtime>:<path_of_the old_runtime_inside_the_container>
   Browse to the destination folder and verify the contents of INSTALL_DIR_MS_OLD.

   Note: If you cannot access the destination folder, ensure that full permissions are granted.

To activate the multi-schema mode, complete the following steps:

1. Configure the following properties:
   • multischema.enabled=true
   • multischema.version=<containerized version>
   • multischema.file= <set the value to a valid containerized version (10.0) colony.xml>. For more information about the colony.xml file, see Sample silent addColony.xml file.
2. Activate the changes by running the following command:
   ./setupfiles.sh

After upgrading your single-schema or multi-schema runtime, you can validate whether the upgrade is successful by completing the following steps:

1. Run DB verify from ifs-10 to ensure all your entity changes are captured and no alters are generated.
2. Generate the application (cpq-ifs-app) and agent (cpq-ifs-agent) containers. For more information about generating the application and agent containers, see Generating custom images.
3. Deploy cpq-ifs-app and cpq-ifs-agent in your OpenShift® Container Platform. For more information about deploying the containers, see Deploying IBM Field Sales on OpenShift Container Platform.
4. Launch the Applications Manager. Go to Help > About, and verify the version. Validate that the customizations you applied are enabled.