Deploy and Configure Siebel Cloud Manager

For this solution, we will deploy Siebel Cloud Manager, available on the OCI Marketplace.

Deploy Siebel Cloud Manager:

1. Navigate to Oracle Cloud Marketplace and select the latest Siebel Cloud Manager image.
2. Choose the appropriate compartment and review the terms and conditions. Once reviewed, click Launch Stack.

Configure Stack information:

3. Review the stack details. If required, update the stack name.
4. Click Next to proceed.

Configure Variables:

5. On the Configure Variables page, provide details for the following sections:
   • General
   • Permissions
   • VCN
   • Compute
   • Storage
   • Key Management
   • Advanced Network Configuration

Review and create the Stack:

6. Review the configuration details and click Create.

Monitor Stack execution:

7. Monitor the execution of the Siebel Cloud Manager stack until it is successfully completed.
   Once completed, review the logs in the Output section for URLs of the following: Siebel Cloud Manager (SCM), Lift Utility, Shift Utility.

Configure the Siebel Lift Utility

After you have deployed the Siebel Cloud Manager, download and configure the Siebel Lift Utility.

Download and Configure the Siebel Lift Utility:

1. Get the siebelliftutility_container.zip file from Siebel Cloud Manager.
2. Extract the contents of the ZIP file.
3. Install and configure Docker software for managing containers.

   Note:

   When running the Siebel Lift Utility in the Docker container to generate database artifacts (deployment kits), ensure the correct database client location is provided.
4. Update the volumemounts.ini file and tnsnames.ora file with the required values.

Validate Siebel Cloud Manager:

5. Access the Siebel Cloud Manager URL through a web browser to validate its deployment.

Prepare a Payload for Siebel Environment creation:

6. Prepare a JSON payload containing the following sections:
   • Siebel section:
     • registry_url
     • siebel_architecture
     • registry_user
     • registry_password
     • database_type
     • industry
   • Infrastructure section:
     • gitlab_url
     • gitlab_accesstoken
     • gitlab_selfsigned_cacert
     • siebel_cluster_subnet_ocid
     • siebel_lb_subnet_ocid
     • siebel_private_subnet_ocid
     • siebel_db_subnet_ocid
     • vcn_ocid_of_db_subnet
     • load_balancer_type
   • Database section:
     • db_type
     • db_version
     • db_home_admin_password
     • data_storage_size_in_gbs
     • db_admin_password
   • Auth Info section:
     • siebel_admin_username
     • siebel_admin_password
     • default_user_password
     • table_owner_password
     • table_owner_user
     • anonymous_user_password
   • Size section:
     • kubernetes_node_shape
     • kubernetes_node_count
     • node_shape_config
     • ses_resource_limits
     • ses_resource_requests
     • cgw_resource_limits
     • cgw_resource_requests
     • sai_resource_limits
     • sai_resource_requests

Create a Vault for Master Encryption Keys and Secrets:

7. Create a vault to manage the encryption keys and secrets required for the environment.

Execute the Payload:

8. Submit the prepared payload using a tool such as Postman:
   • Endpoint: POST http://siebelcloudmanager:16690/scm/api/v1.0/environment/
   • Authorization: Basic Auth (Username: admin, Password: **************)
   • Body: Raw JSON payload.

Monitor the environment build:

9. Upon successful submission, an environment ID is generated.
10. Monitor the build via the OCI Console or by sending a GET request using the environment ID: Endpoint: GET http://localhost:16690/scm/api/v1.0/environment/env_id. Alternatively, check the Resource Manager under Stacks.

• The Siebel environment can be accessed using the URL.
• A Siebel OKE cluster with three worker nodes is deployed.
• The Siebel database is provisioned as Oracle Base Database Service.