1. Deploying Siebel CRM Containers
  2. Migrating Persistent Volume Content from Prior Releases to Siebel CRM 22.6 or Later

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

This topic is part of Migrating Persistent Volume Content.

Note: If you are coming from a version earlier than Siebel CRM 21.2 to Siebel CRM 22.6 or later, then first read and act upon the information in Migrating Persistent Volume Content from Prior Releases to Siebel CRM 21.2 or Later and Migrating Persistent Volume Content from Prior Releases to Siebel CRM 21.4 or Later. If you are coming from Siebel CRM 21.2 or 21.3 to Siebel CRM 22.6 or later, then first read and act upon the information in Migrating Persistent Volume Content from Prior Releases to Siebel CRM 21.4 or Later before performing this task.

Siebel CRM 22.6 and later releases provide a new version of Apache ZooKeeper, which is used for the Siebel Gateway registry. As result, there is a change to the persistent volume content for the container acting as the CGW node. For more information about ZooKeeper and Siebel Gateway, see also Siebel Installation Guide on the Siebel Bookshelf.

You only need to take action if you have a need to make custom additions to the registry.properties file that ZooKeeper uses. In previous versions, this file was considered persistent, meaning that changes made would persist between Siebel updates. However, because new content is required for Siebel CRM 22.6 or later to function, this model has been changed. Instead, the registry.properties file is recreated every time the Siebel container starts.

To customize the registry.properties file, you need to take one of two actions:

  • Add a custom container layer. Using a Docker file, replace the registry.properties file stored in the location /siebel/mde/gtwysrvr/registry/conf.

  • Provide a registry.properties.process file. The goal of the registry.properties.process file is to create the registry.properties file. At a minimum, this file must copy /siebel/mde/gtwysrvr/registry/zookeeper/conf/registry.properties (consider this a template). However, the registry.properties.process file might also make additional changes using standard UNIX tools such as sed and awk in order to modify the contents.

    If you create a file called registry.properties.process in the persistence volume for CGW, located in /scratch/persistent/PV/ENT2/CGW/gtwysrvr/registry/conf, then this file will be processed before registry.properties is read. If registry.properties.process fails to create registry.properties in the correct location, then the template file will be used, ensuring a working enterprise.