Using the Application Server Administration Menu

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:

1. From the PeopleSoft Import Application Server Configuration menu, select Import from file.

2. 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.53\appserv\appserv\PT850TST

3. Enter a name for the new domain.

To import configuration settings from an existing domain:

1. From the PeopleSoft Import Application Server Configuration menu, select Import from application domain.

2. Enter the path to the appropriate PS_CFG_HOME.

   For example,

   c:\documents and settings\TSAWYER.DOMAINX\PSFT\PT\8.53\appserv

3. From the Tuxedo domain list, select the domain containing the desired configuration settings.

4. 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.

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.

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.

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        62645       RTDC796+       0  42801   2140050 (  IDLE )
PSAPPSRV.exe   APPQ        APPSRV         1    422     21100 (  IDLE )
PSMONITORSRV.e MONITOR     MONITOR        1      0         0 (  IDLE )
PSWATCHSRV.exe WATCH       WATCH          1      0         0 (  IDLE )
PSAPPSRV.exe   APPQ        APPSRV         2      4       200 (  IDLE )
JSL.exe        00095.00200 JSLGRP       200      0         0 (  IDLE )
PSMSGDSP.exe   00098.00100 PUBSUB       100      4       200 (  IDLE )
PSSAMSRV.exe   SAMQ        APPSRV       100      0         0 (  IDLE )
PSMSGHND.exe   MBHQ        PUBSUB       101      0         0 (  IDLE )
JREPSVR.exe    00094.00250 JREPGRP      250     29      1450 (  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
--------------- --------------- --------------- -------- ------- -------------
RTDC79623VMC    NT              JSH             **:**:** IDLE    0/0/0
RTDC79623VMC    NT              JSH             **:**:** IDLE    0/0/0
RTDC79623VMC    JPOOL_15        dhcp-adc-twvpn+  0:02:03 IDLE/W  0/0/0
RTDC79623VMC    NT              tmadmin          0:00:00 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
---------      ------------------- ---------  --------  --------    -------
PSAPPSRV.exe   APPQ              2         -         0         - RTDC79623+
JSL.exe        00095.00200       1         -         0         - RTDC79623+
JREPSVR.exe    00094.00250       1         -         0         - RTDC79623+
BBL.exe        62645             1         -         0         - RTDC79623+
PSMONITORSRV.e MONITOR           1         -         0         - RTDC79623+
PSWATCHSRV.exe WATCH             1         -         0         - RTDC79623+
PSSAMSRV.exe   SAMQ              1         -         0         - RTDC79623+
PSMSGHND.exe   MBHQ              1         -         0         - RTDC79623+
PSMSGDSP.exe   00098.00100       1         -         0         - RTDC79623+

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.

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.

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 domain boot (serial or parallel) and during a server process recycle.

When you boot a domain in serial mode, a message warns the user of a possible delay in booting the domain and lists the project that is being loaded, but when you boot a domain in parallel mode, the message is not displayed.

When a 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. If a project does not load completely, an administrator can adjust the boot timeout setting.

Logs pertaining to preloading memory cache are logged in the application server log file. In the application server configuration file, the log fence setting must be set to 5 to view the preload memory cache logs.

Creating Cache Projects

To create cache projects:

1. In a browser, select PeopleTools, Utilities, Administration, PreLoad Cache, Select Preload Objects.

2. 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 clickAdd.

   Note: All project names used to contain definitions for preloaded cache must contain the "PLC_" prefix.

3. 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.

4. 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.

5. Click Save.

6. Click Build Project Definition.

7. 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:

1. Select PeopleTools, Utilities, Administration, Preload Cache, Delete Preload Project.

2. On the Find an Existing Value page, click the appropriate project name.

3. 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:

1. Shut down the application server domain.

2. 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

3. 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.

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

Working with the Dynamic Cache Repair Utility

PeopleTools provides a dynamic cache repair utility that enables you to configure the system to monitor and adjust automatically a domain’s cache while it runs, requiring no intervention from system administrators, and without requiring the domain or a server process to be restarted.

For more information on enabling and using the cache repair utility, see EnableCacheRepair.