Once you complete the customization instructions, you will have
a WebSphere® Application
Server for z/OS® stand-alone
application server. The application server includes a (simple) cell and node
structure. This article provides useful information for when you work with
your new server.
Before starting your server
Make sure that the WebSphere Application
Server for z/OS product
file system and configuration file system 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.
Starting the stand-alone application server
To start
your stand-alone application server, issue the following MVS console command:
START server_proc,JOBNAME=server_name,ENV=cell_name.node_name.server_name
where:
- server_proc is the stand-alone application server controller
cataloged procedure.
- server_name is the server short name.
- node_name is the node short name.
- cell_name is 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 BBO6ACR,JOBNAME=BBOS001,ENV=MVSA.MVSA.BBOS001
The
START command brings up the controller. The controller starts the location service
daemon, then uses WLM to start the servant. You should see a message like
the following when the entire server is up and running:
BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR Z/OS CONTROL PROCESS BBOS001
Accessing the server administrative console
Once the
server is successfully started, access the administrative console port by
pointing a Web browser to the following URL:
http://hostname:http_port/ibm/console
where:
- hostname is the HTTP transport host name you specified
during customization.
Note: If you specified "*" for the HTTP host name, this
is actually the node host name.
- http_port is the HTTP port you specified during customization.
Note: The default Administrative console
port for the stand-alone application server is 9060. This value has changed
since Version 6.0.
Until global security is enabled, you will see a sign-on 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 application
server and deploy and manage J2EE applications.
Accessing the Samples Gallery
If you chose to install
the sample applications, you can access them by pointing a Web browser to
the following URL:
http://hostname:http_port/WSsamples/
where:
- hostname is the HTTP transport host name you specified
during customization.
Note: If you specified "*" for the HTTP host name, this
is actually the node host name.
- http_port is the HTTP port that you specified during
customization.
Note: The default HTTP port for the stand-alone application
server is 9080.
Stopping your stand-alone application server
The easiest
way to stop the stand-alone application server is to stop the location service
daemon. The location service daemon holds pointers to modules in common storage,
and stopping it forces the rest of the cell 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 stand-alone application server is BBODMNB.