Use the New Service wizard to create a new message service.
To create a message service:
In the Service Development perspective, Select File|New|Service from the menu bar. For other ways to access the New wizard, see Methods of Accessing New Wizards.
The New Service wizard opens.
Select Message Service from the Service Selection Page and click Next.
Select the project that uses this service. Name the new service file with a unique and descriptive name, and click Next.
From the Service Overview page, use the following information to complete the process of creating a message service.
The Service Type Information pane is automatically completed.
In the Service Information pane, complete the following:
Service Information
| Field | Description |
|---|---|
| Name | Edit the file name. The wizard automatically enters the same name as the service file in your project. It is recommended that you keep the names consistent for easy reference in the future. |
| Category | Enter a new category, or select an existing category from the drop-down list. Note: If you plan to create multiple services, it is recommended that you group services into meaningful categories. |
| Description | Provide an internal description, such as an explanation of how and where this service is used. You can also add notes for other developers who may be implement this service. |
Choose one of the following:
From the Service Overview page, click Finish to complete the service creation. The service file appears in the Navigator and the Message Service editor opens. You can now use the editor to define the message service interface.
or
Click Next to continue in the wizard to Service Binding Creation.
Select one of the following and click Next. For additional information about endpoint binding, see Choosing an Endpoint Binding Strategy.
Yes, create an endpoint now. Creating a service binding at this point is optional. Choose this option if you know the following:
The endpoint to which the service is to be bound.
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.
That a connection profile has been defined or the connection property values for the messaging type.
The values for runtime properties for the messaging type.
If you create an endpoint now for the service, you can change the binding to another endpoint later during services package profile development or deployment profile development.
No, create an endpoint later. Choose this option if you do not know the endpoint to which the service is to be bound.
If you choose this option and after clicking Next, review the information on the Summary page and click Finish. To edit a value, click Back.
Enter a name for the endpoint. 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.
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 service file appears in the Navigator and the Message Service editor opens. You can now use the editor to define the message service interface.
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com