Step | For procedures, see... |
1. Using the Software AG Installer, install the CloudStreams Server and the Software AG MashZone NextGen server. The Software AG MashZone NextGen Server is required only if you plan to use CloudStreams Analytics. Also, download the CloudStreams Provider (such as the Salesforce.com Provider) from the Software AG TECHcommunity website. Note: From the 9.7 release, CloudStreams providers and provider user guides are available for download from the TECHcommunity website. The provider installation guide is available in the CloudStreams section of the Software AG Documentation website. |  The document Installing Software AG Products.The documentation specific to your CloudStreams provider (for example, webMethods CloudStreams Provider for Salesforce.com Installation and User's Guide). |
2. Create a cloud connection and configure the session management parameters, using the Integration Server Administrator. | The documentation specific to your CloudStreams provider. |
3. Create a cloud connector service for each desired operation defined in the cloud provider's WSDL, or for each desired REST resource, using the Software AG Designer's Service Development plug-in. | The documentation specific to your CloudStreams provider. |
4. Set the CloudStreams configuration options to specify things such as the keystore, truststore and ports to use, the database to use for publishing performance metrics and events, the consumer applications that can access CloudStreams, and more. | |
5. Define a CloudStreams Server target, which specifies an instance of a CloudStreams server to which you will deploy your virtual services and any optional custom connector virtual services. You do this using Software AG Designer. You can define one or more server targets. | |
6. Create a CloudStreams Governance project in which you will create the virtual services, connector virtual services, and their policies. You create projects in your local file system, using Designer's CloudStreams Development plug-in. You can create one or more projects. | |
7. In the CloudStreams Governance project, create virtual services and connector virtual services. You do this using Designer's CloudStreams Development plug-in. You will: Create virtual services to handle the inbound requests.Optionally override the default connector virtual services with custom ones to handle outbound requests. CloudStreams provides a default connector virtual service for each metadata handler (which you cannot modify), but you can create additional connector virtual services with custom policies, if desired. | |
8. In the CloudStreams Governance project, create policies for the virtual services, using Designer's CloudStreams Development plug-in. For the virtual services, you create policies that include WS-SecurityPolicy actions (and other actions) provided by CloudStreams.For the connector virtual services, CloudStreams provides a default policy that logs all outbound transactions. You cannot modify these policies, but you can create additional connector virtual services with custom policies that include the monitoring, logging, and schema validation actions. | |
9. Deploy the virtual services and any custom connector virtual services to a package in a CloudStreams server target. | |
10. Configure CloudStreams Analytics to monitor performance metrics and run-time events. |