Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 9 Manipulating Storage Data Using TIBCO Object Service Broker MAP Tables : Handling TIBCO Object Service Broker Requests

Handling TIBCO Object Service Broker Requests
The following sections describe how requests are handled with respect to:
Synchronization and Recovery
COMMIT and ROLLBACK statements have no effect on MAP tables; data in storage is read or written directly by the GET, REPLACE, and FORALL statements.
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 through the MAP server are trapped under one of the following 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 following exceptions are valid under an ACCESSFAIL exception:
 
INTEGRITYFAIL Exception
An INTEGRITYFAIL exception indicates an attempt to violate data integrity is detected. The following exceptions are valid under an INTEGRITYFAIL exception:
 
RULEFAIL
A RULEFAIL exception indicates that an error is provoked by incorrect rules language coding. The following exceptions are valid under a RULEFAIL exception:
 
An attempt is being made to access unregistered storage, that is, there is no row in @MAP to match the address referenced
See Also
TIBCO Object Service Broker Programming in Rules for more information on exceptions.

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved