Migrating Persistent Volume Content from Prior Releases to Siebel CRM 21.2 or Later

This topic is part of Migrating Persistent Volume Content.

The new Siebel CRM installer provided as of Siebel CRM 21.2 optimizes the Siebel CRM release and allows all aspects of Siebel CRM to be installed into a single container, thereby simplifying deployment. This also means that the container has two instances of Apache Tomcat installed: one for SES and CGW operation modes, and one for SAI operation mode.

Prior to Siebel CRM 21.2, the container had a directory called applicationcontainer, which is replaced by applicationcontainer_internal (for SES and CGW modes) and applicationcontainer_external (for SAI mode).

Thus, if you want to use persistent volumes that you have previously configured for pre-21.2 containers with 21.2 or later containers, then you need to rename the applicationcontainer directory in your SES and CGW persistent volume directories to applicationcontainer_internal, and to rename the applicationcontainer directory in the SAI persistent volume directory to applicationcontainer_external.

Also, the old server.xml file configured for SAI for pre-21.2 containers must be replaced, because static Siebel content has moved from siebel.war (from which it was unpacked to the webapps/siebel directory) to siebelwebroot. It is recommended that you delete the conf directories for all tiers in order to reset them fully.

To make the necessary changes, create a script similar to the following:

mv SAI/applicationcontainer SAI/applicationcontainer_external
mv SAI/applicationcontainer_external/conf SAI/applicationcontainer_external/conf_backup
mv SES/applicationcontainer SES/applicationcontainer_internal
mv SES/applicationcontainer_internal/conf SES/applicationcontainer_internal/conf_backup
mv CGW/applicationcontainer CGW/applicationcontainer_internal
mv CGW/applicationcontainer_internal/conf CGW/applicationcontainer_internal/conf_backup

Alternatively, you can empty your persistent volume directories and set up your container deployment again from scratch.

You must make these changes before launching the containers for the first time for Siebel CRM 21.2 or later.

Note: Also perform the steps described in Migrating Persistent Volume Content from Prior Releases to Siebel CRM 21.4 or Later and Migrating Persistent Volume Content from Prior Releases to Siebel CRM 22.6 or Later.