How Incremental Changes Are Processed

Note the following considerations relevant to how incremental changes are processed. This topic is part of Making Incremental Changes to Your Siebel CRM Deployment on OCI.

• For each upgrade or flux reconcile that you perform, configure job runs, which validate the application configuration. These runs typically take about 2 minutes.

• The Siebel Controller picks up the runtime incremental changes as soon as the above configure job is completed.

• A continuous synchronization operation identifies the changes in configmaps and does the required actions. It might take up to 10 minutes for synchronization to identify the changes.

• In some cases, server restart is required, which is handled by the controller. Whenever a server restart happens, wait at least 5 minutes before you run the next incremental changes, so that the server state will be good.

• YAML files function as configuration files, which are both case-sensitive and indentation-sensitive. YAML uses spaces ( ) to define document structure. YAML does not allow tabs (\t).

• As illustrated in Step 10 of the procedure in Making Incremental Changes, replace <namespace> with your namespace. Also replace <env_id> with your environment ID.

  Note: Do not replace <enterprise_name> and <server_name> in the URLs, because these are substituted programmatically.

• To reduce errors in the code flow, use the YAML validator before adding a block to these files representing incremental configuration changes.

• The configuration files server_edge.yaml and sai_quantum.yaml are Siebel Server (sieb_server) and Siebel Application Interface (SAI) profile configuration (ai_profile) files, respectively. The names edge and quantum are assigned automatically.

  • Any file with the prefix server_ refers to a Siebel Server (sieb_server). For example, in the filename server_edge.yaml, edge is a sieb_server name. Any changes you make in this file apply to all replicas of the server edge.

    Note: You can create other YAML configuration files to configure other Siebel Server instances that are not replicas of edge, as described in Use Cases for Adding Profiles, Deployments, or Adding Resources to Individual Siebel Servers.

  • Any file with the prefix sai_ refers to a SAI profile configuration (ai_profile). For example, in the filename sai_quantum.yaml, quantum is an ai_profile name. Any changes you make in this file apply to all replicas of the ai_profile quantum.

    Note: You can create other YAML configuration files to configure any other SAI instances that are not replicas of quantum, as described in Use Cases for Adding Profiles, Deployments, or Adding Resources to Individual Siebel Servers.
  Note: In this section, the files siebel_edge.yaml and sai_quantum.yaml are used as example configuration files for Siebel Server and SAI. In your Siebel CRM deployment environment, other files might apply instead of or in addition to these files.

• Other YAML files in which you can make configuration changes include enterprise.yaml, comp_definitions.yaml, named_subsystem.yaml, siebel-ingress-app.yaml, and siebel.yaml.