Use with Multibyte Environments

Using BEA AquaLogic Data Services Platform 3.0 in Multibyte Environment

This document describes the known problems and some notes when using BEA AquaLogic Data Services Platform 3.0 under multibyte environment. The contents include:

Notes on Usage

Method for changing display messages to respective language

In ALDSP 3.0, APAC Version installer includes Japanese, Chinese (simplified, traditional), Korean language messages. To convert the displayed messages into these languages, implement the following procedure before using ALDSP.

aldsp_ccjk.jar file is in the %ALDSP_HOME%\lib. Copy this file into the %BEA_HOME%\weblogic92\platform\lib\L10N directory.

Handling of data with delimiters encoded in non-system-default encoding

If your data source is data with delimiters saved in an encoding other than system default, specify the encoding in the JVM startup parameter (ld.csv.encoding) of AquaLogic Data Services Studio(Eclipse) and domain, so that ALDSP will work properly. The following example specifies UTF-8.

Edit %BEA_HOME%\aldsp_3.0\bin\aldsp.ini in text editor and add line -Dld.csv.encoding=UTF-8.
Edit setDomainEnv.cmd (or .sh) present in the domain bin directory and add -Dld.csv.encoding=UTF-8 in the environment variable JAVA_OPTIONS.

Currently, more than one encoding cannot be handled at the same time in ALDSP.

Parameters used for XML element when creating Physical Data Services

Following items are used as file name, data service function name (XQuery function name), schema file name, XML document element name automatically, when generating physical data services.

Java method name
RDBMS procedure name
RDBMS table, view and column names
RDBMS function name
Item names in data with delimiters
File name for data with delimiters

Known Problems and Restrictions

Problems of multibyte character display in Data Lineage page

In the graphical display of ALDSP console data lineage page, only limited languages (characters) can be displayed.

ALDSP selects font automatically from the locale settings of your domain. Some languages that are used may not display the characters properly in the selected font. Please contact our customer support if the language used is not correctly displayed.

Currently, the fonts that are selected by ALDSP are shown below.

Japanese(ja): MS UI Gothic
Korean (ko): Gulim
Chinese(zh_CN): SimSun
Chinese(zh_TW): MingLiU
Other than mentioned above: SansSerif

Problems when multibyte characters are used in the data service file name

When multibyte characters are used for data services file name, you cannot access the data source as a Web service with Web service mapper. When you use data source as Web service, use single-byte characters for data service file name.

Problems of multibyte characters of WSDL created from Web service mapper turning into garbage characters

There is a problem of multibyte characters of WSDL created from Web service mapper with policy enabled, turning into garbage characters.

WSDL created from Web service mapper contains items like 'Data service function name', 'target namespace', ' XML type definition used in the argument and return value of data service function'. If multibyte characters are used in these items, multibyte characters in the WSDL get garbled. Therefore, testing function of Web service or display of WSDL, URL reference, saving the file etc. does not work properly.

When using Web service mapper with the policy enabled, BEA recommends that either you change 'Data service function name' to the single-byte character or develop Web service client by performing following workaround.

Workaround:

Create Web service mapper with policy enabled, by using the normal procedure.
Select "Save WSDL as" and save WSDL in the file.
Since the multibyte characters in the saved WSDL file get garbled, correct it by using text editor etc.
Develop a Web service client by using the corrected WSDL file.

By performing this workaround, you can call data service from Web service client.

When multibyte character is used in target namespace of XML schema, key can not be created by logical data service.

When multibyte characters are used in the namespace for XML schema associated with logical data services, key can not be created in logical data service. When creating key, use single-byte characters in the namespace.

Project including multibyte characters cannot be upgraded successfully

There is a problem in processing multibyte characters in upgrade function of ALDSP3.0 and ALDSP2.5 project containing multibyte characters cannot be upgraded.

When using multibyte characters are in various file names, characters in data service, characters in XML schema in ALDSP2.5 project, the problems such as XML schema not generated, characters garbled in the upgraded files, incomplete upgraded file etc. may occur during upgrade.

These problems may be prevented by using following workaround. If this problem cannot be prevented even after performing the workaround, please contact our Customer Support.

Workaround:

If 'Some characters cannot be mapped' error is displayed during upgrade, ignore that error and continue the upgrade process.
When multibyte characters of data services get garbled after upgrade, close the data service file once and reopen it.