Managed Methods has added runtime exception management in the latest release of JaxView, their product for managing and monitoring Web service operations and SOA environments.

Architects, developers and IT operations managers working with Web services in production need visibility into the operation XML-based services. This includes visibility into faults and exceptions that may occur. Providing thorough exception management at design time is critical for building robust applications. This applies even more so to Web services and SOA, where loose coupling presents challenges for event management. How exceptions are communicated and handled in SOA environments will impact reliability and manageability. Systems may be designed to enable recovery from some types of exceptions. Other exception types may require mediation and manual intervention. JaxView from Managed Methods can act as an intermediary to reduce the impact of exceptions on service quality.

In loosely coupled environments, such as Web services and SOA, communicating and dealing with faults and exceptions is an important design consideration. Exception information should be communicated using the same messaging protocol as other service data. Robust service applications should include fault tolerant mechanisms to allow a business process to retry and resume or advance using alternate resources. In the case of irrecoverable exceptions, there is a risk that sensitive information needed for internal diagnosis may be exposed to external customers. Deployed as a network intermediary or service proxy, JaxView can be used to capture and modify the response returned to the client or service coordinator. JaxView's exception management can also mediate exceptions by rerouting a service request to an alternate provider or process. Routing of service request can also be done by JaxView with its support for WS-Addressing SOAP headers.