Adding Virtual OData Service to Your Asset Catalog

To create and manage Virtual OData Service asset in CentraSite Business UI, you must have the following permissions:

CentraSite Administrator

Organization Administrator

Service Runtime Provider (required to configure run-time actions for the Virtual OData Services)

Mediator Publisher (required to publish Virtual OData Services to Mediator gateways)

API Portal Publisher (required to publish Virtual OData Services to API Portal gateways)

Instance-level Modify permission for a gateway (required to publish Virtual OData Services to that particular gateway)

If you have the CentraSite Administrator role, you can create and manage Virtual OData 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 OData Services within that specific organization.

The following general guidelines apply when adding a Virtual OData Service asset in CentraSite Business UI:

Ensure that the interface for the Native OData Service is completely implemented and that the interface is reflected in the EDMX file that is registered for the service in the CentraSite repository.

An instance of the OData Service is deployed and running at a known point in network.

The metadata for the Native OData Service is valid and up-to-date. If the metadata for the Native OData Service has not been completely specified or is out-of-date, you should update it before you generate the Virtual OData Service so that you do not carry inaccurate or incomplete data into the Virtual OData Service.

In CentraSite Business UI, you can add a Virtual OData Service asset to the catalog in the following ways:

You can create a Virtual OData Service from an existing OData service, also called as a (Native) OData Service in CentraSite, meaning that you create the virtual copy (proxy) of the existing OData Service using an already imported input file.

You can create a Virtual OData Service using an importer, which is a utility that generates the Virtual OData Service from an imported archive file.

You can create a Virtual OData Service using a command line tool, which is a utility that generates the Virtual OData Service from an input EDMX file.