Searching Java CAPS

1 About Update Releases for Sun Java CAPS 5.1.3

These Update Releases are designed to simplify the maintenance of a Java CAPS 5.1.3 installation by delivering a set of individual Emergency Software Releases (ESRs) that exhibit the following characteristics:

• Cumulative: This update release accumulates all fixes that have been delivered in any prior 5.1.3 Update release.
• Co-dependent: The ESRs delivered as part of Update Release 4 have been verified as whole. Specific dependencies of each ESR can be found in the individual installation instructions in Section 3.

2 Contents of this Update Release

Update Release 4 for Sun Java CAPS 5.1.3 (henceforth called "CAPS 5.1.3U4") is delivered as a set of 39 ESRs as follows:

2.1 Use of ESRs from Java CAPS 5.1.3 Update Release 1, 2, or 3

This Update Release contains all updates made since Update Release 3, and also contains all previous updates made since the original 5.1.3 GA Release. If you have already installed previous Java CAPS 5.1.3 Update Releases, you should install the ESRs shipped as part of CAPS 5.1.3U4 over that installation.

2.2 Obsolescence

The ESRs shipped with CAPS 5.1.3U4 obsolete all ESRs released in previous Java CAPS 5.1.3 Update Releases.

2.3 Cumulative Nature of Update Release ESRs

ESRs shipped as part of the Update Releases for CAPS 5.1.3 are cumulative in nature. This means that the ESRs shipped as part of CAPS 5.1.3U4 include the full set of enhancements and bug fixes shipped as part of previous CAPS 5.1.3 releases.

In order to upgrade a Java CAPS 5.1.3 GA installation to Java CAPS 5.1.3U4, you only need to install the ESRs mentioned above.

3 Installation

3.1 Installation Sequence

The ESRs that constitute Update Release 4 need to be installed in the following sequence:

1. Rollup ESRs for eGate
   1. Repository (6787633)
   2. Enterprise Designer (6787640)
   3. Other eGate rollup ESRs (6787639, 6787634, 6730424, 6787632, 6787684)
   4. Non-eGate rollup ESRs (6785598, 6785600-6785603, 6785609, 6785611, 6785616, 6785617, 6787685, 6788203-6788205, 6788580, 6790929, 6790931, 6792793-6792800, 6792802-6792804, 6792806-6792810) in any order
2. All other ESRs

IMPORTANT NOTES:

• Some ESR distribution files are named ESR######-dist.zip and must be extracted prior to installation. This extracts a file named ESR######.zip, which is the ZIP file that you copy into your Java CAPS environment. If you download the distribution files from Goldstar, the files are downloaded as ESR######.zip (without the "-dist"). Make sure to extract this distribution file to access the ZIP file that you copy to Java CAPS, which will also be named ESR######.zip.
• In order for your CAPS 5.1.3 installation to function correctly, you must install all 7 eGate rollup ESRs (Repository, Enterprise Designer, NetBeans relating to Enterprise Designer, Enterprise Manager, Enterprise Manager ESR-Install Utility, Logical Host, JMS for Logical Host).

3.2 Detailed Installation Instructions for Core eGate ESRs

3.2.1 ESR 6787633 (eGate — Repository)

3.2.1.1 Prerequisites

There are no prerequisite ESRs for 6787633.

3.2.1.2 Corequisites

• 6787639
• 6787634
• 6787632
• 6787640
• 6787684
• 6730424

3.2.1.3 Installation

This section only provides an overview of the instruction for the Repository ESR. For complete details please refer to the chapter titled "Installation Instructions for ESRs", especially the section titled "Installing Repository ESRs", in the Java CAPS Installation Guide (CAPS_Install_Guide.pdf). This document is available on the Sun Java CAPS 5.1.3 DVD Disc 1 or any Repository download CD. It is also available at http://docs.sun.com/app/docs/doc/820-0938?l=en.

*Note: *If you are downloading from Goldstar, see these important notes.

You install Repository ESRs on the machine on which the Java CAPS 5.1.3 Repository is running. The steps required to install the Repository ESR are:

1. Shut down the Repository.
2. Extract the ESR distribution file (ESR6787633-dist.zip) to a directory as instructed in the section "Extracting ESR Distribution Files" in the Java CAPS Installation Guide.
3. Copy the ESR ZIP file (ESR6787633.zip) to the <JavaCAPS513>/ESRs folder.
4. Open a command prompt (or Terminal window in Unix) and navigate to <JavaCAPS513>/ESRs.
5. Run the following command:
   ESRInstall 6787633 (for Windows)
   or
   sh ESRInstall.sh 6787633 (for Unix)
   The ESR is applied.

Note: This ESR includes a utility introduced in 5.1.3 Update 2 that allows you to replicate an existing repository. For information and instructions on using this utility, see Using the Repository Replicate Tool.

3.2.1.4 Post-installation Steps

Step 1: Increase the Heap Size in the Repository Startup Script:

The current heap size setting is insufficient to upload the remaining eGate Rollup ESRs. Therefore, you must increase the heap size of the Repository using the following steps:

1. Open the startup script for the Repository in a text editor. This file is named startserver.bat in Windows and startserver.sh in Unix. It is located in the <JavaCAPS513>/repository folder.
2. Locate and change the startup option -Xmx256m to -Xmx512m.
3. Save the modified startup script.

Step 2: Run the Repository Cleanup Script:

1. After the ESR has been successfully installed, open a command prompt (or a Terminal window in Unix) and navigate to <JavaCAPS513>/repository.
2. Run the following command:
   esrxmlfix.bat (for Windows)
   or
   sh esrxmlfix.sh (for Unix)

Step 3: Restart the Repository:

Restart the Repository by executing the startup script (startserver.bat for Windows or startserver.sh for Unix).

3.2.2 ESR 6787640 (eGate — Enterprise Designer)

3.2.2.1 Prerequisites

• 6787633 (Repository) must be installed and its post-installation procedure completed prior to installing ESR 6787640.

3.2.2.2 Corequisites

• 6787639
• 6787634
• 6787632
• 6787684
• 6730424

3.2.2.3 Installation

This section provides an overview of the installation instructions for the Enterprise Designer ESR. For more complete instructions, please refer to the chapter titled "Installation Instructions for ESRs", especially the sections titled "Uploading Enterprise Designer and Logical Host ESRs from the Suite Installer" and "Installing Enterprise Designer ESRs and non-eGate Product Rollup Upgrades", in the Java CAPS Installation Guide (CAPS_Install_Guide.pdf). This document is available on Sun Java CAPS 5.1.3 DVD Disc 1 or on any Repository download CD. It is also available at http://docs.sun.com/app/docs/doc/820-0938?l=en.

*Note: *If you are downloading from Goldstar, see these important notes.

To complete the installation of ESR6787640, each Enterprise Designer needs to be updated through the Update Center. The steps required to install the Enterprise Designer ESR are:

1. Extract the ESR6787640-dist.zip file to a temporary directory as described in "Extracting ESR Distribution Zip Files".
2. Use the Suite Installer to upload ESR6787640.sar to the Repository as described in "Uploading Enterprise Designer ESRs from the Suite Installer".

3.2.3 ESR 6787639 (eGate — NetBeans Relating to Enterprise Designer)

3.2.3.1 Prerequisites

• 6787633 (Repository)
• 6787640 (Enterprise Designer)

3.2.3.2 Corequisites

• 6730424
• 6787634
• 6787632
• 6787684

3.2.3.3 Installation

This section provides an overview of the installation instructions for the NetBeans ESR relating to Enterprise Designer. For more complete instructions, please refer to the chapter titled "Installation Instructions for ESRs", especially the sections titled "Uploading Enterprise Designer and Logical Host ESRs from the Suite Installer" and "Downloading and Extracting Enterprise Designer and Logical Host ESR ZIP Files", in the Java CAPS Installation Guide (CAPS_Install_Guide.pdf). This document is available on Sun Java CAPS 5.1.3 DVD Disc 1 or on any Repository download CD. It is also available at http://docs.sun.com/app/docs/doc/820-0938?l=en.

*Note: *If you are downloading from Goldstar, see these important notes.

This ESR is installed on the machines where the Enterprise Designer is installed. The steps required to install ESR 6787639 are:

1. Shut down Enterprise Designer if it is running.
2. Extract the ESR6787639-dist.zip file to a temporary directory as described in "Extracting ESR Distribution ZIP Files".
3. Use the Suite Installer to upload ESR6787639.sar to the Repository using the Suite Installer as described in "Uploading Enterprise Designer ESRs from the Suite Installer".
4. Download and extract the following file(s) as described in "Downloading and Extracting Enterprise Designer and Logical Host ESR ZIP Files": edesigner_ESR6787639.zip.

3.2.3.4 Post-installation Steps

If you use Command-line Codegen, you must execute the following steps:

1. Navigate to the Downloads tab in the Suite Installer.
2. Click on the link named commandlinecodegen_ESR6787639.zip to download the commandlinecodegen_ESR6787639.zip file to your system.
3. Extract the contents of the ZIP file to the parent of the commandlinecodegen directory.

3.2.4 ESR 6730424 (eGate — Enterprise Manager ESR-Install Utility)

3.2.4.1 Prerequisites

• 6787633 (Repository)
• 6787640 (Enterprise Designer)

3.2.4.2 Corequisites

• 6787639
• 6787634
• 6787632
• 6787684

3.2.4.3 Installation

This section provides an overview of the installation instructions for the Enterprise Manager ESR-Install Utility ESR. For more complete instructions, please refer to the chapter titled "Installation Instructions for ESRs", especially the sections titled "Uploading Enterprise Designer ESRs from the Suite Installer" and "Downloading and Extracting Enterprise Designer and Logical Host ESR Zip Files", in the Java CAPS Installation Guide (CAPS_Install_Guide.pdf). This document is available on Sun Java CAPS 5.1.3 DVD Disc 1 or on any Repository download CD. It is also available at http://docs.sun.com/app/docs/doc/820-0938?l=en.

Note: If this is the first time that you are installing Enterprise Manager or if you have never started Enterprise Manager on this system, you must start and stop the Enterprise Manager at least once before applying ESR 6730424. If you are downloading from Goldstar, see these important notes.

1. Shut down Enterprise Manager.
2. Extract the ESR6730424-dist.zip file to a temporary directory as described in "Extracting ESR Distribution ZIP Files".
3. Copy ESR6730424.zip to the <eManager>/ESRs folder.
4. Open a command prompt (or a Terminal window in Unix) and type:
   cd <eManager>/ESRs
   ESRInstall 6730424 (for Windows)
   or
   sh ESRInstall.sh 6730424 (for Unix)
5. Restart Enterprise Manager.

3.2.5 ESR 6787634 (eGate — Enterprise Manager)

3.2.5.1 Prerequisites

• 6787633 (Repository)
• 6787640 (Enterprise Designer)
• 6730424 (Enterprise Manager ESR-Install Utility)

3.2.5.2 Corequisites

• 6787639
• 6787632
• 6787684

3.2.5.3 Installation

Enterprise Manager ESRs are installed on the machine on which the Enterprise Manager server is running. The steps required to install the Enterprise Manager ESR are:

Note: If this is the first time that you are installing Enterprise Manager or if you have never started Enterprise Manager on this system, you must start and stop the Enterprise Manager at least once before applying ESR 6787634. If you are downloading from Goldstar, see these important notes.

1. Shut down Enterprise Manager.
2. Extract the ESR6787634-dist.zip file to a temporary directory as described in "Extracting ESR Distribution ZIP Files".
3. Copy ESR6787634.zip to the <eManager>/ESRs folder.
4. Open a command prompt (or a Terminal window in Unix) and type:
   cd <eManager>/ESRs
   ESRInstall 6787634 (for Windows)
   or
   sh ESRInstall.sh 6787634 (for Unix)
5. Restart Enterprise Manager.

3.2.6 ESR 6787632 (eGate — LogicalHost)

3.2.6.1 Prerequisites

• 6787633 (Repository)
• 6787640 (Enterprise Designer)

3.2.6.2 Corequisites

• 6730424
• 6787639
• 6787634
• 6787684

3.2.6.3 Installation

*Note: *If you are downloading from Goldstar, see these important notes.

You install Logical Host ESRs on the machines on which instances of the Logical Host are running. The steps required to install ESR 6787632 are:

1. Shut down any domains that are running.
   *IMPORTANT:* If this ESR is to be installed in a cluster environment, the domains and all of their associated processes should be stopped on all cluster nodes before installing this ESR.
2. Extract the ESR6787632-dist.zip file to a temporary directory as described in "Extracting ESR Distribution ZIP Files".
3. Copy ESR6787632.zip to the <LogicalHost>/ESRs folder.
4. Open a command prompt (or Terminal window in Unix) and type:
   cd <LogicalHost>\ESRs
   ESRInstall.bat 6787632 (for Windows)
   or
   sh ESRInstall.sh 6787632 (for Unix)
5. Restart the domains.

3.2.7 ESR 6787684 (eGate — JMS for LogicalHost)

3.2.7.1 Prerequisites

• 6787633 (Repository)
• 6787640 (Enterprise Designer)

3.2.7.2 Corequisites

• 6730424
• 6787639
• 6787634
• 6787632

3.2.7.3 Installation

*Note: *If you are downloading from Goldstar, see these important notes.

You install JMS ESRs on the machines on which instances of the Logical Host are running. The steps required to install ESR 6787684 are:

1. Shut down any domains that are running.
2. Extract the ESR6787684-dist.zip file to a temporary directory as described in "Extracting ESR Distribution Zip Files".
3. Copy the version of ESR6787684.zip corresponding to your operating system to the <LogicalHost>/ESRs folder.
4. Open a command prompt (or Terminal window in Unix) and type:
   cd <LogicalHost>\ESRs
   ESRInstall.bat 6787684 (for Windows)
   or
   sh ESRInstall.sh 6787684 (for Unix)
5. Restart the domains.

3.3 Installation Instructions For All Other 5.1.3U4 ESRs

3.3.1 General ESR Installation Instructions

Most ESRs follow the same general ESR installation instructions described in this section. If additional steps are required, those instructions will be specified in the sections below.

3.3.1.1 Prerequisites

Install the following ESRs before installing these ESRs:

• 6787633
• 6787640
• 6787639
• 6730424
• 6787634
• 6787632
• 6787684

3.2.8.2 Corequisites

None.

3.2.8.3 Installation

*Note: *If you are downloading from Goldstar, see these important notes.

The steps required to install these ESRs are:

1. Extract the ESR<number>-dist.zip file to a temporary directory as described in "Extracting ESR Distribution Zip Files".
2. Use the Suite Installer to upload ESR<number>.sar to the Repository as described in "Uploading Enterprise Designer and Logical Host ESRs from the Suite Installer".
3. On the Tools menu in Enterprise Designer, click Update Center to start the Update Center Wizard. Then, follow the instructions in the section titled "Installing Enterprise Designer ESRs and non-eGate Product Rollup Upgrades".

3.3.2 ESR 6787685 (eInsight Business Process Manager)

See Section 3.3.1.

3.3.3 ESR 6788580 (eTL Integrator)

See Section 3.3.1.

3.3.4 ESR 6788203 (eView Studio)

See Section 3.3.1, then follow the instructions below.

3.3.4.1 Installation

The steps required to install this ESR are:

1. Back up any existing eView projects by exporting them.
2. Follow the installation instructions in Section 3.3.1.
3. In order for this ESR to take effect on existing eView Projects, perform the following steps:
   1. Regenerate each application, and rebuild and redeploy the server Projects (for more information, see the eView Studio User's Guide).
   2. Refresh any Java Collaborations in client Projects that reference the eView Projects.
   3. Re-import the eView JAR files into each client Collaboration.
   4. Rebuild and redeploy the client Projects.

3.3.5 ESR 6792793 (eVision Studio)

See Section 3.3.1.

3.3.6 ESR 6788204 (eIndex Single Patient View)

Follow the instructions in the section below that applies to your environment.

3.3.6.1 Installing eIndex Single Patient View for the First Time

*Note: *If you are downloading from Goldstar, see these important notes.

The eIndex ESR includes two SAR files; one for Oracle and one for SQL Server. Make sure to install the SAR file for the database platform you use. If this is a new installation of eIndex Single Patient View, follow these steps:

1. Extract the ESR<number>-dist.zip file to a temporary directory as described in "Extracting ESR Distribution Zip Files".
2. Use the Suite Installer to upload the ESR<number>.sar from the appropriate database folder to the Repository as described in "Uploading Enterprise Designer and Logical Host ESRs from the Suite Installer".
3. On the Tools menu in Enterprise Designer, click Update Center to start the Update Center Wizard. Then, follow the instructions in the section titled "Installing Enterprise Designer ESRs and non-eGate Product Rollup Upgrades" to install the new Help module.
   Note: If eView Studio is not currently installed, you also need to install the eView modules from the Update Center.

3.3.6.2 Upgrading an Existing Version of eIndex Single Patient View

If this is an upgrade to an existing version of eIndex Single Patient View, follow these instructions:

Note: In order to get the fixes for eView Studio, you must also install ESR 6788203 as described in section 3.3.4.

1. Backup any existing eIndex Projects by exporting them.
2. Extract AliasHelper.java and EnterpriseUpdatePolicy.java from the ESR distribution file into a temporary location.
3. In your existing eIndex server Project, check whether either of these files is customized and do one of the following:
   • If either of these two files has been customized in the existing eIndex server Project, customize the new versions accordingly and replace your existing copy with the newly customized versions.
   • If neither file has been customized in the existing eIndex server project, replace the two files with the new versions you extracted in step 2 above.
4. Regenerate the eIndex application (for more information, see the eIndex Single Patient View User's Guide.
5. Rebuild and redeploy the server Projects.
6. In order for this ESR to take effect on existing eIndex Projects, perform the following steps:
   1. Regenerate each application, and rebuild and redeploy the server Projects (for more information, see the eIndex Single Patient View User's Guide).
   2. Refresh any Java Collaborations in client Projects that reference the eIndex Projects.
   3. Re-import the eIndex JAR files into each client Collaboration.
   4. Rebuild and redeploy the client projects.

3.3.7 ESR 6792794 (Alert Agent)

See Section 3.3.1 for prerequisites and corequisites, then follow the instructions below.

3.3.7.1 Installation

*Note: *If you are downloading from Goldstar, see these important notes.

The steps required to install this ESR are:

1. Extract the ESR6792794-dist.zip file to a temporary directory as described in "Extracting ESR Distribution ZIP Files".
2. Use the Suite Installer to upload ESR6792794.sar to the Repository as described in "Uploading Enterprise Designer and Logical Host ESRs from the Suite Installer".
3. Re-install the Alert Agent EMR component in Enterprise Manager after installing the Alert Agent ESR.

3.3.8 ESR 6792796 (Batch eWay)

See Section 3.1.1.

3.3.9 ESR 6792797 (CICS eWay)

See Section 3.1.1.

3.3.10 ESR 66792804 (COBOL Copybook Converter)

See Section 3.1.1.

3.3.11 ESR 6792798 (COM/DCOM eWay)

See Section 3.1.1.

3.3.12 ESR 6785598 (DB2 eWay)

See Section 3.1.1.

3.3.13 ESR 6785600 (e-Mail eWay)

See Section 3.1.1.

3.3.14 ESR 6792808 (File eWay)

See Section 3.1.1.

3.3.15 ESR 6792802 (HL7 OTD Library)

See Section 3.1.1.

3.3.16 ESR 6785601 (HTTPS eWay)

See Section 3.1.1.

3.3.17 ESR 6792809 (IMS eWay)

See Section 3.1.1.

3.3.18 ESR 6785602 (JDBC/ODBC eWay)

See Section 3.1.1.

3.3.19 ESR 6792799 (LDAP eWay)

See Section 3.1.1.

3.3.20 ESR 6792806 (MSMQ eWay)

See Section 3.1.1.

3.3.21 ESR 6785609 (Oracle Applications eWay)

See Section 3.1.1.

Note: When building an OTD with the Oracle Applications OTD Wizard, in the step titled "Select Oracle Applications Module" you must select the Replace Existing Stored Procedure option.

3.3.22 ESR 6785603 (Oracle eWay)

See Section 3.1.1.

3.3.23 ESR 6785616 (SAP ALE eWay)

See Section 3.1.1.

3.3.24 ESR 6785611 (SAP BAPI eWay)

See Section 3.1.1.

3.3.25 ESR 6792800 (Siebel EAI eWay)

See Section 3.1.1.

3.3.26 ESR 6792810 (SNA eWay)

See Section 3.1.1.

3.3.27 ESR 6785617 (SQL Server eWay)

See Section 3.1.1.

3.3.28 ESR 6788205 (SWIFT OTD Library)

See Section 3.1.1.

3.3.29 ESR 6792807 (Sybase eWay)

See Section 3.1.1.

3.3.30 ESR 6790929 (TCP/IP eWay)

See Section 3.1.1.

3.3.31 ESR 6790931 (TCP/IP HL7 eWay)

See Section 3.3.1 for prerequisites and corequisites, then follow the instructions below.

3.3.31.1 Installation

*Note: *If you are downloading from Goldstar, see these important notes.

The steps required to install ESR 6790931 are:

1. Extract the ESR6790931-dist.zip file to a temporary directory as described in "Extracting ESR Distribution Zip Files".
2. Use the Suite Installer to upload ESR6790931.sar to the Repository as described in "Uploading Enterprise Designer and Logical Host ESRs from the Suite Installer".

3.3.31.2 Post-installation Steps

A sample project named prjHL7Inbound is available from the Downloads tab of the Suite Installer after ESR6790931.sar is successfully uploaded.

IMPORTANT: If you have another project in Enterprise Designer named prjHL7Inbound you must rename it to something different prior to importing the sample project.

3.3.32 ESR 6792795 (UDDI Server)

See Section 3.3.1 for prerequisites and corequisites, then follow the instructions below

3.3.32.1 Installation

This 5.1.3U3 UDDI ESR includes only one new fix (BugID 6615499 - UDDI password can not use any other password but STC) on top of 5.1.3U2 ESR 6649271. If this new fix is not needed, please install 5.1.3U2 ESR 6649271 instead. Otherwise, please follow instructions below to re-install UDDI server.

*Note: *If you are downloading from Goldstar, see these important notes.

1. Extract the ESR6792795-dist.zip file to a temporary directory, as described in "Extracting ESR Distribution ZIP Files".
2. Extract the UDDI installation SAR file based on the platform you are using; for example, stcuddi-Win32.sar.
3. Use the Suite Installer to upload the UDDI SAR file to the Repository as described in "Uploading Files to the Repository".
4. Download and install the UDDI server as described in the the "Web Services" section of the eGate Integrator User's Guide.

3.3.33 ESR 6792803 (WebSphere MQ eWay)

See Section 3.3.1.

4 Issues Addressed in Update Release 4

4.1 eGate — Repository (6787633)

4.2 eGate — Enterprise Designer (6787640)

4.3 eGate — NetBeans Relating to Enterprise Designer (6787639)

4.4 eGate — Enterprise Manager ESR-Install Utility (6730424)

There were no fixes to the ESR Install Utility for this update. For your convenience, this ESR includes the most up-to-date version of the utility.

4.5 eGate — Enterprise Manager (6787634)

4.6 eGate — LogicalHost (6787632)

4.7 eGate — JMS for LogicalHost (6787684)

4.8 eInsight Business Process Manager (6787685)

4.9 eTL Integrator (6788580)

4.10 eView Studio (6788203)

4.11 eVision Studio (6792793)

There were no changes to eVision Studio for this update release. For your convenience, this ESR includes the most up-to-date version of eVision Studio.

4.12 eIndex Single Patient View (6788204)

4.13 Alert Agent (6792794)

There were no changes to Alert Agent for this update release. For your convenience, this ESR includes the most up-to-date version of Alert Agent.

4.14 Batch eWay (6792796)

4.15 CICS eWay (6792797)

There were no changes to the CICS eWay for this update release. For your convenience, this ESR includes the most up-to-date version.

4.16 COBOL CopyBook Converter (6792804)

There were no changes to the COBOL CopyBook Converter for this update release. For your convenience, this ESR includes the most up-to-date version.

4.17 COM/DCOM eWay (6792798)

There were no changes to the COM/DCOM eWay for this update release. For your convenience, this ESR includes the most up-to-date version.

4.18 DB2 eWay (6785598)

4.19 e-Mail eWay (6785600)

4.20 File eWay (6792808)

There were no changes to the File eWay for this update release. For your convenience, this ESR includes the most up-to-date version.

4.21 HL7 OTD Library (6792802)

There were no changes to the HL7 OTD Library for this update release. For your convenience, this ESR includes the most up-to-date version.

4.22 HTTPS eWay (6785601)

4.23 IMS eWay (6792809)

There were no changes to the IMS eWay for this update release. For your convenience, this ESR includes the most up-to-date version.

4.24 JDBC/ODBC eWay (6785602)

4.25 LDAP eWay (6792799)

There were no changes to the LDAP eWay for this update release. For your convenience, this ESR includes the most up-to-date version.

4.26 MSMQ eWay (6792806)

There were no changes to the MSMQ eWay for this update release. For your convenience, this ESR includes the most up-to-date version.

4.27 Oracle Applications eWay (6785609)

4.28 Oracle eWay (6785603)

4.29 SAP ALE eWay (6785616)

4.30 SAP BAPI eWay (6785611)

4.31 Siebel EAI eWay (6792800)

There were no changes to the Siebel EAI eWay for this update release. For your convenience, this ESR includes the most up-to-date version.

4.32 SNA eWay (6792810)

There were no changes to the SNA eWay for this update release. For your convenience, this ESR includes the most up-to-date version.

4.33 SQL Server eWay (6785617)

4.34 SWIFT OTD Library (6788205)

4.35 Sybase eWay (6792807)

There were no changes to the Sybase eWay for this update release. For your convenience, this ESR includes the most up-to-date version.

4.36 TCP/IP eWay (6790929)

4.37 TCP/IP HL7 eWay (6790931)

4.38 UDDI Server (6792795)

There were no changes to the UDDI Server for this update release. For your convenience, this ESR includes the most up-to-date version.

4.39 WebSphere MQ eWay (6792803)

There were no changes to the WebSphere MQ eWay for this update release. For your convenience, this ESR includes the most up-to-date version.

5 Known Issues and Workarounds

5.1 6644346 eTL: DriverProperties must be set when using JDBC eWay with eTL.

Problem Summary
When using eTL in conjunction with the JDBC eWay, an exception occurs (java.sql.SQLException "No suitable driver at java.sql.DriverManager.getConnection") if the JDBC external system's DriverProperties have no value set for the URL connect string property.

Workaround
Set the properties in the JDBC external system (Outbound JDBC eWay - JDBC Connector settings - DriverProperties) so as to include the URL connect string. As an example, for DB2 on AS400, this string would be as follows:
setURL#jdbc:as400://myas400host:446;naming=sql;errors=full##

5.2 6692447 eTL: Full outer join is not supported for all data sources.

Problem Summary
Certain data sources do not support the use of a full outer join, though Java CAPS does not prevent you from creating an invalid full outer join. Full outer joins are not supported by the Axion database, for tables that are from different databases, or with flat-file data sources. Full outer joins are supported if all tables in the join belong to the same relational database (for example, Oracle, SQL Server, and DB2).

Workaround
Only create full outer joins for the supported case described above.

5.3 6657450 eView: The JNDI settings in the eView Javadocs sample are incorrect.

Problem Summary
The server settings in the sample provided with the eView Javadocs are based on previous version and need to be updated in order for the sample client to work. These are the incorrect lines in the sample:
// server connection parameters
String server = "java://localhost:18005";
String jndiName = "ejb/PersonMasterController";
...

// connect to server and get handle MasterController
Hashtable env = new Hashtable();
env.put("java.naming.factory.initial", "com.stc.is.naming.NamingContextFactory");
env.put("java.naming.provider.url", server);
env.put(Context.OBJECT_FACTORIES, "com.stc.is.naming.CorbaObjectFactory");
Context context = new InitialContext(env);
Object obj = context.lookup(jndiName);

Workaround
Replace the above lines with the following text:
//server connection parameters
String url = "iiop://localhost:18002";
String ctxtFactoryName = "com.sun.jndi.cosnaming.CNCtxFactory";
...

//connect to server and get handle MasterController
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, ctxtFactoryName);
env.put(Context.PROVIDER_URL, url);
InitialContext jndiContext = new InitialContext(env);
Object obj = jndiContext.lookup("ejb/PersonMasterController");

5.4 6718625 Reports Do Not Generate

Problem Summary
If a field is included in the EDM reports but is not configured to be visible on the EDM, the reports will not generate.

Workaround
To work around this issue, do not include fields that are not visible on the EDM in the reports.

5.5 6582807 Using DB2 Non-Journaled Tables

Problem Summary
The DB2 eWay throws an exception when trying to insert data into a non-journaled DB2 table due to a limitation of the DataDirect drivers.

Workaround
Do one of the following:

• In the DB2 database, set journalling to true for the tables being accessed by the eWay.
• In the Java Collaboration Definition, set the transaction isolation level to NONE and set autocommit to true.

5.6 6598637 Decreased Performance With Oracle eWay

Problem Summary
The Oracle eWay experiences decreased performance when an insert is done using a table OTD because a full table scan is performed.

Workaround
Do one of the following:

• Use select() with a where clause that avoids a full table scan (for example, 1=0 or <UniqueIndex>=<NonExistingValue>) and then moveToInsertRow()
• Use a preparedStatement OTD instead of the table OTD.

5.7 6606791 DB2 Connect Statements Hold Open Numerous Cursors

Problem Summary
A DB2 statement holds numerous cursors open until the Java Collaboration Definition (JCD) is finished. This occurs because the default value of auto-commit is false for the driver mode.

Workaround
Manually change the default value of auto-commit, or commit the statement manually in the JCD. Listed below are the default values for the three DB2 Connect Type 2 driver options in the Connectivity Map and Environment.

• DB2 Connect XA - autocommit is set to false
• DB2 Connect Non-Transactional - autocommit is set to true
• DB2 Connect Local - autocommit is set to false

5.8 6807907 Enterprise Manager Displays Running Components as Down

Problem Summary
The monitoring console on the Enterprise Manager shows certain components as being down when they are actually deployed and running successfully.

Workaround
There is currently no workaround for this issue. It does not affect how the affected components run, but does prevent access to information for the components.

5.9 6815720 The Web Service eWay Icon is Wrong in Enterprise Manager

Problem Summary
The monitoring console on the Enterprise Manager displays the wrong icon for the Web Service eWay, and the name of the eWay is missing as well.

Workaround

6 Additional Information and Instructions

6.1 Using the New Repository Replicate Tool

ESR 6787633 includes a command-line utility that copies the entire repository (including all installed products), and that allows the host name and port numbers to be changed. The utility is named replicate.bat for Windows and replicate.sh for Unix. This utility was first introduced in Release 5.1.3 Update 2.

The utility is intended to be executed on the machine to which you want the repository moved (hereafter called the 'target machine'.) The machine from which the repository is being copied is called the 'r?source machine'.

6.1.1 Replicating a Repository

This section provides instructions for copying an entire repository from a source machine to a target machine. Perform the steps on the source machine first, followed by the steps for the target machine.
On the source machine, do the following:

1. Install the ESR 6787633.
2. Start the repository.
3. Change to the directory where the replicate utility (replicate.bat or replicate.sh) is located.
4. Create a backup of the source repository by running the following command:
   • For Windows: replicate.bat export <username> <password> <RepositoryBackupFileName>
   • For Unix: replicate.sh export <username> <password> <RepositoryBackupFileName>

On the target machine, do the following:

1. Ensure that the Java CAPS Repository CD1 (or a copy of its contents) is available on the target machine. The location of install.bat (on Windows) or install.sh (on Unix) is a required parameter for the replicate utility.
2. Copy the following files from the source machine to the target machine:
   • <repository>\util\replicate.bat (on Windows) or <repository>/util/replicate.sh (on Unix)
   • The backup file created above from running the replicate utility on the source machine. If you do not want to copy the files from the source machine to the target machine, you can create a shared network directory on the target machine that points to the respective directories on the source machine.
3. Change to the directory where the replicate utility is located.
4. Start the replicate utility by running one of the following commands:
   • For Windows: replicate.bat import <RepositoryImagePath> <TargetRepositoryPath> <ExistingRepositoryName> <TargetRepositoryPort> <BackupFile>
   • For Unix: replicate.sh import <RepositoryImagePath> <TargetRepositoryPath> <ExistingRepositoryName> <TargetRepositoryPort> <BackupFile>

where:

• RepositoryImagePath is the location of install.bat or install.sh on the Java CAPS Repository CD1.
• TargetRepositoryPath is the location where you want the copied repository to be installed.
• ExistingRepositoryName is the name of the original repository.
• TargetRepositoryPort is the starting port number for the copied repository. You need to allocate 9 contiguous port numbers for the target repository.
• BackupFile is the location of the backup file created by running the replicate utility on the source machine.

The contents of the original repository are now available in the location specified by 'TargetRepositoryPath'. The target repository can be started by running the repository startup command (startserver.bat for Windows or startserver.sh for Unix) from the TargetRepositoryPath directory.

6.2 Deploying an eView Client on a Separate Domain

If you need to deploy an eView client to a separate domain, perform the following steps:

1. Navigate to <CAPS_Home>/edesigner/bin and open runed.bat for editing.
2. Insert the following parameter into the runidew command:
   -J-DJNDI_PROVIDER_URL="corbaname:iiop:<eView-server-host>:<port>" where <eView-server-host> is the machine where the eView server application is deployed and <port> is the iiop port number (non-secured iiop-listener id="orb-listener-1" in domain.xml).
   • For example:
     • For the SeeBeyond Application Server: -J-DJNDI_PROVIDER_URL="corbaname:iiop:MyHost:18002"
     • For the GlassFish application server: -J-DJNDI_PROVIDER_URL="corbaname:iiop:MyHost:3700"
3. Save and close runed.bat.
4. Open the eView server Project in Enterprise Designer.
5. Regenerate the eView application, and then rebuild the eView server Project.
6. Re-import all generated JAR files for any Collaboration client Projects that reference the eView application.
7. Rebuild any eView client Projects.
8. Redeploy the eView server and client EAR files.

6.3 Dynamically Configuring SAP Connectivity

The following environment properties are exposed for the SAP outbound eWay:

• Application Server Host Name
• System Number
• Client Number
• User
• Password
• Language
• System ID
• Gateway Host Name
• Gateway Service
• Message Server Host Name
• Application Server Group
• Router String
  To use the new OTD:

1. Set the connection parameter values using the setXXX() methods.
   Note: If a parameter value is not changed, the value configured in the External System is used.
2. Call connectWithNewParams() to update the SAP connector configuration object values with the dynamic values.
3. Call connect() to establish the actual connection to SAP.

7 Documentation Errata and Omissions

The following information replaces or enhances information available in the documentation provided with Java CAPS 5.1.3.

7.1 Supported Apache Ant Version

On page 156 of the eGate Integrator User's Guide, the supported version of Apache Ant is listed as version 6. This should be version 1.6.

7.2 Oracle References in the eWay Adapter for SQL Server User's Guide

There are references to Oracle in the SQL Server eWay guide.

• On page 21:
  • Outbound Oracle eWay should be Outbound SQLServer eWay
  • Outbound Oracle non-Transactional eWay should be Outbound SQL Server non-Transactional eWay
  • Outbound Oracle XA-eWay should be Outbound SQL Server XA-eWay
• On Page 25,
  • Oracle thin driver non-Transactional Connection Pool Datasource should be Sqlserver driver non-Transactional Connection Pool Datasource
  • oracle.jdbc.pool.OracleConnectionPoolDataSource }} should be {{com.SeeBeyond.sqlserver.jdbcx.sqlserver.SQLServerDataSource

7.3 MaxPoolSize Documented Incorrectly for Database eWays

Most database eWay user's guides include the following description for the MaxPoolSize property:
Specifies the maximum number of physical connections the pool should keep available at all times. 0 (zero) indicates that there is no maximum.

The Sun SeeBeyond Integration Server does not support unlimited connections. When the MaxPoolSize is less than the MinPoolSize, then the MinPoolSize is used as the maximum number of pools.

7.4 Image Does not Match Default Port Number

In the eGate Integrator User's Guide under section 10.8.2, "Starting the Java Debugger", the image under step 3A shows the port number as 18000. The default port number is 1044.

7.5 Instructions for Changing a Keystore Location are not Provided

The eGate Integrator System Administration Guide describes how to create and configure keystores and truststores in section 12.6.2 (pages 168-176). This section does not provide information on how to change the keystore location when using the Sun SeeBeyond Integration Server.

You change the keystore location in the Integration Server's JVM parameters as follows:

-Djavax.net.ssl.keyStore=${com.sun.aas.instanceRoot}/config/keystore.jks
-Djavax.net.ssl.keyStorePassword=changeit
-Djavax.net.ssl.trustStore=${com.sun.aas.instanceRoot}/config/cacerts.jks

7.6 Pointer to Wrong Document for SSL Configuration

The eInsight Business Process Manager User's Guide incorrectly directs the reader to the eGate Integrator User's Guide for SSL information. This information is actually provided in the eGate Integrator System Administration Guide.

7.7 MySQL Driver Properties are Required

In section A.3.2 of the JDBC/ODBC eWay Adapter User's Guide, it states that the DriverProperties field is not required for MySQL databases. The field is required, and is the URL of the database in the format jdbc:mysql://<hostname>:<port_number>/<database_name>.

7.8 Incorrect Syntax for eInsight LDAP Tutorials

The syntax for the schema definition for the Audit Processing and Worklist Manager tutorials is missing spaces. This schema is defined in section C.2.1 of the eInsight Business Process Manager User's Guide. The schema should be defined as follows:

# schema/stc.schema
#
# Auxiliary Object Class to be used with Person (or subtypes of it)
#
# Roles allow a user to be cross functional
attributetype ( 1.3.6.1.4.1.1351.666.1.1
NAME 'stcWFRole'
DESC 'STC WorkFlow User Roles' SUP organizationalUnitName )
# Groups provide department level groupings
attributetype ( 1.3.6.1.4.1.1351.666.1.2
NAME 'stcWFGroup'
DESC 'STC WorkFlow User Group' SUP organizationalUnitName )
# Manager shows hierarchy in the organization
attributetype ( 1.3.6.1.4.1.1351.666.1.3
NAME 'stcWFManager'
DESC 'STC WorkFlow User Manager'
EQUALITY distinguishedNameMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 SINGLE-VALUE )
# stcWorkFlowPerson
# The stcWorkFlowPerson represents people who are associated with
# an organization in both a department and a role. It is an
# auxiliary class
objectclass( 1.3.6.1.4.1.1351.666.1
NAME 'stcWorkFlowPerson'
DESC 'STC Work Flow Assignment Person'
AUXILIARY
MAY ( stcWFRole $ stcWFGroup $ stcWFManager )
)

7.9 The eInsight End-to-End Payroll Tutorial is Missing a Step

In Appendix B of the eInsight Business Process Manager User's Guide, the instructions for the Payroll Tutorial are missing the instructions to marshal the data. Without this step, the Project fails to run. After you complete the steps under "Configuring the Match Fields Activity", perform the following additional steps:

1. Right-click the connector between Prepare Output and Process Payroll, and click Add Business Rule.
2. In the Business Rule Designer, expand the attributes trees in both the left and right panels.
3. Click contents in the left panel and drag a connector to text in the right panel.
4. Save and close the Business Process.

7.10 There is no Upper Limit for Number of RFC Servers in SAP BAPI eWay

In table 4 (Inbound eWay - Server Connection Settings) of the SAP BAPI eWay Adapter User's Guide, it states that the valid value for the Number of RFC Servers to Create is any integer from 1 to 10. The lower limit of 1 is correct, but there is no upper limit.