Configuring WebSphere variables

This topic describes how to create a WebSphere Application Server variable.

Before you begin

You can define a WebSphere Application Server variable to provide a parameter for some values in the system. After you define the name and value for a variable, the value is used in place of the variable name. Variables most often specify file paths. However, some system components also support the use of variables. The Variable settings topic supplies further details about specifying variables and highlights further details about WebSphere Application Server components that use them.

WebSphere variables are used for:

The scope of a variable can be cell-wide, node-wide, or applicable to only one server process.

Why and when to perform this task

Define variables on the Environment > WebSphere Variables console page.

Define the scope to apply a variable node-wide or to only one server process. A variable resolves to its new value when used in a component that supports the use of variables.

Steps for this task

  1. Click Environment > Manage WebSphere Variables in the console navigation tree. On the WebSphere Variables page, click New.
  2. Specify the scope of the new variable. Indicate if new variable should be for the Node, or Server, then click Apply.
    The scope limits the variable to the level that you select. Choosing to apply a variable to a node or server puts the variable on all servers at that particular level. If you specify the same variable on a node as on a server, the server level variable overrides the or node variable. Similarly, a variable at the node level overrides the instance specified at the cell level.
  3. On the Variable page, specify a name, value and description for the variable. Then click OK.
    You can use the following options for setting WebSphere variables:
    • Use Cell-wide z/OS variables.
    • Use WebSphere variables to modify the daemon configuration. By appending a server custom property onto a daemon tag, you can designate that variable specifically for that daemon. Enter DAEMON_<server custom property> in the Name field. For example, if you enter DAEMON_ras_trace_outputlocation in the Name field and SYSOUT in the Value field, you can direct that particular daemon's trace output to SYSPRINT.
    • WebSphere variables support substitution. The name of a variable can be formed by substituting the value of another variable. If you enter ${<variable name>} in the Name field, the value of <variable name> is the name of your new WebSphere variable. For example ${JAVA_HOME} creates a WebSphere variable with a name that is equal to the Java home directory.
    • The application server uses WebSphere internal variables for its own purposes. The prefixes that indicate that a variable is WebSphere internal are WAS_DAEMON_<server custom property>, WAS_DAEMON_ONLY_<server custom property>, and WAS_SERVER_ONLY_<server custom property>. Any variables with these tags are not intended for your use. They are reserved exclusively for use by the server run time. Modifying these variables can cause unexpected errors.
  4. Verify that the variable is shown correctly in the list of variables. The administrative console does not pick up errors in spelling. The variable is ignored if added incorrectly.
  5. Save your configuration.
  6. To have the configuration take effect, stop the server and then start the server again.

Related concepts
Variables overview
Variables
Related tasks
Configuring the cell-wide environment
Related reference
WebSphere variables collection



Searchable topic ID:   trun_variable
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/tcws_variable.html

Library | Support | Terms of Use | Feedback