Skip navigation.

Use with Multibyte Environments

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents

Using BEA AquaLogic Service Bus in Multibyte Environment

 

This document describes the known problems and some notes when using BEA AquaLogic Service Bus 2.5 under multibyte environment. The contents include:

 


Notes on usage

This chapter describes the necessary preparation and some notes when using BEA AquaLogic Service Bus 2.5 under multibyte environment.

XQuery Mapper

From this release, BEA Workshop is contained in the installer and XQuery Mapper is provided as a plugin. See also the BEA Workshop documents when using this feature.


Known Problems

This chapter describes the known problems with the use of BEA AquaLogic Service Bus 2.5 under multibyte environment.

Request/response Encoding in Tuxedo Transport

To transfer data containing multibyte characters using MBSTRING in Tuxedo transport, UTF-8 must always be specified for request and response encoding regardless of the encoding environment of both parties.

 


Restrictions

This chapter describes some restrictions under the multibyte environment for BEA AquaLogic Service Bus.

Encoding for Sending Alert Message Using JMS

When an alert occurs where Send an alert to a JMS Destination is selected, the message sent will be BytesMessage type. (You cannot specify Text type.) The contents will be a byte array encoded by the encoding specified by Request encoding.

Restriction on Multibyte Character Use for Delimiter in FormatBuilder

Multibyte characters cannot be used as delimiters in FormatBuilder.

URL Encoding at Importing URL Specified Resources

In v2.1, the function to specify URL to obtain resources from external Service Bus Servers has been added. The URL format in this case will be as follows:

  http://localhost:7021/sbresource?WSDL/[project name]/[folder name]/[resource name]

[project name] is the name of the project where the resource is registered
[folder name] is the name of the folder where the resource is registered
[resource name] is the name of the resource

When multibyte characters are used in any of project, folder or resource names for the resource you want to obtain, you must specify the character string that is URL encoded by UTF-8.

Loading Resources from Zip File

From v2.1, loading resources from zip files becomes possible by specifying .zip or .jar files. (Project Explorer - Create Resource - Bulk - Zipped Resources) This function does not work properly when any file name in the zip file contain multibyte characters. When multibyte file names are included, you must use jar files.

Characters Displayable on ServiceBus Console

When you access the ServiceBus Console using Internet Explorer, special characters, especially those in the four-byte area of UTF-8, may be garbled. (The characters are displayed as rectangles.)

Workaround: This phenomenon has not been reported to have occurred in Firefox. BEA recommends using Firefox.

Localization of Traditional Chinese Version

The Traditional Chinese version of BEA AquaLogic Service Bus 2.5 has not been localized. Therefore the GUI, error messages, and online help of AquaLogic Service Bus are displayed in English. Because of the localized bundle, the GUI and online help of WebLogic Server are displayed in traditional Chinese.
However, part of AquaLogic Service Bus calls WebLogic Server resources and the translated resources are displayed for that part.
AquaLogic Server Bus 2.5 has been verified to operate properly in Traditional Chinese environments. BEA is sure that it will be as satisfactory as other localized versions.

 

Back to Top Previous Next