Professional Documents
Culture Documents
Architecture Overview
Application
Server(s)
11g DB/
11g RAC
Integration
Broker
Web Client
Web Server
Cluster
http(s)
Jolt
PeopleSoft
Application
Database
Tuxedo
Portal
Process
Scheduler
Application
Developer
LDAP Directory
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)
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
Hardware Load
balancers for Clustered
Web Servers
Extranet
(DMZ)
Web Servers
(Oracle Application
Server/BEA WebLogic
Server)
BEA Tuxedo Servers
PeopleSoft Application
Servers
Intranet
RAC Cluster
Oracle
Database
Storage
Real Application
Clusters (RAC)
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
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//
(psserver=appserver_host1:9000#3,appserver_host2:9010#1)
In the above scenario
Monitoring Options
search.oracle.com
http://www.oracle.com
https://www.peoplesoft.com/corp/en/login.jsp (Retiring
Nov 7)
http://metalink3.oracle.com
QUESTIONS
ANSWERS