Purpose

This tool mentor describes a simple scenario of setting up the Component Broker (CB) server and client runtime environment on OS/390, accessing a DB2-backed Business Object. 

Depending on the requirements for security, access to other transaction managers. and the like, developers should refer to the Component Broker Planning, Performance, and Installation Guide and Assembling Applications for setup details.

Related Rational Unified Process activity: Activity: Execute Functional Integration Test on the Development Platform.

Overview

To setup the CB390 server:

  1. Plan the Server Configuration
  2. Install and Configure Prerequisite Software on Server
  3. Install, Configure, and Verify the CB390 Runtime Environment
  4. Application Server Installation and Setup

In this tool mentor, it is assumed that a typical java client machine is set up. To set up a typical CB client:

  1. Install Prerequisite and Other Support Software on Client
  2. Install the CB client

1. Plan the Server Configuration To top of page

Installing CB390 on a single OS/390 in a single system or a multi-system sysplex is sufficient to do application, functional, and performance testing, without the need for additional requirements on the infrastructure for a multi-system environment requiring data sharing, load balancing, and so forth. However, in all environments the requirements for client authentication must be considered in assessing the placement of client code: servlets, and the overall security requirements of the configuration (for example, the  requirement for DCE).

For details, refer to the section titled "Setting Up System Security" and the chapter titled "Advanced topics" of the OS/390 Component Broker Planning and Installation Guide.

2. Install and Configure Prerequisite Software on Server To top of page

The following software must be installed prior to installing and configuring the CB390 server environment:

  1. OS/390 Version 2 Release 8 or later, configured as a sysplex. For details, see OS/390 MVS Setting up a Sysplex and the OS/390 Version 2 Release 8 Planning for Installation.
  2. DB2 Version 6 for OS/390. For details, see DB2 UDB for OS/390 V6 Installation Guide.
  3. CICS/TS 1.3, if the CICS-EXCI PAA is to be used. For details see the CICS Transaction Server for OS/390 Installation Guide.
  4. IMS/TM 6.1, if the IMS-OTMA PAA is to be used. For details, see IMS/VS Installation, Volumes 1 and 2.
  5. JDK 1.1.8 for OS/390
  6. C/C++ MVS Compiler and Runtime. For details, see C/C++ MVS Compiler and Runtime Migration Guide.

Additionally, the following OS/390 features must be configured before configuring the CB390 server environment:

  1. Recovery Resource Services. For details, see OS/390 MVS Programming: Resource Recovery.
  2. Workload management must be operating in goal mode. For details, see OS/390 MVS Planning: Workload Management.
  3. OS/390 System logger. For details, see OS/390 MVS Setting Up a Sysplex.
  4. APPC, if the IMS-APPC PAA is to be used. For details, see OS/390 MVS Planning: APPC/MVS Management.
  5. LDAP— details, see OS/390 Security Server/LDAP Server Administration and Usage Guide.
  6. System Security product, such as Security Server (RACF). For details, see OS/390 Security Server (RACF) Planning: Installation and Migration.

For additional prerequisite information for your server and application development environments, see Chapter 4 of the Planning and Installation Guide.

3. Install, Configure, and Verify the CB390 Runtime Environment To top of page

  1. Install the CB390 code. See the Program Directory for the SMP/E planning and requirements.
  2. Configure the CB390 Runtime. See Chapter 3 of the Planning and Installation Guide for details on setting up the Server Procedures, environmental files, security definitions, and DB2 tables and plans.
  3. Install the CB390 Administrative and Operational Client on a Windows NT system. See the Planning and Installation Guide.
  4. Test CB installation with the samples. See the Planning and Installation Guide.

4. Application Server Installation and Setup To top of page

  1. Transfer source code form development environment to USS environment on OS/390.
  2. Build the executables application— details, see "Assembling server applications on OS/390" in the OS/390 Component Broker Assembling Applications manual.
  3. Define the procedures, security constructs, DB2 databases, DB2 packages, and so on for the servers and clients. For details, see "Deploying server applications in OS/390 Component Broker servers" in the Assembling Applications manual.
  4. Using the CB for OS/390 Administration Utility, install the application servers on the OS/390 system.

5. Install Prerequisite and Other Support Software on the Client To top of page

  1. A Java or C++ client residing on OS/390 requires the CB390 runtime environment to be installed on that OS/390 image.
  2. (Optional) If your OS/390 resident Java client is a servlet, then WebSphere Application Server V1.1 or higher must be installed on an OS/390 system where a CB390 server environment is installed.
  3. If your client does not reside on OS/390, then refer to the CB installation instructionss for that platform.

6. Install the CB client To top of page

Install the CB client in the appropriate directory. There is no client installation tool for CB390. Update the LIBPATH and the CLASSPATH of the client to include the appropriate files and directories.

For details, see the section titled "Preparing and Running Client Applications" in the Assembling Applications manual.

This information is provided by IBM Corporation

 

© Copyright IBM Corporation 1999-2000

Display Rational Unified Process using frames

Rational Unified Process