Skip to content

#112 – psappsrv.cfg

This week Dan and Kyle walk through the psappsrv.cfg file and discuss how they have configured their application servers.

Show Notes

  • psappsrv.cfg @ 3:00

4 thoughts on “#112 – psappsrv.cfg”

  1. Excellent session. Lots of little tips and thoughts. Really enjoyed it. A few comments:

    1.DisableGTTStats: From Oracle 12c statistics on Global Temporary Tables are private to the individual physical instantiation of the table in each database session. Whereas, in 11g, all sessions share statistics on the same Global Temporary Table. Obviously, you don’t want statistics bleeding from one session to another.
    So don’t disable this from 12c, but do disable up to 11g.
    2. Add to path: Setting the path of the database client can be a good thing if you have multiple versions of the client installed. You are not at mercy of environmental changes before you start the domain
    3. Domain ID: If you use PeopleSoft Performance Monitor then Domain ID should uniquely identify each domain. That will help you distinguish domains. It can be easier than using host:port.
    4. Dynamic Changes does have a small additional overhead. The application server repeatedly rereads the config file to detect any changes. Fine to enable in development, but I wouldn’t in production.
    5. LogFence = 4: Increasing the logging can have an additional overhead. If you have Oracle Diagnostics Pack then you can identify slow components with the database instrumentation (set EnableDBMonitoring) and Active Session History.
    6. MgrAutoLock: The problem is even more insidious. I have seen the system become unusable when an administrator experienced a component crash when saving a change to user security. It left them holding a lock on the User Profile Management (UPM) version number in the database. Then, nobody can log into PeopleTools because they can’t update the version because it is locked. The lock only clears when the PSAPPSRV service times out and the session is terminated by dead connection detection after the application server process recycles. This parameter is documented in Oracle Support Note 2175273.1.
    7. Match Fetch Size applies to PS/Query. The entire query result set is loaded into memory. The limit is there to protect the system from the users! It is typical to set the limit lower on the PSAPPSRV than the PSQRYSRV to protect online users from ad-hoc queries run in the query manager component.

  2. Pingback: #118 – What Metadata?

Leave a Reply

Your email address will not be published. Required fields are marked *