SOA Governance and API Management : Run-time Governance with CentraSite : Virtualized Services in CentraSite : Creating Virtual Services
Creating Virtual Services
 
Creating a Virtual Service from Scratch
Virtualizing an Existing Service
Generally speaking, you should ensure that the following conditions are satisfied before you create a virtual service:
*Ensure that the interface for the native service is completely implemented and that interface is reflected in the WSDL or schema file that is registered for the service in the CentraSite registry.
*An instance of the service is deployed and running at a known point in network.
*The metadata for the native service is valid and up-to-date. If the metadata for the native service has not been completely specified or is out-of-date, you should update it before you generate the virtual service so that you do not carry inaccurate/incomplete data into the virtual service.
*This is of specific relevance to virtual REST and XML based service assets. Beginning with version 9.7, CentraSite Control does not support the following out-of-the-box asset types: REST Service, XML Service, Virtual REST Service, and Virtual XML Service. This is because, CentraSite Control does not support the enhanced interface for REST and XML service assets (in contrast, earlier versions of CentraSite Control supported a standardized interface for REST and XML service assets). Documentation of the prior REST and XML service interface is available to Software AG customers who have a current maintenance contract in Empower, Software AG's global extranet (http://empower.softwareag.com/).
Therefore, you cannot create virtual instances of the asset types REST Service and XML Service using the CentraSite Control user interface. Instead, you can create them by using the CentraSite Business UI.
There are two ways to virtualize a service in CentraSite Control.
Copyright © 2015- 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback