Masking Native OData Service
Mediator supports masking of the native OData service. This is used to hide the native service from the consumers.
To mask the native OData service URLs, you must:
1. Process OData metadata and service document: The resources exposed by a virtualized OData service may be restricted when compared to a set of resources exposed by the native OData service. Therefore, the virtualized OData service must not expose the service and the metadata document of the native service. This virtual OData service consists of its own service and metadata document. Service or metadata document requests are then intercepted by Mediator and the service or metadata document of the virtual service is returned to the requester. The metadata document URL of an OData service is returned by appending “$metadata” to service root URL. The service document URL of an OData service is returned by a GET request to the service root. The document is returned in JSON format and in Mediator a version string is added to the service root URL. For example,
http://hostname:portnumber/service/ to http://hostname:portnumber/mediator/V-Cars/1.0/
and
http://host/service/$metadata is appended by http://<mediator_host:port>mediator/V-Cars/1.0/$metadata
2. Rewrite the URL in the OData response payload: An OData service response contains URLs like the OData context URL pointing to the native services. These URLs are rewritten to relative URLs by removing the native service information. For example,
"http://daefermion3:8080/odata-server-sample/cars.svc/$metadata#Cars" is replaced by "$metadata#Cars"
Contact Support
|
Community
|
Feedback