Making Incremental Changes

Use the procedure below to make incremental changes to your Siebel CRM deployment. This topic is part of Making Incremental Changes to Your Siebel CRM Deployment on OCI.

Note: Before making any updates, review all of the topics in this section.

To make incremental changes

Execute the following commands:

docker ps

docker exec -it cloudmanager bash

Execute the following command:

source /home/opc/siebel/<env_id>/k8sprofile

Execute the following command:
```
cd /home/opc/siebel/<env_id>/<namespace>-helmcharts/siebel-config/paramconfig
```
Note: All configuration and runtime data for a deployed environment is located in /home/opc/siebel/<env_id>/<namespace>-helmcharts/siebel-config/paramconfig.
Edit the required YAML file with the incremental changes you require (for example, run vi enterprise.yaml).

For details, see How Incremental Changes Are Processed and all the remaining topics in this section.

Note: Back up all YAML files before you modify them, to help you back out your changes if you experience errors.
Edit the file /home/opc/siebel/<env_id>/<namespace>-helmcharts/siebel-config/Chart.yaml. Increment the value of version (for example, increment 0.1.0 to 0.1.1).
Execute commands like the following to specify the files that are part of the update you are making and to push these changes to the deployment:
```
cd /home/opc/siebel/<env_id>/<namespace>-helmcharts/siebel-config
```
```
git status
```
```
git add <modifiedfile1> <modifiedfile2>
```
```
git commit -m "<message or comment>"
```
```
git push
```
Flux automatically upgrades the siebel-config helmchart. The automatic flux reconcile might take a few minutes.

If needed, load flux reconcile manually using the following commands:

flux reconcile source git siebel-repo -n <namespace>

flux reconcile kustomization apps -n <namespace>

Verify the new version of siebel-config using the following command:
```
flux get all -n <namespace>
```
Incremental changes, including modified files, are pushed to configmaps, and siebel-controller will automatically pick up changes and execute the required actions.
To verify the incremental changes after performing the previous steps, wait at least 5 minutes. Then you can verify your changes from the Siebel Management Console (SMC) or by using server manager.

If the changes are not reflected even after about 10 minutes, to review and analyze logs, first get the name of the siebel-controller pod using the following command:
```
kubectl get pods -n <namespace>
```
In this command, <namespace> is the relevant namespace for your deployment. Then, to see the logs, enter a command like the following:
```
kubectl logs -n <namespace> siebel-controller-<pod_id> -f
```
In this command, <pod_id> is the pod ID for which you want to view logs. To view only the latest logs, you can optionally use --tail=0 at the end of this command.