This article lists definitions for the terms you will come across in the WebSphere Application Server for z/OS Customization Dialog.
Note: Some term definitions--those that you cannot set in the related panel--are not displayed. To see the definition, you must to go to the Information Center article for the panel on which you can change that particular term.
1 System locations (directories, HLQs, etc)
System Locations (1 of 2)
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 42 characters for the data set names.
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.
Specify the following Language Environment and WebSphere Application Server for z/OS data sets and whether they are ("Y") or are not ("N") in the link list or the link pack area (LPA). "N" indicates the generated JCL will contain STEPLIB statements for these data sets. Refer to your SMP/E installation for the location of these data sets listed by their DD Name.
Note: If you run multiple versions of WebSphere Application Server for z/OS on your system, specify "N" for each of the following in order to generate the proper //STEPLIB DD cards for all the appropriate jobs and procs.
In z/OS Version 1 Release 6, the contents of the System SSL data set SGSKLOAD were merged into the SIEALNKE system data set..
Select one of the following options.
Note: Do not modify setupCmdLine.sh except as directed by product documentation or by service personnel. In particular, do not move lines around or comment them out. This might cause problems with post-installer scripts that update setupCmdLine.sh and other files as needed. If you need to remove data set names from the STEPLIB variable, be sure to leave at least one STEPLIB= line in the OS/390 section: STEPLIB=$STEPLIB
Specify the following WebSphere Application Server for z/OS libraries so they can be accessed by the customized job streams the Dialog produces. These data sets must be cataloged.
System Locations (2 of 2)
Locations of HFS Resident Components:
2 System Environment Customization
System Environment Customization (1 of 1)
WebSphere HFS Information
Rule: You can specify up to 42 characters for the data set name.
Recommendation: The minimum suggested size is 250 cylinders (3390).
Recommendation: The minimum suggested size is 100 cylinders.
3 Server Customization
The WebSphere Application Server for z/OS runtime requires four base cell servers: Application Server, deployment manager, node agent, 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.
Recommendation: Use the IBM default names the first time you install WebSphere Application Server for z/OS to make the installation instructions easier to follow.
For identification, each controller and servant start procedure must have a user ID and will be defined in the STARTED class.
Servers are started by the MVS START command using the controller start procedure.
Server Customization (1 of 4)
Deployment Manager Definitions
Rule: In the following, unless specified otherwise, names must be 8 or fewer characters.
Note: You need to change the cell and node values so they properly apply to your deployment manager. They must be different from the values used for the base Application Server node.
Note: You can alter only the portion after "/WebSphere/V5R0M0."
Note: If WebSphere Application Server 5.0 is already installed and you are installing WebSphere Application Server 5.1, the cell short name should be unique.
Rules:
Note: This value, imported from the base Application Server node configuration, is a temporary value because the base Application Server node's cell goes away when the node is federated into the deployment manager's cell. So, you need to change the cell name to the one you want in the final configuration.
Rules:
Note: This value, imported from the base Application Server node configuration, is a temporary value because the base Application Server node's cell goes away when the node is federated into the deployment manager's cell. So, you need to change the cell name to the one you want in the final configuration.
Rules:
Note: Ensure that the node name is unique (different from those in other deployment manager or base server configurations).
Rules:
Rule: Name must usually contain 7 or fewer all-uppercase characters. If you wish to instead specify 8 characters, you must follow the steps outlined in the Information Center article "Converting a 7-character jobname to 8 characters."
Note: When you define a server, its server short name receives a default prefix of BBO* and a corresponding RACF BBO* profile is created. During installation, if you change the server short name to use a prefix other than BBO*, you must create your own non-default RACF profile using the non-default prefix. See RACF server class profiles for information on creating your own RACF profile and Understanding System Authorization Facility profile names generated by the Customization Dialog for information on how the Customization Dialog manages SAF profiles.
Rule: Name must be 60 or fewer characters and can be of mixed case.
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 8 or fewer characters and all uppercase.
Server Customization (2 of 4)
Rule: In the following, unless specified otherwise, names must be 8 or fewer characters.
Note: The RACF profiles you created during the construction of the base Application Server node will also work for the deployment manager. Also, the STARTED profiles are generic enough to cover any MVS jobname starting with AZ*.
Deployment Manager Definitions
Controller Information
Rule: Name must be 7 or fewer characters.
Note: If you are using a non-IBM security system, the user ID may have to match the procedure name. Please refer to your security system's documentation.
Rule: UIDs must be unique numbers, between 1 and 2,147,483,647, within the system.
Servant Information
Rule: Name must be 7 or fewer characters.
Note: If you are using a non-IBM security system, the user ID may have to match the procedure name. Please refer to your security system's documentation.
Rule: UIDs must be unique numbers, between 1 and 2,147,483,647, within the system.
Server Customization (3 of 4)
Deployment Manager Definitions
Rule: In the following, unless specified otherwise, names must be 8 or fewer characters.
Note: You must change all the port values from those used by the base Application 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 base 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.
Rule: Value cannot be 0.
Rule: Value cannot be 0.
Rule: Value cannot be 0.
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.
Rule: Value cannot be 0.
Rule: Value cannot be 0.
Server Customization (4 of 4)
Location Service Daemon Definitions
Rule: In the following, unless specified otherwise, names must be 8 or fewer characters.
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.
Note: This is also the name that will be used for all post-federation location service daemons on other MVS images. 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 job name value.
Caution: When configuring a second cell, ensure you change the daemon job name 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.
Rule: Name must be 7 or fewer characters.
Rule: UIDs must be unique numbers, between 1 and 2,147,483,647, within the system.
Adhere to the following regarding your location service daemon IP name:
Note: IBM recommends you use z/OS Sysplex Distributor via a "Dynamic Virtual IP address" (DVIPA). See related sections in the Information Center for more information.
Note: Select the IP name and port number for the location service daemon carefully. You can choose any name you want, but, once chosen, it is difficult to change, even in the middle of customization.
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.
4 View Security Domain Configuration Panels
This panel displays values you previously set in the "Configure security domain" option--you can not change any of the values here. If you do wish to make changes, you must go back to the main Dialog panel and run through the "Configure security domain" option again.