1. Deploying Siebel CRM Containers on Kubernetes using Siebel Cloud Manager
  2. Customizing Configurations Prior to Greenfield Deployment

Customizing Configurations Prior to Greenfield Deployment

In a greenfield deployment scenario, when you deploy a Siebel CRM environment as described in Deploying Siebel CRM on OCI, by default the environment is automatically configured and provisioned as a single step. This topic describes how you can optionally decouple the configuration and provisioning stages, for the purpose of customizing the configuration before you provision the environment.

Configurations are maintained in Git repositories for your subsequent customization and use. The configurations present in Git repositories are the source for environment provisioning in this use case.

Once you've created a configuration, you can customize it according to your requirements. Configuration customizations can include any of the types of changes described for deployed environments in Making Incremental Changes to Your Siebel CRM Deployment on OCI. Examples include adding or deleting components on a server, adding new profiles, or adding or deleting parameters for an enterprise, server, or component.

You can use your customized configuration as a base for provisioning multiple environments, such as for test or production purposes. To do this, you must pass the configuration ID during the provisioning step.

Configuration options for a Siebel CRM greenfield deployment on OCI have the following use cases:

  • Greenfield deployment use case 1 (default configuration). In this use case, you use SCM to deploy a new Siebel CRM environment on OCI with a default configuration.

  • Greenfield deployment use case 2 (customized configuration). In this use case, you use SCM to deploy a new Siebel CRM environment on OCI with a customized configuration. The configuration is created first (for which a configuration ID is generated), then you customize the configuration, and then you deploy it for one or more environments. This is the use case described in this topic.

For an example payload and usage guidelines, see Example Payload to Deploy Siebel CRM.

Note: After deployment, any configuration changes must be made in the deployed environment, as described in Making Incremental Changes to Your Siebel CRM Deployment on OCI. If you require the same changes in the original customized configuration that you created using greenfield configuration use case 2, then you must make the same changes in both locations.

This topic contains the following information:

Related Topics

Deploying Siebel CRM on OCI

Checking the Status of a Requested Configuration

Making Incremental Changes to Your Siebel CRM Deployment on OCI

Creating the Configuration and Obtaining the Configuration ID

This topic is part of Customizing Configurations Prior to Greenfield Deployment.

If you plan to customize the configuration prior to provisioning the environment for greenfield deployment use case 2, then the first step is to create the configuration and to obtain the six-character ID for this configuration.

To create the configuration and obtain the configuration ID

  • Do a POST API like the following: 

    POST https://<CM_Instance_IP>:16690/scm/api/v1.0/configuration
    Note: Specify a payload appropriate for greenfield deployment use case 2. For an example payload and for usage guidelines, see Example Payload to Deploy Siebel CRM.

    The configuration is created and its configuration ID is returned, such as MZM3RJ.

    As a result of the above POST API, if the git_type is set to gitlab, the following two Git repositories are created:

    • config_<namespace>_<config_id>-helmcharts

      (for example: config_stage_MZM3RJ-helmcharts) 

    • config_<namespace>_<config_id>-cloud-manager

      (for example: config_stage_MZM3RJ-cloud-manager)

    This configuration can be accessed at the following location inside the SCM container by SSH into the SCM instance. 

    /home/opc/siebel/configuration/MZM3RJ

    Enter commands like the following:

    docker exec -it cloudmanager bash
    You can use a selfLink like the following for monitoring purposes:
    https://<CM_Instance_IP>:16690/scm/api/v1.0/configuration/MZM3RJ

Customizing the Configuration

This topic is part of Customizing Configurations Prior to Greenfield Deployment.

After creating a configuration and obtaining its configuration ID, you can customize this configuration prior to provisioning the environment (greenfield deployment use case 2).

To customize Siebel CRM configuration that require changes in helm charts repository

For example, for adding a custom component, changing parameter values in a component, enabling/disabling components, named subsystem changes, component definition changes and so on.

  1. SSH into the SCM instance.

  2. Enter commands like the following: 

    docker exec -it cloudmanager bash 
cd /home/opc/siebel/configuration/<config_id>/config_<namespace>_<config_id>-helmcharts/siebel-config/paramconfig

    The paramconfig folder has files supporting this Siebel CRM configuration. For more information about customization use cases and the YAML or other configuration files that you can modify, see Making Incremental Changes to Your Siebel CRM Deployment on OCI. (For existing deployments, the paramconfig folder is in a different location.)

  3. Make all changes necessary to customize the configuration files.

  4. Enter commands like the following to commit your customization in the helm charts Git repository. Make sure to add all modified files: 

    cd /home/opc/siebel/configuration/<config_id>/config_<namespace>_<config_id>-helmcharts/siebel-config
git add .
git commit -m "<customization note>"
git push

    The above changes will be included in the initial environment provisioning, where you specify the configuration ID.

  5. Check the status of a requested configuration, as described in Checking the Status of a Requested Configuration.

  6. Deploy the environment with the customized configuration, as described in Deploying Siebel CRM on OCI. In this step (for greenfield deployment use case 2), you specify only the configuration ID and the deployment name.

To customize Siebel CRM Kubernetes deployment parameters that require changes in the SCM repository

For example, for changing the number of replicas for SES or SAI, adding a new SiebServer Profile, setting resources like CPU and memory specific to individual Siebel Server and so on.

  1. SSH into the SCM instance.

  2. Enter commands like the following: 

    docker exec -it cloudmanager bash

    Edit the /home/opc/siebel/<env_id>/<Cloud manager repository name>/flux-crm/apps/base/siebel/siebel.yaml file to add "sesResources" for each Siebel server as:

    siebelServer:
  - profile: siebel
    replicas: 1
    sesResources:
      limits:
        cpu: 4
        memory: 24Gi
      requests:
        cpu: 1
        memory: 8Gi
    siebsrvr_prefix: edge
  - profile: siebel
    replicas: 1
    sesResources:
      limits:
        cpu: 4
        memory: 24Gi
      requests:
        cpu: 1
        memory: 8Gi
    siebsrvr_prefix: tibus
    Note: sesResources defined at the profile level for individual Siebel server takes higher precedence over the generic sesResources overridden in payload.
  3. Make all changes necessary to customize the configuration files.
  4. Commit your customization in the SCM Git repository. Make sure to add all modified files. The above changes will be included in the initial environment provisioning, where you specify the 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, as described in Deploying Siebel CRM on OCI using Siebel Cloud Manager. In this step (for greenfield deployment use case 2), you specify only the configuration ID and the deployment name.