This topic applies only on the z/OS operating system.

Working with your new deployment manager

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 J2EE applications, you must add application server nodes. See below for details.) This article provides useful information for working with your new Network Deployment cell.

Before you begin

Make sure that the WebSphere Application Server for z/OS product HFS and configuration HFS are mounted. If you chose to load the SBBOLPA (and possibly SBBOLOAD) into the system link pack area, make sure that these libraries are loaded into LPA before starting the server.

Make sure that these data sets are APF-authorized if they are in LPA or if they are being added to STEPLIB.

Procedure

  1. To start your deployment manager, issue the following MVS console command:
    START server_proc,JOBNAME=dmgr_name,ENV=cell_name.node_name.dmgr_name
    Option Description
    server_proc The deployment manager controller cataloged procedure.
    dmgr_name The deployment manager short name.
    node_name The deployment manager node short name.
    cell_name The cell short name.
    If you chose default values and your system is named MVSA, for example, you would enter the following START command:
    START BBO6DCR,JOBNAME=BBODMGR,ENV=MVSA.MVSA.BBODMGR
    The START command brings up 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
  2. 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
    Option Description
    hostname The deployment manager HTTP transport host name 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 The deployment manager HTTP port 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 J2EE applications. Before you can deploy applications, however, you need to add application server nodes to your Network Deployment cell.

  3. Add an application server node to a Network Deployment cell using one of two methods:
    • Create an (empty) managed node using the Customization Dialog. 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 J2EE applications in the node.

      See Planning for a new managed node in a Network Deployment cell for more information.

    • Federate an existing stand-alone application server into the Network Deployment cell. The stand-alone server node becomes a managed node in the Network Deployment cell, along with any J2EE applications that have been deployed on it.

      See Planning to federate a stand-alone server into a Network Deployment cell for more information.

    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 stand-alone or Network Deployment cell hosted on the system.
  4. 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 jobname. The default location service daemon jobname 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 J2EE 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.




In this information ...


Related reference

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 10:03:57 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=tins_dialogsteps_work3.dita
File name: tins_dialogsteps_work3.html