IBM Tivoli Web Access for Information Management

14 IBM Tivoli Web Access for Information Management

2.3 Customizing your Information Management installation

The following steps assume that Information Management for z/OS Version 7.1 has been fully

installed using the steps in Chapter 1 of the

Tivoli Information Management for z/OS Planning

and Installation Guide and Reference, Version 7

.1, GC31-8751 (BLGP2E10). Many of the

steps here reference back to this guide and to the

Tivoli Information Management for z/OS

Operation and Maintenance Reference, Version 7.1

, SC31-8749 (BLGO1E10). You should

also have available Table 2-2 on page 12 that you completed at the beginning of this chapter.

httpd.conf Path and file name:____________________________________________________________

Configuration file used by the HTTP Server. The HTTP Server configuration file is specified in the -r

parameter on the ICSPARM parameter in your HTTP Server startup procedure. If the -r parameter is

not specified on ICSPARM, or if ICSPARM is not specified, the configuration file defaults to

/etc/httpd.conf. If you specify the -r parameter, but do not specify a fully qualified file name, the path

for the configuration file defaults to the /etc directory.

BLQPARMS Path and file name:____________________________________________________________

Web Access configuration file. Loaded into an HFS directory during the SMP/E install. Pointed to by

the INFOMANWEBTOOLKITCONF= keyword in the httpd.envvars file. The Web Access-supplied file

is BLQPARMS and is installed in the /usr/lpp/InfoMan/web/samples directory.

HTML Path:_______________________________________________________________________

Contains the HTML used by Web Access. Contains subdirectories js/, css/, and images/. The Web

Access installation directory is /usr/lpp/InfoMan/web/html.

REXX Path:_______________________________________________________________________

Contains the REXX programs used by Web Access. The Web Access installation directory is

/usr/lpp/InfoMan/web/rexx.

a. See Chapter 10, “Setting Up Your BLX-SP,” in

Tivoli Information Management for z/OS Planning and Installation

Guide and Reference, Version 7.1

, GC31-8751 (BLGP2E10).

b. Typically, there is one load library that contains the Information Management for z/OS code and one or more load

libraries that contain your code (such as program exits and session members). Include all the PDSs here and use

them whenever you are instructed to add SBLMMOD1 to the //STEPLIB, for example. Browse your BLX-PROC for

a STEPLIB. If it uses a STEPLIB, note each data set. If it does not have a STEPLIB, then SBLMMOD1 is in

LINKLIST.

c. It is possible that two different PDSs are used for the Information Management for z/OS and Web Access parts

during the SMP/E install. To see if a PDS is shared (recommended) by the two products, browse the PDS. Web

Access members begin with the letters BLQ, and Information Management for z/OS members with BLG and BLM

(also BLH and BTN, but BLG and BLM are the key prefixes). If you find BLQ members along with BLG or BLM mem-

bers, or both, in a PDS, the two products share the PDS. If the PDS does not contain both member prefixes, contact

your local SMP/E expert to obtain the PDS names used.

d. See Appendix D, '”Defining Tivoli Information Management for z/OS Session-Parameters Members,” in

Tivoli

In-

formation Management for z/OS Planning and Installation Guide and Reference, Version 7.1

, GC31-8751

(BLGP2E10).

e. You can put your data records (problem, change, and so on) and your data model records into the same data-

base. It is also possible to have your data model records in databases different from your data records. Putting all

the records into one database simplifies the installation of Web Access. Using different databases can make it eas-

ier to move your Web Access application from your development/test system to your production system. If your data

model records are not in the same database as your data records, your data session needs to refer to the MOD-

ELDB parameter (also see Footnote d).

Name Location and description