Tivoli Workload Scheduler - IBMpublib.boulder.ibm.com/tividd/td/TWS/GC32-0641-00/en_US/... · 2002-11-09 · Tivoli Workload Scheduler Extended Agent for Oracle User’s Guide 1 1

Tivoli WorkloadSchedulerExtended Agent for Oracle User’s GuideVersion 1.3

Tivoli WorkloadSchedulerExtended Agent for Oracle User’s GuideVersion 1.3

Tivoli Workload Scheduler Extended Agent for Oracle User’s Guide (May 2000)

Copyright Notice

Copyright © 2000 by Tivoli Systems, an IBM Company, including this documentation and all software. All rights reserved.May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products to IBMCustomer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrievalsystem, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical,chemical, manual, or otherwise, without prior written permission of Tivoli Systems. The document is not intended forproduction and is furnished “as is” without warranty of any kind. All warranties on this document are hereby disclaimedincluding the warranties of merchantability and fitness for a particular purpose.

Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subject torestrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

Trademarks

The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/2, RS/6000, TivoliManagement Environment, and TME 10.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation.UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open CompanyLimited.

Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others.

Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will beavailable in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services isnot intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to TivoliSystems’ or IBM’s valid intellectual property or other legally protectable right, any functionally equivalent product, program,or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation inconjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of theuser.

Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. Thefurnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to theIBM Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, New York 10594.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vWho Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Prerequisite and Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

What This Guide Contains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Support for Oracle Apps Version 10.6 and 10.7 . . . . . . . . . . . . . . . . . . . 2

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

CD-ROM Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Tape Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Interface Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2. Set Up and Operation . . . . . . . . . . . . . . . . . . . . . . . . . 9Defining a TWS Extended Agent for Oracle Applications Workstation . . . . . 10

Command Line Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Defining Jobs in Oracle Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Running a Single Job Concurrently . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Defining Oracle Applications Jobs in TWS . . . . . . . . . . . . . . . . . . . . . . . . . 15


Scheduling Oracle Applications Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21


TWS and Oracle Applications Job States . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

iiiTivoli Workload Scheduler Extended Agent for Oracle User’s Guide

Chapter 3. Options File Reference . . . . . . . . . . . . . . . . . . . . . . 25The mcmoptions File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Entry Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Encrypting Oracle Applications User Passwords. . . . . . . . . . . . . . . . . . 27

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

iv Version 1.3

Preface

Who Should Read This GuideThe target audience for this guide is system managers who willinstall and configure TWS Extended Agents, and systemadministrators who perform daily administration tasks using OracleApplications.

Users of the guide should have some knowledge of:

¶ The Tivoli Workload Scheduler (TWS), (formerly known asUnison/Tivoli maestro) Oracle Applications operatingenvironments.

¶ The UNIX and Windows NT operating systems

Prerequisite and Related DocumentsThe following document contains information related to the TivoliWorkload Scheduler (TWS) Extended Agent for Oracle Applications:

¶ Tivoli Workload Scheduler User Guide

Provides information about setting up and managing the TivoliWorkload Scheduler environment. It also provides generalinformation about extended agents. (Prerequisite)

What This Guide ContainsThe sections contained in this manual are:

¶ Section 1 Introduction—provides an introduction to the productand installation information.

¶ Section 2 Set Up and Operation—describes how to configurethe TWS Extended Agent for Oracle Applications workstation,and how to create jobstreams with Oracle Applications jobs.

¶ Section 3 Options File Reference—provides information aboutTWS Extended Agent for Oracle Applications options file.

vTivoli Workload Scheduler Extended Agent for Oracle User’s Guide

Conventions Used in This GuideThe following conventions are used in this guide to describe thespecial terms or commands. These conventions have the followingmeanings:

Bold Commands, keywords, file names, or other information thatyou must use literally appear bold.Names of windows,dialogs, and other controls also appear bold.

Italics Variables and values that you must provide appear in italics.

Bold ItalicsNew terms appear in bold italics the first time they are used.

MonospaceCode examples appear in monospace font.

Contacting Customer SupportIf you encounter difficulties with any Tivoli products, you can enterhttp://www.support.tivoli.com to view the Tivoli Support home page.After you link to and submit the customer registration form, you willbe able to access many customer support services on the Web.

Use the following phone numbers to contact customer support in theUnited States:

The Tivoli number is 1-800-848-6548 (1-800-TIVOLI8)

The IBM number is 1-800-235-5511 (press or say 8 after you reachthis number).

Both of these numbers direct your call to the Tivoli CustomerSupport Call Center.

We are very interested in hearing from you about your experiencewith Tivoli products and documentation. We welcome yoursuggestions for improvements. If you have comments or suggestionsabout this documentation, please send e-mail to [email protected].

vi Version 1.3

Introduction

The Tivoli Workload Scheduler (TWS) Extended Agent for OracleApplications (x-agent) gives you the ability to schedule OracleApplications jobs using the sophisticated job scheduling features ofTWS. In the following diagram, read “WS” (Workload Scheduler) as“TWS” (Tivoli Workload Scheduler).

Note: The TWS Host, the TWS Extended Agent for OracleApplications, and the Oracle Applications Instance must beinstalled on the same physical node.

Features¶ Use TWS’s standard job dependencies (except Open File

dependencies).

WSWin NT

WSMVS X-Agent

WSHP MPE

WSUnix

WSHost

X-Agent

Oracle Apps

1

1Tivoli Workload Scheduler Extended Agent for Oracle User’s Guide

1.In

trod

uctio

n

¶ Schedule Oracle Applications jobs to run on specified days,times, and in a prescribed order.

¶ Define inter-dependencies between Oracle Applications jobs andjobs that run on different systems such as SAP R/3 and Baan IV.

¶ Define inter-dependencies between Oracle Applications jobs andjobs that run on different platforms, including Windows NT,MVS, HP MPE, and UNIX.

Software RequirementsTo install and use the TWS Extended Agent for Oracle Applications(x-agent) you must have the following software installed:

¶ TWS version 5.2 or higher

¶ Oracle RDBMS 7.3.3 or higher.

¶ Oracle Applications version 10.6 or 10.7

¶ ANSI C compiler. This option must be selected when installingthe Oracle server. For Oracle server installation instructions seethe Oracle documentation.

One of the following supported operating systems:

¶ HP-UX version 10.20 or 11.0

¶ Sun Solaris version 2.6 or 2.7

¶ IBM AIX 4.2 or 4.3

For the latest list of supported platforms, contact the Tivoli CustomerSupport representative.

Support for Oracle Apps Version 10.6 and 10.7The TWS Extended Agent for Oracle Applications version 1.3 iscertified for Oracle Applications versions 10.6 and 10.7.

Features

2 Version 1.3

Installation

CD-ROM InstallationTo install the TWS Extended Agent for Oracle Applications softwareon the TWS UNIX host computer, perform the following steps:

1. Log in as an Oracle Applications UNIX user, who has access toall the files under the Oracle Application Top directory.

2. Create a temporary directory and change to the temporarydirectory:mkdir temp

cd temp

3. Copy the TWS Extended Agent for Oracle Applications softwarefrom the CD-ROM to the temporary directory:tar -xvf cd_device/TWS/platform/ora_ver/ORACLE.TAR

where:

cd_deviceThe pathname of your CD drive.

″TWS”used to be called “Maestro”.

platformThe target platform from the list below.

AIX IBM

HPUXHewlett-Packard

SOLARISSun Solaris

ora_verEither ORA106 for Oracle Applications 10.6 or ORA107 forOracle Applications 10.7.

Note: If you are running the Oracle Applications demo database,substitute the APPDEMO.env file in steps 4 and 5.

4. Modify the Oracle Applications APPLSYS.env file as follows:

Installation


1.In

trod

uctio

n

a. Append MCM to the APPLSHAR and APPLFULL variables.APPLSHAR=’ALR FF MCM’

APPLFUL=’FND AD AX AK GL RG INV OP MCM’

b. Define and export the shell variable MCM_TOP:MCM_TOP=$APPL_TOP/mcm/integration

export MCM_TOP

c. Add the $MCM_TOP/bin to the PATH variable by enteringthe following lines at the bottom of the APPLSYS.env file:PATH=$PATH:$MCM_TOP/bin

export PATH

5. Run the APPLSYS.env file to set the environment:. APPLSYS.env

Note: Make sure that the Oracle Applications login has permissionsto write into the TWShome and methods directories.

6. Run the installation script mcminstall from the temp directory.An Oracle Tivoli screen is displayed.

7. Enter I and press return. The installation scripts are started andthe integration files are installed to the TWShome/methodsdirectory.

If the installation script returns a 0 the install was successful. Areturn code of 1 indicates that the install failed.

8. Delete the temporary directory:cd..

rm temp

The installation is complete.

Tape InstallationTo install the Oracle Applications x-agent software on the WorkloadScheduler UNIX host computer, perform the following steps:

1. Log in as an Oracle Applications UNIX user, who has access toall the files under the Oracle Application Top directory.

Installation

4 Version 1.3

2. Create a temporary directory and change to the temporarydirectory:mkdir temp

cd temp

3. Copy the integration software from the tape into the temporarydirectory:tar -xv[f device] TWS/platform/ora_ver/ORACLE.TAR

where:

cd_deviceThe pathname of your CD drive. “WS” used to be called“Maestro”.

platformThe target platform from the list below.

AIX IBM

HPUXHewlett-Packard

SOLARISSun Solaris

ora_verEither ORA106 for Oracle Applications 10.6 or ORA107 forOracle Applications 10.7.

4. Untar the product files:tar -xvf

TWS/platform/ora_ver/ORACLE.TAR

Note: If you are running the Oracle Applications demo database,substitute the APPDEMO.env file in steps 4 and 5.

5. Modify the Oracle Applications APPLSYS.env file as follows:

a. Append MCM to the APPLSHAR and APPLFULL variables.APPLSHAR=’ALR FF MCM’

APPLFUL=’FND AD AX AK GL RG INV OP MCM’

b. Define and export the shell variable MCM_TOP:

Installation


1.In

trod

uctio

n

MCM_TOP=$APPL_TOP/mcm/integration

export MCM_TOP

c. Add the $MCM_TOP/bin to the PATH variable by entering thefollowing lines at the bottom of the APPLSYS.env file:PATH=$PATH:$MCM_TOP/bin

export PATH

6. Run the APPLSYS.env file to set the environment:. APPLSYS.env

Note: Make sure that the Oracle Applications login has permissionsto write into the TWShome and methods directories.

7. Run the installation script mcminstall from the temp directory.An Oracle Tivoli screen is displayed.

8. Enter I and press return. The installation scripts are started andthe integration files are installed to the TWShome/methodsdirectory.

If the installation script returns a 0 the install was successful. Areturn code of 1 indicates that the install failed.

9. Delete the temporary directory:cd..

rm temp

The installation is complete.

Interface SoftwareThe interface between Tivoli Workload Scheduler (TWS) and OracleApplications is comprised of the following software:

MCMAGENTis theTWS Extended Agent for Oracle Applications (x-agent)access method.

MCMLJsubmits a job to Oracle Concurrent Manager (OCM).

MCMSTATmonitors the status of the job submitted.

Installation

6 Version 1.3

MCMTJterminates the job submitted, on receiving a kill signal fromTWS.

mcm.mkis a makefile utility for linking the above programs withOracle Applications.

mcmoptionsis a sample options file which contains details about theenvironment to be set before starting the TWS OracleApplications x-agent. This file must strictly follow theformat specified in the following screen shot.

Interface Software


1.In

trod

uctio

n

Customer SupportIf you have any questions about the product, please call the TivoliCustomer Support Call Center:

1-800-TIVOLI8 (1-800-848-6548) or 1-800-235-5511

You can also contact Tivoli at the following addresses:

Company home page: http://www.tivoli.com

Support home page: http://www.support.tivoli.com

E-mail address for technical support: [email protected]

E-mail address for documentation comments: [email protected]

Customer Support

8 Version 1.3

Set Up and Operation

Tivoli Workload Scheduler (TWS) can launch and monitor jobs onan instance of Oracle Applications using a TWS Extended Agent forOracle Applications(x-agent) workstation. The Oracle Applicationsx-agent is defined in a standard TWS workstation definition, whichgives the x-agent a name and identifies the access method asMCMAGENT. Each instance of Oracle Applications is defined as aseparate x-agent workstation, and each must have a separate entry inthe mcmoptions file.

The workstation definition for the Oracle Application x-agent is alogical definition for an instance of Oracle Applications. OracleApplications and the TWS Host must run on the same physicalworkstation.

2


2.S

etU

pan

dO

peratio

n

In the above diagram, read “WS (Workload Scheduler)” as “TWS”(Tivoli Workload Scheduler).

To launch an Oracle Applications job, TWS executes the x-agent’saccess method, MCMAGENT, passing it the x-agent’s workstation nameand information about the job. Using the x-agent’s workstation nameas a key, MCMAGENT looks up the corresponding entry in themcmoptions file to determine which instance of Oracle Applicationsit will connect to. The Oracle Applications x-agent can then launchjobs on that instance of Oracle Applications and monitor the jobsthrough completion, writing job progress and status information tothe job’s standard list file.

Note: Before an Oracle Applications job can be launched by TWS,it must be defined in both Oracle Applications and in TWS.

Defining a TWS Extended Agent for OracleApplications Workstation

TWS Extended Agent for Oracle Applications (x-agent) workstationdefinitions are required for each instance of Oracle Applications thatwill execute TWS-scheduled jobs. They are defined in the standardmanner and include the name of the x-agent’s host and the access

WS Host

MCMAGENT mcmoptions

Oracle Applicationsinstance 01

job1

access method

Maeworkstation1

Oracle Applicationsinstance 02

job2

Oraworkstation1 Oraworkstation2X-agent workstation definition

MCMAGENTaccess method

X-agent workstation definition

Set Up and Operation

10 Version 1.3

method name. The following figures show both the legacy GUI andnew JS Console screens. The first screen is the legacy GUIComposer Workstation Definition window for an Oracle Applicationsx-agent named ORA002. The second screen shows the JobScheduling (JS) Console window for defining a workstation. Forinformation about using JS Console to define a workstation, refer tothe Tivoli Workload Scheduler User’s Guide.

The legacy GUI fields are:

Node Not used. Enter at least one letter.

TCP AddressNot used. Enter at least one number.

Operating SystemSelect OTHER.

DescriptionA description of the workstation. It can contain up to 40alphanumeric characters. This field is optional.

Maestro OptionsNot used.

Defining a TWS Extended Agent for Oracle Applications Workstation


2.S

etU

pan

dO

peratio

n

ServerNot used.

Host CPUThe TWS name of the host system. This is the TWS master,fault-tolerant agent, or standard agent that hosts the OracleApplications x-agent workstation. Click the Workstations...button to select a workstation from a list.

AccessThe name of the Oracle Applications access method,MCMAGENT. This is executed by the TWS host to connect toan instance of Oracle Applications. Click the Methods...button to select MCMAGENT from a list.

The JS Console Workstation Definition GUI fields are:


12 Version 1.3

Name The TWS name of the Oracle Applications x-agent. It cancontain up to eight alphanumeric characters starting with aletter.

Node Enter the fully qualified machine name.

TCP PortUse the same netman port number as you do on your master.

Operating SystemSelect OTHER.

DomainUse Master if the x-agent is in that domain. If it is not,browse for a domain to use by selecting “ ... ”.

Time ZoneSelect the relevant time zone from the drop down menu, forthe applicable system. You must have Time Zone enabled onthe Master DM to utilize this feature. If your master doesnot use Time Zone, leave this field blank.

DescriptionA description of the workstation. It can contain up to 40alphanumeric characters. This field is optional.

Workstation TypeSelect Extended Agent.

AutoLinkSelect this if you want TWS to initialize the x-agent.

IgnoreUse this if you do not want TWS to initalize this system.

Full StatusNot used.

Resolve DependenciesNot used.

ServerNot used.

Access MethodThe name of the Oracle Applications access method,



2.S

etU

pan

dO

peratio

n

MCMAGENT. This is executed by the TWS host to connect toan instance of Oracle Applications. Enter MCMAGENT.

Host The TWS name of the host system. This is the TWS master,fault-tolerant agent, or standard agent that hosts the OracleApplications x-agent workstation. Click the Workstations ...button to select workstation from the list.

Command Line ExampleWorkstation definitions can also be entered at the Composercommand line. The workstation definition shown in the previousexample would be entered as follows:workstationname ora002

node nullos otherdescription "oracle extended agent #002"for Workload Scheduler

host goliathaccess mcmagent

end

For information about using the Composer command line interface tocreate workstation definitions, refer to the Tivoli Workload SchedulerReference Manual.

Defining Jobs in Oracle ApplicationsIn Oracle Applications, jobs that are to be scheduled with TWS aredefined in the same manner as other Oracle Applications jobs (andcan be submitted in OCM). When you are submitting the job inOCM, specify the scheduling and resubmission information. Whenyou are submitting the job through TWS, TWS will take care of thescheduling and resubmission information.

To define a job, use the Define Concurrent Program Executables andDefine Concurrent Program forms and fill in the general datainformation for the job. The job is now available for schedulingfrom TWS (and can also be submitted in OCM as well).


14 Version 1.3

Running a Single Job ConcurrentlyIf an Oracle Applications job is scheduled to run more than once inTWS, and TWS launches it concurrently, the jobs will run normally.However, if the Oracle Applications user has specified that the jobcannot run concurrently, the second job will enter a state of WAITuntil the first job completes.

Defining Oracle Applications Jobs in TWSTWS job definitions are required for each Oracle Applications jobyou intend to schedule. Oracle Applications jobs are defined in TWSlike other jobs and include job name, user name, and recoveryoptions. The following figures show Job Definition windows. Thefirst figure is the legacy GUI and shows the job definition for a jobnamed ORAJOB2 on the Oracle Applications x-agent workstationORA002. The second figure is the JS Console GUI, Properties - JobDefinition windows (General and Task) for job TEST9.

For information about using TWS to define jobs, refer to the TivoliWorkload Scheduler Reference Manual.

The legacy GUI Job Definition fields are:

Logon The user name used to run the job in TWS. This must be a

Defining Jobs in Oracle Applications


2.S

etU

pan

dO

peratio

n

valid user on the TWS host workstation. It is required toschedule the job in TWS, and it will appear in TWSdisplays.

DescriptionA description of the job. It can contain up to 40alphanumeric characters. This field is optional.

Script FileEnter the specifications for the Oracle Applications job file.These are the parameters:

-user appslogin

-job jobspecs

-prn printopts

[-vn {’value’|null|:parameter}]

-userappsloginEnter a valid Oracle Applications user (Apps login). Forexample:

-user GLOBAL

-jobjobspecsEnter the Oracle Applications job attributes. There are fourjob attributes to be specified. They must be entered in thefollowing order:

¶ name of the Applications module used to sign on to OracleApplications (for example, FND)

¶ a valid responsibility for the Applications module (for example,“Application Developer”). This parameter must be enclosed inquotes.

¶ name of the application which registered the job (for example,PO)

¶ job name (for example, POXACR). The job name must beuppercase. For example:

-job FND ’Application Developer’ PO POXACR

-prnprintopts Enter the two printer options for the job. They mustbe entered in the following order:

Defining Oracle Applications Jobs in TWS

16 Version 1.3

¶ printer name (optional). If omitted the default printer specified inthe mcmoptions file is used.

¶ number of copies

¶ Below are two examples:-prn ps4 2

-prn 0


Enter the job’s parameters, if any. If no parameters are specified inOracle Applications for the job, this string is optional.

¶ n is the parameter number (v1, v2, etc.)

¶ the Oracle x-agent software will automatically add all parametersthat you do not specify in the definition with a value of null.

¶ enter an actual value (enclose value in single quotes if itcontains special characters)

¶ enter the name of a TWS:parameter. The parameter must bedefined beforehand. See the Tivoli Workload Scheduler User’sGuide for more information about TWS parameters.

Below are two examples:-v4 ’abc’

-v15 :p1

Below is an example of an entire Script File field specification:-user GLOBAL -job FND ’Application Developer’ PO POXACR -prn ps4 2 -v1 ’abc’

CommandNot used.

For information on recovery options and about using TWS to definiejobs refer to the Tivoli Workload Scheduler Reference Manual and



2.S

etU

pan

dO

peratio

n

User’s Guide.

The JS Console GUI Job Definition fields are:

Name The TWS name of the Oracle Applications job. It cancontain up to eight alphanumeric characters, including dashesand underscores, but must start with a letter. Embeddedspaces are not allowed. This name is used to schedule thejob in TWS. The name will appear in TWS displays. Thisname can be the same as the Oracle Applications job name,unless it would be invalid in TWS.

WorkstationThe TWS name of the Oracle Applications x-agentworkstation.

DescriptionA description of the job. It can contain up to 40alphanumeric characters. This field is optional.

Login The user name used to run the job in TWS. This must be a


18 Version 1.3

valid user on the TWS host workstation. It is required toschedule the job in TWS, and it will appear in TWSdisplays.

Recovery OptionsStop, Continue, Rerun. The Default is Stop. For informationon recovery options refer to the Tivoli Workload SchedulerReference Manual.

MessageUse this to enter an optional message.

The JS Console GUI Job Definition fields are:

Task Enter the task name and any additional parameters needed asfollows: Enter the specifications for the Oracle Applicationsjob file. These are the parameters:

-user appslogin

-job jobspecs



2.S

etU

pan

dO

peratio

n

-prn printopts


-userappsloginEnter a valid Oracle Applications user (Apps login). Forexample:

-user GLOBAL

-jobjobspecsEnter the Oracle Applications job attributes. There are fourjob attributes to be specified. They must be entered in thefollowing order:

¶ name of the Applications module used to sign on to OracleApplications (for example, FND)

¶ a valid responsibility for the Applications module (for example,“Application Developer”). This parameter must be enclosed inquotes.

¶ name of the application which registered the job (for example,PO)

¶ job name (for example, POXACR). The job name must beuppercase. For example:

-job FND ’Application Developer’ PO POXACR

-prnprintoptsEnter the two printer options for the job. They must beentered in the following order

¶ printer name (optional). If omitted the default printer specified inthe mcmoptions file is used.

¶ number of copies

¶ Below are two examples:-prn ps4 2

-prn 0


Enter the job’s parameters, if any. If no parameters are specified inOracle Applications for the job, this string is optional.

¶ n is the parameter number (v1, v2, etc.)


20 Version 1.3

¶ the Oracle x-agent software will automatically add all parametersthat you do not specify in the definition with a value of null.

¶ enter an actual value (enclose value in single quotes if itcontains special characters)

¶ enter the name of a TWS:parameter. The parameter must bedefined beforehand. See the Tivoli Workload Scheduler User’sGuide for more information about TWS parameters.

Below are two examples:-v4 ’abc’

-v15 :p1

Below is an example of an entire Script File field specification:-user GLOBAL -job FND ’Application Developer’ PO POXACR -prn ps4 2 \-v1 ’abc’

Command Line ExampleJobs can also be defined at the composer command line. Thefollowing example documents a TWS job named ORAJOB2 thatruns on an Oracle Applications x-agent workstation named ORA002.It logs on to UNIX as ORAJOBS and launches a job under OracleApplications. The Oracle Applications job is named POXACR andits owner is GLOBAL. If recovery is needed, TWS will run jobRECOV2 and then continue processing.ora002#orajob2

streamlogon orajobsscriptname "-user global-job fnd ’application developer’ po poxacr

-prn ps4 2-v1 ’abc’"

description "oracle apps job #2"recovery continue after recov2

Scheduling Oracle Applications JobsOracle Applications jobs are scheduled (jobstreamed) in the samemanner as other TWS jobs and can include dependencies and othercontrols. The following figures show the legacy GUI and the JSConsole GUI. The legacy GUI screen shows a Composer JobstreamDefinition window for a jobstream named MYSKED on workstation



2.S

etU

pan

dO

peratio

n

ORA002, which includes the job MAINWORKSTATION#MYJOBand the Oracle Applications x-agent jobs ORAJOB1 and ORAJOB2.

Note: ORAJOB1 and ORAJOB2 are the TWS names for the jobs,the Oracle Applications names for the jobs may be different.

Note: Opens Files dependencies are not supported for the Oraclex-agent.

For information about using the JS Console to create jobstreams,refer to the Tivoli Workload Scheduler User’s Guide.

The following figures show the JS Console GUI Job StreamDefinition window and Job Stream Editor window:

Scheduling Oracle Applications Jobs

22 Version 1.3

Command Line ExampleJobstreams can also be entered at the Composer command line. Thefollowing example shows a jobstream called MYSKED on theOracle Applications x-agent ORA002.



2.S

etU

pan

dO

peratio

n

jobstream ora002#myskedon monthendat 1600

:mainworkstation#myjobora002#orajob1 follows mainworkstation#myjobora002#orajob2 follows ora002#orajob1

end

For information about using the JS Console command line to createjobstreams, refer to the Tivoli Workload Scheduler ReferenceManual.

TWS and Oracle Applications Job StatesWhen an Oracle Applications job is launched by TWS, you canmonitor its progress via the command line, with TWS’s consolemanager, Conman. The state transitions in TWS and thecorresponding Oracle Applications states are listed below.

Oracle Concurrent ManagerStates

TWS States

Request Failure or Request notFound

UT (unsupported task)

Inactive SUSP

Pending WAIT

Pending Normal ADD

Running Normal EXEC

Completed Normal SUCC

Completed Warning SUCC

Completed Error ABEND

Completed Terminated ABEND

Completed Canceled ABEND

For more information about job management, refer to the TivoliWorkload Scheduler Reference Manual.


24 Version 1.3

Options File Reference

This section provides detailed reference information about the TWSExtended Agent for Oracle Applications (x-agent) options file,mcmoptions.

The mcmoptions FileThe options file contains an entry for each instance of OracleApplications that TWS will run jobs on. The entries must beseparated by one or more spaces. This file must exist in the directoryTWShome/methods.

The mcmoptions file entries must be in the following format. All ofthe entries are required.

Entry Syntaxxagent oraclehome oracle_sid oraapptopdirfndtopdir path env userid password printernamemintime maxtime

where:

xagent The TWS workstation name of the extended agent for thisinstance of Oracle Applications.

oraclehomeThe UNIX directory where Oracle software is installed.

oracle_sidThe Oracle system identifier of the database instance you are

3


3.O

ptio

ns

File

Referen

ce

connecting to. This corresponds to the value of the OracleApplications $ORACLE_SID variable.

oraapptopdirThe UNIX directory where Oracle Applications is installed.

fndtopdirThe FND top directory where the Application Object Libraryresides.

path The setting of the PATH variable, including, the existingpath, the path to the bin directory of Oracle Applications,the path to the include directory under the FND Topdirectory, and others as needed.

env The environment file to execute. Each instance of OracleApplications has its own environment file (APPLSYS.env orAPPDEMO.env). The .env filename given here will be usedto set the environment dynamically when TWS runs jobs onthe Oracle Applications x-agent.

userid A database user id that has access to all the Modules inOracle Applications. It must be able to launch, manage andterminate jobs in Oracle Applications.

passwordThe password for the selected userid.

printernameThe default printer id.

mintimeThe number of seconds to be added to the previous pollinginterval after which the job status check has to be carriedout, expressed in seconds.

maxtimeWhen the polling interval reaches this limit, it will notincremented, thereby the polling interval remains constant,expressed in seconds.

ExampleHP9000 /general/ora716 DEMO106 /apps106 $APPL_TOP/fnd/*

The mcmoptions File

26 Version 1.3

$PATH:$ORACLE_HOME/bin:$FND_TOP/include$APPL_TOP/APPDEMO106.env APPS_US APPS_USPRINTER1 10 200

Encrypting Oracle Applications User PasswordsWhen you make entries in the mcmoptions file, the password valueis automatically encrypted before it is written to the file. If youmodify the file with a text editor, you must run the enigma programto encrypt the password before writing it to the file. Run the enigmaprogram as follows:enigma [password]

You can include the password on the command line or enter it in theresponse to a prompt. The program returns an encrypted version thatyou can then enter in the mcmoptions file.

The mcmoptions File


3.O

ptio

ns

File

Referen

ce

28 Version 1.3

Index

Aagent

fault-tolerant 1standard 1

Ddefining jobs in Oracle Applications 14defining Oracle Applications jobs

command line example 21in Maestro 15

defining the cpu 10

Eencrypting user passwords 27enigma 27

Ffeatures 1

Iinterface software 6

Jjob states

Maestro and Oracle Applications 24

MMCMAGENT 6, 9, 12, 13mcmoptions

overview 7mcmoptions file

entry syntax 25example 26overview 9, 25

OOracle Applications jobs

defining 14scheduling 21scheduling, command line example 23script file 16

Oracle Applications x-agentaccess method 12, 13cpu name 13defining the cpu 10defining the cpu, command line example 14features 1host cpu 12, 14setup and operation 9


Ind

ex

Ppassword encryption 27

Sscheduling Oracle Applications jobs 21setup and operation 9software

components 6requirements 2

syntax, mcmoptions file 25

30 Version 1.3

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC32-0641-00