May 9-12, 2006

®

IBM Software Group

© 2010 IBM Corporation

Marco Borgianni

May 9-12, 2006

IBM Tivoli Workload Schedulerfor Applications

IBM Software Group | Tivoli software


TWS XA

TWSDM

TWS and Extended Agents – Topology Example

TWSMDM

JSC

TWSDM

TWSFTA

TWSFTA

TWSFTA

TWSSA

TDWC



TWS for Applications: Architecture

An Application Extensions’ workstation (CPU) is only a logical entity related to an access method hosted by a physical workstation where the Fault Tolerant Agent (FTA) runs

More than one Application Extension workstations can be hosted by the same FTA and rely on the same access method

JSC

TDWC

TDWCFTA

Oracle System1

Oracle System2

MCMAGENT

ApplicationExtensions

CPUs



Application Specific Extensions

SAP R/3 and Business Warehouse

PeopleSoft

Oracle e-Business Suite

MVS (CA7/JES/OPC)



Business Application Integration Summary

Benefits PayoffsLeverages commodity computing and

standardsTotal Cost of Ownership is dramatically reduced. One scheduler to allocate business application integration.

Fewer skills to build in the company

Sustain Business Grow Sustain Business Grow

Higher System Utilization Logical Workstation hosted by the same physical machine connecting to many Application Servers provides an increased ROI for the E2E solution.

Reduced Capital costs. Enhanced system optimization.

Optimize the DemandOptimize the Demand

Integrated Product Solution Higher IT productivity. Maximize flexibility. More granular control.

Automate the ProcessAutomate the Process

IBM Tivoli Workload Scheduler for Applications Extends the End to End capabilities

IBM Tivoli Workload Scheduler for Applications Extends the End to End capabilities



Workload Scheduler Application Extensions

master domain manager

extended agent

java console

fault tolerant agent

domain manager

extended agent


Access Method

application server

Application A

PI

unix/windows server



Application Extension Execution

Job is then monitored through completion, writing progress and status to Workload Scheduler’s job log

Fault Tolerant Agent executes the access method;it checks options file for configuration

extended agent


Access method

application server

Application A

PI

unix/windows server

method.opts

Method attaches to 3rd party application, finds job and launches it “now”



What is an Extended Agent?

An extended agent (x-agent) is a system or application that is dependent on its Fault Tolerant Agent host to receive scheduling instructions

IBM TWS accepts information from the x-agent

The Interface between IBM TWS and an x-agent is called the access method

Extended Agents and Access Methods are fully documented in the “X-Agent Programmer’s Reference”



Deployment – XA workstation definition

cpuname ORACLEdescription “Oracle E-Business Suite"os OTHERnode nulltcpaddr 39999domain MASTERDMTIMEZONE GMTfor maestrotype X-AGENT host l3orasun access MCMAGENT autolink on fullstatus off resolvedep offend

Scheduling

Language



Application Extensions – Configuration Files

Whenever an access method is launched, it reads some configuration

files which customize its execution.

Usually this files are:

options file (method.opts and XACPU_method.opts)

trace properties file (method.properties)

return code mapping configuration files (method-type.rcm and XACPU_method-type.rcm)

Some methods could read additional files.

Note: Any change to those files will affect any further access method process: a running access method will not be aware of any change made after its execution.



Configuration files customization – Option Editor

This tree showsthe list of all theexisting options files, gathered by method type

Three possibleviews:1 Simple View2 Table View3 Text View

Options Files Tree

Field Description

File View



Oracle Applications Agent

Simple Agent Creation

Co-existence

Concurrent Jobs Supported

Multiple Instances

Command Line & GUI



TWS ENGINE

Ora

clee

-Busine

ssS

uite

MC

MA

GE

NT

XA INTERFACE

MCMAGENT

SQL queries & Oracle APIs

TrackLaunch Terminate

ApplicationsDB

Oracle Concurrent Managers

Xagent for Oracle e-Business Suite components



1. TWS submits an Oracle Applications job.

2. The method inserts the request in the Oracle request queue.

3. The Oracle Applications Engine takes into account the submitted request.

4. The method monitors the job untill it’s completion.

5. The method tells TWS how the job is going.

TWS

Method

Oracle Applications Engine

2

5

3

4

1

TWS Application Extensions – Oracle XA



Software Interface

Front-end

Back-end

TWS environment Oracle environment



Oracle e-Business suite JOB entities

The identity that interacts with the system, that may have different responsibilities assigned. When running under a specific responsibility a user may access to a defined subset of an application

Application (es: GL)

Concurrent ProgramConcurrent Program


Users (es: SYSADMIN)

ResponsibilityResponsibility

ResponsibilityResponsibility

Concurrent Managers



The aggregation of definitions, data and programs that addresses one or more business topic.

Programs that manage actions related to various applications, implementing business flows. Servers waiting for events representing business requests.



XA – Standard XA Job Definition

In the General Tab you shouldput general information such asthe target extended agent cpu,login name and recovery options.

In the Task Tab you need to putthe extended agent command, as required by each specificaccess method.

You could either insert a ReturnCode Mapping expression.



TWS Oracle job Script file specification parameters:

-user Apps Login (An Oracle Apps user)

-job Job specs (Job attributes)

• Name of Applications module used to sign on.• Valid responsibility for Applications module.• Name of Application that registered job.• Job Name.

-prn Printer Options

•Printer Name•Number of copies

-vn Parameter values•n is the parameter number

Ex. -user GLOBAL -job FND ‘Application Developer’ PO POXACR -prn ps4 2 -v1 ‘abc’

Oracle Job Specification



TWS Oracle Job Definition



TWS - Oracle Job Output



TWS - Oracle Status



TWS – FrontEnd & BackEnd

FTA

Oracle

XA CPUs

\tws_home\methods\MCMAGENT \oracle_home\oa\SID_APPL\mcm\integration\lib



MCMAGENT - Oracle Applications x-agent access method.MCMLJ - submits a job to Oracle Concurrent Manager (OCM).MCMSTAT - monitors the status of the job submitted.MCMTJ - terminates the job submitted, on receiving a kill signal from TWS.

TWS – FrontEnd & BackEnd



Questions & Answers

Documents

May 9-12, 2006