Configure WebSphere variables

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

 

Before you begin

We can define a WAS 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.

WebSphere variables are used for:

• Configuring WAS path names, such as JAVA_HOME, and APP_INSTALL_ROOT.

• Configuring certain cell-wide or cluster-wide customization values.

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

 

Overview

Define variables on the Environment > WebSphere Variables console page.

Define the scope to apply a variable cell-wide, cluster-wide, 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.

 

Procedure

1. Click Environment > WebSphere Variables in the administrative console to define a new variable.

2. Specify the scope of the variable. Declare the new variable for the Cell, Cluster, Node or Server and click Apply.

   The variable exists at the level you specify. Define a variable at multiple levels to use multiple values. The more granular definition overrides the higher level setting.

   For instance, if you specify the same variable on a node and a server, the server setting overrides the node setting. Similarly, a node level setting overrides a cluster or cell setting.

   Scoping variables is particularly important when testing data source objects. Variable scoping can cause a data source to fail the test connection, but to succeed at run time, or to pass the test connection, but fail at run time.

   See Test connection service for more information.

3. Click New on the WebSphere Variables page.

4. Specify a name, a value, and a description on the Variable page. Click OK.

5. Verify that the variable is displayed in the list of variables. The administrative console does not pick up typing errors. The variable is ignored if it is referred to incorrectly.

6. Save your configuration.

7. Stop the server and start the server again to put the variable configuration into effect.

 

See also

WebSphere variables collection
IBM Toolbox for Java JDBC driver
Configure and use the jt400.jar file

 

See Also

Variables

 

See Also

Session management custom properties

 

Related Information

HTTP transport custom properties

 

---