Updating the database configuration of an existing Engineering Lifecycle Management instance by using Red Hat OpenShift CLI

When your database server is moved to a different host or when database credentials are updated, you must update the database configuration of the Engineering Lifecycle Management instance. You can do it using the Red Hat® OpenShift® CLI method.

Before you begin

Ensure that the existing Engineering Lifecycle Management setup is functional without any errors and all Engineering Lifecycle Management applications are accessible.
Back up the old database.
Note: To stop the Engineering Lifecycle Management applications before database backup, you can use the ELMOperation CR. For more information, see Stopping and starting Engineering Lifecycle Management application pods by using ELM Operation instance.
Use the database vendor-specific tools to migrate the data from the old database to the new database.

Important: For IBM® Db2® or for z/OS®, follow the unload and load instructions in Running UNLOAD and LOAD processes on Db2 to create a backup database.
Ensure that the new database configuration inputs are available to you.
Note: The new database server must be of the same vendor type.
Consider the downtime of Engineering Lifecycle Management applications and plan the activity.
Log in using the appropriate user role that has the privilege to update the database configuration. For more information about the roles that are used in the Red Hat OpenShift, see User roles mapping in Engineering Lifecycle Management on Hybrid Cloud.

Procedure

Update the database details in the Engineering Lifecycle Management instance. If you are using multiple database servers, update the details of the specific databases that were changed. For more information, see Configuring separate database instances for the Engineering Lifecycle Management instance.

Fetch the ELM YAML file and save it to your local system.

oc get elm -n <namespace_name>
oc get elm/<elm_instance_name> -n <namespace_name> -o yaml > ELM-CR.yaml

Update the details of the new database server in the YAML file. See Example of ELM instance YAML file.
```
database: 
  dbHostname: <value>
  dbPort: <value>
  dbType: <value>
  dbUserName: <value>
```

Apply the changes to the deployment in the cluster.

oc apply --from-file=<your-directory-path>/ELM-CR.yaml

Update the existing elm-auth-secret secret for the Engineering Lifecycle Management instance. Follow the steps:
1. Fetch the elm-auth-secret
```
oc get secret elm-auth-secret -n  <namespace> -o yaml > elm-auth-secret.yaml
```
2. Modify the secret in the yaml file and update it in the cluster
```
oc apply –from-file=<your-directory-path>/elm-auth-secret.yaml
```
Stop and start the application pods that are having database configuration changes by using the ELMOperation instance. For more information, see Stopping and starting Engineering Lifecycle Management application pods by using ELM Operation instance. Alternatively, you can delete the application pods.
```
oc delete pod <pod-name> -n <namespace> 
oc delete pods  -l app.kubernetes.io/instance=ELM  -n <namespace>
```
Verify the status of the Engineering Lifecycle Management application. View the applications status section by using command
```
oc describe elm/<elm_instance_name> -n <namespace_name>
```
Verify access to the Engineering Lifecycle Management application by using the updated database configuration. Get the route of applications by using the following command
```
oc get routes -n <namespace> echo "$(oc get route <route-name> -n my-namespace -o jsonpath='{.spec.host}{.spec.path}')"
```
View the particular URL in the browser and log in to the JAS application by using your user ID and password. The Engineering Lifecycle Management application opens.