Planning the HA for PeopleSoft Process Scheduler Installation and Configuration

Language:

This section contains the information you need to plan your HA for PeopleSoft process scheduler configuration.

The HA for PeopleSoft process scheduler data service uses the ORCL.PeopleSoft_process_scheduler resource type and the software is delivered as part of the ha-cluster/data-service/peoplesoft package. The resource type uses the psadmin command to start, stop, and fault monitor the specific process scheduler commands. You can use the command to verify the PeopleSoft process scheduler domain status.

Configuration Restrictions for the HA for PeopleSoft Process Scheduler

The configuration restrictions in the subsections that follow apply only to the HA for PeopleSoft process scheduler.

For restrictions that apply to all data services, see the Oracle Solaris Cluster 4.3 Release Notes.

Caution - Your data service configuration might not be supported if you do not observe these restrictions.

Multiple process scheduler instances – If multiple process scheduler instances are configured for the same Oracle Solaris database, you must configure a resource for each of the process scheduler instances.
Failover support only – PeopleSoft process scheduler can be configured only as a failover data service and not as a scalable data service.
Multiple process scheduler domains –The Oracle Solaris Cluster resource of resource type ORCL.PeopleSoft_process_scheduler can manage exactly one PeopleSoft process scheduler domain. To manage multiple PeopleSoft process scheduler domains, configure multiple Oracle Solaris Cluster resources of resource type ORCL.PeopleSoft_process_scheduler, each resource managing exactly one PeopleSoft process scheduler domain.

Configuration Requirements for the HA for PeopleSoft process scheduler

Use the requirements in this section to plan the configuration of HA for PeopleSoft process scheduler. These requirements apply to HA for PeopleSoft process scheduler only.

Information about how to install PeopleSoft Enterprise PeopleTools version 8.52 is published in the PeopleSoft PeopleTools 8.52 Install Documentation Library.

For requirements that apply to all data services, see Chapter 1, Planning for Oracle Solaris Cluster Data Services in Oracle Solaris Cluster 4.3 Data Services Planning and Administration Guide.

UNIX user and group - The UNIX user and group that are used to install, operate, and manage the PeopleSoft process scheduler domain must exist on all cluster nodes where the corresponding resource for the PeopleSoft process scheduler domain is configured to come online.
File systems - The corresponding file system resource for the domain is configured in the same resource group as the PeopleSoft process scheduler's resource domain. The file systems used to store the required binaries and data for the domain must be configured on highly available local file systems. If you choose to install the binaries on local storage, install and keep them identical on all the cluster nodes. The directory specified for Psft_Cfg_Home must reside on a highly available local file system, which needs to be accessible where the corresponding resource for the PeopleSoft process scheduler domain comes online.

If you are setting up HA for PeopleSoft process scheduler in a multi-instance configuration, the PeopleSoft process scheduler installation should be located on network attached storage (NAS) accessible to all the nodes running the server.
Environment variables - In addition to the required environment variables that are explained in thePeopleSoft Enterprise PeopleTools installation guide, you must set up the following variables before you configure the PeopleSoft process scheduler domain:
- SC_LHOSTNAME
- LD_PRELOAD_32
- LD_PRELOAD_64
Set SC_LHOSTNAME to the logical hostname under which the PeopleSoft process scheduler domain must be reachable from the web tier. For more details, refer to the libschost.so.1 (1) man page.

Set these environment variables for the profile of the user that operates the PeopleSoft process scheduler domain. Ensure that the login for the user is noninteractive. If you invoke as user root, you must see these variables displayed in the psadmin command output:
```
# su - Psft_User -c "/Psft_Home/appserv/psadmin -env"
```
Database tier dependency - If the database tier is deployed on the same global cluster, the resource for the PeopleSoft process scheduler domain must define a strong resource dependency to the resources for the database instance and database listener. This ensures that the PeopleSoft process scheduler domain will only try to start when the corresponding database is already operational. This configuration is required for a successful startup of the PeopleSoft process scheduler domain. If the Oracle database is not managed through Oracle Solaris Cluster, you can also configure the database tier dependency by using the data service delivered as part of the Oracle External Proxy resource. You can specify a resource dependency to the Oracle External Proxy resource.
Database client network connection - The database client used by the PeopleSoft process scheduler domain configuration must be configured to connect to the network address that is managed by the cluster framework for the corresponding database server.

Configuration Options for the HA for PeopleSoft process scheduler

Use the data service configurations in this section to plan the installation and configuration of HA for PeopleSoft process scheduler.

Failover Configurations

When the PeopleSoft software is installed in a traditional file system, a failover deployment requires a configuration where one failover resource group contains the PeopleSoft process scheduler resource, the logical hostname resource, and the failover storage resource. For more information, see the graphics in HA for PeopleSoft Application Server Data Service Configurations.

Multi-Instance Configurations

Multi-instance configuration is an application deployment topology where multiple instances of the same application provide an aggregation of services. This topology can be achieved independently of using a data service because you can manually start and stop the instances on the cluster nodes. When HA of such instances is required, you can enable a data service for the instances by creating multiple single-node resource groups or a few multi-master resource groups. For more information, see the graphics in HA for PeopleSoft Application Server Data Service Configurations.