CloudStreams 10.5 | webMethods CloudStreams | Administering webMethods CloudStreams | Virtual Services | Creating a New Connector Virtual Service (REST) | The Error Sequence Step (Connector Virtual Service, REST)
 
The Error Sequence Step (Connector Virtual Service, REST)
The default connector virtual services are configured to return the native service provider's service fault, if one is available. CloudStreams will send whatever content it received from the native service provider. You can optionally invoke IS services to pre-process or post-process the error messages.
*To configure the Error Sequence step (connector virtual service, REST)
1. Open Software AG Designer and display the CloudStreams Development perspective by clicking Window > Open Perspective > Other > CloudStreams Development.
2. In the CloudStreams Governance view, expand your CloudStreams Governance project and click the connector virtual service name.
3. Expand Error Sequence.
4. Click Error Messaging and complete the fields in the General page in the Properties view as follows.
Option
Description
Name
You can optionally change the step name to any other name. There are no naming restrictions.
Type
(Read-only field.) Error Messaging.
Processing Method
Optionally select either of the following:
*Pre-Processing: Select this option if you want to invoke an IS service to manipulate the response message before the Error Sequence step is invoked. The IS service will have access to the response message context (the axis2 MessageContext instance) before it is updated with the custom error message. For example, you might want to send emails or perform custom alerts based on the response payload. For more information about IS services, see The Invoke IS Service Step (Inbound, SOAP).
*Post-Processing: Select this option if you want to invoke an IS service to manipulate the service fault after the Error Sequence step is invoked. The IS service will have access to the entire service fault and the custom error message. You can make further changes to the fault message structure, if needed. For more information about IS services, see The Invoke IS Service Step (Inbound, SOAP).