Working with your new managed server nodes
Once you complete the customization instructions, you will have a WebSphere® Application Server for z/OS® application server node (managed node) in your Network Deployment cell.
Before you begin
Make sure that the WebSphere Application Server for z/OS product HFS and configuration HFS are mounted.
Procedure
- Start your node agent by issuing the following MVS™ console
command:
where:START server_proc,JOBNAME=nodeagent_name,ENV=cell_name.node_name.nodeagent_name
- server_proc is the node agent cataloged procedure.
- nodeagent_name is the node agent short name.
- node_name is the node short name.
- cell_name is the cell short name.
The START command starts the node agent. The node agent starts the location service daemon (if one is not already running). You should see a message like the following when the node is up and running:START BBO7ACR,JOBNAME=BBON001,ENV=CELL1.MVSA.BBON001
BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR z/OS CONTROL PROCESS BBON001 The node agent must be running in order for the deployment manager to administer the node.
- When the deployment manager for the cell is up and running,
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.
Until administrative security is enabled, you will see a signon screen that asks you for a user ID but no password.
The user ID can be anything and is used only to provide basic tracking of changes. Be aware that until you enable administrative security, anyone with a Web browser and access to the HTTP port can modify your application serving environment.
You can use the administrative console, scripting, or both to manage the node and deploy and manage J2EE applications. Before you can deploy applications, however, you need to add application servers to your managed node.
- hostname is the deployment manager HTTP transport
host name that you specified during customization.
- Application servers can be added to the managed server
node using the administrative console or scripting. You
can use one of the following methods:
- Create a new application server directly using the administrative
console or scripting. You can use the controller, servant and CRA
cataloged procedures and user IDs created during the managed node
setup process for any application servers you create in the managed
node. However, after you create additional application servers in
an existing node, you must run the following RACF commands:
RDEFINE STARTED new_server_short_nameA.* STDATA(USER(controller_region_userid) GROUP(configuration_group)) RDEFINE STARTED new_server_short_nameS.* STDATA(USER(servant_region_userid) GROUP(configuration_group)) RDEFINE SERVER CB.*.new_cluster_transition_name.* UACC(NONE) RDEFINE SERVER CB.*.new_cluster_transition_nameADJUNCT.* UACC(NONE) PERMIT CB.*.new_cluster_transition_name.* CLASS(SERVER) ID(servant_region_userid) ACC(READ) PERMIT CB.*.new_cluster_transition_name.* CLASS(SERVER) ID(controller_region_userid) ACC(READ) PERMIT CB.*.new_cluster_transition_nameADJUNCT.* CLASS(SERVER) ID(controller_region_userid) ACC(READ) SETROPTS RACLIST(STARTED) GENERIC(STARTED) REFRESH SETROPTS RACLIST(SERVER) GENERIC(SERVER) REFRESH
- Cluster an existing application server in another node, using this managed node as a target. This action creates a cloned copy of the application server being clustered in your new managed node.
- Create a new application server directly using the administrative
console or scripting. You can use the controller, servant and CRA
cataloged procedures and user IDs created during the managed node
setup process for any application servers you create in the managed
node. However, after you create additional application servers in
an existing node, you must run the following RACF commands:
- To start one of your managed node's application servers,
issue the following MVS console command:
where:START server_proc,JOBNAME=server_name,ENV=cell_name.node_name.server_name
- server_proc is the application server agent cataloged procedure (can be the same as the node agent cataloged procedure).
- nodeagent_name is the application server short name.
- node_name is the node short name.
- cell_name is the cell short name.
The START command starts the application server controller. The controller starts the location service daemon (if one is not already running) and then uses WLM to start the control region adjunct and the servants. You should see a message similar to the following when the node is up and running:START BBO7ACR,JOBNAME=AZSR01A,ENV=CELL1.MVSA.AZSR01A
BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR Z/OS CONTROL PROCESS AZSR01A
- Use one of the following two methods to stop your deployment
manager:
- Stop the location service daemon, which also stops any of
the cell's nodes on the same z/OS system. The location service
daemon holds pointers to modules in common storage, and stopping it
forces all cell members on the same z/OS system
as the daemon to shut down. To stop the location service daemon, enter
the following MVS console command:
where daemon_jobname is the location service daemon job name. The default location service daemon job name for a Network Deployment cell is BBODMNC.STOP daemon_jobname
- Stop just the node agent and its application servers while
leaving the location service daemon, deployment manager (if present),
and any other managed nodes on the z/OS system
still running. To stop the node agent, enter the following MVS console
command:
where nodeagent_name is the node agent short name. The default node agent short name is BBON001.STOP nodeagent_name
- Stop the location service daemon, which also stops any of
the cell's nodes on the same z/OS system. The location service
daemon holds pointers to modules in common storage, and stopping it
forces all cell members on the same z/OS system
as the daemon to shut down. To stop the location service daemon, enter
the following MVS console command:


File name: tins_dialogsteps_work4.html