Use with Multibyte Environments
 |
 |
 |
|
This document describes the known problems and some notes when using BEA AquaLogic Service Bus under multibyte environment. The contents include:
This chapter describes the necessary preparation and some notes when using AquaLogic Service Bus 2.0 under multibyte environment.
In order to display multibyte characters correctly in XQuery Mapper, you may need to do the font setting for Eclipse manually in some cases. In such cases, follow the next sequence: Open the menu Window - Preferences, and select Workbench - Colors and Fonts. From the list for colors and fonts displayed on the right side, select an element named xxxx Font, then click Change... button. In the dialogue that appears to show the character set, change the language to the appropriate one.
Although XQuery Mapper is based on Eclipse 3.0.1, it does not contain Eclipse language pack. The language pack can be downloaded from the following page. Note however that the operation of the software with language pack applied has not been verified by BEA.
http://www.eclipse.org/downloads/index.php
This chapter describes the known problems with the use of AquaLogic Service Bus 2.0 under multibyte environment.
When you enable Pass By Reference option for proxy service using e-mail transport, the use of multibyte characters in the archive directory name will cause incorrect operations.
If you specify a multibyte character to escape-uri function of XQuery, the result does not match the “%-escaped 2 digit hexadecimal expression” which is defined in the “W3C XQuery 1.0 and XPath 2.0 Functions and Operators” specification. The results will be output in 4 digit expression.
When you generate a message format file using file generating wizard in XQuery Mapper, and if you use multibyte characters for the file name, field name and Root description data in FormatBuilder will be garbled.
Workaround: Re-edition in FormatBuilder is recommended.
In Alert Summary page on the Dashboard, a list of alerts that have occurred is displayed. You can click one of the alert rule names to display the detailed information of the alert rule, but those alert rules for services using multibyte characters may not be displayed correctly.
For the proxy services using File or FTP transport, you need to specify the encoding for XML type file in Request encoding on proxy service configuration page. If Request encoding and the actual encoding do not match, it is possible that the processing will be erroneous even if encoding attributes of XML declaration is present.
When using a report action in a pipeline and outputting a plain text for the report, the view message details page in Service Bus Console will not be displayed correctly by default setting.
Workaround: After the view message detail page is displayed, manually change the encoding specification of browser to UTF-8.
In server information view page on Dashboard, you can click More Info link to invoke a help window. However, an English help window is displayed regardless of the environment.
Workaround: By clicking Help link in the upper right corner, you can invoke the help of desired language.
In the resource importing page (System Administration – Import Resources – Import Configuration Data – Select Resources and Import), you can click Item link in the References column to display the resource information of the resources having the reference relations. However, when multibyte characters are used for resource names, display will not be done correctly, although the importing itself will be done correctly.
When a new credential is created for a service account, this creation may not be done correctly if multibyte characters are included in the service account name or, the project or the folder where the service account exists.
When the product is installed under the directory containing multibyte characters, XQuery Mapper may not be started correctly.
Workaround: Replace the contents of the following file by the results of executing native2ascii command supplied by JDK. An example of execution (on Windows OS) is shown below.
% cd c:\bea\eclipse301\links
% ren com.bea.wli.ide.mapper.feature.link com.bea.wli.ide.mapper.feature.link.bak
% c:\bea\jrockit90_150_03\bin\native2ascii com.bea.wli.ide.mapper.feature.link.bak com.bea.wli.ide.mapper.feature.link
This chapter describes some restrictions under the multibyte environment for BEA AquaLogic Service Bus.
When employing HTTP GET method at proxy services, the assumption is that URL has been URL encoded by UTF-8. If the URL encoding has been done by anything other than UTF-8, the expected results may not be obtained.
Since the variables defined within proxy services are used as XQuery variables, you cannot use any characters other than those allowed by XQuery specification. More specifically, multibyte alphanumeric characters are not allowed. If used, an error will occur and Activate button in the Change Center become invalid.
For the details of allowed characters, see the following XQuery specification.
XQuery 1.0: An XML Query Language
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.
When multibyte characters are input in the input field of ‘examplesWebApp,’ which is a sample application provided as a part of the product, the expected results may not be obtained.
|
|
|