This article lists definitions for the terms you will come across
in the WebSphere® Application
Server for z/OS® Customization
Dialog.
The WebSphere Application
Server for z/OS runtime
requires four servers in a Network Deployment cell: application server, deployment
manager, node agent, and location service daemon. The panels corresponding
to the following tables set up the names, network configuration, start procedures,
and user IDs for a Network Deployment cell.
System Locations
This section identifies the target z/OS system
on which you will configure the deployment manager for the Network Deployment
cell, along with system data set names.
- System name
- The system name for the target z/OS system on which you will configure WebSphere Application
Server for z/OS.
- Sysplex name
- The sysplex name for the target z/OS system on which you will configure WebSphere Application
Server for z/OS.
Tip: If
you are not sure what the system name (&SYSNAME) and sysplex name (&SYSPLEX)
are, use the console command D SYMBOLS on the target z/OS system
to display them.
For the following, specify the fully qualified data set
names without quotes.
Rule: You can specify up to 44 characters
for the data set names.
- PROCLIB
- An existing procedure library where the WebSphere Application Server for z/OS cataloged
procedures are added.
- PARMLIB
- An existing parameter library for system definitions to support WebSphere Application
Server for z/OS.
This data set must be in the parmlib concatenation for the target z/OS system.
- SYSEXEC
- A variable-block (RECFM=VB, LRECL=255) data set into which the customization
process places REXX EXECs to be called from TSO, such as the WebSphere Application
Server for z/OS error
log browser, BBORBLOG. You must allocate this data set and concatenate it
as part of the SYSEXEC DD allocation in your installation-wide TSO logon PROC
or allocation exec.
If your existing SYSEXEC DD data set concatenation consists
of fixed-blocked (RECFM=FB) data sets, you must make a copy of the hlq.DATA
data set (produced by the Customization Dialog) after the customization process
is complete, and place the copy in the SYSEXEC concatenation.
If you
do not specify a data set name, the customization process does not place any
REXX EXECs in any data set.
WebSphere Application
Server for z/OS product
data sets
Specify the following WebSphere Application Server for z/OS libraries
so they can be accessed by the customized jobstreams the dialog produces.
These data sets must be cataloged. See Product data sets for more information.
- Run WebSphere Application
Server from STEPLIB (Y/N)?
- Specifies whether to load WebSphere Application Server for z/OS load
modules from STEPLIB ("Y") or from the link pack area and link list ("N").
See Link pack area, link list, and STEPLIB for
more information.
- SBBOLPA
- WebSphere Application
Server for z/OS load
module library. It has modules that should go into LPA or the location service
daemon STEPLIB.
- SBBOLOAD
- WebSphere Application
Server for z/OS 31-bit
load module library. It has members that should go into the link list or LPA,
or into STEPLIB.
- SBBGLOAD
- WebSphere Application
Server for z/OS 64-bit
load module library. It has members that should go into the link list or LPA,
or into STEPLIB.
- SBBOLD2
- WebSphere Application
Server for z/OS load
module library that you installed through SMP/E. It has members that should
go into the link list, or into STEPLIB. DO NOT place them in LPA.
- SBBOEXEC
- WebSphere Application
Server for z/OS CLIST
library.
- SBBOMSG
- SBBOMSG WebSphere Application
Server for z/OS message
skeletons for language translation.
Additional system data sets
Specify
the following Language
Environment® and WebSphere Application Server for z/OS data sets
and whether they should ("Y") or should not ("N") load from STEPLIB. "Y" indicates
that the generated JCL will contain STEPLIB statements for these data sets.
Refer to your z/OS SMP/E
installation for the location of these data sets listed by their DD Name.
- SCEERUN
- Language
Environment runtime load module library.
- SCEERUN2
- Language
Environment runtime load module library.
- SGSKLOAD
- System SSL load module library. This data set does not exist in z/OS Version
1 Release 6 or later. See Link pack area, link list, and STEPLIB for
the effects of this change. Leave the data set name blank if ALL z/OS target
systems are at z/OS Version
1 Release 6 or later.
WebSphere Application Server for z/OS product
directory
- WebSphere Application
Server product directory
- The name of the directory where WebSphere Application Server for z/OS files
reside after installation. See Product file system for more information.
WebSphere configuration HFS
This
section defines the WebSphere configuration HFS that you will use for
the deployment manager. See
HFS configuration strategy for more information.
- Mount point
- Read/write HFS directory mount point where application data and environment
files are written. The customization process creates this mount point if it
does not already exist.
- Name
- Hierarchical File System data set you will create and mount at the above
mount point.
Rule: You can specify up to 44 characters for the data
set name.
- Volume, or '*' for SMS
- Specify either the DASD volume serial number to contain the above data
set or "*" to let SMS select a volume. Using "*" requires that SMS automatic
class selection (ACS) routines be in place to select the volume. If you do
not have SMS set up to handle data set allocation automatically, list the
volume explicitly.
- Primary allocation in cylinders
- Initial size allocation in cylinders for the above data set.
Recommendation: The
minimum suggested size is 250 cylinders (3390).
- Secondary allocation in cylinders
- Size of each secondary extent in cylinders.
Recommendation:
The minimum suggested size is 100 cylinders.
Server customization
During
this customization task, you will create a cell configuration, a deployment
manager node and deployment manager, and a location service daemon. The panels
corresponding to the following tables set up the names, network configuration,
start procedures, and user IDs for a deployment manager server.
Rule: In
the following customization, names must be eight or fewer characters unless
otherwise specified.
- WebSphere Application
Server home directory
- Directory in which the deployment manager resides. See HFS configuration strategy for more information.
Note: You
can alter only the portion after the configuration HFS mount point.
- Cell name (short)
- Name that identifies the cell to z/OS facilities such as SAF.
Rules:
- Name must be eight or fewer characters and all uppercase.
- Name must be unique among all other cells in the sysplex.
- Cell name (long)
- Primary external identification of this WebSphere Application Server for z/OS cell.
This name identifies the cell as displayed through the administrative console.
Rules:
- Name must be 50 or fewer characters and can be of mixed case.
- Name must be unique among all other cells in the sysplex.
- Node name (short)
- Name that identifies the deployment manager node to z/OS facilities
such as SAF.
Rules:
- Name must be eight or fewer characters and all uppercase.
- Name must be unique within the cell.
- Node name (long)
- Primary external identification of this WebSphere Application Server for z/OS deployment
manager node. This name identifies the node as displayed through the administrative
console.
Rules:
- Name must be 50 or fewer characters and can be of mixed case.
- Name must be unique within the cell.
- Server name (short)
- This value identifies the deployment manager server to z/OS facilities
such as SAF.
Note: The server short name is used as the server
JOBNAME.
Rule: Name must usually contain seven or fewer all-uppercase
characters. To change the jobname later to an eight-character value, you must
follow the steps outlined in the "Converting a 7-character server short name
to 8 characters" article in the information center.
- Server name (long)
- Name of the application server and the primary external identification
of this WebSphere Application
Server for z/OS server.
This name identifies the server as displayed through the administrative console.
The server name has a fixed name (long) of "dmgr".
- Cluster transition name
- WLM APPLENV name for this server.
Note: The deployment manager
is not clusterable, so this value never actually becomes the cluster short
name of this server's cluster. However, like an application server, the deployment
manager still needs an APPLENV, so the cluster transition name is used for
this purpose.
Rule: Name must be eight or fewer characters
and all uppercase.
- Add ability to administer Proxy Server(s) (Y/N) ?
- Specify "Y" to add the capability to administer Proxy Servers.
Deployment manager definitions
Rule: In the
following definitions, names must be eight or fewer characters unless otherwise
specified.
Controller Information
- Jobname
- The jobname, specified in the MVS™ START command JOBNAME parameter, associated
with the deployment manager controller. This is the same as the server short
name and it cannot be changed through the Customization Dialog.
- Procedure name
- Name of member in your procedure library to start the deployment manager
controller.
Rule: Name must be seven or fewer characters.
- User ID
- The user ID associated with the deployment manager controller.
Note: If
you are using a non-IBM security system, the user ID might have to match the
procedure name. Please refer to your security system's documentation.
- UID
- The user identifier associated with this user ID.
Rule: UIDs
must be unique numbers, between 1 and 2,147,483,647, within the system.
Servant Information
- Jobname
- The jobname used by WLM to start the deployment manager servant. This
is set to the server short name followed by the letter "S", and it cannot
be changed through the Customization Dialog.
- Procedure name
- Name of member in your procedure library to start the deployment manager
servant.
Rule: Name must be seven or fewer characters.
- User ID
- The user ID associated with the deployment manager servant.
Note: If
you are using a non-IBM security system, the user ID might have to match the
procedure name. Please refer to your security system's documentation.
- UID
- The user identifier associated with this user ID.
Rule: UIDs
must be unique numbers, between 1 and 2,147,483,647, within the system.
Deployment manager TCP/IP information
Note: Do
not choose port values already in use.
- Node host name
- IP name or address of the system on which the server is configured. This
value is used by other WebSphere Application Server for z/OS functions
to connect to this server.
Note: The node host name must always
resolve to an IP stack on the system where the application server runs. (You
can either have multiple IP stacks on a given MVS image and have the deployment manager
and stand-alone application server tied to separate host names, or you can
associate them with the same node host name.) The node host name cannot be
a DVIPA or a DNS name that, in any other way, causes the direction of requests
to more than one system.
- SOAP JMX Connector port
- Port number for the JMX HTTP connection to this server based on the SOAP
protocol. JMX is used for remote administrative functions, such as invoking
scripts through wsadmin.sh.
Rule: Value cannot be 0.
- Cell Discovery Address port
- Port number used by node agents to connect to this deployment manager
server.
- ORB Listener host name
- IP address on which the server's ORB listens for incoming IIOP requests.
The default is "*", which instructs the ORB to listen on all available IP
addresses.
- ORB port
- Port for IIOP requests that acts as the bootstrap port for this server
and also as the port through which the ORB accepts IIOP requests.
Rule: Value
cannot be 0.
- ORB SSL port
- Port for secure IIOP requests. The default is "0", which allows the system
to choose this port.
- HTTP transport host name
- IP address on which the server's Web container should listen for incoming
HTTP requests. The default is "*", which instructs the Web container to listen
on all available IP addresses.
Note: The "transport host name"
becomes the "hostname" in the virtualhosts.xml file, which makes setting a
specific IP address here less than ideal because, if you do so, you are restricting
yourself to that IP address until you go into the administrative console and
add another virtual host.
- HTTP port
- Port for HTTP requests.
Rule: Value cannot be 0.
- HTTP SSL port
- Port for secure HTTP requests.
Rule: Value cannot be 0.
- High Availability Manager Host
- Host name for the High Availability Manager. This host name must resolve
to a single IP address--it cannot be a multihomed host.
Note: This
field was removed from the Customization Dialog in WebSphere Application Server for z/OS Version
6.0.2.
- High Availability Manager communication port
- Port on which the High Availability Manager listens.
Location service daemon
The location service daemon
is the initial point of client contact in WebSphere Application Server for z/OS.
The server contains the CORBA-based location service agent, which places sessions
in a cell. All RMI/IIOP IORs (for example, for enterprise beans) establish
connections to the location service daemon first, then forward them to the
target application server.
- Daemon home directory
- Directory in which the location service daemon resides. This is set to
the configuration HFS mount point/Daemon and cannot be changed.
- Daemon jobname
- Specifies the jobname of the location service daemon, specified in the
JOBNAME parameter of the MVS start command used to start the location service
daemon.
Note: The same daemon jobname is used on all z/OS systems hosting the cell. Therefore,
this name is generic and has no system indicator. When the deployment manager's
controller started, its location service daemon was started automatically
using this particular daemon jobname value.
Caution: When
configuring a second cell, ensure you change the daemon jobname from the default
or value you used for the first cell.
Note: A server automatically
starts the location service daemon if it is not already running.
- Procedure name
- Name of the member in your procedure library to start the location service
daemon.
Rule: Name must be seven or fewer characters.
- User ID
- The user ID associated with the location service daemon.
- UID
- The user identifier associated with this user ID.
Rule: UIDs
must be unique numbers, between 1 and 2,147,483,647, within the system.
- IP Name
- The fully qualified IP name, registered with the Domain Name Server (DNS),
that the location service daemon uses.
Adhere to the following regarding
your location service daemon IP name:
- It must be unique in the sysplex.
- It must not have the same value as any one system's node host name. (You
can use the host name of the LPAR.)
- It should be a name that can be used in conjunction with a routing service
that distributes requests among nodes in the cell (that is, systems in the
sysplex).
- It should be a virtual IP address (VIPA) if you are operating in a sysplex.
Note:
- IBM® recommends
you use z/OS Sysplex
Distributor by way of a "Dynamic Virtual IP address" (DVIPA). See related
sections in the information center for more information.
- Select the IP name for the location service daemon carefully. Once chosen
it is difficult to change, even in the middle of customization. This name
must not be a numeric, such as, 3.7.25.43.
- Port
- The port number on which the location service daemon listens.
Note: Select
the port number for the location service daemon carefully. You can choose
any port you want; but, once chosen, it is difficult to change, even in the
middle of customization.
- SSL port
- The port number on which the location service daemon listens for SSL connections.
- Register daemon with WLM DNS
- If you use the WLM DNS (connection optimization), you must select "Y"
to register your location service daemon with it. Otherwise, select "N."
Note: Only one location service daemon per LPAR can register its domain
name with WLM DNS. If you have multiple cells in the same LPAR and register
one location service daemon and then a second, the second will fail to start.
Security customization - WebSphere-managed security
For
this security option, you must choose an administrator user ID and password.
- Administrator user ID
- Enter an alphanumeric user ID which you will use to log on to the administrative
console and perform administrative tasks. This user ID and its password will
initially be the only entry in the file-based user registry.
- Administrator password
- This password must not be blank.
Web Server Configuration
If
you are running IBM HTTP
Server for z/OS on
a local or remote z/OS system and want to have WebSphere Application Server for z/OS manage
the
plugin-cfg.xml file, fill in the following values.
- Web Server Name
- Name used to define the Web server in the administrative console.
- Host
- IP name or address of the z/OS system on which the Web server is
located.
- Port
- HTTP port on which the Web server listens.
- Application Mapping
- Determines whether you want to map all applications (A), none of the applications
(N), or the default application (D) to the Web server.
- Deployment manager security is enabled
- Specify "Y" if global security is enabled on the Network Deployment cell
and the deployment manager.
- User ID
- A user ID with full administrative privileges for the Network Deployment
cell. This is set to the security domain administrator user ID and cannot
be changed.
Security Domain Configuration
These
panels display values you previously set in the "Configure security domain"
option--you can not change any of the values here. If you do want to make
changes, you must go back to the main dialog panel and run through the "Configure
security domain" option again.