Services Package Profile Endpoints

Each service in a services package profile must be bound to an endpoint.

For both the Sybase Services Package Profile editor and the EAServer Services Package Profile editor, use the Endpoint Configuration page to modify existing endpoint bindings that were defined during service development. If a service was defined with a logical endpoint, it must be bound to a physical resource before you can deploy the package.

Select the service in the Included Services section and make the changes in the Endpoint Bindings section. The Endpoint Configuration page of the Sybase Services Package Profile editor or the EAServer Services Package Profile editor is divided into the following sections:

Table 1. Endpoint configuration page
Section	Description
Included Services	Lists all of the services included in the package profile. When you click to select a service, the contents of the Endpoint Bindings section changes.
Endpoint Bindings	Displays each interface defined for the selected service. If the service has been bound to an endpoint, this information is displayed.
Endpoints	Provides a cumulative listing of all endpoints defined for services in the package profile. The endpoint type and project location of the endpoint profile is noted.

Changes that you make to the endpoint configuration on this editor page are reflected in the package profile file (<file name>.svcpkgdef for services or <file name>.axispkgdef for EAServer) in the WorkSpace Navigator. Endpoint configuration defined for the package profile is not reflected in the service profile.

CAUTION:

Connection profile properties can be modified after developing a service bound to an endpoint associated with the connection profile. At the time the services package is created, packager attempts to refresh connection properties while generating the meta-data within ear files for packages containing such services. For the refresh to succeed, certain connection profile types and transports that can be used as endpoints, such as JMS, require that the server identified by the profile be accessible.

If the server is unavailable, as is the case when the server is down or the when the server subnet is not reachable, the packager uses the original connection properties and issues a warning message identifying the problem.

An unsuccessful refresh of the properties can cause a deployed package to not operate as expected.