Using WebLogic Integration 7.0 in the Japanese Environment

This document contains the following topics:

• Changes for 7.0SP5

• Notes for 7.0SP4

• Setting up WebLogic Server 7.0SP2 or later to use jRockit

• Regarding the use of double-byte characters

• Limitations

• Known Issues

http://edocs.beasys.co.jp/e-docs/index.html (in Japanese)

Fixed Problems

When a workflow is to be created to call up a Service defined by AI console, the "Request Document Encoding" menu in "Call Application View Service" dialogue of BPM is absent. If the workflow is created and executed in this condition, the resultant encoding will always be "UTF-8". (CR120731)
This problem has been fixed in this release.

1. Obtain the Encodings.properties at http://edocs.beasys.co.jp/e-docs/wli/docs70/ja/Encodings.properties.
2. Unzip $BEAHOME/weblogic700/integration/lib/wlai-plugin-ejb.ja.
3. Deploy Encodings.properties which was obtained by 1 above, to com/bea/wlaiplugin/common in the directory which has been unzipped by 2 above.
4. Recreate wlai-plugin-ejb.jar containing Encodings.properties, and replace it with the original jar.

Changes from 7.0SP1

Setting up WebLogic Server 7.0SP2 or later to use jRockit

WebLogic Integration 7.0 SP2 Japanese installer is not bundled with jRockit. Download the jRockit installer from our Web site http://www.beasys.co.jp/evaluation/index.html and install it to your machine. Then, modify some files as required.

To use jRockit with WebLogic Integration 7.0SP2, follow these steps for modifying the files:

Windows

1. Edit %WL_HOME%\integration\adapters\utils\antEnv.cmd file

- Change the value to be specified by set JAVA_HOME to the directory where JRockit is installed.

2. Edit %WL_HOME%\integration\dbscripts\bpm20_realm_migrator.cmd file

- Change the value to be specified by set JAVA_HOME to the directory where JRockit is installed.

3. Edit %WL_HOME%\integration\dbscripts\bpm20_tutorial_enabler.cmd file

- Change the value to be specified by set JAVA_HOME to the directory where JRockit is installed.

4. Edit %WL_HOME%\common\bin\commEnv.cmd file

- Change the value to be specified by set COMM_JAVA_HOME to the directory where JRockit is installed.

- Change the value to be specified by set COMM_JAVA_VENDOR to BEA.

- Replace all -client to -jrockets.

5. Edit %WL_HOME%\integration\setEnv.cmd file

- Change the value to be specified by set JAVA_HOME to the directory where JRockit is installed.

6. Edit %WL_HOME%\integration\bin\setEnv.cmd file

- Change the value to be specified by set JAVA_HOME to the directory where JRockit is installed.

- Comment out JAVA_OPTIONS.

7. Edit %WL_HOME%\samples\integration\samples\bpm_api\commandline\setEnv.cmd file

- Change the value to be specified by set JAVA_HOME to the directory where JRockit is installed.

8. Edit %WL_HOME%\common\lib\platform.properties file

- Change the values to be specified by set JAVA_HOME and JAVAHOME to the directory where JRockit is installed.

9. Edit %WL_HOME%\samples\server\eval\pointbase\tools\startPointBase.cmd file

- Change the value to be specified by set JAVA_HOME to the directory where JRockit is installed.

10. Edit %WL_HOME%\samples\server\eval\pointbase\tools\startPointBaseConsole.cmd file

- Change the value to be specified by set JAVA_HOME to the directory where JRockit is installed.

11. Edit %WL_HOME%\integration\bin\studio.cmd file

- Delete "%COMM_CLIENT_VM%" from the line "start %JAVA_HOME%\bin\javaw %COMM_CLIENT_VM% -classpath "%CP%" "-Dwli.samples=%SAMPLES_HOME%" "-Dwli.bpm.studio.help=%WLI_HOME%\docs\help" com.bea.wlpi.client.studio.Studio".

12. Edit %WL_HOME%\integration\bin\fb.cmd file

- Delete "%COMM_CLIENT_VM%" from the line "start %JAVA_HOME%\bin\javaw %COMM_CLIENT_VM% -Xmx256m -classpath "%CP%" -Dwlxt.default.document.dev.name=file:%WLI_HOME%\docs\help\FormatBuilder com.bea.wlxt.FormatBuilder.FormatBuilder %1".

13. Edit %WL_HOME%\common\bin\dmwiz.cmd file

・Change "beaUP2\jdk131_06" and "beaUP2\jdk131_06" to the directory where JRockit is installed.

"C:\beaUP2\jdk131_06\bin\javaw" -Dplatform.properties=platform.properties -jar "C:\beaUP2\weblogic700\common\lib\dmwiz.jar"

goto end

:java

"C:\beaUP2\jdk131_06\bin\java" -Dplatform.properties=platform.properties -jar "C:\beaUP2\weblogic700\common\lib\dmwiz.jar" %*

Linux

1. Edit $WLI_HOME/integration/adapters/utils/antEnv.sh file

- Change the value to be set by JAVA_HOME= to the directory where JRockit is installed.

2. Edit $WLI_HOME/integration/dbscripts/bpm20_realm_migrator file

- Change the value to be set by JAVA_HOME= to the directory where JRockit is installed.

3. Edit $WLI_HOME/integration/dbscripts/bpm20_tutorial_enabler file

- Change the value to be set by JAVA_HOME= to the directory where JRockit is installed.

4. Edit $WLI_HOME/common/bin/commEnv.sh file

- Change the value to be set by COMM_JAVA_HOME= to the directory where JRockit is installed.

- Change the value to be set by COMM_JAVA_VENDOR= to BEA.

- Replace all -client to -jrockets.

5. Edit $WLI_HOME/integration/setenv.sh file

- Change the value to be set by JAVA_HOME= to the directory where JRockit is installed.

6. Edit $WLI_HOME/integration/bin/setenv file

- Change the value to be set by JAVA_HOME= to the directory where JRockit is installed.

- Comment out JAVA_OPTIONS.

7. Edit $WLI_HOME/common/lib/platform.properties file

- Change the values to be set by JAVA_HOME= and JAVAHOME= to the directory where JRockit has been installed.

8. Edit $WLI_HOME/samples/server/eval/pointbase/tools/startPointBase.sh file

- Change the value to be set by JAVA_HOME= to the directory where JRockit is installed.

9. Edit $WLI_HOME/samples/server/eval/pointbase/tools/startPointBaseConsole.sh file

- Change the value to be set by JAVA_HOME= to the directory where JRockit is installed.

10. Edit $WLI_HOME/integration/bin/studio file

- Delete "$COMM_CLIENT_VM" from the line "$JAVA_HOME/bin/java $COMM_CLIENT_VM -classpath "$CP" "-Dwli.samples=$SAMPLES_HOME" "-Dwli.bpm.studio.help=$WLI_HOME/docs/help" com.bea.wlpi.client.studio.Studio &".

11. Edit $WLI_HOME/integration/bin/fb file

- Delete "$COMM_CLIENT_VM" from the line "$JAVA_HOME/bin/java $COMM_CLIENT_VM -Xmx256m -classpath "$CP" -Dwlxt.default.document.dev.name=file:$WLI_HOME/docs/help/FormatBuilder com.bea.wlxt.FormatBuilder.FormatBuilder $1 &".

12. Edit $WLI_HOME/common/bin/dmwiz.sh file

・Change "beaUP2/jdk131_06" to the directory where JRockit is installed. "/beaUP2/jdk131_06/bin/java -Dplatform.properties=platform.properties -jar dmwiz.jar $*

Now, you have completed the file editing.

In WLI, unexpected results may occur if double-byte characters (including single-byte Katakana) are used, except for user data and following fields.

Limitations

• The AI console cannot handle a multi-byte character user name.
  Please use single byte characters for user names.
  
• The encoding cannot be specified when exporting data with the B2B console.
  Export data without specifying the encoding; the data will then be exported using the default encoding of your Java VM.
  
• When using RosettaNet or ebXML as a B2B protocol, multi-byte characters cannot be used in the names of the following items:
  • Conversation name
  • Business ID
    
• Multi-byte characters are not allowed as an input for GenerateAdapterTemplate.cmd.
  
• Multi-byte characters cannot be used as separators in the Format Builder.
  
• In the Format Builder, the Default Message Format Encoding and Default Field Code Page should use the same encoding. Otherwise, when the Format Tester creates a binary, output-text might not be displayed correctly.
  
• When XML file is read with "FilePlugin action" in studio, the encoding will be transformed to UTF-8.
  Also, no designation of encoding for writing an XML file is valid; the resultant encoding will always be UTF-8.
  
• When following values are used as a Type for Field in Format Builder, neither "Translate Binary To XML" nor "Translate XML to Binary" is valid.
  
  DATE: DDMMMYY
  DATE: DDMMMYYYY
  DATE: DD-MMM-YY
  DATE: DD-MMM-YYYY
  DATE: MMM-YY
  DATE: MMM-YYYY
  DATE: MMMYY
  DATE: MMMYYYY
  DATE: MMMDDYYYY
  "DATE: Wed Nov 15 10:55:37 CST 2000"
  
  
• Designating Length or Imbedded Length to double-byte field will lead to incorrect translation of Field data.
  
• In Linux, no Japanese characters can be used for Application View folder or Application View name.

• In the Format Builder, the encoding for Default Message Format Encoding and/or Default Field Code Page should use the same character set as the Java VM on which the Format Builder is running. Otherwise, the Binary Text page search might not be performed correctly.
  
• The RunRN2Security sample command does not work correctly on Japanese-mode console.
  
  Please follow the steps below. You need to execute RunRN2Security command at English-mode console first, and then execute commands at the Japanese-mode console.
  For the details of RosettaNet 2.0 Security sample, see RosettaNet 2.0 Security Sample.
  
  Windows
  1. Set the command prompt mode to English:

     %WINDIR%\system32\us.bat

  2. Execute RunRN2Security.cmd.
  3. Run StopRN2Security.cmd to shut down server.
  4. Change the command prompt mode to Japanese:

     %WINDIR%\system32\jp.bat

  5. Start the Peer1 server.

     cd %BEA_HOME\weblogic700\samples\integration\config\samples\RN2Security\config\peer1
     startWeblogic.cmd
     

  6. Start another command prompt in Japanese mode, and then start the Peer2 server.

     cd %BEA_HOME\weblogic700\samples\integration\config\samples\RN2Security\config\peer2
     startWeblogic.cmd
     

  Solaris
  1. Set the console mode to English:

     %WINDIR%\system32\us.bat
     

  2. Execute RunRN2Security.cmd.
  3. Run StopRN2Security.cmd to shut down server.
  4. Change the console mode to Japanese:
     For EUC:

     LANG=ja_JP.eucJP;export LANG
     

     For SJIS:

     LANG=ja_JP.PCK;export LANG
     

  5. Start the Peer1 server.

     cd $BEA_HOME/weblogic700/samples/integration/config/samples/RN2Security/config/peer1
     startWeblogic.cmd
     

  6. Start another console in Japanese mode, and then start the Peer2 server.

     cd $BEA_HOME/weblogic700/samples/integration/config/samples/RN2Security/config/peer2
     startWeblogic.cmd
     

• When MSSQL is designated as the database to be used for RosettaNet2.0 Security sample, edit Peer1 and Peer2 setDBVars files, and add the following database connection parameters. When RunRN2Security command is executed without the parameters being added, the sample may not be correctly executed. Set appropriate values in < >.

  set DB_CODESET=MS932
  set DB_SERVERNAME=<MSSQL_SERVERNAME>
  set DB_NAME=<MSSQL_DBNAME>

  setDBVars files are stored in the following locations:
  
  SAMPLES_HOME/integration/config/samples/RN2Security/config/peer1/dbInfo/mssql
  SAMPLES_HOME/integration/config/samples/RN2Security/config/peer2/dbInfo/mssql
  

• In the servers other than Windows version, the WebLogic Integration sample cannot be executed more than once from QuickStart.
  When it is necessary to execute WebLogic Integration sample again, avoid using QuickStart, but execute WL_HOME/samples/integration/samples/bin/RunSamples.
  
• When PointBase is used for database, Japanese characters cannot be used for organization in BPM.
  When it is necessary to use Japanese characters in organization, modify the file in the following procedure first, and then create the database.
  1. Edit %BEAHOME%\weblogic700\integration\dbscripts\pointbase\BPM_SCHEMA.sql with a text editor.
  
  
  2. Search CREATE TABLE EVENTWATCH, and replace STARTORG LONG VARCHAR NULL, to STARTORG VARCHAR(60) NULL,.
  
  
  3. Save the file and end the text editor.