This article presents a sample of what the Customization Dialog's generated instructions might look like. This is a sample only--you must use the instructions generated from your own variables when configuring your system.
----------------------------------------------- Instructions for customizing WebSphere for z/OS for a Managed node. The customization dialog 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 for z/OS. RULES: 1. If you created the target data sets (*.CNTL and *.DATA) on another (driving) system, you must copy them to the target system and give them the same data set names. 2. You must perform these instructions on your target system. Doing manual configuration updates ---------------------------------- The customization dialog for WebSphere for z/OS does not attempt to update configuration data for your base operating system or existing subsystems. You must do the following manual steps prior to running the WebSphere for z/OS configuration jobs. Perform these steps to do manual configuration updates: 1. Update BLSCUSER. Refer to member BBOIPCSP in 'USERID.TODAY.CNTL' In order to use the IPCS support provided by the product, append the contents of this member to the BLSCUSER member in your IPCSPARM or system PARMLIB datasets. ------------------------------------------------------------------- 2. Update SCHEDxx. Refer to member BBOSCHED in 'USERID.TODAY.CNTL' In order to set the correct program properties for the WebSphere for z/OS run-time executables, append the contents of this member to the SCHEDxx member in your system PARMLIB concatenation. Note: When you are finished, issue the command SET SCH=(xx,xx) to activate SCHEDxx and load a new program properties table. ------------------------------------------------------------------- 3. Make sure the following data sets are APF-authorized: DBEL.WASX.SBBOLPA DBEL.WASX.SBBOLOAD DBEL.WASX.SBBGLOAD DBEL.WASX.SBBOLD2 Add these datasets to your PROGxx or IEAAPFxx parmlib members, as appropriate, ensuring you specify the correct volsers. ------------------------------------------------------------------- 4. If you want to collect the SMF120 records created by the run-time servers, update SMFPRMxx via the following: EXAMPLE: SUBSYS(STC,EXITS(IEFU29,IEFACTRT),INTERVAL(SMF,SYNC), TYPE(0,30,70:79,88,89,120,245)) --- For details on the SMF records, see related topics in the WebSphere for z/OS Information Center at http://www.ibm.com/software/webservers/appserv/zos_os390/library/ ------------------------------------------------------------------- 5. Update your active BPXPRMxx member to have the following WebSphere for z/OS configuration file system: OMVS.WAS.CONFIG.HFS mounted at: /WebSphere/V6R1 in read/write mode. EXAMPLE: MOUNT FILESYSTEM('OMVS.WAS.CONFIG.HFS') MOUNTPOINT('/WebSphere/V6R1') TYPE(HFS) MODE(RDWR) ------------------------------------------------------------------- 6. Update TCP/IP by reserving the following ports for WebSphere for z/OS. These will be used during the federation process of your managed node. SOAP JMX Connector port - 9360 Node Discovery port - 7272 Node Multicast Discovery Port - 5000 Node Agent's ORB port - 2809 High Availability Manager Communication port - 9354 View member BBOTCPIM in 'USERID.TODAY.CNTL' Add the contents of this member to the PORT section of the file referenced by the DD statement for the TCP/IP profile in the TCP/IP start procedure. Cut and paste from this member 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 update the WebSphere for z/OS customization dialog with new port specifications, be sure to regenerate the customization jobs, data, and instructions. Note: The addNode process introduces a special utility server to the node. This utility server is called a nodeagent and exists to support administrative functions on the node. By default the nodeagent takes over ORB port 2809. Note on WebSphere z/OS the ORB port doubles as the INS CosNaming bootstrap port. By default, this port (2809) was assigned to the Application Server. Normally you want the nodeagent to be the INS CosNaming bootstrap point for the entire node, so that RMI/IIOP clients that do not override the INS CosNaming bootstrap defaults can locate within the namespace, EJBs installed on any server on that node. In order for the nodeagent to take over port 2809, the Application Server must be assigned a new ORB port. The default new ORB port for the Application Server is 9810. The nodeagent will take over a Application Server's ORB port if and only if the nodeagent's ORB port is equal to an Application Server's ORB port. You can specify the nodeagent's ORB port in the 'ORB port' field. You can specify the new ORB port for the Application Server in the 'Appplication Server's ORB Port' field. ATTENTION: Skip this step if the ports are already defined in the TCP/IP profile. ------------------------------------------------------------------- 7. The WebSphere product libraries will be placed in STEPLIB as needed, rather than in the system link pack area and system link list. Make sure that the target MVS system has at least 8MB of free storage in extended CSA for the daemon and for EACH node (deployment manager node or application server node). SBBOLOAD and SBBOLD2: ==================== The following data sets will be placed in the STEPLIB concatenation for the location service daemon, controller and servant regions, and in the setupCmdLine.sh script in the WebSphere Configuration file system. You must not remove these STEPLIB statements. DBEL.WASX.SBBOLOAD DBEL.WASX.SBBOLD2 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, you need take no further action. Otherwise, issue the following MVS console command to load BBORTS61 into dynamic LPA: SETPROG LPA,ADD,MODNAME=BBORTS61, DSNAME=DBEL.WASX.SBBOLPA Alternatively, you can place the following statement in a parmlib PROGxx member which is activated with the SET PROG= command after system IPL is complete: LPA ADD MODNAME(BBORTS61) DSNAME(DBEL.WASX.SBBOLPA) Make sure that the BBORTS61 module is loaded into LPA after each system IPL. ------------------------------------------------------------------- 8. WebSphere for z/OS customization assumes that the following system data sets are in the system link list or link pack area: Language Environment® SCEERUN SCEERUN2 System SSL SGSKLOAD (z/OS 1.5 and below) SIEALNKE (z/OS 1.6 and above) Placing these data sets in the link list or link pack area improves performance and insulates your WebSphere 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 or link pack area, you must perform the following steps before starting any WebSphere Application Server for z/OS servers: - Make sure the data sets are APF-authorized - Complete the optional step below to add the data sets to STEPLIB in the server JCL and setupCmdLine.sh script(s). If you regenerate server cataloged procedures at any point, make sure the data sets are added to the new cataloged procedures. ------------------------------------------------------------------- 9. If the error logstream WAS.ERROR.LOG does not already exist on your target system, make a copy of the appropriate job in the SBBOJCL data set, customize it according to the comments in the job, and run it: BBOERRLC Create an error logstream in a coupling facility BBOERRLD Create a DASD-only error logstream ------------------------------------------------------------------- 10. WebSphere for z/OS regions open a large number of files (more than 1024). Make sure your BPXPRMxx parmlib member(s) specify a value of MAXFILEPROC that is greater than or equal to 2000. Use the following MVS console command to see your current MAXFILEPROC setting: D OMVS,OPTIONS Running the customized jobs --------------------------- The customization dialog built a number of batch jobs with the variables you supplied. You must run the jobs in the order listed below using user IDs with the appropriate authority. BEFORE YOU BEGIN: Complete the section above entitled "Doing manual configuration updates." Follow the table below, which lists in order the jobs you must submit and the commands you must enter. Special handling notes are included in the table. All jobs are members of USERID.TODAY.CNTL Attention: After submitting each job, carefully check the output. Errors may exist even when all return codes are zero. +-----------+----------------------------------------------------------+ | BBOMSGC | User ID requirement: Update authority for data set | +-----------+ SYS1.MSGENU and/or SYS1.MSGJPN. | | Done: | | | | ATTENTION: This is optional unless you require message | | | translation. | | By: | | | | This job sets up MMS to translate messages for WebSphere | | | for z/OS. | | | | | | There are two steps to update SYS1.MSGENU and | | | SYS1.MSGJPN. Remove the unneeded step and change the | | | target libraries, if necessary. | +-----------+----------------------------------------------------------+ | | Check WebSphere Application Server home directories. | +-----------+ | | Done: | Verify that the following directories exist on your | | | target z/OS system and that the ownership and permission | | | bits are correct: | | By: | | | | /var/WebSphere/home | | | ownership: (any) | | | permission bits: 755 | | | | | | /var/WebSphere/home/WSCFG1 | | | ownership: WSOWNER:WSCFG1 | | | permission bits: 770 | | | | | | | | | /var/WebSphere/home/WSSR1 | | | ownership: WSOWNER:WSSR1 | | | permission bits: 770 | | | | | | | | | /var/WebSphere/home/WSCLGP | | | ownership: WSOWNER:WSCLGP | | | permission bits: 770 | | | | | | If the these directories do not exist, create them with | | | the above ownership and permission bits. | | | | | | The security domain configuration job BBOSBRAM can be | | | used to create these directories if necessary. | | | | +-----------+----------------------------------------------------------+ | BBOMBRAJ | User ID requirement: Authority to update data set | +-----------+ | | Done: | USERID.TODAY.DATA | | | | | | This job builds (but does not execute) the RACF® commands | | By: | for the WebSphere for z/OS run-time clusters and places | | | them into member BBOMBRAK of data set | | | | | | USERID.TODAY.DATA | | | | | | Carefully review these definitions with your security | | | administrator. | +-----------+----------------------------------------------------------+ | BBOMBRAK | User ID requirement: RACF special authority. | +-----------+ | | Done: | This job executes the RACF commands set up in the | | | previous job. | | | | | | RESULT: You may receive errors, such as INVALID USER | | By: | 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 | | | BBOMBRAK. If not, then change the values in the | | | customization dialog which are causing the conflict, | | | regenerate the customization jobs, and restart the | | | process. | | | | +-----------+----------------------------------------------------------+ | -------- | Check user ID authorizations. | +-----------+ | | Done: | Make sure the WSCFG1 group has read access to all | | | WebSphere product data sets, as well as to any other | | | data sets which will be placed in WebSphere for z/OS | | | cataloged procedure STEPLIB concatenations. | | | | | By: | 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. | | | | | | ASCR1 | | | ASSR1 | | | | | | 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: | | | | | | WSDMNCR1 | | | | | | 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 Application Server Controller user ID (ASCR1) | | | needs 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: | | | | | | PERMIT START_profile_name CLASS(OPERCMDS) | | | ID (ASCR1 WSADMSH) ACCESS(UPDATE) | | | | | | PERMIT STOP_profile_name CLASS(OPERCMDS) | | | ID (ASCR1 ) ACCESS(UPDATE) | | | | | | PERMIT MODIFY_profile_name CLASS(OPERCMDS) | | | ID (ASCR1 ) ACCESS(UPDATE) | | | | | | PERMIT CANCEL_profile_name CLASS(OPERCMDS) | | | ID (ASCR1 ) ACCESS(UPDATE) | | | | | | PERMIT FORCE_profile_name CLASS(OPERCMDS) | | | ID (ASCR1 ) ACCESS(UPDATE) | | | | | | You must also grant the appropriate console command | | | authority to any user ID that executes the | | | startServer.sh or stopServer.sh script. | | | | +-----------+----------------------------------------------------------+ | BBOMCHFS | User ID requirement: UID=0 and authority to allocate | +-----------+ | | Done: | OMVS.WAS.CONFIG.HFS | | | | | | This job: | | | | | By: | o Creates a mount point directory | | | | | | /WebSphere/V6R1 | | | | | | o Allocates the configuration file system using | | | the Hierarchical File System (HFS) | | | | | | OMVS.WAS.CONFIG.HFS | | | | | | and mounts it at the above mount point. | | | | | | DO NOT RUN THIS JOB IF: | | | 1. The configuration file system already exists and is | | | mounted at the desired mountpoint, or if | | | | | | 2. The mount point directory is controlled by | | | automount. Either disable the automount rule for | | | the configuration mount point while running this | | | job, or perform the following steps manually: | | | | | | a. Allocate the configuration file system data set. | | | b. Issue the following shell commands, which will | | | also cause automount to mount the file system | | | | | | chmod 775 /WebSphere/V6R1 | | | chown WSOWNER:WSCFG1 /WebSphere/V6R1 | | | | | | | | | BEFORE YOU BEGIN: The BBOMCHFS job assumes your root | | | file system is mounted in read/write mode. If the root | | | file system is not mounted in read/write mode, manually | | | create the directory | | | | | | /WebSphere/V6R1 | | | | | | and any needed higher directories, set file permissions | | | to 775, and set the owning user ID and group to WSOWNER | | | and WSCFG1 before running BBOMCHFS. | | | | | | EXAMPLE: If you plan to use /WebSphere/V6R0M0 as your | | | directory, issue the following commands from within the | | | OMVS shell: | | | | | | mkdir -p -m 775 /WebSphere/V6R0M0 | | | chown -R WSOWNER:WSCFG1 /WebSphere | | | | +-----------+----------------------------------------------------------+ | BBOMHFSA | User ID requirement: UID=0. | +-----------+ | | Done: | This job populates the previously-created file system. | | | | | | Upon completion, examine the job output. Success is | | By: | indicated with a RC=0 in the job output. | | | | +-----------+----------------------------------------------------------+ | BBOWCPYM | User ID requirement: update authority for: | +-----------+ | | Done: | SYS1.PROCLIB | | | | | By: | | | | | | | | | | This job copies the tailored start procedures, | | | parameters, and EXECs to the run-time libraries. | | | | | | ATTENTION: Be aware that you may overlay existing | | | members in the above data sets. | | | | +-----------+----------------------------------------------------------+ | BBOWWPFM | User ID requirement: UID=0. | +-----------+ | | Done: | This job sets up the runtime file system. | | | | | | | | By: | Upon completion, examine the job output. Success is | | | indicated by rc=0. | | | | | | Note: If the BBOWWPFM (profile creation) job fails, | | | delete the WAS_HOME/profiles/default directory and all | | | its contents before rerunning BBOWWPFM. | | | | +-----------+----------------------------------------------------------+ | BBOMHFSB | User ID requirement: UID=0. | +-----------+ | | Done: | This job will complete the file system initialization. | | | | | | Upon completion, examine the job output. Success is | | By: | indicated with a RC=0 in the job output. | | | | +-----------+----------------------------------------------------------+ | -------- | All WebSphere Application Server processes require | +-----------+ access to the Language Environment and System SSL load | | Done: | modules. | | | | | | If the SCEERUN, SCEERUN2 and System SSL load module | | | libraries are not in the system link list or link pack | | | area, add them to the STEPLIB DD concatenation in each | | | of the following cataloged procedures in | | | SYS1.PROCLIB: | | | | | | BBO6ACRZ | | | BBO6ASRZ | | | BBO6CRAZ | | | BBO6DMNZ | | | | | | and also add the full data set names, separated by | | | colons (:), to the STEPLIB variable in the shell script | | | | | | /WebSphere/V6R1/ | | | AppServer/ | | | profiles/default/bin/setupCmdLine.sh | | By: | | | | When modifying the setupCmdLine.sh script, do not | | | remove lines or comment them out, as this may cause | | | problems with automated updates to the script. | | | | | | Add only those data sets which are NOT in the link list | | | or link pack area. | | | | +-----------+----------------------------------------------------------+ | -------- | Make sure Resource Recovery Services (RRS) is active. | +-----------+ (See the InfoCenter for setup instructions if necessary.)| | Done: | Look for the following console message to verify that | | | RRS was successfully started: | | | | | By: | | | | ASA2011I RRS INITIALIZATION COMPLETE. COMPONENT | | | ID=SCRRS | | | | +-----------+----------------------------------------------------------+ | BBOWMNAN | User ID requirement: WSADMIN | +-----------+ | | Done: | If you choose the start the node agent automatically, | | | the user ID used to run BBOWMNAN will also need the | | | authority to issue the MVS START command. | | | | | | This job will federate your node into the specified | | | Deployment Manager cell. Ensure that your Deployment | | | Manager is running before submitting this job | | | | | | Upon completion, examine the job output. Success is | | By: | indicated with a RC=0 in the job output. | | | | +-----------+----------------------------------------------------------+ | -------- | If your system is busy, you may want to include a rule | +-----------+ in your WLM policy that OMVS work for job BBON001 | | Done: | (such as the postinstaller step) is to run in a service | | | class with a high service objective. | | By: | | +----------------------------------------------------------------------+ | -------- | Start the node agent server | +-----------+ | | | Note: The node agent is automatically started by the node| | | federation process. This step is information, for | | | starting the node agent at other times. | | | | | | Issue the following MVS command to start your node agent | | | server, replacing dmgr_cell_short_name with the | | Done: | cell short name of the target Deployment Manager cell | | | | | By: | START BBO6ACR,JOBNAME=BBON001, | | | ENV=dmg_cell_short_name.AQFT.BBON001 | | | | | | RESULT: The following message appears on the console and | | | in the job log of BBON001. | | | BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR | | | z/OS CONTROL PROCESS BBON001 | | | | +-----------+----------------------------------------------------------+ +-----------+----------------------------------------------------------+ | The product is now configured. You may create and manage | | application servers in the node using the administrative console or | | scripting. | | | +----------------------------------------------------------------------+