BEA AquaLogic Service Bus Encoding Handling

BEA AquaLogic Service Bus Encoding Handling

BEA AquaLogic Service Bus has been designed, as its unique product feature requires, to flexibly cope with various encodings (*1) of messages sent from various systems. When linking with the systems that employ multibyte characters, it is essential to know how AquaLogic Service Bus handles the encoding. With the AquaLogic Service Bus that handles multiple transports, the implementation has been done to adapt to as different transport rules as possible, but this may lead to unnecessary differences among transports; this is not a simple situation. This document describes how each transport handles encodings. When you read this document, having the following chart in mind will help you understand the description. Case 1 shows the example of routing from inside the message flow to other services, and Case 2 shows a flow without any routing.

Figure 1: Message Flow Overview Diagram

(*1) However, the encodings that AquaLogic Service Bus can handle are only those supported by Java.

HTTP/HTTPS Transport

With HTTP/HTTPS transport, the encoding at the scene of receiving the messages from outside will be selected from one of following, according to the priority, and then processed.

• Content-Type/charset attribute inside HTTP header
• Request/Response encoding set at service definition time
• Default encoding (iso-8859-1)

Also the encoding when a message is sent out to outside services is selected from one of following, according to the priority.

• Request/Response encoding set at service definition time
• Generic encoding (UTF-8)
• Encoding of the source message
  Taking Figure 1 as an example, in Case 1, the encoding of 2.request takes over that of 1.request, whereas 4.response takes over that of 3.response. In Case 2, 4.response takes over the encoding of 1.request.

The priority is shown in the following table.

Proxy Service request		Business Service request
1. Content-Type/charset attribute 2. Request encoding set value 3. Default : iso-8859-1		1. Request encoding set value 2. (At $body update) Generic encoding : UTF-8 3. Encoding of source message
Proxy Service response		Business Service response
1. Response encoding set value 2. (At $body update) Generic encoding : UTF-8 3. Encoding of source message		1. Content-Type/charset attribute 2. Response encoding set value 3.Default : iso-8859-1

For the details of context variables such as $body, see Message Context in Products Documentation.

e-mail Transport

In e-mail transport, when a proxy service receives an e-mail, the encoding of the message is selected from following, according to the priority, and then processed.

• Content-Type/charset attribute inside message header
• Request encoding set at service definition time
• Default encoding (iso-8859-1)

Also the encoding at sending from business service is selected from following, according to the priority, and then processed.

• Request encoding set at service definition time
• Generic encoding (UTF-8)
• Encoding of the source message received by proxy service

The priority is shown in the following table.

Proxy Service request		Business Service request
1. Content-Type/charset attribute 2. Request encoding set value 3. Default : iso-8859-1		1. Request encoding set value 2. (At $body update) Generic encoding : UTF-8 3. Encoding of source message

file/ftp Transport

With file and ftp transport, both the encoding at file reading by proxy service and the encoding at writing by business service are selected according to the following priority and processed.

1. Request encoding set at service definition time
2. XML declaration encoding attribute value (only XML type)
3. Default value (UTF-8)

JMS Transport

With JMS transport, both the encoding at cue/topic reading by proxy service and the encoding at writing by business service are selected according to the following priority and processed.

1. Request encoding set at service definition time
2. Default value (UTF-8)

The encoding processing at JMS transport is done only when ByteMessage I/F of JMS is used.