Additional environment variables
Chapter 4. Installing and customizing DB2 GrouperGrouper
In this chapter we discuss the installation and configuration steps necessary in order to install the
server
component of DB2 Grouper. We assume that in our environment the SMP/E installation has been completed prior to beginning the installation work. The optionalGrouper Client
installation is discussed in Chapter 6, “Optionally defining DB2 Grouper Client” on page 65.This chapter contains the following:
Pre-installation activities
Installation steps for host: Details
Installation verification
4
4.1 Pre-installation activities
We review the Grouper Server installation materials to familiarize ourselves with any issues or areas of special concern.You might not need to perform these steps as part of your
installation. Probably your system programmer will do it for you.
4.1.1 Program Directory
Normally, the program directory is shipped as part of the installation package, along with the installation tapes. You can always download the most current version of the program directory from the IBM Data Management Tools Web site located at the URL:
http://www.software.ibm.com/db2/db2imstools
At the time of our residency, the publication number for the DB2 Grouper Program Directory, GI10-8569 was the publication number, yours may be different if a newer publication is made available after the redbook publication
Included in the program directory is information that helps you identify the second document that needs to be reviewed for installation planning: the Preventive Service Planning
document. This document is also sometimes referred to as the
PSP bucket
. In the program directory there is a section called “Preventive Service Planning” and it tells you how to identify the PSP.4.1.2 Preventive Service Planning
Using the UPGRADE and the SUBSET IDs documented in the program directory, you can download a current copy of the preventive service planning (PSP) using RETAIN, or by contacting the IBM Support Center and requesting a copy. For access to RETAIN, visit the URL:
http://www.ibmlink.ibm.com
Information normally found in the PSP includes items such as installation notes, changes to documentation, general information, and service recommendations including any high impact or pervasive APARs. As the information contained in the PSP is kept very current, it should be reviewed at the beginning of the installation process, as well as prior to migrating DB2 Grouper into your production environment.
Our PSP bucket was empty at the time we installed DB2 Grouper, so we had no additional action items documented through PSP. Example 4-1 shows the content of a typical PSP
DATE LAST
LIST--4.1.3 Review PTF cover letters
As part IBM’s standard software delivery mechanism, product fixes are packaged into a series of elements known as Program Temporary Fixes or PTFs. Each PTF includes a cover letter printed during the SMP/E receive process, which outlines any necessary action that is required in order to complete the application of the particular PTF. In our case, our system programmer had already reviewed all of the PTF cover letters and sent us a list of necessary action items. You should review your PTF cover letters and perform any documented action items.
4.1.4 Review and verify product prerequisites
The system requirements for running DB2 Grouper on z/OS are the same as those required for DB2 Data Archive Expert. Please refer to 3.1.4, “Review and verify product prerequisites”
on page 20 for a description of the specific instructions for this step. In addition, you are required to have PTF UQ73301 applied to DB2 UDB for z/OS and OS/390 Version 7. We used the SMP/E ISPF display dialog to verify that this particular fix was applied to our environment.
4.2 Installation steps for host: Details
We performed the product installation of DB2 Grouper using a RACF ID named PAOLOR2, which had SYSADM authority on the target DB2 subsystem.
4.2.1 Step 1. Installing Grouper metadata for z/OS
We modified the sample DDL in SEGFSAMP member EGFDDLC and created a separate DB2 storage group for the Grouper objects.
Member EGFFISH contains the DDL to create necessary views, and was executed without modification.
Create an SQL insert statement modified to include the USS directory where Grouper has been installed. Refer to Example 4-2 for a sample SQL statement.
Example 4-2 Sample SQL insert statement for Grouper metadata insert into SYSTOOLS.EGF_PROPERTIES
values ('EGFSERVERHOME', '/usr/lpp/egfv1r1')
The value for server-directory in the above referenced sample refers to the USS directory path that points to the Java Jar file created by the SMP/E installation. We used the UNIX System Services ISPF shell to locate this. Section 3.2.4, “Step 4. Java environment variable settings” on page 30 describes how we used the USS shell for the DB2 Data Archive Expert installation. We installed the DB2 Grouper Java components into the USS directory path:
Important: The DB2 Grouper product requires that the table qualifier be SYSTOOLS. Do not change this in the samplib member EGFDDLC.
Tip: In looking at the order of instructions as described in the DB2 Grouper User’s Guide, SC18-7409, it appears that you need to execute member EGFDDLD. Do not do this unless you really mean to because this member contains DDL to DROP the Grouper metadata and views.
/usr/lpp/egfv1r1
4.2.2 Step2. Defining Grouper Java stored procedures to DB2
Defining the stored procedure environment for Grouper was similar to the procedure we used to define the DB2 Data Archive Expert stored procedure. We refer to the process previously documented, but for additional information refer to the DB2 UDB for OS/390 and z/OS V7 Application Programming Guide and Reference for Java, SC26-9932.
Defining the WLM environment
We elected to create a separate WLM environment for Grouper. Using a process similar to the procedure documented in the previous chapter “Defining the WLM environment” on page 26, we defined our WLM environment as shown in Figure 4-1.
Figure 4-1 Grouper WLM environment definition