Merge pull request #7336 from OpenLiberty/7320-jvm

time zone jvm prop edits

modules/ROOT/pages/log-trace-configuration.adoc

@@ -24,6 +24,13 @@ A server has the following four primary log files:
 
 - `verbosegc.XXX.log` - These files contain verbose garbage collection output from the JVM and are created by default when the Java implementation is either IBM Java or IBM Semeru Runtimes. Up to 10 rolling log files are created in your log directory, with 1024 GC cycles per file, where `XXX` represents the sequence number of the log file. Custom configurations take precedence over the default behavior. To disable the verbose garbage collection logs, add `VERBOSEGC=false` to the `server.env` file. For more information, see the https://eclipse.dev/openj9/docs/vgclog[Verbose garbage collection logs].
 
+You can use the `user.timezone` JVM property to set the time zone for your application environments. Set the `user.timezone` property in the `jvm.properties` file. The updated time zone information is displayed in the `messages.log` and `trace.log` files. The following example shows how to set the time zone.
+
+[subs=+quotes]
+----
+-Duser.timezone=_time_zone_code_
+----
+
 The following sections provide more information about configuring your Open Liberty logs:
 
 * <<#configuaration,Logging configuration>>

modules/reference/pages/config/server-configuration-overview.adoc

@@ -166,15 +166,17 @@ If no `jvm.options` files exist in these locations, then the server script looks
 Common uses of `jvm.options` files include:
 
 * Setting JVM memory limits
-* Enabling Java Agents that are provided by monitoring products
-* Setting Java System Properties
+* Enabling Java agents that are provided by monitoring products
+* Setting Java system properties
+* Setting time zones
 
 The `jvm.options` file format uses one line per JVM option, as shown in the following example:
 
-[source,properties]
+[subs=+quotes]
 ----
 -Xmx512m
--Dmy.system.prop=This is the value.
+-Dmy.system.prop=_property_value_
+-Duser.timezone=_time_zone_code_
 ----
 
 You don’t need to escape special characters, such as spaces.
@@ -222,7 +224,7 @@ The `configDropins` directory offers a convenient method for adding or modifying
 
 * Defaults (`usr/servers/server_name/configDropins/defaults`): This directory is for setting defaults for configuration elements that are not specified in `server.xml`. It allows `server.xml` to remain the primary configuration source, with other default settings provided through this directory.
 
-Changes to the configuration files placed in either the `configDropins/overrides` or `configDropins/defaults` directories are dynamically monitored. Additions, removals, or updates are reflected in the runtime configuration automatically. 
+Changes to the configuration files placed in either the `configDropins/overrides` or `configDropins/defaults` directories are dynamically monitored. Additions, removals, or updates are reflected in the runtime configuration automatically.
 
 Configurations in the `configDropins/overrides` directory take precedence over configurations in the `server.xml` file, which in turn take precedence over configurations in the `configDropins/defaults` directory. The configurations in `configDropins/overrides` and `configDropins/defaults` supersede any default settings a feature specifies.