Deploying Virtual Services and Connector Virtual Services
Overview of Deployment
You can deploy virtual services and Connector Virtual Services 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.