This article gives an overview of the contents of the Customization Dialog instruction file for this option. You need to follow the actual file in the Dialog to configure your system.
The major stages of the Application Server node customization process are:
Stage | Description |
---|---|
1 | Make a variety of configuration changes to your z/OS system configuration (PARMLIB, TCP/IP, workload management, and so forth). The customized instructions provide details and pointers to relevant documentation. |
2 | If
you require message translation, set up MMS to translate messages for WebSphere
Application Server for z/OS with job BBOMSGC. Note: If you are not using NLS (National Language Support), you can skip this job. |
3 | Define log streams used by WebSphere Application Server for z/OS and RRS through jobs BBOERRLG and BBORRSLS. You do not need to run BBORRSLS if RRS is already running on your target MVS system. |
4 | Allocate the CTRACE data set through job BBOWCTR. |
5 | Create a customized set of RACF commands for initial WebSphere Application Server for z/OS security setup through job BBOCBRAJ. The RACF commands are saved in member BBOWBRAK of the hlq. DATA data set. Job BBOWBRAK executes these RACF commands. Later, you can use the RACF commands saved in BBOWBRAK to help in defining security for additional servers or users. |
6 | Check the authorization level of all your user IDs and modify them where necessary. |
7 | Allocate and mount the WebSphere Application Server for z/OS runtime HFS through job BBOWCHFS. If your root HFS is mounted read-only, you may need to create one or more directories manually. See the instructions for details. If your runtime HFS is automounted, automount should be disabled before running BBOWCHFS. Job BBOMCFG creates subdirectories in the WebSphere Application Server for z/OS runtime HFS. |
8 | Copy customized PARMLIB and PROCLIB members into their proper locations using job BBOWCPY1. |
9 | Copy customized HFS files into their proper locations using job BBOWCPY2. |
10 | Create the was.env file for the location service daemon and the Application Servers through job BBOWC2N. |
11 | Install the administrative console and the IVT application through job BBOWIAPP. |
12 | (Optional) Copy digital certificates from RACF to the keystores in the HFS with job BBOCR2FA. |
13 | Complete the HFS initialization with job BBOMCFG2. |
14 | Activate Resource Recovery Services (RRS), if it is not already active, with the MVS command START ATRRRS,SUB=MSTR. |
15 | Start the CTRACE writer used by WebSphere Application Server for z/OS with the MVS command TRACE CT,WTRSTART= BBOWTR. |
16 | Start
the Application Server with the following MVS command: S <controller_procname,JOBNAME=server_shortname, ENV=<cell_shortname.node_shortname.server_shortname This process causes information to be stored in the HFS. Once the process is complete, you have a working WebSphere Application Server for z/OS runtime that you will use to run the Installation Verification Test (using job BBOWIVT) and your own applications. |
17 | For reference purposes only, configure samples with jobs BBODEFR, BBOINST, and BBOUNIN. Ensure you reset all sample EAR files to their original state and delete the samples when you are finished with them. |
18 | Use the BBOWBRAC sample exec to help define security controls for clusters. It defines all the user IDs and groups that are necessary and sufficient for installing WebSphere Application Server for z/OS, among other things. |