Use with Multibyte Environments

WebLogic Integration 8.1 SP6: Use with Multibyte Environments

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

BEA has confirmed the problems in using multibyte characters in the ebXML action name when using HP-JDK 1.4.2_10 coming with WebLogic Integration 8.1 SP6.

Please thoroughly consider all aspects of upgrading from the current version, before upgrading.

(CR279979)

Points of Caution for All WebLogic Integration 8.1 Resources

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\weblogic81\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\weblogic81\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 the metrics file under the fop directory using org.apache.fop.fonts.apps.TTFReader.

Command Example: [When using a TTC-format font] % cd C:\bea\weblogic81\integration\fop % SET PATH=C:\bea\jdk141_05\bin % java -cp C:\bea\weblogic81\server\lib\fop.jar;C:\bea\weblogic81\server\lib\ avalon-framework.jar;C:\bea\weblogic81\server\lib\xml-apis.jar;C:\bea\weblogic81\server\lib\ xercesImpl.jar;C:\bea\weblogic81\server\lib\xalan.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\weblogic81\integration\fop % SET PATH=C:\bea\jdk141_05\bin % java -cp C:\bea\weblogic81\server\lib\fop.jar;C:\bea\weblogic81\server\lib\ avalon-framework.jar;C:\bea\weblogic81\server\lib\xml-apis.jar;C:\bea\weblogic81\server\lib\ xercesImpl.jar;C:\bea\weblogic81\server\lib\xalan.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.

Points of Caution in Upgrade from WebLogic Integration 8.1 SP2

When performing the domain upgrade and using JRockit 1.4.1_06 as a patch for SP2, it is necessary to modify a portion of the property file in advance.

  Replace jrockitsp2=jrockit81sp2_141_05

within $WLHOME\integration\upgrade\domain_upgrade\domain_upgrade.properties with

jrockitsp2=jrockit81sp2_141_06

and execute the upgrade script.

When using a JDK other than the one that comes with 8.1 SP2 (Sun JDK, JRockit, etc.), the path of the JDK used as the domain must be changed manually. After executing the domain upgrade script, overwrite the JDK path for each file within the domain directory.

The files for which overwriting the JDK path is necessary are as follows.

[Windows Environment]
The JAVA_HOME environment variable settings row for the following files
installService.cmd
startWebLogic.cmd
stopManagedWebLogic.cmd
setDomainEnv.cmd
stopWebLogic.cmd
webappCompile.cmd

[UNIX Environment]
The JAVA_HOME environment variable settings row for the following files
startWebLogic.sh
stopManagedWebLogic.sh
setDomainEnv.sh
stopWebLogic.sh
webappCompile.sh

[Windows/UNIX Common]
The jdkHome.path settings row within workshop.properties
The value for the javahome attribute variable for the domain-info element for _cfgwiz_donotdelete\domain-info.xml
The value for the <value> element within the <setenv name="JAVA_HOME"> element for _cfgwiz_donotdelete\startscript.xml

Restrictions

Multibyte Character Usage Restriction in FormatBuilder Field Name

When creating a message format file (.MFL) using FormatBuilder, the validation function for I/O data cannot be used if multibyte characters are used in the field name.

Multibyte Character Usage Restriction in FormatBuilder Filename

The validation function for I/O data cannot be used if multibyte characters are used in the .MFL filename created using FormatBuilder.

Multibyte Character Usage Restriction in FormatBuilder Delimiter

Multibyte characters cannot be used in FormatBuilder's field definition delimiter.

Multibyte Character Usage Restriction When Using AI Console

Multibyte characters cannot be used in the application view name when creating an application view using AI Console.

Limit for Length of Node Names When Using Multibyte Characters

Business Process node names can be up to 100 bytes. 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.

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.

When FTP-type File Event Generators are used, the WLI execution environment's system default encoding is different from the FTP filename's encoding, and multibyte characters are included in the title of the file intended to be the event trigger, that file cannot be handled correctly.

Avoidance Measures:

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

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 having a schema including multibyte elements is created with 8.1, and an .ear file is deployed and accessed as-is in an 8.1 SP2 or later domain, it is possible that an XmlException will occur.

Avoidance Measures:

Rebuild the application on an 8.1 SP2 or later environment.

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 creating an 8.1 application view and using multibyte characters in the Description, etc., then moving the application having AI Control which uses it to 8.1 SP2 or later environment, multibyte characters in AI Console or WLI Admin Console become invalid characters.

Avoidance Measures:

Change all files within the project saved under the wlai-repository to UTF-8 encoding.
Start up the AI Console and confirm that the invalid characters have been corrected.
Execute "Publish" via the AI Console.
Open the Publish-end application with Workshop. Perform the build.

Alternatively, it is possible to deal with the issue by extracting the created application (.ear) once, then changing the encoding for the following files to UTF-8 and re-archiving them as an .ear file.

<Application Name>_ApplicationView.xml
<Application Name>_Default_Adapter.xml

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.

BpelExport function creates .bpel file or .wsdl file using following items of business process (.jpd). 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.

jpd file name (file name for jpd)
process variable name (the variable name defined by jpd file)
node name (node name existing in jpd file)
control name (name of dtf file, jcs file, etc.)
control variable name (the control variable name defined in Data Palette of jpd file)
control method name (the method name defined in dtf file, jcx file, etc.)
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.