Working with PeopleSoft Server Process Logs

For each PeopleSoft server process, such as PSAPPSRV, the system writes an individual log file to your specified logs directory. Depending on the logging level, these log files can contain varying amounts of information. Reviewing these log files regularly can help you to identify potential issues or system trends, and they are a valuable source of information when troubleshooting. The PIA and application server domain logs include correlation fields, such as SRID, TOP Instance ID, and Operator ID that enable you to correlate log files across multiple domains when troubleshooting. To understand the log information, it is helpful to be able to identify the various log fields that the system writes to an individual line in the log file.

Note: Correlation data is logged when available, otherwise placeholders (hyphen) are used in place of correlation fields to maintain uniformity of format in the log files.

Note: Integration Broker, trace, and third-party log files do not include correlation information. However, all log files include placeholders (hyphen) for the correlation fields to maintain uniformity of format in the log files.

A typical log file contains these log fields:

[Server Process]:[Operating System Process ID] [Service Request Number] [Timestamp] [SRID] [TOP Instance ID] [Operator ID] [Log Level] [Message]

The following fields are included in the logs:

  • Server Process — The PeopleSoft server process, such as PSAPPSRV.

  • Operating System Process ID — The process number assigned by the operating system.

  • Service Request Number — The number of service requests that this Tuxedo server process has sequentially executed.

    See Listeners, Handlers, and Queues.

  • Timestamp — Date and time the message was generated.

    The format is YYYY = year, MM = month, DD = day, HH = hour, MM = minute, SS = seconds, and sss = milliseconds.

  • SRID — A base64 encoded field uniquely associating a user session and its service request in the PeopleSoft-generated online transaction processing (OLTP) log files. For example, 17F2TbFWJw69UXCzfobVhZ.

    Note: This is sometimes referred to as TRID.

  • TOP Instance ID —Top correlation attribute in PPM’s PMU Tree.

    It is a 64-bit integer. For example, 455266533594. It is used for correlating log entries with PPM data. For more information on instance IDs in PMU trees, see Viewing Open PMUs.

  • Operator ID and remote address — PeopleSoft user ID and the remote address (IP address or DNS host name) that the user has at the time the message is logged.

  • Log Level — The relative importance of this particular log message.

    Only messages whose logging levels are less than or equal to the LogFence appear in the log file.

    See the LogFence information in Domain Settings.

  • Message — The actual log message.

The following table provides examples of content for each trace field.

Server Process:PID

Service Request

Timestamp

*(YYYY-MM-DDTHH:MM-SS.sss)

SRID

TOP Instance ID

Oper-ator ID

Log Level

Message

PSAPPSRV.5648

(993)

[2012-12-12T11:54:23.778]

-

-

-

(3)

Authenticate User not needed. New User Id/Password same as current.

PSAPPSRV.5648

(1000)

[2012-12-12T11:54:26.198]

-

-

-

(0)

Recycling server after 1000 services

PSAPPSRV.28708

(0)

[2012-12-12T11:54:35.514]

-

-

-

(0)

Cache Directory being used: D:\PT_SERVER\appserv\T1B85301\CACHE\PSAPPSRV_1\

PSAPPSRV.28708

(0)

[2012-12-12T11:54:38.339]

-

-

-

(0)

Server started

PSAPPSRV.24208

(1344)

[2015-07-14T00:28:15.317]

17F2TbFWJw69UXCzfobVhZ

455266533594

QEDMO

(3)

-

You can select how you prefer to separate the trace fields using the [Domain Settings] LogFieldSeparator setting.