Siebel Cloud Manager Replacing .js Or .so Files With Code Changes Siebel Server LIB Directory Does Not Persist After Oracle Kubernetes Engine (OKE) Node Restart (Doc ID 2915774.1)

Last updated on DECEMBER 20, 2022

Applies to:

Symptoms

When attempting to replace any file (specifically .so or .js files) with new code changes under the LIB directory of Siebel server does not persist after the Siebel Enterprise Server (SES) is restarted

The issue can be reproduced using below steps:

1. Setup Siebel cloud manager and perform lift and shift from on-prem to OCI to move the files
2. For updating any .so or .js files and pushing code changes, modify the actual library files directly on the OCI deployed Siebel server by connecting to the kubernetes node on cloud manager instance with below commands:

3. Once the edge-0 Siebel server pod is connected, replace the existing .so or .js script with a modified .so or .js script under /siebel/mde/siebsrvr/bin directory in the pod

4. Restart the Oracle Kubernetes Engine (OKE) pod manually and then check to see if the changed file persists upon restart.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.