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.
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.
Locations of file system resident
components
- 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
file system
This section defines the WebSphere configuration
file system that you will use for the new managed node. See
Configuration file system for
more information.
- Mount point
- Read/write file system 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
- 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.
- File system type (HFS or ZFS)
- This is the type of file system that will be used when creating
the WebSphere for z/OS configuration
file system. The default is HFS.
WebSphere error
log stream
This section defines the System Logger log stream
that you will use for WebSphere Application Server
for z/OS error logging if TRACEBUFFLOC=BUFFER. Having
the error log in the log stream is optional. By default, the error
log is written to JES SYSOUT.
- Name
- Name of the WebSphere error log stream you will create.
Rules:
- The name must be 26 or fewer characters.
- Do NOT put quotes around the name.
Ctrace Writer Definitions
WebSphere application Server for z/OS uses
component trace (CTRACE) to capture and to display trace data in trace
data sets. WebSphere Application Server for z/OS identifies
itself to CTRACE with the cell short name.
- Trace Parmlib member suffix
- Value that is appended to CTIBBO to form the member name for the
Trace parmlib member.
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 Configuration file system for
more information.
Note: You can alter only the portion
after the configuration file system 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.
Server address space information
This section defines the
cataloged procedures and associated user IDs for the node agent created
during federation.
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.
Note: Additional SAF definitions may
be required for you to start the server successfully.
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.
SSL customization
If you plan to enable Administrative
Security at some point, as is recommended, fill in the following SSL
values:
- Certificate Authority Keylabel
- The name of the key label that identifies the certificate authority
(CA) to be used in generating server certificates.
- Expiration date for CA authority
- The expiration date used for any X509 Certificate Authority certificates,
as well as the expiration date for the personal certificates generated
for WebSphere Application Server for z/OS servers.
You must specify this even if you selected "N" for "Generate Certificate
Authority (CA) certificate."
- Default RACF® keyring name
- The default name given to the RACF keyring
used by WebSphere Application Server for z/OS.
The keyring names created for repertoires are all the same within
a cell.
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 Administrative 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.
- Password
- Password for User ID.
- 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 communication port
- Port on which the High Availability Manager listens.
- ORB listener IP 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.
Security Customization
During
the initial setup, you can select one of the following three options
for administrative security. Choose the same security option as the
Network Deployment cell into which the Managed node will be federated.
- Option 1 - Use z/OS-managed security
- Use the z/OS system's SAF-compliant security database
to define WebSphere Application Server users. The
EJBROLE profile will be used to control role-based access to applications.
An administrator user ID and an unauthenticated user ID will be
created and defined in the security database. Select this option
if the WebSphere Application Server environment
will run entirely on z/OS with a shared SAF-compliant
(Local OS) user registry, or if you plan to implement an non-Local
OS user registry (such as LDAP) with mapping to SAF user IDs.
- Option 2 - Use WebSphere-managed security
- Use a simple file-based registry to define WebSphere Application
Server users. An administrator user ID will be created and defined
in the file-based registry.
- Option 3 - No security
- Do not enable administrative security (not recommended). Your WebSphere Application Server environment
will not be secured until you configure and enable security manually.
For the Managed node customization, there are no
additional security prompts.