Use with Multibyte Environments

The problem areas with HP-JDK 1.4.2_10 coming with WebLogic Integration 8.1 SP6

Points of Caution for All WebLogic Integration 8.1 Resources

Additional Work for Using multibyte characters in the Printable Graph (PDF)

Points of Caution in Upgrade from WebLogic Integration 8.1 SP2

Restrictions

Multibyte Character Usage Restriction in FormatBuilder Field Name

Multibyte Character Usage Restriction in FormatBuilder Filename

Multibyte Character Usage Restriction in FormatBuilder Delimiter

Multibyte Character Usage Restriction When Using AI Console

Limit for Length of Node Names When Using Multibyte Characters

Known Problems

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

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.

An XmlException occurs when an application having a schema including multibyte elements created with 8.1 is deployed and accessed in an 8.1 SP2 or later domain.

When an application using AI Control, created with 8.1, is moved to an 8.1 SP2 or later domain, the portion set with multibyte characters becomes invalid characters.

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.

Notes for SP4 and earlier