Tivoli Workload Scheduler for Applications

Tivoli Workload Scheduler for Applications
PeopleSoft Integration
Marco Borgianni
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Agenda
 Introduction
 XA & TWS for Applications
 Architecture
 Installation
 Configuration
 Scheduling & Monitoring
 Demo
2
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Tivoli Workload Scheduler for Applications – XA
 TWS for Applications extends the concept of jobs into other scheduling
spaces inside Enterprise Resource Planning architectures.
 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
External
System1
WebUI
FTA
Extended
Agent
CPUs
External
System2
X-AGENT
3
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
XA v.s. TWS for Apps
 eXtended Agents (or XA) is a generic protocol provided by TWS
distributed to allow the extension of the concept of job to other domains.
 TWS for Applications is a product made of a set of eXtended Agents that
are in particular demand: SAP, PeopleSoft, Oracle, MVS, TWSz, CA7
 There are other XA in the field, especially to connect to other Tivoli/IBM
products: unixssh (agentless), internetwork dependencies, TSM, VDC.
ERP
SAP, Oracle,
PeopleSoft
Capabilitie
s
XA
XA
Tandem,
netmeth
TWS
Platforms
unixssh,
JES, MVS
4
XA
XA Integration
s
TSM, IGT,
LoadLeveler
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
TWS for Applications: Specific Extensions
 SAP R/3 and Business Warehouse
 PeopleSoft
 Oracle e-Business Suite
 Tandem Netbatch (Business Partner Offering only)
TWS for Application provides two types of benefits
 An advanced job executor and sensor in the specialized domain
– SAP concepts
– Oracle concepts, etc.
 A member of the Tivoli Workload Automation family participating to the extensions
– Event mechanism
– Report mechanism
– Dependency definition
5
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Other eXtended Agents: the default TWS set
 A set of XA coming with the TWS distributed product. This set can
increase with each release.
 Unixlocl: a toy script-based XA, provides a nice way to make load
failover at Master or DM level.
 Unixssh: the agentless XA, useful to avoid agent installation, and
with a very interesting price point.
 Netmeth: the internetwork dependency XA, needed to implement
the relative product feature.
 Tsmxagent: integration with TSM to be able to submit and track
loads in a TSM network and drive backups automatically
6
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Other offerings around eXtended Agents
An XA provided by external partners available through separate offering
 Tandem netbatch: an XA to submit and track load on the Tandem
platform. Provided by a Business Partner.
An XA provided by IBM for additional functions
 TWS2TWS: an XA to submit and track load on another TWS
Distributed, from Distributed or E2E
7
© 2012 IBM Corporation
Tivoli Workload Scheduler for Applications
Architecture
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
SSM
TWS Core
JDBC
SSM TWS Core
TWS XA
WebSphere
ISC
TWS FTA
JSC
psagent
Component Interface
TWS Master
Browser
Tivoli Workload Scheduler for Applications Architecture
DB
9
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Supported PeopleSoft environments
 PeopleTools 8.44 and later
Earlier versions of PeopleTools are supported by TWS for Apps 8.2.x
only
10
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Architecture / Design – PeoplSoft
Typical PeopleSoft Scenario
TUXEDO/Jolt
Transaction/authentication manager
TUXEDO CONN.
APPLICATION
SERVER
ODBC
Open
standard application programming
interface (API) for accessing a
database.
ODBC CONN.
ODBC CONN.
CLIENT
Other servers:
DB SERVER
ODBC CONN.
 File Server
 Report Server
 Web Server
 ...
11
PeopleSoft
Environment
BATCH SERVER
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
PS Architecture – Application Server
PeopleSoft
Web
Server
xagent
Jolt
Jolt
Application Server
PSAPPSRV PSSAMSRV PSQCKSRV PSQRYSRV
SQL
Server Processes
SQL
SQL
Database
12
© 2012 IBM Corporation
Installation
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Installation –
To install you can use any of the following procedures.



The launchpad
The ISMP silent installation
The Tivoli Software Distribution, version 4.1 product or the Software Distribution
component of Tivoli Configuration Manager, version 4.2 or later

14
On UNIX Operating Systems, the twsappsinst command.
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Installation – PSJOA.jar
Before installing you need to have the file:
“psjoa.jar”
You can copy it from the PeopleSoft Application Server, it’s
located in the the directory:
“<PS_HOME>/class/”
The Application Server where you take the psjoa.jar file and the
Application Server the PeopleSoft access method connects to,
must be at the same version. For example, the PeopleSoft
access method will fail to connect to a server 8.45.09 using a
psjoa.jar file taken from a server at level 8.45.11.
The Application Server OS need not match the PeopleSoft
xagent OS. For example the PeopleSoft xagent on Linux can
use a psjoa.jar taken from a Windows Application Server.
Note: Don’t copy the psjoa.jar file into a directory whose name
contains special characters (e.g. “!”), otherwise the PeopleSoft
access method will fail.
15
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Installation – Installed files
After installing you’ll find the following files (among the other ones):
TWS_HOME\methods\psagent(.exe)
TWS_HOME\methods\pwdcrypt(.cmd)
TWS_HOME\methods\psjars\tws4ps.jar
TWS_HOME\methods\psjars\jffdc.jar
TWS_HOME\methods\psjars\jlog.jar
...
16
© 2012 IBM Corporation
Configuration
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Configuration – access method files
CPU1 CPU2
FTA
PSAGENT
18
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Configuration – access method options
Here follows the list of options*:
- PSFT_OPERATOR_ID
- PSFT_OPERATOR_PWD
- SERVER_NAME_LIST
- RUNLOCATION
- PSJOAPATH
- TWS_RETRY
- TWS_MAX_WAIT_TIME
- TWS_MIN_WAIT_TIME
- CHECKINTERVAL
- LJUSER
- PS_DISTSTATUS
- TWSXA_INLINE_CI
- TWSA_SCHED_METH
* Mandatory options in bold. Options new in TWS for Apps 8.3 and later in blue
19
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Configuration – Option Editor
Options files can be created and managed as in previous
releases both with the Option Editor and manually.
The Option Editor has been modified to fully manage the new
options of the PeopleSoft access method.
20
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Configuration – PeopleSoft project 1/3
21
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Configuration – PeopleSoft project 2/3
22
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Configuration – PeopleSoft project 3/3
23
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
PeopleSoft xAgent - Definition
24
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
PeopleSoft Jobs - Definition
25
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
PeopleSoft Jobs - Properties
26
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
PeopleSoft Jobs - Properties
27
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Job Status Mapping
You can have the access method ignore the distribution status
setting the PS_DISTSTATUS option to 0.
Note: If Tivoli Workload Scheduler fails to retrieve the status
of the PeopleSoft job, the Tivoli Workload Scheduler job status is:
UNDECIDED
28
© 2012 IBM Corporation
Schedule & Monitoring
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Typical Agent Processing
batchman
jobman
JOBMAN
JOBMAN
JOBMAN
JOBMAN
psagent.opts
(global and local)
method
jobmanrc
psagent.exe
Script or Command
30
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
PeopleSoft Process Scheduler Jobs

The PeopleSoft process scheduler uses entries in the Process Request table
(PSPRCRQST) to drive its work decisions.

These entries describe the processes which the Process Scheduler server agent
will launch. They also contain the information required to determine the status of
the process.

The access method for PeopleSoft can insert entries, inquire against the
contents and modify the status information within this table (PSPRCRQST).

When documenting a PeopleSoft job in Tivoli Workload Scheduler, the user is
actually defining a process request to be inserted in the Process Request table
(PSPRCRQST).

A process request from Tivoli Workload Scheduler must contain three valid
pieces of data:
1) Process Type 2) Process Name 3) Run Control ID
31
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Scheduling Path
TWS
Method
PROCESSREQUEST CI
PSPRCRQST
Process Scheduler
32
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Monitor on TWS
33
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Monitor on PeopleSoft
34
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
DEMO - Scenario
3
1
WebUI
TWS
PeopleSoft
Extended
Agent
CPUs
X-AGENT
2
4
35
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
Questions & Answer
36
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
37
© 2012 IBM Corporation
Tivoli Workload Automation – PeopleSoft Integration
IBM Tivoli Lab
Briefing Center - Building 2, Floor 6
Via Sciangai 53
00144 Rome, Italy
Briefing Center Phone:+39.06.596.62436
38
© 2012 IBM Corporation