Software AG Products 10.7 | Using CentraSite | Runtime Governance | Virtual Service Asset Management | Managing Virtual Service Assets through CentraSite Business UI | Virtual Service Management | Adding Virtual Service to Your Asset Catalog
 
Adding Virtual Service to Your Asset Catalog
To create and manage Virtual (SOAP) Service asset in CentraSite Business UI, you must have the following permissions:
*CentraSite Administrator
*Organization Administrator
*Asset Provider
*API Runtime Provider (required to configure run-time actions for the Virtual Services)
*Mediator Publisher (required to publish Virtual Services to Mediator gateways)
*API Portal Publisher (required to publish Virtual Services to API Portal gateways)
*Instance-level Modify permission for a gateway (required to publish Virtual Services to that particular gateway)
If you have the CentraSite Administrator role, you can create and manage Virtual Services within any organization.
If you have the Organization Administrator role or API Portal Administrator role for a specific organization, you have the ability to create and manage Virtual Services within that specific organization.
The following general guidelines apply when adding a Virtual Service asset in CentraSite Business UI:
*Ensure that the interface for the Native Service is completely implemented and that the interface is reflected in the WSDL or schema file that is registered for the Web Service in the CentraSite repository.
*An instance of the Web 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 or incomplete data into the Virtual Service.
In CentraSite Business UI, you can add a Virtual Service asset to the catalog in the following ways:
*You can create a Virtual Service from an existing Web Service, also called as a (Native) Service in CentraSite, meaning that you create the virtual copy (proxy) of the existing Web Service using an already imported input file.
*You can create a Virtual Service using an importer, which is a utility that generates the Virtual Service from an imported archive file.
*You can create a Virtual Service from scratch, meaning that you create the Virtual Service (and set its attributes) manually.
*You can create a Virtual Service using a command line tool, which is a utility that generates the Virtual Service from an input WSDL file.