Common sources of error

The following are five general types of errors commonly encountered in setting up user exits and the steps to take to correct them.

File location errors

It is crucial that the WBI-C system be able to find the user exit classes. A Class Not Found exception in either log may occur if:

Additional file location problems can arise if, in a multibox, split topology setup, the appropriate user exits are not deployed with all instances of receivers or routers, as necessary.

Resolution: Make sure the class files are properly loaded in the classpath and that the exact name and location of the user exit class files match the details specified during the upload of the XML descriptor files to through the Console. Make sure all appropriate files exist in all appropriate places.

Handler failure errors

Failure of a pre-processing handler in the receiver component or of either type of handler in the sender component, or failure in an unpackaging, protocol processing, or packaging handler in the router component will produce an error in the appropriate logs and in the Console. Turning on Debug mode will produce a more detailed error report. The error will result in the message or business document not being processed further, and, in the case of an HTTP receiver pre-processing failure, a 500 response code being sent back to the initiating host.

Resolution: Fix the problem in the user exit code, reload the class files, and restart the component.

Processing mode errors

When a document protocol supports synchronous processing, the defined target must have a SyncCheck handler specified. If the protocol does not support synchronous processing, a post-process handler must not be specified.

Resolution: Make sure that the user exits you specify are appropriate for the defined processing mode.

File update errors

There are two ways to update user exit information in the system:

If you update the class files, you should restart the appropriate components to make sure that the changes are effective. Uploading new XML descriptor files for existing user exits (assuming the files have the same name, and designate the same class) will change whatever attributes and attribute values that are set immediately. In this case, any documents that are processed after the new descriptor files are uploaded will be processed as described in those new files.

Resolution: Updating class files requires a component restart to be effective; updating XML descriptor files takes effect immediately.

File deletion errors

A user defined receiver (transport) cannot be deleted once it has been used in a target definition, even if the target itself has been deleted. A user defined sender (transport) cannot be deleted once a gateway using that transport has been defined, even if the gateway is set to an offline or disabled state. On the other hand, a fixed workflow handler can be deleted, even if it is part of a specified workflow. As soon as it is deleted, the handler is immediately removed from the Configured List. Any document flow dependent on that handler that is processed after the deletion will fail.

Resolution: Do not try to delete transports once they have been used to define a target or a gateway. Do not delete handlers for fixed workflow unless you are absolutely sure they are not used anywhere.

Copyright IBM Corp. 2003, 2004