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.
----------------------------------------------- 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 'DATASET.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 'DATASET.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: BOSS.VICOM.W000170.SBBOLPA BOSS.VICOM.W000170.SBBOLOAD BOSS.VICOM.W000170.SBBOLD2 CEE.SCEERUN CEE.SCEERUN2 GSK.SGSKLOAD 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: a. Update the SYS or SUBSYS(STC,...) statement for started tasks to include the 120 record. b. (Optional) You can specify designated subtypes 1-6. 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 HFS: OMVS.WAS.CONFIG.HFS mounted at: /WebSphere/V6R0 in read/write mode. EXAMPLE: MOUNT FILESYSTEM('OMVS.WAS.CONFIG.HFS') MOUNTPOINT('/WebSphere/V6R0') TYPE(HFS) MODE(RDWR) ------------------------------------------------------------------- 6. Update TCP/IP by reserving the following ports for WebSphere for z/OS: SOAP JMX Connector port - 8880 ORB port - 2809 HTTP port - 9080 HTTP SSL port - 9443 High availability manager communication port - 9353 Service Integration port - 7276 Service Integration Secure port - 7286 Service Integration MQ Interoperability port - 5558 Service Integration MQ Interoperability Secure port - 5578 Daemon IP port - 5655 Daemon SSL port - 5656 View member BBOTCPIP in 'DATASET.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. ------------------------------------------------------------------- 7. The WebSphere product libraries will be placed in STEPLIB as needed, rather than in the system link pack area and system link list. SBBOLPA: ========= The following data set will be placed in the STEPLIB concatentation for the location service daemon. The data set's load modules will be loaded in the MVS™ common storage area when the location service daemon is started. Make sure the target MVS system has at least 8MB free storage in extended CSA before starting the daemon. BOSS.VICOM.W000170.SBBOLPA 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 HFS. You must not remove these STEPLIB statements. BOSS.VICOM.W000170.SBBOLOAD BOSS.VICOM.W000170.SBBOLD2 BBORTSS5: ========= The BBORTSS5 module is used by WebSphere Application Server V6 for component trace support. A copy of this module must be in the system link pack area in order for CTRACE to work correctly. If a copy of BBORTSS5 (any release) is currently loaded into LPA, you need take no further action. Otherwise, issue the following MVS console command to load BBORTSS5 into dynamic LPA: SETPROG LPA,ADD,MODNAME=BBORTSS5, DSNAME=BOSS.VICOM.W000170.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(BBORTSS5) DSNAME(BOSS.VICOM.W000170.SBBOLPA) Make sure that the BBORTSS5 module is loaded into LPA after each system IPL. ------------------------------------------------------------------- 8. Make sure the following Language Environment® data set is in the system link list: CEE.SCEERUN ------------------------------------------------------------------- 9. Make sure the following Language Environment data set is in the system link list: CEE.SCEERUN2 ------------------------------------------------------------------- 10. Make sure the following System SSL data set is in the system link pack area or the system link list on all MVS systems at or below z/OS Version 1.5: GSK.SGSKLOAD ------------------------------------------------------------------- 11. 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 DATASET.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. | +-----------+----------------------------------------------------------+ | BBOERRLG | User ID requirement: Authority to define a log stream. | +-----------+ | | Done: | ATTENTION: If your installation already has a WebSphere | | | for z/OS error log stream named the following, skip this | | | step. | | | | | | WAS.ERROR.LOG | | | | | | This job defines the error log stream. | | By: | | | | The customization dialog supplied the required | | | parameters on the define log stream command. Review and | | | supply any options you require. For more information, | | | see z/OS MVS Setting Up a Sysplex (SA22-7625). | | | | | | RESULT: Upon successful completion of this job, you will | | | see the following message in SYSPRINT: | | | | | | IXG004I LOGR POLICY PROCESSING ENDED WITHOUT ERROR | | | | +-----------+----------------------------------------------------------+ | BBOCBRAJ | User ID requirement: Authority to update data set | +-----------+ | | Done: | DATASET.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 BBOWBRAK of data set | | | | | | DATASET.DATA | | | | | | Carefully review these definitions with your security | | | administrator. | +-----------+----------------------------------------------------------+ | BBOCBRAK | 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 | | | BBOCBRAK. 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 | | | CEE.SCEERUN | | | | | | Make sure the following user IDs have read access to | | 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), | | | the application server Servant user id (ASSR1), and | | | the Service Daemon user ID (WSDMNCR1) need the ability | | | to perform operations on started tasks belonging to | | | WebSphere Application Server for z/OS in the same cell | | | (or security domain). | | | | | | The RACF commands to authorize these user IDs are not | | | generated by the previous job (BBOCBRAJ). The following | | | example commands show what needs to be done, | | | substituting your profile names: | | | | | | PERMIT START_profile_name CLASS(OPERCMDS) | | | ID (ASCR1 ASSR1 WSDMNCR1) | | | ACCESS(UPDATE) | | | | | | PERMIT STOP_profile_name CLASS(OPERCMDS) | | | ID (ASCR1 ASSR1 WSDMNCR1) | | | ACCESS(UPDATE) | | | | | | PERMIT MODIFY_profile_name CLASS(OPERCMDS) | | | ID (ASCR1 ASSR1 WSDMNCR1) | | | ACCESS(UPDATE) | | | | | | PERMIT CANCEL_profile_name CLASS(OPERCMDS) | | | ID (ASCR1 ASSR1 WSDMNCR1) | | | ACCESS(UPDATE) | | | | | | PERMIT FORCE_profile_name CLASS(OPERCMDS) | | | ID (ASCR1 ASSR1 WSDMNCR1) | | | ACCESS(UPDATE) | | | | +-----------+----------------------------------------------------------+ | BBOWCHFS | User ID requirement: UID=0 and authority to allocate | +-----------+ | | Done: | OMVS.WAS.CONFIG.HFS | | | | | | This job: | | | | | By: | o Creates a mount point directory | | | | | | /WebSphere/V6R0 | | | | | | o Allocates the configuration HFS | | | | | | OMVS.WAS.CONFIG.HFS | | | | | | and mounts it at the above mount point. | | | | | | BEFORE YOU BEGIN: The BBOWCHFS job assumes your root HFS | | | is mounted in read/write mode. If the root HFS is not in | | | read/write mode, manually create the directory | | | | | | /WebSphere/V6R0 | | | | | | and any needed higher directories, set file permissions | | | to 775, and set the owning user ID and group to WSADMIN | | | and WSCFG1 before running BBOWCHFS. | | | | | | EXAMPLE: If you plan to use /WebSphere/V6R0 as your | | | directory, issue the following commands from within the | | | OMVS shell: | | | | | | mkdir -p -m 775 /WebSphere/V6R0 | | | chown -R WSADMIN:WSCFG1 /WebSphere | | | | +-----------+----------------------------------------------------------+ | BBOWHFSA | User ID requirement: UID=0. | +-----------+ | | Done: | This job populates the previously-created HFS. | | | | | | Upon completion, examine the job output. Success is | | By: | indicated with a RC=0 in the job output. | | | | +-----------+----------------------------------------------------------+ | BBOWCPY1 | User ID requirement: update authority for: | +-----------+ | | Done: | | | | | | By: | SYS1.PARMLIB | | | | | | | | | 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. | | | | +-----------+----------------------------------------------------------+ | BBOWWPFA | User ID requirement: UID=0. | +-----------+ | | Done: | This job sets up the runtime HFS. | | | | | | | | By: | Upon completion, examine the job output. Success is | | | indicated by rc=0. | | | | +-----------+----------------------------------------------------------+ | BBOWHFSB | User ID requirement: UID=0. | +-----------+ | | Done: | This job will complete the HFS initialization. | | | | | | Upon completion, examine the job output. Success is | | By: | indicated with a RC=0 in the job output. | | | | +-----------+----------------------------------------------------------+ | BBOWCFGW | This job is OPTIONAL. | +-----------+ | | Done: | User ID requirement: UID=0. | | | | | | This job configures a Web server definition for a local | | | or remote z/OS Web server for your stand-alone | | | application server node. | | | | | | Upon completion, examine the job output. Success is | | By: | indicated with a RC=0 in the job output. | | | | +-----------+----------------------------------------------------------+ | -------- | 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 | +-----------+----------------------------------------------------------+ | -------- | Start the application server | +-----------+ | | Done: | Issue the MVS command | | | | | | START BBO6ACR,JOBNAME=BBOS001, | | | ENV=AQTS.AQTS.BBOS001 | | | | | By: | This command starts the application server. Wait until | | | the server is finished initializing before proceeding. | | | | | | RESULT: The following message appears on the console and | | | in the job log of | | | | | | BBOS001 | | | | | | BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR | | | z/OS CONTROL PROCESS BBOS001 | +-----------+----------------------------------------------------------+ | BBOWIVT | User ID requirement: UID=0 or WSADMIN | +-----------+ | | Done: | This job runs the IVT application. See related topics in | | | the WebSphere for z/OS Information Center at | | | http://www.ibm.com/software/webservers/appserv/zos_os390/| | | library/ | | | | | | for information about how to run this job. | | By: | | +-----------+----------------------------------------------------------+ | The product is now configured and verified. | | | | To start the application server, issue the MVS command: | | | | START BBO6ACR,JOBNAME=BBOS001, | | ENV=AQTS.AQTS.BBOS001 | | | | To stop the application server, enter the MVS command: | | | | STOP BBODMNB | +----------------------------------------------------------------------+
Use the following jobs to configure a database for the Scheduler component. These are optional if you do not plan to use the Scheduler. +-----------+----------------------------------------------------------+ | | On the z/OS machine that will host the database: | +-----------+ | | | - Log on to the native z/OS environment. | | Done: | - If multiple DB2® systems are installed, then decide | | | which subsystem you want to use. Note the subsystem. | | | - Using the DB2 administration menu, create a new | | | database (SCHEDDB, for example). Note the database | | By: | name | | | - Create a storage group (or use an existing one) and | | | note the name | | | - Decide which user ID will connect to the database | | | from the remote machine running the product. Normally,| | | for security reasons, this user ID is not the one you | | | used to create the database. | | | - Grant the user ID rights to access the database and | | | storage group. The user ID must also have permission | | | to create new tables for the database. | +-----------+----------------------------------------------------------+ | BBOCRTTS | User ID requirement: WSADMIN | +-----------+ | | Done: | This job creates the tablespaces in the Scheduler | | | database | | | | | | | | By: | | +-----------+----------------------------------------------------------+ | BBOCRTSC | User ID requirement: WSADMIN | +-----------+ | | Done: | This job creates the schema for the Scheduler | | | database. This job assumes that BBOCRTTS has already | | | been run to create the necessary tablespaces in the | | | Scheduler database | | By: | | +-----------+----------------------------------------------------------+ | BBODRPTS | User ID requirement: WSADMIN | +-----------+ | | Done: | This job drops the previously created Scheduler | | | tablespaces. This job is customized to drop tablespaces | | | which were created with the matching BBOCRTTS job | | | | | By: | | +-----------+----------------------------------------------------------+ | BBODRPSC | User ID requirement: WSADMIN | +-----------+ | | Done: | This job drops the previously created Scheduler | | | schema. This job is customized to drop the schema | | | which was created with the matching BBOCRTSC job | | | | | By: | | +-----------+----------------------------------------------------------+
The following is a useful script that helps you define security controls for clusters. It is in data set 'DATASET.DATA' +-----------+----------------------------------------------------------+ | BBOWBRAC | This is a sample exec you can modify to include | +-----------+ installation-specific RACF controls. This exec defines | | Done: | all the user IDs and groups that are necessary and | | | sufficient for installing WebSphere for z/OS. | | | | | By: | Additionally, there are commented sections for other | | | components that might be used (SSL, for example). | +-----------+----------------------------------------------------------+