As part of developing a message service, you must define operation properties for each operation in the message service.
Operation Properties appear in the Properties section of the Service Interface page when an operation is selected in the service interface diagram.
Properties for the General tab are always available for a service operation.
Properties for the Operation Context and Wire Format tabs are specific to the messaging type of the message service endpoint. These operation properties are available only if an endpoint has been added to the service.
If you are planning to expose the operation via a JMS transport, operation context properties set by the inbound transport, JMS or email, cannot be overwritten by operation context properties set in the message service. The property fields are editable in the message service editor, however, the output message retains the original property values as set by the inbound transport.
If the endpoint type is File or FTP, there are no Operation Context properties.
To edit the properties of an operation:
In the Message Service Editor, click the Service Interface tab.
The Message Service Interface page appears.
In the Service Interface diagram, click to select the operation box.
In the Properties section or Property Panels view, edit the following information:
General
Property | Description |
---|---|
Name | Rename the operation. |
Description | Provide an internal description, such as an explanation of this operation. |
Input Message Name | Field is automatically populated with a default value and used when generating the WSDL for a service. Careful consideration should occur before editing this field to alter the name in WSDL. Modifying the Message Name can be useful in some very specific use-cases, such as in Business Process to reuse the same internal WSDL message for more than one operation; this can be an optimization to prevent the copying of messages unnecessarily. |
Output Message Name | Field is automatically populated with a default value and used when generating the WSDL for a service. Careful consideration should occur before editing this field to alter the name in WSDL. Modifying the Message Name can be useful in some very specific use-cases, such as in Business Process to reuse the same internal WSDL message for more than one operation; this can be an optimization to prevent the copying of messages unnecessarily. |
Visible | Identifies whether the service operation is visible or not visible. Only service operations that are defined to be visible can be exposed when the service is made publicly accessible. |
Custom Properties | Add and remove custom properties as needed. |
Operation Context: Email
Property | Description |
---|---|
Attachments | Defines attachment files for the email message. Click ... to open the Edit Attachments dialog. Click Add to browse to locate an attachment. Select an attachment and click Remove to remove an attachment. When edits are complete, click OK. |
Bcc | Identifies email addresses for blind carbon copy recipients |
cc | Identifies email addresses for carbon copy recipients |
Content Description | Describes the email content. The value is
added in the "Content-Description" header field for the message.
|
Content Disposition | Identifies the disposition of the
email content. The value is added in the "Content-Disposition" header field of the message.
|
Content Id | The value is added in the "Content-ID"
header field of the message. Identifies the URL scheme that permits the HTML to refer to the images or other data included in
the message.
|
Content Language | The value is added in the "Content-Language" header of the MIME part. Identifies the language of the message. Several languages may be identified in a comma-separated list. |
Content MD5 | The value is added in the "Content-MD5" header field of the message. Generated only by an originating user agent, this field is used to verify that the retrieved and decoded data are the same data that were originally sent. |
Content Transfer Encoding | Defines the encoding used for the message content. Select one of the transfer encoding options from the drop-list. The default is 7BIT. |
Content Type | Identifies the media type of the data in the body of the message. Select one of the content types from the drop list. The default is text/plain. |
From | Identifies the email address of the sender. |
Reply To | Identifies the email address to which replies to the email are sent. |
Subject | Alpha-numeric field editable by the sender. |
To | Identifies the email addresses for the email recipients. |
Operation Context: JMS
Property | Description |
---|---|
Content Type | Identifies the message type associated with the message. |
Content Format | Specify the format of the
message. Choose from the following:
|
Correlated Response | Set to True or False, identifies whether the message is expected to have a correlated response. |
JMS Correlation ID | Identifies the JMS provider-assigned correlation id for the message; correlation ids are used to link response messages with request messages. |
JMS Delivery Mode | Sets the delivery mode for the message. Choose between JMS_DELIVERY_MODE_PERSISTENT or JMS_DELIVERY_MODE_NONPERSISTENT |
JMS Destination | Identifies the destination to which the message is sent. |
JMS Expiration | Identifies the time the message should expire. If set to zero (0), the message does not expire. When the expiration time is reached, providers should discard the message. |
JMS Message ID | Identifies the identification value for the message; every message has a unique message ID. |
JMS Priority | Identifies the priority value for the message. Priority is a numeric value, from 0 to 9, where 0 is lowest priority. |
JMS Redelivered | set to True or False, identifies whether the message is being redelivered. |
JMS Reply To | Identifies the queue destination where a reply to the current message is to be sent. If this field is null, no reply is expected. |
JMS Timestamp | Identifies the time the message was handed off to a provider to be sent. |
Wire Format
Property | Description |
---|---|
Custom Wire Format | Select if a custom wire format is to be associated with the operation. See Message Designer Overview. |
XML | Select if the operation will use an XML schema. |
Encoding | Identifies the encoding associated with the XML schema. |
Save the service. Select File|Save from the main menu bar.
Next: Defining Service Operation Parameters for a Message Service
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com