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.
- Start your node agent by issuing the following MVS console command:
START server_proc,JOBNAME=nodeagent_name,ENV=cell_name.node_name.nodeagent_name
Option |
Description |
server_proc |
The node
agent cataloged procedure. |
nodeagent_name |
The node
agent short name. |
node_name |
The node short
name. |
cell_name |
The cell short
name. |
If you chose default values for example (your sysplex is named CELL1
and your system is named MVSA), you would enter the following START command:START BBO6ACR,JOBNAME=BBON001,ENV=CELL1.MVSA.BBON001
The START command brings up 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: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:
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 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 global 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.
- Application servers can be added to the managed server node using
the administrative console or scripting. Either of two methods can be used:
- 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.
- Cluster an existing application server in another
node, using this managed node as a target. This will create a "cloned" copy
of the application server being clustered in your new managed node.
- To start one of your managed node's application servers, issue
the following MVS console command:
START server_proc,JOBNAME=server_name,ENV=cell_name.node_name.server_name
Option |
Description |
server_proc |
The application
server agent cataloged procedure (can be the same as the node agent cataloged
procedure). |
nodeagent_name |
The application
server short name. |
node_name |
The node short
name. |
cell_name |
The cell short
name. |
If you chose the default procedure name for example (your sysplex
is named CELL1, your node is named MVSA, and your server is named AZSR01A),
you would enter the following START command:START BBO6ACR,JOBNAME=AZSR01A,ENV=CELL1.MVSA.AZSR01A
The START command brings up 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: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:
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.
- 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:
STOP nodeagent_name
where nodeagent_name is
the node agent short name. The default node agent short name is BBON001.