z/OS basic naming convention

In WebSphere® Application Server for z/OS®, cells and nodes are created using customization jobs that are built using the Profile Management Tool or the zpmt command. When you use the Profile Management Tool to create these customization jobs, most fields are preset to default values. Fixed defaults are used that follow the basic naming convention if one- and two-character cell, cluster, and system identifier values are not specified during customization.

The basic naming convention is intended to assist you in gaining experience with WebSphere Application Server on z/OS, and it is suitable for small application environments consisting of a single application server or Network Deployment cell with one each of the other types of servers—administrative agent, job manager, and secure proxy server. If a Network Deployment cell is created, additional servers can be generated in the single application server node.

Default values for a standalone application server

By default, a standalone application server is build with cell short name BBOBASE, node short name BBONODE, and server short name BBOS001. The corresponding long names are cell name bbobase, node name bbonode, and server name server1. This illustrates the convention that the default long names are simply the lowercase forms of the corresponding short names, which only use uppercase letters, unless there is a traditional name such as server1 or proxy1 that is used instead. The server generic short name, which is used to identify the server to Workload Management, is BBOC001.

The default dataset name for the configuration file system is the following:
OMVS.WAS70.BBOBASE.BBONODE.HFS
(or .ZFS if a zFS file system is selected)
and it is mounted at the following location:
/wasv7config/bbobase/bbonode

This shows another feature of both the basic and standard naming conventions in WebSphere Application Server for z/OS Version 7.0. The cell and node short names are used to name the configuration file system and this file system's mount point is based on the cell and node long names. This convention helps to familiarize installers with the relevant names in each cell and makes it easy to remount file systems in the appropriate places.

Table 1. SAF groups and user IDs.

The following SAF groups and user IDs are created during customization:

WSCFG1 Configuration group

Provides administration and server privileges

WSSR1 Servant group

Provides privileges needed by servant regions

WSCLGP Unauthenticated, local user, or guest group

Provides basic privileges to access the cell but nothing more

WSCRU1 Controller user ID

Controller, control region adjunct, and daemon started tasks

WSSRU1 Servant user ID

Servant started tasks

WSADMIN Administrator user ID

Used for cell configuration and, in certain circumstances, as a WAS administrator

WSADMSH Asynchronous administration user ID

Used to run administrative shell scripts under a started task

WSGUEST Unauthenticated-user user ID (z/OS-managed security only)

Represents an unknown user for security purposes

Table 2. Job names and cataloged-procedure names.

The following job names and cataloged-procedure names are used for the various regions:

Job Name Cataloged-Procedure Name Region
BBOS001 BBO7ACR Controller
BBOS001A BBO7AAR Control region adjunct (handles messaging tasks for the controller)
BBOS001S BBO7ASR Servant region
BBODMNB BBO7DMNB Location service daemon
-------- BBO7ADM Asynchronous administrative cataloged procedure
Note that the cataloged-procedure names in the second column of this table provide the following: This pattern is used throughout the basic naming convention. The daemon job name and cataloged-procedure names follow their own pattern.

Default values for a deployment manager

To build a Network Deployment cell, you start with a deployment manager. To allow a standalone application server that is also built with the defaults to be federated into the Network Deployment cell, you must choose a new cell name and node name for the deployment manager.

By default, a deployment manager is built with cell short name BBOCELL, node short name BBODMGR, and server short name BBODMGR. The corresponding long names are cell name bbocell, node name bbodmgr, and server name dmgr. The deployment manager long name is fixed by the product architecture. The deployment manager can never be clustered; therefore, its default server generic short name, which is used to identify the deployment manager to Workload Management, is the same as the server short name: BBODMGR.

In versions of WebSphere Application Server for z/OS earlier than Version 7.0, the z/OS system name and sysplex name were used as cell names for the standalone application server and Network Deployment cell, respectively. This limited the old naming convention to a maximum of two cells for one z/OS system. In addition, there is no reason for a z/OS system name and its sysplex name to be different, causing a collision if the two values are used as names for different cells. In WebSphere Application Server for z/OS Version 7.0, fixed cell names are used to avoid these problems.

The default dataset name for the configuration file system is the following:
OMVS.WAS70.BBOCELL.BBODMGR.HFS
(or .ZFS if a zFS file system is selected)
and it is mounted at the following location:
/wasv7config/bbocell/bbodmgr

The SAF groups and user IDs created during customization have the same default names as for the standalone application server in order to make federation possible and minimize the number of security database entries that must be created. No Asynchronous administration user ID is created because a deployment manager does not need one.

Table 3. Job names and cataloged-procedure names.

The following job names and cataloged-procedure names are used for the various regions:

Job Name Cataloged-Procedure Name Region
BBODMGR BBO7DCR Controller
BBODMGRS BBO7DSR Servant region
BBODMNC BBO7DMNC Location service daemon
The cataloged-procedure names follow the same pattern as for the standalone application server. The D in the controller and servant procedure names indicates a deployment manager, and the C at the end of the location service daemon job name and cataloged-procedure name indicate an ND cell (as opposed to the B used for a base or standalone application server cell). The B and C in these names are values inherited from previous releases.

Default values for a managed node

When a managed (custom) node—an application server node with no servers that is intended for federation into a Network Deployment cell—is built, the name of the cell into which it will be federated is not actually specified. The managed node is created with a temporary cell name that must be different from the Network Deployment cell name. Therefore, the same defaults are used as those used for a standalone application server. Although this means that the configuration file system and mount point incorporate the temporary cell name, this can be corrected manually during customization if necessary.

The SAF groups, user IDS, and cataloged-procedure names are the same as those used for a standalone application server. However, an empty managed node does not have an application server; it only has a node agent (for node administration) until new servers are created in the node. The node agent has default server short name BBON001 and server long name nodeagent, which is fixed by the product architecture.

Default values for an administrative agent

An administrative agent controls one or more standalone application servers without requiring that they be federated into a Network Deployment cell.

By default, an administrative agent is built with cell short name BBOADMA, node short name BBOADMA, and server short name BBOADMA. The corresponding long names are cell name bboadma, node name bboadma, and server name adminagent, which is fixed by the product architecture. Like a deployment manager, the administrative agent can never be clustered; therefore, its default server generic short name, which is used to identify the administrative agent to Workload Management, is also set to BBOADMA.

The default dataset name for the configuration file system is the following:
OMVS.WAS70.BBOADMA.BBOADMA.HFS
(or .ZFS if a zFS file system is selected)
and it is mounted at the following location:
/wasv7config/bboadma/bboadma

The SAF groups and user IDs created during customization have the same default names as those used for the standalone application server in order to make it possible to register the standalone application server with the administrative agent.

The following job names and cataloged-procedure names are used for the various regions:
Table 4. Job names and cataloged-procedure names.

The following job names and cataloged-procedure names are used for the various regions:

Job Name Cataloged-Procedure Name Region
BBOADMA BBO7GCR Controller
BBOADMAS BBO7GSR Servant region
BBODMNG BBO7DMNG Location service daemon
The job names and cataloged-procedure names are similar to those used for the deployment manager, but they use G to indicate an administrative agent.
This makes the MVS start command for the administrative agent very simple:
START 
BBO7GCR,JOBNAME=BBOADMA,ENV=BBOADMA.BBOADMA.BBOADMA

Default values for a job manager

A job manager can control an administrative agent's registered application server nodes or a deployment manager and its managed and unmanaged nodes. In fact, it can manage several of each. On a system using the basic naming convention, you can register either the standalone application server (through its administrative agent) or a Network Deployment cell (through its deployment manager) with the job manager.

By default, a job manager is built with cell short name BBOJMGR, node short name BBOJMGR, and server short name BBOJMGR. The corresponding long names are cell name bbojmgr, node name bbojmgr, and server name jobmgr (which is fixed by the product architecture). Like a deployment manager, the administrative agent can never be clustered; therefore, its default server generic short name, which is used to identify the job manager to Workload Management, is also set to BBOJMGR.

The default dataset name for the configuration file system is the following:
OMVS.WAS70.BBOJMGR.BBOJMGR.HFS
(or .ZFS if a zFS file system is selected)
and it is mounted at the following location:
/wasv7config/bbojmgr/bbojmgr

The SAF groups and user IDs created during customization have the same default names used for the other server types.

The following job names and cataloged-procedure names are used for the various regions:
Table 5. Job names and cataloged-procedure names.

The following job names and cataloged-procedure names are used for the various regions:

Job Name Cataloged-Procedure Name Region
BBOJMGR BBO7JCR Controller
BBOJMGRS BBO7JSR Servant region
BBODMNJ BBO7DMNJ Location service daemon
The job names and cataloged-procedure names are similar to those used for the deployment manager, but they use J to indicate a job manager.

Default values for a secure proxy server

A secure proxy server is intended to run in the "demilitarized" zone (DMZ), across a firewall from the WebSphere Application Server cells for which it serves as a front end. Unlike a regular proxy server, it cannot be clustered; but it can be registered with an administrative agent to provide some remote administration capabilities.

By default, a secure proxy server is built with cell short name BBOPROX, node short name BBOPROX, and server short name BBOPROX. The corresponding long names are cell name bboprox, node name bboprox, and server name proxy1. The default server generic short name, which is used to identify the server to Workload Management, is BBOPROX.

The default dataset name for the configuration file system is the following:
OMVS.WAS70.BBOPROX.BBOPROX.HFS
(or .ZFS if a zFS file system is selected)
and it is mounted at the following location:
/wasv7config/bboprox/bboprox

The SAF groups and user IDs created during customization have the same default names used for the other server types.

The following job names and cataloged-procedure names are used for the various regions:
Table 6. Job names and cataloged-procedure names.

The following job names and cataloged-procedure names are used for the various regions:

Job Name Cataloged-Procedure Name Region
BBOPROX BBO7XCR Controller
BBOPROXS BBO7XSR Servant region
BBODMNX BBO7DMNX Location service daemon
The job names and cataloged-procedure names are similar to those used for the deployment manager, but they use X to indicate a secure proxy server.

Default values for a secure proxy administrative agent

A secure proxy server can be registered with an administrative agent to provide some remote administration capabilities.

By default, a secure proxy administrative agent is built with cell short name BBOPRXA, node short name BBOPRXA, and server short name BBOPRXA. The corresponding long names are cell name bboprxa, node name bboprxa, and server name adminagent. The default server generic short name, which is used to identify the administrative agent to Workload Management, is BBOPRXA.

The default dataset name for the configuration file system is the following:
OMVS.WAS70.BBOPRXA.BBOPRXA.HFS
(or .ZFS if a zFS file system is selected)
and it is mounted at the following location:
/wasv7config/bboprxa/bboprxa

The SAF groups and user IDs created during customization have the same default names used for the other server types.

The following job names and cataloged-procedure names are used for the various regions:
Table 7. Job names and cataloged-procedure names.

The following job names and cataloged-procedure names are used for the various regions:

Job Name Cataloged-Procedure Name Region
BBOPRXA BBO7YCR Controller
BBOPRXAS BBO7YSR Servant region
BBODMNY BBO7DMNY Location service daemon
The job names and cataloged-procedure names are similar to those used for the deployment manager, but they use Y to indicate a secure proxy administrative agent.
As with the regular administrative agent, the MVS start command is very simple:
START 
BBO7YCR,JOBNAME=BBOPRXA,ENV=BBOPRXA.BBOPRXA.BBOPRXA

Where to go next

The basic naming convention is adequate for an introduction to the WebSphere Application Server for z/OS product. However, most enterprises will want to create at least two application server nodes, whether for test and production or to allow for failover in a Network Deployment cell. For these configurations, you must use a more complex server naming convention.

The WebSphere Application Server for z/OS standard naming convention is a straightforward extension of the basic naming convention. The BBO and WS prefixes are replaced with a two-character cell identifier; this allows for several concurrent cells or groups of cells with similar administrative needs that sharing a common set of server user IDs. Cluster identifiers and a system identifier, which are specified during customization, provide additional flexibility. Read z/OS standard naming convention for more information.




Related concepts
z/OS application server naming conventions
z/OS standard naming convention
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 6, 2014 2:33:37 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-zos&topic=cins_plannambase
File name: cins_plannambase.html