Before you develop your service, you should consider the type of binding strategy you want to use. The strategy you choose will depend on your environment.
An endpoint is a key part of a service because it defines the implementation with which operations used in the service can interact.
Endpoint binding is the process that associates the logical design of a service to an endpoint and, thus, a specific implementation. Multiple endpoints can be defined for a particular service, but before deploying the service, you bind the service to a specific endpoint.
Sybase WorkSpace provides flexibility to complete or modify endpoint bindings during the development process. Bindings can be set and modified during the service development, packaging, or deployment phase.
Service Development Binding
Endpoint binding is defined using the service editor. Binding defined during service development is:
Saved as part of the service definition.
Carried forward through packaging and deployment unless the binding is modified during package definition or during deployment definition.
Package Profile Binding
Endpoint binding is defined using the Endpoint Configuration page of the Services Package Profile editor. Binding defined during package profile definition:
Overwrites a binding defined in a service profile.
Is saved as part of a package profile.
Is not saved to a service profile.
Can be further modified during creation of the deployment profile.
Deployment Profile Binding
Endpoint binding is defined using the Configuration page of the Deployment Profile editor. Binding must be defined here if is has not been defined during service development or during package profile definition. Binding defined during deployment profile definition:
Overwrites binding defined in a service profile or a package profile.
Is saved as part of the deployment profile.
Does not save to a service profile or to a package profile.
Service Development Binding and Deployment Profile Binding:
In this example, you are developing a single service that will be deployed multiple times with the same endpoint in a test environment before deploying the service one final time to a runtime environment. The binding strategy could a combination of Service Development Binding and Deployment Binding.
Service Development Binding binds the service to the endpoint in a test environment and this setting is maintained through multiple iterations of test deployment. The service definition stores the binding information, eliminating the need to define the binding each time the package is created or each time the package is deployed in the test environment.
When the service is then deployed to a runtime environment, the binding is set and maintained using Deployment Profile Binding. Whenever the package is deployed using the runtime deployment profile, the runtime binding overrides the binding in the service profile.
Package Profile Binding
In this example, you are developing multiple services that will be packaged together. The services will be reused for other packages as well.
Using a Package Profile Binding strategy allows you to develop the services independent of any binding settings and move management of binding to the package level. By using this strategy, binding is set in the package profile.
Deployment Profile Binding
In this example, a single package is deployed to multiple servers, each using a different endpoint, or multiple packages are deployed to the same server.
The Deployment Profile Binding allows you to bind to the endpoint a single time during deployment profile definition rather than for each service or for each package.
Service Development Binding or Package Profile Binding: If you are deploying a package in an environment outside the Sybase WorkSpace deployment framework, such as using the command link interface of the Unwired Service Command and Control component. In this case, you must bind during service development or during package profile definition.
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com