1. Deploying Siebel CRM Containers on Kubernetes using Siebel Cloud Manager
  2. 8. Verifying the Open Integration Deployment Status

8. Verifying the Open Integration Deployment Status

You can now verify the status of the Open Integration application. This allows you to monitor the progress of the deployment, verify that it is fully deployed, and diagnose any issues that may occur during the deployment process. You can query the deployment status using the /openintegration API with the deployment ID as the parameter:

  • Method: GET
  • Endpoint: /openintegration/<deploy_id>
  • Description: Helps you to retrieve the status of the Open Integration deployment.
  • Sample API call request:
    GET https://<SCM_instance_IP>:<port_num>/scm/api/v1.0/openintegration/<deploy_id> 
Authorization: Basic Auth

    In the example above, <deploy_id> is the unique ID that was generated when the Open Integration deployment was initiated.

  • Sample API call response:
    {
   "data": {
      "ansible_chart_name": "ansible-test6-ntntd1",
      "app_dir": "/home/opc/siebel/microservices/siebel_openint/NTNTD1",
      "coherence": {
         "coherence_cluster_name": "siebelcache",
         "namespace": "openint2",
         "use_existing": false
      },
      "deploy_id": "NTNTD1",
      "deploy_status": "completed",
      "infra_id": "GXWODN",
      "name": "test6",
      "namespace": "openint2",
      "openintegration": {
         "git": {
            "git_id": "FSDCDF",
            "git_openint_branch": "main",
            "git_openint_directory": "siebel_openint"
         },
         "siebel_server_keystore_file_path": "/home/opc/siebel/siebelkeystore.jks",
         "siebel_client_keystore_file_path": "/home/opc/siebel/siebelkeystore_client.jks",
         "siebel_truststore_file_path": "/home/opc/siebel/siebeltruststore.jks",
         "siebel_server_keystore_password": "server",
         "siebel_truststore_password": "siebel",
         "siebel_client_keystore_password": "client"
      },
      "product_name": "siebel_openint",
      "self_link": "https://<SCM_instance_IP>:<port_num>/scm/api/v1.0/openintegration/NTNTD1",
      "stages": [
      {
         "end_time": "Wed, 21 May 2025 12:17:39 +0000",
         "log_api_link": "https://<SCM_instance_IP>:<port_num>/scm/api/v1.0/openintegration/NTNTD1/logs/prepare_gitops",
         "log_location": "/home/opc/siebel/microservices/siebel_openint/NTNTD1/logs/prepare_gitops.log",
         "name": "Prepare GitOps",
         "previous_status": "",
         "stage_description": "Generate Flux definitions, Prepare helmchart to git and Prepare GitOps",
         "stage_name": "prepare_gitops",
         "start_time": "Wed, 21 May 2025 12:17:14 +0000",
         "status": "passed"
      },
      {
         "end_time": "Wed, 21 May 2025 12:18:47 +0000",
         "log_api_link": "https://<SCM_instance_IP>:<port_num>/scm/api/v1.0/openintegration/NTNTD1/logs/pre_deploy",
         "log_location": "/home/opc/siebel/microservices/siebel_openint/NTNTD1/logs/pre_deploy.log",
         "name": "Pre Deploy",
         "previous_status": "",
         "stage_description": "Create pre requisites and other preparations",
         "stage_name": "pre_deploy",
         "start_time": "Wed, 21 May 2025 12:17:40 +0000",
         "status": "passed"
      },
      {
         "end_time": "Wed, 21 May 2025 12:19:02 +0000",
         "log_api_link": "https://<SCM_instance_IP>:<port_num>/scm/api/v1.0/openintegration/NTNTD1/logs/flux_setup",
         "log_location": "/home/opc/siebel/microservices/siebel_openint/NTNTD1/logs/flux_setup.log",
         "name": "Flux Setup",
         "previous_status": "",
         "stage_description": "Do flux Setup and Perform flux bootstrap",
         "stage_name": "flux_setup",
         "start_time": "Wed, 21 May 2025 12:18:48 +0000",
         "status": "passed"
      },
      {
         "end_time": "",
         "log_api_link": "https://<SCM_instance_IP>:<port_num>/scm/api/v1.0/openintegration/NTNTD1/logs/verify_deployment",
         "log_location": "/home/opc/siebel/microservices/siebel_openint/NTNTD1/logs/verify_deployment.log",
         "name": "Verify Deployment",
         "previous_status": "",
         "stage_description": "Verify HR Deployment",
         "stage_name": "verify_deployment",
         "start_time": "Wed, 21 May 2025 12:22:03 +0000",
         "status": "passed"
      }
   ]
   },
   "message": "success",
   "status": "success"
}

Runtime Configuration Checks

Use the following checks to verify the Open Integration runtime configuration:

  • The application sets OI_LOG_LEVEL and DLQ_LOG_LEVEL to ERROR by default.
  • The runtime log directory, /openintv2Installer/openint-deploy/target/logs, is writable and ephemeral. Log4j can create siebel-openint.log in this directory. The log contents are removed when the pod is recreated.
  • SCM writes Openint.cache.enabled and Openint.cache.tlsEnabled in the customer profile.json file as JSON boolean values.
  • The Coherence configuration includes OpenIntRest_* and oi-distributed-rest-sessions for REST-session caching. Before you use this feature, make sure the deployed Coherence runtime includes the required Open Integration cache classes.