Base Application Server node federation considerations
This article presents considerations for when you federate your
base Application Server node.
- Ensure that you run the Dialog on the MVS image on which the base Application
Server you will federate resides.
- The original base Application Server node's cell structure is no longer
used once federation completes--the active cell structure is the deployment
manager's cell. The location service daemon server of the original base Application
Server node is also no longer used. The original base Application Server node's
HFS and its mount point remain, however, as well as the entire contents of
the HFS, which are only copied over to the deployment manager's HFS. (This
is in case you want to un-federate the node later.) When federation occurs,
the contents of the base Application Server node's HFS is modified to reflect
the new cell in which it resides. This means the symbolic links used during
server startup are modified, and some of the XML files are updated to reflect
the new cell name.
- When loading customization variables for this option, ensure that your
"WAS home directory" value is correct. Select the "Load customization variables"
option and specify the proper saved variables data set prior to defining your
variables:
- If you are running at a service level prior to W502000 (indicated by an
unmodifiable "WAS home directory" field), load the saved variables from the
base Application Server configuration. Then go through and manually modify
the rest of the fields with the correct deployment manager and node agent
values.
- If you are running at the W502000 service level or above (indicated by
a modifiable "WAS home directory" field), load the saved variables from the
deployment manager configuration. Then, if necessary, modify the "WAS home
directory" field and provide the correct base Application Server directory
value.
- When allocating target data sets for this option, it is recommended that
you use different target data sets than any used before.
- When defining variables for this option, you will need to modify some
of the defaults depending on from which configuration you loaded the variables.
See Define variables for federate base Application Server node - definitions for
more information.
- Ensure you save your variables to a different file than one you used for
any other configuration.
- When you go to generate the customized jobs, code the job card information
to specify the authority of the WebSphere administrator ID. This ensures that
each customized job's JOB card will have this information, which is important
because that authority is required for many of the jobs to run properly.
- Prior to running the BBOWADDN job according to the instructions from the
Customization Dialog, stop your base Application Server manually by stopping
its location service daemon. The federation process will attempt to stop the
server automatically, but doing it manually ensures it is stopped correctly.
Also make sure the files bbowaddn.out and bbowaddn.err don't already exist
in your /tmp directory.

Setting up a Network Deployment environment
Searchable topic ID:
cinsconsidfed
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/cins_considfed.html