Program user-defined extensions to write entries in the local error log.
In most circumstances, user-defined extensions should use exceptions to report errors. However, you can choose to provide information about significant events, error or otherwise, for problem determination and operational purposes. The details that you supply are included in pre-defined message text that is extracted from a message source or catalog.
You can also write trace information,
using CciUserTrace, CciUserTraceW, CciUserDebugTrace,
and CciUserDebugTraceW when tracing and debugging
is active.
You can choose to write messages that are defined in the
product message catalog (BIPv600)
to which you can add your own text as an argument. If you prefer, you can
create your own message catalog, so that you can create more complex messages,
or share a message catalog with other applications. If you want to create
your own message catalog, see Creating message catalogs.
The description here covers exceptions that are raised during normal message flow processing. You must also provide for exceptions that are raised when you deploy and configure a message flow. Messages that result from these configuration exceptions are reported back to the workbench for display to the workbench user. Create an appropriately-named Java properties file to contain your messages, then copy the file to each computer on which you are running the workbench, so that your messages can be displayed.