Working with your new deployment managers
Once you complete the customization instructions, you will have a WebSphere® Application Server for z/OS® Network Deployment cell. The Network Deployment cell consists of a deployment manager and a location service daemon. To run Java™ EE applications, you must add application server nodes.
Before you begin
Make sure that the WebSphere Application Server for z/OS product HFS and configuration HFS are mounted.
Procedure
- To start your deployment manager, issue the following MVS™ console
command:
where:START server_proc,JOBNAME=dmgr_name,ENV=cell_name.node_name.dmgr_name
- server_proc is the deployment manager controller cataloged procedure.
- dmgr_name is the deployment manager short name.
- node_name is the deployment manager node short name.
- cell_name is the cell short name.
The START command starts the deployment manager controller. The controller starts the location service daemon, then uses WLM to start the deployment manager servant. You should see a message similar to the following when the deployment manager is up and running:START BBO7DCR,JOBNAME=BBODMGR,ENV=BBOCELL.BBODMGR.BBODMGR
BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR Z/OS CONTROL PROCESS BBODMGR
- Once the deployment manager is successfully started, access
the administrative console by pointing a web browser to the following
URL:
where:http://hostname:http_port/ibm/console
- hostname is the deployment manager HTTP transport
host name that you specified during customization.Note: If you specified * for the deployment manager HTTP host name, this is actually the deployment manager node host name.
- http_port is the deployment manager HTTP port
that you specified during customization.Note: The default HTTP port for the deployment manager is 9060.
The user ID needs to be the one defined during the customization of the dmgr.
You can use the administrative console, scripting, or both to manage the Network Deployment cell and deploy and manage Java EE applications. Before you can deploy applications, however, you need to add application server nodes to your Network Deployment cell.
- hostname is the deployment manager HTTP transport
host name that you specified during customization.
- Add an application server node to a Network Deployment
cell using one of two methods:
- Create an (empty) managed node using the Profile Management
Tool or zpmt command. The new node can reside on
the same or a different z/OS system as the deployment manager.
The new managed node, consisting of just a node agent and perhaps
a location service daemon, is federated into the Network Deployment
cell. Once this is done, you can use the administrative console or
scripting to add application servers and deploy and manage Java EE applications in the node.
See Planning for new managed (custom) nodes for more information.
- Federate an existing standalone application server into the
Network Deployment cell. The standalone server node becomes a managed
node in the Network Deployment cell, along with any Java EE
applications that have been deployed on it.
See Planning to federate standalone servers into a Network Deployment cells for more information.
Note: Each z/OS system also needs one location service daemon for each standalone or Network Deployment cell hosted on the system. - Create an (empty) managed node using the Profile Management
Tool or zpmt command. The new node can reside on
the same or a different z/OS system as the deployment manager.
The new managed node, consisting of just a node agent and perhaps
a location service daemon, is federated into the Network Deployment
cell. Once this is done, you can use the administrative console or
scripting to add application servers and deploy and manage Java EE applications in the node.
- Use one of the following two methods to stop your deployment
manager:
- Stop the location service daemon, which also stops the deployment
manager and any of the cell's managed nodes on the same z/OS system.
The location service daemon holds pointers to modules in common storage,
and stopping it forces the cell's nodes on the same z/OS system
as the location service daemon to shut down. To stop the location
service daemon, enter the following MVS console
command:
STOP daemon_jobname
where daemon_jobname is the location service daemon job name. The default location service daemon job name for a Network Deployment cell is BBODMNC.
Note: This is the easiest way to stop the deployment manager. - Stop just the deployment manager, leaving the location service
daemon and any managed nodes on the z/OS system
still running. This works because the deployment manager is used to
administer only the cell--it does not need to be up for Java EE applications in the cell to run. To
stop the deployment manager, enter the following MVS console
command:
STOP dmgr_name
where dmgr_name is the deployment manager short name. The default deployment manager short name is BBODMGR.
- Stop the location service daemon, which also stops the deployment
manager and any of the cell's managed nodes on the same z/OS system.
The location service daemon holds pointers to modules in common storage,
and stopping it forces the cell's nodes on the same z/OS system
as the location service daemon to shut down. To stop the location
service daemon, enter the following MVS console
command:


File name: tins_dialogsteps_work3.html