1. Deploying Siebel CRM Containers on Kubernetes using Siebel Cloud Manager
  2. Adding and Overriding Environment Variables by Customizing the Configuration

Adding and Overriding Environment Variables by Customizing the Configuration

You can use customization to add new environment variables and also override existing environment variables in the following Siebel pods:

  • Siebel Server pods such as edge, tibus and so on
  • SAI pods such as quantum, alchemist and so on
  • CGW pods
  • SMC pods

To add or override the environment variables:

Note: If you use SSH for Git, you must set the GIT_SSH_COMMAND environment variable in the current shell before you run your first remote Git command. For more information, see the "Configuring SSH for Manual Git Operations" section in Using Existing Git Repositories.
  1. SSH into the SCM instance:
    sudo podman exec -it cloudmanager bash
  2. Go to the /home/opc/siebel/<ENV_ID>/<Cloud manager repository name>/flux-crm/apps/base/siebel directory.
  3. Add the envlist parameter to the Siebel pod sections as required in the files specified below:
    Siebel Pod Sample Data
    Siebel server in the siebel.yaml file. 
    siebelServer:
- profile: siebel
      replicas: 1
      sesResources:
            limits:
                  cpu: 4
                  memory: 24Gi
            requests:
                  cpu: 1
                  memory: 8Gi
      siebsrvr_prefix: edge
      envlist:
      - name: SBL_HEAP_OPTS
            value: "-Xms700m -Xmx7G"
      - name: SIEBEL_LOG_EVENTS
            value: "2"
    SAI server in the siebel.yaml file. 
    saiServer:
- profile: sai_profile
      replicas: 1
      saiResources:
            limits:
                  cpu: 4
                  memory: 24Gi
            requests:
                  cpu: 1
                  memory: 8Gi
      saisrvr_prefix: quantum
      envlist:
      - name: SBL_HEAP_OPTS
            value: "-Xms700m -Xmx7G"
      - name: SIEBEL_LOG_EVENTS
            value: "2"
    CGW pod in the siebel-gateway.yaml file. 
    cgw:
      replicas: 3
      cgwResources:
            limits:
                  cpu: 4
                  memory: 24Gi
            requests:
                  cpu: 1
                  memory: 8Gi
      envlist:
      - name: SIEBEL_LOG_EVENTS
            value: "3"
    SMC pod in the siebel-gateway.yaml file. 
    smc:
      replicas: 1
      envlist:
            - name: SIEBEL_LOG_EVENTS
                  value: "1"
  4. Commit the customization in the SCM Git repository as follows:
    git pull
git add .
git commit -m "<message>"
git push
    Note: Ensure that you include all the modified files, as these changes will be included in the initial environment provisioning that is based on this configuration ID.
  5. Check the status of a requested configuration. For more information, see Checking the Status of a Requested Configuration.
  6. Deploy the environment with the customized configuration specifying the configuration ID and the deployment name. For more information, see About this Chapter.