webMethods and Intelligent Business Operations 10.2 | Integrating Cloud Applications | Administering CloudStreams | Overview | About CloudStreams | Inbound Architecture
 
Inbound Architecture
In the inbound run-time scenario, a SaaS application invokes an on-premises application through CloudStreams as follows:
Step
Description
1
A SaaS application invokes a virtual service that has been deployed to CloudStreams. The virtual service's policy performs security checks and any other user-defined processing before sending the request to the on-premises application.
2
The virtual service invokes a service endpoint (an Integration Server flow service or a Java service) in the on-premises application.
3
The endpoint service then invokes the on-premises application service(s).
4
The on-premises application processes the request against the native service and sends a response back to the SaaS application.
5
The CloudStreams server collects run-time metrics and events, and publishes them to the CloudStreams Analytics facility, which is powered by Software AG MashZone NextGen Server. You can use the CloudStreams Analytics dashboard to monitor the metrics.
6
The virtual service logs the request/response transaction and its payload.
Note: See Cloud Connections and Services for more information on CloudStreams providers, connectors, cloud connections, cloud connector services, and how to manage cloud connectors and cloud connector packages.

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