Endpoints

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 endpoints, but all message endpoints are similar.
You can also define endpoints using the endpoint wizard while you are developing a service, developing a services package profile, or developing a deployment profile.
Endpoints are either logical or physical:
- A logical endpoint is used as a placeholder that must be replaced by a physical endpoint before the service can be deployed. That replacement is performed by a developer who substitutes the name of the actual endpoint or determined by environmental information such as information within the message.
  The default color for logical endpoints is red. The default color for a highlighted logical endpoint is purple. The colors can be changed in Windows|Preferences|Sybase|Services|Service Editor Colors.
- A physical endpoint is the server, database, queuing system, or Java class used by the service. The physical implementation of the endpoint varies based on the type of service. See Endpoint Types.
  The default color for physical endpoints is orange. The default color for a highlighted physical endpoint is light orange.

For information about when to add an endpoint, read Choosing an Endpoint Binding Strategy.

For information about working with endpoints during the packaging phase, read Configuring Endpoints for a Services Package Profile.

For information about working with endpoints for service types that must have endpoints configured before they are functional, refer to the following:

Creating a File Connection Profile

Creating a Monitor Connection Profile

Creating an FTP Connection Profile

Creating a UDDI Registry Connection Profile

Creating an EAServer Connection Profile

Creating a JDBC Connection Profile

Creating a JMS Connection Profile

Creating a Sybase ASA Connection Profile

Creating a Sybase ASE Connection Profile

Creating a Service Container (EAServer) Connection Profile

Using the Default Connection Profiles