Use with Multibyte Environments

Using WebLogic Integration 10.2 in Multibyte Environment

General Notes on Using the WebLogic Integration 10.2 Release

Additional Work for Using multibyte characters in Microsoft SQL Server environment

To use Microsoft SQL Server as a database on WLI 10.2, additional work is required to use multibyte characters.

Configure the database in accordance with Choosing Internationalization and Localization Settings described in the following page.

http://edocs.bea.com/wlp/docs100/db/db_architecture.html#wp1069678

Restrictions

Multibyte Usage Restriction in Process Package Names

Multibyte characters are unusable for any statefull process package name.

Multibyte Character Usage Restriction in FormatBuilder Field Name

When a multibyte character is used for a field name to create a message format file (.MFL) by using FormatBuilder, the validation function becomes unusable for input/output data.

Multibyte Character Usage Restriction in FormatBuilder Filename

When a multibyte character is used for a .MFL file name created with FormatBuilder, the validation function becomes unusable for input/output data.

Multibyte Usage Restriction in FormatBuilder Delimiter

Multibyte characters are not allowed to be used for FormatBuilder's field definition delimiter.

Limit for Length of Node Names When Using Multibyte Characters

Up to 100 bytes are allowed for the name of a business process node. For multibyte characters, the number of bytes necessary in one character depends on the character set. When using long node names, confirm your data base's character set. Be careful node names do not exceed 100 bytes.

Known Problems

The FTP-type File Event Generator's function for sorting by date does not work properly.

In File Event Generator using FTP-server, there are cases in which the function for sorting files by date of modification does not work properly. This problem is occured because the File Event Generator analyzes the date column of the file list that the LIST command of that FTP server returns internally, and can not recognize the date when that date format is different from what it is expected. Attention is required especially in Non-English-speaking sphere, because sometimes locale-specific description except for English is used.

Workaround:

This problem can be avoided by starting the FTP server with English locale. Or, it is necessary to use the FTP server that uses English description in non-English locale environment.

For FTP-type File Event Generators, filenames including multibyte characters cannot be handled correctly when the WLI execution environment's system default encoding is different from the FTP filename's encoding.

For FTP-type File Event Generators, a file which is the target of an event trigger and has a name including multibyte characters cannot be handled correctly when the WLI execution environment's system default encoding is different from the FTP filename's encoding.

Workaround:

Make the WLI execution environment's system default encoding and the encoding for the filenames on the FTP server the same.

When some multibyte characters are used within a business process, .bpel file or .wsdl file that has been exported by BpelExport may not match BPEL4WS schema or WSDL schema respectively.

The BpelExport function generates .bpel file and .wsdl files by using the file business process items (.jpd) listed below. While BPEL and WSDL schema in some cases define these items as NCName type or QName type and therefore restrict allowed characters, BpelExport has no countermeasure processing against restricted characters. For this reason, when some multibyte characters not usable in NCName type or QName type are used in a business process, it is possible that .bpel or .wsdl files not matching their schemas are created.

process file name
process variable name (the variable names defined in a process file)
node name (the node names in a process file)
control name (the names of a control file and so forth)
control variable name (the control variable names defined in Data Palette of a process file)
control method name (the method names defined in a control file and so forth)
control method variable name (the variable name defined in control method)

Workaround:

Modify the wrong characters manually by editing the created .bpel or .wsdl file.

'Not Found' error occurs if Worklist User Portal help is displayed in simplified Chinese (zh_CN), Traditional Chinese (zh_TW) environment.

'Error 404--Not Found' error occurs if Worklist User Portal help is displayed in simplified Chinese (zh_CN), Traditional Chinese (zh_TW) environment.

Workaround:

Directly specifying the URL in the web browser displays Help in simplified Chinese (zh_CN) and Traditional Chinese (zh_TW). The URL is as indicated below:

http://[hostname]:[portno]/[Web Project]/help/[zh_CN or zh_TW]/intro.html