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:
START server_proc,JOBNAME=dmgr_name,ENV=cell_name.node_name.dmgr_name
where:- 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.
If you chose default values, for example, you
would enter the following START command: START BBO7DCR,JOBNAME=BBODMGR,ENV=BBOCELL.BBODMGR.BBODMGR
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: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:
http://hostname:http_port/ibm/console
where:- 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.
Until global security is enabled, you will see a
signon screen that asks you for a user ID.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.
- Add an application server node to a Network Deployment
cell using one of two methods:
Application server nodes (also called managed nodes) in a Network
Deployment cell consist of a node agent and any number of application
servers per node.
Note: Each z/OS system also needs one location
service daemon for each standalone or Network Deployment cell hosted
on the system.
- 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.