Use with Multibyte Environments

WebLogic Integration 8.1 SP4: Use with Multibyte Environments

Points of Caution for All WebLogic Integration 8.1 Resources

Points of Caution in Upgrade from WebLogic Integration 8.1 SP2

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&gtfontBaseDir</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 traditional Chinese, the font is minliu.ttc, and so on.

* For Japanese, the font-triplet's name attribute "Gothic" is fixed. For Korean,
it is "Gulim". For simplified Chinese and traditional Chinese, it is "SimSun".

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, "SimSun" 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

* In the example, the simplified Chinese font is set to simhei.ttf. In Korean, the font set is ngulim.ttf, and so on.

[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.

Restrictions Through 8.1 SP2

There are the following restrictions in addition to the above.

Multibyte Character Restriction in ebXML Service Name

It is possible that an exception will occur when multibyte characters are used in the ebXML service name.

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 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 domain, it is possible that an XmlException will occur.

Avoidance Measures:

Rebuild the application on an 8.1 SP2 environment.

When an application using AI Control, created with 8.1, is moved to 8.1 SP2, 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, 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

Known Problems through 8.1 SP2

Process control buttons for graphics display (SVG) invalid.

When displaying the graphics display, the "Suspend", "Resume", and "Exit" buttons from process status display, but do not function in multibyte environments.

Avoidance Measures:

It is possible to carry out process control from the process instance summary screen or the process instance detail screen.

An error occurs when executing a process using multibyte elements in XML. (When using JRockit only)

It is possible that a WebLogic Server hangup or a JRockit abort, etc. can occur when codes processing multibyte elements are included in XML within processes (.jpd) for 32bit environments.

Avoidance Measures:

Install JRockit8.1SP2 RP1 or later version, or SP3 or later version.