This topic applies only on the z/OS operating system.

Sample generated instructions: Network Deployment cell

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.

Note: This sample is based on the installation of WebSphere® Application Server for z/OS® Version 6.0.2. Generated instructions from different releases of Version 6 would have different content.

Instructions for customizing WebSphere for z/OS for a Deployment Manager node for 6.0.2.

-----------------------------------------------                                 
                                                  
                                                                                
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 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)                                                            
                                                                                
    -------------------------------------------------------------------         
                                                                                
2.  Update TCP/IP by reserving the following ports for WebSphere for            
    z/OS:                                                                       
                                                                                
       SOAP JMX Connector port                       - 8879                     
       CELL DISCOVERY ADDRESS port                   - 7277                     
       ORB port                                      - 9809                     
       HTTP port                                     - 9060                     
       HTTP SSL port                                 - 9043                     
                                                                                
       High Availability Manager Communications port - 9352                     
                                                                                
       Daemon IP port                                - 5755                     
       Daemon SSL port                               - 5756                     
                                                                                
    View member BBOTCPID 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 instuctions.                   
                                                                                
    -------------------------------------------------------------------         
                                                                                
3.  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.                                                                 
                                                                                
    -------------------------------------------------------------------         
                                                                                
4.  Make sure the following Language Environment® data set is in the             
    system link list:                                                           
                                                                                
    CEE.SCEERUN                                                                 
                                                                                
    -------------------------------------------------------------------         
                                                                                
5.  Make sure the following Language Environment data set is in the             
    system linklist:                                                            
                                                                                
    CEE.SCEERUN2                                                                
                                                                                
    -------------------------------------------------------------------         
                                                                                
6.  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                                                                
                                                                                
    -------------------------------------------------------------------         
                                                                                
7.  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                                                            
                                                                                
    -------------------------------------------------------------------         
                                                                                
8.  Grant WSDMNCR1 read access to                                               
    SYS1.PARMLIB                                                                
    and any other parmlibs that precede                                         
    SYS1.PARMLIB                                                                
    in the parmlib concatenation of the LOADzz member in IPLPARM. Use           
    the D IPLINFO command to determine which LOADzz member is current           
    and where it resides.                                                       
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.                           
                                                                                
+-----------+----------------------------------------------------------+        
| BBODBRAJ  | User ID requirement: Authority to update data set        |        
+-----------+                                                          |        
| Done:     | DATASET.DATA                                             |        
|           |                                                          |        
|           | This job builds (but does not execute) the RACF® commands|        
|           | for the WebSphere for z/OS run-time clusters and places|        
| By:       | them into member BBODBRAK of data set                    |        
|           |                                                          |        
|           | DATASET.DATA                                             |        
|           |                                                          |        
|           | Carefully review these definitions with your security    |        
|           | administrator.                                           |        
+-----------+----------------------------------------------------------+        
| BBODBRAK  | 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     |        
|           | 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.                                                 |        
|           |                                                          |        
| By:       |                                                          |        
|           | 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 Location Service Daemon user ID, |        
|           |  (WSDMNCR1), the Deployment Manager Controller user      |        
|           |  ID (DMCR1), and the Deployment Manager Servant user     |        
|           |  ID (DMSR1) 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 (BBODBRAJ). The following |        
|           |  example commands show what needs to be done,            |        
|           |  substituting your profile names:                        |        
|           |                                                          |        
|           |  PERMIT  START_profile_name CLASS(OPERCMDS)              |        
|           |          ID(WSDMNCR1 DMCR1 DMSR1)                        |        
|           |          ACC(UPDATE)                                     |        
|           |                                                          |        
|           |  PERMIT  STOP_profile_name CLASS(OPERCMDS)               |        
|           |          ID(WSDMNCR1 DMCR1 DMSR1)                        |        
|           |          ACC(UPDATE)                                     |        
|           |                                                          |        
|           |  PERMIT  MODIFY_profile_name CLASS(OPERCMDS)             |        
|           |          ID(WSDMNCR1 DMCR1 DMSR1)                        |        
|           |          ACC(UPDATE)                                     |        
|           |                                                          |        
|           |  PERMIT  CANCEL_profile_name CLASS(OPERCMDS)             |        
|           |          ID(WSDMNCR1 DMCR1 DMSR1)                        |        
|           |          ACC(UPDATE)                                     |        
|           |                                                          |        
|           |  PERMIT  FORCE_profile_name CLASS(OPERCMDS)              |        
|           |          ID(WSDMNCR1 DMCR1 DMSR1)                        |        
|           |          ACC(UPDATE)                                     |        
|           |                                                          |        
+-----------+----------------------------------------------------------+        
| BBODCHFS  | User ID requirement: UID=0 and authority to allocate     |        
+-----------+                                                          |        
| Done:     | OMVS.WAS.CONFIG.HFS                                      |        
|           |                                                          |        
|           | ATTENTION: Skip this step if the mount point is already  |        
|           | created, such as for the stand-alone application server  |        
|           |                                                          |        
| By:       | This job:                                                |        
|           |                                                          |        
|           | 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 BBODCHFS 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 BBODCHFS.                      |        
|           |                                                          |        
|           | 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                     |        
|           |                                                          |        
+-----------+----------------------------------------------------------+        
| BBODHFSA  | 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.                 |        
|           |                                                          |        
+-----------+----------------------------------------------------------+        
| BBODCPY1  | User ID requirement: update authority for:               |        
+-----------+                                                          |        
| Done:     |                                                          |        
|           |                                                          |        
|           |     SYS1.PROCLIB                                         |        
| By:       |                                                          |        
|           |                                                          |        
|           | This job copies the tailored start procedures,           |        
|           | parameters, and EXECs to the run-time product libraries  |        
|           |                                                          |        
|           | ATTENTION: Be aware that you may overlay existing        |        
|           | members in the above data set.                           |        
|           |                                                          |        
+-----------+----------------------------------------------------------+        
| BBOWWPFD  | 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.                                       |        
|           |                                                          |        
+-----------+----------------------------------------------------------+        
| BBODHFSB  | 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.                 |        
|           |                                                          |        
+-----------+----------------------------------------------------------+        
| BBODPROX  | This job is OPTIONAL.                                    |        
+-----------+                                                          |        
|           | User ID requirement: UID=0.                              |        
| Done:     |                                                          |        
|           | You answered NO to 'Allow ability to administer Proxy    |        
|           | Server(s)'                                               |        
|           |                                                          |        
|           | This job will add the ability to administer Proxy        |        
|           | Servers to your Deployment Manager                       |        
|           |                                                          |        
| By:       | Upon completion, examine the job output. Success is      |        
|           | indicated with a RC=0 in the job output.                 |        
|           |                                                          |        
+-----------+----------------------------------------------------------+        
| --------  | Start the Deployment Manager.                            |        
+-----------+                                                          |        
| Done:     | Issue the MVS command                                   |        
|           |                                                          |        
|           |   START BBO6DCR,JOBNAME=BBODMGR,                         |        
|           |         ENV=MCLXCF01.MCLXCF01.BBODMGR                    |        
|           |                                                          |        
| By:       | This command starts the Deployment Manager and also      |        
|           | starts the location service daemon. Wait until the       |        
|           | server is finished initializing before proceeding.       |        
|           |                                                          |        
|           | RESULT: The following message appears on the console and |        
|           | in the job log of BBODMGR                                |        
|           |                                                          |        
|           |   BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR    |        
|           |     z/OS CONTROL PROCESS BBODMGR                        |        
|           |                                                          |        
+-----------+----------------------------------------------------------+        
| BBODCFGW  | This job is OPTIONAL.                                    |        
+-----------+                                                          |        
|           | User ID requirement: UID=0.                              |        
| Done:     |                                                          |        
|           | Ensure that your Deployment Manager is running before    |        
|           | submitting this job.                                     |        
|           |                                                          |        
|           | This job configures a plug-in for a local or remote z/OS|        
|           | Web server for your Network Deployment cell              |        
|           |                                                          |        
|           | Upon completion, examine the job output. Success is      |        
| By:       | indicated with a RC=0 in the job output.                 |        
|           |                                                          |        
+-----------+----------------------------------------------------------+        
|                                                                      |        
| The product is now configured for a Deployment Manager.              |        
|                                                                      |        
+-----------+----------------------------------------------------------+        
Note: If you want to federate a managed node or stand-alone Application         
Server node, you will need to run option 2 or 3 of the dialog,                  
respectively.                                                                   
                                                                                
+-----------+----------------------------------------------------------+        
| To start the Deployment Manager, issue the following MVS command:   |        
|                                                                      |        
|   START BBO6DCR,JOBNAME=BBODMGR,                                     |        
|         ENV=MCLXCF01.MCLXCF01.BBODMGR                                |        
|                                                                      |        
| To stop the WebSphere for z/OS servers, enter the MVS command:   |        
|                                                                      |        
|   STOP BBODMNC                                                       |        
|                                                                      |        
+----------------------------------------------------------------------+        
                                                                                
The following is a useful script that helps you define security                 
controls. It is in data set                                                     
                                                                                
'DATASET.DATA'                                                                  
                                                                                
+-----------+----------------------------------------------------------+        
| BBODBRAC  | This is a sample exec that you may 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).        |        
+-----------+----------------------------------------------------------+        



Related reference
Related information
Following the generated customization instructions: Network Deployment cell
Reference topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 8:25:23 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=rins_dialogsteps_sampinst3
File name: rins_dialogsteps_sampinst3.html