Tools for Deploying Siebel CRM using SCM

SCM and the Siebel Lift utility use several third-party products and custom operators to support deployment pipeline operations. These products include the following:

• Flux (Flux Operator): Flux is a continuous deployment tool and a CNCF Graduated project pioneered by Weaveworks. SCM uses Flux to synchronize the Git repository with the Kubernetes cluster and automate Siebel CRM deployment by using a GitOps approach. Flux helps ensure that the Siebel CRM deployment in the cluster matches the configuration defined in the Git repository. When Flux detects changes in the Git repository, it synchronizes the changes with the deployment.
• Helm: SCM uses Helm charts to deploy Siebel CRM and its supporting components.
• kubectl: You can use kubectl to interact with the Kubernetes cluster and perform administration tasks. For example, you can use kubectl to open a session in a Kubernetes pod and run commands.
• Config Operator: The Config Operator performs Siebel CRM configuration through Siebel Management Console (SMC) REST APIs. A Kubernetes job managed by Helm initiates this operator. This job is triggered when:
  • A successful Siebel CRM database connection is established.
  • SMC is running.

  The Helm Git repository contains the Siebel CRM configuration and deployment definition YAMLs. The paramconfigdirectory in the Helm Git repository contains the profile definition of the Siebel CRM infrastructure. The Config Operator uses this profile definition to perform Siebel CRM configuration.

  For more information on Git repositories, see Git Repositories for Siebel CRM Deployment.

• Siebel Operator (An Incremental Operator): The Siebel Operator is a Metacontroller based custom controller that performs incremental changes in an existing Siebel CRM deployment created using SCM. It facilitates GitOps to create a powerful, automated, and declarative approach to managing the Siebel CRM resources. For each upgrade or Flux reconcile that's performed, configure job runs to validate the application configuration.

  The Siebel Operator monitors the paramconfig ConfigMaps, detects incremental changes, deploys runtime additions at the Enterprise, Siebel CRM Server, and component levels, and restarts the Siebel CRM Server when required. The Siebel Operator detects and synchronizes ConfigMap changes when you add the following incremental changes in paramconfig:

  • Enable a component group
  • Enable / disable a component
  • Enterprise parameter changes
  • Server parameter changes
  • Component parameter changes
  • Adding new named subsystem
  • Adding a new component definition
  • Adding new components to the server
  • Adding AI parameters
  • Adding a new Siebel server or AI
  • Changing log level
• Artifactory server: The Artifactory server is part of SCM and provides an artifact repository for Siebel CRM deployment artifacts. It stores and manages deployment artifacts and provides access to the files required for different deployment scenarios. It plays an important role in the deployment process:
  • In a greenfield or fresh Siebel CRM deployment, the Artifactory server acts as the source for deployment artifacts.
  • In lift-and-shift scenarios, the Artifactory server helps migrate existing Siebel CRM artifacts. The Siebel Lift utility extracts these artifacts from an existing Siebel CRM environment. You can optionally store the artifacts on an NFS path, and the Artifactory server mounts that NFS location to make the files available for deployment.