Deploying and Launching the Siebel Containers

This topic is part of Configuring and Running the Siebel Applications.

Parameters to launch and configure the environment are stored in a configuration file, such as sample-architecture-19.sh. In almost all cases, you will need to read and edit the parameters in this file. To do this, it is recommended to first copy this file to a new name, as appropriate for your deployment.

To set the environment definitions in the configuration file:

As appropriate, copy the sample-architecture-19.sh file to a new name (for example, siebent.sh), and make appropriate changes to the parameters in the file copy. The main parameters you are likely to need to change are the following:
- PV. Set PV to point to the location you chose to store persistent volumes. For example:
```
PV=/var/lib/docker/volumes/PV
```
- ROOT. Set ROOT to point to the location where the automate-architecture folder exists, which is part of the launch system you cloned from GitHub. For example:
```
ROOT=/home/demoadmin/dev/oraclesiebel/oraclelinux/manage/scripts/automate-architecture
```
- DOMAIN. Set DOMAIN to match the domain for which the SSL certificate was generated. For containers obtained from ARU, set this to company.com. If you are building your own containers, then adjust appropriately. The value siebel.local is correct only if you build your container using the supplied build system from GitHub.
```
DOMAIN=siebel.local
```
- CONTAINERBASE. Set CONTAINERBASE to match the image name, which you can see using the docker images command. For containers obtained from ARU, set this to store/oracle/siebel.
```
CONTAINERBASE=registry.local.com:5000/siebel
```
- COMPGRPS. Set COMPGRPS to the component groups that will be configured using the configure command later in this guide.
```
COMPGRPS=callcenter,siebelwebtools,eai
```
Once the environment parameters are set, start the containers for the enterprise using a command like the following:
```
bash startAll19 version parameter_file
```
For example, you might use the following command for Siebel CRM 22.6:
```
bash startAll19 22.6 siebent.sh
```

The example script startAll19 launches four containers. First, it launches the database engine, then the SAI container, the CGW container, and finally the SES container.

The given setup assumes that the sample-architecture-19.sh parameter file (or siebent.sh in the example) describes the base location for the persistent volumes using the variable PV. The PV directory contains a directory named by the ENTERPRISE parameter, and this directory contains the subdirectories CGW, SES, SAI, and SFS. Create these directories before the first run, as described in Creating Directories for Persistence Volumes that Store the Container Configurations. These directories must be writeable by the user who will run the scripts, as defined by the parameter RUNASUSER.

If the persistence directories are empty on the first run, then they are populated during the launch of the containers. If they were populated by a previous run, then the contents already present are used. This is the primary mechanism by which the state is saved for the enterprise.