webMethods and Intelligent Business Operations 10.2 | Integrating Cloud Applications | Administering CloudStreams | Virtual Services | Creating a New Virtual Service (REST) | The "In Sequence" Step (REST) | The "Invoke IS Service" Step (Inbound, REST)
 
The "Invoke IS Service" Step (Inbound, REST)
This optional step invokes a user-defined Integration Server flow service. You can invoke an IS service in:
*The "In Sequence" step, to pre-process the request message before it is submitted to the native service.
*The "Out Sequence" step, to pre-process the response message from the native service before it is returned to the consuming application.
The IS service you invoke must be running on the same Integration Server as CloudStreams. It can call out a C++ or Java or .NET function. It can also call other IS services to manipulate the SOAP message.
You can use predefined or custom context variables in an IS service. For more information, see Using Context Variables in IS Services.
You can create multiple "Invoke IS Service" steps.
* To add the "Invoke IS Service" step (inbound, 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 virtual service name.
3. Right-click In Sequence and click Invoke IS Service.
The "Invoke IS Service" step is added under the Entry Step (and under a Transform step, if one exists). You cannot change the order of the steps.
4. Click Invoke IS Service and complete the following fields in the General page in the Properties view.
Option
Description
Name
You can optionally change the step name to any other name. There are no naming restrictions.
Type
(Read-only.) Invoke IS Service.
Service
Specify the IS service to pre-process the request message before it is submitted to the native service.
5. When you define the IS service, the Pipeline In section of the flow should have the following input variables:
*proxy.name: This is the name of the virtual service.
*SOAPEnvelope: This is of the Java type org.apache.axiom.soap.SOAPEnvelope.
*MessageContext: CloudStreams will automatically place a MessageContext variable into the pipeline before executing the IS service call. MessageContext is of the Java type org.apache.axis2.context.MessageContext.
Integration Server users can use the Axis2 MessageContext object to manipulate the incoming SOAP request. The Integration Server provides built-in services (the pub.soap.* services) to work with the MessageContext object to get/set/modify the SOAP body, header, properties, etc. Integration Server users should use these services to extract the information they need from the MessageContext to build the necessary business logic. Users do not need to understand Axis2 or Axiom (the xml object model based on StAX) to work with the SOAP request, because if they are familiar with the Integration Server pub.soap.* services, they can accomplish most of the tasks. For more information about these related Integration Server services, see the webMethods Integration Server Built-In Services Reference.
6. To create an additional "Invoke IS Service" step, right-click In Sequence and select Invoke IS Service again.
7. To delete an "Invoke IS Service" step, right-click Invoke IS Service and click Delete.
Copyright © 2015- 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release