On the Instrumentation Platform tab page, under Specific Settings, you can specify the following data collection modes, per system, for EM-IPA at runtime:

• Journal Mode

  Data is written for every processing step to exception management logging, regardless of whether an exception occurred. Only step data is persisted; in other words, there is no error or payload information. This setting is not sensitive to the trace flags provided by SAP Extended Passport. This means that tracing occurs for all users in all sessions in which the appropriate processing step is executed.

• Trace Mode

  Data is written for every processing step to exception management logging, regardless of whether an exception occurred. This setting is sensitive to the trace flags provided by SAP Extended Passport. This means that the trace information is written only if the appropriate trace flags are set from outside, for example, by SAP Client Plug-In. The complete information, including the callstack and payload, is persisted.

• Exception Mode

  Data is written for every processing step to exception management logging, but only when an exception has occurred. In this case, the complete information, including the callstack and payload, is persisted.

• Test Mode

  Data is written for every processing step to exception management logging, regardless of whether an exception occurred. The complete information, including the callstack and payload, is persisted.

   Note

  In exception mode and test mode, you can selectively switch off the collection of payload and/or callstack information.

  End of the note.

• On the Repository tab page, under General Settings, configure the following:

  During instrumentation, it is necessary to specify a business process type ID to distinguish the different process types. If different business process type IDs were specified, these have to be maintained accordingly within the exception management repository. The process ID is mapped to a category/subcategory, which can either be imported from the Solution Directory or manually maintained here.

• Housekeeping

  Specify how long the system retains the exception data in the exception management store.

• Self Monitoring

  Administer the exception management extractors. You can activate and deactivate extractors, and display the extractor log and detailed information about each extractor. The log shows when the extractors last sent exceptions from the managed systems, the quantity of data, and whether there were any problems.