What are the WebSphere environment variables?
The environment variables are used to specify where files such as logs
and enterprise applications are located on each node. The variables can be
set at three levels or scopes:
- global or cell level
- node level
- application server level.
Where in the administrative repository are the variables stored?
The variables.xml files are located at the node level
($WAS_INSTALL/config/cells/<cell name>/nodes/<node name>
directory) or at the server level ($WAS_INSTALL/config/cells/<cell
name>/nodes/<node name>/servers/<server name> directory)
based on visibility level.
Why is there no variables.xml file for the nodeagent?
There is no variables.xml file in the $WAS_HOME/config/cells/<cell
name>/nodes/<node name>/servers/nodeagent directory because the
node agent uses the variables.xml located at the node level. This is the
node global variables.xml file and is the only variables.xml file the node
agent uses since this server cannot be modified (cannot install ear files
to or change it's purpose).
Why aren't the log files created and stored where I want
them?
This depends on exactly how the variable configuration was done. If the
variable was set as follows using the administrative console:
1. Opened an admin console.
2. Expanded the "Environment" section.
3. Chose the "Manage WebSphere Variables".
4. Modified the LOG_ROOT variable.
And the logs are not where you specified, here are some things to
check.
1. Is the scope correct?
There is a "Scope" option above the "New" and "Delete" buttons (above
the list of environment variables). Expand this (Press the "+" box) and it
will state which variables.xml file is being modified. So this might not
be pointing to the correct variables.xml file that it was intended for the
console to modify. Click "Browse Nodes" to choose the variables.xml at the
node level. To look at the variables.xml file for the application server,
click the "Browse Servers" to choose the application server. Note: only
the list of application servers for the corresponding node selected from
the "Browse Nodes" option will be shown. Then press the "Apply" button to
bring up the list of environment variables in the variables.xml file for
the specific scope that was set.
2. Did you save the configuration?
After all the changes to environment variables are made, save the
changes to the main repository. Click on the save option at the top menu
and press the "Save" button. Note: if nodes were added to the Network
Deployment Manager, check the "Synchronize changes with Nodes" box so the
changes are immediately propagated to all the nodes.
3. Did you synchronize the node with the Deployment
Manager?
The nodes and Network Deployment Manager do not have identical
repositories. If the "Synchronize changes with Nodes" option was not
chosen when saving or if the node did not get the changes because it was
not responding to the Network Deployment Manager, the nodes will need to
be synchronized. Do not just copy the files from the master repository to
the local node repository. Instead, expand the "System Administration"
menu then choose "Nodes". Check off the nodes to be synchronized and press
the "Synchronize" button.
4. Do you need to recycle the node?
The JVMs with the modified variables that are for runtime objects (for
example log files) have to be restarted (if they were running when you
made the changes) for the changes to take effect.
If these steps do not solve the problem, call 1-800-IBM-SERV to
talk to IBM support and open a problem management record (PMR).