Skip to Main Content
Return to Navigation

Setting Up the PeopleSoft Windows Service to Start an Application Server Domain

This section provides an overview and discusses how to:

Note: This section applies only to Microsoft Windows servers. It involves setting application server, Process Scheduler server, and search server domains to start as PeopleSoft Windows services.

Understanding Microsoft Windows Services

A Microsoft Windows service is a Microsoft-standard package that automatically starts and stops a process when you boot or shut down a Windows system. You can also start and stop Microsoft Windows services manually through the Administrative Tools - Services utility, which you can access through the Control Panel. A service uses a standard application programming interface (API) so that it can interact with the Control Panel and log messages to the standard event log.

For PeopleSoft domains, the service starts in an environment that is separate from any users who are signed in to the system (or to the server machine). If using the Windows service, administrators do not need to log on to a machine, start PSADMIN, and enter the proper commands to start a domain. In addition, if you use the PeopleSoft service, an administrator's logon session does not need to remain open while the domain runs.

If you have multiple application server domains, Process Scheduler servers, or search servers on the same machine, you can start them all by using the same service setup.

Note: The PeopleSoft service supersedes the method that is provided in the Microsoft Windows resource kit. Do not use SRVANY.EXE or AT commands to start PeopleSoft domains.

Configuring the PeopleSoft Service

The following procedure assumes that you have already installed and configured a domain on the Microsoft Windows server.

After completing this procedure, the specified PeopleSoft domains start and shut down automatically when the operating system recycles.

To set up the Microsoft Windows service:

  1. Open the System utility within the Control Panel, and make sure the following variables are set on the Environment tab in the System Variables section:




    Specify the location of the TEMP directory on the Microsoft Windows server, as in C:\TEMP.

  2. In PSADMIN utility, select Service Setup from the main menu.

  3. Select Configure a Service from the PeopleSoft Services Administration menu.

  4. Enter y to indicate that you want to change configuration values.

  5. Enter the names of the application server domains, the Process Scheduler databases, or search server domains that you want to include as part of the Microsoft Windows service.

    To add multiple values, separate each value with a comma and a space.

    For example,

    Application Server Domains=HRDOM1, HRDOM2, HRDOM3
  6. Select Install a Service from the PeopleSoft Services Administration menu.

    Note: All of the domains and databases that you specified are part of a single Windows service called PeopleSoft PS_CFG_HOME, wherePS_CFG_HOME is the location of the domain installations.

  7. Return to the Windows Control Panel, and start the Administrative Tools, Services utility.

  8. In the Services utility, scroll to find the entry that adheres to the PeopleSoft PS_CFG_HOME naming convention and access its properties.

  9. On the General tab of the service properties, select a startup type of Automatic.

    Note: The default startup mode is Manual.

  10. On the Log On tab, the Log On As setting must match theLog On As setting that's defined for the Oracle ProcMGR service, which was created when you installed Tuxedo.

    Both services should either be configured to Log On As Local System Account, or toLog On As This Account (referring to the same account).

  11. On the General tab of the service properties, click Start.

Note: If using a secure, remote PS_HOME, the user ID that starts the Oracle ProcMGR service and the PeopleSoft service must be same domain user ID and have sufficient privileges to at least read-execute the remote resources. Also, the TM_IPC_MAPDRIVER environment variable needs to be set appropriately. The PeopleSoft Windows Service must run under the same user id as the ProcMGR service because the PeopleSoft Windows service executes the PSADMIN command line options to start and stop domains.

See Understanding PS_HOME and PS_CFG_HOME.

Service Start Failure

It's possible that one or more of the domains or databases that are configured as part of the PeopleSoft service will fail to start, for reasons unrelated to the service.

The service is marked as started even if only one of its assigned domains starts. A message is written to the Windows event log for each domain, indicating whether it has started or not. If you experience problems with any domain or database, check the event log to see if it started successfully.

If all of the assigned domains and databases fail to start, the service is marked as stopped, and the following message is written to the event log:

Unable to start any of the domains configured for service service_name.

Testing the Service

To test the Microsoft Windows service, reboot the server, and make sure that the appropriate server executables are running.

For example, for the application server, use the Microsoft Windows Task Manager or the Server status option from the Domain status menu to see that the following executables are running:





Also make sure that any additional server processes that you have configured, such as PSQCKSRV.EXE, are running.

Editing the Service Configuration File

The Windows Services section of PSADMIN modifies the PSWINSRV.CFG file in the PS_CFG_HOME\appserv directory. You can edit the file directly by selecting4 (Edit a Service Configuration File) from the PeopleSoft Services Administration menu. This opens the PSWINSRV.CFG file in a text editor, where you can enter and save your changes.

The following sections describe each parameter.

Service Start Delay

When a domain resides on the same machine as the database server, consider using the Service Start Delay setting. By using this feature, you can avoid the situation where the database server is booting and is not ready to process requests at the time that the service attempts to boot the domain. In this scenario, without a delay set, the connection fails.

You can configure a Service Start Delay parameter that specifies a delay, in seconds, that elapses before a service attempts to start any domains. This allows the RDBMS enough time to boot and become available to accept requests.

The default is 60 seconds.

Application Server Domains

Specify the names of the domains that you want to start automatically when you boot the application server machine.

If you specify multiple domains, separate each domain with a comma and a space.

Process Scheduler Databases

Enter the databases with which a Process Scheduler server is associated. For each database that you specify, the associated Process Scheduler server starts when you boot the Microsoft Windows server.

If you specify multiple databases, separate each database with a comma and a space.

Search Server Domains

Specify the names of the domains that you want to start automatically when you boot the search server machine.

If you specify multiple domains, separate each domain with a comma and a space.