IBM Support

Setting environment entries in the WebSphere Application Server V8.5 Liberty profile

Question & Answer


How to set environment entries in the WebSphere Application Server V8.5 Liberty profile since there is no administrative console available?


Environment entries can be used to specify variables not specific to the WebSphere Application Server Liberty profile, but are defined by other elements as well. These variables tend to be operating system-specific and also include such variables as JAVA_HOME, WLP_USER_DIR, and WLP_OUTPUT_DIR.

WebSphere Application Server V8.5 Liberty profile
Within the Liberty profile these environment variables can be specified in the following two locations and support only KEY=value pairs. Shell and variable expansion are not supported:.

  • Runtime-Level file affecting all servers within the Liberty profile:


  • Server-Level file affecting only a specific server within the Liberty profile:


If the server management script locates both of the server.env files, the contents of the two server.env files will be merged, with values in the the Server-Level file taking precedence over values in the Runtime-Level file.

If <>/etc/server.env and/or <>/usr/servers/<serverName>/server.env exists and is readable, its key=value contents are read and set into the environment. The file can be in ASCII or EBCDIC. Comments start with a '#' and go to the end of the line. Values that contain white space can be placed in double quotes. Any environment entries specified in this file will override entries from the initial environment.

For example:

# Use a specific Java binary
# JAVA_HOME=c:\Java

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"General","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.5;8.5","Edition":"Liberty","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 June 2018