Prepare OS/390 for WebSphere Enterprise EditionPrepare OS/390 for WebSphere Enterprise Edition...

ibm.com/redbooks

Prepare OS/390 for WebSphereEnterprise Edition

Roland TraunerIriani Ratna

Eva Yan

Infrastructure for WebSphere Enterprise Edition

Configure DB2, RRS, System Logger, ARM, LDAP and more

General CB installation hints

http://www.redbooks.ibm.com/


Prepare OS/390for WebSphereEnterprise Edition

February 2001

SG24-5685-00

International Technical Support Organization

© Copyright International Business Machines Corporation 2001. All rights reserved.Note to U.S Government Users – Documentation related to restricted rights – Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

First Edition (February 2001)

This edition applies to IBM WebSphere Application Server 3.02 Enterprise Edition for OS/390 for use with the OS/390 R10

Comments may be addressed to:IBM Corporation, International Technical Support OrganizationDept. HYJ Mail Station P0992455 South RoadPoughkeepsie, NY 12601-5400

When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.

Before using this information and the product it supports, be sure to read the general information in Appendix C, “Special notices” on page 103.

Take Note!

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiThe team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1. Overview of software requirements . . . . . . . . . . . . . . . . . . . 1

Chapter 2. Setting up a monoplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1 Format a Sysplex couple data set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2 Update SYS1.PARMLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.3 IPL the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.4 Useful commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 3. Workload management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.1 OS/390 performance control interface . . . . . . . . . . . . . . . . . . . . . . . . . 73.2 Preparing the WLM environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.2.1 Using the WLM ISPF application . . . . . . . . . . . . . . . . . . . . . . . . . 83.2.2 Making a WLM couple data set available . . . . . . . . . . . . . . . . . . . 83.2.3 Service definition implementation . . . . . . . . . . . . . . . . . . . . . . . . 103.2.4 Switch into goal mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.3 Setting up workload management for Component Broker . . . . . . . . . . 333.4 Useful commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 4. System Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.1 Setting up System Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.2 Setting up for Component Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.3 Useful commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 5. Resource Recovery Services . . . . . . . . . . . . . . . . . . . . . . . 395.1 Define RRS log streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395.2 Running RRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 6. Automatic Restart Manager . . . . . . . . . . . . . . . . . . . . . . . . 416.1 Formatting an ARM couple data set . . . . . . . . . . . . . . . . . . . . . . . . . . 416.2 Starting the ARM policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426.3 Customizing the automation policy . . . . . . . . . . . . . . . . . . . . . . . . . . . 436.4 Useful commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 7. OS/390 UNIX setup issues . . . . . . . . . . . . . . . . . . . . . . . . . . 457.1 Tuning for TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457.2 Tuning the OS/390 application development environment . . . . . . . . . 45

© Copyright IBM Corp. 2001 iii

Chapter 8. Java for OS/390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478.1 Java for OS/390 at the JDK 1.1.8 level . . . . . . . . . . . . . . . . . . . . . . . . 47

8.1.1 Installing the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478.1.2 Post installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

8.2 IBM Developer Kit for OS/390, Java™ 2 Technology Edition . . . . . . . 498.2.1 Installing the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 9. HTTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519.1 Basic configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

9.1.1 Define the Web server working directory structure . . . . . . . . 529.1.2 Copy the Web server configuration files . . . . . . . . . . . . . . . . . . . 539.1.3 Prepare the Web server configuration files . . . . . . . . . . . . . . . . . 539.1.4 Define the security environment . . . . . . . . . . . . . . . . . . . . . . . . . 579.1.5 Define the Web server started procedure . . . . . . . . . . . . . . . . . . 599.1.6 Authorize the started procedure to RACF . . . . . . . . . . . . . . . . . . 599.1.7 Create a homepage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609.1.8 Start the Web server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609.1.9 Test the Web server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

9.2 Configuring the Web server to host an application server . . . . . . . . . . 619.3 Starting the application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

9.3.1 Invoking the Installation Verification Program . . . . . . . . . . . . . . . 62

Chapter 10. DB2 enablement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6510.1 DB2 considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

10.1.1 DB2 subsystem name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6610.1.2 Increase the buffer pool size. . . . . . . . . . . . . . . . . . . . . . . . . . . 66

10.2 DB2 Call Level Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6710.3 Java Database Connectivity and static SQL . . . . . . . . . . . . . . . . . . . 7010.4 Defining OS/390 Component Broker system management database 7010.5 Granting access to the system management database . . . . . . . . . . . 71

Chapter 11. LDAP enablement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7311.1 Setting up the LDAP server for OS/390 Component Broker . . . . . . . 74

11.1.1 Configuration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 7411.1.2 Configuring LDAP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

11.2 Setting RACF authorization for LDAP . . . . . . . . . . . . . . . . . . . . . . . . 7911.3 Granting Access to LDAP databases . . . . . . . . . . . . . . . . . . . . . . . . 8011.4 Starting the LDAP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8011.5 Testing the LDAP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 12. Additional WebSphere EE enablement . . . . . . . . . . . . . . . 8512.1 Authorization for OS/390 Component Broker . . . . . . . . . . . . . . . . . . 8512.2 Setting OS/390 base system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8712.3 Setting initial.env file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

iv Prepare OS/390 for WebSphere Enterprise Edition

Appendix A. Sample DB2 bind and SQL sources and JCL . . . . . . . . . . 91A.1 DB2 bind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

A.1.1 Bind system management data base of OS/390 Component Broker 91A.1.2 Bind for LDAP setup for OS/390 Component Broker packages . . . . 93

A.2 SQL source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94A.2.1 SQL to grant system management database of Component Broker 94A.2.2 SQL to create database for LDAP server . . . . . . . . . . . . . . . . . . . . . 95

A.3 JCL to prime LDAP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Appendix B. Worksheets for defining a service definition . . . . . . . . . . 97B.1 Workloads and service classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98B.2 Resource groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99B.3 Classification rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100B.4 Application environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101B.5 Scheduling environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Appendix C. Special notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Appendix D. Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107D.1 IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107D.2 IBM Redbooks collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107D.3 Other resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108D.4 Referenced Web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111IBM Redbooks fax order form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

IBM Redbooks review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

v

vi Prepare OS/390 for WebSphere Enterprise Edition

PrefaceThis book helps you set up OS/390 for the IBM WebSphere Application Server for OS/390 Enterprise Edition.

We worked on an OS/390 R10 system, setting up IBM WebSphere Application Server 3.02 Enterprise Edition for OS/390. This redbook describes the setup for all the necessary components required to run WAS EE. However, we do not describe how to set up the CB/390 part in detail, or how to deploy EJBs, since at the time of writing of this book, IBM WebSphere Application Server 4.0 Enterprise Edition for OS/390 was already on the horizon. Since the deployment of EJBs will be different in WAS EE 4.0 from WAS EE 3.02, we decided to describe the EJB deployment for WAS 4.0 EE in detail in a future redbook.

In this book we discuss the following topics:

• Setting up OS/390 as a monoplex system if you are not running it in a sysplex

• Workload management issues, especially how to switch to WLM goal mode

• Setting up an OS/390 System Logger • Setting up OS/390 Resource Recovery Services (RRS) • Preparing the Automatic Restart Management (ARM) • OS/390 UNIX issues • Setting up Java 1.1.8 and 1.3.1 for OS/390 • Setting up an IBM HTTP Server and enabling the JSP and servlet engine • Customizing DB2 and LDAP to be used with the IBM WebSphere

Application Server for OS/390 • Some CB/390 related issues

This book is intended for system programmers, security administrators, network administrators, or database administrators who configure OS/390 WebSphere Enterprise Edition.

In preparation and in conjunction with this book, we recommend the following additional redbooks:

• OS/390 Workload Manager Implementation and Exploitation, SG24-5326 • IBM WebSphere Application Server Standard Edition Customization and

Usage, SG24-5870 • IBM HTTP Server for OS/390 Customization and Usage, SG24-6205

© Copyright IBM Corp. 2000 vii

The team that wrote this redbook

This redbook was produced by a team of specialists from around the world working at the International Technical Support Organization Poughkeepsie Center.

Roland Trauner is an IT consultant and IBM certified professional at the International Technical Support Organization, Poughkeepsie Center. He writes extensively and teaches IBM classes worldwide on all areas of OS/390 e-business, network computing and WebSphere. Before joining the ITSO in 1998, Roland worked on the IBM S/390 technical support team in Germany for IBM EMEA Central Region. His assignment at the ITSO ended in November 2000 and he now works for IBM Germany in the WebSphere brand management area for S/390. Roland joined IBM in 1979. If you have questions or comments regarding this book, feel free to contact him per e-mail at [email protected].

Iriani Ratna is an I/T Availability at ITS - IBM Indonesia. She holds a degree in Mathematics from the University of Indonesia. She has worked at IBM for 5 years, mostly supporting OS/390 customers in areas of OS/390, TCP/IP and VTAM. She has also been involved in many OS/390 installation and migration projects. Before joining IBM, she worked for several years at an oil company as MVS and VM system programmer.

Eva Yan is an OS/390 e-busines technical support specialist in the United States. She has 13 years of experience in various S/390 areas, including OS/390 design and development, and technical consultations. She holds a Master of Science degree in Software Engineering from Marist College. Her areas of expertise include OS/390, XML, server consolidation and application porting from non-OS/390 platforms.

Thanks to the following people for their invaluable contributions to this project:

Rich Conway and Bob Haimowitz from IBM ITSO for preparing and maintaining the system.

Tom Hackett from IBM Poughkeepsie to help us with the CB installation.

Maria Clarke, Sabine Holl, Uwe Sager, Thomas Weinzettl and Holger Wunderlich from IBM as well as Vince Wallace from Boeing in Seattle for contributing hints, tips and good spirit to the residency.

Thanks to the IBM S/390 e-business division for sponsoring this book.

viii Prepare OS/390 for WebSphere EE

Comments welcome

Your comments are important to us!

We want our Redbooks to be as helpful as possible. Please send us your comments about this or other Redbooks in one of the following ways:

• Fax the evaluation form found in “IBM Redbooks review” on page 117 to the fax number shown on the form.

• Use the online evaluation form found at ibm.com/redbooks

• Send your comments in an Internet note to [email protected]

ix



http://www.redbooks.ibm.com/contacts.html

x Prepare OS/390 for WebSphere EE

Chapter 1. Overview of software requirements

WebSphere Application Server Enterprise Edition for OS/390 consists of:

• Component Broker • WebSphere Application Server Standard Edition • Java for OS/390 • WebSphere Application Server Site Analyzer

This book describes the customization steps for those OS/390 components that can be done before you install and configure this product. All procedures and examples documented here are based and tested on OS/390 V2R10. Only those components that require customization specific to WAS EE are described. The reference section in Table 1 lists documents that contain additional information about all other required components. For complete information on WAS EE, see:

• WebSphere Application Server for OS/390 V3.02 Program Directory, GA22-7460

• WebSphere Application Server Standard Edition Planning, Installing and Using Version 3.02, GC34-4806

• OS/390 Component Broker Planning and Installation Guide GA22-7325

Table 1. OS/390 functional requisites for WebSphere Application Server for OS/390, Enterprise Edition

OS/390 element, feature, or component

Description and usage References

OS/390 base system

WAS EE requires at least a single-system sysplex (monoplex) configuration.

“Setting up a monoplex” on page 5OS/390 MVS Setting Up a Sysplex, GC28-1779

C/C++ with or without Debug Tool

Provides a C compiler, C++ compiler, C/C++ application development utilities, and, optionally, a debug tool that runs with C and C++ as well as other languages. The C/C++ feature is needed for compiling code but not for runtime.If you plan to use the IBM Distributed Debugger with C++ or VisualAge for Java, you need the debug tool.

OS/390 Planning for Installation, GC28-1726OS/390 C/C++ User’s Guide, SC09-2361Debug Tool User’s Guide and Reference, SC09-2137

C/C++ IBM Open Class Library

C/C++ IBM Open Class Library provides a comprehensive set of C++ class libraries that are used for application development and execution

OS/390 C/C++ IBM Open Class Library User’s Guide, SC09-2363

© Copyright IBM Corp. 2001 1

IBM HTTP Server IBM HTTP Server is the Web server for OS/390 V2R7 and higher. It is available as follows:In OS/390 V2R7 and V2R8, as a component of the base element WebSphere Application Server In OS/390 V2R9 and higher, as a base element in OS/390

Chapter 9, “HTTP server” on page 51IBM HTTP Server for OS/390, Planning, Installing, and Using, SC31-8690

IP Services Communications Server (also known as CS OS/390) supports secure TCP/IP, SNA, and UNIX networking throughout an enterprise. It provides the ability to connect subsystems and applications to each other, and to connect network devices to the system. In OS/390 V2R7, this base element is known as eNetwork Communications Server. In OS/390 V2R8 and V2R9, it is known as SecureWay Communications Server.

OS/390 SecureWay Communications Server: IP Configuration, SC31-8513

Language Environment

Language Environment provides the runtime environment for programs generated with , among others, OS/390 C/C++ and VisualAge for Java Enterprise Edition for OS/390.

OS/390 Language Environment Customization, SC28-1941

OS/390 UNIX System Services

OS/390 System Services provides an interactive UNIX command interface and includes:Application Services (shell, utilities, debugger, and Parallel Environment)Connection ManagerProcess ManagerIntegrated Call Level Interface

Chapter 7, “OS/390 UNIX setup issues” on page 45OS/390 UNIX System Services Planning, SC28-1890

Resource Recovery Services (RRS)

WAS EE requires RRS support for JDBC connection pooling.

Chapter 5, “Resource Recovery Services” on page 39OS/390 Programming: Resource Recovery, GC28-1739



2 Prepare OS/390 for WebSphere Enterprise Edition

SecureWay Security Server (V2R8 or higher)

SecureWay Security Server lets you control access to protected resources. It includes:RACFDCE Security ServerLDAP ServerFirewall TechnologiesOpen Cryptographic Enhanced Plug-ins (OCEP)RACF provides Security Authorization Facility (SAF) support for the Web server, from which the Application Server also derives its security support. You may also substitute another SAF-based security product as long as it provides equivalent function.

OS/390 SecureWay Security Server RACF Migration, GC28-1920

SecureWay Security Server LDAP Server

As of OS/390 R8, LDAP (Lightweight Directory Access Protocol) Server is licensed with the base operating system and, thus, does not require that SecureWay Security Server be ordered or enabled. However, SecureWay Security Server does have to be installed in order to make LDAP Server functional.

Chapter 11, “LDAP enablement” on page 73OS/390 Security Server LDAP Server Administration and Usage Guide, SC24-5861

System Logger System Logger ia an MVS component that allows an application to log data from a sysplex.WAS EE requires at least a monoplex configuration, which requires the system logger.

Chapter 4, “ System Logger” on page 35OS/390 MVS Setting Up a Sysplex, GC28-1779

Workload management (WLM)

WAS EE requires WLM to manage workloads and requires that you run WLM in goal mode.

Chapter 3, “Workload management” on page 7OS/390 Planning: Workload Management, GC28-1761OS/390 Component Broker Planning and Installation Guide GA22-7325



Chapter 1. Overview of software requirements 3

DB2 for OS/390 (V5 or higher)

You can use DB2 V5 or higher for:Session state supportJDBC and SQLJ connectorsJDBC/ODBC bridgeJDBC connection pooling also requires RRS support and the system logger.WAS EE requires DB2 V5 or higher as the persistent data store for LDAP, the Naming Service, and system management data.You can also use WAS EE with DB2 V5 for non-PAA connection support; however, PAA connection support requires DB2 V6 or higher.

Chapter 10, “DB2 enablement” on page 65For DB2 V5, see:DB2 for OS/390 V5 Application Programming Guide and Reference for Java, SC26-9547DB2 for OS/390 V5 Data Sharing: Planning and Administration, SC26-8961For DB2 V6, see:DB2 UDB for OS/390 V6 Application Programming Guide and Reference for Java, SC26-9018DB2 UDB for OS/390 V6 Data Sharing: Planning and Administration, SC26-9007




Chapter 2. Setting up a monoplex

WAS EE requires at least a single-system sysplex (monoplex). Follow these steps to set up a monoplex.

2.1 Format a Sysplex couple data set

In monoplex mode, you need a formatted primary sysplex couple data set before you IPL the system. Sample JCL to run the utility to format a sysplex couple data set is shipped with OS/390 in SYS1.SAMPLIB member IXCSYSPF. Figure 1 shows the JCL we used to create our primary and alternate sysplex couple data set:

//DEFCDS JOB (999,POK),'L06R ',NOTIFY=&SYSUID,// CLASS=A,MSGCLASS=T,TIME=1439,// REGION=5000K,MSGLEVEL=(1,1)//******************************************************************//* JCL TO FORMAT THE PRIMARY AND ALTERNATE SYSPLEX CDS.//******************************************************************//STEP1 EXEC PGM=IXCL1DSU//STEPLIB DD DSN=SYS1.MIGLIB,DISP=SHR//SYSPRINT DD SYSOUT=*//SYSIN DD *

DEFINEDS SYSPLEX(OPPLEX)DSN(SYS1.XCF.CDS01) VOLSER(OPPLEX)MAXSYSTEM(16)CATALOG

DATA TYPE(SYSPLEX)ITEM NAME(GRS) NUMBER(1)ITEM NAME(GROUP) NUMBER(100)ITEM NAME(MEMBER) NUMBER(200)

DEFINEDS SYSPLEX(OPPLEX)DSN(SYS1.XCF.CDS02) VOLSER(OPPLEX)MAXSYSTEM(16)CATALOG

DATA TYPE(SYSPLEX)ITEM NAME(GRS) NUMBER(1)ITEM NAME(GROUP) NUMBER(100)ITEM NAME(MEMBER) NUMBER(200)

/*

Figure 1. JCL to format a primary and alternate couple data set

2.2 Update SYS1.PARMLIB

Use the following parameters in IEASYSxx parmlib member to IPL the system:

• COUPLE=xx specifies the COUPLExx parmlib member that describes the single-system sysplex for the system. COUPLExx must specify at least a sysplex name and a primary sysplex couple data set name. The sysplex couple data set must be unique for that system. COUPLExx must also


specify the couple data set for any function, such as WLM, that you plan to use.

/*******************************************************************//* MEMBER = COUPLE00 *//* *//* DESCRIPTION = THIS PARMLIB MEMBER IS ACCESSED THROUGH THE *//* SYSTEM PARAMETERS BY SPECIFYING COUPLE=00 *//* *//*******************************************************************/COUPLE SYSPLEX(OPPLEX)

PCOUPLE(SYS1.OPPLEX.CDS01)DATA TYPE(LOGR)

PCOUPLE(SYS1.OPPLEX.LOGR01)DATA TYPE(WLM)

PCOUPLE(SYS1.OPPLEX.WLM03)DATA TYPE(ARM)

PCOUPLE(SYS1.OPPLEX.ARM01)

Figure 2. Updating COUPLExx member

• PLEXCFG=MONOPLEX indicates that the system is to be initialized as a single-system sysplex.

2.3 IPL the system

IPL the system to use the newly defined parameters to bring up the monoplex. You should see the following messages on your console:

IXC415I FORCING SYSPLEX CONFIGURATION TO BE MONOPLEX MODEIXC413I MULTISYSTEM SYSPLEX CONFIGURATION PREVENTED BY PLEXCFG=MONOPLEXIXC413I XCFLOCAL SYSPLEX CONFIGURATION PREVENTED BY PLEXCFG=MONOPLEXIXC418I SYSTEM SC59 IS NOW ACTIVE IN SYSPLEX OPPLEX

2.4 Useful commands

• Display status of the sysplex:

D XCF,SYSPLEX,ALL

• Display information about the active sysplex couple data set:

D XCF,COUPLE,TYPE=SYSPLEX


Chapter 3. Workload management

OS/390 WebSphere Application Server Enterprise Edition uses the workload management (WLM) function to manage workloads throughout the sysplex. You must configure your system to run in goal mode.

WLM replaces the primary existing set of SRM controls: the IEAICSxx and IEAIPSxx members in SYS1.PARMLIB. Processing from an ICS and IPS is called compatibility mode; processing from goals defined in the WLM service definition is called goal mode. It is possible to switch individual systems between the two modes with an operator command.

This chapter describes how to perform the transition from compatibility mode to goal mode.

3.1 OS/390 performance control interface

WLM processing in goal mode uses the following interfaces to control resource distribution:

• IEAOPTxx in SYS1.PARMLIB

Only a subset of the parameters is now applicable. Values that are not used by WLM are ignored; no changes are necessary to the existing IEAOPTxx unless installation-specific updates are required.

Basically it is possible to control physical resource thresholds like central and expanded storage, but not values that influence the system behavior such as expanded storage criteria aging, logical swapping, and MPL control. For additional information on IEAOPTxx, see OS/390 MVS Initialization and Tuning Guide, SC28-1751 and OS/390 MVS Initialization and Tuning Reference, SC28-1752.

• The WLM Service Definition

The WLM Service Definition is installed and activated into a WLM couple data set using the WLM ISPF application. “Using the WLM ISPF application” on page 8 describes the ISPF interface to input and manage the service definition.

3.2 Preparing the WLM environment

To use WLM in goal mode, you must be, at the minimum, in a single-system sysplex (monoplex). Chapter 2, “Setting up a monoplex” on page 5 describes


how to implement a monoplex. If your system currently runs in compatibility mode, follow these tasks to implement goal mode:

• “Using the WLM ISPF application” on page 8

• “Making a WLM couple data set available” on page 8

• “Service definition implementation” on page 10

• “Switch into goal mode” on page 32

3.2.1 Using the WLM ISPF applicationYou use the WLM ISPF administrative application to define your service definition. This application requires the following products:

• TSO/E Version 2.5 plus SPEs or later

• ISPF 4.3 or later

The user of this application must have update access to the RACF FACILITY class profile MVSADMIN.WLM.POLICY. To start the application, issue the following command on a TSO command line:

ex ‘SYS1.SBLSCLI0(IWMARIN0)’

If you plan to use the application frequently, you should add it as an option on your ISPF application. To add the WLM application as an option on your ISPF primary panel, add the following statement to the processing section of the primary option menu panel (ISR@PRIM):

WLM,'CMD(%IWMARIN0) NEWAPPL(IWMP) PASSLIB'

Make sure you concatenate the library containing your customized primary panel before any others in your logon procedure or CLIST.

3.2.2 Making a WLM couple data set availableA WLM couple data set is necessary for storing the services definition information. You can choose to use one of the following methods to create and format the WLM couple data set:

• The facility provided in the WLM ISPF application. See “Using the WLM ISPF application” on page 8. Select option 3 from the Utilities menu as shown in Figure 3.

• The XCF utility. Figure 4 on page 9 shows the JCL to format the WLM CDS.


Figure 3. Utilities pop-up menu for allocating CDS

Figure 4. JCL to format the WLM CDS

To make the newly formatted couple data set available to the sysplex, use the following SETXCF operator commands:

File Utilities Notes Options Help----- EsssssssssssssssssssssssssssssssssssssssssssssssssN ----------------Funct e 4 1. Install definition e Appl LEVEL011Comma e 2. Extract definition e _________________

e 3. Activate service policy eDefin e 4. Allocate couple data set e

e 5. Allocate couple data set using CDS values eDefin DsssssssssssssssssssssssssssssssssssssssssssssssssMDescription . . . . . . . quickstart def of Cheryl Watson

Select one of thefollowing options. . . . . ___ 1. Policies

2. Workloads3. Resource Groups4. Service Classes5. Classification Groups6. Classification Rules7. Report Classes8. Service Coefficients/Options9. Application Environments10. Scheduling Environments

//DEFLOWLM JOB (999,POK),'L06R',CLASS=A,REGION=4096K,// MSGCLASS=T,TIME=10,MSGLEVEL=(1,1),NOTIFY=&SYSUID//*******************************************************************//* *//* JCL TO FORMAT THE PRIMARY AND ALTERNATE WLM CDS *//* *//*******************************************************************//STEP1 EXEC PGM=IXCL1DSU//SYSPRINT DD SYSOUT=*//SYSIN DD *

DEFINEDS SYSPLEX(OPPLEX)MAXSYSTEM(4)DSN(SYS1.OPPLEX.WLM02) VOLSER(OPPLEX)CATALOGDATA TYPE(WLM)ITEM NAME(POLICY) NUMBER(25)ITEM NAME(WORKLOAD) NUMBER(50)ITEM NAME(SRVCLASS) NUMBER(100)ITEM NAME(SVDEFEXT) NUMBER(100)ITEM NAME(SVDCREXT) NUMBER(100)ITEM NAME(APPLENV) NUMBER(100)

/*

Chapter 3. Workload management 9

• To make a primary WLM couple data set called SYS1.OPPLEX.WLM01 residing on volume TEMP01 available:

SETXCF COUPLE,TYPE=WLM,PCOUPLE=(SYS1.OPPLEX.WLM01,TEMP01)

• To make an alternate WLM couple data set called SYS1.OPPLEX.WLM02 residing on volume TEMP02 available:

SETXCF COUPLE,TYPE=WLM,ACOUPLE=(SYS1.OPPLEX.WLM02,TEMP02)

Remember that you still need to update the COUPLExx member in SYS1.PARMLIB as shown in Figure 2 on page 6, so that any subsequent IPLs will automatically pick up the WLM couple data set.

3.2.3 Service definition implementationYou also use the WLM ISPF application to define service definitions. Before going into the application, you should have already planned your service definition on worksheets. Appendix B, “Worksheets for defining a service definition” on page 97 provides sample worksheets that you can use as a model. Your service definition will be composed of:

• One or more service policies

• Classification rules (one set per service definition, which categorize work into service classes, and optional report classes)

• Workloads (JES, TSO, CICS, IMS, and so on), which are arbitrary group collections for reporting purposes

• Service classes (one or more per workload; for each service class there is a service goal and importance)

• Resource groups (optional, associated with service class)

• Application environments (optional)

• Scheduling environments (optional)

Preparing a service definition requires you to:

• Understand your workload

• Set service classes for major workloads

• Set classification rules to get work into the correct service classes

Use your ICS/IPS configuration as a model. This may be an opportune time for a careful review of workloads and business priorities. It is also highly recommended to plan on reducing the number of service class categories compared to the number of performance groups. Less systems programmer fine-tuning is required with WLM goal mode.


In this section we use Cheryl Watson’s Quickstart Service Policy. A copy of the policy, which can be used as a base, is available at:

http://www.watsonwalker.com/qspdown.html

A full description, and the latest version of Cheryl Watson’s Quickstart Service definition may be found at:

http://www.watsonwalker.com/quickst.html

3.2.3.1 Specifying your service definitionAs you enter the WLM application you must specify where you would like WLM to read a prior definition from, or whether you want to create a new definition. The first time you need to create a new service definition, choose option 3 on the Choose Service Definition pop-up menu as illustrated in Figure 5.

Figure 5. Choose service definition panel

If you need to stop updating the service definition, press PF3. The PF3 save function saves the tables into a PDS and ends the WLM session. The next time you start the WLM application, choose Read saved definition and then specify the PDS data set name.

File Help--------------------------------------------------------------------------

Command ===> ______________________________________________________________

ssssssssssssssssssssssssssssssssssssssssssssssNe Choose Service Definition ee ee Select one of the following options. ee __ 1. Read saved definition ee 2. Extract definition from WLM ee couple data set ee 3. Create new definition ee ee F1=Help F2=Split F5=KeysHelp ee F9=Swap F12=Cancel eDsssssssssssssssssssssssssssssssssssssssssssssM

ENTER to continue


3.2.3.2 Main Definition MenuNow is the time to enter the information that you placed in the service definition worksheet, as shown in Table 2.

Table 2. QUICKDEF Sample Service Definition

The definition menu is the central place for entering your service definition. Your service definition name and description are entered on the main definition menu panel (see Figure 6).

The definition data set field will be none until you save the service definition into a data set. You specify the data set to save into when exiting the application, or you can issue a save at any time by using the File command bar options.

The WLM ISPF application will dynamically allocate the PDS save data set if you specify a data set which does not already exist. Also, the application maintains a copy of PDS names used, and will display this list when you type a question mark (?) prompt into the data set name field.

Figure 6. Definition Main Panel

Service Definition Name

Description Coefficients

QUICKDEF Quickstart -Cheryl Watson

CPU: 1.0, IOC: 0.1, MSO: 0, SRB: 1.0 IO Priority Management: NO

File Utilities Notes Options Help--------------------------------------------------------------------------Functionality LEVEL001 Definition Menu WLM Appl LEVEL011Command ===> ______________________________________________________________

Definition data set . . : none

Definition name . . . . . quick (Required)Description . . . . . . . quickstart def of Cheryl Watson




3.2.3.3 Service coefficient definitionService coefficients define the weight to be applied to one type of service over another in the calculation of service rates. You can enter new values for the CPU, IOC, MSO, and SRB service coefficients. The WLM application provides the opportunity to change these coefficients. Choosing low numbers will reduce the magnitude of the service units reported.

There is an additional option on this panel for I/O priority management. The default is no, meaning I/O priorities are to be the same as dispatching priorities. Specifying yes means I/O priorities should be managed separately from dispatching priorities, according to the goals of the work. Note that this option affects the way execution velocities are calculated. With I/O priority management set to yes, the velocity calculation includes I/O as well as delay values.

Choose option 8 from the main panel (Figure 6 on page 12) to bring up the panel shown in Figure 7, where you can specify the coefficients/options.

Figure 7. Service Coefficient/Options Panel

3.2.3.4 Service policy definitionThe next step is to define your service policy or policies.

You will need to provide a name and description for each policy, including any policy overrides. The first time you set up a service definition, define a policy name and description. If you do not have a business need to change your goals, you can run with one service policy, without any policy overrides. You should have outlined your service policy names on a worksheet similar to Table 3. In this example, QUICKPOL is the base policy definition; QUICKBAT

Coefficients/Options Notes Options Help--------------------------------------------------------------------------

Service Coefficient/Service Definition OptionsCommand ===> ______________________________________________________________

Enter or change the Service Coefficients:

CPU . . . . . . . . . . . . . 1.0____ (0.0-99.9)IOC . . . . . . . . . . . . . 0.5____ (0.0-99.9)MSO . . . . . . . . . . . . . 0.0000_ (0.0000-99.9999)SRB . . . . . . . . . . . . . 1.0____ (0.0-99.9)

Enter or change the service definition options:

I/O priority management . . . . . . . . NO (Yes or No)Dynamic alias management . . . . . . . . NO (Yes or No)


and QUICKTST are override policies. See “Policy overrides” on page 28 for an example of defining policy override.

Table 3. Sample service policy definitions.

Figure 8. Service policy selection list panel

3.2.3.5 Workload specificationA workload logically consists of a group of one or more service classes. You associate a workload with a service class in the Service Class panel. Enter your workloads before creating your service classes.

Note: A workload is only used as a grouping of service classes for reporting purposes. It does not affect workload management.

Input your workloads and their descriptions from your worksheets, as shown in Table 4.

Table 4. Sample workload classification

Service Policy Name

Description SRVCLASS or RG Overrides

QUICKPOL Service policy QUICKPOL

QUICKBAT production batch night override

SRVCLASS:PRDBATHI

QUICKTST This is a copy from QUICKPOL

SRVCLASS:TSTBATHI, TSTBATMD

Workload name Description

ASCH APPC/MVS users

OMVS UNIX System Services users

Service-Policy View Notes Options Help--------------------------------------------------------------------------

Service Policy Selection List Row 1 to 1 of 1Command ===> ______________________________________________________________

Action Codes: 1=Create, 2=Copy, 3=Modify, 4=Browse, 5=Print, 6=Delete,7=Override Service Classes, 8=Override Resource Groups,/=Menu Bar

----Last Change-----Action Name Description User Date__ QUICKPOL Service policy QUICKPOL YAN 2000/10/02

******************************* Bottom of data *******************************


Workload class descriptions are entered by using option 2. Workloads must be defined before they can be used in service class definitions. Figure 9 shows the workload selection list panel.

Figure 9. Workload selection list panel

3.2.3.6 Resource group specificationA resource group defines a minimum or maximum amount of processing capacity. You associate a resource group with a service class in the Service Class panel. A resource group can be associated with multiple service classes. Enter resource groups using option 3, which is shown in Figure 10:

ONLINE Online systems

PRDBAT Production batch

STC Started tasks

TSO TSO users

TSTBAT Test batch

Workload name Description

Workload View Notes Options Help--------------------------------------------------------------------------

Workload Selection List Row 1 to 7 of 7Command ===> ______________________________________________________________

Action Codes: 1=Create, 2=Copy, 3=Modify, 4=Browse, 5=Print, 6=Delete,/=Menu Bar

----Last Change-----Action Name Description User Date__ ASCH APPC/MVS users YAN 2000/10/02__ OMVS UNIX System Serverices usres YAN 2000/10/02__ ONLINE Online systems YAN 2000/10/02__ PRDBAT Production batch YAN 2000/10/02__ STC Started tasks YAN 2000/10/02__ TSO TSO users YAN 2000/10/02__ TSTBAT Test batch YAN 2000/10/02

******************************* Bottom of data *******************************


Figure 10. Create a resource group panel

3.2.3.7 Working with service classA service class is a group of work with similar performance goals, resource requirements, or business importance. You make the association between service class, workload and resource groups in the Service Class panel. You associate a service class with incoming work in the Classification Rules panel. Make sure you enter service classes before creating classification rules.

After all your preparation and planning, you will have created a worksheet, similar to Table 5, that describes your service classes.

Table 5. Sample service class definition

SRVCLASS Description Workload RG Per Dur Imp Goal

ASCH APPC/MVS users ASCH 1 500 2 80% 00:00:00.50

2 4 Velocity 30

Omvs UNIX system services users

OMVS 1 500 2 80% 00:00:00.50

2 4 Velocity 30

ONLPRD Online production ONLINE 1 1 Velocity 50

ONLPRDHI Online production high

ONLINE 1 1 80% 00:00:00.50

ONLPRDLO Online production low

ONLINE 1 3 50% 00:00:10.00

ONLPRDMD Online production medium

ONLINE 1 2 80% 00:00:03.00

Resource-Group View Notes Options Help--------------------------------------------------------------------------

Resource Group Selection List Row 1 to 2 of 2Command ===> ______________________________________________________________


----Last Change-----Action Name Description User Date__ OTHERS Other TSO work YAN 2000/10/02__ TOPTSO Priority TSO work YAN 2000/10/02

******************************* Bottom of data ********************************


Note: Workload specification must be completed prior to using option 3 for service classes definition.

Entering the service classes using main definition panel option 4 is a relatively minor task (compared to the planning and preparation). Period and duration specification is similar to IEAIPS PGN periods. While you are using the service class input panel, shown in Figure 11, a pop-up window will be presented for you to choose one of four types of goal:

• Average response time

• Response time with percentile

• Execution velocity

• Discretionary

ONLTST Online test regions ONLINE 1 Discretionary

PRDBATHI Production batch high

PRDBAT 1 2 Velocity 30

PRDBATLO Production batch low

PRDBAT 1 Discretionary

STCLO STC low STC 1 Discretionary

STCMD STC medium STC 1 3 Velocity 30

TSOPROD TSO users TSO 1 500 2 80% 00:00:00.50

1 2000 3 80% 00:00:00.20

3 5 50% 00:10:00.00

TSTBATHI Test batch high TSTBAT 1 3 90% 00:10:00.00

TSTBATLO Test batch low TSTBAT 1 Discretionary

TSTBATMD Test batch medium TSTBAT 1 4 80% 00:30:00.00

SRVCLASS Description Workload RG Per Dur Imp Goal


Figure 11. Create a service class panel

Figure 12 shows the stacked windows that will be displayed as you either enter or update the goals. In this case a typing error was made inputting the percentile, and needed to be fixed.

Figure 12. Update a service class pop-up panel

Service-Class Xref Notes Options Help--------------------------------------------------------------------------

Modify a Service Class Row 1 to 3 of 3Command ===> ______________________________________________________________

Service Class Name . . . . . : ASCHDescription . . . . . . . . . APPC/MVS usersWorkload Name . . . . . . . . ASCH (name or ?)Base Resource Group . . . . . ________ (name or ?)Cpu Critical . . . . . . . . . NO (YES or NO)

Specify BASE GOAL information. Action Codes: I=Insert new period,E=Edit period, D=Delete period.

---Period--- ---------------------Goal---------------------Action # Duration Imp. Description____ 1 500 2 80% complete within 00:00:00.500__ 2 4 Execution velocity of 30

******************************* Bottom of data ********************************

Service-Class Xref Notes Options Help- EsssssssssssssssssssssssssssssssssssssssssN ----------------------------e Choose a goal type for period 1 e ss Row 1 to 3 of 3

C e e _____________________________e e

S e 2 1. Average response time eD e 2. Response time with percentile eW e 3. Execution velocity e or ?)B e 4. Discretionary e or ?)C e e or NO)e F1=Help F2=Split F5=KeysHelp e

S e F9=Swap F12=Cancel e I=Insert new period,E DsssssssssssssssssssssssssssssssssssssssssM

---Period--- ---------------------Goal---------------------Action # Duration Imp. Description__e 1 500 2 80% complete within 00:00:00.500__ 2 4 Execution velocity of 30

******************************* Bottom of data ********************************


When you have completed entering your service classes, you can create any policy overrides that might be required. See “Policy overrides” on page 28 for additional information.

3.2.3.8 Classification groupsClassification groups are optional. You use groups to simplify classification. You associate a classification group with a service class in the classification rules panel. If you intend to use them, create groups before creating classification rules.

Here, we have chosen to classify as much work as possible into groups; see Table 6 on page 19. Qualifier groups of more than five members are quicker to check than single instances in the classification rules.

Note: An asterisk (*) represents the use of wildcards.

Table 6. Sample classification groups

Type Group name

Description Qualifier Description

TCG PRDBATHI Production batch class group

Q Payroll reserved initiator

TCG TSSBATHI Hot test batch group H Emergency test batch

TCG TSTBATLO Low test batch group A IOU department batch

TCG TSTBATMD Medium test batch group M Medium test batch

TNG ONLPRD Online production group CICSP* Production CICS

IMSP* Production IMS

DB2P* Production DB2

TNG ONLTST Online test regions group CICST* Test CICS

IMST* Test IMS

DB2T* Test DB2


Enter classification groups using option 5. Figure 13 shows the transaction name classification groups.

Figure 13. Group selection list panel

Figure 14 demonstrates the modify group panel. Simply enter action 3 next to the group name to modify it. To get information about a field, use the

TNG STCHI High STCs NPM RMF JES* APPC ASCH OMVS AOPS DLF IRLM* LLA MIM OMON* OMVSKERN PCAUTH RACF SMS SYSBMAS TRACE TSO VLF VTAM

TNG STCMD Medium STCs SCHED

SPOOLPGM

PRINTMGT

OPS_JOBS

Type Group name

Description Qualifier Description

Group View Notes Options Help--------------------------------------------------------------------------

Group Selection List Row 1 to 4 of 4Command ===> ______________________________________________________________

Qualifier type . . . . . . . : Transaction Name


----Last Change-----Action Name Description User Date3_ ONLPRD Online production regions YAN 2000/10/02__ ONLTST Online test regions YAN 2000/10/02__ STCHI High STCs YAN 2000/10/02__ STCMD Medium STCs YAN 2000/10/02

******************************* Bottom of data ********************************


cursor-sensitive help function. Place your cursor over the data field, and press PF1 for help.

Figure 14. Modify a group panel

3.2.3.9 Classification rulesClassification rules assign incoming work to service classes. Before you create your classification rules, you must understand which subsystem's work is represented in each of your service classes.

When you choose option 6 for classification rules, you go to the Subsystem Type Selection List for Rules, as shown in Figure 15 on page 23. This selection list is primed with all of the IBM-supplied subsystem types. They are reserved names.

You should have created a worksheet, similar to Table 7, that describes your classification rules. Remember, there is only one set of classification rules in the service definition for a sysplex. They are the same regardless of which service policy is in effect; a policy cannot override classification rules.

Note: An asterisk (*) represents the use of wildcards.

Table 7. Sample classification rules definition

Subsystem

Description

Level

Type

Name Start SRVCLASS

RPTCLASS

Description

ASCH APPC/MVS

Default ASCH All APPC

CB

CICS CICS Default ONLPRDHI Prod CICS

Group Xref Notes Options Help--------------------------------------------------------------------------

Modify a Group Row 1 to 4 of 4Command ===> ______________________________________________________________

Enter or change the following information:

Qualifier type . . . . . . . : Transaction NameGroup name . . . . . . . . . : ONLPRDDescription . . . . . . . . . Online production regionsFold qualifier names? . . . . Y (Y or N)

Qualifier Name DescriptionCICSP* Production CICSIMSP* Production IMSDB2P* Production DB2________ ________________________________


DB2D

DDF

IMS IMS Default ONLPRDMD

Prod IMS

IWEB

JES JES batch Default PRDBATLO PRDBAT

1 TCG

PRDBATHI

PRDBATHI PRDBAT

1 TCG

PRDBATHI

PRDBATHI

1 TCG

TSTBATMD

TSTBATMD

1 TCG

TSTBATLO

TSTBATLO

LSFM

OMVS UNIX System Services

Default OMVS All OMS

STC Started tasks

Default SYSSTC

1 TNG

STCHI SYSSTC

1 TNG

STCMD

STCMD

1 TNG

ONLPRD

ONLPRD

1 TNG

ONLTST

ONLTST

1 TNG

* STCLO

TSO TSO Default TSOPRD

Subsystem

Description

Level

Type

Name Start SRVCLASS

RPTCLASS

Description


Figure 15 on page 23 shows the Subsystem Type Selection List for Rules panel. This is the main panel for defining classification rules. Do not delete any of the entries provided by IBM, even subsystems which you do not currently use, because you may need to use them in the future. Select action 3 next to the subsystem type to modify its rules.

Figure 15. Subsystem Type Selection List for Rules panel

RYO Roll your own

Default ONLPRDLO

1 AI DEPT12*

5 ONLPRDLO

2 PR ONLPRDMD

3 NET

ONLPRDHI

2 PR ONLPRDHI

Subsystem

Description

Level

Type

Name Start SRVCLASS

RPTCLASS

Description

Subsystem-Type View Notes Options Help--------------------------------------------------------------------------

Subsystem Type Selection List for Rules Row 1 to 14 of 14Command ===> ______________________________________________________________


------Class-------Action Type Description Service Report__ ASCH APPC/MVS users ASCH__ CB Use Modify to enter YOUR rules__ CICS Prod CICS ONPRDHI__ DB2 Use Modify to enter YOUR rules__ DDF Use Modify to enter YOUR rules__ IMS IMS ONPRDMD__ IWEB Use Modify to enter YOUR rules__ JES JES batch PRDBATLO PRDBAT__ LSFM Use Modify to enter YOUR rules__ MQ Use Modify to enter YOUR rules__ OMVS UNIX System Services OMVS__ SOM Use Modify to enter YOUR rules__ STC Started tasks SYSSTC__ TSO TSO TSOPRD

******************************* Bottom of data ********************************


Figure 15 shows that we have completed entering the IBM reserved subsystem workloads, and need to create the rules for workload RYO. RYO is intended to cover user-related workloads. Figure 16 shows the entry for RYO. .

Figure 16. Classification rules for roll your own (RYO)

3.2.3.10 Report classA report class is a group of work for which you want reporting data. You do not have to define report classes before assigning them to work in classification rules. You can create them from within the classification rules menu.

RMF will automatically produce data which enables you to analyze SRVCLASS performance, so we do not need to provide a RPTCLASS for each SRVCLASS. Here, as shown in Table 8, we have only one report class.

Table 8. Sample report class definition.

Report class descriptions can be specified using option 7. Also, specifying the report class in classification rules will prompt for the description.

Figure 17, Figure 18, and Figure 19 on page 25 show you the series of panels to select and modify a report class. Use the Xref on the command bar to find which classification rules use PRDBAT. The results from the Xref are displayed in the pop-up window displayed in Figure 19 on page 25.

Report class name Description

PRDBAT Production batch report

Subsystem-Type Xref Notes Options Help--------------------------------------------------------------------------

Create Rules for the Subsystem Type Row 1 to 3 of 3Command ===> ____________________________________________ SCROLL ===> PAGE

Subsystem Type RYO (Required) Fold qualifier names? Y (Y or N)Description . . . Roll your own

Action codes: A=After C=Copy M=Move I=Insert ruleB=Before D=Delete row R=Repeat IS=Insert Sub-rule

More ===>--------Qualifier-------- -------Class--------

Action Type Name Start Service ReportDEFAULTS: ONPRDLO ________

____ 1 AI DEPT12* 5 ONPRDLO ____________ 2 PR PRNAME2 ___ ONPRDHI ________is__ 2 PR PRNAME ___ ONPRDMD ________

****************************** BOTTOM OF DATA ******************************


Figure 17. Report class selection list

Figure 18. Modify a report class panel

Figure 19. Xref / Subsystem type pop-up window

3.2.3.11 Application environment specification for WAS EEAn application environment is a group of application functions invoked by request and executed in server address spaces. You can have workload management start and stop these server address spaces automatically, or do this manually or through automation. You define the application environment name, an optional procedure name for starting the server address spaces, and any start parameters needed for the start procedure.

Report-Class View Notes Options Help--------------------------------------------------------------------------

Report Class Selection List Row 1 to 1 of 1Command ===> ______________________________________________________________


----Last Change-----Action Name Description User Date__ PRDBAT Production batch report YAN 2000/10/02

******************************* Bottom of data ********************************

Report-Class Xref Notes Options Help--------------------------------------------------------------------------

Modify a Report ClassCommand ===> ______________________________________________________________

Enter or change the following information:

Report Class name . . . . . : PRDBATDescription . . . . . . . . . Production batch report

Report Class References Row 1 to 1 of 1Command ===> _________________________________________

These subsystem types refer to the report class.

Action Codes: 4=Browse

Action Name Description_ JES JES batch

******************* Bottom of data *******************


The example in Table 9 is for defining the necessary environment for WAS EE. For additional information about these run-time servers, refer to OS/390 Component Broker Planning and Installation Guide GA22-7325.

Table 9. Application environment specification for WAS EE run-time servers

From the main definition panel, select option 9 to create your application environment. Figure 20 on page 27 shows the Create an Application Environment panel where you enter data from your worksheet.

Run-time server

Application environment

Subsystem- type

Procedure name for the run-time server region

Start parameter Limit on starting server address space for a subsystem instance

Naming Server

CBNAMING CB BBONMS IWMSSNM=&IWMSSNM No limit

System Management Server

CBSYSMGT CB BBOSMSS IWMSSNM=&IWMSSNM No limit

Interface Repository Server

CBINTFRP CB BBOIRS IWMSSNM=&IWMSSNM No limit

Application Server

BBOASR1 CB BBOASR1S IWMSSNM=&IWMSSNM Single address space per system


Figure 20. Create an Application Environment panel

3.2.3.12 Create a scheduling environmentA scheduling environment is a list of resource names, along with their required states. By associating incoming work with a scheduling environment, you ensure that work is assigned to a system only if that system satisfies all of the requirements. You define the scheduling environment, listing all of the resource names and required states that are contained within. You also define the resource names themselves. Currently, JES2, JES3 and other IBM products can use scheduling environments.

Table 10 shows an example of a scheduling environment definition.

Table 10. Sample scheduling environment definition.

Scheduling environment specifications can be specified using option 10. Figure 21 on page 28 shows the panel used to create a scheduling environment definition. Keep specifying “a” to add until you get a chance to select the resource group. For additional assistance, use online HELP or refer to Chapter 16, section “Creating a New Resource” in OS/390 Planning: Workload Management, GC28-1761.

Scheduling environment

Description Resource Resource description

DB2A DB2 subsystem

9672RN6 CMOS generation 6

Application-Environment Notes Options Help--------------------------------------------------------------------------

Create an Application EnvironmentCommand ===> ______________________________________________________________

Application Environment . . . BBOASR1 RequiredDescription . . . . . . . . . App.Env. for Application ServerSubsystem Type . . . . . . . . CB RequiredProcedure Name . . . . . . . . BBOASR1SStart Parameters . . . . . . . IWMSSNM=&IWMSSNM ________

___________________________________________________________________________

Limit on starting server address spaces for a subsystem instance:2 1. No limit

2. Single address space per system3. Single address space per sysplex


Figure 21. Create a Scheduling Environment panel

The next panel (Figure 22) shows the resources you have defined. When you select the resource, Figure 21 will be re-displayed and you need to specify the Required State.

Figure 22. Scheduling environment Resource Definition List panel

3.2.3.13 Policy overridesYou use a policy override only if you have a business need to change a goal for a certain time, such as for the weekend or for nighttime. If you were using multiple IPS/ICS members, changed with the SET command based on business needs, then you may need comparable service policy overrides. Alternatively, you may find with the dynamic management of goal mode that one policy with one set of goals and realistic importance values is sufficient. Less important work will automatically be assigned more resource as more important work tapers off. You can define your policy overrides once you have defined your service classes.

Scheduling-Environments Notes Options Help--------------------------------------------------------------------------

Create a Scheduling Environment Row 1 to 1 of 1Command ===> ______________________________________________________________

Scheduling Environment Name DB2A____________ RequiredDescription . . . . . . . . . DB2 subsystem___________________

Action Codes: A=Add D=Delete

RequiredAction Resource Name State Resource Descriptiona_ ________

******************************* Bottom of data ********************************

Resources Notes Options XREF Help--------------------------------------------------------------------------

Resource Definition List Row 1 to 1 of 1Command ===> ______________________________________________________________

Selection For Scheduling Environment DB2A

Action Codes: A=Add S=Select X=XREF /=Menu Bar

Action Resource Name In Use Resource Descriptions_ 9672RN6 CMOS generation 6

******************************* Bottom of data *******************************


To define an override policy, choose option 1 Policies from the main definition panel, then use action 7 on the Service Policy Selection List panel to override service classes. Action 8 can be used to override resource groups. Figure 23 shows action 7 after the overrides for QUICKBAT have been entered.

Figure 23. Override service class selection list panel

Override View Notes Options Help--------------------------------------------------------------------------

Override Service Class Selection List Row 1 to 15 of 15Command ===> ______________________________________________________________

Service Policy Name . . . . : QUICKPOL

Action Codes: 3=Override Service Class, 4=Browse, 5=Print,6=Restore Base attributes, /=Menu Bar

Service OverriddenAction Class Goal Description__ ASCH NO APPC/MVS users__ OMVS NO UNIX System services users__ ONLPRD NO Online production__ ONLTST NO Online test rregions__ ONPRDHI NO Online production high__ ONPRDLO NO Online production low__ ONPRDMD NO Online production medium__ PRDBATHI NO Production batch high__ PRDBATLO NO Production batch low__ STCLO NO Started tasks low__ STCMD NO Started tasks medium__ TSOPRD NO TSO users__ TSTBATHI NO Test batch high__ TSTBATLO NO Test batch low__ TSTBATMD NO Test batch medium

******************************* Bottom of data ********************************


3.2.3.14 Installing and activating your service policyFigure 24 shows the Notepad panel that is displayed after selecting the Notepad option from the menu bar. Enter a description of the changes made.

Figure 24. Notepad panel

To install the service definition, select Utilities from the menu bar. You will be presented with a pop-up menu, as shown in Figure 25 on page 31. The options are explained below. Select option 1 to install the definition.

Install definition Use this option to install the service definition onto the WLM couple data set. Installing the service definition makes any changes available for policy activation.

Extract definition Use this option to extract the service definition previously installed on the WLM couple data set.

Activate service policy Use this option to activate a policy. When you select this option, the application displays a list of the service policies defined in the service definition currently installed on the WLM couple data set. You activate the service policy by selecting it from the list. Policy activation makes the policy go into effect for all systems in the sysplex. Note: If you have just made changes to a service definition, make sure you install it and activate a policy to have the changes take effect.

Allocate couple data set Use this option to allocate both your primary and alternate WLM couple data sets. This option is for users who are doing one of the following:

• Allocating a WLM couple data set for the first time • Migrating to an OS/390 R3 or later release where the current WLM

couple data set was allocated with a pre-OS/390 R3 release. In this

Notepad Help-----------------------------------------------------------------------------

NotepadCommand ===> _______________________________________________ SCROLL ===> PAGE

Definition name . . . . : quickDescription . . . . . . : quickstart def of Cheryl Watson

Enter up to 500 lines of notepad information.

****** **************************** Top of Data *****************************000100 10/03/2000 Installed quickstart policy.... Eva****** *************************** Bottom of Data ***************************


case you should run the IWMARSZ utility to determine the size of the current WLM couple data set.

Allocate couple data set using CDS values Use this option to allocate both your primary and alternate WLM couple data sets based on your existing WLM couple data set size. Use this option if your current WLM couple data set was allocated using OS/390 R3 or higher. The application displays the current size values on the panel. To make the WLM couple data set available for use in the sysplex, you must update your COUPLExx parmlib member and issue the SETXCF command; see Figure 2 on page 6.

Figure 25. Install definition panel

You may then get another window pop-up, requesting your confirmation to install the service definition, as shown in Figure 26 on page 32. You will need to make a decision on whether you can overwrite the CDS service definition; specify Yes to overwrite.

File Utilities Notes Options Help----- EsssssssssssssssssssssssssssssssssssssssssssssssssN ----------------Funct e 1 1. Install definition e Appl LEVEL011Comma e 2. Extract definition e _________________

e 3. Activate service policy eDefin e 4. Allocate couple data set e

e 5. Allocate couple data set using CDS values eDefin DsssssssssssssssssssssssssssssssssssssssssssssssssMDescription . . . . . . . quickstart def of Cheryl Watson




Figure 26. Overwrite service definition

3.2.4 Switch into goal modeAt this point, a WLM service policy exists. The system, running in compatibility mode, is still managing resources according to existing IPS and ICS definitions. To switch to goal mode, issue the following operator command:

MODIFY WLM,MODE=GOAL

• To ensure that goal mode will be the default configuration on your next IPL, you must remove the IPS= and ICS= parameters from the IEASYSxx member in SYS1.PARMLIB. You can switch back to compatibility mode any time by issuing:

MODIFY WLM,MODE=COMPAT

The operator will be prompted to enter the desired ICS and IPS members.

File Utilities Notes Options Help--------------------------------------------------------------------------Functionality LEVEL006 Definition Menu WLM Appl LEVEL011Command ===> ______________________________________________________________

Definition data set . . : 'YAN.QUICKPOL'

Definition name . . . . . quick (Required)Description . . . . . . . quickstart def of Cheryl Watson


EssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssNe Overwrite Service Definition ee ee Another service definition was found on the WLM couple data ee set. ee ee Service definition name : WEB_GOAL ee ee Definition installed by : YAN from system SC59 ee Definition installed on : 2000/10/02 at 13:27:17 ee ee Do you want to overwrite this? YES (Yes or No) ee ee ee F1=Help F2=Split F5=KeysHelp F9=Swap F12=Cancel eDssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssM


3.3 Setting up workload management for Component Broker

In addition to setting up workload management in goal mode, you need to define workload management policies for the following OS/390 Component Broker servers and run-time servers:

• System Manager Server

• Naming Server

• Interface Repository Server

• Application Server

Refer to “Application environment specification for WAS EE” on page 25 on how to use the ISPF application IWMARIN0 to define these policies.

3.4 Useful commands

• Set, or reset, the IPS and ICS in use (only valid in compatibility mode):

SET IPS=01,ICS=00DISPLAY DMNSETDMN

• Display the WLM CDS in use:

DISPLAY XCF,COUPLE,TYPE=WLM

• Set primary and alternate CDS:

SETXCF COUPLE,TYPE=WLM,PCOUPLE=(YOUR.WLM.PRIMARY)SETXCF COUPLE,TYPE=WLM,ACOUPLE=(YOUR.WLM.ALTERNAT)SETXCF COUPLE,TYPE=WLM,PSWITCH

• Display the current policy use, status of a system, or all systems in the sysplex:

DISPLAY WLMDISPLAY WLM,SYSTEMSDISPLAY WLM,APPLENV=...,SCHENV=...,RESOURCE=....

• Change the active WLM policy:

VARY WLM,POLICY=xxxx

• Change between goal and compatibility mode on a system:

MODIFY WLM,MODE=GOALMODIFY WLM,MODE=COMPAT

• Manage application environments:

VARY WLM,APPLENV=xxxx,QUIESCE


VARY WLM,APPLENV=xxxx,RESUMEVARY WLM,APPLENV=xxxx,REFRESH

• Manage resource usage on a system; used for affinity scheduling:

MODIFY WLM,RESOURCE=xxxx,ONMODIFY WLM,RESOURCE=xxxx,OFFMODIFY WLM,RESOURCE=xxxx,RESET

• Change between goal and compatibility mode; reset resource usage on system:

MODIFY WLM,MODE=GOAL|COMPATMODIFY WLM,RESOURCE=xxxx,ON|OFF|RESET


Chapter 4. System Logger

There are two types of log streams: coupling facility log streams and DASD-only log streams. The main difference between the two types of log streams is the storage medium System Logger uses to hold interim log data:

• In a coupling facility log stream, interim storage for log data is contained in coupling facility list structures.

• In a DASD-only log stream, interim storage for log data is contained in local storage buffers on the system.

We use a DASD-only log stream in this project. See OS/390 MVS Setting Up a Sysplex, GC28-1779 for further explanations on preparing a System Logger application.

4.1 Setting up System Logger

System Logger manages log streams based on the policy information that is placed in the LOGR couple data set. You must create this couple data set and make it available before any log streams can be defined to the system.

• Create and format the LOGR couple data set.

System Logger manages log streams based on the policy information that is placed in the LOGR couple data set. We used the following JCL to format our LOGR couple data set:

• Update the COUPLExx member in SYS1.PARMLIB

Add the LOGR couple data set to the COUPLExx member. Refer to Figure 2 on page 6, “Updating COUPLExx member”.

//DEFLOGR JOB (999,POK),'DEFINE LOGR CDS',CLASS=A,REGION=4M,// MSGCLASS=T,TIME=10,MSGLEVEL=(1,1),NOTIFY=&SYSUID//STEP1 EXEC PGM=IXCL1DSU//SYSPRINT DD SYSOUT=*//SYSIN DD *

DEFINEDS SYSPLEX(OPPLEX)MAXSYSTEM(1)DSN(SYS1.OPPLEX.LOGR00) VOLSER(OPPLEX)CATALOG

DATA TYPE(LOGR)ITEM NAME(LSR) NUMBER(100)ITEM NAME(LSTRR) NUMBER(60)ITEM NAME(DSEXTENT) NUMBER(10)

/*


• Make the LOGR couple data set available

You can use either of the following ways to make the primary and alternate couple data sets available to the system:

- IPL the system with the newly defined specifications in the COUPLxx parmlib member.

- Issue the following SETXCF commands when you want to bring the LOGR couple data sets online without IPLing the system:

SETXCF COUPLE,TYPE=LOGR,PCOUPLE=(SYS1.OPPLEX.LOGR00)SETXCF COUPLE,TYPE=LOGR,ACOUPLE=(SYS1.OPPLEX.LOGR01)

4.2 Setting up for Component Broker

OS/390 Component Broker has an error log stream that records error information when it detects an unexpected condition or failure within its own code, such as:

• Assertion failures

• Unrecoverable error conditions

• Vital resource failures, such as memory

• Operating system exceptions

• Programming defects in OS/390 Component Broker code

Configure this error log stream by using the JCL provided in BBORDLGS of BBO.SBBOJCL. This job will create a DASD-only log stream. A REXX EXEC, BBORBLOG, is provided in BBO.SBBOEXEC to browse the content of this log stream. You can create different error log streams for each Component Broker server. We chose to use one generic log stream instead.

4.3 Useful commands

• Display system logger status:

DISPLAY LOGGER

• Display log stream information:

DISPLAY LOGGER,LOGSTREAM

• Display the LOGR couple data set in use:

DISPLAY XCF,COUPLE,TYPE=LOGR

• Set primary and alternate couple data set:


SETXCF COUPLE,TYPE=LOGR,PCOUPLE=(YOUR.LOGR.PRIMARY)SETXCF COUPLE,TYPE=LOGR,ACOUPLE=(YOUR.LOGR.ALTERNAT)SETXCF COUPLE,TYPE=LOGR,PSWITCH

Chapter 4. System Logger 37

Chapter 5. Resource Recovery Services

Resource Recovery Services (RRS) is a required OS/390 function for Component Broker. RRS is used in conjunction with DB2 to back persistent objects. Before enabling RRS, you must configure OS/390 System Logger. RRS uses System Logger to record events related to protected resources in log streams that are shared by systems in a sysplex.

5.1 Define RRS log streams

RRS requires five log streams to be defined to System Logger. Table 11 shows the recommended size of these log streams when you enable WAS EE.

Table 11. Recommended size of log streams

Figure 27 contains the JCL we used to define these logstreams. Note the use of DASD-only log streams. Also, we used much smaller size log streams for testing purposes.

//DEFLOGRP JOB (999,POK),'LOGR POLICY',CLASS=A,REGION=4M,// MSGCLASS=X,TIME=10,MSGLEVEL=(1,1),NOTIFY=&SYSUID//*//* DEFINE AN ALIAS FOR HLQ IXGLOGR BEFORE RUNNING THIS JOB//*//STEP1 EXEC PGM=IXCMIAPU//SYSPRINT DD SYSOUT=*//SYSABEND DD SYSOUT=*//SYSIN DD *DATA TYPE(LOGR) REPORT(YES)

DEFINE LOGSTREAMNAME(ATR.OPPLEX.ARCHIVE)HLQ(IXGLOGR) MODEL(NO) LS_SIZE(1024)LOWOFFLOAD(0) HIGHOFFLOAD(80)RETPD(15) AUTODELETE(YES)DASDONLY(YES)

DEFINE LOGSTREAMNAME(ATR.OPPLEX.RM.DATA)HLQ(IXGLOGR) MODEL(NO) LS_SIZE(1024)

Log Stream Initial size Size

RM.DATA 1MB 1MB

MAIN.UR 5MB 50MB

DELAYED.UR 5MB 50MB

RESTART 1MB 5MB

ARCHIVE 5MB 50MB


LOWOFFLOAD(0) HIGHOFFLOAD(80)RETPD(15) AUTODELETE(YES)DASDONLY(YES)

DEFINE LOGSTREAMNAME(ATR.OPPLEX.MAIN.UR)HLQ(IXGLOGR) MODEL(NO) LS_SIZE(1024)LOWOFFLOAD(0) HIGHOFFLOAD(80)RETPD(15) AUTODELETE(YES)DASDONLY(YES)

DEFINE LOGSTREAMNAME(ATR.OPPLEX.DELAYED.UR)HLQ(IXGLOGR) MODEL(NO) LS_SIZE(1024)LOWOFFLOAD(0) HIGHOFFLOAD(80)RETPD(15) AUTODELETE(YES)DASDONLY(YES)

DEFINE LOGSTREAMNAME(ATR.OPPLEX.RESTART)HLQ(IXGLOGR) MODEL(NO) LS_SIZE(1024)LOWOFFLOAD(0) HIGHOFFLOAD(80)RETPD(15) AUTODELETE(YES)DASDONLY(YES)

/*

Figure 27. JCL to define the log streams required by RRS

5.2 Running RRS

Before you can start RRS, you must:

• Set up your log streams, as described in “Define RRS log streams” on page 39.

• Define RRS as a subsystem by placing the following statement in the IEFSSNxx member in SYS1.PARMLIB:

SUBSYS SUBNAME(RRS)

• Copy SYS1.PROCLIB(ATRRRS) to SYS1.PROCLIB(ATRRRS).

• Start RRS by issuing the operator command:

START RRS

• To stop RRS:

SETRRS CANCELFORCE RRS,ARM


Chapter 6. Automatic Restart Manager

The use of Automatic Restart Manager (ARM) is optional. We did not have ARM enabled during our testing. If you currently have ARM enabled, you may wish to disable it for the Component Broker address spaces before you install and customize Component Broker. During customization, job errors may cause unnecessary restarts of Component Broker address spaces.

If you do decide to enable ARM after installation and customization of Component Broker, make sure that the automation policies initialize the Component Broker and associated functions in the correct order, which is:

1. System Logger2. RRS3. DB2 for OS/3904. TCP/IP5. LDAP (optional)6. DCE (if used)7. The Daemon Server, which automatically starts the System Management

Server, Naming Server, and Interface Repository Server8. Your business application servers

Follow the remainder of this chapter to activate ARM for OS/390 Component Broker.

6.1 Formatting an ARM couple data set

Sample JCL to run the format utility for formatting an ARM couple data set is shipped in SYS1.PARMLIB member IXCARMF. Figure 28 shows a sample JCL job for formatting a primary ARM couple data set.

Note: The format utility will create a default policy which can be used on your first activation of ARM.

//IXCARMF JOB (999,POK),'ARMCDS',// MSGCLASS=H,NOTIFY=&SYSUID//*//*//STEP1 EXEC PGM=IXCL1DSU,REGION=2M//STEPLIB DD DSN=SYS1.MIGLIB,DISP=SHR//SYSPRINT DD SYSOUT=*//SYSABEND DD SYSOUT=*//SYSIN DD *

/* Allocating a primary Couple Dataset*/DEFINEDS SYSPLEX(OPPLEX)

DSN(SYS1.OPPLEX.ARM01) VOLSER(OPPLEX)NOCATALOG MAXSYSTEM(8)

DATA TYPE(ARM)/* Note that, if any of the


following ITEM NAME(xxx) andits NUMBER(n) are not specifi-ed, default value for thatitem will take effect. */

ITEM NAME(POLICY) NUMBER(5) /* Maximum number of user-definedARM policies that will be onthe couple data set at anygiven time.Defaults to 3. */

ITEM NAME(MAXELEM) NUMBER(25) /* Maximum number of elementsper policy.Defaults to 10. */

ITEM NAME(TOTELEM) NUMBER(20) /* Maximum number of elements thatare anticipated to be register-ed with ARM across the sysplexat any given time.Defaults to 500. */

/*

Figure 28. JCL job to format an ARM CDS

Update the COUPLExx member in SYS1.PARMLIB to add the newly formatted ARM couple data set so that it will be included on subsequent IPLs. Refer to Figure 2 on page 6, “Updating COUPLExx member”.

To make the ARM couple data set available, you can use either of the following methods:

• IPL the system with the newly defined specifications in the COUPLExx parmlib member.

• Issue the following SETXCF commands when you want to bring the ARM couple data sets online without IPLing the system:

SETXCF COUPLE,TYPE=ARM,PCOUPLE=(SYS1.OPPLEX.ARM01)

6.2 Starting the ARM policy

The next step is to start the ARM policy in the ARM couple data set. Once the policy is started, all systems connected to the ARM couple data set will use the same active policy.

To start the policy with defaults, issue:

SETXCF START,POLICY,TYPE=ARM

To start your own policy (mypol, for example), issue:

SETXCF START,POLICY,TYPE=ARM,POLNAME=mypol


6.3 Customizing the automation policy

You may choose to either modify the policy at this point or wait until WAS EE has been installed. These policies should adhere to the following guidelines:

• We recommend that you do not enable cross-system restart for OS/390 Component Broker server instances. The workload can move from the failing system to a running system, but you cannot bring the workload back to the original system once it is restored. Use the Administrative Data Utility (IXCMIAPU) to change the default ARM policy set by the OS/390 Component Broker servers. See OS/390 MVS Setting Up a Sysplex, GC28-1779 for details.

• If a failure occurs, automatic restart management can restart OS/390 Component Broker and related server instances on the same system.

• To change the policy, you need to know the existing element names for OS/390 Component Broker run-time server instances and how to name new elements for additional run-time server instances. The element names for the OS/390 Component Broker run-time server instances are shown in Table 12. OS/390 Component Broker creates element names for server instances by prefixing the server instance name with CBSRV. The Daemon server instance is an exception: its server instance name is prefixed with CBDMN. For example, the element name for a system management server instance called SYSMGT01 is CBSRVSYSMGT01, but the element name for a Daemon server instance called DAEMON01 is CBDMNDAEMON01.

Table 12. Automatic Restart Management element names for OS/390 Component Broker run-time server instances

• Prefix the names of your application server instances with CBSRV . For instance, if your server instance is called MYSERVER , the element name would be CBSRVMYSERVER .

Server instance Element name *

Daemon CBDMNDAEMON01

System Management CBSRVSYSMGT01

Naming CBSRVNAMING01

Interface Repository CBSRVINTFRP01

* The first server instance has the suffix 01. Each subsequent server instance replica increments the suffix by 1.

Chapter 6. Automatic Restart Manager 43

• Do not enable ARM for non-data sharing OS/390 Component Broker configurations in a sysplex (that is, multiple discreet OS/390 Component Broker systems running in a sysplex, but not doing data sharing).

• If you create a restart group, keep the following in the same restart group and set the restart order for the elements as indicated:

- RRS

- DB2 for OS/390 with IRLM

- IMS, CICS, and other transaction or resource managers, if used by your application servers in the restart group

- OS/390 Component Broker Daemon server instance

- OS/390 Component Broker System Management, Naming, and Interface Repository server instances.

- Your application server instances

6.4 Useful commands

• Display ARM status:

DISPLAY XCF,ARMSTATUS

• Display the ARM couple data set in use:

DISPLAY XCF,COUPLE,TYPE=ARM

• Set primary and alternate couple data set:

SETXCF COUPLE,TYPE=ARM,PCOUPLE=(YOUR.ARM.PRIMARY)SETXCF COUPLE,TYPE=ARM,ACOUPLE=(YOUR.ARM.ALTERNAT)SETXCF COUPLE,TYPE=ARM,PSWITCH


Chapter 7. OS/390 UNIX setup issues

There are no specific customization tasks that are required by WAS EE. However, it is important to adjust parameters in the BPXPRMxx member of SYS1.PARMLIB so that your installation can support the expected workload.

7.1 Tuning for TCP/IP

In the BPXPRM parmlib member, increase the number of sockets and file handles allowed.

• For sockets, on the MAXSOCKETS parameter in the NETWORK statement, add four times the number of clients simultaneously accessing the system to your existing number of sockets. Thus, if you will have 250 clients simultaneously accessing the system, and 1,000 sockets already defined, you should specify 2,000 sockets (4 x 250 +1,000).

• For file handles, on the MAXFILEPROC parameter, add the number of clients simultaneously accessing the system to your current number of file handles. Thus, if you have 250 clients simultaneously accessing the system, and the current number of file handles is 1,000, you should specify 1,250 file handles (250 + 1,000).

Note: Be sure not to exceed the overall maximum number of sockets or the maximum number of file handles set for your system.

• Check the NETWORK statement values of INADDRANYPORT and INADDRANYCOUNT. These two values act as a range for reserving ports, where INADDRYANYPORT is the starting point. This range cannot encompass the Daemon port value. For instance, if the Daemon port is 5555, INADDRANYPORT could start higher at 6000.

7.2 Tuning the OS/390 application development environment

• Allocate at least 100 cylinders of HFS space in the home directory for each application developer. You can maintain the application development storage the same way you maintain OS/390 UNIX HFS storage.

• Check the number of file descriptor files defined (MAXFILEPROC statement in the BPXPRMxx parmlib member). You may need additional file descriptor files when you compile programs.

• Check the maximum number of processes allowed (MAXPROCUSER statement in the BPXPRMxx parmlib member). You may need to add to the limit when you run makes.


• Check each application developer’s region size (MAXASSIZE in BPXPRMxx or ASSIZEMAX on the RACF ADDUSER or ALTUSER commands). The rule of thumb is to run with the largest region size possible. The size can be limited by the IEFUSI exit, JES2 EXIT06, JES3 IATUX03, or TSO segment defaults. If the compiler runs out of memory, you may need to increase the application developer’s region size.


Chapter 8. Java for OS/390

Java for OS/390 with Java Development Kit (JDK) is part of WAS EE which can be installed separately. If you already have the JDK installed on your system, you do not have to re-install it. Check the program directory for your release of WAS EE for Java release requirement.

Java for OS/390 can also be ordered separately. There is no charge to you when you order Java for OS/390. You can get the product through the normal OS/390 ordering procedures (for an SMP/E installable tape) or by downloading the product from the following Web site:

http://www.s390.ibm.com/java

From the Web, you can get either an SMP/E installable or non-SMP/E installable product.

8.1 Java for OS/390 at the JDK 1.1.8 level

For our project, we installed Java for OS/390 at the JDK 1.1.8 level, which has the following functions:

• Java 1.1 APIs

• Security enhancements

• Remote Abstract Windowing Toolkit (RAWT)

• JRIO

• Java 2 functions

- Security migration aid

- RMI-IIOP

- SWING

• Hardware floating point support for G5 and above

8.1.1 Installing the productDetailed instructions on how to install this product are available from:http://www.s390.ibm.com/java

We list the non-SMP/E installation procedures here for you convenience.

There are two ways to do a non-SMP/E install of the JDK TAR file:

• Automatically (by running the ajvinst.exec script)


• Manually (by issuing a set of commands)

8.1.1.1 Automated installTo start the install exec ajvinst.exec, enter the following command and follow the prompts:

exec ajvinst exec

8.1.1.2 Manual installInstructions are given using OS/390 UNIX commands. The installation below assumes the following:

• The file you have downloaded is called HJVA11E.TAR.Z

• You wish to install the package in /usr/lpp/java

• Your current directory is /usr/lpp/java

• The target directory /usr/lpp/java must be large enough to contain the entire Java product, approximately 150 MB after expansion for HJVA11E.TAR.Z

The following instructions will install the product:

1. Remove or rename any previous installation of this product, otherwise unpredictable results will occur. These commands can be issued while in the UNIX shell to accomplish this:

cd /usr/lpp/java/chmod -fR 700 J1.1rm -rf J1.1

Note: If the tar file was downloaded to an MVS data set, issue the OPUT command from the TSO command line to transfer the file HJVA11E.TAR.Z into the HFS:

OPUT HJVA11E.TAR.Z '/usr/lpp/java/HJVA11E.TAR.Z' BINARY

2. While in the UNIX shell and in your current directory, /usr/lpp/java, decompress and untar the file:

tar -xpozf HJVA11E.TAR.Z

8.1.2 Post installationYou will now have a directory called /usr/lpp/java/J1.1. Issue the following command to make Java available:

export PATH = /usr/lpp/java/J1.1/bin:$PATH


If Java installed successfully, the following commands will return options and versions:

java

java -fullversion

If you wish to continue with installation of the optional components, consult the installation guide available from the Web site.

8.2 IBM Developer Kit for OS/390, Java™ 2 Technology Edition

The IBM Developer Kit for OS/390, Java 2 Technology Edition provides a complete Java 2 Technology Development Kit at the SDK 1.3.0 level for the S/390 platform. In addition to the Java 2 APIs, the IBM Developer Kit for OS/390, Java 2 Technology Edition provides additional functional capability as represented by the Java Record I/O (JRIO) and security API functions introduced in the previous Java product.

8.2.1 Installing the productIn the download area on the Java for OS/390 Web site at http://www.s390.ibm.com/java there is a wizard to guide you through the decisions for getting and installing the IBM Developer Kit for OS/390, Java™ 2 Technology Edition. As you go through this tool, you will be asked questions and guided to further questions based on your answers. You will be given information as you need it based on the answers you supply.

There are a few details you should be aware of before using this wizard:

• The IBM Developer Kit for OS/390, Java™ 2 Technology Edition runs on OS/390 Version 2 Release 8 or higher.

• This wizard will not work correctly if you enter it on any page but the first (where you are now), so do not bookmark any page within the wizard.

• On any page, you can click on the ‘?’ to read help or related information.

Chapter 8. Java for OS/390 49

Chapter 9. HTTP server

This chapter helps you set up the Web server configuration file to be used with a single server. This server is intended to run in normal mode only (no SSL encryption). For detailed hints about customization and usage of the IBM HTTP Server for OS/390, refer to IBM HTTP Server for OS/390 Customization and Usage, SG24-6205.

You can configure the server using the remote Configuration and Administration forms or by editing the configuration file. The following descriptions are based on the use of a text editor, instead of the remote tool, for configuration of the IBM HTTP Server 5.3 for OS/390. For information on how to use the Configuration and Administration forms, see IBM HTTP Server for OS/390, Planning, Installing, and Using, SC31-8690.

We assume that:

• OS/390 UNIX is set up.

• TCP/IP is running.

• The code for the HTTP server code has been SMP/E installed as outlined in the Program Directory for OS/390, GI10-4001. The SMP/E installation will place the HTTP server code in the directory /usr/lpp/internet.

9.1 Basic configuration

Our proposed “Quick and Proper” customization consists of the following steps:

1. Define the Web server working directory structure.

2. Copy the Web server configuration files.

3. Prepare the Web server configuration files.

4. Define the security environment.

5. Define the Web server started procedure.

6. Authorize the started procedure to RACF.

7. Create a homepage.

8. Start the Web server.

The details for these steps are presented in the following sections.


9.1.1 Define the Web server working directory structureWe suggest you use a directory structure similar to the one outlined in Figure 29.

Figure 29. Suggested web server working directory structure

The directory structure outlined above should contain some separate HFSs and serves the following purposes:

/web root directory for Web servers/web/server1 working directory for server1

small HFScontains all Web server configuration files

.../pub directory for Web content (HTML etc.)extra HFS

.../sec directory for security-related files (certificates, group files etc.)

.../logs contains all Web server logsextra HFS

.../reports contains all Web server reporting filesextra HFS

.../ocgi directory for CGI programsextra HFS if needed

.../servlets directory for Java Servletsextra HFS if needed

.../rex directory for GWAPI REXXextra HFS if needed

During the residency we defined /web/apple, /web/bean, /web/candy, and so on. There is no deep meaning behind the names we used; they allow an easy identification of the Web servers. Each of these Web servers had its own start procedure, named WEBAPPLE, WEBBEAN and so forth.

Why did we choose to use so many separate HFSs? The reasons were:

• We found separate HFSs more convenient to maintain.

/web/server1/pub/sec/logs/reports/ocgi/servlets/rexx

/web/server2/pub...


• Once set up, some HFSs can be mounted READ ONLY for security reasons, if desired.

• At least the /logs, the /reports and the /pub directory should reside in an extra HFS because of their unpredictable size.

Our reasons for choosing this particular directory structure were:

• In several projects at the ITSO and with customers we found this a good general fitting structure.

• At the ITSO in Poughkeepsie we run multiple Web servers concurrently and, more often than not, on different software levels. The structure helps to manage them easily and keep the configurations and configuration files separate.

• Maintenance, which normally will overwrite files in /usr/lpp/internet, does not affect the individual Web server configuration files but becomes effective for all Web servers.

9.1.2 Copy the Web server configuration filesCopy the Web server configuration files into the individual Web server working directory. Copy the files shown in Figure 30 from the /usr/lpp/internet/samples/config to /web/server1, /web/server2, and so on.

Figure 30. Web server configuration files

9.1.3 Prepare the Web server configuration filesInitially, only two configuration files need to be changed:

• httpd.conf • httpd.envvars

9.1.3.1 Customize httpd.confhttpd.conf is the Web server main configuration file.

httpd.conf - Web Server main configuration fileshttpd.envvars - Web Server environment variablesmvsds.conf - MVSDS function config fileics_pics.conf - PICS Rating filejavelin.conf - Web Traffic Express (Proxy) config filesocks.conf - another Proxy config filelgw_fcgi.conf - Fast CGI config fileIMWSendMail.cfg - "old" SendMail config file

Chapter 9. HTTP server 53

You may choose to modify it by using the Remote Server Configuration Dialog or you may modify the file using OEDIT, like we did. Remote Server Configuration allows you to modify your Web server by using a Web connection and Java applet-enhanced Web pages.

Configuration directive details can be found as comments in httpd.conf, or in IBM HTTP Server for OS/390, Planning, Installing, and Using Version 5.3, SC31-8690 (suffix 05).

The httpd.conf configuration example in Figure 31 prepares for a generally accessible Web server in accordance with our suggested structure. We suggest that you never overwrite a parameter, but rather repeat it on a new line, comment the original line, and change the repeated line. Only the minimum changes necessary are shown.

InstallPath /usr/lpp/internet <-default

# ServerRoot server_root <-defaultServerRoot /web/apple <-changed

Port 80 <-default.Change the Port directive if you like to run multipleWeb servers on the same IP address.The port can also be defined with the -p parameter inthe Web server started procedure

# UserId %%CLIENT%% <-defaultUserId PUBLIC <-changed to allow genereal

(anonymous) access without user identification

# PidFile /usr/lpp/internet/server_root/httpd-pid <-defaultPidFile /web/server1/httpd-pid <-changed# AccessLog /usr/lpp/internet/server_root/logs/httpd-log <-default# AgentLog /usr/lpp/internet/server_root/logs/agent-log <-default# RefererLog /usr/lpp/internet/server_root/logs/referer-log <-default# ErrorLog /usr/lpp/internet/server_root/logs/httpd-errors <-default# CgiErrorLog /usr/lpp/internet/server_root/logs/cgi-error <-default

AccessLog /web/apple/logs/httpd-log <-changedAgentLog /web/apple/logs/agent-log <-changedRefererLog /web/apple/logs/referer-log <-changedErrorLog /web/apple/logs/httpd-errors <-changedCgiErrorLog /web/apple/logs/cgi-error <-changed

# AccessLogArchive none <-default# ErrorLogArchive none <-default


AccessLogArchive purge <-changedErrorLogArchive purge <-changed

Purge the logs. Condition defined later.# AccessLogExpire 0 <-default# ErrorLogExpire 0 <-defaultAccessLogExpire 10 <-changedErrorLogExpire 10 <-changed

Keep the last 10 logs.

# AccessReportRoot /usr/lpp/internet/server_root/pub/reports <-defaultAccessReportRoot /web/apple/reports <-changed

# ReportDataArchive none <-defaultReportDataArchive purge <-changed

Purge the reports. Condition defined later.

# ReportDataExpire 0 <-defaultReportDataExpire 40 <-changed

Keep the reports for 40 days.

# LoggingReportingProgram /usr/lpp/internet/sbin/htlogrep <-default# LoggingReportingProgramOptions -c/etc/httpd.conf <-defaultLoggingReportingProgram /usr/lpp/internet/sbin/htlogrep <-changedLoggingReportingProgramOptions -c/web/apple/httpd.conf <-changed

Enable htlogrep reporting# >>> The following 4 statements have been disabled# >>> (commented) to disable Web Traffic Express (WTE),# >>> a special Proxy function because we do not use them now.# >>> Performance/Resource option.

# ServerInit /usr/lpp/internet/bin/Jav_dll.so:Javelin_init# Service /cgi-bin/dogc.icapi /usr/lpp/internet/bin/Jav_dll.so:doGC# PreExit /usr/lpp/internet/bin/Jav_dll.so:Javelin_preFilter# Enable ICSERRORLOG /usr/lpp/internet/bin/Jav_dll.so:Javelin_errorLog

# >>> The following 3 statements have been disabled# >>> (commented) to disable the WebSphere Application Server# >>> (WebAS) functions because we do not use them now.# >>> WebAS is the Java servlet engine for the Web server.# >>> Enabling this options also reqires WebAS to be configured.

# Service /*.jhtml /usr/lpp/WebSphere/AppServer/lib/libadpter.so:AdapterService# Service /*.shtml /usr/lpp/WebSphere/AppServer/lib/libadpter.so:AdapterService# Service /servlet/* /usr/lpp/WebSphere/AppServer/lib/libadpter.so:AdapterService

# >>> Modify the following exec and pass statements

Pass /admin-bin/webexec/* /usr/lpp/internet/server_root/admin-bin/webexec/*


Exec /cgi-bin/* /usr/lpp/internet/server_root/admin-bin/*Exec /admin-bin/* /usr/lpp/internet/server_root/admin-bin/*Exec /Docs/admin-bin/* /usr/lpp/internet/server_root/admin-bin/*

Exec /my-cgi-bin/* /web/apple/ocgi/* <-add for your own CGIs

Pass /icons/* /usr/lpp/internet/server_root/icons/*Pass /Admin/*.jpg /usr/lpp/internet/server_root/icons/Admin/*.jpgPass /Admin/*.gif /usr/lpp/internet/server_root/icons/Admin/*.gifPass /Admin/*.html /usr/lpp/internet/server_root/icons/Admin/*.htmlPass /Docs/* /usr/lpp/internet/server_root/Docs/*

# The following line is for WTE (Proxy).# Pass /reports/javelin/* ... /usr/lpp/internet/server_root/pub/reports/javelin/*

Pass /reports/java/* /usr/lpp/internet/server_root/pub/reports/java/*# Pass /reports/* /usr/lpp/internet/server_root/pub/reports/*Pass /reports/* /web/apple/reports/*Pass /img-bin/* /usr/lpp/internet/server_root/img-bin/*

# The following three lines are for CAServlet that req’s WebAS# Pass /CAServlet/* /usr/lpp/internet/server_root/CAServlet/C/*# Pass /ServletExpress/resources/* /usr/lpp/internet/server_root/CAServlet/C/*# Pass /ServletExpress/* /usr/lpp/WebSphere/AppServer/web/*

# *** ADD NEW PASS RULES HERE ***# Pass /* /usr/lpp/internet/server_root/pub/*Pass /Server/* /usr/lpp/internet/server_root/pub/*Pass /* /web/apple/pub/*

Figure 31. httpd.conf definitions

Figure 31 notes:

• The default setup and mapping rules define /usr/lpp/internet/server_root/pub/Frntpage.html to be the primary homepage.

• The changed setup and mapping rules define /web/apple/pub/index.html to be the primary homepage.

• Frntpage.html (and with it the Remote Server Configuration Dialog) can still be reached using the URL http://servername/Server

• If you decide not to use the Remote Server Configuration Dialog and some of the IBM deliveries like status panels, you may comment most of the mapping statements.

Pass /admin-bin/webexec/* /usr/lpp/internet/server_root/admin-bin/webexec/*Exec /cgi-bin/* /usr/lpp/internet/server_root/admin-bin/*Exec /admin-bin/* /usr/lpp/internet/server_root/admin-bin/*Exec /Docs/admin-bin/* /usr/lpp/internet/server_root/admin-bin/*Pass /icons/* /usr/lpp/internet/server_root/icons/*Pass /Admin/*.jpg /usr/lpp/internet/server_root/icons/Admin/*.jpgPass /Admin/*.gif /usr/lpp/internet/server_root/icons/Admin/*.gifPass /Admin/*.html /usr/lpp/internet/server_root/icons/Admin/*.htmlPass /Docs/* /usr/lpp/internet/server_root/Docs/*


Pass /img-bin/* /usr/lpp/internet/server_root/img-bin/*Pass /Server/* /usr/lpp/internet/server_root/pub/*

• You may keep the “original” Frntpage.html, but you should certainly cache your homepage, including all the images.

9.1.3.2 Customize httpd.envvarsThe next file to customize is httpd.envvars, which is the Web server’s global variable file. The httpd.envvars example file delivered with the Web server is Java-enabled to configure the Web server with the IBM WebSphere Application Server. We suggest that you keep the Java definitions for later use even if you do not need them for a general Web server. Figure 32 shows an httpd.envvars example file.

Figure 32. httpd.envvars definitions

Note: If you enable the Web server for Java, make sure that the modules in <JAVAHOME>/lib/mvs/native_threads have the program control flag on. Otherwise you will get a dirty environment.

All statements must be coded without line feeds. To make them more visible, we broke them up and added a -- cont --> (continuation) sign.

9.1.4 Define the security environment The IBM HTTP Server requires some setup regarding security (RACF). The following steps are necessary to enable a general Web server:

1. Create the Web server Administration ID (WEBADM) and its RACF group.

2. Create the Web server’s own user ID (WEBSRV).

PATH=/usr/lpp/internet/bin:/usr/lpp/internet/sbin:-- cont --> /usr/lpp/java16p/J1.1/bin:/bin:.:/usr/sbin:-- cont --> /usr/lpp/ldap/binSHELL=/bin/shTZ=EST5EDTLANG=CLC_ALL=en_US.IBM-1047NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lpp/internet/%L/%N:-- cont --> /usr/lpp/ldap/lib/nls/msg/%L/%NLIBPATH=/usr/lpp/internet/bin:/usr/lpp/internet/sbin:-- cont --> /usr/lpp/java16p/J1.1/lib/mvs/native_threads:-- cont --> /usr/lpp/ldap/libCLASSPATH=.:/usr/lpp/java16p/J1.1/lib/classes.zipSTEPLIB=CURRENT


3. Permit WEBSRV to BPX.DAEMON and BPX.SERVER FACILITY classes (and make sure they are activated).

4. Create the anonymous access user ID (PUBLIC) and its RACF group.

5. Turn on program control. Program control is not needed to prevent access to programs (in the classical RACF sense), but to indicate that these libraries are authorized libraries.

Security experts may suggest using other user IDs and groups than the published ones to make it more difficult for hackers. We suggest that you stay with these names if this is your first installation, and switch them later when you have gained a complete understanding of all the dependant security mechanisms (like PROTECT statements in httpd.conf).

Figure 33 displays the RACF commands required to set up a Web server called CANDY.

Figure 33. Web server security setup

ADDGROUP IMWEB OMVS(GID(205))ADDGROUP EXTERNAL OMVS(GID(999))ADDUSER WEBADM DFLTGRP(IMWEB) OMVS(UID(206) HOME('/usr/lpp/internet')... PROGRAM('/bin/sh'))

ADDUSER WEBSRV DFLTGRP(IMWEB) OMVS(UID(0) HOME('/usr/lpp/internet')... PROGRAM('/bin/sh'))

ADDUSER PUBLIC DFLTGRP(EXTERNAL) OMVS(UID(998) HOME('/')... PROGRAM('/bin/sh'))

RDEFINE SURROGAT BPX.SERVER.WEBADM UACC(NONE)RDEFINE SURROGAT BPX.SERVER.PUBLIC UACC(NONE)PERMIT BPX.DAEMON CLASS(FACILITY) ID(WEBSRV) ACCESS(READ)PERMIT BPX.SERVER CLASS(FACILITY) ID(WEBSRV) ACCESS(UPDATE)PERMIT BPX.SRV.WEBADM CLASS(SURROGAT) ID(WEBSRV) ACCESS(READ)PERMIT BPX.SRV.PUBLIC CLASS(SURROGAT) ID(WEBSRV) ACCESS(READ)

RALTER PROGRAM * ADDMEM('SYS1.SCEERUN'/'volser'/NOPADCHK) UACC(READ)RALTER PROGRAM * ADDMEM('CBC.SCLBDLL'/'volser'/NOPADCHK) UACC(READ)RALTER PROGRAM * ADDMEM('SYS1.LINKLIB'/'volser'/NOPADCHK) UACC(READ)SETR RACLIST(FACILITY) REFRESHSETR WHEN(PROGRAM) REFRESHSETR CLASSACT(SURROGAT) if not already done


9.1.5 Define the Web server started procedureThe started procedure for the Web server needs to be set up as shown in Figure 34.

Figure 34. Web server started procedure setup - CANDY server

9.1.6 Authorize the started procedure to RACFAfter the Started Procedure is defined, you need to authorize it to RACF and refresh the STARTED class. This is shown in Figure 35.

Figure 35. Authorizing the Web server started procedure

//WEBCANDY PROC P1='-B',// P2='-r /web/candy/httpd.conf',// P3='-p 8100 -vv',// LEPARM='ENVAR("_CEE_ENVFILE=/web/candy/httpd.envvars")'//*--------------------------------------------------------//* -vv # VERY VERBOSE trace to stderr//* -p nnnn # Port nnn (default 80)//* -r /etc/httpd.imwebbox.icssec # RuleFile path/name//*--------------------------------------------------------//WEBSRV EXEC PGM=IMWHTTPD,REGION=0K,TIME=NOLIMIT,// PARM=('&LEPARM/&P1 &P2 &P3')//SYSIN DD DUMMY//OUTDSC DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SYSOUT DD SYSOUT=*//SYSERR DD SYSOUT=*//STDOUT DD SYSOUT=*//STDERR DD SYSOUT=*//CEEDUMP DD SYSOUT=*

RDEFINE STARTED WEBCANDY.** STDATA(USER(WEBSRV))SETR RACLIST(STARTED) REFRESH

We called our started procedure WEBCANDY. It's up to you to choose a suitable name.


9.1.7 Create a homepageTo begin with, create a small homepage in your directory for Web content /web/candy/pub and call it index.html. Figure 36 shows a simple homepage to get you started.

Figure 36. Sample homepage

9.1.8 Start the Web serverYou can now start your Quick and Proper Web server by starting the procedure.

9.1.9 Test the Web serverUsing a browser, you can test the Web server with the home page you just created. Your browser should display content similar to the Figure 37.

Figure 37. Sample homepage viewed on the Web

<html><head><title>HTTP 5.3 Project - The Candy Web Server on Port 8105</title><head><body bgcolor="FFFFFF"><h1>Welcome to the CANDY Web server on port 8105</h1><p>This is IBM HTTP Web Server V5.3.<hr>Follow this link to access the<a href="/Server/">Remote Server Administration</a>.</html>


9.2 Configuring the Web server to host an application server

In order to instantiate an instance of the application server within a Web server address space, you must:

• Add the following Web server directives to the httpd.conf configuration file of the Web server that will be hosting an IBM WebSphere Application Server instance to provide the Web server with the entry point to the application server’s initialization, request processing, and exit routines. These routines exist as entry points init_exit, service_exit, and term_exit, respectively, within the was302plugin.so DLL. The was302plugin.so DLL is found within the applicationserver_root/AppServer/bin directory.

ServerInit applicationserver_root/AppServer/bin/was302plugin.so:init_exit applicationserver_rootService /webapp/examples/*applicationserver_root /AppServer/bin/was302plugin.so:service_exitServerTerm applicationserver_root/AppServer/bin/was302plugin.so:term_exit

Note: In this example, the ServerInit , Service, and ServerTerm directives are split for printing purposes. In the actual file, each directive is on a single line.

• Make sure that the JAVA_HOME environment variable (as well as any other hard-coded pointers to the JDK libraries) point to the Java Development Kit (JDK) that is required by the application server. This variable is contained in the hosting Web server’s envvars file. For example, if you’ve installed the JDK in /usr/lpp/java/, before starting a hosting Web server, set JAVA_HOME=/usr/lpp/java/J1.1.

9.3 Starting the application server

At execution time, an application server instance will be instantiated within any Web server address space in which an application server plugin routine has been properly configured. Both the Web server and the application server issue status messages to the standard error (stderr) log file to indicate their progress throughout their initialization process. The following depicts the content of the stderr log file upon successful initialization of the application server. Successful completion of initialization is indicated by messages in the log file from both the application server and the hosting Web server, indicating that the server is ready.

............This is IBM HTTP Server web_server_type

............Built on date at time .

............Started at day date time year .

............Running as "your_server_name ",UID:OS/390_UNIX_UID ,GID:OS/390_group_ID .


IMW0234I Starting..httpd/u/your_server_name >............This is IBM WebSphere Application Server for OS/390 3.02 built onOS/390 Version 2 release_number ,WAS Service Level service_level_number............Built on date at time .............Started at day date time year............Started Queue State =HTTPD............Started Server Type =STANDALONE............WAS Startup Parameter --Install Root =/applicationserver_root............WAS Startup Parameter --Configuration file =applicationserver_root /AppServer/proper............WAS Startup Parameter --Bootstrap file =applicationserver_root /AppServer/properties/default_global.properties............WAS Startup Parameter --JDK install directory (JAVA_HOME)=/usr/lpp/java/J1.1.8/J1.1............WAS Startup Parameter --Plugin Logging Level =WARNING............WAS Startup Parameter --Plugin Logging Directory =/your_server_name /logs............WAS generated CLASSPATH follows:............CLASSPATH entry:applicationserver_root /AppServer/lib............CLASSPATH entry:applicationserver_root /AppServer/lib/databeans.jar............CLASSPATH entry:applicationserver_root /AppServer/lib/ibmwebas.jar............CLASSPATH entry:applicationserver_root /AppServer/lib/jsp10.jar............CLASSPATH entry:applicationserver_root /AppServer/lib/lotusxsl.jar............CLASSPATH entry:applicationserver_root /AppServer/lib/servlet.jar............CLASSPATH entry:applicationserver_root /AppServer/lib/xml4j.jar............CLASSPATH entry:applicationserver_root /AppServer/lib/x509v1.jar............CLASSPATH entry:applicationserver_root /AppServer/properties............CLASSPATH entry:applicationserver_root /AppServer/classes............CLASSPATH entry:/usr/lpp/java/J1.1.8/J1.1/lib/classes.zip............CLASSPATH entry:/usr/lpp/java/J1.1.8/J1.1/lib/RACF.jar............CLASSPATH entry:/usr/lpp/java/J1.1.8/J1.1/lib/jndi.jar............End of generated CLASSPATH............WAS Startup Parameter --Servlet Engine Logging Level =WARNING............WAS Startup Parameter --Servlet Engine Logging Level =WARNING............WAS Startup Parameter --Servlet Engine Logging Directory =/your_server_name /logs............WAS Startup Parameter --Servlet Engine Working Directory =/your_server_name /work............IBM WebSphere Application Server native plugin initialization went OK :-)IMW0235I Server is ready.

Message IMW0235I indicates that your Web server has successfully initialized. The preceding “smiley-face” message indicates that the application server successfully initialized. It is possible to get message IMW0235I without the preceding smiley-face message if the application server did not successfully initialize. If you do not receive message IMW0235I, an error has occurred.

9.3.1 Invoking the Installation Verification ProgramOnce the Application Server is started, you can verify the install by entering the following URL from a browser to invoke the IBM-provided Installation Verification Program:

http://your.server.name /webapp/examples/index.html

You can then select one of the examples from the screen shown in Figure 38 on page 63 to verify that the Application Server has properly installed.


Figure 38. WebSphere Application Server example page


Chapter 10. DB2 enablement

This chapter focuses on how to enable DB2 for OS/390 Component Broker. It also describes how to set up the system management database that OS/390 Component Broker uses to manage servers.

It is assumed that DB2 for OS/390 is already installed, set up, and initialized in your installation environment. In our testing, we worked with DB2 UDB for OS/390 Version 6 and OS/390 Component Broker for WAS 3.02 EE.

The topics included in this chapter are:

• What you need to prepare in your DB2 installation

• The DB2 Call Level Interface and initialization file

• Guidelines to use JDBC/SQLJ in an OS/390 Component Broker environment

• How to define the system management database

• How to grant access to the system management database.

For information about DB2 installation and customization, refer to DB2 UDB for OS/390 Version 6 Installation Guide, GC26-9008, and Program Directory for DB2 UDB for OS/390 Version 6.

10.1 DB2 considerations

Before configuring DB2 for Component Broker on OS/390, you need to perform the following steps:

• Check the DB2 subsystem name.

You need to specify the DB2 subsystem name in the environment file that is used by the OS/390 Component Broker components.

• Increase the BP32K buffer pool to a minimum of 100.

• Check the size of your DB2 for OS/390 logs.

You may have to enlarge them because of the number of transactions that OS/390 Component Broker generates.

• Check the 32K temporary work space for DB2 for OS/390.

Since the OS/390 Component Broker uses the 32K temporary work space, you have to allocate the work space if your DB2 installation does not have it. Run the job DSNTIJTM to allocate the work space and make sure you allocate it large enough.


• Take note that OS/390 Component Broker uses row-level locking and Type 2 indexes.

10.1.1 DB2 subsystem nameThe DB2 subsystem name must be specified in the OS/390 Component Broker file, specifically the environment file.

To find the DB2 subsystem name, look at IEFSSNxx member of the PARMLIB data set. In our testing environment, we use SYS1.PARMLIB(IEFSSN00), which definition is shown as follows:

SUBSYS SUBNAME(DBS3) /* DB2 6.1 */INITRTN(DSN3INI)INITPARM('DSN3EPX,=DBS3,S')

So, the DB2 subsystem name that we use is DBS3.

Once you configure the OS/390 Component Broker, you need to update the environment variables file used by the Component Broker servers. You have to modify the variable that requires DB2 subsystem name specification:

SYS_DB2_SUB_SYSTEM_NAME=<your_db2_subsystem_name>

10.1.2 Increase the buffer pool sizeYou are required to increase the BP32K buffer pool size. You have to set the BP32K buffer pool to at least a size of 100.

First, check the size that has been set in your DB2 installation. You can use DB2I to enter the DB2I PRIMARY OPTION MENU, and select the DB2 COMMAND function. Then enter the following command:

-DISPLAY BUFFERPOOL (BP32K)


Figure 39. Output of the display buffer pool command

Figure 39 shows that the current size of the BP32K buffer pool is 24. Therefore, we need to increase the size.

Use the following command to change the BP32K buffer pool size:

-ALTER BUFFERPOOL(BP32K) VPSIZE(size)

So, if you want to increase the BP32K buffer pool size to 100, issue the following command in the DB2 COMMAND interface:

-ALTER BUFFERPOOL(BP32K) VPSIZE(100)

Once you successfully set the BP32K buffer pool size to 100, you will get a notification as follows:

DSNB522I =DBS3 VPSIZE FOR BP32K HAS BEEN SET TO 100DSN9022I =DBS3 DSNB1CMD '-ALTER BUFFERPOOL' NORMAL COMPLETION

10.2 DB2 Call Level Interface

The Call Level Interface (CLI) is a prerequisite for LDAP. The CLI packages and plan are installed during the installation of DB2. You need to bind the packages and plan if they are not bound yet in your DB2 installation process.

Note that in DB2 UDB for OS/390 Version 6, DB2 CLI is renamed DB2 ODBC to align with common industry terminology. This is a change in name only; the support and function remain the same.

DSNB401I =DBS3 BUFFERPOOL NAME BP32K, BUFFERPOOL ID 80, USE COUNT 0DSNB402I =DBS3 VIRTUAL BUFFERPOOL SIZE = 24 BUFFERS

ALLOCATED = 0 TO BE DELETED = 0IN-USE/UPDATED = 0

DSNB406I =DBS3 VIRTUAL BUFFERPOOL TYPE -CURRENT = PRIMARYPENDING = PRIMARY

PAGE STEALING METHOD = LRUDSNB403I =DBS3 HIPERPOOL SIZE = 0 BUFFERS, CASTOUT = YES

ALLOCATED = 0 TO BE DELETED = 0BACKED BY ES = 0

DSNB404I =DBS3 THRESHOLDS -VP SEQUENTIAL = 80 HP SEQUENTIAL = 80DEFERRED WRITE = 50 VERTICAL DEFERRED WRT = 10,0PARALLEL SEQUENTIAL = 50 ASSISTING PARALLEL SEQT= 0

DSNB408I =DBS3 NO DETAIL STATISTICS AVAILABLE FOR BUFFER POOL BP32KDSN9022I =DBS3 DSNB1CMD '-DISPLAY BUFFERPOOL' NORMAL COMPLETION***

Chapter 10. DB2 enablement 67

To use the CLI, you need to define the CLI initialization file. This file, either an MVS data set or an HFS file, is a file that stores a set of values for DB2 CLI configuration options. As an MVS data set, the initialization file can be either fixed or variable length.

The DB2 CLI initialization file is read at application runtime.The initialization file will be referred to by the LDAP server or the Component Broker servers, by specifying either a DSNAOINI DD card statement or defining DSNAOINI of the environment variables file.

Figure 40 is an example of a CLI initialization file.

Figure 40. CLI initialization file

In the CLI initialization file, you need to update the following keywords:

• MVSDEFAULTSSID = ssid

The MVSDEFAULTSSID keyword specifies the default DB2 subsystem to which the application is connected when invoking the SQLAllocEnv function. You must specify a 4-character name of an installed DB2 subsystem.

• MVSATTACHTYPE = CAF | RRSAF

The MVSATTACHTYPE keyword is used to specify the DB2 for OS/390 attachment type that DB2 CLI uses to connect to the DB2 for OS/390 address space. This parameter is ignored if the DB2 CLI application is running as a DB2 for OS/390 stored procedure. In that case, DB2 CLI uses the attachment type that was defined for the stored procedure.

; This is a comment line ...; Example COMMON stanza[COMMON]MVSDEFAULTSSID=<DB2_ssn>TRACE=0TRACE_BUFFER_SIZE=2000000TRACE_NO_WRAP=0CLITRACE=0;TRACEFILENAME=DD:CLITRACE

; Example SUBSYSTEM stanza for V42A subsystem[<DB2_ssn>]MVSATTACHTYPE=RRSAFPLANNAME=DSNACLI

; DATA SOURCE stanza for your data source[<db2_location_name>]AUTOCOMMIT=0CONNECTTYPE=1


CAF: DB2 CLI uses the DB2 for OS/390 call attachment facility (CAF).

RRSAF: DB2 CLI uses the DB2 for OS/390 Recoverable Resource Manager Services attachment facility (RRSAF).

In our testing, we used RRSAF as the attachment type.

• PLANNAME = planname

The PLANNAME keyword specifies the name of the DB2 for OS/390 PLAN that was created during installation. A PLAN name is required when initializing the application connection to the DB2 for OS/390 subsystem, which occurs during the processing of the SQLAllocEnv call.

If no PLANNAME is specified, the default value DSNACLI is used.

• <db2_location_name>

db2_location_name refers to the LOCATION keyword that is contained in the distributed data facility (DDF) definition. The DDF is included in your bootstrap data set (BSDS).

To find the DB2 location name, run the DB2 utility, DSNJU004, using the same data sets specified in the BSDS1 and BSDS2 DD statement in the DB2 started task JCL procedure. This utility will list the DB2 location name at the very bottom of the output.

If you use DB2 for OS/390 Version 5, see DB2 for OS/390 Version 5 Call Level Interface Guide and Reference, SC26-8959 (suffix 03), for more information on CLI file keywords and settings. And for DB2 UDB for OS/390 Version 6, refer to DB2 UDB for OS/390 Version 6 ODBC Guide and Reference, GC26-9011, for more information on ODBC file keywords and settings.

The OS/390 Component Broker provides a sample of the CLI initialization file to be used while you are configuring an LDAP server for the OS/390 Component Broker.

Once you copy the sample file, you need to modify the file by changing the default name of the DB2 subsystem and the name of the data sources in your DB2 installation options. In addition, you have to change the setting on the MVSATTACHTYPE keyword to RRSAF to indicate that the RRS Attach Facility is to be used to connect to the DB2 for OS/390 address space.

“Configuring LDAP server” on page 74 describes how to set up CLI for LDAP server for OS/390 Component Broker.


10.3 Java Database Connectivity and static SQL

Java Database Connectivity (JDBC) is an interface for Java application programs to access a relational database by using dynamic SQL. Meanwhile, static SQL (SQLJ) provides support for embedded static SQL in Java applications and applets. DB2 for OS/390 supports both these application interfaces.

If you intend to use JDBC and SQLJ in the OS/390 Component Broker area, consider the following guidelines:

• Use the RRS Attachment Facility (RRSAF), not the CAF.

• Set the DSNAOINI environment variable to point to the DSNAONI file.

• You cannot use multi-context support.

• Your application must turn AutoCommit off.

See DB2 UDB for OS/390 V6 Application Programming Guide and Reference for Java, SC26-9018, for complete information about JDBC and SQLJ.

10.4 Defining OS/390 Component Broker system management database

This section shows you how to set up the system management database that OS/390 Component Broker uses to manage its servers.

Before you begin to set up the OS/390 Component Broker system management database, you must have Resource Recovery Services (RRS) and DB2 for OS/390 set up and initialized. Refer to Chapter 5, “Resource Recovery Services” on page 39 to enable RRS.

Perform the following steps to define the OS/390 Component Broker system management database:

1. Create the Component Broker system management database that includes storage group, database, table spaces, tables, and indexes.

The BBO.SBBOJCL(BBOMCRDB) is a sample JCL to create the system management database provided by the OS/390 Component Broker. Copy and modify the file as your DB2 installation options, then submit the job from a user ID with DB2 for OS/390 SYSADM authority.


2. Bind Component Broker series DB2 packages into DB2.

The BBO.SBBOJCL(BBOBIND) is sample JCL to install Component Broker series DB2 Packages into DB2 for Component Broker series functions. Copy and modify the file as your DB2 installation options, then submit the job from a user ID with DB2 for OS/390 SYSADM authority.

Note: In BBOBIND, the DBRMLIB must refer to DBRMLIB provided by OS/390 Component Broker.

“Bind system management data base of OS/390 Component Broker” on page 91 shows the DB2 bind commands that we used to bind Component Broker series packages.

10.5 Granting access to the system management database

Once you finish setting up the system management database, you need to grant access authority to the database you created. Refer to “Authorization for OS/390 Component Broker” on page 85 to correspond the user IDs used by OS/390 Component Broker regions that will have DB2 access authority.

Make a copy of BBO.SBBOJCL(BBOCBGRT) and modify it according to the comments in the file. Submit the job from a user ID with DB2 for OS/390 SYSADM authority.

The sample BBOCBGRT will grant access as following:

• Grant the following authority to general users:

GRANT EXECUTE ON PACKAGE CBSERVER_PKG.* TO PUBLIC;

• Grant the following authorities to the user IDs under which the Daemon server runs:

GRANT EXECUTE ON PACKAGE CBDAEMON_PKG.* TO daemon_racf_userid;GRANT EXECUTE ON PACKAGE CBSYSMGT_PKG.* TO daemon_racf_userid;

where daemon_racf_userid is the RACF user ID associated with Daemon server region.

a. OS/390 Component Broker uses BBO as the prefix for its DB2 for OS/390 tables. You cannot change it.

b. In BBOMCRDB, the DBRMLIB must refer to the one used in your DB2 installation.

Note


• Grant the following authorities to the user IDs under which the System Management server runs and to an admin user ID:

GRANT EXECUTE ON PACKAGE CBSYSMGT_PKG.* TO sysm_racf_userid;GRANT EXECUTE ON PACKAGE CBSYSMGT_PKG.* TO cb_admin;

where sysm_racf_userid is the RACF user ID associated with System Management server region and cb_admin is the RACF user ID to be used as Component Broker administrator.

• Grant the following authorities to the user IDs under which the Naming server runs:

GRANT EXECUTE ON PACKAGE CBLIFECYCLE_PKG.* TO naming_racf_userid;GRANT EXECUTE ON PACKAGE DSNAOCLI.* TO naming_racf_userid;GRANT SELECT ON SYSIBM.SYSTABLES TO naming_racf_userid;GRANT SELECT ON SYSIBM.SYSCOLUMNS TO naming_racf_userid;GRANT DBADM ON DATABASE BBOLDAP TO naming_racf_userid;

where naming_racf_userid is the RACF user ID associated with the Naming server region.

• Grant the following authorities to the user IDs under which the Interface Repository server runs:

GRANT EXECUTE ON PACKAGE DSNAOCLI.* TO intrp_racf_userid;GRANT SELECT ON SYSIBM.SYSTABLES TO intrp_racf_userid;GRANT SELECT ON SYSIBM.SYSCOLUMNS TO intrp_racf_userid;GRANT DBADM ON DATABASE BBOLDAP TO intrp_racf_userid;

where intrp_racf_userid is the RACF user ID associated with Interface Repository server region.

See “Authorization for OS/390 Component Broker” on page 85 for the user IDs that are used for Component Broker control regions and server regions. “SQL to grant system management database of Component Broker” on page 94 shows you the SQL statement we used to grant access to our Component Broker system management database.

The samples supplied with the OS/390 Component Broker use traditional DB2 for OS/390 security. If you use RACF protection for DB2 for OS/390, that is DSNR class, and secondary authorization IDs, then you have to create scripts of your own for all the jobs that grant usage authorities to plan and packages.


Chapter 11. LDAP enablement

The OS/390 Component Broker uses DB2 for OS/390 for system management and instance management. The Component Broker servers, specifically the Naming server and Interface Repository server, use DB2 for OS/390 through LDAP. The Naming server uses LDAP for its directory. Using the LDAP functionality gives the Naming server efficient directory services. Before running the Naming server, an LDAP daemon has to be initialized, primed or populated, and then started. Once the LDAP daemon is started, it runs in the background, receiving LDAP API calls.

Controlling access to information in the LDAP server is performed by setting up Access Control Lists (ACLs). ACLs provide a means to protect information stored in an LDAP directory. Administrators use ACLs to restrict access to different portions of the directory, or to specific directory entries. The LDAP directory entries are related to each other by a hierarchical tree structure. Each directory entry, or object, contains the entry’s distinguished name, a set of attributes, and their corresponding values. ACLs and groups may be created and managed through the LDAP Directory Server Access Control List and Group Administration Utility.

All procedures and examples documented here are based and tested on OS/390 V2R10 Secure Way Security Server LDAP, OS/390 Component Broker for WAS 3.02 EE and DB2 UDB for OS/390 Version 6.

This chapter focuses on the customizing needed to enable the LDAP server for OS/390 Component Broker. It includes details on the following topics:

• Configuring an LDAP server for OS/390 Component Broker

• RACF authorization for LDAP

• DB2 authorization access to LDAP databases

• LDAP started task procedure

• Testing the LDAP server

For information about customization of LDAP server for OS/390 Component Broker, refer to OS/390 Security Server LDAP Server Administration and Usage Guide, SC24-5861, and OS/390 Component Broker Planning and Installation Guide GA22-7325.


11.1 Setting up the LDAP server for OS/390 Component Broker

This section describes the issues you must consider before you configure an LDAP server, and discusses the setup that needs to be performed to configure an LDAP server for OS/390 Component Broker.

11.1.1 Configuration considerationsFollow these guidelines before you configure the LDAP server:

• You must have RRS and DB2 for OS/390 set up and initialized before you configure LDAP. See Chapter 5, “Resource Recovery Services” on page 39 and Chapter 10, “DB2 enablement” on page 65 for enablement of DB2 for OS/390 Component Broker.

• If you already have an LDAP server on your system, you must create a separate LDAP server exclusively for OS/390 Component Broker. The reasons are:

- The data you put in the database is used only by the OS/390 Component Broker and accessible through OS/390 Component Broker services.

- In addition, an exclusive LDAP server helps you keep the OS/390 Component Broker databases synchronized.

• Keep the OS/390 Component Broker LDAP tables separate from other LDAP tables. Then you can back up the OS/390 Component Broker LDAP tables with the OS/390 Component Broker system management database as a unit. Also, if necessary, it is easier to restore the backup without interfering with the LDAP tables used by other applications.

• Use a user ID that has DB2 for OS/390 SYSADM authority to submit the jobs while you are working with DB2 for OS/390.

• Refer to the comments in the JCL or files provided by OS/390 Component Broker while you are updating the JCL and files to match your DB2 for OS/390.

11.1.2 Configuring LDAP serverThis section describes how to configure an LDAP server for OS/390 Component Broker.

Proceed as follows:

1. Create the LDAP configuration file and the LDAP Data Interchange Format (LDIF) file.


In our testing, we created /WebSphere390/CB390/etc as the directory for LDAP files associated with OS/390 Component Broker, copied the samples of LDAP configuration and LDIF files into the directory, then modified the files according to comments in the files.

a. Copy the sample of the LDAP configuration file from /usr/lpp/CB390/samples/bboslapd.conf into your LDAP configuration file, and update your copy.

We modified the LDAP configuration file as follows:

#errorLog /tmp/slapd.errors#----------------------------------------------------------------# Attribute and object class definitions#----------------------------------------------------------------include /usr/lpp/ldap/etc/slapd.at.systeminclude /usr/lpp/ldap/etc/slapd.cb.at.confinclude /usr/lpp/ldap/etc/slapd.at.confinclude /usr/lpp/ldap/etc/slapd.oc.systeminclude /usr/lpp/ldap/etc/slapd.cb.oc.confinclude /usr/lpp/ldap/etc/slapd.oc.conf#----------------------------------------------------------------# Server configuration definitions#----------------------------------------------------------------port 1389 1maxthreads 10maxconnections 10waitingthreads 10timelimit 3600sizelimit 500adminDN "cn=BOSSAdmin, cn=localhost" 5adminPW password 6#----------------------------------------------------------------# DB2 database access definitions#----------------------------------------------------------------database rdbm GLDBRDBM#dsnaoini <will be determined from JCL DD statement>dsnaoini BBO.DSNAOINI 2#servername <db2_location_name>servername DBS3 3databasename BBOLDAP 4#dbuserid <cb_ldap_table_prefix_id>dbuserid BBOtbspaceentry BBOENT 4tbspace32k BBO32K 4tbspace4k BBO4K 4tbspacemutex BBOMUTX 4suffix "cn=localhost"

Chapter 11. LDAP enablement 75

suffix "o=BOSS,c=US" 5

1 Port number that is used by LDAP server. We used port 1389.

2 DSNAOINI data set, or the file that contains the CLI or ODBC initialization file. We named our ODBC file BBO.DSNAOINI.

3 DB2 server location as defined in the CLI initialization file. DBS3 was our DB2 location name.

4 The RDBM backend-specific options. The values of these parameters have to match with the DB2 database and tablespaces created for the LDAP server.

5 Distinguished Name (DN) of the administrator for the LDAP server and the suffix used while running the LDAP utilities. The values of these parameters are the same as defined in the LDIF file.

6 The admin password.

b. Copy the sample of LDIF file from /usr/lpp/CB390/samples/bboldif.cb into your LDIF file, then modify your copy as required.

Figure 41 is the LDIF file that we used in our project.

Figure 41. Sample LDIF file for Component Broker WAS 3.02 EE

2. Create DSNAOINI file that contains a CLI initialization file or ODBC initialization file.

dn: o=BOSS, c=USo: BOSSobjectclass: topobjectclass: organizationdescription: CBServer Name Tree RootuserPassword: bossSecretownersource: o=BOSS, c=USentryowner: access-id:cn=BOSSAdmin, o=BOSS, c=USaclpropagate: TRUEinheritoncreate: TRUEownerpropagate: TRUEaclsource: o=BOSS, c=USaclentry: access-id:cn=BOSSAdmin, o=BOSS, c=US:normal:rwsc:object:adaclentry: access-id:CBADMIN:normal:rwsc:object:adaclentry: access-id:CBSYMCR1:normal:rwsc:object:adaclentry:group:CN=ANYBODY:normal:rsc

dn: cn=BOSSAdmin, o=BOSS, c=USobjectclass: personcn: BOSSAdminsn: BOSSuserPassword: secret


Copy the sample of DSNAOINI from BBO.SBBOJCL(BBOAINI) into the data set with a name of your choice, and modify it.

Figure 42 shows the DSNAOINI file that we used in our testing.

Figure 42. DSANOINI file

Figure 42 notes:

1 DBS3 is the default DB2 subsystem to which our LDAP server is connected.

2 RRSAF is the attachment type that DB2 CLI uses to connect to DB2 for OS/390 address space.

3 DSNACLI is a PLAN used to initialize the application connection to the DB2 for OS/390 subsystem.

4 The DB2 location (DDF) in our DB2 installation is DBS3.

3. Create the LDAP database and tablespaces.

Copy BBO.SBBOJCL(BBOLDTBC) and update it. The BBOLDTBC is a JCL that will be used to create databases used by LDAP in support of Component Broker Naming and Interface Repository.

[COMMON]MVSDEFAULTSSID=DBS3 1TRACE=0TRACE_BUFFER_SIZE=2000000TRACE_NO_WRAP=0CLITRACE=0;TRACEFILENAME=DD:CLITRACE

; Example SUBSYSTEM stanza for V42A subsystem[DBS3]MVSATTACHTYPE=RRSAF 2PLANNAME=DSNACLI 3

; DATA SOURCE stanza for your data source[DBS3] 4AUTOCOMMIT=0CONNECTTYPE=1

In our project, we set up an LDAP server on a monoplex. If you plan to install OS/390 Component Broker on a sysplex, you should use a unique LDAP configuration file, LDIF file and DSNAOINI data set for each system in the sysplex.

Note


“SQL to create database for LDAP server” on page 95 shows the SQL statement s that we used to create our LDAP server database.

If you need to drop the databases and tables that you have created, see BBO.SBBOJCL(BBOLDTBD).

4. Bind CLI required for LDAP server.

Copy and modify the BBO.SBBOJCL(BBO1JCL).

To determine whether the DSNCLI already has been bound, you can run a SPUFI query like the following:

select * from sysibm.sysplan where name=’DSNACLI’;

If DSNACLI already exists, you can perform as follows:

- Bind DSNACLI again by specifying RETAIN so that existing privileges are not lost.

- Find out who has execute privileges on the plan by running the following SPUFI query:

select * from sysibm.sysplanauth where name=’DSNACLI’;

Then run BBO1JCL and re-grant the privileges.

- Create a new plan name, update the DSNAOINI data set used by the LDAP and Component Broker with the new plan name, then bind the new plan using BBO1JCL.

- Notice that you need also to update execute permissions appropriately for BBOLDAP, BBOIRS, and BBONMS, or PUBLIC depending on your installation policies.

5. Bind Component Broker packages required for LDAP server.

The BBO.SBBOJCL(BBO2JCL) is sample JCL to bind OS/390 Component Broker packages required for the LDAP server. Make a copy of the JCL and modify it.

Make sure that you run BBO1JCL successfully, before you submit BBO2JCL.

Once you submit the job BBO1JCL and BBO2JCL, you may get the result of return code 4 for each job, and this is acceptable.

If DSNACLI already exists or you have already run BIND DSNACLI, do not run BBO1JCL again because it will destroy all GRANT privileges established for DB2 for OS/390.

Attention


“Bind for LDAP setup for OS/390 Component Broker packages” on page 93 shows DB2 bind commands that we use to bind Component Broker packages required for LDAP server.

6. Create entries in the LDAP server DB2 database.

Copy and modify BBO.SBBOJCL(BBOLD2DB). This job is used to populate the LDAP server DB2 database with entries defined in the LDIF file.

“JCL to prime LDAP server” on page 96 shows JCL that we use to populate our LDAP server database.

11.2 Setting RACF authorization for LDAP

You have to perform the following steps to define RACF authorization for an LDAP server:

• Define a RACF user ID under which to run the LDAP server. This user ID has an OMVS superuser authority (UID equals to zero).

• Give this user ID relevant access to the Facility class profiles (BPX.DAEMON and BPX.SERVER), if you use thread-level authority.

• If you have protected your data sets, give this user ID access to the MVS data sets defined in the LDAP procedure.

• Finally, define the Started class for the LDAP server procedure.

Make a copy of the BBO.SBBOEXEC(BBOLDRAC) and BBO.SBBOJCL(BBOLDRAJ), then modify the files. The BBOLDRAC is a REXX program to perform RACF authorization for LDAP. Once you modify your copies, submit the BBOLDRAJ that will execute BBOLDRAC from a user ID with relevant RACF authority.

In our testing, we used the following definitions to set up RACF authorization for our LDAP server:

ADDGROUP CBCTL1 OMVS(GID(1000)) OWNER(SYS1) SUPGROUP(SYS1)ADDUSER CBLDAP DFLTGRP(CBCTL1) NAME('LDAP SERVER') OWNER(CBCTL1) NOPASWORDOMVS(UID(0) HOME('/') PROGRAM(‘/bin/sh’)

PERMIT BPX.DAEMON CLASS(FACILITY) ID(CBLDAP) ACCESS(READ)PERMIT BPX.SERVER CLASS(FACILITY) ID(CBLDAP) ACCESS(UPDATE)

RDEFINE STARTED BBOLDAP.* STDATA(USER(CBLDAP))SETROPTS RACLIST(STARTED) REFRESH


11.3 Granting Access to LDAP databases

The LDAP server requires DB2 for OS/390 access authority to the databases you created.

The BBO.SBBOJCL(BBOLDGRT) is a sample JCL to grant access to the LDAP database. In this JCL, we perform as follows:

• Grant the following DB2 for OS/390 authorities for the user ID under which the LDAP server runs:

GRANT SELECT ON SYSIBM.SYSTABLES TO racf_userid;GRANT SELECT ON SYSIBM.SYSCOLUMNS TO racf_userid;GRANT DBADM ON DATABASE ldap_data_base TO racf_userid;

where racf_userid is the RACF user ID under which the LDAP server runs and ldap_data_base is the LDAP database name that is specified on the database keyword in your slapd.conf file.

• Grant the following authority to general users:

GRANT EXECUTE ON PLAN DSNACLI TO PUBLIC;

11.4 Starting the LDAP server

You are now ready to start your LDAP server. However, there are a number of things that have to be checked before starting the LDAP server. Make sure that the required environment variables have been configured to meet your USS environment. You may use the following checklist when you start working with the LDAP server:

Environment variables

• PATH

• LIBPATH

• NLSPATH

• MANPATH

• _CEE_ENVFILE

• LDAP_BASEDN

TCP/IP configuration

• RESOLVER CONFIG

Language specification


• LANG

Now, you can start the LDAP server. You can either start it from the OS/390 UNIX shell or the MVS console.

In our project, we used a started task procedure to run the LDAP server. We used a sample procedure in BBO.SBBOJCL(BBOLDAP) to run LDAP server as a started task. We copied the sample to SYS1.PROCLIB and modified the procedure as required.

Figure 43 shows the started task of the LDAP server that runs in our project environment. All names highlighted in bold are changed to reflect our installation environment.

Figure 43. LDAP started procedure

If you have not registered the SGLDLNK and SDSNLOAD data set into LNKLST, you need to put the data set at the STEPLIB in the LDAP started procedure.

In Figure 43, locate and find the ENVVAR. In this LDAP started procedure, we specify the environment variables as an HFS file. We define the environment variables as shown in Figure 44.

Figure 44. Environment variables used in the LDAP started procedure

//BBOLDAP PROC REGSIZE=0M,// PARMS='',// OUTCLASS='O'//* See instructions at the bottom of this file.// SET LDAP='GLD'// SET DB2='DSN610'// SET SYSNAME='OPPLEX'// SET LDAPDIR='/WebSphere390/CB390/etc'//BBOLDAP EXEC PGM=GLDSLAPD,REGION=&REGSIZE,TIME=1440,// PARM=('/&PARMS >DD:SLAPDOUT 2>&1')//STEPLIB DD DSN=&LDAP..SGLDLNK,DISP=SHR// DD DSN=&DB2..SDSNLOAD,DISP=SHR//CONFIG DD PATH='&LDAPDIR/&SYSNAME..bboslapd.conf'//ENVVAR DD PATH='/usr/lpp/ldap/etc/slapd.envvars'//*DSNAOINI DD PATH='&LDAPDIR/&SYSNAME..dsnaoini'//DSNAOINI DD DISP=SHR,DSN=BBO.DSNAOINI//SLAPDOUT DD SYSOUT=&OUTCLASS,FREE=CLOSE,SPIN=UNALLOC//SYSOUT DD SYSOUT=&OUTCLASS,FREE=CLOSE,SPIN=UNALLOC//SYSUDUMP DD SYSOUT=&OUTCLASS,FREE=CLOSE,SPIN=UNALLOC//CEEDUMP DD SYSOUT=&OUTCLASS,FREE=CLOSE,SPIN=UNALLOC

NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/En_US.IBM-1047/%NLANG=En_US.IBM-1047


You will see the following message, once the server is completely initialized:

GLD0122I Slapd is ready for requests.

The LDAP server is now ready for requests.

11.5 Testing the LDAP server

Once the LDAP server is initialized without any error indication, you can test it for proper operation. Use a utility ldapsearch, which can either be run from the USS shell command prompt or as a TSO command, to test your LDAP server.

To issue ldapsearch from USS, you may need to modify the PATH variable in your environment file as follows:

PATH=$PATH:/usr/lpp/ldap/bin

From TSO command, issue ldapsrch. You may need to concatenate SGLDLNK to STEPLIB DD in your TSO logon procedure if the data set is not in link list. The command ldapsrch is found in SGLDEXEC data set.

Using the database that we created by running the BBOLD2DB job, we tested our LDAP server. We performed query all object classes from USS shell as follows:

ldapsearch -v -p 1389 -h wtsc59oe -w password -b "o=BOSS,c=US""objectclass=*"


The result is shown in Figure 45.

Figure 45. LDAPSEARCH result of querying object class

In addition, you can perform a query of the Access Control List (ACL) entries, the way they should be propagated, and the source for these ACLs.

We issued the following command to see the ACLs:

ldapsearch -v -p 1389 -h wtsc59 -w password -b "o=BOSS,c=US""objectclass=organization" aclentry aclpropagate aclsource

Figure 46 shows the result of querying the ACL entries.

Figure 46. LDAPSEARCH result of querying the ACLs

RATNA@SC59:/u/ratna: >export PATH=$PATH:/usr/lpp/ldap/binRATNA@SC59:/u/ratna: >ldapsearch -v -p 1389 -h wtsc59oe -w password-b "o=BOSS,c=US" "objectclass=*"

ldap_init(127.0.0.1, 1389)filter pattern: objectclass=*returning: ALLfilter is: (objectclass=*)o=BOSS, c=USo=BOSSobjectclass=topobjectclass=organizationdescription=CBServer Name Tree Root

cn=BOSSAdmin, o=BOSS, c=USobjectclass=personcn=BOSSAdminsn=BOSSsn=BOSS2 matches

RATNA@SC59:/u/ratna> ldapsearch -v -p 1389 -h wtsc59 -w password -b"o=BOSS,c=US" "objectclass=organization" aclentry aclpropagateaclsource

ldap_init(wtsc59, 1389)filter pattern: objectclass=organizationreturning: aclentry aclpropagate aclsourcefilter is: (objectclass=organization)o=BOSS, c=USaclsource=O=BOSS,C=USaclpropagate=TRUEaclentry=group:CN=ANYBODY:normal:rscaclentry=access-id:CBSYMCR1:normal:rwsc:object:adaclentry=access-id:CBADMIN:normal:rwsc:object:adaclentry=access-id:CN=BOSSADMIN,O=BOSS,C=US:normal:rwsc:object:ad1 matches


Chapter 12. Additional WebSphere EE enablement

This chapter discusses additional steps required to enable OS/390 Component Broker, specifically the following:

• Authorization checking for OS/390 Component Broker regions

• Basic setup on OS/390 system for OS/390 Component Broker

• Setup of the initialization environment file

All procedures and examples documented here are based and tested on OS/390 Component Broker for WAS 3.02 EE.

12.1 Authorization for OS/390 Component Broker

This section summarizes server identification and authorization checking in OS/390 Component Broker.

The OS/390 Component Broker uses security services provided by the OS/390 Security Server, or equivalent product. The general rules for server authorization checking to control access to the OS/390 Component Broker are as follows:

• You would give more authority to the control regions and less authority to the server regions.

Table 13. Level of trust and authority for regions

• Regarding the OS/390 Component Broker run-time servers, the Daemon and the Naming server have less authority than the System Management Server.

Region Level of trust and access authority

Control Region Trusted, serves multiple users. Superuser authority. Run APF authorized.

Server Region Untrusted. Needs authorization to get work and to attach to data stores, should run unauthorized. Resources are access under the authority of the client. Client authorities cannot be increased by the server


Table 14. Assigning authorities to OS/390 Component Broker control regions and server regions

The following RACF authorization or control access can be used:

• CBIND class and the RACF profile CB.BIND.<generic server name> is used to restrict a client’s access to be able to access (BIND) a control region.

• CBIND class and the RACF profile CB.<generic server name> is used for determining if a client can use managed objects in a server.

• SOMDOBJS class is used to control a client’s access to homes and the ability to invoke methods. In addition, you have to specify method-level access checking through the OS/390 Component Broker Administration application.

DB2 for OS/390 and LDAP, as resource managers, have implemented their own resource controls that control the ability of servers to bind to resources. All control regions and server regions have to be granted access to relevant resources. You can do this by using RACF authorization. In addition, LDAP can be set up to use access control lists (ACLs) for its objects, in which case the Naming server needs to be authorized to these objects.

The BBO.SBBOJCL(BBOCBRAJ) is JCL that calls and executes the sample REXX program BBO.SBBOEXEC(BBOCBRAC), which contains RACF commands to set up necessary and sufficient authority for initial installation of the OS/390 Component Broker. You should re-examine and modify the REXX

Runtime server Region Required authorities

Daemon Server Control Profile in RACF STARTED class, access to WLM services

Naming Server Control Profile in RACF STARTED class, access to WLM services

Server Profile in RACF STARTED class, READ authority to SERVER class, DBADM for LDAP database

System Management server

Control Profile in RACF STARTED class, superuser authority in OMVS segment

Server Profile in RACF STARTED class, READ authority to SERVER class

Interface Repository server

Control Profile in RACF STARTED class, superuser authority in OMVS segment

Server Profile in RACF STARTED class, READ authority to SERVER class, DBADM for LDAP database


script with your installation options, and you need a proper RACF authority to run this REXX exec.

We used the default RACF definitions provided in BBOCBRAC. Table 15 shows the group IDs and user IDs of Component Broker control regions and server regions in our testing installation, and the associated RACF SERVER class authority that we used for the regions.

Table 15. User IDs and group IDs of CB control regions

12.2 Setting OS/390 base system

Following are recommendations to place OS/390 Component Broker modules:

• Load all members of BBO.SBBOLPA into LPA. Since the data set SBBOLPA is a PDSE and OS/390 cannot load members of a PDSE at system initialization time (IPL), you have to load the members dynamically into LPA.

Make sure that your CSA page data set can hold the run time OS/390 Component Broker modules that comprise about 200 MB in size.

Issue the following command to add OS/390 Component Broker modules dynamically into LPA:

SETPROG LPA,ADD,MASK=*,DSNAME=BBO.SBBOLPA

• Put BBO.SBBOLOAD and BBO.SBBOLD2 in the link list.

• Set APF authorized to BBO.SBBOLOAD, BBO.SBBOLD2 and BBO.SBBOLPA, or place the data sets into PROGxx.

• Change SCHEDxx to include the statement from BBO.SBBOJCL(BBOSCHED) sample file.

Region Runtime Server

Procedure Group ID

User ID SERVER Class Authority

Control Daemon BBODMN CBCTL1 CBDMNCR1

System Management BBOSMS CBSYMCR1

Naming BBONM CBNAMCR1

Interface Repository BBOIR CBINTCR1

Server System Management BBOSMSS CBSR1 CBSYMSR1 READ

Naming BBONMS CBNAMSR1 READ

Interface Repository BBOIRS CBINTSR1 READ

Chapter 12. Additional WebSphere EE enablement 87

• Do not APF authorize BBO.SBBOULIB or SBBOMIG, because it should run under the authority of the client.

• Do not place BBO.SBBOULIB in either the LPA or link list.

Note that you have to put this data set in the STEPLIB DD card of the started procedure of Component Broker server region BBOASR1S.

12.3 Setting initial.env file

You have to create and customize the initial.env.file and the files required for an instance of Component Broker:

1. Set up HFS directories for the initial.env file and the files required for an instance of Component Broker.

The BBO.SBBOJCL(BBOMCFG) contains sample JCL to set up HFS directories for the initial environment file and the files required for instances of Component Broker. The job BBOMCFG runs REXX script for setting up HFS. Edit or modify the variables according to the comments in the JCL.

You may copy and modify the SYSIN into a USS shell script and run it from USS command, as we did in our testing. We created /WebSphere390/CB390/controlinfo as the directory that contains the Component Broker initial environment file and ran the scripts shown in Figure 47.

Figure 47. Script to set up HFS directories for initialization environment files

2. Modify the initial.env file.

• CBCONFIG

/usr/lpp/CB390/bin/bbomcfg \-INSTALLDIR /usr/lpp/CB390 \-TARGETDIR /WebSphere390/CB390/controlinfo \-LDAPDIR /WebSphere390/CB390/etc \-SYSPLEX OPPLEX \-DM_NAME DAEMON01 \-IR_NAME INTFRP01 \-NM_NAME NAMING01 \-SM_NAME SYSMGT01 \-OWNER CBSYMSR1 \-GROUP CBSR1 + \1> /tmp/bbomcfg.out + \2> /tmp/bbomcfg.err


The value must match the -TARGETDIR value specified in BBOMCFG or script file to create HFS directories for initial.env file and other files required for an instance of Component Broker.

• DAEMON_PORT

Specifies the port as defined in the TCP/IP resolve configuration file. The default is 5555.

• DAEMON_IPNAME

The domain-qualified hostname.

• SYS_DB2_SUB_SYSTEM_NAME

The name of your DB2 subsystem Name.

• RESOLVE_IPNAME

The hostname specified in PROFILE.TCPIP.

• LOGSTREAMNAME

Refers to your log stream defined for Component Broker.

• LDAPCONF

Specifies LDAP configuration file.

• LDAPIRCONF

Refers to the LDAP configuration file.

• LDAPROOT

The root naming context as you defined in the LDIF file.

• LDAPIRROOT

This variable also refers to the root naming context as you defined in the LDIF file.

Figure 48 on page 90 shows the initial.env file that we used in our testing environment. The names highlighted in bold type reflect our installation configuration.

Chapter 12. Additional WebSphere EE enablement 89

Figure 48. Sample of intial.env file

1 These lines have been split for redbook printing purposes. In the actual file, they are on a single line.

LIBPATH=/lib:/usr/lpp/java/J1.1/lib/mvs/native_threads:/usr/lpp/CB390/libCLASSPATH=/usr/lpp/CB390/lib/bboprogm.jar:/usr/lpp/CB390/lib/bborbrt.jar:1 /usr/lpp/CB390/lib/bboidlc.jar:/usr/lpp/java/J1.1/lib/classes.zip:1 /usr/lpp/CB390/samples/PolicyIVP/PRODUCTION/bboplc.jar:1 /usr/lpp/CB390/samples/PolicyIVP/PRODUCTION/bboplsj.jarJAVA_COMPILER=jitcSYS_DB2_SUB_SYSTEM_NAME=DBS3TRACEALL=1TRACEPARM=00OTS_DEFAULT_TIMEOUT=2400OTS_MAXIMUM_TIMEOUT=2400SMPROC=BBOSMSIRPROC=BBOIRNMPROC=BBONMDAEMON_PORT=5555DAEMON_IPNAME=itso.ibm.comRESOLVE_PORT=900RESOLVE_IPNAME=itsocbLDAPCONF=/WebSphere390/CB390/etc/OPPLEX.bboslapd.confLDAPIRCONF=/WebSphere390/CB390/etc/OPPLEX.bboslapd.confLDAPROOT=o=BOSS,c=USLDAPIRROOT=o=BOSS,c=USSOMOOSQL=1CBCONFIG=/WebSphere390/CB390/controlinfoICU_DATA=/usr/lpp/CB390/bin/LOGSTREAMNAME=BBO.ERRORLOGTRACEBUFFLOC=BUFFERRAS_MINORCODEDEFAULT=NODIAGNOSTICDATA


Appendix A. Sample DB2 bind and SQL sources and JCL

This appendix contains the samples of DB2 bind commands, SQL sources and JCL that we have used to run the samples in Chapter 10, “DB2 enablement” on page 65 and Chapter 11, “LDAP enablement” on page 73.

Note: Consult your database administrator (DBA) before running these jobs. To run the jobs you need to have the relevant DB2 authority.

A.1 DB2 bind

In our installation, we used the JCL shown in Figure 49 to execute the DB2 bind command:

Figure 49. Sample JCL to execute DB2 bind

All names in the JCL and DB2 bind commands that may be changed are highlighted in bolds.

A.1.1 Bind system management data base of OS/390 Component BrokerBIND PACKAGE(CBDAEMON_PKG) MEMBER(BBODADT ) ACTION(REPLACE) +

ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)BIND PACKAGE(CBSERVER_PKG) MEMBER(BBOFDBC ) ACTION(REPLACE) +

ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)BIND PACKAGE(CBSERVER_PKG) MEMBER(BBOFDBM ) ACTION(REPLACE) +ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)

BIND PACKAGE(CBSERVER_PKG) MEMBER(BBOFDKB ) ACTION(REPLACE) +ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)

BIND PACKAGE(CBSERVER_PKG) MEMBER(BBOISPEC) ACTION(REPLACE) +ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)

BIND PACKAGE(CBSYSMGT_PKG) MEMBER(BBOMEXIM) ACTION(REPLACE) +ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)

BIND PACKAGE(CBSYSMGT_PKG) MEMBER(BBOMID02) ACTION(REPLACE) +ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)

BIND PACKAGE(CBSYSMGT_PKG) MEMBER(BBOMID04) ACTION(REPLACE) +

//<JOBCARD> JOB// SET BBOLIB='BBO'//BIND EXEC PGM=IKJEFT01,REGION=0M//STEPLIB DD DSN=DSN610.SDSNLOAD,DISP=SHR// DD DSN=DB2V61S3.SDSNEXIT,DISP=SHR//SYSTSPRT DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//DBRMLIB DD DSN=&BBOLIB..SBBODBRM,DISP=SHR//SYSTSIN DD *DSN SYSTEM(DBS3)

<DB2_bind_commands>END/*


ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)BIND PACKAGE(CBSYSMGT_PKG) MEMBER(BBOMID06) ACTION(REPLACE) +ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)

















BIND PACKAGE(CBSYSMGT_PKG) MEMBER(BBOMIMRI) ACTION(REPLACE) +ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)

BIND PACKAGE(CBSYSMGT_PKG) MEMBER(BBOMMD01) ACTION(REPLACE) +ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)




















BIND PACKAGE(CBSYSMGT_PKG) MEMBER(BBOMRDI ) ACTION(REPLACE) +ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)

BIND PACKAGE(CBSYSMGT_PKG) MEMBER(BBOMSD51) ACTION(REPLACE) +ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)



BIND PACKAGE(CBLIFECYCLE_PKG) MEMBER(BBOSLDOI) ACTION(REPLACE) +ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)

BIND PACKAGE(CBIVP_PKG) MEMBER(BBOSQDB ) ACTION(REPLACE) +ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)

BIND PACKAGE(CBSERVER_PKG) MEMBER(BBOSQDB ) ACTION(REPLACE) +ISOLATION(CS) CURRENTDATA(NO) RELEASE(COMMIT) VALIDATE(BIND)

A.1.2 Bind for LDAP setup for OS/390 Component Broker packagesBIND PACKAGE (CBLIFECYCLE_PKG) MEMBER(DSNCLICS) ISOLATION(CS) +

VALIDATE(BIND)BIND PACKAGE (CBLIFECYCLE_PKG) MEMBER(DSNCLINC) ISOLATION(NC) +

VALIDATE(BIND)BIND PACKAGE (CBLIFECYCLE_PKG) MEMBER(DSNCLIRR) ISOLATION(RR) +

VALIDATE(BIND)BIND PACKAGE (CBLIFECYCLE_PKG) MEMBER(DSNCLIRS) ISOLATION(RS) +

VALIDATE(BIND)BIND PACKAGE (CBLIFECYCLE_PKG) MEMBER(DSNCLIUR) ISOLATION(UR) +

VALIDATE(BIND)BIND PACKAGE (CBLIFECYCLE_PKG) MEMBER(DSNCLIC1) +

VALIDATE(BIND)BIND PACKAGE (CBLIFECYCLE_PKG) MEMBER(DSNCLIC2) +

VALIDATE(BIND)BIND PACKAGE (CBLIFECYCLE_PKG) MEMBER(DSNCLIF4)BIND PACKAGE (CBLIFECYCLE_PKG) MEMBER(DSNCLIMS) +

VALIDATE(BIND)BIND PACKAGE (CBLIFECYCLE_PKG) MEMBER(DSNCLIQR) +

VALIDATE(BIND)END

Appendix A. Sample DB2 bind and SQL sources and JCL 93

A.2 SQL source

Figure 50 shows JCL that we used to execute the SQL statement:

Figure 50. Sample JCL to execute SQL statement

Modify the the SQL statement to reflect your DB2 environment. All names and user IDs in the JCL and SQL source that may be changed are highlighted in bold type.

A.2.1 SQL to grant system management database of Component Broker

GRANT EXECUTE ON PACKAGE CBSERVER_PKG.* TO PUBLIC;GRANT EXECUTE ON PACKAGE CBDAEMON_PKG.* TO CBDMNCR1;GRANT EXECUTE ON PACKAGE CBSYSMGT_PKG.* TO CBDMNCR1;

GRANT EXECUTE ON PACKAGE CBSYSMGT_PKG.* TO CBSYMCR1;

GRANT EXECUTE ON PACKAGE CBLIFECYCLE_PKG.* TO CBNAMSR1;GRANT EXECUTE ON PACKAGE DSNAOCLI.* TO CBNAMSR1;GRANT SELECT ON SYSIBM.SYSTABLES TO CBNAMSR1;GRANT SELECT ON SYSIBM.SYSCOLUMNS TO CBNAMSR1;GRANT DBADM ON DATABASE BBOLDAP TO CBNAMSR1;

GRANT EXECUTE ON PACKAGE DSNAOCLI.* TO CBINTSR1;GRANT SELECT ON SYSIBM.SYSTABLES TO CBINTSR1;GRANT SELECT ON SYSIBM.SYSCOLUMNS TO CBINTSR1;GRANT DBADM ON DATABASE BBOLDAP TO CBINTSR1;

GRANT EXECUTE ON PACKAGE CBSYSMGT_PKG.* TO CBADMIN;

//<JOBCARD> JOB//STEP1 EXEC PGM=IKJEFT01,DYNAMNBR=20//STEPLIB DD DSN=DSN610.SDSNLOAD,DISP=SHR//DBRMLIB DD DSN=DB2V61S3.DBRMLIB.DATA,DISP=SHR// DD DSN=DSN610.SDSNDBRM,DISP=SHR//SYSTSPRT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SYSTSIN DD *DSN SYSTEM(DBS3)RUN PROGRAM(DSNTIAD) PLAN(DSNTIA61) -

LIB('DB2V61S3.RUNLIB.LOAD')END//SYSIN DD *

sql_input_deck/*//


A.2.2 SQL to create database for LDAP server

CREATE STOGROUP BBOLDSTOVOLUMES ("TARDB1")VCAT DB2V61S3;

CREATE DATABASE BBOLDAPSTOGROUP BBOLDSTO;

CREATE LARGE TABLESPACE BBOENTIN BBOLDAPNUMPARTS 1 BUFFERPOOL BP32KUSING STOGROUP BBOLDSTOPRIQTY 7500 SECQTY 800 LOCKSIZE ROW;

CREATE TABLESPACE BBO4KIN BBOLDAPSEGSIZE 4 BUFFERPOOL BP0USING STOGROUP BBOLDSTOPRIQTY 5000 SECQTY 500 LOCKSIZE ROW;

CREATE TABLESPACE BBO32KIN BBOLDAPSEGSIZE 4 BUFFERPOOL BP32KUSING STOGROUP BBOLDSTOPRIQTY 7500 SECQTY 800 LOCKSIZE ROW;

CREATE TABLESPACE BBOMUTXIN BBOLDAPBUFFERPOOL BP0USING STOGROUP BBOLDSTOLOCKSIZE TABLESPACE;

Appendix A. Sample DB2 bind and SQL sources and JCL 95

A.3 JCL to prime LDAP server

Following is JCL that we used to populate our LDAP server DB2 databases:

//BBOLD2DB JOB (POK,999),MSGCLASS=T,MSGLEVEL=(1,1)// SET DB2='DSN610'// SET LDAP='GLD'// SET LDAPDIR='/WebSphere390/CB390/etc'// SET SYSNAME='OPPLEX'// SET PARMS='-i //DD:LDIFIN -f //DD:CONFIG'//BBOLD2DB EXEC PGM=GLDLD2DB,REGION=0M,TIME=1440,// PARM=('/&PARMS >DD:SLAPDOUT 2>&1')//STEPLIB DD DISP=SHR,DSN=&DB2..SDSNLOAD// DD DISP=SHR,DSN=&LDAP..SGLDLNK//ENVVAR DD PATH='/usr/lpp/ldap/etc/slapd.envvars'//LDIFIN DD PATH='&LDAPDIR/&SYSNAME..bboldif.cb'//CONFIG DD PATH='&LDAPDIR/&SYSNAME..bboslapd.conf'//DSNAOINI DD DSN=BBO.DSNAOINI,DISP=SHR//SLAPDOUT DD SYSOUT=*//SYSOUT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//CEEDUMP DD SYSOUT=*//


Appendix B. Worksheets for defining a service definition

The following worksheets help you define a service definition. These worksheets, in order of presentation, are to help you define your:

• “Workloads and service classes” on page 98

• “Resource groups” on page 99

• “Classification rules” on page 100

• “Application environments” on page 101

• “Scheduling environments” on page 102

You should use the worksheets to set up your service definition before you enter any information into the ISPF administrative application.


B.1 Workloads and service classes

------------------ Base -----------------------------------------------Policy ________ Policy ________

(overrides)

Workload ________Description _______________________

Service Class ________Description ______________________

Resource Group ________ ________

Goal ________ ________Period Importance ________ ________1 Duration ________ ________



Service Class ________Description _______________________

Resource Group ________

Period Goal ________ ________1 Importance ________ ________








B.2 Resource groups

------------------ Base -------------------------------Policy _________ Policy _________

(overrides)

Resource Group ________Description _______________________

Minimum Capacity ________Maximum Capacity ________

Service Class ________ ________________ ________________ ________



Service Class ________ ________________ ________________ ________



Service Class ________ ________________ ________________ ________

Appendix B. Worksheets for defining a service definition 99

B.3 Classification rules

Classification Rules for ______________ Subsystem

Qualifier Type Qualifier Name Service Class________ ________ Default:_____________________ ________ _____________________ ________ _____________________ ________ _____________________ ________ _____________________ ________ _____________________ ________ _____________________ ________ _____________________ ________ _____________


B.4 Application environments

Application Environment __________________________

Description ____________________________________

Subsystem Type __________

Procedure Name __________

Start Parameters _______________________________

Limit on starting server address spaces for asubsystem instance (select one)

1. No limit2. One address space per system2. One address space per sysplex

Appendix B. Worksheets for defining a service definition 101

B.5 Scheduling environments

Scheduling Environment __________________________

Description ______________________________________

RequiredResource Name State Description_____________ ______ ______________________

_____________ ______ ______________________

_____________ ______ ______________________

_____________ ______ ______________________

_____________ ______ ______________________

_____________ ______ ______________________

_____________ ______ ______________________

_____________ ______ ______________________


Appendix C. Special notices

This publication is intended to help system programmers, system planners and I/T architechts to prepare an OS/390 system for the IBM WebSphere Application Server Enterprise Edition for OS/390. The information in this publication is not intended as the specification of any programming interfaces. See the PUBLICATIONS section of the IBM Programming Announcement for IBM WebSphere Application Server for OS/390 for more information about what publications are considered to be product documentation.

References in this publication to IBM products, programs or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent program that does not infringe any of IBM's intellectual property rights may be used instead of the IBM product, program or service.

Information in this book was developed in conjunction with use of the equipment specified, and is limited in application to those specific hardware and software products and levels.

IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact IBM Corporation, Dept. 600A, Mail Drop 1329, Somers, NY 10589 USA.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The information contained in this document has not been submitted to any formal IBM test and is distributed AS IS. The use of this information or the implementation of any of these techniques is a customer responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. While each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. Customers


attempting to adapt these techniques to their own environments do so at their own risk.

Any pointers in this publication to external Web sites are provided for convenience only and do not in any manner serve as an endorsement of these Web sites.

The following terms are trademarks of the International Business Machines Corporation in the United States and/or other countries:

The following terms are trademarks of other companies:

Tivoli, Manage. Anything. Anywhere.,The Power To Manage., Anything. Anywhere.,TME, NetView, Cross-Site, Tivoli Ready, Tivoli Certified, Planet Tivoli, and Tivoli Enterprise are trademarks or registered trademarks of Tivoli Systems Inc., an IBM company, in the United States, other countries, or both. In Denmark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S.

C-bus is a trademark of Corollary, Inc. in the United States and/or other countries.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and/or other countries.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States and/or other countries.

PC Direct is a trademark of Ziff Communications Company in the United States and/or other countries and is used by IBM Corporation under license.

ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel

IBM �CICSDB2Language EnvironmentOpenEditionRACFRS/6000SecurewayVisualAgeWebSphereDominoNetview

RedbooksRedbooks Logo DRDANetfinityOS/390RMFS/390System/390VTAMLotusNotes

104 Prepare OS/390 for WebSphere EE

Corporation in the United States and/or other countries.

UNIX is a registered trademark in the United States and other countries licensed exclusively through The Open Group.

SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC.

Other company, product, and service names may be trademarks or service marks of others.

Appendix C. Special notices 105

Appendix D. Related publications

The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook.

D.1 IBM Redbooks

For information on ordering these publications see “How to get IBM Redbooks” on page 111.

• OS/390 Workload Manager Implementation and Exploitation, SG24-5326

• IBM WebSphere Application Server Standard Edition Customization and Usage, SG24-5870

• IBM HTTP Server for OS/390 Customization and Usage, SG24-6205

• e-business Enablement Cookbook for OS/390 Vol. I: Technology Introduction, SG24-5664

• e-business Enablement Cookbook for OS/390 Volume II: Infrastructure for Java-based Solutions, SG24-5981

• e-business Enablement Cookbook for OS/390 Volume III: Developing Java Solutions, SG24-5890

D.2 IBM Redbooks collections

Redbooks are also available on the following CD-ROMs. Click the CD-ROMs button at ibm.com/redbooks for information about all the CD-ROMs offered, updates and formats.

CD-ROM Title Collection Kit Number

IBM System/390 Redbooks Collection SK2T-2177IBM Networking Redbooks Collection SK2T-6022IBM Transaction Processing and Data Management Redbooks Collection SK2T-8038IBM Lotus Redbooks Collection SK2T-8039Tivoli Redbooks Collection SK2T-8044IBM AS/400 Redbooks Collection SK2T-2849IBM Netfinity Hardware and Software Redbooks Collection SK2T-8046IBM RS/6000 Redbooks Collection SK2T-8043IBM Application Development Redbooks Collection SK2T-8037IBM Enterprise Storage and Systems Management Solutions SK3T-3694




D.3 Other resources

These publications are also relevant as further information sources:

• WebSphere Application Server for OS/390 V3.02 Program Directory, GA22-7460

• WebSphere Application Server Standard Edition Planning, Installing and Using Version 3.02, GC34-4806

• OS/390 Component Broker Planning and Installation Guide GA22-7325

• OS/390 Planning for Installation, GC28-1726

• OS/390 C/C++ User’s Guide, SC09-2361

• Debug Tool User’s Guide and Reference, SC09-2137

• OS/390 C/C++ IBM Open Class Library User’s Guide, SC09-2363

• IBM HTTP Server for OS/390, Planning, Installing, and Using, SC31-8690

• OS/390 SecureWay Communications Server: IP Configuration, SC31-8513

• OS/390 Language Environment Customization, SC28-1941

• OS/390 UNIX System Services Planning, SC28-1890

• OS/390 Programming: Resource Recovery, GC28-1739

• OS/390 SecureWay Security Server RACF Migration, GC28-1920

• OS/390 Security Server LDAP Server Administration and Usage Guide, SC24-5861

• OS/390 Planning: Workload Management, GC28-1761

• DB2 for OS/390 Version 5 Call Level Interface Guide and Reference, SC26-8959 (suffix 03)

• DB2 for OS/390 V5 Data Sharing: Planning and Administration, SC26-8961

• DB2 for OS/390 V5 Application Programming Guide and Reference for Java, SC26-9547

• DB2 UDB for OS/390 V6 Data Sharing: Planning and Administration, SC26-9007

• DB2 UDB for OS/390 Version 6 Installation Guide, GC26-9008

• DB2 UDB for OS/390 Version 6, refer to DB2 UDB for OS/390 Version 6 ODBC Guide and Reference, GC26-9011


• DB2 UDB for OS/390 V6 Application Programming Guide and Reference for Java, SC26-9018

• Program Directory for OS/390, GI10-4001

D.4 Referenced Web sites

These Web sites are also relevant as further information sources:

• http://www.watsonwalker.com/qspdown.html Cheryl Watson’s Quickstart Service Policy for WLM goal mode setup

• http://www.watsonwalker.com/quickst.html Cheryl Watson’s Quickstart Service definition

• http://www.s390.ibm.com/java Java for OS/390 homepage

Appendix D. Related publications 109

How to get IBM Redbooks

This section explains how both customers and IBM employees can find out about IBM Redbooks, redpieces, and CD-ROMs. A form for ordering books and CD-ROMs by fax or e-mail is also provided.

• Redbooks Web Site ibm.com/redbooks

Search for, view, download, or order hardcopy/CD-ROM Redbooks from the Redbooks Web site. Also read redpieces and download additional materials (code samples or diskette/CD-ROM images) from this Redbooks site.

Redpieces are Redbooks in progress; not all Redbooks become redpieces and sometimes just a few chapters will be published this way. The intent is to get the information out much quicker than the formal publishing process allows.

• E-mail Orders

Send orders by e-mail including information from the IBM Redbooks fax order form to:

• Telephone Orders

• Fax Orders

This information was current at the time of publication, but is continually subject to change. The latest information may be found at the Redbooks Web site.

In United States or CanadaOutside North America

e-mail [email protected] information is in the “How to Order” section at this site:http://www.elink.ibmlink.ibm.com/pbl/pbl

United States (toll free)Canada (toll free)Outside North America

1-800-879-27551-800-IBM-4YOUCountry coordinator phone number is in the “How to Order” section at this site:http://www.elink.ibmlink.ibm.com/pbl/pbl

United States (toll free)CanadaOutside North America

1-800-445-92691-403-267-4455Fax phone number is in the “How to Order” section at this site:http://www.elink.ibmlink.ibm.com/pbl/pbl

IBM employees may register for information on workshops, residencies, and Redbooks by accessing the IBM Intranet Web site at http://w3.itso.ibm.com/ and clicking the ITSO Mailing List button. Look in the Materials repository for workshops, presentations, papers, and Web pages developed and written by the ITSO technical professionals; click the Additional Materials button. Employees may access MyNews at http://w3.ibm.com/ for redbook, residency, and workshop announcements.

IBM Intranet for Employees


mailto: [email protected]

http://www.elink.ibmlink.ibm.com/pbl/pbl


http://w3.itso.ibm.com/

http://w3.ibm.com/










IBM Redbooks fax order form

Please send me the following:

We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card notavailable in all countries. Signature mandatory for credit card payment.

Title Order Number Quantity

First name Last name

Company

Address

City Postal code

Telephone number Telefax number VAT number

Invoice to customer number

Country

Credit card number

Credit card expiration date SignatureCard issued to


Abbreviations and acronyms

ACL Access Control List

APF Authorized Program Facility

API Application Programming Interface

ARM Automatic Restart Manager

ASCII American Standard Code for Information Interchange

ASID Address Space ID

CA Certificate Authority

CB Component Broker

CGI Common Gateway Interface

CLI Call Level Interface

CORBA Common Objects Request Broker Architecture

DASD Direct Access Storage Device

DBA Data Base Administrator

DDF Distributed Data Facility (with DB2)

DGW Domino Go Webserver (predecessor of the IBM HTTP Server)

DLL Dynamic Link Library

DN Distinguished Name

DRDA Distributed Relational Database Architecture

EJB Enterprise Java Beans

FRCA Fast Response Cache Accelerator

FTP File Transfer Protocol

© Copyright IBM Corp. 2000

GWAPI Go Webserver API

HFS Hierarchical File System

HTML Hypertext Markup Language

HTTP Hypertext Transfer Protocol

IBM International Business Machines Corporation

IIIOP Internet Inter-Orb Protocol

IMAP Internet Message Access Protocol

IPC Inter-Process Communication

IPCS Inter-Process Communication Services

ICSS Internet Connection Secure Server

IPL Initial Program Load

ISV Independent Software Vendor

ITSO International Technical Support Organization

JCL Job Control Language

JDBC Java Data Base Connection

JDK Java Development Kit

JIT Just In Time compiler (in Java)

JRIO Java Record I/O

JSP Java Server Pages

JVM Java Virtual Machine

LDAP Lightweight Directory Access Protocol

113

LDIF LDAP Data Interchange Format

LE Language Environment

LPA (OS/390) Link Pack Area

LPAR Logical Partition (S/390 Hardware Feature)

NNTP Network News Transfer Protocol

MVS Old name for OS/390

OEDIT OpenEdition Editor

OMVS OpenEdition MVS, old name for OS/390 UNIX System Services

OpenEdition Old name for UNIX System Services

ORB Object Request Broker

PID Process ID

PPID Parent Process ID

PDS Partitioned Data Set

PDS/E Partitioned Data Set/Extended

POP3 Post Office Protocol 3

PTF Program Temporary Fix

RACF Resource Access Control Facility

RMF Resource Measurement Facility

RRS Resource Recovery Services

RRSAF RRS Attachment Facility

RYO Roll Your Own; Abbrev. for customers own (inhouse) application or setup

SSL Secure Socket Layer

TSO Time Sharing Option

UDB Universal Data Base

URL Uniform Resource Locator

USS UNIX System Services

VIPA Virtual IP Addressing

WAS WebSphere Application Server

WebAS WebSphere Application Server

WLM Workload Manager

XCF Cross system Communication Facility


Index

AAccess Control Lists 73ACLs 73Administrative Data Utility 43Application server 61ARM 41ARM couple data 41ARM policy 42Automatic Restart Manager 41Average response time 17

BBPX.DAEMON 79BPX.SERVER 79

CCall Level Interface 67CB

Daemon 85Naming Server 85OS/390 base system installation 87System Management Server 85

Cheryl Watson’s Quickstart Service definition 11Cheryl Watson’s Quickstart Service Policy 11Classification groups 19Classification rules 21CLI 67Compatibility mode 7Component Broker 85Component Broker authorization 85CSA size 87

DDB2

Bind commands 91BP32K buffer pool size 66Call Level Interface 67DSNAOINI 68OS/390 call attachment facility (CAF) 69OS/390 Recoverable Resource Manager (RRM)

services attachment facility 69SQL sources 91Subsystem name 66

DB2 for OS/390 Component Broke 65

© Copyright IBM Corp. 2000

DB2 ODBC 67Discretionary 17DSNAOINI DD card 68Dynamic SQL 70

EExecution velocity 17

GGLD0122I Slapd is ready for requests 82Goal mode 7

HHTTP Server

Quick and Proper customization 51httpd.conf 53httpd.envvars 57

IIBM WebSphere Application Server 57

Installation Verification Program 62IMW0235I 62initial.env file 88

JJava 2 Technology Edition 49Java Database Connectivity 70Java Development Kit 47Java for OS/390 47JAVA_HOME 61Javahome 57JDBC 70JDK 47JDK 1.1.8 47

LLDAP 73

ENVVAR 81Group Administration Utility 73RACF authorization 79Server configuration 74

LDAP Data Interchange Format 74LDAP Directory Server Access Control List 73LDIF 74

115

Log streams 35LOGR couple data set 35

MMonoplex setup 5MVSADMIN.WLM.POLICY 8MVSATTACHTYPE 68MVSDEFAULTSSID 68

PPersistent objects 39PLANNAME 69program control 58

RRemote Server Configuration Dialog 54Resource group 15Resource Recovery Services 39Response time with percentile 17RRS 39RRS Attachment Facility 70RRSAF 70

SScheduling environment 27SDK 1.3.0 49Security Server 85ServerInit 61ServerTerm 61Service 61Service coefficients 13Service definition 10Service policy 13Software requirements 1SQLJ 70Static SQL 70SYS1.PARMLIB

BPXPRMxx 45COUPLExx 5, 35IEAICSxx 7IEAIPSxx 7IEAOPTxx 7IEASYSxx 5IEFSSNxx 66IXCARMF 41SCHEDxx 87

Sysplex couple data set 5

Sysplex setup 5System Logger 35

Define RRS log streams 39Setting up for Component Broker 36

System management database 71

TTCP/IP tuning 45

VVelocity 13

WWeb server 51

Configuration files 53Started procedure 59Working directory structure 52

Web server started procedure 59Web server working directory structure 52WLM 7

Application environment 25Classification groups 19Classification rules 21couple data set 7, 8ISPF application 7Policy override 28Resource group 15Scheduling environment 27Service classes 14Service coefficients 13Service Definition 7Service policy 13

Workload management 7Worksheets 97

XXCF utility 8


IBM Redbooks review

Your feedback is valued by the Redbook authors. In particular we are interested in situations where a Redbook "made the difference" in a task or problem you encountered. Using one of the following methods, please review the Redbook, addressing value, subject matter, structure, depth and quality as appropriate.

• Use the online Contact us review redbook form found at ibm.com/redbooks • Fax this form to: USA International Access Code + 1 845 432 8264 • Send your comments in an Internet note to [email protected]

Document NumberRedbook Title

SG24-5685-00Prepare OS/390 for WebSphere Enterprise Edition

Review

What other subjects would you like to see IBM Redbooks address?

Please rate your overall satisfaction:

O Very Good O Good O Average O Poor

Please identify yourself as belonging to one of the following groups:

O Customer O Business Partner O Solution DeveloperO IBM, Lotus or Tivoli EmployeeO None of the above

Your email address:The data you provide here may be used to provide you with information from IBM or our business partners about our products, services or activities.

O Please do not use the information collected here for future marketing or promotional contacts or other communications beyond the scope of this transaction.

Questions about IBM’s privacy policy?

The following link explains how we protect your personal information.ibm.com/privacy/yourprivacy/





http://www.ibm.com/privacy/yourprivacy/


http://www.ibm.com/privacy/yourprivacy/

(0.2”spine)0.17”<->0.473”

90<->249 pages

Prepare OS/390 for WebSphere Enterprise Edition

®

SG24-5685-00 ISBN 073841896X

INTERNATIONAL TECHNICALSUPPORTORGANIZATION

BUILDING TECHNICALINFORMATION BASED ONPRACTICAL EXPERIENCE

IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.

For more information:ibm.com/redbooks

Prepare OS/390 for WebSphereEnterprise Edition

Infrastructure for WebSphere Enterprise Edition

Configure DB2, RRS, System Logger, ARM, LDAP, and more

General CB installation hints

Prepare an OS/390 R10 System for WebSphere Enterprise Edition.This book helps you in setting up OS/390 for the IBM WebSphere Application Server for OS/390 Enterprise Edition.We worked on an OS/390 R10 system setting up IBM WebSphere Application Server 3.02 Enterprise Edition for OS/390 . We are describing the set up for all the necessary components required to run WAS EE. We are however not describing how to set the CB/390 part in details, also not how to deploy EJBs since at the time of writing of this book, IBM WebSphere Application Server 4.0 Enterprise Edition for OS/390 was already on the horizon. Since the deployment of EJBs will be different in WAS EE 4.0 from WAS EE 3.02, we decided to describe this EJB deployment for WAS 4.0 EE in details in a redbook to come.




Prepare OS/390 for WebSphere Enterprise EditionPrepare OS/390 for WebSphere Enterprise Edition...

Documents

Transcript of Prepare OS/390 for WebSphere Enterprise EditionPrepare OS/390 for WebSphere Enterprise Edition...