Building a practice WebSphere Application Server for z/OS cell

Use this task to practice configuring WebSphere Application Server for z/OS. If you are installing the product for the first time without migration from an earlier version, it is helpful to install a practice application serving environment in order to learn the customization process.

Before you begin

Note the following when you install your practice runtime:

About this task

You should install a practice runtime when you install WebSphere Application Server on z/OS for the first time and want to learn the steps for installing and customizing it.

Install using either the ISPF Customization Dialogs or the Profile Management tool.

Procedure

  1. Print a copy of the Customization tool worksheet: Common MVS Groups and Users and fill it out using Customization Dialog variables: Common MVS Groups and Users as a guide. When filling out the worksheet, use default values wherever possible.
    Note: Make sure that the user ID names, group names, and UID/GID values that you specify are not already being used on your z/OS system.
  2. Print a copy of the Customization tool worksheet: Stand-alone application server cell and fill it out using Customization variables: Stand-alone application server cell as a guide.
    Note: Make sure that the user ID names, group names, UID/GID values, and TCP/IP port numbers that you specify are not already being used on your z/OS system.
  3. Read the topic in Using the Customization Dialog.
  4. Read the topic in Using the Profile Management Tool.
  5. Follow the steps in Creating common MVS groups and users.
  6. Follow the steps in Creating a stand-alone application server cell. View and follow the generated instructions, which tell you how to:
    • Perform the manual configuration updates in the generated stand-alone application server instructions. These steps affect parts of your system that are usually controlled. These are changes that the systems programmer responsible for your z/OS system should review.
    • Create your log streams and data sets. The first four jobs (BBOMSGC - BBOWCTR) are straightforward system-programming tasks.
    • Update your server-specific security definitions. The next two jobs (BBOCBRAJ and BBOCBRAK) generate and then issue the RACF commands necessary for defining the users, groups, profiles, and permissions for the WebSphere Application Server for z/OS runtime servers.
    • Submit the BBOCBRAK job, or take it and the BBOCBRAJ job to your security administrator for approval. Your security administrator should issue those commands or submit the supplied jobstreams. If your installation has a different profile structure, you might have to modify the RACF commands generated by these execs to suit your particular needs.
      Note: Your installation must have "list of groups" on for these commands to work because the servers must be connected to the WebSphere Application Server for z/OS administrator group.
    • Create the configuration file system and WebSphere Application Server for z/OS home directory for your server. Jobs BBOWCHFS and BBOWHFSA (run at this point) and job BBOWWPFA (see below) run BPXBATCH shell scripts to define, customize, and load data into the configuration HFS and manipulate the ownership and permission attributes. For this reason, you must run these jobs under a user ID with UID=0.
    • Create cataloged procedures for the server and, optionally, for RRS and component trace.
    • Set up the runtime (configuration) file system for the new application server. The BBOWWPFA job might run for some time. The BBOWHFSB job cleans up the configuration file system and makes sure that all file ownerships are correct.
    • Start the new stand-alone application server, and run the Install Verification Test (IVT).
    Note:
    • If the BBOWWPFA (profile creation) job fails with the following error:
      Cannot use the directory: The /WebSphere/V6R1M0/AppServer/profiles/default directory exists and is not empty.
      INSTCONFFAILED: Cannot create profile: The profile does not exist.
      delete the WAS_HOME/profiles/default directory and all its contents before rerunning BBOWWPFA.
    • After you get the application server up and successfully run the IVT, you might want to change the built-in administrators defined for WebSphere Application Server for z/OS or at least change their passwords. If you do not want the user IDs assigned to started tasks used to sign on or submit jobs, make the user IDs protected by adding the keywords "NOPASSWORD" and "NOOIDCARD" to each user's RACF profile.
    • If you have some other security product such as Top Secret or ACF2 instead of RACF, contact your security system vendor for the appropriate security system commands needed to configure WebSphere Application Server for z/OS. You might need to contact the vendor for the latest maintenance and guidance on WebSphere Application Server for z/OS customization.
  7. Troubleshoot any problems you encounter while customizing your application server.

    If you encounter problems while customizing your application server, review the steps that you have performed--especially regarding such things as specific user IDs under which jobs must be run. Check all job output for any error messages that you might have missed. See Troubleshooting installation and configuration for additional advice.

    Watch out for these common mistakes:
    • Navigating the configuration file system with a UID of "0" can alter files or their ownership and permission attributes, making them inaccessible to the WebSphere Application Server for z/OS runtime servers and administrators. To avoid this problem, use the WebSphere Application Server for z/OS administrator user ID.
    • If you decide to change any of the customized variables after you submit any of these jobs, do not make manual modifications to the generated jobstreams or data. Cancel the installation, and start over by regenerating all the jobstreams and start over from the BBOWHFSA job.

Results

After you have successfully followed the instructions, you will have set up a WebSphere Application Server for z/OS stand-alone application server. See Working with your new server for more information.

What to do next

Read the concept articles under Planning for product configuration and plan one or more application serving environments that fit your system environment and business needs.

You might want to delete the practice application server that you just set up in order to save space on your system, to clean up your data sets, or for other reasons. Follow these steps to delete it from your system:
  1. Stop the server.
  2. Unmount and delete the configuration file system.
  3. Delete the cataloged procedures.
  4. Remove any TCP/IP port reservations for the practice application server.
  5. Delete the RACF user IDs, groups, and profiles that you have created unless you use the same security domain for a different WebSphere Application Server for z/OS cell.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 12:02:36 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-zos&topic=tins_practiceinstall
File name: tins_practiceinstall.html