This article lists definitions for the terms you will come
across in the WebSphere® Application Server for z/OS® Customization
Dialog.
System locations
This section identifies
the target z/OS system on which you will configure the
new stand-alone application server, 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.
Note: Specify
"Y" if you have another instance of WebSphere Application
Server for z/OS (Version 4 or later) in the system link
pack area or link list.
- 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 32-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.
"N" indicates 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 new managed node. 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 (temporary) cell configuration, a node configuration,
and a (temporary) location service daemon.
Note: The cell configuration
and location service daemon are temporary because they are replaced
shortly after creation when the new managed node is federated.
The
panels corresponding to the following tables set up the names, network
configuration, start procedures, and user IDs for the future node
agent and application servers.
- WebSphere Application Server home directory
- Directory in which the node's home directories will reside. See HFS configuration strategy for
more information.
Note: You can alter only the portion
after the configuration HFS mount point.
- Node Host Name
- IP address or host name of the system on which the node resides.
- Cell name (short)
- Name that identifies the cell to z/OS facilities
such as SAF. This name is used only until the managed node is federated
into the Network Deployment cell.
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. This name is used only
until the managed node is federated into the Network Deployment cell.
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 node to z/OS facilities
such as SAF. This name is NOT temporary, and will become the
short name of the managed node in the Network Deployment cell. Choose
a name that is unique in the Network Deployment cell.
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 node. This name identifies the node as
displayed through the administrative console. This name is NOT temporary,
and will become the short name of the managed node in the Network
Deployment cell. Choose a name that is unique in the Network Deployment
cell.
Rules:
- Name must be 50 or fewer characters and can be of mixed case.
- Name must be unique within the cell.
- Admin asynch operations procedure name
- Specifies the JCL procedure name of a started task that is launched
by way of the START command by node agents or application servers
to perform certain asynchronous administrative operations (such as
node synchronization) and add and remove a node.
See Cataloged procedures for
more information.
Server address space information
This section defines the cataloged procedures
and associated user IDs for the node agent created during federation.
You can also use these definitions for application servers created
in the node using the administrative console or scripting.
See Cataloged procedures for
more information.
Rule: In the following,
unless specified otherwise, names must be eight or fewer characters.
Controller
Information
- Procedure name
- Name of member in your procedure library to start the node agent.
It can also be used for application controllers in the node.
Rule: Name
must be seven or fewer characters.
- User ID
- The user ID associated with the node agent. It can also be used
as for application server controllers in the node.
- 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
- Procedure name
- Name of member in your procedure library to start the application
server servants in the node. This procedure is not used by the node
agent.
Rule: Name must be seven or fewer characters.
- User ID
- The user ID associated with the application servants in the node.
This user ID is not used by the node agent.
- 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.
Control Region Adjunct
- Procedure name
- Name of member in your procedure library to start application
server control region adjuncts in the node. This procedure is not
used by the node agent.
Rule: Name must be seven or fewer
characters.
- User ID
- The user ID associated with application server control region
adjuncts in the node. This user ID is not used by the node agent.
- 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.
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.
The location service daemon here is temporary and exists
only until the managed node is federated into the Network Deployment
cell.
- Daemon home directory
- Directory in which the location service daemon resides. This is
set to the configuration file system 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.
Caution: When
configuring a new managed node, ensure that this name is different
from the daemon jobname for the Network Deployment cell into which
you will federate the managed node.
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.
Federation variables
- WebSphere Application Server home directory
- The home directory that will be passed to the addnode.sh command
for federation. This is the same as the node home directory and cannot
be changed here.
- Node host name
- The TCP/IP node name of the deployment manager for the Network
Deployment cell.
- JMX SOAP port
- The JMX SOAP port of the deployment manager for the Network Deployment
cell.
- 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 the security domain administrator user ID
and cannot be changed.
- Node group name
- The node group into which the node will be placed. Specify DefaultNodeGroup
if the node is in the same sysplex as the deployment manager.
- Node agent server name (short)
- Name of the node agent server. This is the server's jobname, as
specified in the MVS START command JOBNAME parameter. This value
identifies the server to z/OS facilities such as SAF.
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.
- Node agent server name (long)
- Name of the node agent and the primary external identification
of the node agent server. This name identifies the server as displayed
through the administrative console . The node agent server long name
is set to the fixed value "nodeagent".
- JMX SOAP connector port
- Port number for the JMX HTTP connection to this server based on
the SOAP protocol. JMX is used for remote administrative functions
and is invoked through scripts such as wsadmin.sh.
Rule: Value
cannot be 0.
- Node Discovery port
- Defines the TCP/IP port to which the node agents listens for discovery
requests that originate from the deployment manager.
- Node Multicast Discovery port
- Defines the multicast port through which the node agent sends
discovery requests to its managed servers.
The multicast IP address
on which the discovery port is opened is defaulted by WebSphere Application
Server for z/OS to 232.133.104.73. This default address
can be changed using the administrative console. This is a CLASS D
address. The valid IP range is from 224.0.0.0 to 239.255.255.255.
- High Availability Manager Host
- Node agent 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.
- 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 the
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.
Web Server Configuration
Note: Web server configuration setup
was removed from managed node configuration in WebSphere Application
Server for z/OS Version 6.0.2. Create Web server definitions
for local or remote z/OS Web servers in a Network Deployment
cell using the deployment manager customization job BBODCFGW.
You
can configure your Web server using this panel.
- Web Server Name
- Name used to define the Web server in the administrative console.
- Host
- IP name or address of z/OS system on which Web server
resides.
- 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.