CentraSite Documentation : Runtime Governance with CentraSite : Virtualized Services in CentraSite : Deploying and Undeploying Virtualized Services to Targets : Who Can Deploy Virtualized Services to Targets?
Who Can Deploy Virtualized Services to Targets?
To deploy virtualized services to targets, you must belong to a role with the following permissions:
*Create Assets —OR— Manage Assets
*Manage Runtime Policies (required to configure virtualized services)
*Manage Lifecycle Models (required to change state of virtualized services)
*Mediator Publisher (required to deploy virtualized services)
For more information about roles and permissions, see Getting Started with CentraSite.
Note:  
Mediator exposes several Web service operations to allow CentraSite to manage deployed assets. This Web service is invoked by CentraSite any time a user deploys or undeploys a virtual service to Mediator. A Mediator's configuration details page includes the User Name and Password fields which identify an Integration Server user who is permitted to execute the Integration Server services associated with Mediator's deployer service. After installation, only members of the Integration Server “Administrators” group are allowed to invoke these services. However, administrators have the flexibility to allow their own users or groups to invoke them. Access to these services is controlled by an ACL, called MediatorDeployer. Initially, only the predefined “Administrators” group is assigned to this ACL. An Integration Server administrator can remove this group and add other groups or individual users. For example, you can create your own deployer group, (for example, “MyDeployers”) and add Integration Server user IDs to this group. Then, the user must update the MediatorDeployer ACL by removing the “Administrators” group and adding the “MyDeployers” group. Now, on the target's configuration detail page, you can specify any user ID that belongs to “MyDeployers” group.
The API management platform of CentraSite Business UI allows you to publish Service assets (also, termed as API assets) and Virtual Service assets (also, termed as Virtual API assets) to and from the webMethods Mediator and webMethods API-Portal gateways.
Axis Free Mediation
Axis Free Mediation and WSStack are used to process REST services. The advantage of using Axis Free Mediation is that it supports HTTP patch. However, by default, WSStack is used.
Axis Free Mediation is specified by selecting the VSD format. When a new REST service is published, CentraSite publishes the service to the Axis Free Mediation. When a service is republished, CentraSite considers the mediation stack that the service has been published to. Therefore, republishing a service does not modify the mediation stack of a service.
Note:  
The republished services do not show any different behavior because of switching between the mediation stack. However, if CentraSite is publishing a service to Mediator 9.10 or earlier versions, it publishes and republishes the REST services to the WSStack Mediation stack.
To change the deployment method for REST services, the restServiceStack configuration parameter in the centrasite.xml file has to be set. By default the configuration parameter is set to wsstack. When changing it to Axis-free, any newly published REST service goes to Axis Free Mediation. Redeploying a REST service is not sufficient to change the mediation stack. To change the mediation stack for an already deployed service, it has to be unpublished first and then republished.
Copyright © 2005-2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback