Implementing Header-based Routing

Enhance the runtime performance when exposing one or more services via JMS, by routing the message without parsing it.

You can route a message by either selecting a JMSAction property entry or a user-defined header property entry. You can only expose one service via this method.

Define a custom wire format (user-defined routing). Create a message definition New > Sybase > Message Definition that defines the message structure including wire format that is used as the service's operation parameter. For example, you could define a message called SimpleMessage that contains two fields that use a comma as the delimiter.
Note: To route a custom wire formatted message, you must add the message properties defined for the message to the client message, which is described later.
Create a messaging service (for example, outq). Follow the wizard instructions to define the service. Include:
- Service Endpoint creation – Yes
- Style – Messaging
- Endpoint Type – Server
- Messaging Type – JMS
- Connection Properties – browse for a valid endpoint in the Enterprise Explorer. Use an existing Message Transport connection cache for the JMS messaging endpoint binding or create a new JMS connection profile.
From the Service editor, select the Service Interface tab and add a one-way operation to the service (for example, send).
Add an operation parameter to the operation:
1. Highlight the send operation.
2. Expand the operation parameters list and select Add.
3. Select Complex Type and Browse to the custom message definition (SimpleMessage) you created earlier as your datatype.
From the Service Binding editor, select the Service Binding tab, click the operation, and select:
- The Wire Format Properties tab – select the Custom Wire Format checkbox, and select the custom message from the Format drop-down list.
- The Operation Context tab - change the Content Type to Bytes.
Create the Sybase Services Package Profile. Include the following:
- Contents - Select the messaging service that you just created (outq) to be included in the package
- Access Configuration – remove HTTP from the Transports section, and select Custom Wire Format as the Protocol setting.
Note: You cannot select Custom Wire Format until you remove the HTTP transport from your list of transports (box on the left side).
Associate a name value pair with the operation. This is done from the Access Configuration tab and the Transport sub-tab. You should see the same HeaderName, HeaderValue and HeaderType in the registry definition.
Deploy the service.
Create and deploy a test package that routes the message. (See header-based routing examples below).
Check the service target to ensure the message has been routed.

Header-based Routing Examples

Keep the following in mind when using header-based routing:

To route a custom wire formatted message – include the message properties in your test client, for example:

msg.setStringProperty("locale","en_US");
msg.setStringProperty("encoding","windows-1252");
msg.setStringProperty("formatName","SimpleMessage");
msg.setStringProperty("contentFormat", "sybfmt");

To route by JMS header – when you put the message onto the inbound queue you need to add the JMS header property "operation" using the value of the service/operation, for example,"outq/send". (The JMS header property can be whatever you set it to be in the package when you selected header based routing.)
Note: There is one level of indirection: you always need the header property, "ROUTING_HEADER_NAME" to point to the header property that contains the routing name/value pair. For example:
```
			 msg.setStringProperty("ROUTING_HEADER_NAME", "operation");			
msg.setStringProperty("operation", "outq/send");
```