Deploying Siebel Application Using Docker Image on Oracle Cloud Infrastructure with Vanilla Database


Options



Before You Begin

Purpose

This tutorial shows you how to deploy a complete Siebel CRM 2017-20 application with a vanilla database environment containing seed data only using Docker image and an Oracle 12c database to a virtual machine in Oracle Cloud Infrastructure (OCI) Service (Dedicated).

In this tutorial, you will set up Security Lists to enable HTTP access to your Siebel instance using ports 4430 and 8080. You will choose from the Oracle Cloud Marketplace the Siebel CRM Install Jenkins/Docker Instance image to install the Siebel Gateway, AI and Siebel Application Servers and connect to an Oracle database server containing vanilla data.

Note that the information presented here is based on Siebel CRM 2017-20, which is general availability since 2017.

Time to Complete

60 minutes

Background

Oracle Cloud Infrastructure Service enables you to rapidly provision virtual cloud machines (VCNs) on Oracle Cloud Infrastructure with the necessary storage and networking resources. After you’ve created your virtual machine instance, you can navigate and test out Siebel CRM IP2017/18/19 on the virtual machine.

What Do You Need?

A subscription to Oracle Cloud Infrastructure Service (Dedicated) is mandatory and you must be a user with the Compute_Operations and Storage Read Write Group roles.

For more details on creating Oracle Cloud Infrastructure Service instances, see the following:

Process Overview

To create the required Oracle Cloud Infrastructure Service instance to deploy the Siebel CRM application, you will:

  1. Generate an SSH key pair on your local system. (Prerequisite)
  2. Create a Virtual Cloud Network (Prerequisite)
    • Create a Subnet (Prerequisite)
    • Open Ports (Prerequisite)
  3. Request DBaaS DB Instance and Plug Siebel PDB to DBaaS DB Instance
    • Request DBaaS DB in OCI (Prerequisite for DBaaS DB)
    • Add DBaaS DB Ports in Security Ingress Rule in VCN (Prerequisite for DBaaS DB)
    • Attach PDB From OCIR DockerSidecar DBImage To DBaaS DB In OCI (Prerequisite for DBaaS DB)
      • Automated: Run the script
      • Manual: Get your own PDB and attach to DBaaS DB instance
    • Get orclNetDescString information from DBaaS in OCI (Prerequisite for DBaaS DB)
  4. Launch Jenkins/Docker image from Oracle Marketplace to create your initial Siebel instance into your Tenancy
  5. Deploy Siebel CRM Application
    • Generating Jenkins URL
    • Deploying the Siebel Application
      • Deploy using Docker DB
      • Deploy using DBaaS DB
    • Generating application domain URL
    • Changing the SADMIN Password
    • Upgrading Siebel DBaaS DB and Docker DB
    • Restarting Siebel DBaaS and Docker Services
  6. Log into the Siebel application.

Generating an SSH Key Pair

This is the first prerequisite.

When you create your Oracle Cloud Infrastructure Service instance, you must provide an SSH public key that will be used for authentication when you log in to the instance. Generate your SSH key pair. You can save the SSH key pair to either paste or upload to the Oracle Cloud Infrastructure Tenancy before you start to create your instance.

Generating an SSH Key Pair on UNIX or UNIX-Like Systems Using ssh-keygen

  1. Run the ssh-keygen command.
    ssh-keygen -b 2048 -t rsa
  2. The command prompts you to enter the path to the file in which you want to save the key. A default path and file name are suggested in parentheses. For example: /home/user_name/.ssh/id_rsa. To accept the default path and file name, press Enter. Otherwise, enter the required path and file name, and then press Enter.
  3. Note: The key should be created without a passphrase.

  4. The command generates an SSH key pair consisting of a public key and a private key, and saves them in the specified path. The file name of the public key is created automatically by appending .pub to the name of the private key file. For example, if the file name of the SSH private key is id_rsa, then the file name of the public key would be id_rsa.pub.
  5. Make a note of the path where you've saved the SSH key pair.
    When you create instances, you must provide the SSH public key. When you log in to an instance, you must specify the corresponding SSH private key.

Generating an SSH Key Pair on Windows Using the PuTTY Key Generator

  1. Find puttygen.exe in the PuTTY folder on your computer and double-click it. (If you do not have PuTTY.exe on your computer you can find it on web here http://www.putty.org/)
  2. Accept the default key type, SSH-2 RSA, and set the Number of bits in a generated key to 2048, if it is not already set. Then click Generate.

    Generate SSH key pair on Windows, PuTTY Key Generator

    If you do not see the SSH-2 RSA in key type options, go to Key in the menu.

    Generate SSH key pair on Windows, PuTTY Key Generator

  3. Move your mouse around the blank area to generate randomness. The SSH key pair is generated.

    Generate SSH key pair on Windows, generate randomness.

  4. Save your private key.
    1. The key comment is the name of the key. You can keep the generated key comment or create your own.
    2. Note: The key should be created without a passphrase.

    3. To save the private key in the PuTTY PPK format, click Save private key. Enter the same name as you used for the key comment so that you know which public key to use this private key with. The private key is saved in PuTTY's Private Key (PPK) format, which is a proprietary format that works only with the PuTTY toolset. You can use this key whenever you use PuTTY for SSH.

      Generate SSH key pair on Windows, save private key.

  5. Next, save your SSH public key.
    1. To save the public key, in the PuTTY Key Generator, select all of the characters in the Public key for pasting into OpenSSH authorized_keys file field.

      Generate SSH key pair on Windows, save public key.

      Note: Make sure you select all the characters, not just the ones you can see in the narrow window. If there is a scroll bar next to the characters, you aren't seeing all the characters.

    2. Right-click somewhere in the selected text and select Copy from the menu.

      Generate SSH key pair on Windows, copy public key

    3. Open a text editor and paste the characters. Ensure that you paste the text at the first character in the text editor, and don't insert any line breaks.
    4. Save the key using the same root name that you used for the private key. Add a .pub extension. You can give it any extension you want, but .pub is a useful convention to indicate that this is a public key.
    5. Exit PuTTY Key Generator.
  6. Make a note of the public and private key names and where they are saved.
    When you create instances, you must specify the SSH public key. When you log in to an instance, you must provide the path to the corresponding SSH private key.

Creating a VCN

Creating a VCN and Subnet.

Creating a Sub-Compartment

  1. Log in to OCI, navigate to Identity, and then select Compartments.

    The Compartments page appears.

    Select to change password

  2. To create a sub-compartment, do any of the following:
    • Click Create Compartment to go to Compartments page.
    • Click the root Compartment name to go to Compartment Details page. Click Create Compartment in the Child Compartments section.

    Select to change password

  3. In the Create Compartment window, fill in the following details:
    • Name: Give a logical name to the sub-compartment.
    • Description: Add description of the sub-compartment.
    • Parent Compartment: Select the parent (root) compartment for the sub-compartment.
    • Click Create Compartment.
  4. Select to change password

    The sub-compartment is created for the root compartment.

    Select to change password

Opening Ports

Open the following two ports - 4430 and 8080 within the previously created Subnet.

  1. Navigate to Menu, Networking, and then Virtual Cloud Networks.
  2. Select the VCN you previously created.
  3. Select Security Lists from Resources in the left pane.

    View VCN

  4. In the Security Lists page, click the Default Security Lists for VCN_KS1 link.

    View VCN

  5. In your Default Security List, click Edit All Rules button.

    View VCN

    The Edit Security List Rules pop up appears.

  6. To add port 4430, do the following:
    1. Scroll down to the Another Ingress Rule button and click. An Ingress Rule section is added.
    2. In Source CIDR, add 0.0.0.0/0.
    3. In Destination Port Range, add 4430.
  7. To add port 8080, repeat step 6.

    View VCN

  8. Click Save Security List Rules.

    The ports display in the security list page.

    View VCN

Requesting DBaaS DB Instance and Plugging Siebel PDB to DBaaS DB Instance

This feature is a part of Oracle DBaaS. You can create DBaaS DB from OCI, attach a Siebel PDB to DBaaS DB, and then create an OCI instance. You can deploy Siebel Docker instance using DBaaS DB and Docker DB.

For DBaaS DB, before you deploy, you must do the following:

Requesting DBaaS DB in OCI

  1. Login to OCI - https://login.us-phoenix-1.oraclecloud.com/v1/oauth2/authorize/changeTenant.
  2. Navigate to Bare Metal, VM, and Exadata.
  3. Navigate to Bare Metal, VM, and Exadata
  4. In the DB Systems in Compartment page, click Create DB System.
  5. To create a DB system, complete the following two sections:
    1. DB System Information. Enter the information in the following fields. For example,
      Field Value
      Select a Compartment siebeldev (root)
      Name your DB system Enter a name
      Select a shape type Make sure Virtual Machine is selected
      Select a shape VM.Standard2.4
      Available Storage 256
      Add public SSH keys Upload SSH Keys generated from Putty.
      Virtual Cloud Network Select a VCN in the Siebeldev root compartment
      Client Subnet Select a subnet in the VCN selected previously
      Hostname prefix siebeldbp
    2. Database Information. Click Next and enter the information in the following fields. For example,
      Field Value
      Database name ORCL
      Database version 12.1
      PDB name ORCLCDB
      Password Enter an appropriate password and confirm password.
      Available Storage 256
      Enable automatic backups Select the option (Recommended)
    3. Click Create DB Systems. The create process starts with the status of the DBS as Provisioning. When the DBS is created successfully, the status of the DBS is displayed as Running.
    4. DBS is Provisioning

Adding DBaaS DB Port in Security Ingress rule in VCN

  1. Add DBaaS DB port 1521 in Ingress rule in the Security List in VCN. Refer to the topic Opening Ports to know how to add ports.
  2. Add the following ingress rules to your VCN:
    • Ingress Rule 1
      • Source: 0.0.0.0/0
      • IP Protocol: ICMP
      • Type and Code: 3, 4
    • Ingress Rule 2
      • Source: 0.0.0.0/0
      • IP Protocol: TCP
      • Source Port Range: All
      • Destination Port Range: 1521
    • Ingress Rule 3
      • Source: 10.0.0.0/24
      • IP Protocol: TCP
      • Source Port Range: All
      • Destination Port Range: 6200
    • Ingress Rule 4
      • Source: 10.0.0.0/16
      • IP Protocol: TCP
      • Source Port Range: All
      • Destination Port Range: 6200
    • Get public IP address from Nodes section

Attaching PDB From OCIR DockerSidecar DBImage To DBaaS DB In OCI

  1. Log in to Putty and connect to the DBaaS DB Server.
  2. Choose one of the following two ways to get the PDB and attach it to DBaaS DB
    • Automated: Run the script
    • Manual: Get your own PDB and attach it to DBaaS DB instance

1. Logging in to Putty and connecting to the DBaaS DB Server.

  1. Log in to Putty using your SSH Key.
  2. In OCI, on your DBS page, scroll down to the Databases section and click Nodes and note the Public IP address. Get public IP address from Nodes section
  3. Configure the following Putty settings to connect to DBaaS DB as in the following example.
    1. Enter the following information.
      • Host Name: Enter the Public IP Address noted in step 2.
      • Connection type: SSH
      • Saved Sessions: Select the saved session.
      • Close window on exit: Only on clean exit.
      • Enter information about Host Name, Connection type, Select the saved session, Close window on exit.
    2. Scroll to SSH in the Category pane (on the left) and select the following:
      • Preferred SSH protocol version: 2 only
      • Permitted roles in the shared connection: Upstream and Downstream
      • SSH details
    3. Scroll to Auth in the Category pane (on the left) and select the following:
      • Options controlling SSH authentication: Display pre-authentication banner (SSH-2 only)
      • Authentication methods: Attempt authentication using Pageant and Attempt “keyboard interactive” auth (SSH-2)
      • Private key file for authentication: Upload the private key generated previously.
      • Auth details

2a. Automated: Run the script

  1. Ensure the DBaaS DB port 1521 is added to Ingress Rule in the Security List of VCN.
  2. Log in to DBaaS DB instance and run the following commands.
    • sudo su
    • mkdir -p /scripts;
    • cd /scripts
  3. Download the following script retrieved from the command.

    wget https://objectstorage.us-ashburn-1.oraclecloud.com/p/9uu1U6HJNsFryh0TAUi3X9naf6JQdrOM_xLuwe-9Qqs/n/siebeldev/b/siebeldev/o/SiebelDBaaSDeployPDB.sh

    Run chmod -R 755 /scripts

  4. Run the following script in background to avoid putty timeout issue.

    nohup sh /scripts/SiebelDBaaSDeployPDB.sh --siebelVer 20.7 --dbType vanilla --oracleHome /u01/app/oracle/product/12.2.0.1/dbhome_1 --dbConnectString 'sys/pasword@siebeldb12c-scan.sub03150707300.siebeldc.oraclevcn.com:1521/ORCL_iad1mt.sub03150707300.siebeldc.oraclevcn.com' >& /scripts/plugpdb.log &

    Update the following input values based on your setup. For example:

    • siebelVer 20.7
    • dbType [accepted values vanilla or sample ]
    • oracleHome /u01/app/oracle/product/12.2.0.1/dbhome_1 (This is the default value of DBaaS)
    • dbConnectString 'sys/pasword@siebeldb12c-scan.sub03150707300.siebeldc.oraclevcn.com:1521/ORCL_iad1mt.sub03150707300.siebeldc.oraclevcn.com'(Update your connect string to DB)

  5. Use the following commend to monitor the Log during execution of script.

    tail -f /scripts/plugpdb.log

    If putty session times out when your script is running, log in again via putty and rerun the script.

  6. On completion, verify your PDB is created by running the following commands in SQLPLUS:
    • [oracle@siebeldb12c opc]$ sudo su
    • [oracle@siebeldb12c opc]$ sqlplus / as sysdba
    • SQL > show pdbs

    If your PDB shows restricted access NO, it was created correctly. Note down your Service Name displayed in the and DBaaS DB Long connect string. For more information, refer to Get orclNetDescString information from DBaaS in OCI.

    Once you have both values, that is the Service Name and the DBaaS DB Long connect string, you need to replace Service Name value in the DBaaS DB Long connect string that will be used with the SiebelDeploywithDBaaS option in Jenkins when deploying Siebel instance.

    You can now deploy your VM from Marketplace and attach to your PDB in DBaaS.

Verifying log

Verify the following values at the end of the log.

Log on script execution

2b. Manual: Getting your own PDB and attaching it to DBaaS DB instance

  1. Log in to Putty using user "opc".
  2. In SQLPLUS, run the following commands.
    • [oracle@siebeldb12c opc]$ sudo su
    • [oracle@siebeldb12c opc]$ su oracle
    • [oracle@siebeldb12c opc]$. /home/oracle/.bashrc
    • [oracle@siebeldb12c opc]$ sqlplus / as sysdba
    • SQLPLUS commands
    • Run the command - showpdbs
    • SQLPLUS commands

      You will get the PDB list in the DB server.

  3. Exit SQLPLUS.
  4. Upload your PDB that is compressed to *.tar.gz to OCI Object storage.
  5. Download PDB from OCI object storage using the following steps:
    1. Run the following commands to login as Oracle user and source the .bashrc file.
      • [oracle@siebeldb12c opc]$ sudo su
      • [oracle@siebeldb12c opc]$ su oracle
      • [oracle@siebeldb12c opc]$. /home/oracle/.bashrc
    2. Run the following commands in SQLPLUS.
      • [oracle@siebeldb12c opc]$ cd/u01/app/oracle/oradata/ORCLCDB
      • Then run the PDB link you received. For example, wget https://objectstorage.us-ashburn-1.oraclecloud.com/p/bbGkRMZe2AQ3Vg1QcNBdG-HDaPvK78pFUqP5sKkA7h0/n/siebeldev/b/siebeldev/o/SAMPLE_18.8_DBSAMPLE.tar.gz
      • [oracle@siebeldb12c opc]$ sqlplus / as sysdba
      • SQLPLUS commands
    3. On file download, unzip the file using tar utility - [oracle@siebeldb12c opc]$ tar -zxvf SAMPLE_18.8_DBSAMPLE.tar.gzSQLPLUS commands
    4. Run the following commands in SQLPLUS.
      • [oracle@siebeldb12c opc]$ sudo su
      • [oracle@siebeldb12c opc]$ su oracle
      • [oracle@siebeldb12c opc]$. /home/oracle/.bashrc
      • [oracle@siebeldb12c opc]$ mkdir -p /u02/app/oracle/oradata/ORCLCDB
      • [oracle@siebeldb12c opc]$ chown -R oracle:oinstall /u02
      • [oracle@siebeldb12c opc]$ cd /u02/app/oracle/oradata/ORCLCDB
      • [oracle@siebeldb12c opc]$ ln -s /u01/app/oracle/oradata/ORCLCDB/SAMPLE SAMPLE
      • [oracle@siebeldb12c opc]$ ls -la
      • [oracle@siebeldb12c opc]$ sqlplus / as sysdba
      SQLPLUS commands SQLPLUS commands
    5. Run the following commands to create a PDB in SQLPLUS.
      • SQL > create pluggable database SAMPLE using '/u01/app/oracle/oradata/ORCLCDB/SAMPLE/pdb_SAMPLE.xml' nocopy tempfile reuse ;
      • SQL > alter pluggable database SAMPLE open read write;
      • SQL > alter pluggable database SAMPLE open read write;
      • SQL > commit;
      • SQL > show pdbs
      SQLPLUS commands

      Note the PDB Restricted status. If it is NO, you need not do anything.

      If it is YES, run the following command sets in SQLPLUS till the status returns NO.

      Command set 1 to update SQL patch:

      • [oracle@siebeldb12c opc]$ su oracle
      • [oracle@siebeldb12c opc]$ su oracle
      • [oracle@siebeldb12c opc]$ su oracle
        • [oracle@siebeldb12c opc]$ su oracle
        • SQL > exit;
      • [oracle@siebeldb12c opc]$ cd $ORACLE_HOME/OPatch
      • [oracle@siebeldb12c opc]$
      • ./datapatch -verbose

      Command set 2 to create PDB:

      • [oracle@siebeldb12c opc]$ sqlplus / as sysdba
        • SQL > alter pluggable database "SAMPLE" close IMMEDIATE ;
        • SQL > alter pluggable database "SAMPLE" unplug into '/u01/app/oracle/oradata/ORCLCDB/SAMPLE/pdb_SAMPLE.xml';
        • SQL > DROP PLUGGABLE DATABASE "SAMPLE" KEEP DATAFILES;
        • SQL > commit;
        • SQL > create pluggable database SAMPLE using '/u01/app/oracle/oradata/ORCLCDB/SAMPLE/pdb_SAMPLE.xml' nocopy tempfile reuse ;
        • SQL > alter pluggable database SAMPLE open read write;
        • SQL > alter pluggable database SAMPLE save state;
        • SQL > show pdbs

        Now the PDB should show Restricted Mode = NO.

Getting orclNetDescString information from DBaaS in OCI

  1. Navigate to Bare Metal, VM and Exadata and select the Database system to go to the DB System details page. Navigate to Bare Metal
  2. Scroll down to the Databases section and click on ORCL database. The ORCL database details page appears. Scroll to Databases section
  3. Click on DB Connection. The Database Connection window opens. DB Connection tab
  4. Copy and save the long format of the connection string from DBaaS OCI. Copy and save the long format connection string

    In the connection string, replace the service name ORCL value with the service name of the attached PDB.

    For example, (DESCRIPTION=(CONNECT_TIMEOUT=5)(TRANSPORT_CONNECT_TIMEOUT=3)(RETRY_COUNT=3)(ADDRESS_LIST=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=10.0.0.136)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=10.0.0.137)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=10.0.0.138)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=sample.sub03150707300.siebeldc.oraclevcn.com)))

Launching Instance of Siebel from Marketplace

  1. Log in to Oracle Cloud Infrastructure.
  2. Navigate to Oracle Cloud Infrastructure Marketplace.
  3. Navigate to Marketplace
  4. Click on Siebel CRM install Jenkins/Docker Instance image.
  5. Go to Jenkins/Docker Instance
  6. In the instance page, click Launch Instance.
  7. Click Launch Instance button

  8. In the Launch Instance screen that appears, do the following:
    • Select Compartment. For example, siebelDev
    • Agree to the Terms of Use.
    • Click Launch Instance.

    Click Launch Instance button

  9. In the Create Compute Instance screen that appears, do the following:
    • Name your Instance – Give a logical name to your instance.
    • Select a domain.

    Create Instance button

  10. Go to Add SSH key section and select one of the following:
    • Choose SSH key file – select and upload the SSH key file.
    • Paste SSH keys – select this and paste the SSH key in the given space.

    Paste SSH key

  11. In the Configure Networking section, select the VCN you created previously. Leave the other default selections.

    Define the Compute Instance

  12. Click Create. The create process starts with the status of the instance as Provisioning.

    Compute Instance is Provisioning

    Then, when the instance is created successfully, the status of the instance is displayed as Running.

    Compute Instance is running.

Deploying the Siebel Application

After you have created the instance, you have to generate two URLs:

  1. Jenkins URL: To deploy Siebel application.
  2. Application domain URL: To create Siebel industry specific application.

Generating Jenkins URL

  1. Copy the Public IP Address from your previously created Instance.
  2. Copy IP Public Address

  3. Add the port 8080 preceded with a colon and paste the URL in a browser window to open the Jenkins application.

    <public IP address>:<port number>

    For example: 129.146.133.76:8080

  4. Log in to the Jenkins application.

    Note: Jenkins is a public domain. It is recommended to change the password. For more information, see here.

Deploying the Siebel CRM Application

You can deploy the Siebel CRM application instance using the DBaaS DB And Docker DB, based on the DB you selected for deployment in Jenkins pipeline.

Deploying Siebel Docker Instance with Docker DB

  1. Log in to Jenkins using the Public IP Address you got on creating DBS. The Pipelines screen opens.
  2. Click on SiebelDeploy.

    Select SiebelDeploy

  3. In the Pipeline SiebelDeploy screen, click on Open Blue Ocean.

    click on Open Blue Ocean

  4. In the deployment screen, click on Run.

    Run the deployment

  5. In the Input required dialog box, enter the required input.

    Choose the DB - Sample/Vanilla and click Run.

    Complete the input box

    The deployment process starts.

    deployment starts

    This is another view of deployment process.

    deployment continues

    When the deployment is successfully completed, the screen displays as following.

    deployment successful

    Click on Logs to view build details.

    view logs

Deploying Siebel Docker Instance using OpenLDAP with DBaaS DB

  1. After you login to Jenkins, the Pipelines screen opens. Click on SiebelDeployWithDBaaS.

    Select SiebelDeployWithDBaaS

  2. In the Pipeline SiebelDeploy screen, click on Open Blue Ocean.

    click on Open Blue Ocean

  3. In the deployment screen, click on Run.

    Run the deployment

  4. In the Input required dialog box, enter the required input.

    Paste the DBaaS DB connect string you previously generated and click Run.

    Complete the input box

    The deployment process starts.

    deployment starts

    When the deployment is successfully completed, the screen displays as following.

    deployment successful

    Click on Logs to view build details.

    view logs

Generating application domain URL

Create the application URL using the port 4430, that you opened previously, and the industry you selected while deployment.

http:// <public IP address>:<port number>/siebel/app/<industry>/enu

For example, if you selected Automotive, your application URL for Automotive industry will be the following.

https://129.146.170.80:4430/siebel/app/eautomotive/enu

The application URL will be specific to the Industry you select while deployment, for example, the URL will be:

  • For Service - https:// <public IP address>:4430/siebel/app/callcenter/enu
  • For Siebel Management Console (SMC) - https:// <public IP address>:4430/siebel/smc

Changing the SADMIN Password

  1. In Jenkins application, navigate to siebel toolbar and select Configure.

    Select to change password

  2. Drill down to Password section, change the password, and then click Save.

    Select to change password

Upgrading Siebel Docker Images to the latest version

This supports upgrading the Siebel container CGW, SES, SAI to a higher version including the restart of Siebel services like Gateway, Zookeeper, Siebel Server, and Tomcat.

The database is not upgraded here.

Use the following two jobs for upgrade based on your database.

  • Siebel Version Upgrade for DBaaS DB: DBaaS_SiebelVersionUpgrade
  • Siebel Version Upgrade for Docker DB: SiebelVersionUpgrade

Siebel Version Upgrade for DBaaS DB: DBaaS_SiebelVersionUpgrade

  1. Log in to Jenkins using the Public IP Address you got on creating DBS. Select to change password
  2. Click on the DBaaS_SiebelVersionUpgrade pipeline.
  3. Click on Open Blue Ocean to open the pipeline deployment page.
  4. Click Run to open the Input required window.
    • Enter the appropriate inputs.
    • Select the current and upgrade Siebel versions
    • Paste the DBaaS DB Connect String you previously generated.
    • Click Run
    • DBaaS DB version upgrade

      The upgrade starts. On successful upgrade, the status displays green.

Siebel Version Upgrade for Docker DB: SiebelVersionUpgrade

  1. Log in to Jenkins using the Public IP Address you got on creating DBS. Select to change password
  2. Click on the SiebelVersionUpgrade pipeline.
  3. Click on Open Blue Ocean to open the pipeline deployment page.
  4. Click Run to open the Input required window.
    • Enter the appropriate inputs.
    • Select the current and upgrade Siebel versions
    • Select the current Docker DB.
    • Click Run
    • Docker DB version upgrade

      The upgrade starts. On successful upgrade, the status displays green.

Restarting Siebel Services in DBaaS or Docker DB Type of Deployment

This supports restart of the Siebel container CGW, SES, SAI deployed on the machine along with restart of Siebel services like Gateway, Zookeeper, Siebel Server, and Tomcat.

Use the following to restart services based on your database.

  • Restart of Siebel Services in DBaaS DB type of deployment: DBaaS_ SiebelBounceService
  • Restart of Siebel Services in Docker DB type of deployment: SiebelBounceService and SiebelBounceServiceWithDB

Restart of Siebel Services in DBaaS DB type of deployment

  1. Log in to Jenkins using the Public IP Address you got on creating DBS. Select to change password
  2. Click on the DBaaS_ SiebelBounceService pipeline.
  3. Click on Open Blue Ocean to open the pipeline deployment page.
  4. Click Run to open the Input required window.
    • Enter the appropriate inputs.
    • Paste the DBaaS DB Connect String you previously generated.
    • Click Run
    • DBaaS DB restart

      The services restart. On successful restart, the status displays green.

Restart of Siebel Services in Docker DB type of deployment

  1. Log in to Jenkins using the Public IP Address you got on creating DBS. Select to change password
  2. Click on the SiebelBounceService or SiebelBounceServiceWithDB pipeline.
  3. Click on Open Blue Ocean to open the pipeline deployment page.
  4. Click Run to open the Input required window.
    • Enter the appropriate inputs.
    • Select the current Docker DB.
    • Click Run
    • Docker DB version upgrade

      The services restart. On successful restart, the status displays green.

Logging In to the Siebel Application

After the Siebel CRM Install Jenkins/Docker Instance configuration has completed, you can log in to the Siebel environment details page in a browser using the public IP address that you reserved earlier. See Generating application domain URL. This page contains list of Siebel applications and users.

Activating the Web Tools on a Siebel Environment

The following steps describe how to activate the Web Tools on Siebel Environment.

  1. Log in to the Oracle Enterprise Linux (OEL) instance on OCI using the public IP address or SSH key using the private IP address.

    Use the following credentials:

    • Username: opc
    • Password: The SSH key generated from Putty

  2. Get the list of Docker containers running on this instance by entering the following command,
    • sudo su: This command switches to the root user.
    • docker ps –a: This command initiates the list.

    The Docker containers running on this instance are listed.

    Get the list of Docker containers running on this instance

  3. Select the required Docker container name as displayed in the Names column in the list generated in step 2 to log in.

    Use the following command to log in to the container.

    docker exec –it –u siebel <containername> bash

    Get the list of Docker containers running on this instance

  4. Enable the Web tools on Siebel environment using any one of the following:
    • Command line
    • SMC

    To enable using command line:

    1. Log in to SES Docker container.
    2. Run smgr command. This is an alias to connect to srvrmgr.
    3. Enable the compgroups. Do the following in the smgr console,
      1. Run the list server command to list the server names.
      2. Run the set server <server name> command.
      3. Run the enable compgroup siebelwebtools command.
      4. Exit the smgr console.

    To enable using SMC:

    1. Navigate to Administration - Server Configuration, then Enterprises – Component Groups.
    2. In the Enterprise Component Groups section, select Name, enter the name Siebel Web, and then click the Arrow button to search.
    3. In Components Group Assignments, click the Enable button.
    4. Restart the Siebel server using command line.

  5. Restart the following Siebel services using the corresponding commands on the Docker container.
    • Tomcat Restart (On SES, SAI, and CGW containers)
      • stop_http
      • start_http
    • Siebel Server restart (Only on SES container)
      • stop_server all
      • start_server all
    • Zookeeper, Gateway restart (Only on CGW container)
      • stop_ns
      • start_ns

    For example, to restart only Siebel server,

    1. Stop tomcat on SAI, SES, and CGW containers.
    2. Stop Siebel server on SES container.
    3. Start tomcat on SAI, SES, and CGW containers.
    4. Start Siebel server.

    For example, to restart Siebel Server with complete deployment after enabling components,

    1. Stop tomcat on SAI, SES, and CGW containers.
    2. Stop Siebel server on SES container.
    3. Stop Gateway and Zookeeper on CGW container.
    4. Start Tomcat on SAI, SES, and CGW containers.
    5. Start Gateway and Zookeeper on CGW container.
    6. Start Siebel server on SES container.

  6. (Optional) Get the container details such as, network, persistence storage detail, IP address, and so on, using the following command,

    docker inspect <containername>

Want to Learn More?

  • Search for Siebel Bookshelf in My Oracle Support