Creating Directories for Persistence Volumes that Store the Container Configurations

This topic is part of Setting Up the Siebel Containers in Docker.

To be able to persist the configuration of the Siebel Enterprise Server and Oracle Database, you must create directories that will serve as persistence volumes. A persistence volume is, effectively, the saved state of the container. These are the files that reside outside of the Docker images and store one possible configuration of that image when instantiated as a container.

1. Decide where to create the persistence volume directories.

2. Use the mkdir command to create separate directories to store the configuration data. Create the following directories:

   • ORCL19. Include this directory if you are using the containerized database. You can omit this directory if you are using an existing database: for example, DBaaS or ATP.

   • ENT. Create this directory to contain all of the subdirectories pertinent to a single Siebel Enterprise. Under this directory, create the following directories:

     • CGW. Siebel Gateway (sometimes called the Cloud Gateway).

     • SAI. Siebel Application Interface.

     • SES. Siebel Server.

     • SFS. Siebel File System.

   Storing the enterprise configuration in the persistence volumes means that you do not need to reconfigure the enterprise after the virtual machine or the containers restart. They will load the persistent state and carry on from where they left off. You can also transport the enterprise state to other servers by copying the persistent volumes to another server.