Use with Multibyte Environments

Using WebLogic Integration 9.2 MP1 in Multibyte Environment

General Notes on Using the WebLogic Integration 9.2 Release

Additional Work for Using multibyte characters in Microsoft SQL Server environment

To use Microsoft SQL Server as a database on WLI 9.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.beasys.co.jp/e-docs/wlp/docs92/db/db_architecture.html#wp1069678

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

The user must perform font settings in order for multibyte characters to display properly in the printable graph.Carry out the settings in accordance with the procedure below.

Create a 'fop' directory directly below the integration directory.

% cd C:\bea\weblogic92\integration

% mkdir fop

Create 'userconfig.xml' directly below the fop directory.The contents should be as follows.

    ---------------------------------------------------------------------
<configuration>
<entry>
<key>fontBaseDir</key>
<value>C:\bea\weblogic92\integration\fop\</value>
</entry>
<fonts>
<font metrics-file="msgothic.xml" embed-file="C:\Windows\Fonts\msgothic.ttc" kerning="yes">
<font-triplet name="Gothic" style="normal" weight="normal"/>
<font-triplet name="Gothic" style="normal" weight="bold"/>
<font-triplet name="Gothic" style="italic" weight="normal"/>
<font-triplet name="Gothic" style="italic" weight="bold"/>
</font>
</fonts>
</configuration>
     ---------------------------------------------------------------------

* Correct the directory path in accordance with the system environment.

* It is necessary to make the XML filename for the metrics-file attribute
the same as the actual XML file name created in the next step.

* In the example above, the font is set to msgothic.ttc in the embed-file attribute.
For Korean, the font is gulim.ttc. For simplified Chinese, the font is simsun.ttc.
For tradtional Chinese, the font is minliu.ttc, and so on.

* For Japanese, the font-triplet's name attribute "Gothic" is fixed.
The font format for the Korean version will be “Gulim”, for the simplified Chinese version it will be “SimSun” and for the traditional Chinese version it will be “MingLiU”.

Create a metrics file under the fop directory by using org.apache.fop.fonts.apps.TTFReader.

Command Example: [When using a TTC-format font] % cd C:\bea\weblogic92\integration\fop % SET PATH=C:\bea\jdk150_06\bin % java -cp C:\bea\weblogic92\server\lib\fop.jar;C:\bea\weblogic92\server\lib\avalon-framework.jar org.apache.fop.fonts.apps.TTFReader –ttcname "MS Gothic" C:\Windows\Fonts\msgothic.ttc msgothic.xml

* In the example, the Japanese font "MS Gothic" is set to msgothic.ttc.
In Korean, "Gulim" is set to gulim.ttc. In simplified Chinese, "SimSun" is set to simsun.ttc. In traditional Chinese, "MingLiU" is set to minliu.ttc, and so on.

[When using a TTF-format font] % cd C:\bea\weblogic92\integration\fop % SET PATH=C:\bea\jdk141_05\bin % java -cp C:\bea\weblogic92\server\lib\fop.jar;C:\bea\weblogic92\server\lib\avalon-framework.jar org.apache.fop.fonts.apps.TTFReader C:\Windows\Fonts\simhei.ttf simhei.xml

* The example specifies the simplified Chinese font simhei.ttf. For Korean, use ngulim.ttf, for example.

[Note]

If the system being used does not have a True Type font, the user must add one in advance.

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 Filenames

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.

Multibyte Usage Restriction When Using AI Console

When an application view is created with AI Console, multibyte characters are not allowed to be used for the name of the application view.

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

Upgrading Service Broker Control including multibyte characters causes the multibyte characters to be collapsed.

When a WLI8.1 Service Broker Control source file including multibyte characters is upgraded with WLI9.2, the multibyte characters in the Service Broker Control source file and WSDL file get collapsed at the time of generation.

This problem occurs when WSDL is defined in the Service Broker Control source file. This problem does not occur when WSDL is defined in an external .wsdl file.

Avoidance Measures:

When WSDL is defined in the Service Broker Control source file, take the following steps to avoid this problem.

・Open a Service Broker Control source file with a text editor before upgrading it.

・Find the WSDL definition which begins with "/** @common".

・encoding declaration is set to utf-8. Change it to the system default encoding, and then save the file.

Before change:

/** @common:define name="autoWsdl" value::

<?xml version="1.0" encoding="utf-8"?>

<wsdl:definitions xmlns="" xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/" ...The reset is omitted.

 

After change (Windows Japanese version is in use in the example):

/** @common:define name="autoWsdl" value::

<?xml version="1.0" encoding="Shift_jis"?>

<wsdl:definitions xmlns="" xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/" ...The reset is omitted.

・On WLI9.2 Workshop, select Upgrade Source File(s) to upgrade Service Broker Control.

Worklist Console Help is displayed in English in the Traditional Chinese (zh_TW) environment.

Worklist Console displays Help in English in the Traditional Chinese (zh_TW) environment.

Avoidance Measures:

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

http://[hostname]:[portno]/worklistconsole/help/zh_TW/wwhelp/wwhimpl/java/html/wwhelp.htm?href=intro.html

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

There are cases in which the function for sorting files by date of modification does not work properly when creating an Event Generator for an ftp server operating with a non-English locale.

Avoidance Measures:

Launch the ftp server with English locale.

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.

Avoidance Measures:

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)

Avoidance Measures:

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