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

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.

Note: The key should be created without a passphrase.

3. 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.
4. 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.

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.

   

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

   

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

   

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.

   Note: The key should be created without a passphrase.

   2. 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.

      

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.

      

      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.

      

   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.

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

   The Compartments page appears.

   

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.

   

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.



The sub-compartment is created for the root compartment.

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.

   

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

   

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

   

   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.

   

8. Click Save Security List Rules.

   The ports display in the security list page.

   

1. Login to OCI - https://login.us-phoenix-1.oraclecloud.com/v1/oauth2/authorize/changeTenant.
2. Navigate to Bare Metal, VM, and Exadata.

3. In the DB Systems in Compartment page, click Create DB System.
4. 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.
   

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
   

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.
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.
      
   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
      
   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.
      

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.

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
   
   • Run the command - showpdbs
   

   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
      
   3. On file download, unzip the file using tar utility - [oracle@siebeldb12c opc]$ tar -zxvf SAMPLE_18.8_DBSAMPLE.tar.gz
   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
      
   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
      

      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.

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

   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)))

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



2. 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

3. Log in to the Jenkins application.

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

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.

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

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

   

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

   

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

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.
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
   

   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.
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
   

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