Using the Application Server Administration Menu
This chapter discusses how to:
Use the Application Server Administration menu.
Use the PeopleSoft Process Scheduler menu.
Use the PeopleSoft Search Server 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.
Configure an application server domain to preload cache.
Clean domain IPC resources.
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.
-------------------------------------------- PeopleSoft Application Server Administration -------------------------------------------- 1) Administer a domain 2) Create a domain 3) Delete a domain 4) Import domain configuration q) Quit Command to execute (1-4, q) : 4
The Administer a domain menu offers numerous configuration, administration, and logging parameters that you may access frequently.
The menu options and parameters within the Create a domain and Delete a domain menus are one-time tasks (per domain).
The Import domain configuration menu enables you to import existing configurations.
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 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_CFG_HOME/appserv/domain_name/PSTUXCFG
APPDIR = PS_CFG_HOME/appserv/domain_name
PATH = TUXDIR/bin; PS_HOME/bin/server/winx86; PATH
APP_PW = Application Password (initialize)
Importing Domain ConfigurationsYou import existing domain configurations by selecting the Import domain configuration option from the PeopleSoft Application Server Administration menu. From the PeopleSoft Import Application Server Configuration menu, you have the option to import a regular domain or an Integration Broker Master Configuration.
-------------------------------------------- PeopleSoft Import Application Server Configuration -------------------------------------------- 1) Import regular domain 2) Import IB Master Configuration q) Quit Command to execute (1-2, q) : 1
Importing a Regular Application Server Domain
When importing a regular application server domain, you can import from a file or from a domain.
-------------------------------------------- PeopleSoft Import Application Server Configuration -------------------------------------------- 1) Import from file 2) Import from application domain q) Quit Command to execute (1-2, q) :
To import configuration settings from a file:
From the PeopleSoft Import Application Server Configuration menu, select Import from file.
Enter the complete file path to the PSAPPSRV.CFG file containing the desired configuration settings.
For example,
c:\documents and settings\TSAWYER.DOMAINX\PSFT\PT\8.51\appserv\appserv\PT850TST
Enter a name for the new domain.
To import configuration settings from an existing domain:
From the PeopleSoft Import Application Server Configuration menu, select Import from application domain.
Enter the path to the appropriate PS_CFG_HOME.
For example,
c:\documents and settings\TSAWYER.DOMAINX\PSFT\PT\8.51\appserv
From the Tuxedo domain list, select the domain containing the desired configuration settings.
Enter a name for the new domain.
Importing an Integration Broker Master Configuration
Use this option to import a master configuration, if you are implementing a "master-slave" integration server configuration. This implementation option is documented in detail within the Integration Broker Administration PeopleBook.
See Implementing Master-Slave Dispatchers.
Booting a Domain
This boots the 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.
------------------------------- PeopleSoft Domain Boot Menu ------------------------------- Domain Name: DOC 1) Boot (Serial Boot) 2) Parallel Boot q) Quit Command to execute (1-2, q) [q]:
You have two booting options: a serial boot and a parallel boot.
Running a Serial Boot
A serial boot starts server processes in a sequential order, with one process beginning to start after the previous process has completely started.
Running a Parallel Boot
A parallel boot starts server processes at the same time, rather than having each process start sequentially. This option typically provides shorter boot durations.
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]:
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.
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 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 Tuxedo tmadmin psr subcommand (print server processes), which displays the 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 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_CFG_HOME\appserv\domain_name\CACHE.
Important! You should purge the cache only after due consideration, and in after consultation with PeopleSoft support or consultants.
Please keep the following in mind:
You cannot purge shared file 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.
If database cache is enabled, the database cache will be purged. If the database cache is purged, it affects all domains using that cache. The database cache is shared across all domains that use the same byte-order (little-endian or big-endian).
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_CFG_HOME\appserv\domain_name\Archive\CACHE_mmddyy_hhmm_ss. Hit Enter to continue or provide a new location:
Note. At runtime, PS_CFG_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 INFO: messages related to version, patch level, serial number and so on. These are normal and don't require any action. 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_CFG_HOME\appserv\domain_name\LOGS\PurgeCache_mmddyy_hhmm_ss.log.
Note. At runtime, PS_CFG_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/10 11:47 User Explanation: Processes appeared to take a long time to recycle. Cache Contents archived to C:\ptservers\appserv\QEDMO\Archive\CACHE_021710_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_CFG_HOME/appserv/domain-name/psappsrv.ubb, and carries out the tmloadcf - y psappsrv.ubb command to generate the following file: PS_CFG_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 Tuxedo patch.
Note. If you edit the psappsrv.cfg file directly, it is recommended to reload your domain configuration. This is necessary because some settings in psappsrv.cfg are transferred to the PSTUXCFG file for the domain. This transfer of settings can only be achieved by running UBBGEN and tmloadcf, which the "Configure this domain" option performs.
Editing Configuration and Log Files
Use the Edit Configuration/Log Files menu to view the application server and 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.
Note. Server configuration files (.CFG) support the use of environment variables, such as %PS_HOME%, %TEMP%, and so on.
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 in a text editor. 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 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
The Create a domain option creates a subdirectory under PS_CFG_HOME/appserv using the domain name you specify as the directory name and copies the required domain 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 eight characters.
Select a configuration template from the Configuration template list.
The configuration templates are preconfigured sets of application server processes.
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 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.
Configuring an Application Server Domain to Preload Cache
This section provides an overview and discusses how to:
Create cache projects.
Delete cache projects.
Preloading File Cache.
See ServerCacheMode.
See Load Application Server Cache.
Understanding Preload Cache Projects
To improve performance, the application server uses a caching mechanism that keeps commonly used objects in memory and either file form on the application server or in a database cache. Caching reduces the need for a complete database query each time a definition is accessed. As more definitions are accessed, more data becomes stored in the cache. However, if a page, for example, has not already been accessed, it does not exist in the current cache, and the user may experience a slower response time as the system requests the page from the database for the first time. To prevent this initial performance degradation, you can preload file, database, and memory cache with commonly used definitions inserted into a cache project.
Preloading cache involves creating a project containing commonly used definitions and then referring to these projects in the PSADMIN settings PreloadMemoryCache and PreloadCache. By default, PreloadMemoryCache and PreloadCache are commented out because the two parameters need to be set to a specific name of a project that you create. You can set the parameters to reference separate projects. You use the Select Preload Objects page to select frequently used definitions and build the preload project containing the objects selected.
The cache project is intended to be used for a new domain, where the cache is not yet built. Prior to providing the domain for production use, use the Preload Cache PSADMIN option to build the cache containing the objects specified in the project. The domain starts the PSAPPSRV process, builds the cache, and shuts down.
The memory cache project is intended to be used during a server process recycle. When a the system starts a new process to replace an old one, the new process loads memory cache based on the project specified by PreloadMemoryCache so that the new process will not have delays when processing the first few service requests. Because it is desirable to have new processes start as quickly as possible, there is a timeout (or limit) of 60 seconds for PreloadMemoryCache. That is, PreloadMemoryCache preloads as many definitions as possible before the timeout of 60 seconds.
Note. In general, it is not recommended to create large projects for the PreloadMemoryCache project. For all cache projects (used for file, database, and memory cache) the optimum selections for the projects will require tuning and testing at your site.
Creating Cache Projects
To create cache projects:
In a browser, select PeopleTools, Utilities, Administration, PreLoad Cache, Select Preload Objects.
Select the Add a New Value tab, and in the Project Name edit box, enter the name of the project that will contain the definitions you select, and click Add.
Note. All project names used to contain definitions for preloaded cache must contain the "PLC_" prefix.
On the Select Preload Objects page, enter a Description, and select the Object Type to add.
Object Type refers to the definitions you create with PeopleTools, such as components, menus, pages, Application Engine programs, and so on.
Use the Key fields, to refine the selection of the definition as needed.
The keys will differ depending on the Object Type selected.
Note. Project definitions support up to four keys for identification, so you can use up to four keys when selecting objects for the preload cache project.
Click Save.
Click Build Project Definition.
On the Process Scheduler Request page, click OK.
This invokes an Application Engine program (PTCHPLC_PRJ) that creates the project definition in the database and populates it with the definitions you selected. The PTCHPLC_PRJ also automatically includes all related definitions in the project.
Note. Cache projects can be created manually in Application Designer, without running the PTCHPLC_PRJ program. The project name must include "PLC_".
Deleting Cache Projects
To delete a preload file cache project:
Select PeopleTools, Utilities, Administration, Preload Cache, Delete Preload Project.
On the Find an Existing Value page, click the appropriate project name.
On the Delete Preload Project page confirm that you have selected the appropriate project and click Delete the preload project.
Preloading Cache Projects
To preload a cache project:
Shut down the application server domain.
Edit the PSAPPSRV.CFG configuration file for the appropriate domain.
In the [Cache Settings] section, uncomment the PreloadCache= parameter, and enter the name of the pre-load project for this application server domain.
For example:
PreloadCache=PLC_PROJECTA
On the PeopleSoft Domain Administration menu in PSADMIN, select 9) Preload Cache.
When preloading cache, keep the following in mind:
Preload Cache does not work when shared caching is enabled.
If database caching is enabled, Preload Cache loads the cache project into the database cache.
Increasing the TM_BOOTTIMEOUT value (in the psappsrv.env) may be necessary when creating cache files for larger projects. If you increase the boot timeout value, it should not be regarded as a permanent change. That is, do not reconfigure the domain with the temporary value set, and after preloading cache, revert to the original boot-timeout value.
Preloading Memory Cache
To preload the memory cache:
Edit the PSAPPSRV.CFG configuration file for the appropriate domain.
In the [Cache Settings] section, uncomment the PreloadMemoryCache= parameter, and enter the name of the preload project that should be preloaded on this application server for memory cache.
For example:
PreloadMemoryCache=PLC_PROJECTB
See Also
Cleaning Domain IPC Resources
Use the Clean IPC Resources of this domain option to clear the interprocess communication (IPC) resources utilized by a domain. When a domain shuts down normally, the IPC resources it was using get released as part of the shut down process. However, if a domain terminates abnormally, in many cases the IPC resources are still assigned to the previous domain instance. This option enables you to clean any orphaned IPC resources assigned to a domain.
Using the Process Scheduler Menu
PeopleSoft Process Scheduler is used to schedule and run batch processes against the database. Process Scheduler domains are managed by Tuxedo, just as application server domains are. You only need to configure PeopleSoft Process Scheduler on a server where you intend to run batch processes. The menu options are identical to those provided for administering an application server domain, except where the options are not applicable to a Process Scheduler domain.
-------------------------------------------- PeopleSoft Process Scheduler Administration -------------------------------------------- Domain Name: QEDMO 1) Boot this domain 2) Domain shutdown menu 3) Domain status menu 4) Configure this domain 5) TUXEDO command line (tmadmin) 6) Edit configuration/log files menu 7) Clean IPC resources of this Domain q) Quit Command to execute (1-7, q) :
The Process Scheduler PSADMIN options differ from the application server PSADMIN options for these items.
|
Function |
Difference |
|
Booting |
The Process Scheduler domain boot does not provide the option to select a serial or parallel boot. All Process Scheduler domains start in serial mode. |
|
Viewing//Editing log files and configuration files |
The Process Scheduler Edit/View Configuration/Log Files Menu does not display options for viewing the PSAPPSRV and PSSAMSRV SQL trace files. |
|
Configuring Integration Broker (messaging) servers |
For Process Scheduler domains there is no option to import a Master IB Domain nor is there the option to configure messaging servers. |
|
Caching |
For Process Scheduler domains there are not options to purge or preload file cache. |
All of the Process Scheduler server configuration information for a specific domain is contained in the PSPRCS.CFG file, and PSADMIN provides an interface for and prompts you to edit the PSPRCS.CFG file.
Although you typically edit the PSPRCS.CFG file through PSADMIN, you can find the PSPRCS.CFG file in the following directory:
Windows: PS_CFG_HOME\APPSERV\PRCS\domain
UNIX: PS_CFG_HOME/appserv/prcs/domain
See Also
Using the Application Server Administration Menu
Using the Search Server MenuIf you are setting up a remote search domain, you use the Search Server menu options to configure your search domain. The configuration and administration options used in implementing a search domain are identical to those used in setting up an application server domain.
See Also
Using the Application Server Administration Menu
Setting Up the PeopleSoft Windows Service
This section provides an overview and discusses how to:
Configure the PeopleSoft service.
Test the service.
Edit the service configuration file.
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 ServicesA 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:
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:
|
Variable |
Value |
|
TEMP |
Specify the location of the TEMP directory on the Microsoft Windows server, as in C:\TEMP. |
In PSADMIN utility, 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, 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
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, where PS_CFG_HOME is the location of the domain installations.
Return to the Windows Control Panel, and start the Administrative Tools, Services utility.
In the Services utility, scroll to find the entry that adheres to the PeopleSoft PS_CFG_HOME naming convention and access its properties.
On the General tab of the service properties, select a startup type of Automatic.
Note. The default startup mode is Manual.
On the Log On tab, the Log On As setting must match the Log 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 to Log On As This Account (referring to the same account).
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 Securing 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:
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.
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 selecting 4 (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.
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.
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.
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.
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.