Using PSADMIN Menus

This chapter discusses how to:

Use the Application Server Administration menu.
Use the Process Scheduler menu.
Set up the PeopleSoft Windows service.

Using the Application Server Administration Menu

This section discusses how to:

Access the application server options.
Administer a domain.
Boot a domain.
Shut down a domain.
Perform a normal shutdown.
Perform a forced shutdown.
Check the domain status.
Purge the domain cache.
Configure a domain.
Edit configuration and log files.
Create a domain.
Delete a domain.

Accessing the Application Server Options

To access the menu options for configuring and administering an application server, select Application Server from the PeopleSoft Server Administration (PSADMIN) menu.

The PeopleSoft Application Server Administration menu appears.

The menu options and parameters within the Create a domain and Delete a domain menus are straightforward, one-time tasks (per domain). The Administer a domain menu offers numerous configuration, administration, and logging parameters that you may access frequently.

Administering a Domain

To administer a domain, you must have already created a domain. After you have created a domain, specify environment-specific settings for the application server to function correctly with your system. The following sections describe all of the menus and menu options that you use to administer and configure an application server domain.

To administer a domain:

Select Administer a domain from the PeopleSoft Application Server Administration menu.
In the Select domain number to administer command line, enter the number that corresponds to the previously created domain that you want to administer that appears in the BEA Tuxedo domain list.
Select the option that you want to perform from the PeopleSoft Domain Administration menu.

PSADMIN transparently sets several environment variables before invoking any Tuxedo administrative commands. You don't need to set these variables manually. These environment variables are:

TUXCONFIG = PS_HOME/appserv/domain_name/PSTUXCFG
APPDIR = PS_HOME/appserv/domain_name
PATH = TUXDIR/bin; PS_HOME/bin/server/winx86; PATH
APP_PW = Application Password (initialize)

The following sections describe each option that appears in the PeopleSoft Domain Administration menu

Booting a Domain

This boots the BEA Tuxedo domain (the application server) by using the tmboot command. This command will start all of the server processes that have been configured for your domain.

Shutting Down a Domain

The PeopleSoft Domain Shutdown menu offers two options: a normal shutdown and a forced shutdown.

-------------------------------
PeopleSoft Domain Shutdown Menu
-------------------------------
   Domain Name: ps800dmo

 1) Normal shutdown
 2) Forced shutdown
 q) Quit

Command to execute (1-2, q) [q]:

Performing a Normal Shutdown

A normal shutdown is a quiescent shutdown that waits for users to complete their tasks and turns away new requests before terminating all of the processes in the domain.

Performing a Forced Shutdown

A forced shutdown is a nonquiescent shutdown that immediately terminates all of the processes in the domain. Normally, you use the forced shutdown only when a Bulletin Board Liaison (BBL) process encounters errors and cannot be shut down by using a normal shutdown.

Note. The BBL is a primary BEA Tuxedo process that controls the domain.

Checking the Domain Status

Use the PeopleSoft Domain Status menu to view the status of the server, queues, or clients connected to the domain.

-----------------------------
PeopleSoft Domain Status Menu
-----------------------------
   Domain Name: ps800dmo

 1) Server status
 2) Client status
 3) Queue status
 q) Quit

Command to execute (1-3, q) [q]:

Server Status

Select Server status to invoke the BEA Tuxedo tmadmin psr subcommand (print server processes), which displays the BEA Tuxedo processes and PeopleSoft server processes that are currently running. For example:

Prog Name Queue Name Grp Name ID RqDone Load Done Current Service --------- ---------- -------- -- ------ --------- --------------- BBL.exe 43054 MJOHNST+ 0 10 500 ( IDLE ) PSMONITORSRV.e MONITOR MONITOR 1 0 0 ( IDLE ) PSAPPSRV.exe APPQ APPSRV 1 0 0 ( IDLE ) PSWATCHSRV.exe WATCH WATCH 1 0 0 ( IDLE ) PSAPPSRV.exe APPQ APPSRV 2 8 400 PortalRegistry PSPPMSRV.exe PPMQ2 PPMGRP 100 0 0 ( IDLE ) PSSAMSRV.exe SAMQ APPSRV 100 0 0 ( IDLE ) PSRENSRV.exe RENQ1 RENGRP 101 0 0 ( IDLE ) WSL.exe 00001.00020 BASE 20 0 0 ( IDLE ) JSL.exe 00095.00200 JSLGRP 200 0 0 ( IDLE ) JREPSVR.exe 00094.00250 JREPGRP 250 6 300 ( IDLE )

The number of items appearing depends on the number of server processes that you have configured.

Client Status

Select Client status to invoke the BEA Tuxedo tmadmin pclt subcommand (printclient), which displays connected users. For example:

LMID User Name Client Name Time Status Bgn/Cmmt/Abrt --------------- --------------- --------------- -------- ------- ------------- MJOHNST2040403 NT WSH 0:03:56 IDLE 0/0/0 MJOHNST2040403 NT JSH 0:03:55 IDLE 0/0/0 MJOHNST2040403 PTWEBSERVER MJOHNST2040403 0:01:25 IDLE/W 0/0/0 MJOHNST2040403 QEDMO mjohnst2032202+ 0:01:09 IDLE/W 0/0/0 MJOHNST2040403 NT tmadmin 0:03:54 IDLE 0/0/0

Queue Status

Examining the status of the individual queues for each server process provides valuable tuning information. Check the queues by using the Queue status option. In the following example, the results of the Queue status option show the individual server processes, the associated queue, the number of server processes currently running, and the number of requests waiting to be processed:

Prog Name Queue Name # Serve Wk Queued # Queued Ave. Len Machine --------- ------------------- --------- -------- -------- ------- JSL.exe 00095.00200 1 - 0 - MJOHNST20+ JREPSVR.exe 00094.00250 1 - 0 - MJOHNST20+ PSMONITORSRV.e MONITOR 1 - 0 - MJOHNST20+ PSSAMSRV.exe SAMQ 1 - 0 - MJOHNST20+ BBL.exe 43054 1 - 0 - MJOHNST20+ PSWATCHSRV.exe WATCH 1 - 0 - MJOHNST20+ PSPPMSRV.exe PPMQ2 1 - 0 - MJOHNST20+ WSL.exe 00001.00020 1 - 0 - MJOHNST20+ PSRENSRV.exe RENQ1 1 - 0 - MJOHNST20+ PSAPPSRV.exe APPQ 2 - 1 - MJOHNST20+

The results alert you to any bottlenecks that may be occurring on your application server. With this information, you can make more informed performance decisions. For instance, if the bottlenecks appear to be persistent, it may indicate that you need to add more instances of a particular server process, such as PSAPPSRV for example. Or the results may indicate that you need to start either a PSQCKSRV or a PSQRYSRV.

Purging the Domain Cache

A proven technique for resolving problem application server environments is to purge the application server domain cache located in PS_HOME\appserv\domain_name\CACHE.

Important! You should purge the cache only after due consideration, and in consultation with PeopleSoft.

Please keep the following in mind:

You can purge only non-shared cache.
You can purge the cache regardless of whether the application server domain is running; there's no need to shut it down and reboot. However, the procedure is less disruptive and runs more quickly if the domain is shut down or its activity level is low.
Purging the cache can take five minutes or more on a large or busy domain, depending on the domain configuration.

To purge the domain cache:

On the PeopleSoft Domain Administration menu, select Purge Cache.

If the cache is currently empty, the purge operation is cancelled, and the PeopleSoft Domain Administration menu reappears.

If the cache is not empty, the following prompt appears:
```
Enter log comments about this purge, if any (maximum 256 characters):
```
Enter any information (up to 256 characters) that you want recorded explaining the circumstances of this cache purge operation, and press Enter. Your comments will be saved to a purge log file.

The following prompt appears:
```
Do you wish to archive the contents of the current cache? (y/n) [n] :
```
Enter y to archive the cache contents, or n to delete them permanently. The default response is n.

If you enter y, the following prompt appears:
```
Cache contents will be archived to
 PS_HOME\appserv\domain_name\Archive\CACHE_mmddyy_hhmm_ss.
Hit Enter to continue or provide a new location:
```
Note. At runtime, PS_HOME and domain_name are replaced with values appropriate to your system, and mmddyy_hhmm_ss represents the date and time of the cache purge operation.
(If you chose to archive the cache contents) Enter a different archive location if desired, and press Enter.

If the location you enter is rejected, the following message appears, and you're prompted to continue:
```
Failed to archive cache to location.
```
Note. Continuing this procedure with an invalid location will purge the cache without archiving.

The default location is a unique directory name. Keep in mind that the location you enter might have been rejected for the following reasons:
- The directory can't be created due to an invalid drive or network mount.
- The directory can't be created due to insufficient user privileges.
- The directory has insufficient space for the cache files.
When prompted to continue, enter y to continue the purge operation, or n to cancel the operation and return to the PeopleSoft Domain Administration menu.

Note. Archiving the cache increases the time required to complete the purge, because the cache files must be copied to the archive location.

If the application server domain is running, you might see messages such as the following, which are normal and don't require any action:

INFO: BEA Tuxedo, Version 8.1, 32-bit, Patch Level 118 INFO: Serial #: 650522264137-1048416937507, Expiration NONE, Maxusers 1000000 INFO: Licensed to: PeopleSoft - ISV

When the cache is successfully purged, the following message appears:

Purge Cache operation completed successfully. You may notice that the cache directory is non-empty. Cache files have been invalidated and will be refreshed from the database.

If the cache was archived, you'll also see the following:

You may also have noticed a number of Sharing Violation messages during the Cache Purge. These messages are no cause for alarm and are expected as part of the cache archival.

If the application server domain is running, an entry is written to the application server log file to indicate that the cache has been purged.

The purge log file is saved (including any comments you entered in step 2) as PS_HOME\appserv\domain_name\LOGS\PurgeCache_mmddyy_hhmm_ss.log.

Note. At runtime, PS_HOME and domain_name are replaced with values appropriate to your system, and mmddyy_hhmm_ss represents the date and time of the cache purge operation.

Following is an example of the purge log file contents:

Date:02/17/05 11:47 User Explanation: Processes appeared to take a long time to recycle. Cache Contents archived to C:\ptdvl\appserv\Q846RET\Archive\CACHE_021705_1147_01

Configuring a Domain

This option prompts you with a model configuration file to gather such parameters as port numbers, the number of various server processes that are needed, encryption enabling, and so forth. PSADMIN then invokes a subprogram, UBBGEN, which takes the configuration parameters, builds the file PS_HOME/appserv/domain-name/psappsrv.ubb, and carries out the tmloadcf - y psappsrv.ubb command to generate the following binary file: PS_HOME/appserv/domain-name/pstuxcfg.

The following topics describe all of the parameters that you encounter while configuring an application server. Either read this section before you fine tune the configuration of your application server or have it available while you are doing it.

To configure a domain:

Select Configure this domain from the PeopleSoft Domain Administration menu.

Enter n (No), if you do not want to continue. This returns you to the previous menu. Otherwise, enter y (Yes).
When prompted to change configuration values, enter y.

If you don't need to change any of the values, enter n. By doing so, you create a new configuration file with the same values that were previously specified. Enter n, or elect not to modify the PSADMIN parameters, if:
- You have changed only the location of TUXDIR.
- You would rather edit the PSAPPSRV.CFG file manually.
- You installed a new BEA Tuxedo patch.

Editing Configuration and Log Files

Use the Edit Configuration/Log Files menu to view the application server and BEA Tuxedo log files. You can also manually edit the PSAPPSRV.CFG file if you do not want to use the PSADMIN interface.

To have PSADMIN start your text editor (such as Notepad or KEDIT) so that you can manually edit or view application server configuration and log files, you must specify the text editor in the environment settings. For example, to use KEDIT, the editor environment setting should look like this:

set EDITOR=c:\apps\kedit\keditw32.exe

To use Notepad, it should look like this:

set EDITOR=c:\Windows\Notepad.exe

Note. You can view and edit a domain's PSAPPSRV.CFG file while the domain is running, but the changes that you specify do not take effect until the next time you reconfigure the domain.

For the following options, you must enter your operator ID to view and edit the files:

Edit PSAPPSRV.tracesql (PSAPPSRV SQL trace file)
Edit PSSAMSRV.tracesql (PSSAMSRV SQL trace file)

For example:

Command to execute (1-7, q) [q]: 5
Enter the operator ID : PTXYZ

Note. PeopleSoft secures the Structured Query Language (SQL) traces because, in some instances, the SQL that is traced may involve sensitive information.

Edit PSAPPSRV.CFG

The PSAPPSRV.CFG file contains all of the configuration settings for an application server domain. The PSADMIN interface provides prompts so that you can edit and modify this file within a structured format. In many cases, and perhaps due to personal preference, you may opt to edit the PSAPPSRV.CFG file manually. When editing this configuration file manually, note that it is similar to editing an INI file, because all of the parameters are grouped in sections.

Edit APPSRV.LOG

This log file contains PeopleTools specific logging information.

Edit TUXLOG

The TUXLOG file enables you to trace the BEA Tuxedo component for troubleshooting information.

Edit PSAPPSRV.tracesql

You can specifically trace the activity of the PSAPPSRV server process by setting the PSAPPSRV.tracesql option.

Edit PSSAMSRV.tracesql

You can specifically trace the activity of the PSSAMSRV server process by setting the PSSAMSRV.tracesql option.

Creating a Domain

Use the Create a domain option to create a subdirectory under PS_HOME/appserv by using the domain name that the user specifies and to copy model files to that directory.

To create an application server domain:

Select Create a domain from the PeopleSoft Application Server Administration menu.
Enter the name of the domain that you want to create; the name must not exceed 8 characters.
Select a configuration template from the Configuration template list.

The configuration templates are preconfigured sets of application server processes.

Note. If you are responsible for routinely creating many domains, you may want to either modify the CFX files to reflect your environment or create your own. You can manually edit any CFX file in the PS_HOME\appserv directory with any text editor, such as Notepad. To create your own CFX files, just save the CFX file to a new name after modifying the template values. The next time PSADMIN prompts you for a configuration template to create a domain, your new CFX file appears in the configuration templates list.

Deleting a Domain

Use the Delete a domain option to shut down the domain, if running, and delete the domain's subdirectory.

Note. Before you delete a domain, make sure that it is not running.

To delete a domain:

Select Delete a domain from the PeopleSoft Application Server Administration menu.
From the BEA Tuxedo domain list, select the number that corresponds to the domain that you want to delete.
When prompted to continue, enter y and press Enter.

Using the Process Scheduler Menu

This section provides an overview of the Process Scheduler menu and discusses how to:

Start a Process Scheduler server.
Stop a Process Scheduler server.
Configure a Process Scheduler server.
Create a Process Scheduler server configuration.
Delete a Process Scheduler server.
Edit the Process Scheduler configuration file.
Use the Process Scheduler options.
Use Process Scheduler command-line options.

Understanding the Process Scheduler Menu

Use the PSADMIN utility to configure and administer PeopleSoft Process Scheduler. PeopleSoft Process Scheduler is used to run batch processes. You only need to configure PeopleSoft Process Scheduler on a server where you intend to run batch processes.

The following sections describe the menus and options within the PSADMIN utility that are related to PeopleSoft Process Scheduler in the order that they appear in the PeopleSoft Process Scheduler Administration menu—not in the order that you would access them the first time you configure the Process Scheduler server.

To access the PeopleSoft Process Scheduler Administration menu:

Select 2 from the PSADMIN menu.
Select the option from the PeopleSoft Process Scheduler Administration menu that corresponds to the action that you need to perform.

The following sections explain the options for PeopleSoft Process Scheduler within PSADMIN. Those options that pertain to UNIX only are marked accordingly.

Starting a Process Scheduler Server

To start a Process Scheduler server:

Select 1 from the PeopleSoft Process Scheduler Administration menu.
To start the Process Scheduler server for a specific database, enter the number in the database list that corresponds to the appropriate database.

Stopping a Process Scheduler Server

You can stop a Process Scheduler server that is running on an application server by using PSADMIN or the Process Monitor.

To stop a Process Scheduler server:

Select 2 from the PeopleSoft Process Scheduler Administration menu.
To stop the Process Scheduler server for a specific database, enter the number from the database list that corresponds to the appropriate database.

Configuring a Process Scheduler Server

Configuring a Process Scheduler server is similar to configuring application servers and web servers. From the PeopleSoft Process Scheduler Administration menu, you invoke a text-driven interface that prompts you for parameter values. All of the Process Scheduler server configuration information for a specific database is contained in the PSPRCS.CFG file, and the PSADMIN provides an interface for and prompts you to edit the PSPRCS.CFG file.

Note. The PSPRCS.CFG file supports environment variables. For example, the TEMP setting in the Process Scheduler section can look like this: TEMP=%TEMP%.

For Microsoft Windows, although you edit the PSPRCS.CFG file through PSADMIN, you can find the PSPRCS.CFG file in the following directory: PS_HOME\APPSERV\PRCS\database_name.

For UNIX, although you edit the PSPRCS.CFG file through PSADMIN, you can find the PSPRCS.CFG file in the following directory: PS_HOME/appserv/prcs/database_name.

To configure a Process Scheduler server by editing the PSPRCS.CFG file:

Select 3 from the PeopleSoft Process Scheduler Administration menu.
Select the number in the database list that corresponds to the server that you want to configure.
Specify the appropriate values for your site in the following configuration section prompts.

Creating a Process Scheduler Server Configuration

You must add or create a Process Scheduler server before you can configure it.

To add a Process Scheduler server configuration on the application server:

Select 4 from the PeopleSoft Process Scheduler Administration menu.
Enter the name of the database that the Process Scheduler server will access.
Enter Y to configure the Process Scheduler.
Update the settings as appropriate for your environment. For example, select 9 to change the UserID that the Process Scheduler uses to log on to the database.
When all of the settings are correct, select 4 to load the configuration.

Deleting a Process Scheduler Server

To delete a Process Scheduler server configuration:

Select 5 from the PeopleSoft Process Scheduler Administration menu.
Select the number in the database list that corresponds to the database to which the server has access.
Enter y when PSADMIN prompts you to continue.

Editing the Process Scheduler Configuration File

You can edit the Process Scheduler server configuration file manually instead of using the prompts in the PSADMIN interface to specify environment variables. This enables you to edit the configuration file in your preferred editor. You must set the EDITOR environment variable to point to the editor. For example:

set EDITOR=c:\apps\utils\kedit\keditw32.exe

Use this example if you use Notepad:

set EDITOR=c:\Windows\Notepad.exe

Note. When editing the PSPRCS.CFG file, make sure that there are no spaces between the equals sign and the entries. Also, make sure that there are no trailing spaces.

To manually edit the psprcs.cfg file:

Select 6 from the PeopleSoft Process Scheduler Administration menu.
Select the database that is associated with the file that you want to edit.
Enter the variables for the parameters that you need to specify.

Note. The system invokes the text editor that you have set as the EDITOR environment variable, such as Notepad or KEDIT, on the particular machine.

Using the Process Scheduler Options

You can have the Process Scheduler server run as a standalone component, or you can have the Process Scheduler server be controlled by BEA Tuxedo, which enables automatic restarts if the server goes down.

Using Process Scheduler Command-Line Options

You can bypass the PSADMIN menus to start and stop the Process Scheduler server.

Starting the Process Scheduler Server

To start the Process Scheduler server from the command line, enter the following:

psadmin -p start -d database_name

Stopping the Process Scheduler Server

To stop the Process Scheduler server from the command line, enter the following:

psadmin -p stop -d database_name

Setting Up the PeopleSoft Windows Service

This section provides an overview of Microsoft Windows services and discusses how to:

Configure the PeopleSoft service.
Monitor the executables.
Administer PeopleSoft services.
Edit the PSNTSRV.CFG file manually.

Note. This section applies only to Microsoft Windows servers. It involves setting up both the application server and Process Scheduler server agent as PeopleSoft Windows services. There is no equivalent feature for UNIX servers.

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 the system. You can also start and stop Microsoft Windows services manually through the Service Control Manager (SCM), 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, the service starts in an environment that is separate from any users who are signed in to the system (or to the machine). This means that administrators no longer need to log on to a machine, start the command prompt, and enter the proper commands to start the server process. In addition, if you use the PeopleSoft service, an administrator's logon session does not need to remain open while the Process Scheduler server or the application server runs.

If you have multiple application server domains and Process Scheduler 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 the Process Scheduler or the application server.

You can start application server domains and Process Scheduler servers as Microsoft Windows services. The PeopleSoft service, if configured, automatically starts the application server or Process Scheduler server when you boot the server machine. This means that administrators do not need to manually boot each application server or Process Scheduler server after you reboot a Microsoft Windows server.

Note. When you configure a domain to run as a Windows service, you must set the JavaVM option to –Xrs in the PSAPPSRV.CFG or PSPRCS.CFG file.

Configuring the PeopleSoft Service

The following procedure assumes that you have already installed and configured an application server domain or Process Scheduler server agent on the Microsoft Windows server.

After completing this procedure, the specified application server domains or Process Scheduler servers start and shut down automatically when the operating system recycles.

To set up the Microsoft Windows service for an application server or Process Scheduler server:

Open the System utility within the Control Panel, and set the following variables on the Environment tab:

Variable	Value
TEMP	Specify the location of the TEMP directory on the Microsoft Windows server, as in C:\TEMP.
TUXDIR	Specify the location of the BEA Tuxedo directory on the Microsoft Windows server, as in C:\bea\tuxedo81.

These settings must appear in the System Variables section.

Run the PSADMIN utility, and select Service Setup from the main menu.
Select Configure a Service from the PeopleSoft Services Administration menu.
Enter y to indicate that you want to change configuration values.
Enter the names of the application server domains and the Process Scheduler databases that you want to include as part of the Microsoft Windows service.

To add multiple domains or databases, delimit each value with a comma and a space.

Note. The Windows Services section of PSADMIN modifies the psntsrv.cfg file in the PS_HOME\appserv directory. You can edit this file manually by selecting Edit a Service Configuration File from the PeopleSoft Services Administration menu.
Select Install a Service from the PeopleSoft Services Administration menu.

Note. All of the domains and databases that you specified are now part of a single Windows service called PeopleSoft PS_HOME, where PS_HOME is the root directory of the PeopleSoft system from which you ran PSADMIN (for example, PeopleSoft C:\pt846).
Return to the Windows Control Panel, and start the Services utility.
In the Services dialog box, scroll to find the entry that adheres to the PeopleSoft PS_HOME naming convention and double-click it to access its properties.

Note. The default startup mode is Manual.
On the General tab of the service properties, select a startup type of Automatic.
On the Log On tab, the Log On As setting must match the Log On As setting that's defined for the BEA ProcMGR V 8.1 service, which was created when you installed BEA Tuxedo.

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

Important! If the PeopleSoft service includes a Process Scheduler server agent, you must select Log On As This Account for both the PeopleSoft service and the BEA ProcMGR V 8.1 service, to prevent problems when running Crystal Reports.
On the General tab of the service properties, click Start.

The application and Process Scheduler servers are now running, and will start automatically whenever you boot the server.

Service Start Failure

It's possible that one or more of the domains or databases that are configured as part of the PeopleSoft PS_HOME 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 or databases starts. A message is written to the Windows event log for each domain and database, 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.

Monitoring the Executables

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

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:

PSAPPSRV.EXE
PSSAMSRV.EXE
BBL.EXE
WSL.EXE

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

For PeopleSoft Process Scheduler, use the Microsoft Windows Task Manager or the Process Monitor to make sure that PTPURCS.EXE is running. If you've changed the name of PTPURCS.EXE, look for your name instead.

Administering PeopleSoft Services

you can specify three options that are related to the PeopleSoft service setup by using PSADMIN or by editing the PSNTSRV.CFG file manually.

The following sections describe each parameter.

Service Start Delay

When an application server or Process Scheduler server 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 application server domain or Process Scheduler server. In this scenario, without a delay set, the connection fails.

You can configure a Service Start Delay parameter in the PSNTSRV configuration file that specifies a delay, in seconds, that elapses before a service attempts to start any application server domains or Process Scheduler servers. 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.

Editing the PSNTSRV.CFG File Manually

You can edit the file directly by selecting 4 (Edit a Service Configuration File) from the main menu. This opens the PSNTSRV.CFG file in a text editor, where you can enter and save your changes.