PeopleTools ATT: Understanding Application Engine Trace and Troubleshooting Tools

Introduction

PeopleSoft applications are widely used across industries for enterprise resource planning (ERP) and human capital management (HCM).

Application Engine (AE) is one of the core batch processing tools within PeopleSoft, allowing developers to create, schedule, and manage complex processes.

Debugging and troubleshooting Application Engine programs can be challenging, which is where Application Engine Trace and troubleshooting tools within PeopleTools ATT come into play.

This article provides an in-depth look at how to enable AE tracing, interpret trace files, and utilize troubleshooting tools to identify and resolve issues efficiently.

What is Application Engine Trace?

Application Engine Trace is a logging mechanism that records the execution details of AE programs. This tracing helps developers diagnose performance bottlenecks, unexpected failures, and SQL-related issues. Tracing is particularly useful when dealing with complex processes that involve multiple SQL statements, PeopleCode, and data manipulations.

Types of Application Engine Traces

PeopleTools provides different tracing options for Application Engine:

1. SQL Trace (TraceSQL) – Captures all SQL statements executed by the AE program.
2. PeopleCode Trace – Logs PeopleCode execution and variable values.
3. Step and SQL Trace – Records execution at the step level along with SQL details.
4. Statement Timings Trace – Provides execution times for SQL statements.
5. Application Engine Tracing – Captures metadata, execution flow, and error details.

Each trace type provides valuable insights into specific aspects of AE program execution, allowing for precise troubleshooting.

How to Enable Application Engine Tracing

To enable tracing for an AE program, you can use the following methods:

1. Using Configuration Manager

• Open PeopleSoft Configuration Manager.
• Navigate to the Trace tab.
• Select the appropriate trace options (SQL, PeopleCode, etc.).
• Save changes and restart the process scheduler.

2. Using Process Scheduler

• Navigate to PeopleSoft Process Monitor.
• Select the AE process you want to trace.
• Click on Override Options and enter the trace flags.

3. Using Command-Line Parameters

For direct execution via command line, use:

psae -CT ORACLE -CD HR88 -CO PS -CP password -R tracevalue

Where tracevalue is a combination of trace flags to specify the level of tracing.

4. Using PeopleCode

You can enable tracing dynamically in PeopleCode using:

%TraceAE = 135;

This enables SQL and PeopleCode tracing with detailed output.

Interpreting Trace Files

Once tracing is enabled, PeopleSoft generates log files in the designated directory. Key components of an AE trace file include:

1. Program Start and End Time – Helps in performance analysis.
2. SQL Statements – Displays queries executed by the AE program.
3. PeopleCode Execution – Logs conditional statements and variable values.
4. Errors and Warnings – Highlights issues and points to potential solutions.

By analyzing these logs, developers can pinpoint inefficiencies and resolve unexpected errors in the AE process.

Troubleshooting Application Engine Programs

Apart from AE tracing, PeopleTools provides additional troubleshooting tools to enhance debugging.

1. Process Monitor

The Process Monitor displays the execution status of AE programs. Key statuses include:

• Success – Process completed without issues.
• No Success – Indicates failure.
• Error – Points to an execution problem.
• Processing – Shows an active execution.

Using the View Log/Trace option, developers can access trace files for debugging.

2. Application Engine Restart

PeopleSoft allows AE programs to resume from the last successful step if they fail. To enable restartable AE programs:

• Ensure the State Record is properly configured.
• Set the Restart Enabled flag in the process definition.

If an AE process fails, it can be restarted from PeopleSoft Process Monitor without reprocessing completed steps.

3. Using Application Engine Debugger

The AE Debugger within PeopleTools provides a step-by-step execution view, allowing developers to:

• Pause execution at breakpoints.
• Inspect variable values.
• Modify runtime parameters.

4. Performance Optimization Techniques

To improve AE performance:

• Optimize SQL queries using proper indexing.
• Reduce data processing load by filtering unnecessary records.
• Use Set Processing instead of Row-by-Row Processing for better performance.
• Enable Commit Frequency to manage database transactions efficiently.

Common Errors and Solutions

Here are some common AE issues and how to resolve them:

Error Message	Possible Cause	Solution
ORA-00942: Table or View Does Not Exist	Incorrect table reference	Verify SQL statements and ensure table exists
AE Program Stuck in Processing	Infinite loop or missing commit	Check PeopleCode logic and commit settings
SQL Deadlock Detected	Concurrent updates on the same data	Implement row-level locking and optimize transactions

By leveraging AE trace files and debugging tools, developers can identify and fix these errors efficiently.

Conclusion

Application Engine tracing and troubleshooting tools in PeopleTools ATT are essential for diagnosing and resolving AE program issues. By enabling tracing, analyzing logs, and using tools like Process Monitor and AE Debugger, developers can enhance AE program efficiency and reliability.

Understanding how to use these tools effectively ensures smooth execution of batch processes and optimized performance in PeopleSoft applications.