An endpoint represents an actual instance or implementation of a particular resource type. It specifies which implementation is used when an operation with a service is called. Before you can run a service or business process, you must configure a way for the service to connect to an implementation. Endpoints are key to the functioning of a service or business process because they define a service connection to the implementation with which the service operation interacts.
You can create and manage an inventory of connection profiles for specific endpoint types, such as database and message transport. Endpoints are classified according to their underlying technology. For example, database endpoints are distinct from message transport endpoints, but all message transport endpoints are similar in nature.
You can also define endpoints using the New Endpoint wizard while you are developing a service, developing a services package profile, or developing a deployment profile.
You can define an endpoints to be logical or physical:
A logical endpoint, designated in red, serves as a placeholder. A logical endpoint must be redefined as a physical endpoint before service deployment.
A physical endpoint, designated in orange, defines the actual connection configuration to a server, database, queuing system, or Java class that is used by the service. The endpoint implementation varies based on the type of service. See Endpoint Types for more information.
To redefine the endpoint color designation, go to Windows|Preferences|Sybase|Services|Service Editor Colors.
See Choosing an Endpoint Binding Strategy for information about when to add an endpoint.
See Configuring Endpoints for a Services Package Profile for information about working with endpoints during the packaging phase.
See the following for information about working with endpoints for service types that must have endpoints configured before they are functional:
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com