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.
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.
OMVS.WAS80.BBOBASE.BBONODE.HFS (or .ZFS if a zFS file system is selected)and it is mounted at the following location:
/wasv8config/bbobase/bbonode
This shows another feature of both the basic and standard naming conventions in WebSphere Application Server for z/OS Version 8.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.
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 |
Job Name | Cataloged-Procedure Name | Region |
---|---|---|
BBOS001 | BBO8ACR | Controller |
BBOS001A | BBO8AAR | Control region adjunct (handles messaging tasks for the controller) |
BBOS001S | BBO8ASR | Servant region |
BBODMNB | BBO8DMNB | Location service daemon |
-------- | BBO8ADM | Asynchronous administrative cataloged procedure |
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 and later, fixed cell names are used to avoid these problems.
OMVS.WAS80.BBOCELL.BBODMGR.HFS (or .ZFS if a zFS file system is selected)and it is mounted at the following location:
/wasv8config/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.
Job Name | Cataloged-Procedure Name | Region |
---|---|---|
BBODMGR | BBO8DCR | Controller |
BBODMGRS | BBO8DSR | Servant region |
BBODMNC | BBO8DMNC | Location service daemon |
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.
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.
OMVS.WAS80.BBOADMA.BBOADMA.HFS (or .ZFS if a zFS file system is selected)and it is mounted at the following location:
/wasv8config/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.
Job Name | Cataloged-Procedure Name | Region |
---|---|---|
BBOADMA | BBO8GCR | Controller |
BBOADMAS | BBO8GSR | Servant region |
BBODMNG | BBO8DMNG | Location service daemon |
START BBO8GCR,JOBNAME=BBOADMA,ENV=BBOADMA.BBOADMA.BBOADMA
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.
OMVS.WAS80.BBOJMGR.BBOJMGR.HFS (or .ZFS if a zFS file system is selected)and it is mounted at the following location:
/wasv8config/bbojmgr/bbojmgr
The SAF groups and user IDs created during customization have the same default names used for the other server types.
Job Name | Cataloged-Procedure Name | Region |
---|---|---|
BBOJMGR | BBO8JCR | Controller |
BBOJMGRS | BBO8JSR | Servant region |
BBODMNJ | BBO8DMNJ | Location service daemon |
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.
OMVS.WAS80.BBOPROX.BBOPROX.HFS (or .ZFS if a zFS file system is selected)and it is mounted at the following location:
/wasv8config/bboprox/bboprox
The SAF groups and user IDs created during customization have the same default names used for the other server types.
Job Name | Cataloged-Procedure Name | Region |
---|---|---|
BBOPROX | BBO8XCR | Controller |
BBOPROXS | BBO8XSR | Servant region |
BBODMNX | BBO8DMNX | Location service daemon |
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.
OMVS.WAS80.BBOPRXA.BBOPRXA.HFS (or .ZFS if a zFS file system is selected)and it is mounted at the following location:
/wasv8config/bboprxa/bboprxa
The SAF groups and user IDs created during customization have the same default names used for the other server types.
Job Name | Cataloged-Procedure Name | Region |
---|---|---|
BBOPRXA | BBO8YCR | Controller |
BBOPRXAS | BBO8YSR | Servant region |
BBODMNY | BBO8DMNY | Location service daemon |
START BBO8YCR,JOBNAME=BBOPRXA,ENV=BBOPRXA.BBOPRXA.BBOPRXA
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.