autosys job mgt4.5 admin

Administrator Guide r1 SP3

Unicenter®

Enterprise Job Manager

First Edition

This documentation and related computer software program (hereinafter referred to as the "Documentation") is for the end user's informational purposes only and is subject to change or withdrawal by Computer Associates International, Inc. ("CA") at any time.

This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies.

This right to print copies is limited to the period during which the license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user's responsibility to return to CA the reproduced copies or to certify to CA that same have been destroyed.

To the extent permitted by applicable law, CA provides this documentation "as is" without warranty of any kind, including without limitation, any implied warranties of merchantability, fitness for a particular purpose or noninfringement. In no event will CA be liable to the end user or any third party for any loss or damage, direct or indirect, from the use of this documentation, including without limitation, lost profits, business interruption, goodwill, or lost data, even if CA is expressly advised of such loss or damage.

The use of any product referenced in this documentation and this documentation is governed by the end user's applicable license agreement.

The manufacturer of this documentation is Computer Associates International, Inc.

Provided with "Restricted Rights" as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.

© 2005 Computer Associates International, Inc.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Contents iii

Contents Chapter 1: Introduction 7

Documentation Set................................................................................................................ 7 Contact Customer Support ..................................................................................................... 7

Chapter 2: Concepts and Components 9 Architecture ......................................................................................................................... 9 Job Command Center .......................................................................................................... 11

Quick Start ................................................................................................................... 11 Job Status Views ........................................................................................................... 12 Job Flow Monitoring ....................................................................................................... 12 Job Editor Find Object .................................................................................................... 12 Job Editor Create Object ................................................................................................. 12 CCI Link Status ............................................................................................................. 12 Server Status................................................................................................................ 12 Services Status ............................................................................................................. 13 Credentialed User Summary Status .................................................................................. 13 Credential Group Summary Status ................................................................................... 13 Shift Notes ................................................................................................................... 13

Job Editor .......................................................................................................................... 14 Job Flow Monitoring............................................................................................................. 16

Operating Modes ........................................................................................................... 16 Monitoring Job Flows...................................................................................................... 17

Job Status Console.............................................................................................................. 18 Using Job Status Console................................................................................................ 18

Event Console and Event Management ................................................................................... 20 Host Access........................................................................................................................ 20 Configuration ..................................................................................................................... 20

Chapter 3: Installing Unicenter CA-7 Host Components 21 Reviewing Your Installation Tasks.......................................................................................... 22

Installing the Required CA Common Services for z/OS Components ...................................... 22 Installing CA-CPS .......................................................................................................... 23 Link Editing CAICCI with TCP/IP....................................................................................... 23 Configuring the TCP/IP Gateway Server Started Task.......................................................... 24 Testing TCP/IP Communications....................................................................................... 26 Customizing the CAIENF Procedure to Initiate the SCHSRVR Task ......................................... 27

iv Administrator Guide

Defining the PROFILE Data Set Used by the SCHSRVR Task ................................................. 28 Modifying the SCHSRVR Task .......................................................................................... 29 Identifying the SCHSRVR Started Task to the Host Security Systems..................................... 30 Merging the Unicenter CA-7 Product Table......................................................................... 31 Restarting CAIENF ......................................................................................................... 31 Updating Unicenter CA-7 ................................................................................................ 32 Starting CA-CPS ............................................................................................................ 32

Chapter 4: Installing and Configuring Unicenter AutoSys Job Management Components 33 Installing and Configuring the Java Listener ............................................................................ 33

Prerequisites................................................................................................................. 33 Installing the Java Listener ............................................................................................. 34 Configuring the Java Listener .......................................................................................... 35 Starting and Stopping Java Listener ................................................................................. 38 Testing the Java Listener ................................................................................................ 40 Running the Java Listener as a Windows Service ................................................................ 41 Configuring Java for AIX ................................................................................................. 42

Installing and Configuring RCS.............................................................................................. 43 Installing the RCS.......................................................................................................... 43 Configurable Values and Files .......................................................................................... 44 Starting and Stopping .................................................................................................... 46 Logging........................................................................................................................ 46 Debugging.................................................................................................................... 46

Chapter 5: Installing Unicenter Enterprise Job Manager 47 Installing Unicenter Enterprise Job Manager ............................................................................ 47

Important Considerations Before Installing ........................................................................ 47 Installing Unicenter Enterprise Job Manager on the Server................................................... 48 Installing Unicenter Enterprise Job Manager Silently ........................................................... 49

Uninstalling Unicenter Enterprise Job Manager......................................................................... 50 Installing CA Common Services............................................................................................. 50

Important Considerations before Installing ........................................................................ 50 Installing CA Common Services for Unicenter Enterprise Job Manager ................................... 51 Installing CA Common Services Silently ............................................................................ 52

Chapter 6: Configuring Unicenter Enterprise Job Manager 53 Configuration Tasks............................................................................................................. 53

Setting the CPS_MULTI_SERVER Environment Variable ....................................................... 54 Setting Up Portal ........................................................................................................... 54

Contents v

Configuration Manager ................................................................................................... 71 Setup Tab .................................................................................................................... 71 CAICCI Link Definitions................................................................................................... 72 Verifying CAICCI Link Status ........................................................................................... 72 Adding and Configuring Servers....................................................................................... 72 Verifying Server Status................................................................................................... 72 Adding Host Access Link Definitions.................................................................................. 73 Security Tab ................................................................................................................. 73 Environment Tab ........................................................................................................... 75 Deploy Tab ................................................................................................................... 75

Stopping and Restarting Services .......................................................................................... 76 Restarting User Sessions ................................................................................................ 77

Logging In to the Portal ....................................................................................................... 78 Session Security ................................................................................................................. 78 Modifying Session Timeout Values ......................................................................................... 78

CleverPath Portal Timeouts ............................................................................................. 79 Scheduling and Monitoring Timeouts ................................................................................ 79 Timeouts for Other Servers ............................................................................................. 79

SAP Java Connector............................................................................................................. 80

Chapter 7: Configuring Event Management 81 Consolidated Event Console .................................................................................................. 81 Creating a Consolidated Event Console to View Unicenter AutoSys Job Management Messages ....... 82

Step 1: Send Unicenter AutoSys Job Management Messages to the Unicenter Event Console on the Unicenter AutoSys Job Management Event Processor Machine .............................................. 83 Step 2: Forward Unicenter AutoSys Job Management Messages to the Unicenter Event Console on the Focal Point System ................................................................................................... 85

Setting Up Alarm Management.............................................................................................. 86

Chapter 8: Configuring Your Browser 87 Mozilla 1.6 for Windows ....................................................................................................... 87 Mozilla 1.6 for Linux ............................................................................................................ 88 Increasing the Initial and Maximum Heap Size on the Client Machine.......................................... 89

Chapter 9: Implementing Secure Sockets Layer 91 What Is SSL?...................................................................................................................... 91 Implementing SSL with Unicenter Enterprise Job Manager......................................................... 92

Tomcat and Portal ......................................................................................................... 92 SSL Architecture............................................................................................................ 92 Tomcat Standalone SSL Configuration .............................................................................. 93

vi Administrator Guide

Tomcat with IIS-SSL .....................................................................................................100 Troubleshooting Tips .....................................................................................................100

Appendix A: Acknowledgements 101 Acknowledgements ............................................................................................................102

Index 125

Introduction 7

Chapter 1: Introduction

This guide describes configuration tasks you must perform to enable Unicenter Enterprise Job Manager to function in your enterprise. It is intended for system administrators.

The guide provides information about:

Unicenter Enterprise Job Manager features

Installing Unicenter® CA-7® Job Management host components

Installing and configuring Unicenter® AutoSys® Job Management components

Installing Unicenter Enterprise Job Manager

Configuring Unicenter Enterprise Job Manager

Configuring Event Management

Browser considerations

Implementing Secure Sockets Layer

Documentation Set The following guides are provided with Unicenter Enterprise Job Manager:

Unicenter Enterprise Job Manager Release Summary

Unicenter Enterprise Job Manager Administrator Guide

Unicenter Enterprise Job Manager Host Access User Guide

Contact Customer Support For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Customer Support at http://ca.com/support.

Concepts and Components 9

Chapter 2: Concepts and Components

This chapter helps you to become familiar with the layout of Unicenter Enterprise Job Manager, and to understand its basic concepts and components.

Architecture The Unicenter Enterprise Job Manager architecture has three tiers:

Web client tier

Server tier

Back-end system tier

The tiers and their functions are depicted in the following illustration:

Architecture

10 Administrator Guide

Web Client Tier

From the web client tier, you use the main interface to access the primary Unicenter Enterprise Job Manager functions. The main interface uses CleverPath Portal, which is required at installation.

Server Tier

Most of the work is performed in the server tier. This level includes the interfaces, servlets, servlet engines, and adapters, including the portal application. Each functional category has its own servlet deployed in a private servlet engine.

Each servlet acts as a central point of communication and management between the Web Application and the back-end job management machine. The primary function of the server tier is to provide an interface to the Web Application to allow you to configure and monitor jobs.

Back-end System Tier

The back-end management server, or system, tier includes instances of Unicenter CA-7 Job Management and Unicenter AutoSys Job Management.

Job Command Center


Job Command Center The discipline of Job Management requires real-time status information for your enterprise. Status information must be available in summary form, and the detail information supporting the summary must be readily accessible. For example, it is vital to be informed by the system when a job or job stream is delayed. However, this is not enough. Immediate access to detailed information on the cause of the delay is equally important. Information at both summary and detail levels must be available to Job Management operators and supervisors. Increasingly, this same information must be communicated to other stakeholders in your enterprise.

Job Command Center is a powerful feature that provides users in your enterprise with information at both a summary and detail level. The portlets in Job Command Center provide graphical summaries of key status information related to a particular functional area (job/job stream monitoring; scheduling, or system administration. These portlets are available to users based on their roles in the enterprise and their associated access rights. From the summary information, users can launch the features of Job Command Center in context, to get detailed information that will enable them to analyze warnings and failure points, and take appropriate action to correct any problems.

With Job Command Center, your enterprise will have all the information required to efficiently and effectively manage the job management function. The following sections describe the portlets included in Job Command Center:

Quick Start

The Quick Start portlet displays links to the Unicenter Enterprise Job Manager features to which the current user has access. Depending upon your access level, the Quick Start portlet may display the following features:

Configuration

Job Editor

Event Console

Host Access

Job Flow Design

Job Flow Monitoring

Job Flow Overview

Job Status Console

To launch a feature, click its name in the Quick Start portal. The selected feature opens in a separate window.

Job Command Center


Job Status Views

The Job Status Views portlet displays the Job Status Console view name and dashboard status for all the views in the enterprise. Click any view name to launch Job Status Console, displaying the selected View.

Job Flow Monitoring

Users and system administrators can use the Job Flow Summary View portlet to create and publish Job Flow Summary Views. Job Flow Summary Views consist of one or more Job Flows, and display graphical status information for the Job Flow (in pie chart or bar chart form) and a list view that summarizes status information for the jobs in the Job Flow.

Job Editor Find Object

From the Job Editor Find Object portlet, schedulers and other authorized users can search for a particular job or job object, or perform a wildcard search on a character string to locate a particular job or job object on the selected Unicenter AutoSys Job Management or Unicenter CA-7 Job Management server.

Job Editor Create Object

From the Job Editor Create Object portlet, schedulers and other authorized users can launch Job Editor in context to create a job or job object on the selected Unicenter AutoSys Job Management or Unicenter CA-7 Job Management server.

CCI Link Status

The CCI Link Status portlet summarizes the status of all CCI Links defined on the Unicenter Enterprise Job Manager server. Click a CCI Link name to launch Configuration, displaying the properties of the selected CCI Link.

Server Status

The Server Status portlet summarizes the status of all Unicenter AutoSys Job Management and Unicenter CA-7 Job Management servers defined on the Unicenter Enterprise Job Manager server. Click a server name to launch Configuration, displaying the properties of the selected server.

Job Command Center


Services Status

The Services Status portlet summarizes the status of the Unicenter Enterprise Job Manager services. Click an entry to launch Configuration, displaying the Services page.

Credentialed User Summary Status

The Credential User Summary Status portlet summarizes the credentialed users that are within n days of expiring. Click a Credential User name to launch Configuration, displaying the properties of the selected Credential User.

Credential Group Summary Status

The Credential Group Summary Status portlet summarizes the credentialed groups that are within n days of expiring. Click a Credential Group name to launch Configuration, displaying the properties of the selected Credential Group.

Shift Notes

The Shift Notes portlet lets you add and review notes in a discussion board format.

Job Editor


Job Editor The Job Editor lets you perform tasks related to job management and scheduling. You can view, create, modify, and delete jobs and their associated objects, including jobsets (box jobs or systems), calendars, predecessor jobs, successor jobs, triggers, and global variables.

The interface provides a tree (in the left pane) to display the objects defined in your enterprise. You can filter the tree view to focus on a specific set of jobs or job objects.

When you select an object in the tree, the right pane provides detailed information about that object through multiple views.

The Job Editor lets you administer all of your job scheduling objects using the following views:

Unicenter AutoSys Job Management Views

The Unicenter AutoSys Job Management views allow you to administer global variables, calendars, jobs, and jobsets (box jobs). The views are customized for each type of object, and include the Primary, Schedule, Alarms, Permission, and the Command Info tab for Command jobs or the Resource/Profile tab for File Watcher jobs.

Unicenter CA-7 Job Management Views

The Unicenter CA-7 Job Management views allow you to administer ARFSETs, calendars, datasets, jobsets (systems), and jobs. The views are customized for each type of object, and include the Primary, Resources and JCL views.

Flow View

The Flow View offers a graphical representation of the logical flow of job execution. This view displays the dependencies of a jobset or job, showing you its predecessors and successors.

Job Editor


Requirements View

The Requirements View is a graphical display of all relationships a job or jobset has with other objects, including the conditions of these relationships that must be met before the job or jobset can run. In this view, you can use drag-and-drop to create objects or to create or modify relationships for the selected job or jobset. The following illustration shows a sample Requirements View:

For more information about the Job Editor, see the Job Editor Help.

Job Flow Monitoring


Job Flow Monitoring Job Flow Monitoring allows you to define logical groups of jobs, or Job Flows, that relate to specific business functions in your enterprise. The Job Flows provide integrated views across servers, platforms, and products.

Operating Modes

Job Flow Monitoring includes two portlets:

The Job Flow Monitoring portlet allows you to monitor jobs and other scheduler objects in the Job Flow.

The Job Flow Design portlet allows administrators and authorized users to create or edit Job Flows and specify access for users and groups of users.

Availability of the Job Flow Design applet depends upon your authorized level of access.

With Job Flow Monitoring, scheduling administrators and operators can monitor the overall health of Job Flows, identify failure points swiftly, and take appropriate action.

Job Flow Monitoring


Monitoring Job Flows

When you launch Job Flow Monitoring, the left pane displays the Job Flows defined for your enterprise. Expand a Job Flow object to display its jobs and jobsets.

Each node in the tree displays an icon reflecting the real-time status of the current object, helping you to identify job streams that require attention.

The right pane of Job Flow Monitoring provides detailed information about the objects in the Job Flow through a variety of views:

Graph View

Displays the overall health of the system at a glance. The segments of the graph illustrate the status of the Job Flow components, the jobs and jobsets. Each status, such as Running, Inactive, or Success, is color-coded. A legend identifies the associations between color and status. When you move the mouse over a particular segment, the status and percent represented by that segment appears. You can also view this graph as a bar chart.

List View

Displays job data in a table format, including name, description, owner, job type, status, and scheduling information.

Flow View

Displays the flow of the jobs in a selected Job Flow in a graphical format, in which colors represent status and lines with different styles and colors represent relationships. This view can be at the Job Flow level or at the Job level.

Requirements View

Displays a focused form of the Flow View, with all the job objects directly related to the job you selected.

Properties

Displays complete details of a job in a table format.

For more information about Job Flow Monitoring features and views, see the Job Flow Monitoring Help.

Job Status Console


Job Status Console The Job Status Console is a Web application that provides a real-time, consolidated view of the enterprise, with Job Status, Alert, and Dashboard information.

The Job Status Console provides a powerful alternative to the Job Flow Monitoring interface. Advantages of the Job Status Console include ease of use, compatibility with Java and non-Java browser platforms, and performance.

For more information, see the Release Summary and the Job Status Console Help.

Using Job Status Console

The Job Status Console contains the following tabs:

Job Status

Alerts

Dashboard

Job Status Console


Job Status Tab

From the Job Status tab, you can see the status of the jobs for the selected job management server or view.

From the list of jobs, you can select a job and view its details. The details show the specific properties for each job. From this point, you can manage the job. For example, you can start, stop, or suspend the job, depending on the job manager’s capabilities.

Alerts Tab

In the Job Status Console, you can define alert policies for your enterprise. When the policies are deployed, you can click the Alerts tab to display all alerts generated that match the criteria defined in your policies. You can acknowledge or close alerts and AutoSys alarms from this view.

Dashboard Tab

From the Dashboard tab, you can see the statistical summary of job status and alerts for the current server or view. In addition, you can set the policies to define the severity level of the Dashboard. Based on this configured level of severity, the Dashboard can display a visual cue to alert you to a potential problem.

Specialized View

The Job Status Console also provides specialized views including CA-7’s Run Log and Prior Run queues, the AutoSys Event Processor log, and standard output, standard error, and remote agent logs.

Event Console and Event Management


Event Console and Event Management Event Management is a valuable tool to help you monitor both job management and system events enterprise-wide, giving you the ability to define and initiate a sequence of actions for a particular event message. Event Management automatically collects related network-wide messages, displays them at a single location or routes them to the appropriate locations as needed, and initiates message actions based on user-defined policy.

The Event Console provides a graphical viewer for events in Unicenter-managed environments. You can forward job manager and system events from individual Event Agents to one or more central Event Managers, then view, filter, and respond to the events in the Event Console. Unicenter AutoSys Job Manager, Unicenter NSM Job Management Option, Unicenter CA-7 Job Manager, Unicenter Scheduler Job Manager, and Unicenter Jobtrac Job Manager can all be configured to forward event messages to an Event Console.

For more information, see the Event Console Help (available from the Event Console portlet), and the chapter “Configuring Event Management” in this guide.

Host Access The Host Access portlet provides a web-based terminal emulator to access 3270 host applications.

You create links to 3270 hosts using the Configuration interface.

For more information, see the Host Access Help (available from the Host Access portlet).

Configuration Unicenter Enterprise Job Manager provides full system configuration capabilities. System administrators can configure Job Scheduling, Job Flow Monitoring, and Job Status Console runtime parameters, connectivity to back-end servers, users, CAICCI nodes, OPS/MVS links, and services, and can deploy configuration changes. In addition, administrators can assign credentialed users and groups to back-end servers, providing both an enhanced level of security and simplified logins for users accessing multiple back-end servers.

For more information, see the Configuration Manager Help.

Installing Unicenter CA-7 Host Components 21

Chapter 3: Installing Unicenter CA-7 Host Components

Before you install and configure the essential components used on your Unicenter CA-7 host machine, make sure you are familiar with the components, structure, and concepts of Unicenter Enterprise Job Manager, as described in the chapter "Concepts and Components" in this guide.

Depending on other Computer Associates products and features that may be installed already, you may have performed some of these steps previously. It is not necessary to perform these steps again. The procedures in this chapter contain notes indicating whether you can skip the specific steps.

Reviewing Your Installation Tasks


Reviewing Your Installation Tasks The following is an overview of the steps you must perform to complete the installation and configuration of the essential components on your Unicenter CA-7 host machine. We recommend that you review these steps before beginning, so that you have all the materials and information you need to ensure a smooth and successful installation.

To complete the installation and configuration of your Unicenter CA-7 host machine, follow these steps:

1. Install the required CA Common Services for z/OS components.

2. Install CA-CPS.

3. Link edit CAICCI with TCP/IP.

4. Configure the TCP/IP Gateway server started task.

5. Define parameters for the TCP/IP Gateway server started task.

6. Test TCP/IP communications.

7. Customize the CAIENF procedure to initiate the SCHSRVR task.

8. Define the PROFILE data set used by the SCHSRVR task.

9. Modify the SCHSRVR task.

10. Identify the SCHSRVR started task to the host security systems.

11. Merge the Unicenter CA-7 Product table into the CA Common Services for z/OS ViewPoint Control table.

12. Restart CAIENF.

13. Update Unicenter CA-7.

14. Start CA-CPS.

The following sections provide more information to help you configure your Unicenter CA-7 server so that it can communicate with Unicenter Enterprise Job Manager.

Installing the Required CA Common Services for z/OS Components

Before you install and configure the Unicenter CA-7 Host system, install the required CA Common Services for z/OS components. You must ensure that all of the required FMIDs are installed. These are listed in the z/OS Server Minimum Requirements provided in the Unicenter Enterprise Job Manager Readme file. If any FMIDs are missing, install them before continuing. For instructions, see the CA Common Services for z/OS Getting Started guide.



Installing CA-CPS

If the Unicenter® CA-7® Webstation Component is installed, you can skip this step; however, you must verify that the configuration options are set as detailed in this step.

After you have installed the necessary CA Common Services for z/OS components, you must install CA-CPS. For instructions on installing CA-CPS FMID CWR1000, see the CA Common Product Services Installation Guide.

Ensure that the CA-CPS configuration options are set as follows:

PASSMODE should be set to WARN or DORM rather than FAIL.

ULIMIT should be set to 10 (minimum).

SLIMIT should be set to 50 (minimum).

SESSTOUT should be set to 60 (minutes).

For more information on the CA-CPS configuration values, see the CA-Common Product Services Installation Guide.

Link Editing CAICCI with TCP/IP

If Unicenter CA-7 Webstation Component is installed, or you are doing cross-platform scheduling with Unicenter CA-7, you can skip this step.

After CA-CPS has been installed, you must link edit CAICCI with TCP/IP. Requirements for link editing CAICCI with TCP/IP differ based on the combination of TCP/IP and runtime libraries you are using. For a description of the link edit process, see one of the following Computer Associates publications:

CA Common Services for z/OS Getting Started

CA Common Services for z/OS Administrator Guide



Configuring the TCP/IP Gateway Server Started Task

If Unicenter CA-7 Webstation Component is installed, or you are doing cross-platform scheduling with Unicenter CA-7, you can skip this step.

The next step in the process is to configure the TCP/IP Gateway started task. CAI.CAIPROC member CCITCPGW contains the JCL needed to run the CAICCI TCP/IP Gateway server using IBM TCP/IP with LE/370.

Unicenter® TCPaccess™ Communications Server Users

If you do not have the SAS C Runtime modules in a LNKLST data set, concatenate your runtime library to the appropriate CAICCI TCP/IP load library. (Unicenter TCPaccess Communications Server provides the SAS C Runtime library.) The Unicenter TCPaccess Communications Server load library should be ahead of the SAS C library in the CCIGWI3 STEPLIB concatenation.

IBM TCP/IP Users

If you do not have the IBM LE/370 or SAS C Runtime modules in a LNKLST data set, concatenate your runtime library to the appropriate CAICCI TCP/IP load library.

TCP/IP is normally provided with the operating system for most servers. Consult your vendor documentation for more information.

The following sections provide instructions to define the values for the PROTOCOL statement and identify a port number for your TCP/IP connections. Examples are provided in the section following these instructions.

PROTOCOL Statement

To start the desired TCP address space for host-to-host connectivity, include the PROTOCOL(TCPIPGW,...) statement in the data set pointed to by the //ENFPARMS DD statement with your CAIENF started task JCL. PROTOCOL(TCPIPGW,…) starts procedure CCITCPGW to use IBM TCP/IP (with the IBM C Runtime) for host-to-host connectivity.

TCP/IP can be started before or after any of the CAICCI address spaces. If TCP/IP services are not available, the Gateway server started task periodically retries the connection until TCP/IP starts. If TCP/IP is shut down for any reason, the Gateway server started task terminates. If originally started by CAICCI, the Gateway server started task restarts automatically and again polls for TCP/IP restart. Otherwise, you must restart the address space manually. To manually restart the CAICCI Gateway server, issue the following console command:

ENFPROTOCOL(TCPIPGW,...)



Port Number

TCP/IP connections are based on network addresses, plus a port number. The combination of address and port number uniquely identifies each application on the network. CAICCI, like all other TCP/IP applications, requires that you specify a port number for its use. This port number must be available to both the mainframe CAICCI software and PC client systems.

By default, CAICCI uses port number 7000 for host-to-host connectivity.

Examples

IBM TCP/IP users

If CAICCI starts the TCP address space, override the port number using the associated PROTOCOL statement in the //ENFPARMS DD statement of the CAIENF started task JCL. For example:

SYSID(SYSA) PROTOCOL(TCPIPGW,1721,,SYSA)

Unicenter TCPaccess Communications Server users

If CAICCI starts the TCP address space, override the port number using the associated PROTOCOL statement in the //ENFPARMS DD statement of the CAIENF started task JCL. For example:

SYSID(SYSA) PROTOCOL(TCPIP3GW,SSID=ACSS:1721,,SYSA)

Note: ACSS is the default name for the Unicenter TCPaccess Communications Server subsystem.



Testing TCP/IP Communications

To test TCP/IP communications from the server, issue the following command from a command prompt:

PING ipaddr

where ipaddr is the TCP/IP address or the DNS name of the target Unicenter CA-7 host system where CA-CPS is installed.

Ask your network systems programmer for the TCP/IP address or DNS name of the host computer where TCP/IP is installed and running.

You should receive a response similar to the following:

Pinging ipaddr with 32 bytes of data:

Reply from ipaddr: bytes=32 time=110ms TTL=55



From the z/OS system, at the TSO READY prompt, enter:

PING ipaddr

Where ipaddr is the TCP/IP address or the DNS name of the server on which Unicenter Enterprise Job Manager is to be installed.

You should receive a response similar to the following:

Ping V3R1: Pinging host ipaddr. Use ATTN to interrupt.

PING: Ping #1 response took 0.457 seconds. Successes so far 1. READY



Customizing the CAIENF Procedure to Initiate the SCHSRVR Task

If Unicenter CA-7 Webstation Component or Unicenter CA-7 Job Management Workstation Option is installed, you can skip this step.

You must customize CAIENF with the spawn parameters necessary to start the Unicenter Enterprise Job Manager communications task. To define the spawn parameters, create a PDS member to contain the CAICCI spawn parameters. The CAIENF procedure SPNPARMS DD statement points to these parameters. The spawn parameters describe the SCHSRVR started task and allow it to be started when Unicenter Enterprise Job Manager makes an initial session request through CA-CPS to Unicenter CA-7. When this request is initiated, CA-CPS issues a CAICCI SPAWN request (on behalf of the requestor) to CAIENF that, upon completion, initiates the SCHSRVR started task that communicates with Unicenter CA-7.

The CAIENF procedure ENFPARMS and SPNPARMS DD statements are particularly important. The ENFPARMS DD statement specifies the CAICCI control options and the SPNPARMS DD statement specifies the controls for spawned procedures. Unicenter Enterprise Job Manager requires the SCHSRVR spawned procedure.

The following illustration shows the relationship between the CAIENF procedure, the ENFPARMS DD, and the SPNPARMS DD.

The following are sample spawn parameters you can use to point to the SCHSRVR member addressed by the SPNPARMS DD statement:

UL2 SERVICE START=SPAWN_ONLY, SERVER_NAME=MVS_START_SERVER, SIGNON=SERVICE PROCESS PROCESS_TYPE=MVS_STC, PROCNAME=SCHSRVR



Defining the PROFILE Data Set Used by the SCHSRVR Task


The PROFILE DD statement refers to the CA Common Services for z/OS ViewPoint Profile data set. It contains application-specific information and is created during the installation of CA Common Services for z/OS ViewPoint.

The CA Common Services for z/OS sample JCL library contains member WCnnPROF to allocate the Profile data set, where nn represents the version number. This is a partitioned data set containing at least one member. The name of that member is CACCENV.

Note: The version number replaces nn. If the version number is 2.0, the JCL member is WC20PROF.

Add these statements to the CACCENV member:

CA7APPL=applid CA7SESS=high_acb_name

where:

applid

identifies the VTAM APPLID for the Unicenter CA-7 task with which the server is to communicate. The applid is in the Unicenter CA-7 initialization file on the APPL= keyword of the UCC7VTAM statement.

high-acb-name

identifies the set of VTAM ACB names the Unicenter CA-7 application programming interface (API) can use locally to establish communications with Unicenter CA-7. For example, if you have ten ACBs (CA70001 through CA70010), you should specify CA7SESS=CA70010. The interface deduces from this that there are ten ACBs from which to choose, and locates an available ACB from that pool.

For more information about these parameters, see the Unicenter CA-7 Interfaces Guide, CA-7/API Requirements.

Note: There is a one-to-one correlation between the value placed in the Unicenter CA-7 high-acb-name and the CA-CPS SLIMIT value. Each pertains to the number of concurrent sessions that can take place between active web browser sessions in Unicenter Enterprise Job Manager and Unicenter CA-7 on the z/OS server. The effective limit on the number of sessions will be the lower of these two settings. For more information about the CA-CPS SLIMIT value, see the CA Common Product Services Installation Guide.



Modifying the SCHSRVR Task


When a user logs on to Unicenter Enterprise Job Manager, a communication session in CA-CPS starts on behalf of the user initiating the request. This process initiates the SCHSRVR task defined in the section Customize the CAIENF Procedure to Initiate the SCHSRVR Task in this chapter.

The following is a sample SCHSRVR procedure:

//SCHSRVR PROC //* //SCHSRVR EXEC PGM=CCISRVR,REGION=4M //STEPLIB DD DISP=SHR,DSN=CAI.CAILIB //SYSPRINT DD SYSOUT=*,FREE=CLOSE //PROFILE DD DISP=SHR,DSN=CA.UNI.PROFILE

Note: If the z/OS load library for Unicenter CA-7 is not in the z/OS systems LINKLIST, you must add it to the STEPLIB DD concatenation.



Identifying the SCHSRVR Started Task to the Host Security Systems


You must define the SCHSRVR task to the security package installed on the z/OS server to permit CAIENF authority to START and CANCEL the SCHSRVR procedure.

For eTrust CA-ACF2

Create a logon ID for the SCHSRVR started task:

SET LID INSERT SCHSRVR MUSASS MUSUPDT STC

For eTrust CA-Top Secret

Create an ACID for the SCHSRVR started task:

TSS CREATE(SCHSRVR) TYPE(USER) FACILITY(STC) NAME(SCHSRVR) PASSWORD(NOPW,0) DEPT(ANYDEPT)

Add the SCHSRVR started task to the eTrust CA-Top Secret started task table:

TSS ADD(STC) PROC(SCHSRVR) ACID(SCHSRVR)

For RACF

Define the SCHSRVR started task to the STARTED task RACF class. The following example shows the command necessary for the z/OS security server:

RDEFINE STARTED (SCHSRVR.?) STDATA (USER(=MEMBER) GROUP(STCGRP))



Merging the Unicenter CA-7 Product Table


After you have identified the SCHSRVR task to the host security systems, you must merge the Unicenter CA-7 Product Table into the CA Common Services for z/OS ViewPoint Control Table.

The CA Common Services for z/OS sample JCL library contains member WCnnMRG, where nn represents the version number. This member is created when you install the ViewPoint common component CWC1200 or CWC2000. WCnnMRG is the model JCL that merges individual product tables into the CA4FAPPL table.

Note: The version number replaces nn. If the version number is 2.0, the JCL member is WC20MRG.

The following Unicenter CA-7 Product Table must be merged for Unicenter Enterprise Job Manager:

Control Table name: CA4FAPPL

Product Table name: CAL2APPL

Description: Unicenter CA-7 Application Control Table

To run WCnnMRG, follow the instructions contained in the member. At the bottom of the JCL, there are four EXEC statements for the embedded proc. Use the one for the APPL table only. The EXEC statement should read:

//APPL EXEC WC20MRG,TABLE=APPL,PROD=L2

For more information about the Unicenter CA-7 Product Table, see the Unicenter CA-7 Interfaces Guide, CA-7/API Requirements.

Restarting CAIENF

You must restart CAIENF so that the changes you entered in the previous steps take effect.



Updating Unicenter CA-7

After you restart CAIENF, perform the following steps to update Unicenter CA-7 (if needed):

1. Add virtual terminal definitions, if needed. Each Unicenter Enterprise Job Manager session uses a Unicenter CA-7 virtual terminal to communicate with Unicenter Enterprise Job Manager. If you have not defined Unicenter CA-7 virtual terminals, or if you need to increase the number of virtual terminals, see the discussions of the UCC7VTAM, LINE, and TERM initialization statements in the Unicenter CA-7 Systems Programmer Guide. Enable the online Calendar maintenance facility. This feature allows you to create, update, and delete Unicenter CA-7 base calendars without the need for z/OS batch assemblies. Add the following statement to your Unicenter CA-7 initialization file:

CALENDAR,DSN=calendar.dsnname

where calendar.dsnname specifies the fully qualified name of the Unicenter CA-7 Calendar PDS.

2. Enable the online Calendar maintenance facility. This feature lets you create, update, and delete Unicenter CA-7 base calendars without the need for z/OS batch assemblies. Add the following statement to your Unicenter CA-7 initialization file:

CALENDAR, DSN=calendar.dsname

where calendar.dsname specifies the fully qualified name of the Unicenter CA-7 Calendar PDS.

3. Enable Unicenter CA-7 mixed case editor support to allow you to use mixed case in JCL and prose. This is critical to support cross-platform scheduling definitions. Ensure that the following keyword is specified in the OPTIONS statement in the Unicenter CA-7 initialization file:

OPTIONS,INITCASE=YES

4. Ensure that the user IDs used to log on to Unicenter Enterprise Job Manager are authorized for use with Unicenter CA-7.

If you made any changes to the initialization file, restart Unicenter CA-7 to activate the changes. For more information about virtual terminal definitions and the Unicenter CA-7 initialization file, see the topic CA-7/API Requirements in the Unicenter CA-7 Interfaces Guide.

Starting CA-CPS

When you have completed all of the preceding steps, you can start the CA-CPS started task you installed previously (see Installing CA-CPS (on page 23)).

Installing and Configuring Unicenter AutoSys Job Management Components 33

Chapter 4: Installing and Configuring Unicenter AutoSys Job Management Components

One of the following Unicenter AutoSys Job Management components must be installed and configured to access an AutoSys instance:

Java Listener

Remote Command Service (RCS)

For Unicenter AutoSys Job Management r4.5 installations, use either the Java Listener or the Remote Command Service. For Unicenter AutoSys Job Management r4.0 installations, use the Java Listener.

Installing and Configuring the Java Listener The following sections describe how to set up the Java listener for Unicenter AutoSys Job Management r4.0 or r4.5 installations. For information about RCS, see Installing and Configuring RCS (on page 42).

Prerequisites

Before installing the Java Listener, verify that you have the following software and settings:

Sun Java Runtime Environment (JRE) 1.4

If you are installing the Java Listener on the AIX operating system, see Configuring Java for AIX (on page 38).

A Unicenter AutoSys Job Management 4.0 or 4.5 Event Processor machine or Remote Agent machine. The Java Listener will run on one of these machines.

Note: At a minimum, the Java Listener must be installed on the Event Processor machine.

A defined environment variable for the Unicenter AutoSys Job Management database:

– For Sybase database, variable SYBASE

– For Oracle database, variables ORACLE_HOME and TNSNAME

Installing and Configuring the Java Listener


Installing the Java Listener

Obtain the Java Listener from one of the following sources:

Unicenter AutoSys Job Management Web Interface r4.5 installation media

PTF for Unicenter AutoSys Job Management r4.0 from the CA Technical Support web site. (For detailed information on PTFs required for Unicenter AutoSys Job Management r4.0, see the Unicenter Enterprise Job Manager Readme.)

To install the Java Listener using the Unicenter AutoSys Job Management Web Interface r4.5 installation media, perform the following steps:

Note: If you obtained the Java Listener as a Unicenter AutoSys Job Management PTF, start at Step 4.

1. Insert the Unicenter AutoSys Job Management Web Interface r4.5 installation media into the drive.

2. Locate the JavaListener directory.

3. Expand the JavaListener directory and select the directory for your platform (for example, AIX, HP, Linux, Solaris, Tru64, or Windows).

4. Copy the entire directory for the selected platform to a new directory on your machine. While you can create a directory anywhere on your system, we recommend that you create the directory structure as follows:

Windows

Program Files\CA\UnicenterAutoSysJMJavaListener

Unix and Linux

/opt/CA/UnicenterAutoSysJMJavaListener



Configuring the Java Listener

You must configure the Java Listener to work properly with Unicenter AutoSys Job Management.

Note: After modifying configuration files, you must restart the Java Listener.

Edit the autosysenv.cfg File

Edit the file autosysenv.cfg, located in the Java Listener root directory. Add the following definitions:

Definition Description

port=<portnumber> Listening port (required)

<instance>:AUTOSYS=<autosys> Path to the autosys directory (required).

Note: The instance name is required on this and following statements.

<instance>:AUTOUSER=<autouser> Path to the autouser directory (required)

<instance>:AUTOREMOTEDIR=<autoremotedir>

Path to the autoremotedir directory (required)

<instance>:logdir=<agentlogdir> Path to the agent log directory (required on Remote Agent machines)

<instance>:eplogfile=<eplogfile> Path to the Event Processor log file (required on Event Processor machine)

<instance>:lines=<eploglines> Number of lines sent from Event Processor log file in each request (optional; default is 200)

Note: Only one instance of the Java Listener can be installed on a server. If you have more than one instance of Unicenter AutoSys Job Management installed on the AutoSys Event Processor machine, you can make multiple entries in autosysenv.cfg.



Examples of valid autosysenv.cfg files are as follows:

Windows

Note: This example shows two different Unicenter AutoSys Job Management instances, ACE and A40, in the autosysenv.cfg file.

port=5555 ACE:AUTOSYS=C:\Program Files\CA\UnicenterAutoSysJM.ACE\autosys ACE:AUTOUSER=C:\Program Files\CA\UnicenterAutoSysJM.ACE\autouser ACE:AUTOREMOTEDIR=C:\Program Files\CA\UnicenterAutoSysJM.ACE\tmp ACE:logdir=C:\tmp1 ACE:eplogfile=C:\Program Files\CA\UnicenterAutoSysJM.ACE\autouser\out\event_demon.ACE ACE:lines=200 A40:AUTOSYS=C:\Program Files\CA\UnicenterAutoSys.A40\autosys A40:AUTOUSER=C:\Program Files\CA\UnicenterAutoSys.A40\autouser A40:AUTOREMOTEDIR=C:\Program Files\CA\UnicenterAutoSys.A40\tmp A40:logdir=C:\Program Files\CA\UnicenterAutoSys.A40\tmp A40:eplogfile=C:\Program Files\CA\UnicenterAutoSys.A40\autouser\out\event_demon.A40 A40:lines=200

Unix

port=4444 ACE:AUTOSYS=/autosys/LINUX/ORA/autosys ACE:AUTOUSER=/autosys/LINUX/ORA/autouser ACE:AUTOREMOTEDIR=/tmp ACE:eplogfile=/autosys/LINUX/ORA/autouser/out/event_demon.ACE ACE:lines=200



Edit the validips File

The next step in configuring the Java Listener is to edit the validips configuration file, which is located in the Java Listener root directory.

You must add the IP addresses of the Unicenter Enterprise Job Manager server machines that will access this Java Listener. Type each IP address on its own line, as shown below:

127.0.0.1 123.123.123.123 222.222.222.222



Starting and Stopping Java Listener

You must designate who can start or stop the Java Listener.

User Permission

The user who starts the Java Listener should have the Unicenter AutoSys Job Management Edit Superuser privilege. Also, the user who starts the Java Listener must have write privileges to the directory where the Listener resides.

Windows

On Windows, the user must also have the rights “Act as part of the operating system” and “Log on as a service.”

To set the right “Act as part of the operating system,” do the following:

1. From the Start menu, select Settings, Administrative Tools, Local Security Policy.

The Local Security Settings dialog appears.

2. Expand the Local Policies folder and select User Rights Assignment.

The policies are displayed in the right pane.

3. Double-click “Act as part of the operation system” policy.

The Properties dialog appears.

4. Add the user name to the list, and then click OK.

To set the right “Log on as a service,” perform the previous steps again, except at Step 4, select the “Log on as a service” policy.

UNIX

On UNIX, the program CheckUserLogon must have the permission to validate the user’s credentials.

In the directory /opt/CA/UnicenterAutoSysJMJavaListener\bin, execute the following command to set the permission for the CheckUserLogon program:

chmod u+s CheckUserLogon.exe



Starting and Stopping

To start and stop the Java Listener, do the following.

Windows

On Windows:

To start the listener, execute the startListener.bat file located in the Java Listener directory.

To stop the listener, execute the stopListener.bat file located in the Java Listener directory.

To run Java Listener as a service on Windows, see Running the Java Listener as a Windows Service(on page 37).

UNIX

On UNIX:

To start the listener, execute the startListener.sh file from the Java Listener directory.

To stop the listener, execute the stopListener.sh file from the Java Listener directory.



Testing the Java Listener

To test the Java Listener, start it, and then perform the tasks in this section.

Verify the User's Privilege

To verify the user’s privilege, execute the following program located in the BIN directory under the Java Listener directory:

CheckUserLogon.exe OSuserid OSuserpassword

where OSuserid and OSuserpassword are the user ID and password of the user who has the privilege of starting the Listener.

The program should return the message “Authorization is successful.”

Verify the Java Listener

To verify the Java Listener, open the file jil.log in the Java Listener directory.

If the listener is running correctly, you should see the following messages:

INFO [main] com.ca.uajm.eplis.jillistener.main - port initialized

INFO [main] com.ca.uajm.eplis.jillistener.main - Starting listener on port = 4444



Running the Java Listener as a Windows Service

The Java Listener can be run as a Windows service.

Set Up the Java Listener

From the Windows command prompt, change to the Java Listener directory, and issue the following command:

SrvCtl install path AutoSys_Super_User password

where:

path

is the directory where the Java Listener is installed (for example, c:\listener)

AutoSys_Super_User

is the Unicenter AutoSys Job Management Edit Superuser ID (username or domain\username)

password

is the password for the Edit Superuser

Start and Stop the Java Listener Service

To start the Java Listener service, issue the following command, or start the service from the Windows Services dialog:

SrvCtl start

To stop the Java Listener service, issue the following command, or stop the service from the Windows Services dialog:

SrvCtl stop

Remove the Java Listener Service

To remove the Listener service, issue the following command:

SrvCtl remove



Configuring Java for AIX

If you are installing the Java Listener on AIX, you must make sure JRE 1.4 is properly configured.

Note: If you are installing the Java Listener on AIX 4.3.3, contact CA Technical Support for additional information.

To configure JRE:

1. Download the Sun JSSE package from http://java.sun.com/products/jsse (http://java.sun.com/products/jsse).

2. Extract the JSSE package.

3. Copy jcert.jar, jnet.jar, and jsse.jar to the directory JavaHome/jre/lib/ext.

4. Edit the file JavaHome/jre/lib/security/java.security as follows:

security.provider.1=sun.security.provider.Sun security.provider.2=com.sun.crypto.provider.SunJCE security.provider.3=com.ibm.security.jgss.IBMJGSSProvider security.provider.4=com.ibm.security.cert.IBMCertPath

ssl.KeyManagerFactory.algorithm=SunX509 ssl.TrustManagerFactory.algorithm=SunX509

5. Rename JavaHome/jre/lib/ext/ibmjsse.jar (if it exists) to ibmjsse.jar_.

http://java.sun.com/products/jsse

Installing and Configuring RCS


Installing and Configuring RCS The following sections describe how to set up RCS for Unicenter AutoSys Job Management r4.5 installations. For information about the Java Listener, see Installing and Configuring the Java Listener (on page 33).

Installing the RCS

If you plan to use the Web Interface, you should select the RCS component for installation when installing the Unicenter AutoSys Job Management r4.5 base product.

RCS is included in the base installation with the following environments:

HP 9000/800, 700 HP-UX 11, 11i

IBM RS/6000 AIX 4.3.3, 5.1, 5.2

SUN SPARC Solaris 2.8, 2.9

Red Hat Linux 7.2, 7.3, 8.0, 9.0

SuSE Linux 8.0

Microsoft Windows NT 4.0 SP6, 2000 SP2, XP, 2003



Configurable Values and Files

The Remote Command Service (RCS) includes some configurable values and files including the port number, number of lines to be retrieved from EPLOG, Valid Hosts and IPs, and Valid Directories.

These parameters can be modified during the installation.

PORT NUMBER

The port on which Unicenter AutoSys Remote Command Service will listen for remote command requests

The port number default value is:

4444

EPLOG LINES

Number of lines from the Event Processor log to retrieve and return to the web server when handling an EPLOG request

The eplog lines default value is:

200

Note: After installation the PORT NUMBER and EPLOG LINES values cannot be modified.

The installation allows the user to configure the VALID HOSTS and IPs and the VALID DIRECTORIES files for the RCS. In order for the graphical user interface (GUI) and the RCS to communicate, the hostname for the GUI machine must be entered. In order to view the output or error file through the GUI, the directory path of the file must be entered.

After installation, the VALID HOST and IPs file and the VALID DIRECTORIES file can be modified by editing the validips and valid_dirs files.

The files are by default located in the RCS data directory:

/opt/CA/SharedComponents/UnicenterAutoSys/data

VALID HOSTS and IPs

After the installation, you may add or remove valid machines by modifying the validips. Open the file with a text editor and add an IP address or the hostname of the GUI machine to the list. RCS only accepts requests from the machines listed in validips

Example validips file entries:

127.0.0.1 Autosys autosys-win32 146.124.55.132



VALID DIRS

The valid_dirs file contains a list of valid directories that the RCS uses to find an output or error file from a job that has run successfully. To view a job log through the GUI, the directory path of the output or error file must be specified in this file.

Example valid_dirs file entries:

/tmp /home/autosys/logs

The valid directory refers to the directory that contains the standard output or error file that was specified in the job definition.

Example job definition using output or error file:

insert_job: example machine: localhost command: dir std_out_file: /tmp/dir.out std_err_file: /tmp/dir.err

For a user to view the output from the preceding job using the GUI, the directory, /tmp must be specified as a valid directory. When trying to view a log in which the directory is not an entry in the valid_dirs file, the request will fail the GUI will display a message saying the directory is not valid.

Note: RCS must be restarted after any modifications are made to either one of these two files.



Starting and Stopping

Use the start_rcs and stop_rcs scripts located in the autosys/bin directory to start and stop RCS.

You must run both start_rcs and stop_rcs as root.

Logging

All RCS messages including GUI requests and errors are written to the RCS log file, asrcslsn.log.

These messages are useful when a job may have been added, modified, or deleted from the Event Server, when a web user is mapped, or when an EP or Joblog request is issued through the GUI. You can also use this log file for troubleshooting. For example, when a user tries to add a job through an unknown GUI (that is, through a GUI machine that is not listed as a valid machine in the validips configuration file), the RCS log lists which GUI machine must be added to the validips configuration file.

The RCS log file rolls over daily, at midnight, and the product renames the previous day's file asrcslsn.previous_date. A new log file is then created to receive the current day's messages. Because each day has a unique RCS log file, you should perform regular maintenance on the log files to ensure disk space availability.

Debugging

When a problem occurs, RCS can write more specific system debug information to the log file. This is controlled through the RCSDEBUG system environment variable:

To have RCS write this information to the log file, set the value to 1.

Set and export the variable using the syntax of your current shell.

Example bash shell:

RCSDEBUG=ON export RCSDEBUG

Installing Unicenter Enterprise Job Manager 47

Chapter 5: Installing Unicenter Enterprise Job Manager

This chapter explains the following installation procedures:

How to install Unicenter Enterprise Job Manager on the server

How to install CA Common Services

Installing Unicenter Enterprise Job Manager This section describes how to install Unicenter Enterprise Job Manager on the server.

Important Considerations Before Installing

The installation media provides a Readme file with a description of minimum system requirements for this product. You should also review this file for any additional installation information.

We recommend that you stop all Windows programs, including antivirus software, before installing Unicenter Enterprise Job Manager, with one exception: the portal must be installed and running on the target machine.

You must ensure that all Unicenter-related processes and services, including CAICCI and CA Common Services, are stopped or shut down before starting the installation.

On Windows-based platforms, ensure that you have logged in with an ID that is part of the Administrator group.



Installing Unicenter Enterprise Job Manager on the Server

To install Unicenter Enterprise Job Manager on the server, insert the Unicenter Enterprise Job Manager installation media into the drive of the computer on which you are installing the product. The CA Unicenter Enterprise Job Manager Product Explorer opens.

If the CA Unicenter Enterprise Job Manager Product Explorer does not start, double-click the installation media drive letter in My Computer, then run setupwin32.exe. The Product Explorer Wizard appears with the options Install Unicenter Enterprise Job Manager and Install CA Common Services. The Install Unicenter Enterprise Job Manager option is selected by default.

Note: The Product Explorer lets you explore the product, view product descriptions, and review the Readme file before installing.

Click the Install button, then follow the on-screen prompts to complete the installation. (For CCS installation procedures, see Installing CA Common Services.

Note: When the installation begins, the InstallShield Multiplatform installation searches the target machine to determine whether there is an appropriate Java Virtual Machine (JVM) already installed. If not, the installation installs a temporary version. This JVM is uninstalled as part of the cleanup at the end of the installation, and does not remain on the target machine. The search and installation may take 1-2 minutes and there is no indication that a process is active. Take no action while waiting for this process to end.



Installing Unicenter Enterprise Job Manager Silently

To install Unicenter Enterprise Job Manager silently, follow these steps:

1. During the installation of Unicenter Enterprise Job Manager, select the option Create a Response File.

As the Response File is created, you are prompted for a reboot preference. This does not cause the machine to reboot during the generation of the Response File. At the end of the procedure, a response file is created. The default location is C:\Documents and Settings\administrator\setup.rep. You can accept the location or browse to a directory of your choice. When browsing to a directory, you must specify a filename. For more information, see Installing Unicenter Enterprise Job Manager (on page 39).

Important! Before you invoke silent installation from the command line, you must be aware of licensing information.

2. Refer to the TERMS AND CONDITIONS FOR THE USE OF Java™ 2 Runtime Environment (J2RE), Standard Edition, Version 1.4.2_X in the Acknowledgements section of the Unicenter Enterprise Job Manager Administrator Guide.

3. To begin silent installation, at the command prompt, navigate to the directory containing the Unicenter Enterprise Job Manager setup.jar and setup.exe files. Enter:

setup –options responsefile

Alternatively, provide the fully qualified path to the setup.exe file.

If JVM1.4.0+ is installed and is referenced in the Windows system path, enter:

java –jar setup.jar –options responsefile

The log message is logged to the console.

Note: Enter the full path to access the response file. If you install from an installation media, you must begin the installation from the hard drive of your machine, and specify the fully qualified path to setup.exe. If the path to setup.exe contains spaces, you must enclose the path with double quotes.

4. Check the Task Manager to verify that setup.exe is running.

Uninstalling Unicenter Enterprise Job Manager


Uninstalling Unicenter Enterprise Job Manager To uninstall Unicenter Enterprise Job Manager, follow these steps:

1. From the Start menu, select Settings, Control Panel, Add/Remove Programs.

2. In the dialog, select Unicenter Enterprise Job Manager and follow the prompts.

Note: The portal must be running to uninstall Unicenter Enterprise Job Manager successfully.

3. When you finish the uninstall process, restart the computer.

Installing CA Common Services CA Common Services (CCS) is required for the Event Management component of Unicenter Enterprise Job Manager. If you do not have Unicenter Event Management (Unicenter NSM) running in your enterprise, you can install CA Common Services to provide the Event Management component.

Important Considerations before Installing

During installation, CA Common Services (CCS) checks the validation of the Microsoft SQL Server administrator’s password and user ID. The following conditions must be met for the installation to proceed.

A target instance of Microsoft SQL Server must be available to the installation of CA Common Services for Unicenter Enterprise Job Manager.

The SQL Server instance can be either local, on the target server, or remote.

Mixed-mode authentication (Windows and SQL) is required for the Microsoft SQL Server instance.

You must install SQL Server Client Utilities for remote server access.

You must ensure that all Unicenter-related processes and services, including CAICCI and CA Common Services, are stopped or shut down before starting the installation.

You cannot use spaces (such as c:\Program Files\...) and special characters (such as $, *, ?, ...) in installation paths.

Installing CA Common Services


Installing CA Common Services for Unicenter Enterprise Job Manager

This section provides an overview of the procedure for installing CA Common Services for Unicenter Enterprise Job Manager. We recommend that you review these steps before beginning so that you have all of the materials and information you need to ensure a smooth and successful installation.

Note: You must ensure that all Unicenter-related processes and services, including CAICCI, are stopped or shut down before starting the installation.

Note: If you are installing CA Common Services from the Product Explorer, after installing Unicenter Enterprise Job Manager, you must restart the system first.

To install CA Common Services for Unicenter Enterprise Job Manager, insert the Unicenter Enterprise Job Manager installation media into the drive of the computer on which you are installing the product. The CA Unicenter Enterprise Job Manager Product Explorer opens.

If the CA Unicenter Enterprise Job Manager Product Explorer does not start, double-click the installation media drive letter in My Computer, then run setupwin32.exe. The Product Explorer Wizard appears with the options Install Unicenter Enterprise Job Manager and Install CA Common Services. The Install Unicenter Enterprise Job Manager option is selected by default.

Select the Install CA Common Services option, then click the Install button. Follow the on-screen prompts to complete the installation.

Installing CA Common Services


Installing CA Common Services Silently

To install CA Common Services for Unicenter Enterprise Job Manager silently, followthese steps:

1. During the installation of CA Common Services for Unicenter Enterprise Job Manager, select the option Create a Response File.

As the Response File is created, you are prompted for a reboot preference. This does not cause the machine to reboot during the generation of the Response File. At the end of the procedure, a response file is created. If any element of CCS has been previously installed, you cannot change the install locations. We recommend that you use the installation locations identified in this screen.

Important! Before you invoke silent installation from the command line, you must be aware of licensing information.

2. To begin the silent installation, at the command prompt, navigate to the directory containing the CA Common Services setup.exe files. Enter the following:

setup /S /f1”<ResponseFilePath>:\ccsSetup.iss"

Note: Enter the fully qualified path to access the response file. If you install from an installation media, you must begin the installation from the hard drive of your machine, and specify the fully qualified path to setup.exe. If the path to setup.exe contains spaces, you must enclose the path with double quotes. Also, there is no space between f1 and the path statement.

3. Check the Task Manager to verify that setup.exe is running.

Configuring Unicenter Enterprise Job Manager 53

Chapter 6: Configuring Unicenter Enterprise Job Manager

When the installation process is complete, you must prepare Unicenter Enterprise Job Manager for use. This chapter explains the steps necessary to configure Unicenter Enterprise Job Manager, including:

Adding portal users to workgroups

Creating CAICCI link definitions

Adding and configuring servers

Adding and configuring users and security

Configuring the environment

Deploying changes

This chapter also provides security information, describes how to change session timeout values, and describes the requirements for installing the SAP Java Connector.

Configuration Tasks Configuration tasks for Enterprise Job Manager include the following:

Setting the CPS_MULTI_SERVER environment variable

Adding Portal Users

Adding CAICCI Link Definitions

Adding and Configuring Servers

Adding HostAccess Link Definitions

Create Unicenter Enterprise Job Manager Users

Create Credentialed Groups

Create Credentialed Users

Deploying changes

Configuration Tasks


Setting the CPS_MULTI_SERVER Environment Variable

During installation, Unicenter Enterprise Job Manager creates the CPS_MULTI_SERVER Windows environment variable. Set this Windows variable for your system as follows:

If your enterprise contains more than one z/OS machine and each machine has CA-CPS installed and running, set the CPS_MULTI_SERVER variable to 1. All Unicenter Enterprise Job Manager calls to z/OS are routed directly to the target machine, so a CAICCI REMOTE connection must be set up on the Unicenter Enterprise Job Manager server for each machine.

If your enterprise contains multiple z/OS machines that are connected through CAICCI but are accessible only through one CA-CPS, set the CPS_MULTI_SERVER environment variable to 0. All Unicenter Enterprise Job Manager calls to z/OS are routed through the CA-CPS machine, so a single CAICCI REMOTE connection must be set up on the Unicenter Enterprise Job Manager server for the CA-CPS machine.

Setting Up Portal

UEJM is a portal-based application that leverages the features and functions of CleverPath Portal. To maximize the effectiveness of UEJM in your enterprise, you will need to become familiar with some of the basic features of CleverPath Portal, as described below.

Note: we strongly recommend that you modify the default Portal admin password, to enhance security. When you modify the Portal admin password, you must also update the value of this parameter in UEJM Configuration, on the Environment tab and the Monitoring Server subtab.

Portal Workplaces

Workplaces help you organize the objects and workplace elements to which you have access. Unicenter Enterprise Job Manager provides a default workplace for each sample Portal user, or you can create your own. You can customize the content and layout of your workplace, and you can define multiple workplaces to further organize information. For information about setting up workplaces, see the documentation for your portal. After you define and customize your workplace, you can assign users to the default workgroups.

Configuration Tasks


Portal Workgroups

Workgroups are groupings of users who require access to the same information. For example, the Portal Administrator can set up different workgroups for site members and guests, for various departments within your organization, or for age groups within your user base. The Unicenter Enterprise Job Manager installation creates eight portal workgroups and assigns a launch portlet to each workgroup. Assigning a user to a workgroup gives that user access to the associated portlet and its functionality. Users can be assigned to multiple workgroups, giving them access to multiple launch portlets.

The workgroups created are as follows:

EJM_JobFlow_Overview

This workgroup gives users a general overview of job status throughout the system through the assigned portlet, Job Flow Overviews.

EJM_JobFlow_Run

This workgroup allows users to monitor jobs at a detailed level. The portlet assigned to this workgroup is Job Flow Monitoring.

EJM_JobEditor

This workgroup allows users to create and manage jobs and related objects (calendars, schedules, global variables, datasets, ARFSETS, and so on). The portlet assigned to this workgroup is Job Editor.

EJM_JobFlow_Design

This workgroup provides access to create, modify, and delete job flows through the assigned portlet, Job Flow Design.

EJM_Configuration

This workgroup allows users to configure Unicenter Enterprise Job Manager system objects such as CAICCI Links, servers, users, credentialed users, and servlet parameters. The launch portlet assigned to this workgroup is Configuration.

EJM_Event

This workgroup allows users to access and use the Event Console to monitor events in the enterprise, through the assigned launch portlet, Event Console.

Configuration Tasks


EJM_HostAccess

This workgroup allows users to access and use the 3270 host access facility through the assigned portlet, Host Access.

EJM_JobStatusConsole

This workgroup allows users to monitor jobs and alerts through the Job Status Console. The portlet assigned to this workgroup is Job Status Console.

Configuration Tasks


Portal Users

The Portal Administrator can create users and assign them to one or more workgroups, to provide access rights appropriate for the user’s responsibilities. This provides maximum flexibility in administering Unicenter Enterprise Job Manager.

You must add portal users for each user or user group and assign the user to an appropriate workgroup. To do so, follow these steps:

1. Log in to the portal as the Admin user.

2. Create new portal users. To assist you, sample users are installed with Unicenter Enterprise Job Manager, as described in Portal Users in this chapter.

3. Assign each user to one or more workgroups.

The portal user ID is the key for user authentication. To significantly reduce administrative effort, choose this ID carefully and consider the following:

If a user accesses one back-end server or system only, we recommend that you use the same user ID for the portal and the back-end server. The portal user ID and password are used as credentials to access the back-end server.

If your enterprise uses a common user ID and different passwords for multiple systems, we recommend that you use this user ID for the portal. You can create a credentialed user for each back-end server or system and use the Server Password feature. For more information about credentialed users, see the Configuration Help.

New portal user IDs should meet the most restrictive naming conventions applicable to back-end servers or systems. You can create a credentialed user for each back-end server the user can access, using the Alias ID and Password feature.

Adding Portal Users

There are several ways to add users. You can create users from scratch, copy them from existing users, or import them from another source. Alternately, by enabling self registration, you can let users create their own accounts, which you then only need to review and activate.

For information about adding users, see the following topics:

Enable New User Self Registration

Add New Users Individually

Duplicate Existing Users

Import Multiple Users

Configuration Tasks


Enable New User Self Registration

If your portal is likely to attract a large number of new users, it may become too time-consuming for you, as portal administrator, to register each user individually. You can set the portal server up so that it lets new users register themselves. This involves completing several forms, including the Manage Users, Manage Users - Editing, and User Self Registration Properties forms.

After you enable user self registration, new users can gain access to appropriate areas of the portal as soon as they provide a unique user name and password on the Register form in the portal client. For more information about this form, see the CleverPath Portal User Help.

To enable user self registration, follow these steps:

1. Create a new user account to use for a standard or guest user. For example, you might create a user called Guest with password guest. New unregistered users initially log in to the portal using the Guest user account. For information about creating a new user account, see Add a Single User.

2. Log out as the Admin user and log in to CleverPath Portal as the guest user.

3. Configure the guest user's workplace.

Note: For information about configuring workplaces, see the CleverPath Portal User Help.

4. Log out of the guest user's account and log back in as the Admin user.

5. From the User Administration menu in Portal Administration, click Manage Users. The Manage Users form opens.

6. Click Search to list the users currently defined on the portal server.

7. Choose the new Guest user from the list box, then click Edit. The Manage Users - Editing form opens.

8. In the Create/Edit/Delete Permissions section of the Manage Users - Editing form, click the Yes radio button for Guest Mode.

9. Click Save to save changes to the guest user's profile and close the Manage Users - Editing form.

10. From the Properties menu in Portal Administration, choose Registration. The User Self Registration Properties form opens.

11. Complete the fields in the User Self Registration Properties form as appropriate. The Allow User Self Registration check box must be selected.

12. Click Save to save changes and close the User Self Registration Properties form.

Configuration Tasks


Users may now register themselves with the portal server according to the properties you specified for self-registration. To do so, they must log in to the guest user account, click Register in the top right corner, and then complete and submit the Register form.

Configuration Tasks


Add Individual New Users

Creating user accounts from scratch is accomplished using the Manage Users - Adding form. To add a new user account to the portal server, follow these steps:

1. From the User Administration menu in Portal Administration, click Manage Users. The Manage Users form opens, listing the users currently defined on the portal server.

2. Click Add to add a new user. The Manage Users - Adding form opens.

3. Complete the fields on the Manage Users - Adding form as appropriate.

4. Click Save to add the new user. The Manage Users - Adding form closes and the list box on the Manage Users form updates to include the new user.

5. Repeat Steps 2 through 4 to add another user, or choose a user from the list box and click Edit to edit that user's information.

Manage Users - Adding

The Manage Users - Adding form opens in the right Portal Administration pane when you click Add on the Manage Users form. Use the Manage Users - Adding form to add a single user to the portal server.

Fields

The Manage Users - Adding form contains the following fields:

ObjectKey - Specifies the object key that the portal server assigns to the user's account when it is created. Until you click Save on the Manage Users - Adding form, this number is -1.

Username - Identifies the user ID for the new user. This name classifies the user throughout CleverPath Portal. The user enters the value assigned here during login.

Password - Identifies the password to associate with the Username value. This password must contain at least two alphanumeric characters. A character mask is applied so that this password cannot be viewed even as it is entered.

Password Again - Confirms the password. This must match the Password value exactly.

Note: You have the option of storing the Username and Password on the user’s computer as an encrypted cookie. CleverPath Portal then looks for this cookie as a form of authentication and, if that cookie is present and contains a valid user name/password combination, it bypasses the Log In screen for the user. To implement the cookie, set the remember.me.cookie and remember.me.cookie.duration options in the local.properties file.

Configuration Tasks


First Name - Indicates the user's first name.

Last Name - Indicates the user's last name.

Email - Specifies the user's email address.

Note: If you have enabled wireless services, this field is required for a user to send an SMS message via a wireless device.

Address (line 1) - Specifies the first line of the user's residential address.

Address (line 2) - Specifies the second line of the user's residential address, if applicable.

City - Specifies the city in which the user resides.

State - Specifies the state or province in which the user resides.

Zip - Specifies the zip code in which the user resides.

Country - Specifies the country in which the user resides.

Company - Specifies the company for which the user works.

Title - Specifies the user's job title at the company.

Department - Specifies the department in which the user works.

Business Phone - Specifies the user's business telephone number, including country code, area code, and extension, if applicable.

FAX - Specifies the user's facsimile machine telephone number, including country code, area code, and extension, if applicable.

Home Phone - Specifies the user's home telephone number, including country code, area code, and extension, if applicable.

Cell Phone - Specifies the user's cellular telephone number, including country code, area code, and extension, if applicable.

Pager - Specifies the user's pager number, including country code, area code, and extension, if applicable.

Knowledge - Determines the user's permissions to create, edit, and delete objects in the library and channels for which the user has at least view access. Click the Granted radio button to give the user permission to create, edit, and delete objects. Click the Denied radio button to deny the user permission to create, edit, or delete objects.

Configuration Tasks


Guest Mode - Determines whether the portal server should manage the user's account as a guest account. In guest mode, changes the user makes on the portal server during a session are not saved when the user logs off. Click the Yes radio button to set the user's account to guest mode. Click the No radio button to turn guest mode off for the user.

Note: If user self registration is to be permitted, this field and the Allow User Self Registration field on the User Self Registration Properties form must both be set to Yes.

Description - Describes the user account briefly. You may want to include information about the purpose of the group, membership criteria, and so on.

Template - Determines whether the workgroup template is applied or the user is able to select a template to apply. Choose Personal from the drop-down list if the template used to display the user's portal client should be based on a personal selection. If so, the template specified in the subsequent Template field is used until the user changes it to the template of choice. Choose a workgroup from the drop-down list if the template for the user should be set based on the setting for the workgroup. If so, the template used is the one specified on the Manage Workgroups - Adding form or the Manage Workgroups - Editing form for the selected workgroup.

Default Group - Defines the user's default workgroup. Workgroup membership determines a user's access to channels and channel content, library folders and content, templates, default workplaces, and so on. For more information about workgroups, see Administer Workgroups.

Note: This drop-down list has None as its only option until you move one or more workgroups into the subsequent Member of list box, at which time those workgroups become available for selection here.

Account Status - Indicates the status of this user account. Click the Enabled radio button to make it active. Click the Disabled radio button to make it inactive.

Note: This applies only to non-administrative users. An administrative account cannot be disabled.

Template - Specifies the default template with which to display the user's portal client if you chose Personal from the Template drop-down list in the Create/Edit/Delete Permissions area.

Configuration Tasks


Available - Lists all workgroups currently defined on the portal server. To assign a workgroup to the user, click to select it in the

Available list box and then click . The selected workgroup moves to the Member of list box and is associated with the user. Repeat this procedure for each workgroup to which you want to add the user.

Member of - Lists all workgroups to which the user currently belongs. At first, this is blank for a new user. If you accidentally add the wrong workgroup for the user, click to select it in the

Member of list box and then click . The selected workgroup moves to the Available list box and the user is removed from that workgroup.

Role in Group - Lets you assign additional rights to the user, beyond those granted by the workgroup assignment. This specifies the user's administrative role, if any, in each workgroup selected in the Member of list box. To assign a user sub-administrator privileges in a specific workgroup, click to select the workgroup in the Member of list box for which you want to assign privileges and then choose the appropriate role from the Role In Group drop-down list. Repeat this procedure for each workgroup in which you want to define the user's role. The drop-down list displays the following roles:

– None - Users with this role have no administrative privileges in the associated workgroup or its subgroups.

– Group Admin - Users with this role have access to the Manage Workgroups form of Portal Administration. They are able to add, delete, and modify subgroups of the associated workgroup (and its subgroups) only.

– User Admin - Users with this role have access to the Manage Users form of Portal Administration. They are able to add, delete, and modify users in the associated workgroup (and its subgroups) only. Users with this role can also assign users to the associated workgroup.

– Group/User Admin - Users with this role have both Group Admin and User Admin sub-administration privileges described.

Command Buttons

The Manage Users - Adding form contains the following command buttons:

Save - Saves the user's profile and adds the user to the portal server's database.

Cancel - Closes the Manage Users - Adding form without adding a new user.

Configuration Tasks


Duplicate Existing Users

Copying a user from an existing user to reduce data entry (copying basic user profile data and then adding user-specific information) is accomplished using the Manage Users - Duplicating form. To base a new user's account profile on that of an existing user, follow these steps:

1. From the User Administration menu in Portal Administration, click Manage Users. The Manage Users form opens, listing the users currently defined on the portal server.

2. In the list box of existing users, choose the base user whose profile you want to use for the new user.

3. Click Duplicate User. The Manage Users - Duplicating form opens.

4. Complete the fields on the Manage Users - Duplicating form as appropriate.

5. Click Save to add the new user. The Manage Users - Duplicating form closes and the list box in the Manage Users form updates to include the new user. The portal server creates the new user's account with the same settings that exist in the base user's profile. If you selected the Yes radio button for Copy Workplaces, the base user's workplaces are copied to the new user's workplaces.

Configuration Tasks


Import Multiple Users

When user and authentication information for multiple users already exists on another server or database, you can save time by uploading it all at once to the portal server.

Note: When importing user and workgroup information, you must explicitly set the default workgroup.

For information about how to configure the portal server to upload user and authentication information for multiple users, see the following topics:

Import User Information from CSV Files

Import User Information from LDAP Servers

Import User Information from NIS Servers

Import User Information from CSV Files

You can use the CSV Properties form to configure the portal server to import user and authentication information from a Comma Separated Variables (CSV) file located on the machine on which the portal server is running. A CSV file is used as a portable representation of a database. Each line represents one entry or record, and the fields in a record are separated by commas.

Note: Workgroup information can also be imported here from a CSV file. In Step 3, you have the ability to enter a CSV Group Filename and its corresponding CSV Group Fields.

To upload user and authentication information from a CSV file, follow these steps:

1. Verify that the CSV files that contain the user (and workgroup) information you want to import exist on the machine on which the portal server is running.

2. From the Properties menu in Portal Administration, click CSV. The CSV Properties form opens.

3. Complete the fields as appropriate.

4. Click Import. The fields are imported to the portal server from the CSV file(s).

5. Click Update Changes. The information entered on the CSV Properties form is saved. The new users are listed on the Manage Users form in Portal Administration.

Configuration Tasks


Import User Information from LDAP Servers

You can use the LDAP Properties form to configure the portal server to import user and authentication information from a Lightweight Directory Access Protocol (LDAP) server. To do so, you must have administrator rights to the portal server. To upload user and authentication information from an LDAP server, follow these steps:

1. Verify that the applicable LDAP servers are running and that the user information you want to import exists.

2. From the Properties menu in Portal Administration, click LDAP. The LDAP Properties form opens.

3. Update the Schedule Interval to how often, in minutes, you want the LDAP servers to update the information, or set it to "-1" to run immediately only once. Click the Import check box for each LDAP server from which you want to import user and authentication information, and make any changes necessary to the server definitions. If the LDAP server from which you want to import has not been defined, complete the fields in the Add New Server section of the LDAP Properties form as appropriate, and then click Add New Server. The LDAP Properties form refreshes, and you can now import from the newly defined server. Click Update Changes. The portal server saves the server definition information.

4. From the Microsoft Windows, UNIX, or Linux command line, use the cd command to change to the directory where the portal server is installed.

5. On Windows systems, type import ldap to run the Importer tool. On UNIX or Linux systems, type import.sh ldap to run the Importer tool. The Importer tool is a command-line program provided with the portal server that lets you import user and authentication information from LDAP servers, NIS servers or CSV files.

6. Press Enter. The portal server uploads the user information from the LDAP servers you selected in Step 3. The new users are listed in the Manage Users form in Portal Administration.

When configured in a non-clustered environment, CleverPath Portal has the ability to authenticate LDAP users not yet imported into the portal. Once authenticated, the new user will be added to CleverPath Portal as if the user was imported through a scheduled LDAP import. This reduces the need to schedule frequent LDAP imports to keep CleverPath Portal and the LDAP server in sync.

In order to use this feature, set the following:

In Local.properties

synchronize.key.retrieval=true

In ldap.properties

auto.add.user=1

Configuration Tasks


Import User Information from NIS Servers

Use the NIS Properties form to configure the portal server to import user and authentication information from a Network Information Systems (NIS) server. You must have administrator rights to the portal server. To upload user and authentication information from an NIS server, follow these steps:

1. Verify that the applicable NIS servers are running and that the user information you want to import exists.

2. From the Properties menu in Portal Administration, click NIS. The NIS Properties form opens.

3. Update the Schedule Interval to how often, in minutes, you want the NIS servers to update the information, or set it to "-1" to run immediately only once. Click the Import check box for each NIS server from which you want to import user and authentication information, and make any changes necessary to the server definition. If the NIS server from which you want to import has not been defined, complete the fields in the Add New Server section of the NIS Properties form as appropriate, and then click Add New Server. The NIS Properties form refreshes, and you can import from the newly defined server. Click Update Changes. The portal server saves the server definition information.

4. From the Microsoft Windows, UNIX, or Linux command line, use the cd command to change to the directory where the portal server is installed.

5. On Windows systems, type import nis to run the Importer tool. On UNIX or Linux systems, type import.sh nis to run the Importer tool. The Importer tool is a command-line program provided with the portal server that lets you import user and authentication information from LDAP servers, NIS servers or CSV files.

6. Press Enter. The portal server uploads the user information from the NIS servers you selected in Step 3. The new users are listed in the Manage Users form in Portal Administration.

Configuration Tasks


Sample Portal Users

The following sample portal users (two for each level of access) are created during installation:

EJMADMIN

Provides system configuration access for Unicenter Enterprise Job Manager. Typically, these users are System Administrators or Security Administrators.

EJMADMIN (password: ejmadmin)

ejmadmin (password: ejmadmin)

The workgroup for this user is:

EJM_Configuration

EJMEXEC

Provides access to summary information on job status for Unicenter Enterprise Job Manager. Typically, these users are executives and managers from other disciplines.

EJMEXEC (password: ejmexec)

ejmexec (password: ejmexec)

The workgroups for these users are:



EJMOPERATOR

Provides a basic level of access for Unicenter Enterprise Job Manager. These users are, typically, Scheduling Monitors:

EJMOPERATOR (password: ejmoperator)

ejmoperator (password: ejmoperator)


EJM_Event

EJM_JobFlow_Run



Configuration Tasks


EJMSCHEDULER:

Provides a level of access that includes the ability to create and modify jobs and job objects. These users are, typically, both Scheduling Monitors and Job/Jobset Administrators:

EJMSCHEDULER(password: ejmscheduler)

ejmscheduler (password: ejmscheduler)


EJM_Event

EJM_HostAccess

EJM_JobFlow_Run


EJM_JobEditor


EJMSUPERVISOR

Provides a higher level of access. These users are, typically, both scheduling and/or monitoring supervisors:

EJMSUPERVISOR (password: ejmsupervisor)

ejmsupervisor (password: ejmsupervisor)


EJM_Event

EJM_HostAccess

EJM_JobFlow_Design

EJM_JobFlow_Run


EJM_JobEditor


Configuration Tasks


EJMCOMMANDER

The highest level of access. These users have access to all in Unicenter Enterprise Job Manager features. This user is, typically, a System Administrator, Scheduling Monitor or Job/Jobset Adminstrator:

EJMCOMMANDER (password: ejmcommander)

ejmcommander (password: ejmcommander)


EJM_JobFlow_Run


EJM_JobEditor

EJM_JobFlow_Design

EJM_Configuration

EJM_HostAccess

EJM_Event


Each of these users has a default workplace that opens to display the available launch portlets. No workplace definition is required. Users have access to appropriate portal content from their default workplaces.

These users are set up in the CleverPath Portal instance and the Unicenter Enterprise Job Manager Configuration files.

Configuration Tasks


Configuration Manager

Configuration Manager provides an interface for configuring the Unicenter Enterprise Job Manager job management CAICCI nodes, servers, Host Access links, users, credentialed groups, and credentialed users.

The Configuration Manager contains the following tabs, arranged in logical order:

Setup

Security

Environment

Deploy

Setup Tab

The Setup tab displays by default when you start the Configuration Manager. The Setup tab contains the following options:

CCI Links

Opens the Setup: CCI Links page so you can add, edit, and delete CAICCI nodes for Unicenter Enterprise Job Manager. This is the default page on the Setup tab.

CCI Links Status

Opens the Setup: CCI Links Status page so you view the status of the CCI Links currently deployed in Unicenter Enterprise Job Manager.

Servers

Opens the Setup: Servers page so you can add, edit, and delete servers for Unicenter Enterprise Job Manager.

Servers Status

Opens the Setup: Servers Status page so you verify the status of all servers currently deployed in Unicenter Enterprise Job Manager.

Host Access

Opens the Setup: Host Access Links page so you can add, edit, and delete host access links for Unicenter Enterprise Job Manager.

Configuration Tasks


CAICCI Link Definitions

The first task is to create CCI Links. In the CCI Links subtab, you will perform the following tasks:

Create a CAICCI link definition for each system that you want Unicenter Enterprise Job Manager to access.

Assign appropriate parameter values for the properties of the server or system. For help determining appropriate parameter values, see the Configuration Help.

Verifying CAICCI Link Status

From this page, you can view the status of all CCI Links currently deployed in Unicenter Enterprise Job Manager.

Note: For a link to appear with correct status information, you must deploy the CCI Link definition and then restart the CA-Unicenter (Remote) service.

Adding and Configuring Servers

The second task is to define Unicenter Enterprise Job Manager servers. On the Servers subtab you will perform the following tasks:

Create a Unicenter Enterprise Job Manager server definition for each back-end server or system your enterprise accesses with Unicenter Enterprise Job Manager. The server names you use (display names) must be unique.

Configure each server, assigning parameter values for the properties of the server or system. For help determining parameter values, see the Configuration Manager Help.

Note: Unicenter AutoSys Job Management servers, Unicenter CA-7 Job Management systems, Event Console servers, and SAP servers use different parameters.

Verifying Server Status

From this page, you can verify the status of a deployed Unicenter Enterprise Job Manager Server. To verify a server status:

Select the radio button to the left of the server name and click Verify

The Server Status Verify page opens

Enter appropriate credentials for the server and click Verify.

Configuration Tasks


Adding Host Access Link Definitions

The third task is to create Host Access Links. In the Host Access Link subtab, you will perform the following tasks:

Create a Host Access link definition for each 3270 system to be accessed with Unicenter Enterprise Job Manager.

Assign appropriate parameter values for the properties of the 3270 host. For help determining appropriate parameter values, see the Configuration Help.

Security Tab

The Security tab contains the following options:

Credential Users

Opens the Security: Credential Users page so you can add, edit, and delete credential users for Unicenter Enterprise Job Manager. This is the default page on the Security tab.

Credential Groups

Opens the Security: Credential Groups page so you can add, edit, and delete credential groups for Unicenter Enterprise Job Manager.

Users

Opens the Security: User Configuration page so you can add, edit, and delete users for Unicenter Enterprise Job Manager.

Adding and Configuring Unicenter Enterprise Job Manager Users

The next task is to create Unicenter Enterprise Job Manager users. From the Users subtab, you will perform the following tasks:

Create a user for each portal user with access to Unicenter Enterprise Job Manager. The user must have the same ID as the corresponding portal user.

Identify a list of Unicenter Enterprise Job Manager servers or systems each user can view.

Assign a Terminology Preference, a Monitoring Refresh Interval, a Job Flow Summary Refresh Interval, and an Administration Objects Display Number for each user.

Configuration Tasks


Adding Credentialed Groups

The next task is to create Credentialed Groups. Credentialed groups map one user ID on the back-end server to a group of Credentialed Users to:

Simplify access to back-end servers or systems

Allow you to change group information once and make changes immediately available to all users in the group

Provide an additional level of security

From the Credential Groups subtab, you will perform the following tasks:

Create a credentialed group for each group user ID on the job management server

Configure each credentialed group, assigning parameter values for the properties of the group ID. For help determining parameter values, see the Configuration Manager Help.

Assigning Credentialed Users to Each Server

The next task is to create Credentialed Users. The Credentialed User Configuration feature lets you add and delete credentialed users, and edit information about these users. When adding credentialed users, consider the following:

A Credentialed User ID must be the same as the user's portal user ID.

If a credentialed user has the same user ID for the back-end server or system as for the portal, but the back-end server or system has a different password, assign a Server Password.

If the credentialed user has a different user ID for the back-end server or system, assign an Alias ID and Alias Password. You can use the Alias ID and password for group IDs as well as individual IDs.

If the credentialed user is to be a part of a Credentialed Group, set the Group User Active property to Yes and enter a Group User ID for the Credentialed Group.

From the Credential Users subtab, you will perform the following tasks:

Create a credentialed user for each user ID on the job management server.

Configure each credentialed user, assigning parameter values for the properties of the group ID. For help determining parameter values, see the Configuration Manager Help.

Configuration Tasks


Environment Tab

The Environment tab contains the following options:

Job Scheduling Server

Opens the Environment: Job Scheduling Server page so you can view and edit properties for the job scheduling server. This is the default page on the Environment tab.

Monitoring Server

Opens the Environment: Monitoring Server page so you can view and edit the job management information you want the server to monitor during a session and the intervals at which that information is updated.

Job Status Console Server

Opens the Environment: Job Status Console Server page, so you can view and edit properties for the Job Status Console.

All of the server properties are set to intelligent defaults. You can modify these as required to meet the needs of your enterprise.

Deploy Tab

The Deploy tab contains the following options:

Deploy

Opens the Deploy: Deploy Changes page so you can add comments before deploying configuration changes and view comments made for the previous deployment. You can also deploy configuration changes from this page. This is the default page on the Deploy tab.

Services

Opens the Deploy: Services page so you can start, stop, restart, and refresh Unicenter Enterprise Job Manager services.

Deploying Configuration Changes

Use the Deploy feature, from the Configuration main window, to finalize your configuration changes and make them available to servers. You must deploy configuration changes for these changes to become effective.

Stopping and Restarting Services


Stopping and Restarting Services From the Services subtab, you can stop and restart the following services associated with the Job Scheduling, Job Flow Monitoring, and Configuration functions:

CA-Unicenter (Remote)

CA-Unicenter (NR-Server)

CA-Unicenter (Transport)

CA-Unicenter Enterprise Job Manager Scheduling Server

CA-Unicenter Enterprise Job Manager Monitoring Server

CA-Unicenter Enterprise Job Manager Job Status Console Server

CA-Unicenter Enterprise Job Manager Job Status Console Servant

CA-Unicenter Enterprise Job Manager Event Server

CA-Unicenter Enterprise Job Manager Host Access Server

CA-Unicenter Enterprise Job Manager UI Framework Server

The Services Configuration dialog also provides information about the following services, although you cannot stop or start these services from Services Configuration:

Portal

CA-Unicenter Enterprise Job Manager Configuration Server

If CA Common Services (CCS) is installed on the same server as Unicenter Enterprise Job Manager, the following services can also be administered from this page:

CA-Unicenter

CA-Unicenter NSM Auxiliary Services

Note: CA-Unicenter and CA-Unicenter NSM Auxiliary Services may not be available on all Unicenter Enterprise Job Manager servers. These optional installations may be installed elsewhere in the enterprise.

Important! If you are running Unicenter Enterprise Job Manager from the machine on which it is installed, you can also use the Windows Services dialog to stop and restart your services. The Portal and Configuration services must be stopped and restarted using the Windows Services dialog. To stop, start, and restart either the Configuration service or the Portal service, you must use the Windows Services dialog on the machine on which Unicenter Enterprise Job Manager is installed.

Stopping and Restarting Services


Restarting User Sessions

When a Unicenter Enterprise Job Manager service stops and restarts while users are logged in, the user sessions are broken. To continue to use Unicenter Enterprise Job Manager, you must restart your user session. The following procedures allow you to restart user sessions:

To restart Job Scheduling, close the Job Scheduling window and relaunch Job Scheduling from its launch portlet.

To restart Configuration, close the Configuration window and relaunch Configuration from its launch portlet.

To restart the Event Console, close the Event Console window and relaunch the Event Console from its launch portlet.

To restart Host Access, close the Host Access window and relaunch Host Access from its launch portlet.

To restart Job Flow Monitoring (Job Flow Monitoring, Job Flow Design, or Job Flow Overviews), close the Job Flow Monitoring window, log off the portal, log in again, and restart the Job Flow Monitoring interface from the appropriate launch portlet.

Logging In to the Portal


Logging In to the Portal After the Unicenter Enterprise Job Manager services are restarted, you are ready to start a Unicenter Enterprise Job Manager session Open a browser window, and navigate to the URL for Unicenter Enterprise Job Manager. Typically, this is http://machinename:8080, where machinename is the host name for the UEJM server. The login page opens. Enter appropriate credentials and click Log In. The default workplace for your user ID will open, displaying the features and functions of UEJM that your user ID has authorization to access.

Session Security Security for job sessions uses not only the session timeout of the server but also the session timeout of the CleverPath Portal server. When you log in to the portal and access any file (for example, Job Flow Design or Job Flow Overviews), the client browser session is registered with the server. If the browser remains idle for longer than the server session timeout time (the default session time-out is 30 minutes), the server considers the session to have timed-out and prevents any further user activity. This maintains security and privacy if your browser is inadvertently left open, and it can prevent unauthorized accesses. Sessions can also expire if the server stops and restarts while a user is logged on to the system. This also prevents users from accessing Unicenter Enterprise Job Manager pages directly without logging in to the portal first.

Modifying Session Timeout Values If a session timeout value is exceeded when you are using the Unicenter Enterprise Job Manager, you cannot reconnect to the interfaces. This normal behavior provides an additional layer of security for the underlying web containers. Typically, when a session timeout is exceeded, both the portal session and the interface session time out.

A timeout is indicated by an Authorization Failure message in the interface window. If this condition occurs, simply close the browser window, re-open the browser to the portal URL, and log in to the portal. If you are experiencing a significant number of session timeouts, you may want to modify the session timeout values to accommodate expected usage.

The following sections provide information about session timeout values.

Modifying Session Timeout Values


CleverPath Portal Timeouts

CleverPath Portal is installed to an Apache™ Tomcat server. The default timeout for Apache Tomcat servers is 30 minutes. To modify this value, follow these steps:

1. Log in as admin.

2. From the graphical menu bar, select My Profile.

3. From the Profile page, select Portal Administration. The Portal Administration page opens.

4. From the Properties section of the left pane menu, select Global. The Global properties dialog opens.

5. Change the User Timeout (minutes) value to the desired value and click Update Changes.

Scheduling and Monitoring Timeouts

Session timeouts for Job Scheduling and Job Flow Monitoring are determined by the Session Idle Timeout parameter. This value is the time in seconds that a user session can remain idle before timing out and releasing the session. You can modify the Session Idle Timeout parameter for the respective interface in the Job Scheduling Server and Monitoring Server subtabs of the Environment tab. For more information on modifying these parameters, see the Configuration Manager Help.

Timeouts for Other Servers

To modify the session timeout for other servers, you must modify the timeout value of the underlying Apache Tomcat server. To modify the session timeout for other servers, follow these steps: Open the file install root/ServerNameServer/conf/web.xml in an editable format (typically, either Microsoft Notepad or an HTML editor).

The following XML element contains the Session Timeout value, which is 30 minutes by default:

session-config <session-timeout>30</session-timeout> </session-config>

1. Change the value from 30 to the desired value (in minutes).

2. Save the web.xml file.

Restart the appropriate service (for example, CA-Unicenter Enterprise Job Manager Configuration Server).

SAP Java Connector


SAP Java Connector In order to access SAP support for AutoSys servers, the following must be available:

1. The AutoSys server must have the Unicenter Job Management Adapter for SAP installed and configured. For more information, see the Unicenter Job Management Adapter for SAP Administration Guide.

2. You must define the SAP server in the Unicenter Enterprise Job Manager Configuration Manager. For more information, see the Configuration Manager Help.

3. You must install the SAP Java Connector (JCo) on the Unicenter Enterprise Job Manager Server. You can obtain information regarding the SAP JCo and downloads of this product from the SAP web site. The SAP Java Connector is supplied as a .zip file. Unzip the contents, and complete the following steps:

a. Place librfc32.dll in the WINDOWS\System32 directory

b. Place sapjco.jar and sapjcorfc.dll in the <install root>\AdminServer\webapps\UEJMAdmin\WEB-INF\lib directory.

c. Restart the CA-Unicenter Enterprise Job Manager Scheduling Server service.

Configuring Event Management 81

Chapter 7: Configuring Event Management

This chapter describes how to set up Unicenter Event Management to forward messages to a consolidated event console. It explains the following:

How to configure a Consolidated Event Console to view job manager messages

How to set up the Event Console to acknowledge and close AutoSys alarms

Consolidated Event Console Unicenter Event Management is available through Unicenter Network and Systems Management (NSM) as well as Unicenter Common Services. Using either of these, you can set up Event Management to route job management messages to a consolidated event console. The remainder of this chapter describes how to route Unicenter AutoSys Job Management messages to a consolidated event manager. The consolidated event manager messages can be viewed through the Unicenter Enterprise Job Manager Event Console.

Routing of Unicenter CA-7 Job Management messages requires PTF QO55523 - MESSAGE ROUTING TO EVENT CONSOLE to be applied in your enterprise. Instructions for configuring CA-7 to route the messages to a specified event manager are included in the PTF.

You can also use Unicenter® CA-OPS/MVS® Event Management and Automation (Unicenter CA-OPS/MVS) to forward job manager messages to a consolidated event console. For more information on this option, contact CA Technical Support.

Creating a Consolidated Event Console to View Unicenter AutoSys Job Management Messages



To create a consolidated job management event console to view Unicenter AutoSys Job Management messages across your enterprise, use Unicenter Enterprise Manager to transport Unicenter AutoSys Job Management messages from each Unicenter AutoSys Job Management event processor machine to a Unicenter Event Console on a focal point Windows or UNIX system.

To configure Unicenter AutoSys Job Management to forward its messages through the Unicenter Event Console to the focal point system, follow these steps:

1. Send Unicenter AutoSys Job Management Messages to the Unicenter Event Console on the Unicenter AutoSys Job Management event processor machine.

2. Forward Unicenter AutoSys Job Management messages to the Unicenter Event Console on the focal point system.



Step 1: Send Unicenter AutoSys Job Management Messages to the Unicenter Event Console on the Unicenter AutoSys Job Management Event Processor Machine

The first step is to publish all messages to the Unicenter Event Console on the Unicenter AutoSys Job Management event processor machine. The procedure to do this varies depending on which platform the Unicenter AutoSys Job Management Event Processor machine is running. If the machine is running on a Windows platform, you must modify your administrator configuration as follows:

1. Start the Unicenter AutoSys Job Management Administrator GUI.

2. From the drop-down list, select the instance whose events you want to publish to the Unicenter Event Console, and click OK.

3. Select Event Processor from the Unicenter AutoSys Job Management drop-down list.

4. Enter 3 in the Unicenter Events edit field. This field is located in the lower-right corner of the event processor window.

5. Click Apply, and then click OK.

Note: To modify the settings on this screen, you must have privileges in the Windows Administrators group.

Important! The event processor reads the settings in the Unicenter AutoSys Job Management Administrator on startup only. Therefore, if you make a change that you want to implement immediately, you must stop the event processor using the sendevent -E STOP_DEMON command, and then restart the event processor using the Administrator Services screen (as described in the chapter “AutoSys Administrator” of the Unicenter AutoSys Job Management for Windows User Guide). Alternatively you can restart the CA Unicenter Autosys Event Processor Service.

If the Unicenter AutoSys Job Management event processor machine is running on a UNIX platform, to publish all messages to the Unicenter Event Console on this machine you must enable Unicenter event integration.

To do this, install the Unicenter Event Manager agent on the event processor machine.

Note: The Unicenter Event Manager agent can be installed alone, as part of Unicenter Framework, or as part of the entire Unicenter product.



The UnicenterEvents parameter is located in the file $AUTOUSER/config.$AUTOSERV. When the UnicenterEvents parameter is non-zero, EVENT_DEMON will start an additional demon, AUTO_WTO, to transfer messages between the event processor and Unicenter. The AUTO_WTO demon creates a FIFO (File In File Out,) /tmp/auto_wto_pipe, to communicate with the event processor.

By default, UnicenterEvents is off.

The example entry in the configuration file looks like:

UnicenterEvents = n,

where n is one of the following:

0—Report no events to Unicenter (default setting) 1—Log all Alarms. 2—Log only alarms and job completions. 3—Log all events that are generated to the Unicenter Event Console.

To log all events to the Unicenter Event Console, set UnicenterEvents to the following:

UnicenterEvents = 3



Step 2: Forward Unicenter AutoSys Job Management Messages to the Unicenter Event Console on the Focal Point System

Now that you have configured Unicenter AutoSys Job Management to publish all messages to the Unicenter Event Console on the Unicenter AutoSys Job Management Event Processor machine, you must forward these messages to the Unicenter Event Console on the focal point system as follows:

1. Start the Unicenter Event Manager.

2. Open the messages panel.

3. Add a new message record with a message ID of %CAATS*

4. Save the new message record.

5. Open the %CAATS* message record again. Click Action.

The new action is FORWARD, and the node name is the TCP/IP host name of the focal point system.

You can choose which Unicenter AutoSys Job Management messages are forwarded to the focal point system by using the Unicenter Event Console to further restrict those messages forwarded, based on the text at the beginning of the messages. Unicenter AutoSys Job Management messages begin with the string %CAATS and informational, warning, and error messages are differentiated by the next two characters that follow %CAATS. For example:

%CAATS_I—Informational message %CAATS_W—Warning message %CAATS_E—Error message

To forward only error messages, specify %CAATS_E in Step 3 above. To forward warning messages in addition to error messages, repeat Steps 2 through 6 to create a message record for %CAATS_W, in addition to the one for %CAATS_E.

You can also forward messages based on the entire Unicenter AutoSys Job Management message ID, which is of the format:

%CAATS_ x_ nnn

where x is I, W, or E, and nnn is the three-digit message number.

For information on how to take full advantage of the Unicenter Event Console to view these messages, see the Administrator Guide of either Unicenter Common Services or Unicenter Network and Systems Management.

Setting Up Alarm Management


Setting Up Alarm Management Unicenter Enterprise Job Manager Event Console supports acknowledging and closing AutoSys alarms. The following procedure allows you to set up Unicenter and Unicenter Enterprise Job Manager for Alarm Management.

Considerations:

The Unicenter Enterprise Job Manager server must have an Event Agent installed.

Note: If Unicenter Enterprise Job Manager is the focal machine or has Unicenter Enterprise Job Manager CCS installed, then an Event Agent is installed.

Unicenter Enterprise Job Manager Event Console has been set up to view the Central Event Console. The AutoSys Event EOID PTF must be applied to support alarm acknowledgement. For more information on this PTF, see the Unicenter Enterprise Job Manager Readme file.

Note: Unicenter Enterprise Job Manager Event Console can acknowledge only alarms generated after the PTF has been applied. If the message policy server is not the Unicenter Enterprise Job Manager, then the uejm.utl file should be copied to that machine.

To set up Unicenter and Unicenter Enterprise Job Manager for Alarm Management, follow these steps:

1. Define message policies for Alarm Management by executing the following command from the command window:

cd <install root>\EventServer\alarm cautil –f uejm.uti

Typically, the install root is c:\Program Files\CA\Unicenter Enterprise Job Manager.

2. Reload the new message policies by executing the following command:

Oprcmd opreload

Configuring Your Browser 87

Chapter 8: Configuring Your Browser

This chapter describes how to configure your web browser to run with Unicenter Enterprise Job Manager.

Unicenter Enterprise Job Manager supports the following web browsers and versions:

Microsoft Internet Explorer 6.0

Mozilla 1.6

For the latest information about supported browsers and versions, see the Readme file.

Mozilla 1.6 for Windows To ensure that your Mozilla 1.6 for Windows 2000 or Windows XP browser is correctly configured to run with Unicenter Enterprise Job Manager, follow these steps:

1. Download and install JRE 1.4.2 from the Java website. The JRE can be found at http://java.sun.com/products/archive/index.html (http://java.sun.com/products/archive/index.html).

2. After the JRE 1.4.2 is installed, from the Windows Start menu, choose Settings, Control Panel, Java Plug-in. If you have more than one Java Plug-in installed, click the About tab to verify the version.

3. Click the Browser tab and select the Mozilla checkbox.

4. Click Apply.

5. Close the Plug-in dialog.

6. Close and re-open the browser.

Your Mozilla browser is now ready to support Unicenter Enterprise Job Manager using the JRE 1.4.2 plugin.

http://java.sun.com/products/archive/index.html

Mozilla 1.6 for Linux


Mozilla 1.6 for Linux To ensure that your Mozilla 1.6 for Linux browser is correctly configured to run with Unicenter Enterprise Job Manager, follow these steps:

1. Install JRE 1.4.2 from the Java website. The JRE 1.4.2 is available for download as an RPM file.

2. After successful installation, change to the directory in which Mozilla was installed.

3. Go to the plugins directory and ensure that the JRE was installed correctly. If you installed the JRE using an RPM file, the path of the JRE is:

/usr/java/j2re_1.4.2/

or

/usr/java/j2re_1.4.2_04/

4. Create a symbolic link to the Java plug-in for Mozilla to use. In the Mozilla install directory/plugins directory, use the following command:

ln -s /usr/java/j2re1.4.2_04/plugin/i386/ns610/libjavaplugin_oji.so javaplugin.so

5. Start the Mozilla browser and start the portal.

6. Start the Job Scheduling and Job Flow Monitoring interfaces.

If you have previously installed a version of the JRE Plug-in, you must perform these additional steps:

1. Change to your home directory. Navigate to the .mozilla directory. In the pluginreg.dat file, an entry similar to

java(TM) Plug-in1.4.2_04 :$

is followed by

1:, 2:, 3:, etc.

Locate the last number and, using the next number in sequence, add an entry similar to the following:

Next number:application/x-java-applet;jpi-version=1.4.2:Java:$

For example, if the last number is 10, enter

11:application/x-java-applet;jpi-version=1.4.2:Java:$

2. Restart the Mozilla browser and start the portal.

3. Start the Job Scheduling and Job Flow Monitoring interfaces.

Increasing the Initial and Maximum Heap Size on the Client Machine

Configuring Your Browser 89

Increasing the Initial and Maximum Heap Size on the Client Machine

Graph views such as Flow View and Requirements View involve a large number of GUI objects. Therefore, you must increase the initial and maximum heap size for the memory in the Java Plug-in to support the large number of objects in graphs. To do so, follow these steps:

1. From the Start menu, select Settings.

2. Select Control Panel. In the Control Panel, double-click the Java Plug-in icon.

3. Click the Advanced tab of the Java Plug-in Control Panel.

4. In the Java Runtime Parameters field, enter:

-Xms256m -Xmx400m

5. Click Apply.

Implementing Secure Sockets Layer 91

Chapter 9: Implementing Secure Sockets Layer

Unicenter Enterprise Job Manager supports Secure Sockets Layer (SSL) installations or non-SSL installations.

This chapter describes how to implement SSL with Unicenter Enterprise Job Manager, including how to establishing a standard SSL certificate for Unicenter Enterprise Job Manager.

What Is SSL? SSL is an encryption technology that leverages public and private key infrastructures to provide secure communication between a browser and the web server. The communication is a two-way process between the server and browser, so both must support SSL. Handshaking is performed to establish a connection and the data is encrypted and decrypted on both the server and browser side.

To implement SSL successfully, both the browser and server sides must be configured correctly. The browser must have the proper certificate (proof of identity) and the server must have a certificate to give.

A self-signed SSL certificate is supplied by the Unicenter Enterprise Job Manager installation. This certificate is sufficient for installing and testing Unicenter Enterprise Job Manager. You should, however, replace this certificate with a standard certificate or, at minimum, a self-signed SSL certificate, tailored to the host installation.

Implementing SSL with Unicenter Enterprise Job Manager


Implementing SSL with Unicenter Enterprise Job Manager This section describes SSL implementation and provides procedures to integrate SSL with ApacheTomcat and embedded CleverPath Portal.

The procedures described here show you how to integrate SSL with the following:

Apache Tomcat and CleverPath Portal (see Tomcat Standalone SSL Configuration (on page 93))

Microsoft IIS, Apache Tomcat and CleverPath Portal (see Tomcat with IIS-SSL (on page 100))

Although the steps will vary depending on your environment, they should serve as a reference for most standard installations. Note that this section is not a comprehensive guide to SSL implementations.

Note: This document assumes that Unicenter Enterprise Job Manager was installed with the “Enable SSL” option selected. If it was not, then you must update your installation and choose that option.

Tomcat and Portal

The Portal is a servlet that runs under the Tomcat 3.3a engine. Therefore, most of the configuration to support SSL should be done on the server side.

SSL Architecture

All communications between the user and the Portal Server are encrypted. The following illustration shows the major components.



Tomcat Standalone SSL Configuration

This section describes how to configure Tomcat and the Portal to take advantage of SSL.

Definitions

The following terms are used in this section:

UEJM_ROOT

The installation path of Unicenter Enterprise Job Manager.

PORTAL_INSTALL

The path for the embedded CleverPath Portal. If no other portal installation is found, it is UEJM_ROOT/CleverPath Portal.

TOMCAT_HOME

The path for the Tomcat installation. This should be set to PORTAL_INSTALL/Jakarta-tomcat-3.3a.

Tomcat with SSL

To configure Tomcat to take advantage of SSL, you can use the Tomcat-SSL documentation at http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-ssl-howto.html (http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-ssl-howto.html). You need, however, to make some modifications specific for Portal.

If you are using CleverPath Portal’s JRE, [JRE_HOME] is [PORTAL_INSTALL] and you will need to place any required jar files in the directory [PORTAL_INSTALL]/jre/lib/ext.

For Tomcat purposes, [PORTAL_INSTALL]/jakarta-tomcat-3.3a/ is the same as [TOMCAT_HOME].

CleverPath Portal 3.51 and 4.0 use Tomcat 3.3a.

Important! Due to restrictions in Java, this procedure will only work if the name of the target Unicenter Enterprise Job Manager server does not begin with a numeric character. If the name of the target Unicenter Enterprise Job Manager server begins with a numeric character, please contact CA Technical Support.

http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-ssl-howto.html

http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-ssl-howto.html



JSSE and Tomcat Configuration

You can follow these steps to configure Tomcat to use SSL using the Sun SSL implementation, Java Secure Sockets Extension (JSSE). The steps are for reference only; you will need to adjust them according to your needs and specifications.

Note: Before using this procedure, shut down the Unicenter Enterprise Job Manager servers.

These steps are a summary of the steps outlined in the Tomcat-SSL documentation.

1. Download the Java Secure Socket Extensions (JSSE) package, version 1.03 from http://java.sun.com/products/jsse/index-103.html (http://java.sun.com/products/jsse/index-103.html)

2. Expand the zip file downloaded from Step 1.

3. Put all three JAR files (jcert.jar, jnet.jar, jsse.jar) into [UEJM_ROOT]/cleverpath portal/jre/lib/ext directory. This is used for the default install using the Portal JRE. If you are using a different JRE, you must place the JAR files in the library extension directory of your specified JRE.

4. Now, you must prepare keystore to contain the SSL certificate. For that you will need the keytool utility which is located in your JDK bin directory. Ensure that the JDK bin directory is in the system path.

5. Rename the default keystore file for each of the Unicenter Enterprise Job Manager services. The file (.keystore) is located in each of the following directories:

UEJM_ROOT\AdminServer\conf

UEJM_ROOT\OPSMVSServer\conf

UEJM_ROOT\MonitorServer\conf

UEJM_ROOT\ConfigServer\conf

UEJM_ROOT\EventServer\conf

UEJM_ROOT\JobStatusConsoleServer\conf

UEJM_ROOT\UIFrameworkServer\conf

where UEJM_ROOT is the absolute path to your Unicenter Enterprise Job Manager installation. Rename the file to backup.keystore.

http://java.sun.com/products/jsse/index-103.html



6. Open a command window and execute the following command to create a self-signed certificate:

keytool -genkey -alias tomcat -keyalg RSA –validity 14600 –keystore UEJM_ROOT\AdminServer\conf\.keystore

The command will create a .keystore file in the –keystore value. Ensure that the path uses appropriate escape characters if it contains long file names or blanks.

Note: This command creates a self-signed certificate only; that is, it is used for testing purposes only. For a production server, you need to obtain a certificate from a trusted Certificate Authority like Verisign

7. After executing the command, you will be prompted for the keystore password. The default password used by Tomcat is "changeit". You will need to reflect the password you chose in the server.xml configuration file. The “first and last name” requested should be the hostname for the machine running UEJM.

>keytool -genkey -alias tomcat -keyalg RSA … Enter keystore password: changeit What is your first and last name? [Unknown]: hostname What is the name of your organizational unit? [Unknown]: Chairman What is the name of your organization? [Unknown]: Computer Associates What is the name of your City or Locality? [Unknown]: Islandia What is the name of your State or Province? [Unknown]: NY What is the two-letter country code for this unit? [Unknown]: US Is <CN=www.ca.com, OU=Chairman, O=Computer Associates, L=Islandia, ST=NY, C=US> correct? [no]: yes

Finally, you will be asked for the key password. Use the same password that was used for the keystore, ‘changeit’.



8. Copy the .keystore file generated to the directories modified in step 5. The file (.keystore) is located in each of the following directories:

UEJM_ROOT\OPSMVSServer\conf

UEJM_ROOT\MonitorServer\conf

UEJM_ROOT\ConfigServer\conf

UEJM_ROOT\EventServer\conf

UEJM_ROOT\JobStatusConsoleServer\conf

UEJM_ROOT\UIFrameworkServer\conf

where UEJM_ROOT is the absolute path to your Unicenter Enterprise Job Manager installation. Rename the file to backup.keystore.

9. Export the certificate from the keystore using the following command:

UEJM_ROOT\Jre\bin\keytool -export -alias tomcat -file c:\tempcert.cer

–keystore “UEJM_ROOT\AdminServer\conf\.keystore”

where UEJM_ROOT is the absolute path to your Unicenter Enterprise Job Manager installation. This creates a tempcert.cer file containing the certificate for the alias.

10. Import this certificate into the Unicenter Enterprise Job Manager server trusted keystore (under UEJM_ROOT\Jre\lib\security folder) using the following command:

UEJM_ROOT\Jre\bin\keytool -import -trustcacerts -alias tomcat -file c:\tempcert.cer

-keystore UEJM_ROOT\Jre\lib\security\cacerts

You will be prompted “Trust this certificate[NO]”. Respond yes.

11. Re-boot your machine at this time.

12. Edit your PORTAL_INSTALL/Jre/ lib/security/java.security file. Add a security provider with the following line:

security.provider.x=com.sun.net.ssl.internal.ssl.Provider

Where x is the next number available.



13. Next, configure the Portal Tomcat server.xml file. This is located in [PORTAL_INSTALL]/ jakarta-tomcat-3.3a/conf directory.

Below is a modified version including the SSLImplementation, keystore location and keypass values. You must add the SSLImplementation line just as it appears below. If you have changed the port number, the default directory or password for your keystore then you should include those settings here. <Http10Connector port="8080" secure="true" SSLImplementation="org.apache.tomcat.util.net.JSSEImplementation" keystore="[UEJM_ROOT]/AdminServer/conf/.keystore" keypass="changeit" />

Important! Do NOT use SPACES on the lines that are added. It will cause an error parsing the file.

14. Update the UEJM_ROOT\AdminServer\webapps\UEJMAdmin\WEB-INF\classes\configfileman.properties file. The variable PORTAL_URL needs to be updated from http://nodename:8080 to https://nodename:8080.

Make the same changes in:

UEJM_ROOT\ConfigServer\webapps\ServletConfiguration\WEB-INF\classes

UEJM_ROOT\OPSMVSServer\webapps\OPSMVSServlet\webapps\WEB-INF\classes UEJM_ROOT\MonitorServer\webapps\UEJMMonitor\WEB-INF\classes

UEJM_ROOT\EventServer\webapps\UEJMEvent\WEB-INF\classes

UEJM_ROOT\JobStatusConsoleServer\webapps\JobConServlet\WEB-INF\classes

UEJM_ROOT\UIFrameworkServer\webapps\JobConServlet\WEB-INF\classes

15. This should be all that is necessary on the Tomcat side to implement SSL. The following sections describe additional configuration required for the Portal. For more information please refer to the links specified in Tomcat with SSL. For more information on keytool and on importing certificates from Certificate Authorities, please see http://java.sun.com/j2se/1.3/docs/tooldocs/win32/keytool.html.



Portal.bat/Portal Scripts

You will need to edit the <portal install directory>\conf\wrapper.properties and change the value for wrapper.cmd_line to include the System Property for the Java VM. This property specifies that the protocol is using Sun's SSL implementation (JSSE). The parameter is:

-Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol -Djavax.net.ssl.truststore=”[UEJM_ROOT]\AdminServer\conf\.keystore”

This is included in the wrapper.cmd_line as shown in the following example:

wrapper.cmd_line="$(wrapper.javabin)" -Xrs -ms64M -mx512M -Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol -Djavax.net.ssl.trustStore="<path to keystore directory>\.keystore" -Djava.security.policy=="$(wrapper.tomcat_policy)" -Dtomcat.home="$(wrapper.tomcat_home)" -Dportal.dir="C:/Portal/ssl/" -Dportal.startup.type=service -classpath "$(wrapper.class_path)" $(wrapper.startup_class) -config "$(wrapper.server_xml)"

Note: This command is one line.

Local Properties

The “local.properties” is located in the “properties” subdirectory of the portal installation directory. Edit the file and change the following parameters:

Change the host name parameter:

host.name=hostname

The hostname should be the actual hostname for the machine that UEJM is installed on. It should exactly match the host name that you used to create the certificate in Step 7 above.

Change the protocol scheme parameter:

host.protocol.scheme=https

The protocol scheme specification is one line. Ensure there are no spaces before and after the equal sign, and after https. If your secure connection is the only http connector you have enabled for the portal, then you may also want to alter the host.port= line to reflect the port your portal runs on. This line determines which port the portal uses for XML calls.



Accessing Portal

After you have correctly configured both the Portal and Tomcat sides, you are ready to access the Portal. If you use the default implementation according to instructions, then the HTTPS port will be 8443, but you can change it.

An example SSL URL is https://localhost:8443/servlet/portal (https://localhost:8443/servlet/portal)

The standard port used by browsers for HTTPS is 443.

When you access the portal for the first time, it asks you to install a digital certificate for the site. You must accept this certificate for HTTPS to function properly between client and server.

https://localhost:8443/servlet/portal



Tomcat with IIS-SSL

A popular alternative is to use Microsoft Internet Information Server (IIS) to create your secure socket layer. The choice to use IIS or Tomcat is generally one of preference and administration familiarity. Both solutions provide equivalent functionality.

Under this configuration, you must implement IIS with CleverPath Portal. You must configure IIS to accept your calls to the portal and then install your security credential as directed by the provider of your certificate. For details, see technical document #TEC264794, “Integrating CleverPath Portal/Tomcat 3.3x with IIS,“which is available at Computer Associates Technical Support web site.

Troubleshooting Tips

Requests with URLs containing encoded characters and a query string may lose the query string when the request is forwarded to Tomcat. A bug with the Jakarta isapi_redirect.dll causes this problem. According to the Jakarta site, this affects the isapi_redirect.dll versions prior to 3.3; however, in a specific situation we found that the latest version did not resolve the issue.

The following problem took place in a custom integration to an ASP application within a secure portal. Users who did not log off the portal, but only closed the browser then opened a new browser instance to log into the portal did not have their information correctly passed to the ASP application. When the isapi_redirect.dll was removed and the SSL implementation relied only on the instance of Tomcat to handle the secure connections, the problem was resolved.

Acknowledgements 101

Appendix A: Acknowledgements

This appendix contains copyright and license agreement information from third-party software used in Unicenter Enterprise Job Manager.

Acknowledgements


Acknowledgements Portions of this product include software developed by the Apache Software Foundation (http://www.apache.org/). The Apache software is distributed in accordance with the following license agreement.

Apache License Version 2.0, January 2004 http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, production, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, neither by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

Acknowledgements


"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner.

"Submitted," for the purposes of this definition, means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License.

Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License.

Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution.

Acknowledgements


You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License.

You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions.

Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks.

Acknowledgements


This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty.

Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability.

In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9 Accepting Warranty or Additional Liability.

While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

MIT License Copyright (c) 1999, 2003 TanukiSoftware.org

Acknowledgements


Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sub-license, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OROTHER DEALINGS IN THE SOFTWARE.

Copyright © Gero Vermaas, 1999 - All Rights Reserved E-Mail: [email protected] Web site: http://www.xs4all.nl/~gero.

The original version of this source code and documentation is copyrighted and owned by Gero Vermaas. This notice and attribution to Gero Vermaas may not be removed. Permission to use the software in a commercial or non-commercial product is hereby granted. Permission to distribute the source, the software generated by it and its documentation for REFERENCE PURPOSES is granted: a) to people and organizations that have bought the source code from Gero Vermaas b) provided that this copyright notice appears in all copies. It is not allowed for anyone to sell the source, software generated by it and the documentation as a separate product. This right is reserved to Gero Vermaas only. Gero Vermaas MAKES NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY OF THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. Gero Vermaas SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THIS SOFTWARE OR ITS DERIVATIVES.

Copyright © 1998 - 2002 Tom Sawyer Software All Rights Reserved. Copyright © VISUAL ENGINEERING, INC. All Rights Reserved.

This product includes code licensed from RSA Security, Inc. Some portions licensed from IBM are available at http://oss.software.ibm.com/icu4j/.

Acknowledgements


Copyright © 1999-2003 by Jacada Ltd. All rights reserved. This version of Jacada's JTE software is licensed by Jacada to users of Computer Associates Unicenter CA-OPS/MVS (OPS/MVS) Log Facility within Unicenter Enterprise Job Manager (Unicenter EJM) for use exclusively with such Computer Associates product and pursuant to the clickwrap license agreement which accompanies JTE.

Terms and Conditions for the Use of Java™ 2 Runtime Environment (J2RE), Standard Edition, Version 1.4.x

Licensee agrees that the following terms (in addition to the applicable provisions above) shall apply with respect to any open source provided by Sun Microsystems, Inc. contained within the Product. Notwithstanding anything contained in the CA End User License Agreement, solely with respect to such open source, these terms are not superseded by any written agreement between CA and Licensee:

Title to Java™ 2 Runtime Environment (J2RE), Standard Edition, Version 1.4.x (the “Software”) and all associated intellectual property rights is retained by Sun Microsystems, Inc. (“Sun”) and/or its licensors. Licensee acknowledges that the Software is not designed or intended for use in the design, construction, operation or maintenance of any nuclear facility. Sun disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to any trademark, service mark, logo or trade name of Sun or its licensors is granted under this agreement.

The Software is provided "AS IS". As to any claim made by Licensee against Sun respecting the Software, Licensee’s exclusive remedy and Sun's entire liability under this limited warranty will be at Sun's option to replace the Software media or refund the fee paid for the Software which Licensee acknowledges is $0. The foregoing shall not affect any warranties provided in any other applicable agreement between Licensee and CA.

UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE THE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. The foregoing limitations will apply even if the above stated warranty fails of its essential purpose.

Acknowledgements


Sun may terminate Licensee’s right to use the Software if Licensee fails to comply with any provision of this agreement. Upon such termination, Licensee must destroy all copies of the Software.

Notwithstanding anything to the contrary contained in any agreement between Licensee and CA, any action related to this agreement in which Sun is a party will be governed by California law and controlling U.S. federal law. No choice of law rules of any jurisdiction will apply.

Licensee acknowledges that the Software may automatically download, install, and execute applets, applications, software extensions, and updated versions of the Software from Sun ("Software Updates"), which may require Licensee to accept updated terms and conditions for installation. If additional terms and conditions are not presented on installation, the Software Updates will be considered part of the Software and subject to the terms and conditions of the agreement.

Licensee acknowledges that, by Licensee’s use of the Software and/or by requesting services that require use of the Software, the Software may automatically download, install, and execute software applications from sources other than Sun ("Other Software"). Sun makes no representations of a relationship of any kind to licensors of Other Software. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE OTHER SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Licensee acknowledges and agrees as between Licensee and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET-related trademarks, service marks, logos and other brand designations ("Sun Marks"), and Licensee agrees to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use Licensee makes of the Sun Marks inures to Sun's benefit.

Licensee acknowledges that Sun may terminate this agreement immediately should the Software become, or in Sun’s opinion be likely to become, the subject of a claim of infringement of any intellectual property right.

For inquiries please contact: Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. (LFI#119611/Form ID#011801)

Terms and Conditions for the Use of IBM® 32-bit Runtime Environment for AIX™, Java™ 2 Technology Edition, Version 1.4

Acknowledgements


Licensee agrees that the following terms (in addition to the applicable provisions above) shall apply with respect to any open source provided by International Business Machines Corporation contained within the Product. Notwithstanding anything contained in the CA End User License Agreement, solely with respect to such open source, these terms are not superseded by any written agreement between CA and Licensee:

The IBM® 32-bit Runtime Environment for AIX™, Java™ 2 Technology Edition, Version 1.4 (the “Program”) is owned by International Business Machines Corporation or one of its subsidiaries (IBM) or an IBM supplier, and is copyrighted and licensed, not sold.

No Warranty

SUBJECT TO ANY STATUTORY WARRANTIES WHICH CAN NOT BE EXCLUDED, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE WARRANTY OF NON-INFRINGEMENT AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, REGARDING THE PROGRAM OR TECHNICAL SUPPORT, IF ANY. IBM MAKES NO WARRANTY REGARDING THE CAPABILITY OF THE PROGRAM TO CORRECTLY PROCESS, PROVIDE AND/OR RECEIVE DATE DATA WITHIN AND BETWEEN THE 20TH AND 21ST CENTURIES. This does not affect any warranties contained in any other applicable agreement between Licensee and CA.

The exclusion also applies to any of IBM's subcontractors, suppliers, or program developers (collectively called "Suppliers").

Limitation of Liability

NEITHER IBM NOR ITS SUPPLIERS WILL BE LIABLE FOR ANY DIRECT OR INDIRECT DAMAGES, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST SAVINGS, OR ANY INCIDENTAL, SPECIAL, OR OTHER ECONOMIC CONSEQUENTIAL DAMAGES, EVEN IF IBM IS INFORMED OF THEIR POSSIBILITY. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE EXCLUSION OR LIMITATION MAY NOT APPLY TO LICENSEE.

General Licensee acknowledges that IBM may terminate Licensee’s license if Licensee fails to comply with the terms of this agreement. If IBM does so, Licensee must immediately destroy the Program and all copies Licensee made of it.

With respect to any claim by or against IBM relating to the Program, neither Licensee nor IBM will bring a legal action more than two years after the cause of action arose unless otherwise provided by local law without the possibility of contractual waiver or limitation.

Acknowledgements


The laws of the country in which Licensee acquires the Program govern this agreement, except 1) in Australia, the laws of the State or Territory in which the transaction is performed govern this agreement; 2) in Albania, Armenia, Belarus, Bosnia/Herzegovina, Bulgaria, Croatia, Czech Republic, Georgia, Hungary, Kazakhstan, Kirghizia, Former Yugoslav Republic of Macedonia (FYROM), Moldova, Poland, Romania, Russia, Slovak Republic, Slovenia, Ukraine, and Federal Republic of Yugoslavia, the laws of Austria govern this agreement; 3) in the United Kingdom, all disputes relating to this agreement will be governed by English Law and will be submitted to the exclusive jurisdiction of the English courts; 4) in Canada, the laws in the Province of Ontario govern this agreement; and 5) in the United States and Puerto Rico, and People's Republic of China, the laws of the State of New York govern this agreement.

Part 2 - Country-unique Terms

AUSTRALIA:

No Warranty:

The following paragraph is added to this Section:

Although IBM specifies that there are no warranties, Licensee may have certain rights under the Trade Practices Act 1974 or other legislation and are only limited to the extent permitted by the applicable legislation.

Limitation of Liability:


Where IBM is in breach of a condition or warranty implied by the Trade Practices Act 1974, IBM's liability is limited to the repair or replacement of the goods, or the supply of equivalent goods. Where that condition or warranty relates to right to sell, quiet possession or clear title, or the goods are of a kind ordinarily acquired for personal, domestic or household use or consumption, then none of the limitations in this paragraph apply.

GERMANY:

No Warranty:

The following paragraphs are added to this Section:

The minimum warranty period for Programs is six months.

Acknowledgements


In case a Program is delivered without Specifications, IBM will only warrant that the Program information correctly describes the Program and that the Program can be used according to the Program information. Licensee has to check the usability according to the Program information within the "money-back guaranty" period.



The limitations and exclusions specified in the agreement will not apply to damages caused by IBM with fraud or gross negligence, and for express warranty.

INDIA:

General:

The following replaces the second paragraph of this Section:

If no suit or other legal action is brought, within two years after the cause of action arose, in respect of any claim that either party may have against the other, the rights of the concerned party in respect of such claim will be forfeited and the other party will stand released from its obligations in respect of such claim.

IRELAND:

No Warranty:


Except as expressly provided in these terms and conditions, all statutory conditions, including all warranties implied, but without prejudice to the generality of the foregoing, all warranties implied by the Sale of Goods Act 1893 or the Sale of Goods and Supply of Services Act 1980 are hereby excluded.

ITALY:


This Section is replaced by the following:

Unless otherwise provided by mandatory law, IBM is not liable for any damages which might arise.

NEW ZEALAND:

Acknowledgements


No Warranty:


Although IBM specifies that there are no warranties, Licensee may have certain rights under the Consumer Guarantees Act 1993 or other legislation which cannot be excluded or limited. The Consumer Guarantees Act 1993 will not apply in respect of any goods or services which IBM provides, if Licensee requires the goods and services for the purposes of a business as defined in that Act.



Where Programs are not acquired for the purposes of a business as defined in the Consumer Guarantees Act 1993, the limitations in this Section are subject to the limitations in that Act.

PEOPLE'S REPUBLIC OF CHINA:

Charges:

The following paragraph is added as a new Section:

All banking charges incurred in the People's Republic of China will be borne by Licensee and those incurred outside the People's Republic of China will be borne by IBM.

UNITED KINGDOM:


The following paragraph is added to this Section at the end of the first paragraph:

The limitation of liability will not apply to any breach of IBM's obligations implied by Section 12 of the Sales of Goods Act 1979 or Section 2 of the Supply of Goods and Services Act 1982.

Terms and Conditions for the Use of IBM® zSeries Developer Kit for Linux®, Java™ 2 Technology Edition

Licensee agrees that the following terms (in addition to the applicable provisions above) shall apply with respect to any open source provided by International Business Machines Corporation contained within the Product. Notwithstanding anything contained in the CA End User License Agreement, solely with respect to such open source, these terms are not superseded by any written agreement between CA and Licensee:

Acknowledgements


IBM ® zSeries Developer Kit for Linux®, Java™ 2 Technology Edition (the “Program”) is owned by International Business Machines Corporation or one of its subsidiaries (IBM) or an IBM supplier, and is copyrighted and licensed, not sold.

No Warranty

Licensee acknowledges that the Program is provided ‘AS IS’.

SUBJECT TO ANY STATUTORY WARRANTIES WHICH CAN NOT BE EXCLUDED, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE WARRANTY OF NON-INFRINGEMENT AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, REGARDING THE PROGRAM OR TECHNICAL SUPPORT, IF ANY. IBM MAKES NO WARRANTY REGARDING THE CAPABILITY OF THE PROGRAM TO CORRECTLY PROCESS, PROVIDE AND/OR RECEIVE DATE DATA WITHIN AND BETWEEN THE 20TH AND 21ST CENTURIES. The exclusion also applies to any of IBM's subcontractors, suppliers, or program developers (collectively called "Suppliers"). The foregoing shall not affect any warranties contained in any applicable agreement between Licensee and CA.

Limitation of Liability

NEITHER IBM NOR ITS SUPPLIERS WILL BE LIABLE FOR ANY DIRECT OR INDIRECT DAMAGES, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST SAVINGS, OR ANY INCIDENTAL, SPECIAL, OR OTHER ECONOMIC CONSEQUENTIAL DAMAGES, EVEN IF IBM IS INFORMED OF THEIR POSSIBILITY. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE EXCLUSION OR LIMITATION MAY NOT APPLY TO LICENSEE.

General

Licensee recognizes IBM's and Sun's ownership and title to their respective trademarks and of any goodwill attaching thereto, including goodwill resulting from use. Licensee will not use or attempt to register any trademark which is confusingly similar to such IBM or Sun trademarks.

Licensee acknowledges that IBM may terminate Licensee’s license if Licensee fails to comply with the terms of this agreement. If IBM does so, Licensee must immediately destroy the Program and all copies Licensee made of it.

With respect to any claims by or against IBM relating to the Program, neither Licensee nor IBM will bring a legal action more than two years after the cause of action arose unless otherwise provided by local law without the possibility of contractual waiver or limitation.

Acknowledgements


The laws of the country in which Licensee acquires the Program govern this Agreement, except 1) in Australia, the laws of the State or Territory in which the transaction is performed govern this Agreement; 2) in Albania, Armenia, Belarus, Bosnia/Herzegovina, Bulgaria, Croatia, Czech Republic, Georgia, Hungary, Kazakhstan, Kirghizia, Former Yugoslav Republic of Macedonia (FYROM), Moldova, Poland, Romania, Russia, Slovak Republic, Slovenia, Ukraine, and Federal Republic of Yugoslavia, the laws of Austria govern this Agreement; 3) in the United Kingdom, all disputes relating to this Agreement will be governed by English Law and will be submitted to the exclusive jurisdiction of the English courts; 4) in Canada, the laws in the Province of Ontario govern this Agreement; and 5) in the United States and Puerto Rico, and People's Republic of China, the laws of the State of New York govern this Agreement.

Country Unique Terms

AUSTRALIA:

No Warranty:


Although IBM specifies that there are no warranties, Licensee may have certain rights under the Trade Practices Act 1974 or other legislation and are only limited to the extent permitted by the applicable legislation.



Where IBM is in breach of a condition or warranty implied by the Trade Practices Act 1974, IBM's liability is limited to the repair or replacement of the goods, or the supply of equivalent goods. Where that condition or warranty relates to right to sell, quiet possession or clear title, or the goods are of a kind ordinarily acquired for personal, domestic or household use or consumption, then none of the limitations in this paragraph apply.

GERMANY:

No Warranty:

The following paragraphs are added to this Section:

The minimum warranty period for Programs is six months.

Acknowledgements


In case a Program is delivered without Specifications, IBM will only warrant that the Program information correctly describes the Program and that the Program can be used according to the Program information. Licensee has to check the usability according to the Program information within the "money-back guaranty" period.



The limitations and exclusions specified in the agreement will not apply to damages caused by IBM with fraud or gross negligence, and for express warranty.

INDIA:

General:

The following replaces the third paragraph of this Section:

If no suit or other legal action is brought, within two years after the cause of action arose, in respect of any claim that either party may have against the other, the rights of the concerned party in respect of such claim will be forfeited and the other party will stand released from its obligations in respect of such claim.

IRELAND:

No Warranty:


Except as expressly provided in these terms and conditions, all statutory conditions, including all warranties implied, but without prejudice to the generality of the foregoing, all warranties implied by the Sale of Goods Act 1893 or the Sale of Goods and Supply of Services Act 1980 are hereby excluded.

ITALY:


This Section is replaced by the following:

Unless otherwise provided by mandatory law, IBM is not liable for any damages which might arise.

NEW ZEALAND:

Acknowledgements


No Warranty:


Although IBM specifies that there are no warranties, Licensee may have certain rights under the Consumer Guarantees Act 1993 or other legislation which cannot be excluded or limited. The Consumer Guarantees Act 1993 will not apply in respect of any goods or services which IBM provides, if Licensee requires the goods and services for the purposes of a business as defined in that Act.



Where Programs are not acquired for the purposes of a business as defined in the Consumer Guarantees Act 1993, the limitations in this Section are subject to the limitations in that Act.

PEOPLE'S REPUBLIC OF CHINA:

Charges:

The following paragraph is added as a new Section:

All banking charges incurred in the People's Republic of China will be borne by Licensee and those incurred outside the People's Republic of China will be borne by IBM.

UNITED KINGDOM:


The following paragraph is added to this Section at the end of the first paragraph:

The limitation of liability will not apply to any breach of IBM's obligations implied by Section 12 of the Sales of Goods Act 1979 or Section 2 of the Supply of Goods and Services Act 1982.

Terms and Conditions for the Use of HP-UX Runtime Environment for the Java™ 2 Platform Version 1.4

Acknowledgements


Licensee agrees that the following terms (in addition to the applicable provisions above) shall apply with respect to any open source provided by HP contained within the Product. Notwithstanding anything contained in the CA End User License Agreement, solely with respect to such open source, these terms are not superseded by any written agreement between CA and Licensee:

HP-UX Runtime Environment for the Java™ 2 Platform (the “Software”) is owned and copyrighted by HP or its third party suppliers. This license confers no title or ownership in the Software and is not a sale of any rights in the Software. HP’s third party suppliers may protect their rights in the event of any violation of these license terms.

HP may terminate this license for the Software upon notice for failure to comply with any of these license terms. Upon termination, Licensee must immediately destroy the Software, together with all copies, adaptations and merged portions in any form.

By accepting this license agreement, Licensee confirms that it is not located in (or a national resident of) any country under U.S. economic embargo, not identified on any U.S. Department of Commerce Denied Persons List, Entity List or Treasury Department Designated Nationals exclusion list, and not directly or indirectly involved in the development or production of nuclear, chemical, biological weapons or in missile technology programs as specified in the U.S. Export Administration Regulations.

Licensee acknowledges that the Software is not designed or intended for use in on-line control of aircraft, air traffic, aircraft navigation, or aircraft communications; or in the design, construction, operation or maintenance of any nuclear facility. HP disclaims any express or implied warranty of fitness for such uses.

HP does not warrant that the operation of the Software will be uninterrupted or error free. If HP is unable, within a reasonable time, to repair or replace the Software to a condition warranted, Licensee will be entitled to a refund of the purchase price paid by Licensee to HP, which Licensee acknowledges is $0, upon prompt return of the Software. HP’s warranty does not apply to defects resulting from: a) improper or inadequate maintenance of calibration; b) software, interfacing, parts or supplies not supplied by HP; c) unauthorized modification or misuse; d) operating outside of the published environmental specifications for the Software; or e) improper site preparation or maintenance.

Acknowledgements


TO THE EXTENT ALLOWED BY LOCAL LAW, THE ABOVE WARRANTIES ARE EXCLUSIVE AND NO OTHER WARRANTY OR CONDITION, WHETHER WRITTEN OR ORAL, IS EXPRESSED OR IMPLIED AND HP SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, SATISFACTORY QUALITY, AND FITNESS FOR A PARTICULAR PURPOSE. Some countries, states, or provinces do not allow limitations on the duration of an implied warranty, so the above limitation or exclusion may not apply to Licensee. This warranty gives Licensee specific legal rights and Licensee might also have other rights that vary from country to country, state to state, or province to province. The foregoing shall not affect any warranties provided in any other applicable agreement between Licensee and CA.

TO THE EXTENT ALLOWED BY LOCAL LAW, THE REMEDIES IN THIS WARRANTY STATEMENT ARE LICENSEE’S SOLE AND EXCLUSIVE REMEDIES. EXCEPT AS INDICATED ABOVE, IN NO EVENT WILL HP OR ITS SUPPLIERS BE LIABLE FOR LOSS OF DATA OR FOR DIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL (INCLUDING LOST PROFIT OR DATA), OR OTHER DAMAGE, WHETHER BASED IN CONTRACT, TORT, OR OTHERWISE. Some countries, states, or provinces do not allow the exclusion of limitation of incidental or consequential damages, so the above limitation may not apply to Licensee.

Terms and Conditions for the Use of Java Naming and Directory InterfaceTM (JNDI) Version 1.2.1

and any of the following:

DNS Service Provider Version 1.2 LDAP Service Provider Version 1.2.4 NIS Service Provider Version 1.2.1 RMI Registry Service Provider Version 1.2.1 FS Context Service Provider Version 1.2 beta 3 release COS Naming Service Provider Version 1.2.1 DSML v1 Service Provider Version 1.2 JNDI/LDAP Booster Pack Version 1.0


Acknowledgements


Title to Java Naming and Directory InterfaceTM (JNDI), Version 1.2.1 and the above named Service Providers (collectively the “Software”) and all associated intellectual property rights is retained by Sun Microsystems, Inc. (“Sun”) and/or its licensors. Licensee acknowledges that the Software is not designed, licensed or intended for use in the design, construction, operation or maintenance of any nuclear facility. Sun disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to any trademark, service mark, logo or trade name of Sun or its licensors is granted under this agreement.

The Software is provided "AS IS". As to any claim made by Licensee against Sun respecting the Software, Licensee’s exclusive remedy and Sun's entire liability under this limited warranty will be at Sun's option to replace the Software media or refund the fee paid by Licensee to Sun for the Software which Licensee acknowledges is $0. The foregoing shall not affect any warranties provided in any other applicable agreement between Licensee and CA.



Sun may terminate Licensee’s right to use the Software if Licensee fails to comply with any provision of this agreement. Upon termination, Licensee must destroy all copies of the Software.


Acknowledgements


Licensee acknowledges and agrees as between Licensee and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, STAROFFICE, STARPORTAL and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, STAROFFICE, STARPORTAL and iPLANET-related trademarks, service marks, logos and other brand designations ("Sun Marks"), and Licensee agrees to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use Licensee makes of the Sun Marks inures to Sun's benefit.

License acknowledges that Sun may terminate this agreement immediately should the Software become, or in Sun’s opinion be likely to become, the subject of a claim of infringement of any intellectual property right.

For inquiries please contact: Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A (LFI#107226/Form ID#011801)

Terms and Conditions for the Use of JAVATM XML PACK SUMMER '02 BUNDLE


Title to Java™ XML Pack Summer ’02 Bundle (the “Software”) and all associated intellectual property rights is retained by Sun Microsystems, Inc. (“Sun”) and/or its licensors. Licensee acknowledges that the Software is not designed or intended for use in the design, construction, operation or maintenance of any nuclear facility. Sun disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to any trademark, service mark, logo or trade name of Sun or its licensors is granted under this agreement.



Acknowledgements





Licensee acknowledges and agrees as between Licensee and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET-related trademarks, service marks, logos and other brand designations ("Sun Marks"), and Licensee agrees to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use you make of the Sun Marks inures to Sun's benefit.


For inquiries please contact: Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303 (LFI#113314/Form ID#011801)

Terms and Conditions for the Use of JavaBeans™ Activation Framework, Version 1.0.2


Acknowledgements


Title to JavaBeans™ Activation Framework, Version 1.0.2 (the “Software”) and all associated intellectual property rights is retained by Sun Microsystems, Inc. (“Sun”) and/or its licensors. Licensee acknowledges that the Software is not designed, licensed or intended for use in the design, construction, operation or maintenance of any nuclear facility. Sun disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to any trademark, service mark, logo or trade name of Sun or its licensors is granted under this agreement.






Licensee acknowledges that Sun is under no obligation to support the Software or to provide Licensee with updates or error corrections. Licensee acknowledges that the Software may have defects or deficiencies which cannot or will not be corrected by Sun.

Acknowledgements


Licensee acknowledges and agrees as between Licensee and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET-related trademarks, service marks, logos and other brand designations ("Sun Marks"), and Licensee agrees to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use Licensee makes of the Sun Marks inures to Sun's benefit.


For inquiries please contact: Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303 (LFI#115020/Form ID#011801)

Terms and Conditions for the Use of JavaMail™, Version 1.3


Title to JavaMail™, Version 1.3 (the “Software”) and all associated intellectual property rights is retained by Sun Microsystems, Inc. (“Sun”) and/or its licensors. Licensee acknowledges that the Software is not designed, licensed or intended for use in the design, construction, operation or maintenance of any nuclear facility. Sun disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to any trademark, service mark, logo or trade name of Sun or its licensors is granted under this agreement.



Acknowledgements



Sun may terminate Licensee’s right to use the Software if License fails to comply with any provision of this agreement. Upon termination, Licensee must destroy all copies of the Software.


Licensee acknowledges and agrees as between Licensee and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, STAROFFICE, STARPORTAL and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, STAROFFICE, STARPORTAL and iPLANET-related trademarks, service marks, logos and other brand designations ("Sun Marks"), and Licensee agrees to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use Licensee makes of the Sun Marks inures to Sun's benefit.


For inquiries please contact: Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A (LFI#114176/Form ID#011801)

Index 125

Index

A alarm management, setting up • 86 AutoSys See Unicenter AutoSys Job

Management • 86

B browser configuration • 87

C CA Common Services for z/OS and OS/390 •

22 CA-CPS • 23

starting • 32 CAICCI

link editing with TCP/IP • 23 overview • 24 port number • 24

CAIENF • 24, 30, 31 procedure, customizing • 27

CleverPath Portal • 92, 93, 100 configuring

Unicenter Enterprise Job Manager • 53, 54, 57, 72, 73, 74, 75, 76, 77, 78, 79

consolidated event console • 81

D documentation set • 7

E EJMMGR user • 54 EJMUSER user • 54 eTrust CAACF2 • 30 eTrust CATop Secret • 30 event console

event console, publish all messages to Event Console • 83

H heap size • 89

I IIS • 100

J Java Secure Socket Extensions (JSSE) • 93

M Mozilla • 87

P portal • 92

scripts • 93 portal.bat • 93 PROFILE data set • 28 PROTOCOL statement • 24

R RACF • 30

S SCHSRVR task • 27, 28, 30

modifying • 29 Secure Sockets Layer • 91

architecture • 92 SSL troubleshooting • 100 system administrator • 7

T TCP/IP • 23

communications, testing • 26 Gateway server started task, configuring •

24 Gateway server started task, defining

parameters for • 24 Tomcat • 92, 93, 100

U Unicenter AutoSys Job Management

Unicenter AutoSys Job Management, Adding and Configuring Servers • 72

Unicenter AutoSys Job Management, alarms • 86

Unicenter AutoSys Job Management, Creating a Consolidated Event Console to View Unicenter AutoSys Job Management Messages Only • 82


Unicenter CA-7 • 21 installing host components • 21 server, configuring • 22 updating • 32

Unicenter CA-7 Product Table, merging • 31 Unicenter TCPaccess Communications Server •

24