1. Deploying Siebel CRM Containers on Kubernetes using Siebel Cloud Manager
  2. High Level Steps to Deploy Siebel Using SCM

High Level Steps to Deploy Siebel Using SCM

The term "BYO" stands for "Bring Your Own" and is indicative of existing resources at the disposal of the user. For example BYOD stands for "Bring Your Own Database".

Siebel CRM applications can be deployed using SCM in different ways based on the type of infrastructure information provided in the Siebel CRM deployment payload after SCM has been set up:

  1. User brings all resources (Fully BYOR): When you select "Use existing resource" while provisioning SCM, all the resources such as existing mount target, file system, OKE, database must be provided by the user as part of payload information that the SCM instance will use to create Siebel CRM deployment(s).

  2. SCM creates resources:

    • All infra resources are created by CM: If you don't select "Use existing resource" while provisioning SCM, all the required infrastructure for a Siebel CRM deployment that is database, OKE, mount target, file system, and so on will be created and configured by SCM.
    • All infra resources except database created by SCM (BYOD only): When you don't select "Use existing resource" while provisioning SCM, user can still provide information of an existing database in the payload. All other infra resources (mount target, file system, OKE, etc.) will be created by the SCM for Siebel CRM deployment. User must ensure that database can be connected from SCM and OKE.

The following are the high level steps to deploy Siebel CRM on OCI (these are described in detail later in this document):

  1. GitLab setup:

    1. Setup a GitLab instance.
    2. Generate a private key and an access token.

  2. SCM setup:

    1. Navigate to OCI and in marketplace applications, choose SCM and launch a stack in OCI resource manager.
    2. Copy the private key generated from GitLab instance in a secure location inside SCM instance.
    3. Based on the type of deployment, whether BYOR (Bring Your Own Resource) or BYOD (Bring Your Own Database only) or fully SCM provisioned, provide inputs.
    4. If BYOR, click "Use existing resource" and provide details of the existing resource such as VCN, subnet to launch instance, policies etc.
    5. On successful job, copy the URL present in the outputs and navigate in browser to verify SCM setup.

  3. Siebel CRM deployment:

    1. If a fully SCM provisioned environment for Siebel CRM deployment is to be created, then provide infrastructure details in the payload by referring the user guide.
    2. If BYOD, provide the details of the existing database and infrastructure resource info to be created.
    3. If BYOR, provide the details of all existing resources.
    4. In case of BYOR or BYOD make sure connection exists between the relevant resources that is database to OKE cluster, mount target to OKE cluster.
    5. Use the /environment API to create a deployment using POST method.
    6. The response of the API will either contain any validations if needed to be modified or with a successful environment info.
    7. The response will contain an environment entity which can be accessed to check the progress of the deployment.

  4. General info on provisioning, debugging and retrial:

    1. The provisioning of Siebel CRM environment will involve a series of stages after which the Siebel Management Console (SMC) and component URLs will be published.
    2. In case of any failure in any stage, the stage will show status as failed.
    3. Every stage will contain log links which can be viewed to find what went wrong.
    4. Relevant actions based on the logs have to be performed and the workflow has to be re-run. To re-run the workflow, use the environment's PUT method which will execute all the stages from beginning.
    5. All these stages are idempotent, so the workflow can be run n number of times until the last stage/ deployment is successful.