Skip navigation.

eDocs home > BEA WebLogic Integration 10.2 Documentation > Using WebLogic Integration 10.2 in Multibyte Environment

Use with Multibyte Environments

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents  

General Notes on Using the WebLogic Integration 10.2 Release

Additional Work for Using multibyte characters in Microsoft SQL Server environment

Restrictions

Multibyte Usage Restriction in Process Package Names

Multibyte Character Usage Restriction in FormatBuilder Field Name

Multibyte Character Usage Restriction in FormatBuilder Filename

Multibyte Usage Restriction in FormatBuilder Delimiter

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.

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.

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

 

 Back to Top Previous Next