To run a message service, you must configure a way to connect to the external messaging system. An endpoint provides this connection, or binding, between the service and the external messaging system.
Consider the following:
Each message service interface can have one endpoint.
Adding an endpoint is optional during service development. Endpoints can be added to a service during service development, or later in the process during package definition or deployment definition. Additionally, if an endpoint is added during service development, the endpoint binding can be modified during package definition and/or during development.
Before adding a service endpoint to your service, review choosing an endpoint binding strategy. It is important that you understand the implications of binding endpoints at the various times.
For information about working with endpoints during the packaging phase, see Configuring Endpoints for a Services Package Profile.
Some endpoint types can be configured and grouped as connection profiles. You can create a connection profile for FTP, File and JMS messaging types. The messaging transport connection profiles can be used to quickly add endpoints to services.
If you are planning to use an EAServer JMS transport as the message service endpoint, it is recommended that you define queues instead of using the EAServer default queues. See the EAServer 5.2 Core Documentation for additional information about using EAServer Manager to add a message queue.
To add an endpoint to a message service:
Choose from the following methods:
Drag-and-Drop from a Connection Profile: Use this method if you have a connection profile readily available.
Select the Service Interface page in the service editor.
In the Enterprise Explorer, expand the Message Transports node to locate the connection profile.
If a connection has not been made, right-click and select Connect to connect to the server and display its queues.
Click to select the queue to be used as the service endpoint.
Drag the endpoint from the connection profile in the Enterprise Explorer to the interface object in the service diagram.
The endpoint graphically displays in the service diagram.
Use the New Messaging Endpoint Wizard: Use this method if you are adding an Email messaging type endpoint, if a connection profile is not available, or if you want to add a logical endpoint.
Select the Service Interface page in the service editor.
Right-click on the Interface page and select Add Endpoint
The New Messaging Endpoint wizard opens to guide you through adding a new messaging endpoint.
Select the endpoint type: Server or Logical.
Provide a meaningful name for the endpoint and click Next.
Select the messaging type. Click Next.
Specify the connection properties for the messaging type. Click Next.
Select Reference from Enterprise Explorer to specify the endpoint defined by an FTP, File, or JMS connection profile. Click Browse to locate the appropriate connection profile.
After the connection profile is selected, the table displays the profile's connection properties so that you can verify they are correct.
If you are using a JMS connection profile, verify that the Initial Context Factory and Queue Connection Factory properties are correct for your JMS provider type and site implementation. Some JMS providers allow multiple names for these properties.
Enter User Specified connection properties. You must use this option to define connection properties for Email messaging types.
Set the runtime properties for the messaging type. The Runtime Properties that can be set depend on the properties for the messaging type.
Review the information on the Summary page and click Finish.
The endpoint is added to the interface.
To edit an endpoint for a message service:
Right-click on the endpoint in the Service Interface diagram and select Edit Endpoint. The Edit Messaging Endpoint Wizard opens.
Complete the Edit Messaging Endpoint Wizard and click Finish to complete the changes.
As you work through the wizard, verify that the Endpoint Name is set correctly by the wizard.
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com