Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for Oracle PeopleSoft Enterprise Guide Oracle Solaris Cluster 4.1 |
1. Getting Started with Oracle Solaris Cluster HA for PeopleSoft Enterprise
2. Installing and Configuring the HA for PeopleSoft Application Server
3. Installing and Configuring the HA for PeopleSoft Process Scheduler
Planning the HA for PeopleSoft Process Scheduler Installation and Configuration
Configuration Restrictions for the HA for PeopleSoft Process Scheduler
Configuration Requirements for the HA for PeopleSoft process scheduler
Configuration Options for the HA for PeopleSoft process scheduler
Installing and Configuring the PeopleSoft Process Scheduler Domain
How to Enable the PeopleSoft Process Scheduler Domain to Run in a Cluster
How to Install PeopleSoft Process Scheduler Software
Verifying Installation and Configuration of the PeopleSoft Process Scheduler Domain
How to Verify the PeopleSoft Process Scheduler Domain Installation and Configuration
Registering and Configuring HA for PeopleSoft Process Scheduler
How to Register and Configure HA for PeopleSoft Process Scheduler for Failover
How to Remove a PeopleSoft Process Scheduler Domain From a Failover Resource Group
Verifying Installation and Configuration of the PeopleSoft Process Scheduler Domain Resource
How to Verify PeopleSoft Process Scheduler Domain Resource Installation and Configuration
Tuning the HA for PeopleSoft Process Scheduler Fault Monitor
Probing Algorithm and Functionality
Operations of the PeopleSoft Process Scheduler Probe
Debugging the HA for PeopleSoft Process Scheduler Fault Monitor
How to Activate Debugging for HA for PeopleSoft Process Scheduler
A. HA for PeopleSoft Application Server Extension Properties
The HA for PeopleSoft process scheduler has an extension property named debug_level. This extension property enables you to activate debugging for PeopleSoft process scheduler guest-domain resources.
Perform this procedure to activate debugging.
Note - To deactivate debugging, repeat all steps in this procedure with the following changes:
Change daemon.debug to daemon.notice.
Change the debug_level property to 0.
# grep daemon /etc/syslog.conf *.err;kern.debug;daemon.notice;mail.crit /var/adm/messages *.alert;kern.err;daemon.err operator #
If debugging is active, daemon.debug is set in the file /etc/syslog.conf. You do not need to continue this procedure.
If debugging is inactive, daemon.notice is set in the file /etc/syslog.conf of the appropriate node. Perform the remaining steps in this procedure to activate debugging.
# grep daemon /etc/syslog.conf *.err;kern.debug;daemon.debug;mail.crit /var/adm/messages *.alert;kern.err;daemon.err operator #
# svcadm refresh svc:/system/system-log:default
# clresource set -p debug_level=2 psft-sched-rs