Setting up a Network Deployment environment

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:

WebSphere Application Server for z/OS Network Deployment run-time configuration

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

  1. Configure your deployment manager node on one of the systems in the cell.
    The deployment manager is the central administrative manager for your Network Deployment configuration. Follow the steps in Using the Customization Dialog and the information in Deployment manager node configuration considerations to configure your deployment manager node.
  2. Start the deployment manager process.

    There are two ways to start the deployment manager:

    • As a monitored process, which restarts automatically if a failure occurs.
    • As an unmonitored process, which is what the START dmgr_proc_name command does. See START dmgr_proc_name command for more information.

    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.

  3. Federate desired base Application Server nodes into your new deployment manager cell.
    Federation is the act of taking the node structure of a base Application Server node and merging it into the cell structure of a deployment manager cell. This act of federation may be done within a given MVS image or across MVS images within the same sysplex. Follow the steps in Using the Customization Dialog and the information in Base Application Server node federation considerations to federate the nodes.

    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:

    • Because addnode.sh stops any running Application Servers on the base Application Server node that you are federating, stop the Application Servers manually before performing the actual federation step.
    • To federate a z/OS base Application Server node, use the Customization Dialog to configure your addNode.sh parameters.

    See Applying a service level or restoring to the previous accepted service level and addNode command for more information. Alternatively, you can use the Administrative Console of the deployment manager to add running Application Server nodes to the cell. See Using the administrative console for more information.

  4. Enable the appropriate level of security after the installation is complete.
    See Securing your environment after installation for more information.
  5. Develop and unit test application components.

    Load existing application components and modules into your development environment and debug them. See Developing for more information.

  6. Assemble code into a main application module or enterprise archive (EAR) file.
    See Assembling or packaging for more information.
  7. Start all servers in the test environment.
    See Starting servers for more information.
  8. Deploy your applications in the test environment.
    See Deploying for more information.
  9. Test all applications thoroughly.

    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.

  10. Prepare and monitor the environment into which you deploy applications.
    See Administering for more information.
  11. Adjust application code, configurations, and system settings to improve performance.
    See Tuning for more information.
  12. Fix any known problems.
    See Troubleshooting or problem determination 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.

Related concepts
Deployment manager node configuration considerations
Base Application Server node federation considerations
Related tasks
Planning to install and customize WebSphere Application Server for z/OS
Preparing the base z/OS environment
Setting up a base Application Server cell
Migrating and coexisting
Related reference
addNode command
removeNode command
serverStatus command
START nodeagent_proc_name command
START appserver_proc_name command
STOP nodeagent_proc_name command
STOP appserver_proc_name command
START dmgr_proc_name command
STOP dmgr_proc_name command



Searchable topic ID:   tinszosnd
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/tins_zosnd.html

Library | Support | Terms of Use | Feedback