This article leads you through the background of a Network Deployment cell as well as the tasks involved in setting up a WebSphere Application Server for z/OS Network Deployment environment.
Before you begin
After you have your WebSphere Application Server for z/OS base Application Server cell up and running, there are many reasons why you should continue on and configure a Network Deployment cell. Overall, the Network Deployment cell provides a more robust operating environment. See Choosing between a base or Network Deployment configurationfor more information on the differences between the two environments.
Before you can set up a WebSphere Application Server for z/OS Network Deployment environment, you need to first install and customize the base WebSphere Application Server for z/OS function on each system to create an Application Server node on the system. See Setting up a base Application Server cell for instructions and further information.
Why and when to perform this task
A Network Deployment cell is a group of WebSphere Application Server for z/OS nodes, which includes a single deployment manager node and one or more Application Server nodes. The deployment manager node contains only one server, the deployment manager server named "dmgr," because the deployment manager node isn't allowed to define Application Servers.
The dmgr server is the administrative server for the entire Network Deployment cell, which means that all administrative actions taken on Application Servers within that cell are performed through the dmgr server.
The dmgr server also hosts the administrative application, known as the "Administrative Console," which provides a browser-based, graphical user interface for performing administrative operations on the Network Deployment cell. Similarly scripted administrative actions (through the wsadmin utility) are executed by the dmgr server. Remote scripted adminstrative actions are performed by the wsadmin utility through the dmgr's JMX SOAP or RMI connector.
A Network Deployment cell has the unique ability to:
The picture above depicts a typical WebSphere Application Server for z/OS Network Deployment runtime. It includes a location service daemon (BBODMNC) and two nodes (both housed in a cell, which can span systems); one for the deployment manager and one for the Application Server. The deployment manager node includes a deployment manager (BBODMGR) with a controller and a servant. The Application Server node includes a node agent (BBON001), a JMS server (BBOJ001), and an Application Server (server1) with a controller and any number of servants.
Setting up a Network Deployment environment involves several steps performed on each of the systems that comprise the cell. Follow the steps below to configure your WebSphere Application Server for z/OS Network Deployment environment.
Steps for this task
There are two ways to start the deployment manager:
Run the startManager command from the /bin directory of the installation root of the deployment manager.
For production systems, running the deployment manager as a monitored process is recommended.
Note: It is sometimes necessary to start the deployment manager on an MVS image different from the one on which it was originally configured. See Starting a deployment manager on a different MVS image for information.
In performing the federation process, you will run the addNode.sh script on every node that you plan to federate into the cell. The addNode command incorporates a base WebSphere Application Server product node into a deployment manager cell. You must run this tool on every base application system that you plan to make part of a Network Deployment cell. There are several parameters for the addNode command, but the most important are includeapps, the host name of the deployment manager node, the JMX connector type, and the JMX port of the deployment manager node.
Note:
Load existing application components and modules into your development environment and debug them. See Developing for more information.
See Testing for more information.
Follow normal test procedures as you move the test environment into production. Review the information in the Migrating topic to understand what you must look for. In particular, review the table at the end of the topic that links you to specific recommendations and practices.
You must configure your migrating applications to verify that they migrate in the way that you want. See Migrating and coexisting for more information.
Results
You can create a working WebSphere Application Server for z/OS cell.What to do next
Use the Administrative Console or other administrative tools (see Welcome to System Administration for more information) to validate, observe and control the incorporated nodes and the resources on these nodes. The console provides a central location for configuring, monitoring, and controlling all Application Servers on all nodes within the cell.