Use with Multibyte Environments

BEA AquaLogic Data Services Platform 3.2/3.0.1 use with multibyte environments

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

Notes on Usage

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 that encoding in the JVM startup parameter (ld.csv.encoding) of the domain, so that ALDSP will work properly. The following example specifies UTF-8.

        -Dld.csv.encoding=UTF-8

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

Method for changing display messages to respective language (Only v3.0.1)

In ALDSP 3.0.1 APAC Version installer includes Japanese, Chinese (simplified, traditional), Korean language messages. (Mainly in the ALDSP console) 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.

Known Problems and Restrictions

Problems while creating the physical data service from the data with delimiter

While creating physical data service of the data with delimiter, only the data file with delimiters can be specified, however, when the contents of that file are saved by another encoding than the default system, following problems are raised.

The element name of the created schema get garbled.
When multibyte characters are used, they are not recognized correctly.

Workaround: You will be able to solve this problem by creating schema files in advance and specifying them at the time of creating physical data service.

Problems of multibyte character display in Data Lineage page

In the graphical display of ALDSP console data lineage page, multibyte characters cannot be displayed correctly.

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.

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.

Some problems are only related to the display, so they may be solved by using the following procedure. Test the target project on backup system.

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.