Tools for Deploying Siebel CRM using SCM

SCM and the Siebel Lift utility include various third-party products and custom operators that play a role in pipeline operations. These products include the following:

• Flux (Flux Operator): Flux (A CNCF Graduated project pioneered by Weaveworks) is a continuous deployment tool that synchronizes the Git repository and Kubernetes clusters. SCM uses Flux to automate Siebel CRM deployment in GitOps way. It ensures that Siebel CRM environment deployment in the cluster matches with the configuration defined in the Git repository. If any differences found in the Git repository, Flux syncs up and updates the deployment.
• Helm: Helm charts is used for deploying Siebel CRM and supporting deployments.
• kubectl: kubectl is used for interacting with the Kubernetes cluster and performing administration tasks such as opening a session in a Kubernetes pod for running commands and so on.
• Config Operator: Config Operator does the Siebel CRM Configuration through Siebel Management Console (SMC) REST APIs. This operator is initiated by a Kubernetes job managed by Helm. This job will get triggered when:
  • 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 has the profile definition of the Siebel CRM infrastructure and fed to the config operator to perform Siebel CRM Configuration.

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

• Siebel Operator (An Incremental Operator): Siebel Operator is a metacontroller based custom controller that performs incremental changes in an existing Siebel CRM deployment created using SCM. Siebel Operator 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.
  • Siebel operator works based on monitoring the paramconfig config maps, detects the incremental changes, deploys the runtime additions at each level (Enterprise, Siebel CRM Server and Component level) of Siebel CRM deployment and restarts the Siebel CRM server when required. The Siebel operator detects the changes and syncs the config maps when the following incremental changes are added 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 an integral part of SCM, providing a robust and efficient artifact repository solution. It serves as a centralized repository that:
  • Stores and manages all the essential Siebel CRM deployment artifacts.
  • Ensures reliable and secure access to the files required across various deployment scenarios.

  The Artifactory server plays an important role in the deployment process:

  • In a greenfield or fresh Siebel CRM deployment, the Artifactory server acts as a source for the deployment artifacts. It provides easy access to the deployment files, ensuring a smooth and efficient deployment process from scratch.
  • For lift-and-shift scenarios, the Artifactory server facilitates the migration of existing Siebel CRM artifacts. These artifacts are extracted from an existing Siebel CRM environment by running the Siebel Lift utility and can optionally be stored on an NFS path. The Artifactory server then mounts this NFS location, making the files accessible for deployment.