A cloud connector service defines an interaction that the connector will perform on the SaaS back end. The cloud connector service is analogous to any other Integration Server service and could be used in a flow service. You call a cloud connector service within a flow service and you can audit them from the audit system of Integration Server.

A cloud connector service has input and output signatures. An input signature describes the data that the service expects to find in the service pipeline at run time. An output signature describes the data that the service expects to add to the pipeline when it has successfully executed. You can view the node signature of a cloud connector service on the Input/Output tab of the cloud connector service editor in Software AG Designer. Before configuring a cloud connector service, you must assign it a connection that you created earlier.

A cloud connector service is based on the interaction definitions defined in the connector and contains appropriate logic for executing the interaction and getting the response from the back end.

Based on the connector type, cloud connector service definitions allow you to configure the interactions. For REST, you need to define the Resource, HTTP Headers, and parameters. For SOAP, you need to define the Operation, SOAP Headers, and custom parameters, if any.

You can create a cloud connector service using a wizard in Software AG Designer. See the documentation specific to your CloudStreams provider, for example, webMethods CloudStreams Provider for Salesforce.com Installation and User's Guide.