Customizing a Decision Center time zone

You might need to change the default JVM setting for the time zone in Decision Center as it is set to Central European Time (CET). By changing a JVM argument to a different time zone, you can change the dates and calendars you see in the user interface.

Before you begin

To be able to customize the JVM arguments, you must first create an ODM production release. It is not possible to customize the JVM at installation time.

About this task

When you install an ODM release the following configmap files are created, which define the default Liberty server JVM arguments for each ODM component.

Table 1. Naming convention for configmap files
Component	Name of configmap
Decision Center	`<release_name>`-odm-dc-jvm-options-configmap
Decision Runner	`<release_name>`-odm-dr-jvm-options-configmap
Decision Server Console	`<release_name>`-odm-ds-console-jvm-options-configmap
Decision Server Runtime	`<release_name>`-odm-ds-runtime-jvm-options-configmap

Where <release_name> is the name you gave to the release when you configured it.

By default, the only JVM argument in the Decision Center configmap file is the time zone.

-Duser.timezone=Europe/Paris

Procedure

To change the Decision Center time zone:

Make a copy of the configmap file.

$ kubectl get configmap <release_name>-odm-dc-jvm-options-configmap -o yaml > dc-jvm-options.yaml

Edit the settings in the dc-jvm-options.yaml file and then apply the change.
```
$ kubectl apply -f dc-jvm-options.yaml
```
Tip: If you do need to add multiple options in Decision Center or in the other components, separate the options by using the \n separator.
```
-Dprop1=val1\n-Dprop2=val2
```
Restart the pods that are running the Decision Center containers.

Results

After the pods restart, the /config/configDropins/overrides/jvm.options file is updated in the ODM containers and the Liberty server JVM uses the new arguments.