CentraSite Documentation : Getting Started with CentraSite : Implementation Concepts : Managing Endpoints : Managing the Endpoints of a Native Service over its Lifecycle
Managing the Endpoints of a Native Service over its Lifecycle
 
Example of the Bindings for a Service in a Single-Stage Registry
Example of the Endpoints for a Service in a Two-Stage Registry
When a native service moves through its lifecycle, it usually gains additional endpoints. For example, during development, a developer generally deploys the service somewhere in the development environment. When the service moves to the testing phase, it is generally deployed at another endpoint for testing. Finally, when the service is placed in production, the operations organization deploys the service at an endpoint in the production environment.
Each time you deploy a native service to an additional endpoint, you must add the new endpoint to the service in CentraSite. To do this you:
1. Download the service WSDL from the CentraSite registry.
2. Add the endpoint to the WSDL (as an additional port definition).
3. Reattach the updated WSDL to the service in CentraSite.
When you attach the updated WSDL to the service, CentraSite will automatically update the binding information on the service's Operations panel.
Note:  
Although it is possible to represent the development, test, and production endpoints as individual services in the registry, we recommend that you avoid doing this. Such an approach produces a large amount of duplicated metadata and does not return any real benefits. Instead, maintain just one catalog entry for a native service and add the service endpoints to this entry as the service progresses through its lifecycle.
Copyright © 2005-2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback