On server startup, each Business Process Server component checks its own callback flag and tries to load the sbmcallback.xml file when the flag is set to true. On successful parsing of this file, it loads the adapter classes from the defined location, and validates these classes by looking for the methods defined in the xml file. If this process is successful, then these methods are registered for invocation whenever the component changes state.
During the server initialization phase, errors are logged in the OEBPS_HOME/logs/oebps.log file with detailed information regarding the error. An error message may also be displayed on the EJB server console with a detailed trace of the sequence of calls. Optionally, each Business Process Server component specific log file such as bizlogic.log may contain additional information regarding the error.
In the case of BPM Events server, when an error occurs, the server continues with its startup after printing a warning message on the EJB server console as well as the bpmevents.log file.
All exceptions generated in the adapter class must be caught by the methods and handled appropriately. If these are not caught by the adapter method and propagated to Business Process Server, then an appropriate error message is displayed on the EJB server console and the message is written either to the Business Process Server components log file (bpserver.log or bpmevents.log), or the oebps.log file. The Business Process Server continues its processing after logging this exception.
