An endpoint represents an instance or implementation of a
particular resource type.
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 define
a default endpoint using the New Endpoint wizard when you are developing a service, services package profile, or deployment profile. You can add endpoints when developing a services package profile.
- You can define an endpoint
to be logical or physical:
- A logical endpoint,
designated in red, serves as a placeholder. You must redefine a logical endpoint as a physical endpoint before service deployment.
- A physical endpoint,
designated in orange, defines the actual connection configuration to a server,
database, queuing system, Java class, or resource that is used by the service. The
endpoint implementation varies based on the type of service.