Publishing the Test Endpoint for a Virtual Service on the Consumption Registry
In the consumption CentraSite, the catalog entry for a native service provides consumers with bindings to the test instance of the service and to the production instance of the service. However, with a virtual service, you cannot do this. The set of bindings for a virtual service are generated and managed automatically by CentraSite, and you cannot manually add bindings to this set.
If you have a test instance of a virtual service deployed on the Mediator in your test environment, and you would like to disclose that endpoint to users when they view the virtual service in the registry, you can identify the endpoint in a separate attribute (that is, as additional metadata) within the virtual service on the consumption CentraSite.
Note: | If you have consumer applications that will dynamically bind to a virtual service, be aware that those applications will need to bind against the creation CentraSite during the testing phase of their development and against the consumption CentraSite when they enter production. |
