Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 7 Processing External Data Using TIBCO Object Service Broker : Handling TIBCO Object Service Broker Requests

Handling TIBCO Object Service Broker Requests
The following sections describe how EXP tables handle requests with respect to:
By understanding these operations, you can take full advantage available features when you develop applications.
Transaction Length
An export transaction spans the same length of time as a TIBCO Object Service Broker transaction.
Error Handling
The TIBCO Object Service Broker runtime environment signals system exceptions to permit an application to recover from an error. A three-level hierarchy of exceptions exists. The ERROR exception is the top of the hierarchy and is intended to be a catchall exception. Each exception traps the exceptions that appear below it in the hierarchy.
All errors encountered when accessing external data the EXP tables are trapped under one of the following TIBCO Object Service Broker exceptions:
ERROR Exception
An ERROR exception indicates that an error is detected and no lower-level exception exists in the application.
ACCESSFAIL Exception
An ACCESSFAIL exception indicates that a table access error is detected. The only valid exception under an ACCESSFAIL exception is a GETFAIL, indicating that no occurrence satisfies the selection criteria.
INTEGRITYFAIL Exception
An INTEGRITYFAIL exception indicates an attempt to violate data integrity is detected. The following exceptions are valid under an INTEGRITYFAIL exception:
 
Indicates that permission for the requested action on the TIBCO Object Service Broker object is denied
See Also
TIBCO Object Service Broker Programming in Rules for more information on exceptions.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved