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 SCM: 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. Set up Git repository:

   1. You can bring your own existing Git repositories hosted on any standards-compliant Git distribution, such as OCI DevOps, GitHub, GitLab, Bitbucket, and so on, or
   2. If you want SCM to create the repositories as part of Siebel CRM provisioning:
      • Set up a GitLab instance.
      • Generate a private key and an access token.

2. Set up SCM:

   1. Navigate to OCI and in marketplace applications, choose SCM and launch a stack in OCI resource manager.
   2. For your local instance of Git that is not a hosted service requiring CA signed certificate; for example, if you are using GitLab installed by you, copy the private key generated from the Git instance into a secure location in the SCM container.
   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. Deploy Siebel CRM:

   1. Create a payload according to your chosen infrastructure provisioning option:
      • For a fully SCM provisioned environment for Siebel CRM deployment, provide the infrastructure details in the payload by referring the user guide.
      • For BYOD, provide the details of the existing database and infrastructure resource.
      • For BYOR, provide the details of all existing resources.
      Note: In case of BYOR or BYOD make sure connection exists between:

      • The database and the OKE cluster.
      • The mount target and the OKE cluster.
   2. Use the /environment API to create the Siebel CRM deployment using POST method.
      • Review the API response for validation errors or successful environment information.
      • Use the environment entity in the response to monitor deployment progress.

General info on provisioning, debugging and retrial

The provisioning of Siebel CRM environment occurs in a series of stages until the SMC and component URLs are published. If a failure occurs in any stage, the stage is marked with a "failed" status. You can access the log links in each stage to diagnose issues and take corrective actions. All the stages are idempotent, you can re-run the workflow using the environment's PUT method to restart all stages.