You can customize the Liberty profile environment by using
certain specific variables to support the placement of product binary
files and shared resources in read-only file systems.
About this task
The Liberty profile specific environment variables in
the following list can be configured in the server.env file
to customize the Liberty profile environment. The ${wlp.install.dir} configuration
variable has an inferred location that is always set to the parent
of the directory containing the launch script.
- WLP_USER_DIR
This environment variable can
be used to specify an alternative location for ${wlp.user.dir}.
This variable must be an absolute path. If this variable is specified,
the runtime environment looks for shared resources and server definitions
in the specified directory. The ${server.config.dir} is
equivalent to ${wlp.user.dir}/servers/serverName.
If this environment variable is not specified, ${wlp.user.dir} is
set to ${wlp.install.dir}/usr.
- WLP_OUTPUT_DIR
This environment variable can
be used to specify an alternative location for server generated output
such as logs, the workarea directory, and generated
files. This variable must be an absolute path. If this environment
variable is specified, ${server.output.dir} is set
to the equivalent of WLP_OUTPUT_DIR/serverName.
If this environment variable is not specified, ${server.output.dir} is
the same as ${server.config.dir}.
When the
server command is used, the server process uses the output directory
as its current working directory.
WLP_DEBUG_ADDRESSThis
environment variable can be used to specify an alternative port when
running the server in debug mode. The default value is 7777.
You can specify WLP_OUTPUT_DIR and WLP_USER_DIR environment
variables in server.env files. You can also specify
JVM options in jvm.options files. Both server.env and jvm.options files
only work when using the server management script. If you use the ws-server.jar executable
JAR file to launch your server, these files are not supported.