Skip to main content
Version: 4

Configuring local time zone for the application

This document explains how to configure Adeptia Connect to use a local time zone (For example, EST) instead of the default UTC/GMT. Whether you're setting this up during initial deployment or modifying an existing deployment, applying the configuration ensures that time values across all modules and logs reflect your local server time.

Prerequisites​

  • If the application is already deployed deactivate all events.

  • Ensure that you have access to the global values.yaml file used for the application deployment.

  • Verify that you have the required permissions to modify Kubernetes deployments and run Helm commands.

Steps to configure local time zone​

  1. Open the global values.yaml file and set the values for the following variables to false.

    1. EXECUTE_STATIC_JOB (in the static section of the global values.yaml file)

    2. EXECUTE_CLEANUP_JOB (in the cleanup section of the global values.yaml file)

    3. EXECUTE_MIGRATION_JOB (in the migration section of the global values.yaml file)

  2. Within the same values.yaml file, navigate to the webrunner > environmentVariables section and add the -Duser.timezone Java system property to the JAVA_OPTS variable to specify the desired time zone.

    For example:

    Success
    • Replace America/New_York with the appropriate Java-supported time zone identifier, for example, Asia/Kolkata, America/Chicago.
    • If other Java system properties are already defined in JAVA_OPTS, append the -Duser.timezone property, separating it with a space.
      For example:
      JAVA_OPTS: "-Dsome.other.property=value -Duser.timezone=America/New_York"

  3. Repeat this addition for each microservice to ensure the time zone setting is applied across the application.

  4. Save the updated values.yaml file.

  5. Update the Helm repository by running the following command:

  6. If the application is already deployed, run the following upgrade command. Else, skip to the next step.

  7. If you are performing a fresh install of the application, run the following deployment command:

  8. Restart all the microservices.

  9. Reactivate the previously deactivated events.