Searching Java CAPS

1 About Updates for Sun Java CAPS 6

These Java CAPS Updates are designed to simplify the maintenance of a Java CAPS installation by delivering a comprehensive set of product-specific patches. Each patch contains all updates for that product made since the GA Release. An additional benefit is that the patches that constitute this Update are self-consistent, since the Update has been verified as a whole.

2 Contents of this Update

Update 1 for Sun Java CAPS 6 (henceforth called "CAPS 6U1") consists of the following types of patches:

1. Patch for NetBeans 6.1 - this upgrades your NetBeans installation to NetBeans 6.1 Patch 4 from NetBeans 6.1 Patch 1.
2. Patch for Sun Java System Application Server 9.1 UR2 (henceforth called AS 9.1UR2) - this upgrades your Application Server installation to Application Server 9.1 UR2 Patch 3.
3. Updated CAPS patch utilities
4. CAPS-specific jumbo patches as specified in the table below

There are five CAPS-specific jumbo patches in CAPS 6U1. They are:

3 New Features

3.1 Newly Supported Platforms and Systems

• Now compatible with Open Solaris 2008.05
• Now compatible with Windows XP SP3
• Now built on GlassFish 9.1 Update 2 Patch 3
• Now built on Netbeans 6.1 Patch 4
• Many components are now compatible with MySQL

For a complete listing of supported operating systems, see Java CAPS Supported Operating Systems in Planning for Java CAPS Installation

3.2 New Components

3.2.1 New Service Engines and Project Types/Editors:

• IEP (Intelligent Event Processor) - The IEP engine and editors are used for Complex Event Processing (CEP) and Event Stream Processing (ESP) using the Continuous Query Language (CQL). A rich set of built-in operators and GUI tools are provided to create and analyze messages from clouds and streams.
• XSLT - The XSLT engine and editors are used to transform data between different XML schemas.
• Data Mashup - The Data Mashup engine and editors provide data federation or mashup services to Java CAPS components included with Update 1. Mashup allows for a single relational view of data that have different origins but are located within the same enterprise.

3.2.2 New Binding Components (BCs):

• Database
• JMS
• File
• FTP
• LDAP

3.2.3 New JCA Adapters and Code Seeders:

• TCP/IP
• Oracle Applications

3.2.4 New Repository-based Components:

• HL7 Adapter
• Message Library for HL7 2.6

3.2.5 Other Components:

• JMS JCA wizard and code seeder
• Custom encoders: Provides OTD-like capabilities outside of the Repository and without tight coupling to specific adapters.

3.3 Enhancements to Existing Components

• BPEL SE - Now supports MySQL 5.0, and failover
• HTTP BC - Now supports SOAP Version 1.2
• Support for SWIFT 2008 Message Libraries

3.4 Enhancements to Master Data Management (MDM) Suite

• New data mashup services; see New service engines above.
• Sun Master Index now supports MySQL Enterprise Server (ES) 5.1
• The Initial Bulk Match and Load tool now supports MySQL ES 5.1
• Master Index now requires two connection pools and two JDBC resources; one is for the main application connection and the second is for the sequence generator. Previously, it used one connection pool and one JDBC resource.
• Master Index Data Manager now allows unmerging of two system records.
• Master Index Data Manager was enhanced to improve readability, workflow, validations, and error messaging.
• When outbound messages are generated for updates to the Master Index database, reversing an assumed match now results in an Assumed Match outbound message.
• The Data Integrator Wizard was updated to provide complete steps for creating an ETL processes that include multiple data sources of multiple types, including flat files, relational databases, Excel spreadsheets, HTML pages, and so on. The wizard allows you to configure the data sources and targets, and to map the source tables to the target tables.
• The Data Integrator Wizard provides complete steps for creating a Master Index staging database and the ETL collaboration that extracts bulk data from source system databases. The staging database can be used by the Sun Master Index data quality tools and by the Initial Bulk Match and Load tool.
• The Data Integrator Bulk Loader can now be generated and configured using the Data Integrator Wizard. The generated Bulk Loader can be run from the NetBeans IDE. The command line tool is still available.

4 Interoperability

Interoperability testing between Java CAPS 6 Update 1 and the Java Enterprise System (JES) has been completed for the following products:

Known Interoperability Issues With Sun Java System Access Manager

6690970 No Support for HTTP Binding Component Authentication with Access Manager in Legacy Mode

6695565 No Support for HTTP Binding Component Authentication for x.500 Suffix Naming Convention

6707146 The Default Access Manager Setup Provided by Java CAPS does not Work with Federated Access Manager 8.0

Known Interoperability Issues With Sun Java Portal Server

6662622 Worklist Manager Portlet from Java CAPS 5.1.3 does not Deploy on Portal Server 7

Known Interoperability Issues With Sun Java Application Server

5 Installation

IMPORTANT: In order for your CAPS 6 installation to function correctly, you must install the NetBeans, Application Server and CAPS-specific patches listed in section 2 above. You must also install the updated CAPS patch utilities. You do not need to install the Jumbo patches if you already have the full install of CAPS 6 U1 at your end.

4.1 Installation Sequence

The patches that constitute Update 1 need to be installed in the following sequence:

1. Patch for NetBeans 6.1
2. Patch for AS 9.1 UR2
3. Patch Utilities
4. Repository Jumbo Patch (6744145-01)
5. NetBeans Jumbo Patch (6744143-01)
6. Remaining patches (6744148-01, 6744146-01, 6744151-01) in any order

4.2 Detailed Installation Instructions

NOTE: In the following sections,

• JavaCAPS6-install-dir is the directory where you installed Java CAPS.
• patch-dir is the temporary directory where you downloaded the patch being discussed.

4.2.1 Patch for NetBeans 6.1

NOTE: This patch needs to be installed on every system where NetBeans 6.1 is installed.

1. Check under Tools -> Plugins -> Settings that only "NetBeans" and "CAPS Repository Update Center" are selected.
2. Download the file nb137824.zip from http://sunsolve.sun.com to a temporary directory (patch-dir).
3. Extract the contents of the zip file in patch-dir.
4. From the NetBeans main menu, select the Tools -> Plugins menu option.
5. Click on the "Downloaded" tab in the "Plugins" dialog.
6. Click the "Add Plugins" button.
7. Navigate to patch-dir in the resulting file-selection dialog.
8. Select all the .nbm files that were extracted from nb137824.zip and click "Open".
9. The list of plugins you selected is now populated in the "Plugins" dialog.
10. Select all the plugins and click the "Install Plugins" button.
11. Follow any on-screen instructions and restart the IDE, if prompted. (If you have already updated your netbeans installation via internet update it may occur that some or all of your plugins are prompted as "already installed" and will not be in the installable list.)

Your NetBeans installation has now been upgraded to NetBeans 6.1 Patch 4.

4.2.2 Patch for Sun Java System Application Server 9.1 UR2

4.2.2.1 Special Instructions for Installation on UNIX Platforms

If you are installing the patch for AS 9.1UR2 on a UNIX platform, you must follow the instructions in this section prior to those in the next section or your installation will fail.

1. Check if you have an application server domain named "domain1" in your installation. You could do this by running the following command:
   JavaCAPS6-install-dir/appserver/bin/asadmin list-domainsIf the command returns a line that says either "domain1 is not running" or "domain1 running" you have a domain named "domain1" in your installation.
2. If you do not have a domain named "domain1" installed, skip to the next section (4.2.2.2) otherwise, go to the next step.
3. Back up domain1 by executing the following command:
   JavaCAPS6-install-dir/bin/asadmin backup-domain domain1
4. Rename the directory "domain1" to a different name, say "orig_domain1"
   $ mv JavaCAPS6-install-dir/appserver/domains/domain1 JavaCAPS6-install-dir/appserver/domains/orig_domain1
5. Install the patch for AS 9.1UR2 following the instructions in the next section (4.2.2.2).
6. Delete the directory "domain1"
   $ rm -rf JavaCAPS6-install-dir/appserver/domains/domain1
7. Rename the directory "orig_domain1" to "domain1"
   $ mv JavaCAPS6-install-dir/appserver/domains/orig_domain1 JavaCAPS6-install-dir/appserver/domains/domain1

4.2.2.2 Installation Instructions for all Platforms

NOTE: If you are installing the patch on a UNIX platform, follow the instructions in section 4.2.2.1 first. Then follow the instructions in this section.

The patches for AS 9.1UR2 are delivered as 6 different files, one per installation platform. The files and the associated platforms are listed in the table below:

1. Shut down the application server and all domains that are running.
2. Download the patch for your platform from http://sunsolve.sun.com/ to a temporary directory (patch-dir). If you run into any issues downloading the patch, please contact JAVA CAPS support at caps-support@sun.com.
3. Extract the contents of the downloaded file. The extraction process creates a folder with the patch ID in patch-dir.
4. Change to directory patch-dir/patchID.
5. Run the executable (typically named sjsas-9_1_02-p03-platform). For example, this file is named sjsas-9_1_02-p03-windows.exe on Windows.
6. Use the default options and set the installation directory to be the directory where you have installed the application server (in most Java CAPS 6 installations, it should be JavaCAPS6-install-dir/appserver). Do not select any other options.
7. Follow all other instructions in the installation wizard.

4.2.3 Patch Utilities

1. Download esr6788313.zip from http://goldstar.stc.comto a temporary directory (patch-dir) and extract the patch utilities caps-patch.zip.
2. Stop any running instances of CAPS 6 patch utilities.
3. In a Windows Command Prompt or UNIX Terminal window, navigate to the directory where you installed Java CAPS (JavaCAPS6-install-dir).
4. Extract the downloaded file patch-dir/caps-patch.zip to JavaCAPS6-install-dir.

4.2.4 Patch 6744145-01 (Repository Jumbo Patch)

4.2.4.1 Prerequisites

None.

4.2.4.2 Corequisites

• 6744143-01 (NetBeans Jumbo Patch)
• 6744148-01 (Commandline Codegen Jumbo Patch)
• 6744146-01 (Runtime Jumbo Patch)
• 6744151-01 (Enterprise Manager Jumbo Patch)

4.2.4.3 Installation

1. Download esr6788313.zip from http://goldstar.stc.com to a temporary directory (patch-dir) and extract the patch 6744145-01-REP.zip.
2. In a Windows Command Prompt or UNIX Terminal window, navigate to JavaCAPS6-install-dir/repository/repository.
3. At the command line, run the following command to stop the repository server: stopserver.bat (for Windows) or ./stopserver.sh (for UNIX).
4. In a Windows Command Prompt or UNIX Terminal window, navigate to JavaCAPS6-install-dir/caps-patch/util/bin.
5. At the command line, run the following command:
   caps-patch-install -verbose -repuser userid -reppwd password -b JavaCAPS6-install-dir\repository -t REP -patch patch-dir/6744145-01-REP.zip (for Windows)
   ./caps-patch-install -verbose -repuser userid -reppwd password -b JavaCAPS6-install-dir\repository -t REP -patch patch-dir/6744145-01-REP.zip  (for UNIX)
   NOTE: Your repository might require the additional parameters -repuser userid -reppwd password
6. To verify that this patch was installed, run caps-patch-info.bat or ./caps-patch-info.sh. In the resulting list, you should see the following entry:
   6744145-01 :CAPS R6U1 Repository Jumbo Patch.

4.2.5 Patch 6744143-01 (NetBeans Jumbo Patch)

4.2.5.1 Prerequisites

• 6744145-01 (Repository Jumbo Patch) must be installed prior to installing Patch 6744143-01.

4.2.5.2 Corequisites

• 6744148-01 (Commandline Codegen Jumbo Patch)
• 6744146-01 (Runtime Jumbo Patch)
• 6744151-01 (Enterprise Manager Jumbo Patch)

4.2.5.3 Installation

1. Download esr6788313.zip from http://goldstar.stc.comto a temporary directory (patch-dir) and extract the patch 6744143-01-DT-NB.zip.
2. Stop any running instances of NetBeans IDE.
3. In a Windows Command Prompt or UNIX Terminal window, navigate to JavaCAPS6-install-dir/caps-patch/util/bin.
4. At the command line, run the following command:
   caps-patch-install -verbose -b JavaCAPS6-install-dir\netneans -t DT-NB -patch patch-dir/6744143-01-DT-NB.zip (for Windows)
   ./caps-patch-install -verbose -b JavaCAPS6-install-dir\netneans -t DT-NB -patch patch-dir/6744143-01-DT-NB.zip  (for UNIX).
5. To verify that this patch was installed, run caps-patch-info.bat or ./caps-patch-info.sh. In the resulting list, you should see the following entry:
   6744143-01 :CAPS R6U1 NetBeans Jumbo Patch.

4.2.5.4 Post-Installation for Sun Master Index Only

Once you install the NetBeans Jumbo Patch, you need to copy some of the updated NetBeans files into any existing Sun Master Index projects. See Section 4.6 (below) for instructions.

4.2.6 Patch 6744148-01 (Commandline Codegen Jumbo Patch)

4.2.6.1 Prerequisites

• 6744145-01 (Repository Jumbo Patch)
• 6744143-01 (Design Time - NetBeans)

4.2.6.2 Corequisites

• 6744146-01 (Runtime Jumbo Patch)
• 6744151-01 (Enterprise Manager Jumbo Patch)

4.2.6.3 Installation

NOTE: If you have a new installation, and have not yet run commandline codegen, you need to run it once to set up the command-line environment.

1. Download esr6788313.zip from http://goldstar.stc.com to a temporary directory (patch-dir) and extract the patch 6744148-01-DT-CLI.zip.
2. Stop any running instances of Commandline Codegen.
3. In a Windows Command Prompt or UNIX Terminal window, navigate to JavaCAPS6-install-dir/caps-patch/util/bin.
4. At the command line, run the following command:
   caps-patch-install.bat -verbose -b JavaCAPS6-install-dir\commandlinecodegen -t DT-CLI -patch patch-dir/6744148-01-DT-CLI.zip (for Windows)
   ./caps-patch-install -verbose -b JavaCAPS6-install-dir\commandlinecodegen -t DT-CLI -patch patch-dir/6744148-01-DT-CLI.zip (for UNIX)
5. To verify that this patch was installed, run caps-patch-info.bat or ./caps-patch-info.sh. In the resulting list, you should see the following entry:
   6744148-01 :CAPS R6U1 Commandline Codegen Jumbo Patch.

4.2.7 Patch 6744146-01 (Runtime Jumbo Patch)

4.2.7.1 Prerequisites

• 6744145-01 (Repository Jumbo Patch)
• 6744143-01 (NetBeans Jumbo Patch)

4.2.7.2 Corequisites

• 6744148-01 (Commandline Codegen Jumbo Patch)
• 6744151-01 (Enterprise Manager Jumbo Patch)

4.2.7.3 Installation

4.2.7.3.1 To Patch a Single Domain in a Multiple Domain Environment

1. Download esr6788313.zip from http://goldstar.stc.com to a temporary directory (patch-dir) and extract the patch 6744146-01-RT.zip.
2. In a Windows Command Prompt or UNIX Terminal window, navigate to JavaCAPS6-install-dir.
3. At the command line, run the following command for each domain: stop-appserver-domain-name.
4. In a Windows Command Prompt or UNIX Terminal window, navigate to JavaCAPS6-install-dir/caps-patch/util/bin.
5. At the command line, run the following command to patch the application server installation:
   caps-patch-install -verbose -b JavaCAPS6-install-dir\appserver -t RT -patch patch-dir/6744146-01-RT.zip.
6. At the command line, run the following command to patch the domain domain-name:
   caps-patch-install -verbose -b JavaCAPS6-install-dir\appserver -domaindir \JavaCAPS6-install-dir\appserver\domains -domain domain-name -t RT -patch patch-dir_/6744146-01-RT.zip (for Windows)
   ./caps-patch-install -verbose -b JavaCAPS6-install-dir\appserver -domaindir \JavaCAPS6-install-dir\appserver\domains -domain domain-name -t RT -patch patch-dir_/6744146-01-RT.zip (for UNIX).
7. To verify that this patch was installed, run caps-patch-info.bat or ./caps-patch-info.sh. In the resulting list, you should see the following entries:
   Runtime Environment:
   6744146-01 :CAPS R6U1 Runtime Jumbo Patch (for the Application Server)
   Runtime Environment: Domain:domain-name
   6744146-01 :CAPS R6U1 Runtime Jumbo Patch (for the Domain)

4.2.7.3.1 To Patch All Domains At Once

1. Download esr6788313.zip from http://goldstar.stc.com to a temporary directory (patch-dir) and extract the patch 6744146-01-RT.zip.
2. In a Windows Command Prompt or UNIX Terminal window, navigate to JavaCAPS6-install-dir.
3. At the command line, run the following command for each domain: stop-appserver-domain-name.
4. In a Windows Command Prompt or UNIX Terminal window, navigate to JavaCAPS6-install-dir/caps-patch/util/bin.
5. At the command line, run the following command to patch all domains and the application server installation:
   caps-patch-install -verbose -b JavaCAPS6-install-dir\appserver -domaindir \JavaCAPS6-install-dir\appserver\domains -t RT  -patch patch-dir/6744146-01-RT.zip -domain all (for Windows)
   ./caps-patch-install -verbose -b JavaCAPS6-install-dir\appserver -domaindir \JavaCAPS6-install-dir\appserver\domains -t RT  -patch patch-dir/6744146-01-RT.zip -domain all (for UNIX).
6. To verify that this patch was installed, run caps-patch-info.bat or ./caps-patch-info.sh. In the resulting list, you should see the following entries:
   Runtime Environment:
   6744146-01 :CAPS R6U1 Runtime Jumbo Patch (for the Application Server)
   Runtime Environment: Domain:domain-name
   6744146-01 :CAPS R6U1 Runtime Jumbo Patch (repeated for each Domain)

4.2.8 Patch 6744151-01 (Enterprise Manager Jumbo Patch)

4.2.8.1 Prerequisites

• 6744145-01 (Repository Jumbo Patch)
• 6744143-01 (NetBeans Jumbo Patch)

4.2.8.2 Corequisites

• 6744148-01 (Commandline Codegen Jumbo Patch)
• 6744146-01 (Runtime Jumbo Patch)

4.2.8.3 Installation

1. Download esr6788313 from http://goldstar.stc.com to a temporary directory (patch-dir) and extract zipthe patch 6744151-01-EM.zip.
2. In a Windows Command Prompt or UNIX Terminal window, navigate to JavaCAPS6-install-dir/emanager/.
3. At the command line, run the following command: stopserver.bat (for Windows) or ./stopserver.sh (for UNIX).
4. In a Windows Command Prompt or UNIX Terminal window, navigate to JavaCAPS6-install-dir/caps-patch/util/bin.
5. At the command line, run the following command:
   caps-patch-install -verbose -b JavaCAPS6-install-dir\emanager -t EM  -patch patch-dir/6744151-01-EM.zip (for Windows)
   ./caps-patch-install -verbose -b JavaCAPS6-install-dir\emanager -t EM  -patch patch-dir/6744151-01-EM.zip  (for UNIX)
6. To verify that this patch was installed, run caps-patch-info.bat. In the resulting list, you should see the following entry:
   6744151-01 :CAPS R6U1 Enterprise Manager Jumbo Patch.

4.3 Adapter Pack (OPTIONAL)

This pack contains adapters for TCP/IP and Oracle JCA. Note that the Adapter Pack is to be installed only on a NetBeans instance that does not have any CAPS components.

4.3.1 Installation

• Download esr6788313 from http://goldstar.stc.com to a temporary directory and extract the file AdapterPack.zip and unzip it to a temporary location.
• Go to the NetBeansGUI, click on Tools/Plugins. Click on the Downloaded tab and select the Add Plugins button and select the NBM you want to install from the earlier location.

4.4 HL7 OTD Library 2.6

4.4.1 Installation

• Download esr6788313 from http://goldstar.stc.com to a temporary directory and extract the file HL7OTDLibrary26.sar.
• Upload the sar file to the repository, install the HL7 OTD plugin through the CAPS Repository Update Center in the NetBeans GUI, and do a "Refresh All" under Tools/CAPS Repository.

4.5 SWIFT 2008 OTD Library

4.5.1 Installation

• Download esr6788313 from http://goldstar.stc.comto a temporary directory and extract the file SwiftOTDLibrary2008.sar.
• Upload the sar file to the repository, install the SWIFT OTD plugin through the CAPS Repository Update Center in the NetBeans GUI, and do a "Refresh All" under Tools/CAPS Repository.

4.6 Post-Installation Steps for Sun Master Index

Once you install the NetBeans Jumbo Patch (see Section 3.2.5), you need to copy some of the updated files into any existing Sun Master Index projects. It is not likely that any of these files would be customized in your installation, but you should backup any projects that you are going to update before beginning these steps. Perform these steps for each Master Index project.

1. If the Master Index project is open in the NetBeans IDE, close the project.
2. Navigate to JavaCAPS-install-dir/netbeans/soa2/modules/ext/mdm/repository/schema, and then copy the following files to project-home/src/Configuration/schema (where project-home is the location of the master index project files).
   • master.xsd
   • mefa.xsd
   • midm.xsd
   • object.xsd
   • query.xsd
   • validation.xsd
3. Navigate to JavaCAPS-install-dir/netbeans/soa2/modules/ext/mdm/standardizer/deployment.
4. Open Address.zip and extract the following files to project-home/src/StandardizationEngine/Address (or its appropriate subfolder), replacing the existing files:
   • serviceType.xml
   • /instance/AU/lib/standardizer-sbme-au-address.jar
   • /instance/AU/resources/masterClues.dat
   • /instance/UK/lib/standardizer-sbme-uk-address.jar
   • /instance/US/lib/standardizer-sbme-us-address.jar
5. In the deployment directory, open BusinessName.zip and extract the following files to project-home/src/StandardizationEngine/BusinessName (or its appropriate subfolder), replacing the existing files:
   • serviceType.xml
   • /instance/Generic/lib/standardizer-sbme-generic-businessname.jar
   • /lib/standardizer-sbme-businessname.jar
6. In the deployment directory, open PersonName.zip and extract /lib/standardizer-api.jar and /lib/standardizer-impl.jar to project-home/src/StandardizationEngine/PersonName/lib, replacing the existing files.
7. In the deployment directory, open PhoneNumber.zip and extract /lib/standardizer-api.jar and /lib/standardizer-impl.jar to project-home/src/StandardizationEngine/PhoneNumber/lib, replacing the existing files.
8. Clean and build the master index project and then redeploy the project.

6 Issues Addressed in Update Release 1

5.1 Repository Jumbo Patch (6744145-01)

5.2 NetBeans Jumbo Patch (6744143-01)

5.3 Commandline Codegen Jumbo Patch (6744148-01)

5.4 Runtime Jumbo Patch (6744146-01)

5.5 Enterprise Manager Jumbo Patch (6744151-01)

7 Known Issues and Workarounds

6.1 eTL/Data Integrator Compatibility Issue:

There is a compatibility issue with existing eTL/Data Integrator project scenarios (Modern) from previous Java CAPS releases (Java CAPS 6 GA and Java CAPS 5.1.x) that are migrated into Java CAPS 6 Update 1. To resolve this issue, you need to update the file PROJECT_HOME\nbproject\build-impl.xml (in each existing project scenario) by manually adding and saving the following two entries:

• include name="org-openide-io.jar"/
• include name="org-openide-explorer.jar"/

6.2 Intelligent Event Processor (IEP) Issues

6.2.1 Oracle JDBC Driver - Supported Version

Issue 449

If you want to configure the IEP database to use Oracle, then you must use Oracle JDBC driver version 10.2.0.4.0 or above. The default driver included with Oracle 9.2 (ojdbc14.jar) is version 9.0.2.0.0, and will not work with IEP. To determine the driver version you are using, view the manifest.mf file in the driver JAR file.

6.2.2 High Availability and Failover

Issue 1083

Problem: The IEP Service Engine may not work as expected in high availability and failover mode.

Assume that you have two instances of the IEP Service Engine: instance 1 and instance 2. Deploy a project on instance 1 and then on instance 2. Test the configuration by sending input messages. Instance 1 generates the output, which is the expected behavior.

Undeploy the project from instance 2 and then from instance 1.

Deploy the project again on instance 2 and then on instance 1. Instance 2 should be the owner of the process and, therefore, should generate the output. Test the configuration by sending input messages. Both instance 1 and instance 2 generate the output, which is not the expected behavior.

Workaround: Restart the IEP Service Engine on instance 2. This workaround ensures that instance 2 does not generate the output.

6.2.3 Time Based Aggregator Operator on Oracle

Issue 1169

Problem: When the IEP database is configured to use Oracle, the Time Based Aggregator operator may not work as expected.

Assume that the Time Based Aggregator operator has a size of 1 minute and an interval of 5 seconds. If one event is sent to the operator, the operator should send out an event every 5 seconds. At the end of one minute, the output file should contain 12 events. However, the output file contains only one event.

Workaround: None at this time.

6.2.4 Tuple Based Aggregator Operator on Oracle

Issue 1171

Problem: When the IEP database is configured to use Oracle, the Tuple Based Aggregator operator may not work as expected.

Assume that the Tuple Based Aggregator operator has a start value of 2, an increment value of 3, and a size value of 4. If four events are sent to the process, the calculation is triggered as expected. Because of the GROUP BY clause, the output should contain all four events. However, the output contains only the last event.

Workaround: None at this time.

6.2.5 IEP Issue When Upgrading to CAPS 6U1

Issue 1184

Problem: This issue applies only to upgrading from CAPS R6 to CAPS R6U1. After the patches are applied and the GlassFish application server is started, the IEP Service Engine might be unable to connect to Java DB or might return exceptions indicating that iepseDB does not exist.

Workaround: Uninstall and then reinstall the IEP Service Engine.

1. Go to the install-dir/appserver/domains/domain1/jbi/autoinstall directory and locate the iepserviceengine.jar file.
2. In the Services window of the NetBeans IDE, expand the Servers node, the GlassFish V2 node, the JBI node, and the Service Engines node.
3. Right-click the sun-iep-engine node and choose Uninstall. The IEP Service Engine is uninstalled.
4. Log in to the Sun Java System Application Server Admin Console.
5. Expand the Resources node and the JDBC node, and select the JDBC Resources node.
6. Delete jdbc/iepseDerbyXA and jdbc/iepseDerbyNonXA.
7. If the iepseDB directory exists in the install-dir/.netbeans-derby directory, then log out of the NetBeans IDE and remove the iepseDB directory.
8. Restart the NetBeans IDE and then restart the GlassFish application server.
9. Right-click the Service Engines node and choose Install and Start. Select the iepserviceengine.jar file referenced in step 1.
10. Accept the default configuration and click Install.
    The IEP Service Engine is installed and connected to Java DB (iepseDB) successfully.

6.2.6 Union Operator on Oracle

Issue 1187

Problem: When the IEP database is configured to use Oracle, the Union operator may not work as expected.

In a test case, two Relation Aggregator operators were connected to the Union operator. The output was expected to contain seven events. However, the output contained only three events.

In another test case, two Time Based Window operators were connected to the Union operator. For every event that is received by one of the Time Based Window operators, the Union operator is calculated as expected. However, the Union operator is recalculated when the Time Based Window operator expires, which seems to be incorrect.

Workaround: None at this time.

6.2.7 Automatic Creation of JDBC Pools and Resources

The IEP Service Engine creates connection pools and JDBC resources during installation.

This automatic creation takes place only when the IEP Service Engine is installed in a GlassFish Domain Administration Server (DAS) instance. If the IEP Service Engine is installed in a GlassFish standalone instance, then the IEP Service Engine does not create the connection pools and JDBC resources. Instead, you must manually create the connection pools and JDBC resources and then install the IEP Service Engine.

6.2.8 Maximum Number of Event Processors in an IEP Module Project

An IEP Module project can have multiple event processors. The IEP Module project needs to be associated with a Composite Application project to be deployed.

When the Composite Application project is deployed and started, the event processors are also started and said to be running. When the Composite Application project is stopped, the event processors are also stopped.

For each event processor that is running in the IEP Service Engine, one database connection is created and kept open. Therefore, each running event processor has a dedicated database connection. When the event processors stops running, this connection is released. As mentioned earlier, this happens when the Composite Application project is stopped. The IEP Service Engine also uses database connections for other tasks.

It is recommended that the number of event processors that are running in IEP Service Engine is always less than the maximum pool size of the connection pools by a count of 10.

When the IEP Service Engine is installed and using the Derby database, IEP Service Engine creates two connection pools. The maximum pool size for these connection pools is 32. In this scenario, the maximum number of event processors that can be running is 22. If you need to have more event processors running, then increase the maximum pool size for both connection pools.

6.2.9 Deploying an IEP Process for Iterative Development

By default, IEP generates a WSDL document for each IEP process document, and regenerates the WSDL document every time the IEP process is edited. By default, bindings and services are generated in this WSDL, and these elements usually need to be edited to work properly when deployed. However, if these WSDL documents are edited, the edits are replaced by the default values every time the WSDL document is regenerated.

You can define bindings and services by using the CASA Editor. These bindings and services are not affected when the IEP WSDL documents are regenerated. However, you should not clone the IEP WSDL file to customize its generated bindings and services in the CASA Editor, because updates to the generated WSDL files will not be updated after the cloning. Over time, the cloned and edited WSDL deployed for the bindings will become inconsistent with the WSDL document deployed for the IEP Service Engine.

Consider using the following procedure for setting up your composite application and IEP project for iterative development:

1. Define the IEP Module project.
2. Turn off the generation of concrete configuration elements (bindings and services) in the IEP generated WSDL files by setting the always.generate.abstract.wsdl flag in the project.properties file to true.
3. Build the IEP Module project.
4. Add the IEP Module project to a new Composite Application project and build the project.
5. Define the desired binding components and connections by using the CASA Editor. To use the composite application test feature, define SOAP input and file output bindings as appropriate for your test environment.
6. Build and deploy the composite application.
7. Run tests.
8. Change the IEP Module project, adjust binding component and service configurations if necessary or desired in the CASA Editor, and rebuild/redeploy the composite application and run tests. Repeat.

6.3 Interoperability Issues with Sun Java Application Server

Issue 6763641
Problem: The HTTP binding component configuration is not refreshed by restarting the binding component itself; you need to restart GlassFish.

Issue 6761432
Problem: After fresh installation, it is not possible to undeploy amserver, and GlassFish <-> NetBeans is inoperative.

6.4 Interoperability Issues with Sun Java Access Manager

Issue 6703514
Problem: Bundled Access Manager is pre-configured for "localhost" not the FQDN.

Issue 6763628
Problem: The HTTP binding component cannot authenticate against Access Manager server running on HTTPS port.

6.5 Other Issues

Issue 6761256
Problem: The command "stop_emanager" throws an exception into the terminal when Enterprise Manager is already stopped.

Issue 6778554
Problem: Java CAPS projects are not currently supported on Sun Application Server 9.1.1.

Issue 6688807
Problem: The HTTP binding component is not listening on correct HTTPS port.

Issue 6743857
Problem: When using a MySQL database with the JDBC/ODBC Adapter in outbound mode, an exception is thrown if relaxautocommit is set to false in the JDBC External System properties and AutoCommit is set to true for the database.
Workaround: Set relaxautocommit to true.

Issue 6744536
Problem: In Java CAPS 6, there is no mechanism to switch on and off the Unique Particle Attribution (UPA) rule for the XML Schema, which prevents schema ambiguity. In Java CAPS 5.1.3, the default is to have UPA checking disabled; in Java CAPS 6, the default is to have UPA checking enabled.
Workaround: Create a file named "XML.properties", and enter the following line:
enforceUnqPartAttrib=false
Save the file to \.netbeans\caps\config\Preferences\com\stc\capsee\core\utilities. This disables UPA checking. To enable UPA checking, remove the file or set the parameter to true.