Designer 10.7 | Cloudstreams Development Help | CloudStreams Governance Project | Deploy
 
Deploy
You can deploy Virtual Services and Connector Virtual Services to CloudStreams server targets in two ways:
*Deploy all Virtual Services, and any custom Connector Virtual Services, that are contained in a particular CloudStreams Governance project.
OR
*Deploy a single Virtual Service or custom Connector Virtual Service. Generally, this is useful for testing purposes.
Note:
CloudStreams does not support sharing of Connector Virtual Services, Virtual Services, and Policies across nodes in a clustered setup. These artifacts should be manually deployed to a clustered node as needed.
Note:
CloudStreams automatically deploys the default Connector Virtual Services WmCloudStreams.SoapVS and WmCloudStreams.RestVS; there is no need for you to deploy them.
When you execute the deployment operation, CloudStreams will immediately deploy the service(s) and the following items to the CloudStreams server target(s) that you specify:
*The policies of each service, as well as any other artifacts that you associated with the services when you created them.
*The VSD (virtual service definition) of each virtual service or connector virtual service.
When you deploy a Virtual Service or a Connector Virtual Service, CloudStreams generates an XML document called a virtual service definition (VSD). The VSD defines the virtual service or connector virtual service for CloudStreams, and contains all the resources required to deploy the service to a CloudStreams server, including the policy that applies to the service. You cannot edit the VSD, but you can view it in the Advanced page in the Properties view of each service.
Before you deploy a virtual service, you should:
*Ensure that all policies of the services are Active; the value of the Status field in the Properties view of each policy should be Active. If it is not, right-click the policy name in the CloudStreams Governance view and click Active. You will not be allowed to activate a policy unless all of its action parameters have been set.
*Ensure that at least one CloudStreams server target has already been defined, as described in Add CloudStreams Servers Dialog Box.
*Ensure that the server's specified deployment URL is active and the user credentials of Integration Server are valid.
*Test the server connection from the Designer menu by clicking Window > Preferences > Software AG > CloudStreams Servers and using the Test button. If the connection is not active and valid, activate the deployment endpoint and modify the user credentials as required.
If CloudStreams encounters a problem deploying or redeploying a service, it displays a failure message, which is logged to the deployment log at the bottom of the page. In this case, it is up to the CloudStreams administrator to take corrective action and redeploy the service. If the reason for the failure is that the CloudStreams server is unavailable, and then you restart the CloudStreams server, it loads all information about any previously deployed services. For more information, see the topic What Happens When You Deploy a Service? in the document Administering webMethods CloudStreams.
To deploy all services in a CloudStreams Governance project:
When you deploy a CloudStreams Governance project, all virtual services in the project are deployed at once. If any custom connector virtual services are defined in the project, they are deployed too.
When you deploy a project, Integration Server automatically creates a package to support the project. The package name is the same as your project name. This package includes startup/shutdown services to manage the registration of the virtual service definitions (VSDs) when Integration Server restarts.
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, right-click the project you want to deploy and click Deploy.
3. In the Deploy dialog box, choose one or more CloudStreams server targets to which to deploy the services and click OK. The services are immediately deployed.
If only one CloudStreams server target is available to select, this dialog box will not appear.
The services are immediately deployed to the following location:
IntegrationServer_directory\packages\<PackageName><ProjectName\config\proxies\VirtualService
To deploy a single virtual service or connector virtual service:
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, right-click the service name you want to deploy and click Deploy.
3. In the Deploy dialog box, choose one or more CloudStreams server targets to which to deploy the service and click OK. The service is immediately deployed.
If only one CloudStreams server target is available to select, this dialog box will not appear.
The service is immediately deployed to the following location:
IntegrationServer_directory\packages\<PackageName><ProjectName\config\proxies\VirtualService