Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Error handling in service rules

Updated on September 10, 2021

 This presentation is part of the Services and Connectors Self-Study Course.


Many service types either have a Faults tab or Exceptions tab that can be configured on the Service Rule. Through these facilities you can communicate service errors to the calling application.  You can also configure clipboard property values to be sent back in case of error.  It is especially important to configure the clipboard property values as this is the only clean way to communicate fatal exceptions, such as service activity not found.

Remember that your PRPC service may be part of a larger application, possibly orchestrated by a service oriented architecture (SOA).  If your service is performing updates to data repositories, you may need to build in some manual rollback processing in case other components within the application fail.  If you are doing database updates and your service is being called through a Java API, such as JSR-94, then your application server may be set up to handle extended transactions that cover all database updates occurring in the same JVM, even when you are accessing different databases.  So it very much depends on the type of service you are putting together, along with the type of application server software (for example, Apache Tomcat versus IBM Websphere).

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us