Use with Multibyte Environments
|
 |
 |
|
This document describes the known problems and some notes when using BEA AquaLogic Service Bus 2.6 under multibyte environment. The contents include:
This chapter describes the necessary preparation and some notes when using BEA AquaLogic Service Bus 2.6 under multibyte environment.
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.
To transfer data containing multibyte characters using MBSTRING in Tuxedo transport on 2.5, UTF-8 had to be always specified for request and response encoding. However, on 2.6, it is necessary to specify the correct encoding on each message to be sent or received. Note that Tuxedo transport bundled in 2.6 encounters a trouble when Messaging/Text type and MBSTRING buffer type are used at the same time and a patch must be applied for correct operations . (CR307948)
This chapter describes some known problems under the multibyte environment of BEA AquaLogic Service Bus.
On an import of a configuration file from the UDDI registry (ALSR), the names and/or comments of business entities and/or services registered in the registry are not displayed correctly when the resource corresponding to an expected language (*1) is not registed in the registry.
(*1) An expected language is the language configuration of the browser or the locale of the environment (Operating System) in which the domain is operating when there is no language configuration for the browser.
Workaround: Register expected language resources for each information on the UDDI registry.
This chapter describes some restrictions under the multibyte environment for BEA AquaLogic Service Bus.
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.
Multibyte characters cannot be used as delimiters in FormatBuilder.
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.
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.
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.
|
|
|