How To
Summary
Sometimes, when you're troubleshooting behaviors in OpenPages, you need to determine if there are triggers related to the issue or if there are triggers for the related objects.
Objective
This steps will guide you through a way of checking this just reviewing the <server>-OPNode#Server#-startup.log file.
Steps
- Log in to the OpenPages Application Server using an administrative user
- Navigate to <OpenPages_Home>/aurora/log folder
- Open the <server>-OPNode#Server#-startup.log file using any text editor
- Analyze the log using the following guidance:
Every time the OpenPages services are started, these lines are recorded:
After this, all the triggers are loaded and at the end these lines are recorded:
Therefore, it is recommended to extract just the last recorded full section and paste it in a blank file in order to make analyzing the startup/file easier.
The file from which the triggers are loaded is recorded in the log, generally (and that is the recommendation to developers) the custom triggers are configured under custom XML files.
OpenPages uses out-of-the-box (OOB) the following XML files:
The java classes used in the triggers are recorded, generally custom classes are used and you can distinguish them from the IBM classes by the sequence, custom classes generally have a name related to the specific customer.
5. Using the tips described in step 4, you can start looking for the fields or the object related to your issue and discover if they are used by OOB or custom triggers.
Was this topic helpful?
Document Information
Modified date:
13 July 2018
UID
ibm10717073