What Happens When You Deploy a Virtualized Service?
When you deploy a virtualized service to one or more Mediator gateways, keep the following in mind.
CentraSite automatically validates the service's run-time policy (or policies) to ensure that:
Any action that appears in a single policy multiple times is allowed to appear multiple times.
All action dependencies are properly met.
CentraSite will inform you of any violation, and you will need to correct the violations before deploying the service. For more information about dependencies and which actions can be included multiple times in a single policy, see
Built-In Run-Time Actions Reference for
Virtual Services.
You must make modifications to deployed assets in CentraSite. If you need to modify a virtualized service that is already deployed, you must modify it in CentraSite and then redeploy it to Mediator. Mediator does not monitor CentraSite for updates to deployed assets. If you make changes to a virtual service's processing steps, for example, you must manually redeploy the virtual service to put those changes into effect.
You cannot make changes to a run-time policy while it is active. To make changes to a policy after it has been switched to the active state you must do one of the following:
Switch the policy to the Suspended state (to deactivate it), update the policy and then switch it back to the Productive state (to reactivate it).
OR
Create a new version of the policy, make your changes to the new version of the policy and then switch the new version to the Productive state. Switching the new version of the policy to the Productive state will automatically Retire (and deactivate) the old version.
If you need to update a run-time policy that is already deployed with virtual services that are in production, always use the second method described above (i.e., create a new version of the policy). If you use the first method, which requires you to suspend the existing policy, your production services will be running without the policy while you are making your revisions to it.
When you deploy a virtualized service, CentraSite generates a VSD. When you deploy a virtualized service to a Mediator, CentraSite generates an XML document called a virtual service definition (VSD). The VSD defines the virtualized service for Mediator, and contains all the run-time policies and resources required to deploy the virtualized service to Mediator.
You should not manually edit the endpoint information for virtualized services. CentraSite automatically updates the service’s CentraSite endpoint to its Mediator endpoint. You can view the Mediator endpoint on the virtualized service's detail page in CentraSite. Because the endpoint information for virtualized services is generated and updated by CentraSite, unlike when managing native services, you should not manually add endpoints to a virtualized service. Instead, allow CentraSite to generate and manage the endpoints for the virtualized services that you deploy.
However, you can deploy multiple virtualized services for a single native service to make the service available over multiple transports and/or security mechanisms. For details about managing endpoints, see Getting Started with CentraSite.
If deployment fails, the status is set to “Failed” and the failure is logged. If Mediator encounters a problem deploying or redeploying a virtualized service, it sets the service's Deployment Status to “Failed” and sends a message to CentraSite describing the problem. This failure is also logged to Mediator. In this case, it is up to the CentraSite or Mediator administrator to take corrective action and redeploy the service manually from CentraSite.
If the reason for the failure is that the Mediator instance is unavailable, and then you restart the Mediator instance, it loads all information about any previously deployed assets.
