Errors in the system usually become apparent when jobs do not move forward (for example, a user uploads a job and it then returns to a downloaded state).
When under workflow control, it is recommended that you troubleshoot issues starting with looking at the audit trail of the workflow. You will need the job ID before starting.
Once the location of the fault has been identified, check the individual service log files.
Investigating a System error
-
Open the SOA Enterprise Manager Console.
-
Navigate to the workflow (labelled SMSMainWorkflow) to display the instances.
Note: Click Show All if not all of the instances are displayed. You may also need to adjust the time filter.
-
Use the Name search filter to find the required workflow.
The workflow names are in the form [job_id]-[timestamp].
Note: The filter [job_id]% is usually sufficient.
- Click Instance to display the trace.
-
Click on *SMSMainWorkflow and select the Flow tab.
-
A task that has errored is highlighted in red. Click the task to show the error message from a component.
Instead, you may find your workflow is in a state where it is waiting for a response from a service. In this case, select the last task in the flow labelled Waiting On. If the process has been waiting for a very long time, this may be an indication of a crashed or hung component service.
Note: You can also see the errors in the workflows by opening the Faults and Rejected Messages tab.
