The Profile Management Tool has created jobs based on the information you
provided. These instructions tell you how to modify the operating
system and run the jobs to customize WebSphere Application Server for z/OS.
When you upload the customization jobs to the target system, a text version of
these instructions will be written to:
The Profile Management Tool does not attempt to update configuration data for your base operating system or existing subsystems. You need to perform the following manual steps prior to running the WebSphere for z/OS configuration jobs.
Status of task | Date |
---|---|
Status of task | Date |
---|---|
Add these datasets to your PROGxx or IEAAPFxx parmlib members, as
appropriate, ensuring you specify the correct volsers.
Note: You must add the actual data set names to your parmlib members and not any aliases you may have specified.
Status of task | Date |
---|---|
SUBSYS(STC,EXITS(IEFU29,IEFACTRT),INTERVAL(SMF,SYNC),TYPE(0,30,70:79,88,89,120,245))
Status of task | Date |
---|---|
Status of task | Date |
---|---|
Type | Number |
---|---|
SOAP JMX Connector port | ${zSoapPort} |
Cell Discovery Address port | ${zCellDiscoveryPort} |
ORB port | ${zOrbListenerPort} |
ORB SSL port | ${zOrbListenerSslPort} |
Administrative console port | ${zAdminConsolePort} |
Administrative console secure port | ${zAdminConsoleSecurePort} |
High Availability Manager Communications port | ${zHighAvailManagerPort} |
Type | Number |
---|---|
SOAP JMX Connector port | ${zNodeAgentJmxSoapConnectorPort} |
Node Discovery port | ${zNodeAgentNodeDiscoveryPort} |
Node Multicast Discovery Port | ${zNodeAgentNodeMulticastDiscoveryPort} |
Node IPv6 multicast discovery port | ${zNodeAgentNodeIPv6MulticastDiscoveryPort} |
ORB port | ${zNodeAgentOrbPortName} |
High Availability Manager Communication port | ${zNodeAgentHamCommPort} |
ORB SSL port | ${zNodeAgentOrbSslPortName} |
Type | Number |
---|---|
SOAP JMX Connector port | ${zAppServerSoapPort} |
ORB port | ${zAppServerOrbListenerPort} |
ORB SSL port | ${zAppServerOrbListenerSslPort} |
High availability manager communication port | ${zAppServerOrbListenerSslPort} |
Service Integration port | ${zAppServerServiceIntegrationPort} |
Service Integration Secure port | ${zAppServerServiceIntegrationSecurePort} |
Service Integration MQ Interoperability port | ${zAppServerServiceIntegrationMqPort} |
Service Integration MQ Interoperability Secure port | ${zAppServerServiceIntegrationSecureMqPort} |
Session Initiation Protocol (SIP) port | ${zAppServerSessionInitiationPort} |
Session Initiation Protocol (SIP) secure port | ${zAppServerSessionInitiationSecurePort} |
Type | Number |
---|---|
Daemon IP port | ${zDaemonPort} |
Daemon SSL port | ${zDaemonSslPort} |
Add the contents of the cntl/bbotcpim file within this customization definition to the PORT section of the file referenced by the DD statement for the TCP/IP profile in the TCP/IP start procedure. Copy and paste from this file into the data set used by your installation.
Attention: If another application has already reserved any of these ports for its own use, you must resolve the resulting conflict before you continue. If you use the Profile Management Tool to update the port specifications, be sure to upload the updated customization jobs.
Status of task | Date |
---|---|
Check that no other copies of WebSphere Application server, from any release, reside in the link pack area or the system link list. Also, check that the target MVS system has at least 40MB of free storage in the extended CSA if SBBOLOAD is placed in the link pack area, or 8MB of free storage in extended CSA for the daemon and for each node (deployment manager node or application server node), if SBBOLOAD is placed in the link list.
Alternatively, you can place the following statement in a parmlib PROGxx member which is activated with the SET PROG=xx command after system IPL is complete:
Check that sure that the SBBOLOAD modules are loaded into LPA after each system IPL.
Status of task | Date |
---|---|
${zBboloadName} ${zBbgloadName} ${zBbolod2Name}The following data sets will be placed in the STEPLIB concatenation for the application server controller, controller adjunct and servant regions, and in the setupCmdLine.sh script in the WebSphere Configuration file system for the application server. You must not remove these STEPLIB statements.
${zAppServerBboloadName} ${zAppServerBbgloadName} ${zAppServerBbolod2Name}
BBORTS61
The BBORTS61 module is used by WebSphere Application Server for component trace support. A copy of this module (any maintenance level) must be in the system link pack area in order for CTRACE to work correctly.
If a copy of BBORTS61 is currently loaded into LPA, no further action is required.
Otherwise, issue the following MVS console command to load BBORTS61 into dynamic LPA:
Alternatively, you can place the following statement in a parmlib PROGxx member, which is activated with the SET PROG=xx command after system IPL is complete:
Check that the BBORTS61 module is loaded into LPA after each system IPL.
Status of task | Date |
---|---|
See the Language Environment Customization manual and the System SSL Programming manual for your z/OS release for advice on placing members from the libraries into the system link pack area.
Placing these data sets in the link list insulates your WebSphere Application Server for z/OS configuration from changes in data set names (for example, when migrating to z/OS 1.6).
If the Language Environment or System SSL load module libraries are not in your system link list, you need to perform the following steps before starting any WebSphere Application Server for z/OS servers:
Status of task | Date |
---|---|
Status of task | Date |
---|---|
Status of task | Date |
---|---|
The Profile Management Tool built a number of batch jobs with the variables you supplied. You need to run the jobs in the order listed below, using user IDs with the appropriate authority.
If the UNIXPRIV profile CHOWN.UNRESTRICTED is defined, then the SUPERUSER.FILESYS.CHOWN is not required. For information about the UNIXPRIV class, see the z/OS Unix System Services Planning book.
Before you begin: Complete the section above entitled "Manual configuration updates".Type | Group/userid | GID/UID |
---|---|---|
Configuration group | ${zConfigurationGroup} | ${zConfigurationGroupGID} |
Servant group | ${zServantGroup} | ${zServantGroupGID} |
Local user group | ${zLocalUserGroup} | ${zLocalUserGroupGID} |
File system owner user ID | ${zHFSOwnerUserID} | ${zHFSOwnerUID} |
Carefully review these definitions with your security administrator.
Status of task | Date |
---|---|
This job executes the RACF commands created by the previous job. If the group and user IDs named above have already been created during a previous WebSphere Application Server for z/OS configuration and are in all target system RACF databases, you do not need to rerun this job.
Result: You may receive errors, such as INVALID USER messages, from this job because a user ID, group or profile is already defined. Make sure the existing user ID, group, or profile has the same characteristics as the user ID, group, or profile being created by BBOSBRAK. If not, then change the values in the Profile Management Tool, which are causing the conflict. Then upload the updated customization jobs and restart the process.
When this step is complete, all groups and user IDs
listed above for job BBOSBRAJ should be defined in the
RACF database on each target system for the cell.
Note: The WebSphere Application Server owner user ID
${zHFSOwnerUserID} must have the WebSphere Application Server
configuration group ${zConfigurationGroup} as its
default OMVS group.
Status of task | Date |
---|---|
User ID requirement: File system update authority (see above).
This job creates home directories for WebSphere Application Server for z/OS user IDS. These home directories will be subdirectories of ${zUserIDHomeDirectory}
This job will create the following directories:${zUserIDHomeDirectory} ownership: (any) permission bits: 755 ${zUserIDHomeDirectory}/${zConfigurationGroup} ownership: ${zHFSOwnerUserID}:${zConfigurationGroup} permission bits: 770 ${zUserIDHomeDirectory}/${zServantGroup} ownership: ${zHFSOwnerUserID}:${zServantGroup} permission bits: 770 ${zUserIDHomeDirectory}/${zLocalUserGroup} ownership: ${zHFSOwnerUserID}:${zLocalUserGroup} permission bits: 770
This job should be run on each z/OS system that will host WebSphere Application Server nodes using these WebSphere Application Server for z/OS common groups and owner user ID. After execution, verify that the directories have been created with the correct permissions on each system.
If these directories already exist with the specified ownership and permission on a target system, then this job does not need to be run on that system.
Attention: If the directory ${zUserIDHomeDirectory} is used by applications other than WebSphere Application Server, make sure that the permissions set by BBOSBRAM (755) are appropriate, or change them manually. This directory must be world-readable for Websphere Application Server to run correctly.
Status of task | Date |
---|---|
Status of task | Date |
---|---|
Status of task | Date |
---|---|
Status of task | Date |
---|---|
Status of task | Date |
---|---|
Status of task | Date |
---|---|
Make sure the ${zConfigurationGroup} group has read access to all WebSphere product data sets, as well as to any other data sets which will be placed in WebSphere Application Server for z/OS cataloged procedure STEPLIB concatenations.
Make sure the following user IDs have read access to
the resolver configuration file in use on your system.
Depending on your IP setup, this file may be
/etc/resolv.conf, SYS1.TCPPARMS(TCPDATA), or another
data set.
See the z/OS eNetwork Communication Server IP Configuration manual for the resolver search order.
Ensure the following user ID has read access to the data
sets in your system parmlib concatenation:
Attention: If operator commands are protected by the z/OS security server at your installation, you must ensure that sufficient authority is given to WebSphere tasks to control operations.
The Deployment Manager and Application Server controller user IDs (${zControlUserid} and ${zAppServerControlUserid}) need the ability to perform operations on started tasks belonging to WebSphere Application Server for z/OS.
The asynchronous administrator user ID, and any user ID used to run the federation job when the node agent is started automatically, need the authority to issue the MVS START command.
If you are currently controlling MVS console command
authority with SAF OPERCMDS profiles, grant the
following authorities as indicated, substituting your
own profile names:
You need to also grant the appropriate console command authority to any user ID that executes the startServer.sh or stopServer.sh script.
Status of task | Date |
---|---|
Creates the following mount point directories
Allocates the following configuration file system(s) using the Hierarchical File System (HFS)
${zConfigHfsName} ${zAppServerConfigHfsName}
Allocates the following configuration file system(s) using the z/OS Distributed File Service zSeries File System (zFS)
${zConfigHfsName} ${zAppServerConfigHfsName}
Allocates the following configuration file system(s) using the Hierarchical File System (HFS) ${zAppServerConfigHfsName}
Allocates the following configuration file system(s)
using the z/OS Distributed File Service zSeries File
System (zFS)
${zAppServerConfigHfsName}
and mounts them at the above mount points.
Status of task | Date |
---|---|
Status of task | Date |
---|---|
Status of task | Date |
---|---|
cd ${zConfigMountPoint}/${zWasServerDir} ./bin/bbowprof.sh -deleteAll rm profileRegistry.xml rm -R profiles cd ${zAppServerConfigMountPoint}/${zAppServerWasServerDir} ./bin/bbowprof.sh -deleteAll rm profileRegistry.xml rm -R profilesThen correct the problem that caused BBOWWPFC to fail and re-run the job.
Status of task | Date |
---|---|
Status of task | Date |
---|---|
${zConfigMountPoint}/${zWasServerDir}/profiles/default/bin/setupCmdLine.sh ${zAppServerConfigMountPoint}/${zAppServerWasServerDir}/profiles/default/bin/setupCmdLine.shWhen modifying the setupCmdLine.sh script, do not remove lines or comment them out, as this may cause problems with automated updates to the script.
Status of task | Date |
---|---|
Status of task | Date |
---|---|
If you later convert the Deployment Manager to 64-bit
mode, you need to add AMODE=64 to the START command:
Status of task | Date |
---|---|
If you later convert the node agent to 64-bit mode, you need to add
AMODE=64 to the START command:
Status of task | Date |
---|---|
If you later convert the Application Server to 64-bit
mode, you need to add AMODE=64 to the START command:
Status of task | Date |
---|---|