#171 – Web Profiles

This week on the podcast we discuss Event Mapping for App Engines that was teased in a PeopleSoft Talk. Then Kyle shares what learned about Portal Registries and security, and the new Reload Web Profile feature in 8.57.

Show Notes

#77 – Why the Cloud is Important w/ David Bain

This week on the podcast David Bain, Product Manager for PeopleTools, joins us to talk about Fluid, the Cloud and PeopleSoft, and his favorite PeopleTools features. Dan and Kyle also recap some great discussions they had at the Collaborate conference.

Show Notes

  • David Bain Interview
    • Why the cloud is important to PeopleSoft @ 2:00
    • Why Fluid is a better user interface @ 13:00
    • Favorite new PeopleTools feature @ 19:45
    • How PeopleSoft uses PTF internally @ 22:45
    • Favorite PeopleTools feature of all time @ 26:00
  • Recap of David’s Interview @ 28:00
  • Unsexy software features @ 38:00
  • “Hidden” PeopleTools features @ 39:30
  • Interaction Hub @ 45:45
  • Phire and a Testing Module @ 52:30

8.55 – Log Analyzer

The Log Analyzer is a new PeopleTools 8.55 tool that helps you get more information from App Engine trace files. Log Analyzer is specific to analyzing App Engine traces. It feels like a simplified version of TraceMagic (a good thing!). If you have used TraceMagic for PeopleCode, or the Trace2SQL utility to parse .tracesql files, Log Analyzer feels like the two tools combined.

Trace Settings

You need to set the App Engine trace settings to at least these values in the psprcs.cfg file for the Log Analyzer to work:

  • Trace SQL: 3
  • Trace PC: 64

If you are using Config Manager, that translates to these options:

PeopleCode Trace

  • Trace Start of Programs

App Engine Trace

  • Step
  • SQL

Last, you can set them at the process level:


You can use higher trace values, but these are the minimum for the Log Analyzer to correctly parse your files. Make sure to specify the App Engine SQL trace. If you select the PeopleTools SQL trace, you won’t get an *.AET file when the app engine runs. You can generate a SQL trace (.tracesql) and an App Engine trace (.AET). But at a minimum, you need an *.AET file. Log Analyzer also uses the .TRC PeopleCode trace file.

Log Analyzer GUI

The Log Analyzer tool is a separate java application located under PS_HOME\bin\client\winx86\AELogAnalyzerTool. To launch the tool, run the runTraceAnalyzer.bat batch script. After launching the tool, you’ll see an empty screen. You need to load in an *.AET file.

Screen Shot 2015-12-30 at 1.38.48 PM

Once you load an *.AET trace file, the Log Analyzer will display the heirarchy of the trace program in the lower window. You can expand each section and click on the SQL steps. To view the associated SQL and parameters, click on the “View Details” button. You can also look at the trace in execution order (without the parent/child nesting) by clicking on the “Linearize” button.

Load PeopleCode

If you generate a PeopleCode .TRC trace file, you can import the .TRC file into Log Analyzer. If the trace file has the “Trace Start of Programs” lines (value 64), Log Analyzer will correlate the PeopleCode statements to the app engine step. In the lower window, you can click on the PeopleCode step and view the PeopleCode much like the SQL.

Apply Filters

Log Analyzer has different ways to filter and view your trace file. There are four options to view the different SQL operations: insert, select, update, delete. You can also filter the log output based on a text value, the duration of the step (useful for tuning), or by the number of rows updated.

Log Analyzer feels like a new tool. It functions are still limited (you can filter, but not search), but I think it will be a great tool to add for admins and developers. If you have used TraceMagic, Log Analyzer will be easy to pick up.

VERSION Run Control Options

I have to keep looking this up, so I’m writing it down to make it easier to find next time! There are three modes for the VERSION app engine:

  • Report Mode
    Evaluates the VERSION counters and reports any changes needed; does not change data.
  • Classic Mode
    Resets all the VERSION counters to their starting value (1)
  • Enhanced Mode
    The default mode – it will “advance VERSION counters in a preditable manner” according to Oracle Support.

The name of your run control is how you change the behavior of the VERSION app engine.

  • Report Mode: REPORTONLYxxx – The run control must start with the REPORTONLY value (not case-sensitive)
  • Classic Mode: RESETVERSIONSxxx – The run control must start with the RESETVERSIONS value (not case-sensitive)
  • Enhanced Mode: Any value other than the two above will trigger Enhanced Mode

There is much more to running VERSION, but I’ll save that for another post.

Disabling the App Engine Server

I was having a discussion with another admin recently, and he questioned why we were running our process schedulers with Application Engine Server(PSAESRV) enabled. He pointed out that there is very little gained by running PSAESRV, so why have it turned on?

Now, you aren’t completely without loss in turning this off. Depending on what applications you are running and what your system’s needs are, you will have to make that decision for yourself. Check out Doc ID 651970.1 in MOS for a run down on the pros and cons for each method of running App Engines on your process schedulers.