PeopleSoft on RAC SIG

<Insert Picture Here>

PeopleSoft on Oracle Real Application Clusters Pat Bangalore PMPConsulting Technical ManagerOracle Consulting

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

© 2008 Oracle Corporation – Proprietary and Confidential


PeopleSoft on RAC Agenda• Overview of PeopleSoft Architecture on RAC• Infrastructure Deployment Options• Database Specific changes for RAC• High Availability and Failover• Workload Distribution• PeopleSoft Monitoring for RAC• PeopleSoft Platform Support for RAC• FAQ - PeopleSoft on RAC


Architecture Overview

Process Scheduler

Application Server(s)

PeopleSoftApplication Database

Web Server Cluster

Jolthttp(s)

Application Developer

Web Client

Tuxedo

11g DB/ 11g RAC

Portal

LDAP Directory

Integration Broker


What’s RAC for PeopleSoft?

• Multiple instances of Oracle running on many nodes• All instances share a single physical database• All instances have common data, control, and

initialization files• Each instances has its own thread of online redo logs

and undo tablespaces• All instances can simultaneously execute transactions

against the single database• The Caches are synchronized using Oracle’s Global

Cache Management technology (Cache Fusion)

Hardware setup for PeopleSoft on RAC


Logical Architecture on RAC



Deployment Options


Infrastructure Options• RAC Instance and PeopleSoft Batch server on the same server,

Application Server on a separate host (Connecting to Global Database name)

• RAC Instance and PeopleSoft Batch server on a separate server,Application Server on a separate host (Connecting to Global Database name)

• PeopleSoft batch server on the same server or on a separate server, Application server on a separate Host (Connecting to the local Instance name of the RAC node)

• Use of a Hardware based Load Balancer

Architecture Configurations

• Dedicated host for RAC Instance, Batch server and Application Server

• PeopleSoft Connects to a Global Database name

• Clustered Web Severs through Load Balancer

• Multiple Process Schedulers for Batch processing

• Multiple Application servers being load balanced


-Continued• Application server installed on RAC members use cluster

member IP address (PS_MACH)

• Transparent Application Failover (TAF) for RAC

• Use Master Scheduler to enable Load Balancing of Work Load for PeopleSoft Batch job Requests

• Jolt Failover and Weighted Load Balancing for App Server


Ideal PeopleSoft on RAC Architecture


Extranet(DMZ)

Intranet

Internet

Web Servers(Oracle Application

Server/BEA WebLogic Server)

Hardware Load balancers for Clustered Web Servers

PeopleSoft ApplicationServers

BEA Tuxedo Servers

Storage

USERS

Real ApplicationClusters (RAC)

RAC Cluster

OracleDatabase


Database Specifics for RAC


PeopleSoft Database Specifics for RAC


1. Use Oracle’s Database assistant (DBCA) to create RAC database or create database manually by editing the delivered PeopleSoft supplied scripts

2. It is not recommended to use PeopleSoft Database Configuration Wizard for RAC

3. Use Raw devices for Oracle control and data files or Oracle’s ASM storage or OCFS (Oracle’s cluster file system) unless a O.S cluster file system is supported by the cluster software.

4. Install RAC version of the Oracle Database

PeopleSoft Scripts to edit for RAC


Edit the following delivered scripts appropriate file system/ASM storage

• Createdb10.sql (Use DBCA)• Utlspace.sql• XXddl.sql Application specific tablespace scripts)

example hcddl.sql for HCM • Create an ORACLE_SID=RAC1 - Initialization file

for each instance

Create Initialization files for each Oracle Instance (ORCL1,ORCL2)


Oracle initialization file for first Oracle Instance where ORACLE_SID=orcl1:

• Initorcl1.ora (Instance specific)• Init.ora (Common file)Oracle initialization file for second Oracle Instance

where ORACLE_SID=orcl2:• Initorcl2.ora (Instance specific)• Init.ora (common file)

Configure Database Security


Modify the PSDBOWNER Table to reflect the number of RAC nodes.

There must be an entry in the PSDBOWNER table for each Oracle instance

Make sure this table contains entries to the multiple DBNAMES and Owner IDs; for instance:DBNAMES Owner ID-------------- -------------ORCL1 SYSADMORCL2 SYSADMORCL SYSADM

PeopleSoft Kernel Sizing


• Resize OS Kernel - If Process Scheduler or Application server is installed on the cluster members of RAC then set O.S kernel parameters in addition to the minimum required kernel changes for Oracle RAC Database

• Adjust Semaphores ,Message queues and Shared Memory according to number of PeopleSoft processes started and size of your domain


High Availability and Failover Options


Failover Options

• Connect Time Failover – When a PeopleSoft application loses its connection to the database, it will retry and connect to the other Oracle instance based on the alternate IP address specified in tnsnames.ora

• (Multiple listeners or IP address pointing to a Database service name)

• No reference to Global database name of PeopleSoft

• Failure that occurs while initiating a connection to the Database


Failover Options

• Transparent Application Failover (TAF)

• Failure occurs after a successful PeopleSoft connection has already been established, and subsequently the connection gets terminated.

• Can be used with multiple nodes or with primary/secondary instance configurations

• Is designed for RAC but can be used for:• Replicated systems• Data Guard• Single Instance


TAF Configuration in PeopleSoft

HRPRD =(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = vip1)(PORT = 1521))(ADDRESS = (PROTOCOL = TCP)(HOST = vip2)(PORT = 1521))(FAILOVER = yes) (LOAD_BALANCE = yes)(CONNECT_DATA =

(SERVER = DEDICATED)(SERVICE_NAME = HRPRD)(FAILOVER_MODE =

(TYPE = SELECT)(METHOD = BASIC)(RETRIES=180)(DELAY =5)

))

)


Failover mode options

• Add failover options manually to TNS configuration files.• These options are part of the CONNECT_DATA section of a

connect descriptor.• Failover options include:

• TYPE: Identifies the nature of TAF, if any• METHOD: Configures how quickly failover can occur• BACKUP: Identifies an alternative net service name• RETRIES: Limits the number of times that a reconnection is

attempted• DELAY: Specifies how long to wait between reconnection

attempts


Failover Methods

• Determine how quickly connections become available following a failover.

• BASIC: • Connect to failover instance upon failure.

• PRECONNECT: • Keep active connections to both instances

//sample//(CONNECT_DATA =

(SERVER = DEDICATED)(FAILOVER_MODE = (TYPE = SELECT)

(METHOD=PRECONNECT)))//sample//


What TAF does for PeopleSoft?

• Reconnect to the backup Instance/Alternate node

• Re-establish the PeopleSoft session (Stateful Transactions)

• Resume the SELECT statement in progress

• User Login is preserved

• Automatic re-Initiation of AE jobs based on “Restartable” parameter


What TAF does NOT do for PeopleSoft?

• Transactional Web pages may see an error if the connection is made to the failed node during retries.

• Cobol and complex SQR jobs with multiple updates/Commits may have to be restarted/reinitiated

• While Saving or Editing data in a component, you may see interruptions during node and transaction failover


So What’s the Bottom Line on Failover?

• TAF is still the solution for Transaction Failover

• Error message could be minimized by adjusting “Allow consec service failure”

• “Recycle count parameter” can be adjusted to release the memory foot print on the failed node

• Some customers have leveraged “Bolt-on” scripts to trap PeopleSoft error messages during failover as a work around

• Enhanced Retry Failover logic is planned in future release of Peopletools



PeopleSoft Work Load Distribution


Application Server Load balancing

• Load Balancing is managed within a Domain by BEA Tuxedo• Requests are handled by idle server processes• Predefined algorithm for load distribution

• Load is balanced between domains via the psserver property in PIA config file for its Application servers

• Enhanced Load balancing is available with Jolt Weight based load balancing

(psserver=appserver_host1:9000#3,appserver_host2:9010#1)

• In the above scenarioAppserver_host1 would receive 3 times more requests than

appserver2_host2


Batch Server Load Balancing

• Master Scheduler in PeopleSoft does Load Balancing of Work load by automatically routing requests to the available Process scheduler

• PeopleSoft batch servers are connected to global database name and not to individual cluster members of RAC

• The Batch servers would use TAF entries for connecting to RAC nodes.

• Queued Job requests can be failed over to the available scheduler based on TAF entries



Monitoring Options


Oracle Enterprise Manager

• Enterprise Manager is the Oracle System Management solution

• The PeopleSoft Enterprise Management Plug-In is an extension of Enterprise Manager

• Minimum version of Enterprise Manager supported is 10.2.0.2

OEM with PeopleSoft Architecture


OEM Plug-in for PeopleSoft


• PS Application Server Domain• PS Process Scheduler Domain• PS Search Server Domain• PS PIA • PS Web Site• PS App DB

PeopleSoft OEM Dashboard



PeopleSoft Support for RAC


PeopleSoft Support for RAC


PeopleSoft on RAC References• Oracle® Real Application Clusters Installation and

Configuration Guide for step by step installation of CRS and RAC

• PeopleSoft installation guide (Customer Connection)• PeopleSoft Red Paper on High Availability

onhttp://www.peoplesoft.com/corp/en/doc_archive/red_paper/tools_oracle9i_real_app.jsp

• People books-http://www.oracle.com/technology/documentation/psftent.html

• Customer Connection –http://www.peoplesoft.com/corp/en/public_index.jsp


http://download-west.oracle.com/docs/html/B10766_01/toc.htm

http://download-west.oracle.com/docs/html/B10766_01/toc.htm

http://www.peoplesoft.com/corp/en/doc_archive/red_paper/tools_oracle9i_real_app.jsp

http://www.peoplesoft.com/corp/en/doc_archive/red_paper/tools_oracle9i_real_app.jsp

http://www.oracle.com/technology/documentation/psftent.html

http://www.peoplesoft.com/corp/en/public_index.jsp

PeopleSoft on RAC FAQ’s• Which versions of Oracle are currently

supported?Oracle 9i (Versions 9.2.0.2.x and higher)

• Which PeopleSoft versions are supported?PeopleSoft 8 applications running on PT8.42 tools or higher. Which OS Platforms are currently supported?HP Tru 64 5.1HP UX11i IBM AIX 5.1MS Windows 2000Sun Solaris 8Oracle Enterprise Linux, Red Hat Linux & Suse Enterprise Linux


“The single point of failure in our PeopleSoft Infrastructure was the Database and that has been a myth ever since we moved to RAC”

“Our goal is to obtain 99.99% availability for our campus solutions during Student enrollment and RAC for PeopleSoft is the way to go for our Application”

“We have decreased our unplanned downtime with RAC and the application is more scalable and flexible from all tiers of PeopleSoft Architecture”

What Customers are Saying


For More Information

search.oracle.com

http://www.oracle.comhttps://www.peoplesoft.com/corp/en/login.jsp (Retiring

Nov 7)http://metalink3.oracle.com




Q U E S T I O N SA N S W E R S

Documents

PeopleSoft on RAC SIG