Choose a network deployment configuration when your production environment needs features such as capacity, availability, scalability, and failover support.
When setting up a network deployment environment, WebSphere Application Server for z/OS must be configured on the server with a deployment manager node and an empty managed node that has not been federated to the deployment manager. The empty managed node must be federated only after you have augmented it to contain IBM Business Process Manager for z/OS configuration data.
When configuring a deployment manager node, the following consideration applies when allocating target data sets to hold the configuration JCL. It is possible, though not recommended, to use the same target data sets that you might have used for a stand-alone application server node. The job names for each configuration are very similar to one another, so if you use the same target data sets, it might be difficult to keep the two sets of jobs separate. Therefore, create a new set of target data sets for the deployment manager node and keep the two sets of jobs separate from one another.
All nodes in the network deployment cell are in the same administrative domain, and the JNDI namespace is shared among all servers in the cell. You can start and stop servers independently.