Why and when to perform this task
Planning the product is fundamental for a successful installation. In addition to the obvious configuration aspects, there are other things that should be considered, including:
Location service daemons are perhaps the least understood component of a configuration. A location service daemon is a single controller server. A Network Deployment configuration that spans MVS images in a Sysplex will have one location service daemon per system over which the cell spans.
Note: What does a location service daemon do? Its role is to provide "location name services" to the node, and as part, be able to resolve indirect object requests from external clients into direct references. Suffice it to say, a location service daemon is required. Bring down the location service daemon and all servers related to that location service daemon come down as well.
For more information on location service daemons, see Location service daemons.WebSphere Application Server will use the dynamic capability of WLM if it is available, otherwise it will rely on static WLM application environments. Static application environments still in existence when APAR OW54622 is applied will simply stop being used in favor of dynamically created ones of the same name.
Allow no more than one node per system in the cell. The primary reason for imposing this limitation is because use of the Sysplex Distributor for the bootstrap port of the node agents, particularly when all the node agents in the cell are listening on the same bootstrap port. Two node agents on the same MVS image listening on the same port might imply TCP port sharing.
It is possible to have multiple TCP stacks on the same MVS image, and to tie a port to a specific TCP stack. Multiple nodes on separate MVS images means each has its own TCP stacks with separate IP addresses. There's very little reason to configure multiple nodes in the same cell on the same MVS image. Once a node is created on an MVS image and becomes part of the configuration cell, no other nodes will be federated on that MVS image. If more servers are desired on the MVS image, servers will be added to the existing node rather than federating in more nodes.
You can now configure a new log stream; the Transaction XA Partner log. For more information about the Transaction XA Partner log, see Working with diagnostic tools and controls.