Sun Java Composite Application Platform Suite 6.2 Release Notes

Sun Java Composite Application Platform Suite (Java CAPS) combines technologies from Sun to form a modular and pluggable business integration platform that supports the complete spectrum of service integration requirements. Java CAPS includes repository-based core components and Adapters along with JBI Service Engines and Binding Components, giving you more options and greater flexibility in designing your composite applications. It uses NetBeans as the visual development environment, and the applications you create are deployed on the GlassFish Enterprise Server. This combination allows you to develop custom composite applications, Java EE applications, web applications, mobile applications, and web services using Java EE, JBI, and repository-based components.

The changes for this release are described in the following topics:

• Operating System, External System, and Platform Updates

• Upgrading

• Changes and Enhancements to Java CAPS Components

• Issues Addressed in Java CAPS 6.2

• Known Issues in Java CAPS 6.2

To access all the Java CAPS documentation in HTML and PDF format, go to the Sun Java Composite Application Platform Suite documentation page at docs.sun.com.

Operating System, External System, and Platform Updates

Java CAPS 6.2 supports newer versions of NetBeans and GlassFish Enterprise Server. In addition, release 6.2 provides support for new operating systems and external systems.

The following sections list the newly supported systems and platforms:

• Design-Time and Runtime Platform Changes

• Operating System Changes

• Browser and External System Changes

For a complete list of supported operating systems and external systems, see Java CAPS 6.2 Supported Operating Systems in Planning for Java CAPS Installation and Java CAPS 6.2 Components and Supported External Systems in Planning for Java CAPS Installation .

Design-Time and Runtime Platform Changes

This release of Java CAPS uses the following versions of NetBeans and GlassFish:

• NetBeans IDE 6.5.1

• GlassFish Enterprise Server 2.1 patch 2

The supported JDK versions are 1.5.0_14 or later and 1.6.0_03 or later. For JDK version information for specific platforms, see Java CAPS 6.2 Supported JDK Versions in Planning for Java CAPS Installation .

---

Note –

JDK 1.6.0_13 and 1.6.0_14 are not recommended for use with Java CAPS.

---

Operating System Changes

This release of Java CAPS provides new support for the following operating systems:

Design-Time

• Windows Server 2008

• Red Hat Enterprise Linux Server 5.3 (64 bit)

Runtime

• Windows Server 2008 (OS: 32 bit; JVM: 32 bit)

• OpenSolaris 2008.11 (OS: 32 bit; JVM: 32 bit)

• Red Hat Enterprise Linux Server 5.3 (OS: 32 bit; JVM: 32 bit)

• Red Hat Enterprise Linux Server 5.3 (OS: 64 bit; JVM: 32 bit)

• IBM AIX 5L 5.3 (OS: 64 bit; JVM: 32 bit)

---

Note –

Java CAPS 6.2 no longer supports AIX 5L 5.2. Red Hat Enterprise Linux is supported on both the basic Server and the Advanced Platform versions.

---

Browser and External System Changes

This release of Java CAPS adds support for the following browsers and external systems:

• Firefox 3.5.2 for accessing all Java CAPS browser components

• OpenSSO Web Services Security (WSS) Agent for the HTTP Adapter

• SWIFT 2009 message support and SWIFT 2009 certification

• SAP JCo 3 for the SAP BAPI Adapter

Upgrading

There are two paths to upgrade the Repository-based Java CAPS components from previous versions of release 6. In the first method, you install Java CAPS 6.2, export all projects from the older release 6 environment, and then import them into the new 6.2 environment. In the second method, you install Java CAPS 6.2, install a patch to update the older release 6 Repository, and then connect to the older Repository from the Java CAPS 6.2 environment. With the second option, you have a side-by-side installation, but you do not use the new Repository. Instead you continue to use the existing upgraded Repository.

The patch to upgrade the Repository is included on your installation media in patches/patches_ml.zip. The patch file is named 6836560-01-REP.zip. For full upgrade instructions, see Upgrading to Java CAPS 6.2.

Changes and Enhancements to Java CAPS Components

The changes listed in the following sections provide enhanced functionality to the products or address issues in such a way that affects general usability of the components.

• Java EE Component Changes and Enhancements

• JBI Component Changes and Enhancements

• Changes and Enhancements to Repository–Based Components

For a list of additional fixes to existing issues, see Issues Addressed in Java CAPS 6.2.

Java EE Component Changes and Enhancements

• HL7 JCA Adapter

  This new component is part of the Adapter Pack, and provides JCA support for HL7 messaging.

JBI Component Changes and Enhancements

Java CAPS includes the following new JBI features and components in this release. In addition, GlassFish clustering is supported for JBI components in Java CAPS 6.2; clustering support does not extend to Repository-based applications.

• Scheduler Binding Component

  This new component provides scheduling capabilities for initiating JBI services and allows you to schedule triggers to launch other JBI components.

• BPEL Service Engine

  • Support for validate activities.

  • The ability to add JavaScript code to a business process as an activity.

• File Binding Component

  • Support for UTF-16 characterset encoding.

  • Configurable options for on-demand reads that allow you remove a file resource once it has been read.

  • The ability to specify polling file names using Java regular expression-based file name patterns. This is supported through a new file:message attribute named fileNameIsRegex. Note that regex is not supported for output files.

  • The ability to specify a directory location for lock files rather than the location being relative to the fileDirectory property. This is supported through a new file:address attribute named persistenceBaseLoc.

• FTP Binding Component

  • The ability to specify a directory location for lock files using a new ftp:address attribute named baseLocation.

• HTTP Binding Component

  • Support for OpenSSO Web Services Security (WSS) Agent, which allows the HTTP BC to communicate with OpenSSO Enterprise 8 on a remote or local machine.

• LDAP Binding Component

  • Support for connection pooling.

• JMS Binding Component

  • Support for using multiple queues with WebSphere Message Queue. (CR 6812395)

Changes and Enhancements to Repository–Based Components

Java CAPS includes the following changes and enhancements to repository-based components in this release:

• General Changes and Enhancements

  • The ability to use any JAR file by creating a common path, netbeans.user/userdir/lib, for user library JAR files instead of manually importing changed files. You can now copy external JAR files to this directory and to domain/lib on the application server where the applications are deployed. (CR 6735569)

  • In the Server Type list on Enterprise Manager, “Sun Java System Application Server Domain” refers to both SJSAS 9.1 and GlassFish ES v2.1. (CR 6866695)

  • Support for prefixes for LDAP groups. To use prefixing for roles and groups, you need to add the following to the JAVA_OPTS section of startserver.bat (or .sh):

    -Dorg.apache.catalina.realm.JNDIRealm.ROLE_PREFIX=prefix

    where prefix is the full LDAP prefix to use; for example, com.sun.java.

    (CR 6760987)

• Alert Agent

  • The ability to set mail.smtp.auth to false when creating or configuring an alert channel on the Enterprise Manager so email can be sent to SMTP servers that do not have authentication. To facilitate this, a new check box named Use Authentication was added to the Channels window that appears when you click New or Edit of the Alert Agent's Channels tab on Enterprise Manager. (CR 6847411)

  • The ability to send alert notifications to a JMS topic in Sun Java System Message Queue (SJSMQ). To configure the Alert Agent channel, click New or Edit on the Alert Agent's Channel tab on Enterprise Manager. In the Type field of the Channels window, select JMS. The window changes to display JMS properties. (CR 6736357)

• Business Process Manager

  • Provides a graphical display of the appropriate abstract types, supports cast selection, and automatically generates the correct BPEL code to support these features.

  • The Worklist Manager now provides the ability to filter tasks, allowing you to perform queries and select data based on attributes. The filters support AND/OR operators. (CR 6637459)

• Sun Adapter for HTTP

  • The ability to obtain the length of the messages processed by the HTTP Adapter. Very long messages can increase processing times, and this feature allows you to avoid processing messages that are above a given size. Two new methods were added to accommodate this:

    • public void head () throws HTTPApplicationException

      This method invokes the HTTP head operation. It is in the HttpClientApplication class, and is similar to get except the server does not return the message body in the response. You can set HTTP request data using the HTTPRequest object returned from the getRequest method, and then obtain the result from the HTTPResult object returned from the getResult method. The syntax is:

    • public int getContentLenght() throws HTTPApplicationException

      This method is in the HTTPResult class. It extracts the content length provided by the HTTP Response Headers. The exception is thrown if the content-length header value is not set.

  (CR 6860182)

• Sun Adapter for SAP BAPI

  • Provides an easy way to configure an inbound SAP BAPI Adapter for load balancing. To support this, one new property was added to the inbound Adapter properties in the Connectivity Map, and two new properties were added to the inbound External System properties in the Environment. The new properties are listed below:

    • Use Load Balanced Server: Configure this property in the Connectivity Map. Set it to true if you are using a load-balanced SAP server; otherwise set it to false.

    • Message Server Hostname: Configure this property in the Environment. On the Properties Editor, expand Inbound SAP BAPI eWay and then select Server Connection Settings to access the property. Specify the host name of the R/3 Message Server.

    • Application Server Group: Configure this property in the Environment in the same location as above. Specify the name of the SAP application servers that are sharing the work load.

    (CR 6725723)

  • Exposes the following outbound connectivity properties in the OTD for dynamic configuration:

    • Application Server Hostname

    • System Number

    • Client Number

    • User

    • Password

    • Language

    • System ID

    • Gateway Hostname

    • Gateway Service

    • Message Server Hostname

    • Application Server Group

    • Router String

    To use the properties, do the following:

    1. Set the connection property values using the set* methods.

    2. Call connectWithNewParams to switch the SAP connection configuration object values with the dynamic values.

    3. Call connect to establish the connection to SAP.

  (CR 6733879)

• STCMS

  • Provides a new limit on the number of uncommitted messages a subscriber can have in protected concurrent FIFO mode (this value is configurable, but defaults to 1000). Previously, when using message selectors and protected concurrent FIFO, and a message is received out of order, the STCMS server might time out. The new limit prevents the timeout from occurring. (CR 6845501)

  • Supports the asterisk wildcard character (*) in destination names. (CR 6601025)

• XSD OTD Wizard

  • When you export an XSD node from the XSD OTD Editor a dialog box appears. The dialog box includes these two new options so you can control the namespace in the marshalled output:

    • Emit Default namespace

    • Emit Optional default attributes

  • OTD inheritance and object casting features can now be used without having to import the XSDArtifact.jar file. (CR 6734083)

• Sun Master Index

  • To improve performance when looking up the active EUID for a merged EUID, an index was added on the merged_euid column of the sbyn_merge table. To implement this change in existing databases, run the following SQL statement against your Master Index database:

    CREATE INDEX SBYN_MERGE2 ON SBYN_MERGE (MERGED_EUID ASC)

  • The ExecuteMatchLogics class includes a method rejectAssumedMatch that can be used to stop an assumed match from occurring. These rejected assumed matches should become potential duplicates, but they are not. To address this, two additional methods were added to the DecisionMakerResult class:

    • void rejectAssumedMatch() - Flag the assumed match to be rejected.

    • void acceptAssumedMatch() - Flag the assumed match to be accepted.

    In the MasterControllerCoreImpl.processMatch method, when the ExceuteMatchLogics.rejectAssumedMatch method returns true and the disallowAdd method returns false, the new rejectAssumedMatch method is called. See Open Dm MI Issue 135. (CR 6739926)

  • When Sun Master Index server and client projects are deployed on different servers, you need to modify the NetBeansHome/etc/netbeans.conf file by adding the following text to the netbeans_default_options property.

    -J-DJNDI_PROVIDER_URL=\"corbaname:iiop:MasterIndexHost:iiop-port\"

    where MasterIndexServer is the name of the server hosting the application server on which the master index server project is deployed, and iiop-port is the port number of orb-listener-1 in domain.xml.

    (CR 6755913)

Issues Addressed in Java CAPS 6.2

The following sections list the issues addressed by this Java CAPS release. The repository-based issues are listed in this document; links are provided for the JBI issues.

• JBI Issues Addressed

• Repository-Based Issues Addressed

• Master Data Management Issues Addressed

JBI Issues Addressed

Numerous updates were made to the JBI design-time and runtime components for this release. Below are links to the issues addressed for both design-time and runtime components.

• To view all runtime issues that were resolved in this release, see the OpenESB IssueTracker.

• To view all design-time issues that were resolved in this release , see the NetBeans IssueTracker.

  ---

  Note –

  The links above require you to perform a query for the issues. You can find links to the complete lists of JBI runtime and design-time issues that were resolved under Issues Resolved in the GlassFish ESB Release Notes.

  ---

The issues in the following table were also addressed for JBI components:

Issue ID	Description
6856003	Support for the following Data Integrator operators was not carried forward into Java CAPS 6:  Normalize Name Parse Address Parse Business Name Null If Number to Hex String to Hex
6856270	Runtime fails for a Data Integrator project if the ETL Collaboration contain flat-file tables.
6723702	Refreshing database table metadata from an ETL Collaboration does not refresh the primary keys.
6808993	When you launch the ETL Monitor, a blank page appears.
6784306	When you select Purge All on the Data Integrator (eTL) Monitor, there is no confirmation dialog box for you to verify or cancel the purge.
6808822	You cannot modify an application configuration for the FTP BC using the Admin Console.
6763628	When using the HTTP BC and Access Manager, an error occurs when you try to authenticate against the Access Manager running on the HTTPS port.
6804542	If you uninstall the LDAP BC from the GlassFish ES, you cannot reinstall it using the Admin Console.
6805041	The CASA Editor does not allow you to disable all consumer ports in Binding Components.

Repository-Based Issues Addressed

The following table lists and provides brief descriptions for the issues addressed for the repository-based components for this release.

Issue ID	Description
6826572	If the first patch installation for a given version uses the –basedir and –type arguments, subsequent patch installations fail if those two arguments are not used.
6873904	For the Alert Agent, if “localhost” is used instead of “FQDN” for the application server host, the email alerts incorrectly indicate that the server is down.
6673876	In the Alert Agent notification window, the text “undefined” appears where the alert type of component should appear.
6854720	The alerts sent by a Collaboration are not correctly sent to the Alert Agent.
6758036	The configagent URL (http://hostname:portnumber/configagent) throws an HTTP 403 error.
6741432, 6791279, 6817248, 6818090, 6721528, 6793310, 6688669, 6818531, 6795512, 6813828	Code completion does not work correctly in several cases:  For database OTDs For the Batch Adapter For IDocs for the SAP ALE Adapter When an Adapter throws a codegen exception while creating OTD JAR files When a JCD calls another JCD In projects created prior to R5.1.3U4 that use XSD OTD with repeating nodes For Excel OTDs and the COM/DCOM Adapter With certain users or certain subpackages
6870281	Duplicate modules are installed in separate directories during the Java CAPS installation.
6797961	The location of common library files is changed to be relative to the installation path for Java CAPS R6U1. If you import projects created in one Java CAPS environment into a different Java CAPS environment, they will have reference errors.
6854845	A null pointer exception occurs when you open a Java Collaboration in a project that was imported from a previous version.
6820987	The Java debugger does not stop on the specified breakpoints in Java Collaboration Definitions (JCDs). The debuggers throws an illegal state exception.
6738600	When using JDK 1.6.0 with the Japan locale, Java CAPS fails to create a Logical Host and produces an XML error.
6819884	A null pointer exception occurs during the build process.
6854726	After a JAR file is exported and checked-in, an error occurs when you check out the exported file.
67694146774099	When a Connectivity Map is copied, the UUID is reused for the Batch Adapter. The Adapter uses the UUID to store the state file.
6698893	An Adapter developed using the Sun Adapter Development Kit throws a null pointer exception when the Adapter properties are modified on the Connectivity Map.
6740575	An illegal state exception occurs when an imported JAR file is updated.
6866132	With both NetBeans and GlassFish ES running on Solaris, an IAS deployment exception occurs when deploying an application.
6737840	Compiling a JCD that uses a WSDL document throws a JaxRpcCodelet exception.
6749529	If you edit the HL7, File, or Batch external system properties and then check in the components, you cannot view the properties again.
6789726	Large Java Collaboration Definitions take a long time to open in the Java Collaboration Editor.
6811471	An incorrect class named used by the Java Collaboration Editor causes compilation to fail.
6697896	When a method in a JCD throws an exception and does not include the throw clause, the Java Collaboration Editor does not detect the missing clause. The build process fails.
6763815	A stack overflow error might occur when you try to import a JAR file to a JCD.
6850777	The validation window for the JCD code validation no longer includes links that take you to the location of the error in the JCD code.
6711362	JCD validation fails for some SAP BAPI RFC OTD methods when the JCD is relaunched.
6856662	When you expand OTD nodes to add a string literal to a field, the OTD tree collapses when you select String Literal and you have to expand the nodes again.
6784131	The New Project Wizard is displayed in English when using the Japan locale.
6776449	The CAPS repository menu is displayed in English when using the Japan locale.
6824032	The OTD Tester and JCD Editor cannot be opened when Shift_JIS, EUC_JP, MS932, UTF-8, or ASCII is set for antecoding, encoding, decoding, and postcoding. An unknown encoding name error occurs.
6864437	The XSD OTD Tester hangs intermittently.
6762637	When using the OTD Tester on custom HL7 OTDs with imported nodes, extra fields appear in the OTD nodes and messages are mapped incorrectly.
6670197	In the XSD and DTD OTD Testers, Big5 encoding does not appear in the encoding list.
6785593	When using Java CAPS on Japanese Windows 2003, you cannot select Topic in the Enterprise Manager.
6855515	Email alerts are not generated when the application server stops responding.
6865584	When you shut down Enterprise Manager, not all related processes are stopped.
672112467211266716090	Enterprise Manager is slow to display the list of servers.
6800355	Enterprise Manager continues to display the old server log from the original location after the location is changed.
6732516	Enterprise Manager needs to support publishing messages to a JMS Grid daemon that is configured for SSL.
6847410	Custom alerts sent by a JCD cannot be viewed on the Enterprise Manager.
6751770	On the Manager Servers window of the Enterprise Manager, the application server username and password appear in text instead of being encrypted.
6851084	When several domains are being monitored in Enterprise Manager, the domains' status may change to “UNKNOWN” and Enterprise Manager must be restarted in order to continue monitoring services.
6846203	The Enterprise Manager displays “NA” for the Last Published Date/Time for queues and topics when Enterprise Manager is in a different locale from the Logical Host.
6594815	The server log displays the following error as a result of miscommunication between Event Management and Application Deployer:  Access denied for user: lh1.mydomain.com:18000. Password is invalid.
6759925	Enterprise Manager no longer received alerts after the domain is restarted.
6859272	An email alert should be generated when the application server starts up.
6701138	When running Java CAPS on the Traditional Chinese locale, most components show English language messages on the GlassFish Admin Console.
6723372	When you delete a queue in a Sun Message Server using Enterprise Manager, the message server pauses and does not recover. All subsequent connection attempts fail.
6839760	You cannot use Enterprise Manager to republish journalled messages.
6807782	An email alert should be generated when the application server shuts down.
6632052	The new Enterprise Manager web application, Configurator, requires Japanese translation.
6585570	Command line codegen fails on Linux platforms.
6692113	Importing a Web Service Definition fails with a runtime validation exception.
6803308	When a WSDL document from a JCD is factored into a BPEL project (so the business process can invoke the JCD web service), the WSDL document that is generated by building and deploying the BPEL project is incorrect.
6758401	Running the asadmin extract-caps-application-configuration command does not generate the Connectivity Map properties file.
6794552	When you expose a web service hosted on GlassFish, the WSDL file is redirected to an incorrect file.
6818409	When a SOAP fault response contains non-ASCII characters, those characters are transmitted incorrectly, generating the following error: Invalid byte 2 of 3–byte UTF-8 sequence.
6767075	There is a JMQ login failure between GlassFish ES and the remote JMQ broker if the passwords in the Connector Connection Pools are encrypted.
6846935	JAX RPC does not handle the nillable attribute “xsi:nil” correctly, causing a namespace error after a call to an external web service.
6721690	The delay in milliseconds and the number of encounters for JMS JCA redelivery attempts is restricted to 5000. This limit should be removed.
6755951	JMS JCA activation fails with a connection leak, which in turn causes a memory leak in JMS Grid.
6730245	On the JMS JCA Wizard, the concurrency mode options are incorrect. They should be serial, cc, and sync.
6737996	It is not possible to use JMS JCA message-driven beans to look up managed connection pools using lookup://ResourceName in repository-based projects.
6704923	Expired JMS messages still appear in Enterprise Manager and the control utility for a short time.
6628677	You cannot change the default stcms.log file location because the log file name is overridden during initialization.
6799451	After an in-doubt transaction is rolled back for a queue receiver, the messages are included in the message count for the queue again but they are not redelivered.
6793140	After an in-doubt transaction is recovered, database references for the transactions are not cleaned up. This causes the size of the database files to increase.
6821855	After messages fill a database file and a new file is created, the synchronization might not be up to date. This means that if the server is restarted, messages are redelivered resulting in the following error: Duplicate Message On Restart.
6795780	When using an older stcjms.jar client to receive JMS messages from an STCMS queue, a persistence optimization fault occurs when the client commits on receiving. Also, when the domain hosting the STCMS is restarted, the consumed messages are not marked as having been consumed.
6636894	When the JMS service is shut down using stcmsctrlutil, the application server interrupts all blocking JMS client threads and the clients throw an interrupted exception.
6768755	Running stcmsctrlutil.exe against the STCMS server generates poller errors.
6777456	The circular list on which the backlog manager's log action list is based is not thread safe.
6805901	An STCMS client Ping Runner might incorrectly close sockets that it does not own when socket pooling is enabled.
6820661	The TxLogManager is unable to delete an empty database file, causing a break in sequence numbers on startup. The STCMS log shows a broken pipe error.
6808637	The raunifiedjms.jar file needs to be updated with the latest version of stcjms_453.jar.
6831154	Several JMS Ping Runner threads cause an out of memory error.
6673656	Running the command asadmin restore-stcms does not restore the STCMS instance on Solaris and Linux.
6800006	The STCMS IQ Manager stops processing messages and eventually crashes with a core dump.
6717194	STCMS might have excessive memory usage due to memory fragmentation under heavy loads, and the server will stop responding.
6821861	When journalling is enabled, the following message appears in stcms.log on startup: StartupMessageLists() : MessageQueue with id=xxx was deleted
6794825	Include Java Message Queue 4.2 or later with Java CAPS.
6798247	During heavy stress tests, the application server might experience ping timeouts and forcibly disconnect client connections.
6855097	If you undeploy and redeploy a business process while a transaction is in process, the application server becomes stuck in a continuous loop until the domain is restarted.
6801521	When the network connection on a JMS client is disabled before the STCMS server receives a ping message on the socket, the socket remains established and is not cleaned up.
6845567	When the number of messages in the JMS server reaches the ServerMaxMessage value, throttling begins and the insert rate is reduced.
6772445	Duplicate JMS message are produced because in-doubt transactions are not recovered properly.
6850646	The journaller might incorrectly overwrite the backup LSN for a queue or topic in the backup.log file, causing duplicate backups of the same messages.
6831273	Java Message Queue message redelivery does not work when the destination is a queue and the source is a topic.
6793357	Messages are not picked up from a JMS queue when the receive method is used with multiple client instances.
6746747	When the setClientId method tries to change the client ID, an exception (javax.jms.IllegalStateException) should occur.
6835050	JMS is unable to process large messages on Windows Server 2003 running in 64–byte mode.
6780050	JMS messages are lost on restart when multiple subscribers with different message selectors subscribe to the same topic.
6731073	The JMS server duplicates sequence numbers when message selectors subscribe to the same topic.
6728669	When message selector is used and some subscribers do not match the selector, the server might use invalid message location information on restart to skip these messages, causing the server to stop responding.
6697729	When using the ESB API Kit in a request/reply scenario, the IQ Manager leaks memory and requires frequent restarts.
6729721	When an ESB API Kit for C/C++ client connects using SSL, the QueueReceiver.receive and QueueReceiver.receiveNoWait methods throw exceptions.
6768533	For the ESB API Kit for COBOL, the JMSEMAP.COB and JMSOMAP.COB files are in EBCDIC but should be in ASCII.
6802532	An error occurs while running the ESB API Kit for COBOL sample, JMSRQRP.
6856220	An error occurs when you import an OTD template using the OTD Editor.
6776513	Data is parsed incorrectly in DTD OTDs created from a DTD that contains an element of the type “ANY”.
6704168	In NetBeans, the copy option from the drop-down menu does not work for HL7 OTDs.
6734987	The methods for an Oracle OTD table node do not appear in the auto-completion list in the Java Collaboration Editor.
6713648	If you add elements from external templates to a user-defined OTD, the OTD Editor fails to load the OTD.
6861987	The EDIFACT OTC Library cannot be accessed from NetBeans.
6786703	Unmarshalling for an EDIFACT message does not work when special mask characters appear in the message.
6816675	The marshal process for an EDIFECT OTD does not preserve the leading zero before a decimal point.
6687344	The Oracle OTD Wizard displays duplicate rows for a table if the table has multiple synonyms.
6666832	When you modify an Oracle or Sybase prepared statement in an OTD, the parameter names all reset to param1, param2, and so on. This breaks any code that uses the prepared statement.
6764153	When you modify an Oracle or Sybase prepared statement in an OTD, the updates are not saved.
6605314	An exception occurs when you select the java.sql.ARRAY type for the return parameter when using the OTD Wizard to create an OTD from a procedure.
6744950	In an ASC_X12 OTD, an unmarshall exception is thrown when trying to unmarshal a node defined as “ANY” with xsi:type=”ST”.
6773219	XSD OTD unmarshal process runs slowly.
6757893	Using relaunch.sh to relaunch an XSD OTD from the command line fails.
6802091	Relaunching an XSD OTD from the command line checks out the OTD automatically.
6784305	After the marshal process for an XSD OTD, additional characters appear in the parsed data.
6731064	If you import a project that includes a custom OTD and a business process from Java CAPS 5.1.1, a runtime exception occurs when you run the deployed project.
6755454	Multiple enhancements to the validation OTD and Collaborations for SWIFT.
6755496	Some private methods are used by not generated in validation Collaborations for MT fields in the SWIFT OTD libraries.
6755961	There are parsing errors for the following two similar patterns: “cv/ 160–288h ls” and “CV/ 160–288h )”.
6765321 6755499 6867642	Multiple fixes to MT fields in the SWIFT 2008 OTD Library.
6788175	In the SWIFT OTD Library, field 40E fails to parse for MT700, MT710, and MT720.
6771459	The command-line build process fails for a project that contains a MT541 OTD from the 2008 SWIFT OTD Library.
6862418	SVR rules in SWIFT OTDs need to be updated.
6758499	Multiple fixes to the SWIFT 2008 OTD Library.
6873632	The SWIFT OTD Library is not working in a BPEL use case scenario.
6674137	An error occurs when unmarshalling a SWIFT MT300 message using the Unmarshal From String button on the OTD Editor.
6773189	The SEF OTD Wizard does not generate the SEF OTD.
6828882	The COBOL Copybook Converter handles “OCCURS” incorrectly in a redefined item, which might result in wrong data being unmarshalled to a repeating node in the generated OTD.
6614227	Extra fields appear in the OTD Editor after dragging the same OTD from the external templates twice.
6817815	When an OTD contains recursive nodes, NetBeans stops responding when you try to map the fields. A severe heap-size error occurs.
6770478	A Java Collaboration Definition (JCD) cannot be created for the COM/DCOM Adapter.
6732365	Weblogic OTD methods are not available to be called from a JCD.
6855976	When using an XSD OTD with two elements, each having a child and sharing the same name, changing an attribute in one of the elements also changes the attribute in the other element.
6820389	A compiling error occurs when a remove method is called in an OTD generated from an XSD, even though the method appears in the generated OTD class and appears in the method completion dialog box.
6821073	The Command Line Branch Installer Tool needs to be added to version 6.2.
6838020	The SwiftOTDLibrary2008.sar file cannot be installed on a machine that has multiple IP addresses.
6766868	Patch installation fails when a custom administrator username and password are used. This release adds two new options to the patch installer: -repuser and -reppwd.
6861603	When you import a project that uses Java CAPS components that are not installed, the import process fails with no warning.
6702637	When there are multiple repository branches running on the Chinese locale, you cannot change to a different branch in NetBeans.
67431606763648	The repository project import tool is not working correctly, either from the command line or IDE.
6794338	Performance is slow on the NetBeans IDE when working with a remote Java CAPS repository.
6736086	You cannot use “data” as part of the repository name.
6794581	A “missing port information” exception occurs when a project contains a JCD exposed as a web service, which in turn invokes a second JCD exposed as a web service.
6853915	A null pointer exception occurs when trying to view WSDL provider details in the UDDI Registry.
6857884	The tool buttons on the WSDL Binding Editor are not visible.
6804467	SQL 2000 and SQL 2005 stored procedure result sets always display 0 (zero) and cannot be edited in the WSDL Wizard.
6760541	Invoking an SSL-enabled web service from a JCD client fails because it attempts to invoke the incorrect ENDPOINT_ADDRESS_PROPERTY.
6756093	When working with the Chinese or Japanese locale, you cannot create a correlation set for a business process.
6694020	When working with a Chinese locale, you cannot set the Use Correlations property in the Business Process Manager Editor.
6680585	On AIX domains, log messages change depending on the logging levels and the SOAP response does not match it's defining WSDL file in a Business Process Manager project.
6855693	In NetBeans, you cannot save changes to a BPM database script that was modified externally.
6681111	Building a project containing a business process fails with a codegen exception.
6770863	If a JCD in a business process throws an exception, the Enterprise Manager does not show the failed JCD in red.
6727500	Tasks are not listed on the Worklist Manager for any user with the Manager role.
6819654	After making changes to a Composite Page Designer page flow, you cannot save the changes.
6833158	A Composite Page Designer page-flow applications stop responding after a popup window is closed.
6750082	When you create non-JMS connector connection pools using asadmin commands with the default properties, the connection pools do not appear under the CAPS node on the GlassFish Admin Console.
6818090	When an Adapter throws a CodeGenException, code completion is disabled without any information about the cause of the exception.
6862156	A null pointer exception occurs when you import a 5.0.5 project and try to migrate a Batch eWay module.
6762993	The Batch SFTP Adapter stops responding when the server is unresponsive. The get method performs slowly.
6670570	The JCD Tester does not work for Collaborations that contain a Batch FTP OTD.
6762992	The Batch SFTP Adapter stops responding when the application server becomes unresponsive. The Adapter is also experiencing delays when calling the get method.
6762418	The get method in the Batch Local File OTD does not perform post-transfer commands if Synchronization is set to “no” in the Connectivity Map.
6759950	A Batch SFTP project stops responding after processing 1000 messages, and the domain main process stops responding as well.
6767112	When the specified file is not found by the Batch Adapter, the FileNotFoundException is not captured when the TargetFileNameIsPattern property is set to false.
6790775	When using a Batch SFTP External Application to connect to a Serv-U SFTP server, the connection fails and an SftpStatusException is thrown.
6757925	Batch Local File External Applications incorrectly concatenate the drive letter to the UNC path, so the Adapter is unable to write the file to the specified location.
6818519	The Batch SFTP External System throws an exception when connecting to MySecureShell SFTP server. Part of the solution to this is to set SFTP version 3 as the maximum SFTP protocol version to be used by the client.
6877193	The sample provided for the Adapter Development Kit does not work correctly.
6869815	Projects created with Adapter Development Kit components cannot be opened in Java CAPS 6.2.
6870286	The NBM files for Adapters created by the Adapter Development Kit fail to build.
6856357	When the Adapter Development Kit is used to create a new Adapter with custom icons (that is, not the default image files), the code generation fails.
6867425	When the Adapter Development Kit is used to create a new Adapter, the Adapter SAR file fails to build.
6814363	A null pointer exception occurs when DB2 Connect Type 4 drivers are used to access a result set returned from a stored procedure.
6802229	The Statement.setQueryTimeout method is not supported for mainframe DB2 drivers.
677254067725416771937	Connections to DB2, SQL Server, and Oracle intermittently experience very long delays.
6835472	A BPEL project with an eMail Adapter fails at runtime with the following error: NoClassDefFoundError:PersistentBeanMEssageWrapper
6750580	The eMail Adapter throws an exception when processing multipart/related messages and does not process subsequent messages.
6771879	For the HTTP Adapter, a call to input.getRequest.getText returns null even if the message contained text.
6807060	For the HTTP Adapter, a call to the post method throws a null pointer exception.
6770903	Under heavy loads, the HTTP Adapter produces the following error: Internal Server Error – 500.
6852307	When using an HTTP Adapter server project with basic authentication, deployment fails with an exception.
6830725	When a JCD connects to Informix, the JCD does not reconnect if the connection to Informix is broken.
6843990	When Sun Java System Application Server is the deployment target, the Connection Pool Settings properties for the LDAP Adapter are ignored.
6855988	The build process fails for a Composite Application that includes a JBI Bridge project.
6760943	The application server throws an “instance not found” exception when deploying a Composite Application that includes a JBI Bridge project.
6677837	The Admin Console stops responding when you create a Connector Connection Pool on Solaris 10, zh_TW locale (Traditional Chinese).
6750562	When using the JDBC/ODBC Adapter to invoke a DB2 procedure with several IN and OUT parameters, a SQL error occurs. This is due to the clearParameters method.
6781008	The command asadmin extract-caps-application-configuration does not work for the WebSphere MQ Adapter.
6841180	With JDK 1.6 versions, Environment Override does not work for the Oracle Adapter after running the asadmin extract and asadmin import commands on the project's EAR file.
6744428	When you import a 5.0.5 project that includes a SAP eWay, the import process stops responding and has to be ended manually.
6856107	The SAP Wizard fails and throws an exception due to an issue with sapjco3.jar backward compatibility.
6818117	When the SAP BAPI Global RAR is used in inbound mode with JCo 3, an abstract method error occurs.
6810843	The SAP BAPI Adapter does not auto-commit when used in non-transactional/Transactional (tRfc) mode.
6795976	When a SAP BAPI OTD is relaunched, the JCD using that OTD no longer works.
6724617	When a SAP project is imported from ICAN 5.0.5, the JCD fails validation and cannot be built.
6739514	On the SAP IDoc Wizard, the List IDocs button does not display all IDocs in the system.
6772238	The Sap IDoc Wizard allows you to select unsupported versions of SAP.
6867277	TCP/IP Adapter projects fail with a NotSerializableException.
6696822	The order of the database columns in a business process is different than the order in the SQL Server OTD.
6775765	The TCP/IP Adapter methods app.getSocket().getInputStream() and app.getSocket() dispose of the first 1024 bytes passed to it.
6795068	Port numbers for the TCP/IP Adapter are logged incorrectly (they include a comma).
6827513	An invalid descriptor error occurs when deploying some Composite Applications.
6738915	Frequent class cast exceptions are thrown on HL7 connections when multiple HL7 projects are running on the same server.
6827513	With the TCP/IP HL7 Adapter installed, projects that were upgraded from Release 6 fail to deploy with an “invalid archive descriptor” error.
6798876	Autoboxing is supported in Java CAPS, but the code does not compile for JCDs in repository-based projects.
6785947	Deploying a project that uses the Unified Resource Adapter (URA) is deployed throws a an exception, ClassNotFound Exception.
6813161	The ECRC file needs to be synchronized in all user's userid directory. This file should be stored in one location in the NetBeans home directory.
6718240	The Scheduler might start at an incorrect time when set to Weekly by Day.
6768527	An Access Control List (ACL) cannot be removed from a project.
6792243	When a user is removed through User Management in NetBeans, the user persists after the IDE is restarted because the ACL is not updated.
6809565	If you select the spreadsheet view on a Deployment Profile, all fields display “Invalid Data”.
6751202	An out of memory exception occurs during deployment and redeployment of a Batch Adapter project.
6734521	The logical host randomly fails with an index out of bounds exception.
6794331	If on the Admin Console you select Application Server, the Monitor tab, the Runtime tab, and then any View option other than JVM, an HTTP 404 error occurs.
6824377	A generated WSDL document does not create SLL and user token elements.
6858220	A web services project imported from version 5.0.5 fails to build in Release 6.2.
6828690	When using a token and SSL connection, the web service throws a socket exception.
6770349	The response from a web service operation cannot be parsed due to “nil” dateTime elements, and an unmarshal exception occurs.
6691795	An error occurs when sending a web service request that contains the text xsi:nil="true" on AIX.
6780177	An LDAP reference used in a web service client environment property is interpreted literally.
6740199	A web service client project throws a null pointer exception during runtime.
6799913	Web service response time is slow.
6809678	Escape characters contained within XML elements of SOAP requests are being escaped twice,
6703921	When multiple web services are invoked from JCDs and each WSDL document has the same target namespace, the projects cannot be built due to non-unique package and class names.
6807530	You cannot send nullable elements to a web service.
6737049	Unable to retrieve the SOAP fault message after invoking a web service from a JCD.
6810985	Invoking an external web service fails when the response contains a datetime element with an empty value.

Master Data Management Issues Addressed

The following tables list and provide brief descriptions for the issues addressed for master index components for this release.

Table 1 Sun Master Index (Repository) Issues

Issue ID	Description
6659613	When using keyless child objects, the SBR duplicates some of the child objects.
6731913	The getEUID method throws inappropriate null pointer exceptions. With this fix, getEUID behaves as follows:   Given a valid facility and LID, getEUID returns the EUID. Given a valid facility and invalid LID, getEUID returns null. Given a valid facility and an LID that does not match the required format, getEUID throws a validation exception. Given an invalid facility, getEUID throws a validation exception.
6699674	If an identifier that is too long is passed to getEUID, a null pointer exception is thrown instead of a validation exception.
6807758	You have to modify runed.bat in order to run a Master Index client project.
6718625	The value of the max-result-size property for EDM reports is being overridden by a default value of 100.
6855160	From NetBeans, you cannot save changes to the database or configuration files.
6799090	After importing a 5.1.3 eView project, the Sun Master Index External Application is not recognized in the client deployment profile.
6697222	The Enterprise Data Manager (EDM) does not display fields that contain double-quotes correctly.
6752758	Installing Sun Master Patient Index creates multiple eView.Person objects beneath the Master Patient Index projects.
6747936	The resolved date for potential duplicates is not stored in the Master Index database.
6778606	Serialization of MergeResult and TransactionObject objects does not work when the client is run from a different JVM.
6825113	The ObjectNode.equals(Object o) method does not take the class into account when comparing objects, resulting in false positives.
6875294	Master Index has trouble initializing when running with a JRE version 1.5.0_14.
6875297	An EJB exception is thrown when trying to create the first record in a master index from the EDM. This occurs with JRE 1.5.0_14.
6637511	The cursor is not positioned correctly when a new page on the EDM is displayed.

Table 2 Sun Master Index Issues

Issue ID	Description
Issue 160	Outbound messages from Master Index are missing the create date and update date values.
Issue 189	The MIDM Audit Log currently displays the create date as a date rather than a timestamp. There can be many transactions within a short period, so a timestamp would be more useful.
Issue 212	When an address field is added with an apostrophe in the text, the field cannot be edited.
Issue 219	The banner for the Information dialog box that appears when you tab away from the Edit Source Record window is partially hidden.
Issue 222	The generated outbound.xsd file is unusable in NetBeans. The following lines were added to address this: xmlns:tns="uri:PersonOutMsg" targetNamespace="uri:PersonOutMsg"
Issue 229	The transaction reconstruction for Master Index is inefficient. In addition, the timestamp is only to the second, which can lead to an exception when two transactions are processed in the same second.
Issue 237	The Transaction Detail does not display when the EPath parser finds invalid characters.
Issue 240	If the same code list is being used for more than one field on the MIDM, then the generated codelist.sql file will contain that code list more than once. This causes an error when running the script.
Issue 255	The update.xsd file that is used to validate update.xml does not allow fields to be specified in the system-fields element in the survivor calculator.
Issue 257	Fields that are defined as not editable can be modified through the Source Record View/Edit window.
Issue 272	The resolved date for potential duplicates is not stored in the database.
Issue 278	The outbound JMS message XML does not have a namespace.
Issue 287	The Clear buttons for child objects on the Source Record window do not work consistently.
Issue 293	A remote call to the Master Controller EJB fails on merge methods because the result object cannot be instantiated on the client.
Issue 295	Data enclosed in square brackets cause a validation error in the FieldDescriptor.validate method.
Issue 298	When a field contains data of the type Long, the text covers the next record. To prevent this, Long data fields only display 20 characters. If the field contains more characters, an ellipsis (...) appears at the end of the data. Mousing over the ellipsis displays the full text.
Issue 304	The generated outbound,xsd file has maxOccurs=”1” for the SBR element. Some transaction types have two SBR elements.
Issue 309	The Print button on the Transactions window does not appear correctly.
Issue 312	Transaction History on the MIDM does not work correctly with Firefox 2.0.x.
Issue 322	When the system and local ID are displayed on the Transaction History and Audit pages, the local ID is displayed first. Since the formatting of the local ID is dependent on the selected system, the system field should appear first.
Issue 324	The MIDM does not allow variable local ID lengths.
Issue 325	The topic connection is not closed when the EJB call that triggers an outbound message completes, resulting in too many open connections. A processing exception is thrown.
Issue 332	Non-updateable fields do not appear on the Potential Duplicate report.
Issue 334	When Master Index generates outbound messages, it includes deleted child objects in the message even though they are flagged as being removed.
Issue 335	When you clean and build an MDM project, the properties are rest for the corresponding EJB project, which removes any custom changes including the additional of JAR files. The EJB project will no longer compile.
Issue 341	The error message is not displayed in certain cases of SEQException, so the cause of the exception is not apparent.
Issue 344	The SBYN_MERGE database table should have an index on the merged_euid column.
6682971	Range search fields should be arranged more clearly on the MIDM search windows.
6708211	A record's history displays incorrectly after an unmerge transaction.
6710895	When a record is updated while you are viewing its transaction history on the MIDM, you are not alerted that you are no longer viewing the most current information.
6858060	When you enter a field name with more than 20 characters, a message appears warning of an Oracle limitation. This limitation also exists for MySQL databases, but can be removed since MySQL does not have the same limit.
6700054	The field labels and field values look too similar on the MIDM Records Detail page.
6703149	When you enter an invalid local ID on the Duplicate Records page on the MIDM, an error message appears. When the error message is closed, you cannot click on the local ID field to fix it and the System field is cleared.
6829621	A null pointer exception occurs as a result of a multi-threading issue in the Sun Match Engine and on TransactionObjectDB.

Known Issues in Java CAPS 6.2

The following sections list and describe the known issues in this release. Work-arounds are also documented where applicable. In the following sections, links are provided to issues that originated in the OpenESB project, and “CR” refers to the change request number for an issue.

Known Issues for Adapters

The following are known issues for Sun Adapters:

• CR 6676202

  If you import a 5.1.0 project that contains an Oracle Adapter (eWay) along with its associated Environment, the Environment Properties window for the External System does not list the Outbound non-Transaction properties. This occurs because release 5.1.0 did not support non-transactional messaging.

  To work around this issue, create and configure a new Oracle External System in the imported Environment.

• CR 6702711

  The MSMQ Adapter implemented the connection pooling feature, which made changes to the template and added properties to the external system.

  If you import and build MSMQ projects from Java CAPS 5.1.3 and earlier, you need to open the environment properties and Connectivity Map properties in order to build the project.

• CR 6674397

  The database table locks if the application server goes down during the middle of an XA Transaction.

  To work around this issue, restart the database to release the lock.

• CR 6697220

  There is no LDAP support for inbound configuration of HTTP, Siebel, and PeopleSoft Adapters.

• CR 6779560

  The HL7 V3 functionality is disabled from use in HL7 JCA-based EJBs.

• CR 6854684

  The Oracle Adapter must be installed before installing the Oracle Applications Adapter to ensure the correct JAR files are installed. Note that the Oracle Adapter is installed in the standard Java CAPS installation.

• The Adapter Development Kit does not support creating Global RAR (JCA Adapters). (CR 6876283)

• eWays created using the 5.1.x version of the eWay Development Kit need to be recreated in Java CAPS 6.x using the Adapter Development Kit.

Known Issues for the BPEL Service Engine

---

Note –

For BPEL SE stop and restart issues, see Known JBI Management Issues.

---

The following are known issues for the BPEL Service Engine:

• NetBeans Issue 148288

  If a BPEL project is deleted using the Delete Source option and a new project is then created that reuses the same name, the newly created project's Properties window cannot be opened.

  To work around this issue, stop and then restart the NetBeans IDE.

• Issue 555

  The BPEL Service Engine only creates connection pools and data sources for the Derby database. This functionality is available to assist developers and is not available for other databases or in a cluster. The BPEL Service Engine does create the persistence tables automatically for all supported databases, but only in standalone mode; this feature is not available in cluster mode. If you create connection pools, data sources, and tables before you install the BPEL Service Engine, it is possible to install the component with persistence enabled. Otherwise, installing to the cluster will fail.

  To work around the issue of tables not being automatically created, you can create the tables in standalone mode and then add the BPEL SE to the cluster.

• Issue 1802

  When an optional node is missing in the input message, an invalidVariable exception is thrown. This should not occur since the node is not required. This is due to an issue with BPEL case and message variables of the schema type.

Known Issues for Composite Page Designer

The following is a known issue for the Composite Page Designer:

• CR 6624231

  A user-generated portlet for a project found in the tutorial operates when deployed on portal server in the application server web container (using a Solaris 10 x86 zone), but it does not render properly in Firefox.

  To work around this issue, change the portlet to thin rather than thick. This will not fix the problem entirely but will make it easier to view.

Known Issues for the Data Integrator Service Engine

The following are known issues for the Sun Data Integrator Service Engine:

• There is a compatibility issue with existing eTL/Data Integrator projects (Modern) from previous Java CAPS releases that are migrated into Java CAPS 6.2. To resolve this issue, you need to update the build-impl.xml file for each project. The file is located in ProjectHome/nbproject. Add the following two entries for each project:

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

• CR 6681744

  Importing eTL 5.1.x projects into Java CAPS 6 using a command line results in an exception.

  When importing 5.1.x projects, set the NB_HOME, DB_DRIVERS_HOME, ETL_MIGRATION_CLASSPATH and DB_DRIVER_PATH variables as shown below. Exceptions still persist if the eTL collaborations contain database tables. There are no issues when flat files are used. To work around the database table issue, restart the repository, and then rerun the import command. Alternatively, import the project using the NetBeans GUI.

  set NB_HOME=C:/JavaCAPS6/netbeans set DB_DRIVERS_HOME=C:/JavaCAPS6/.netbeans/caps/modules/ext set ETL_MIGRATION_CLASSPATH= %NB_HOME%/ide9/modules/org-netbeans-modules-project-ant.jar; %NB_HOME%/ide9/modules/org-netbeans-modules-projectuiapi.jar; %NB_HOME%/ide9/modules/org-netbeans-modules-projectapi.jar; %NB_HOME%/platform8\lib\org-openide-util.jar; %NB_HOME%/soa2/modules/org-netbeans-modules-etl-editor.jar; %NB_HOME%/soa2/modules/org-netbeans-modules-etl-project.jar; %NB_HOME%/platform8\modules\org-openide-dialogs.jar; %NB_HOME%/platform8\core\org-openide-filesystems.jar; %NB_HOME%/ide9/modules/org-netbeans-modules-db.jar; %NB_HOME%/platform8\modules\org-openide-nodes.jar; %NB_HOME%/platform8\modules\org-openide-text.jar; %NB_HOME%/xml2\modules\org-netbeans-modules-xml-validation.jar; %NB_HOME%/ide9\modules\org-netbeans-api-xml.jar; %NB_HOME%/soa2\modules\org-netbeans-modules-soa-ui.jar; %NB_HOME%/\platform8\modules\org-openide-loaders.jar; %NB_HOME%/platform8\modules\org-openide-windows.jar; %NB_HOME%/platform8\modules\org-openide-awt.jar; %NB_HOME%/xml2\modules\org-netbeans-modules-xml-xam-ui.jar; %NB_HOME%/platform8\modules\org-openide-options.jar; set DB_DRIVER_PATH=%DB_DRIVERS_HOME%/db2adapter/db2builder.jar; %DB_DRIVERS_HOME%/stc/ewaycommon/com.stc.ewayrepositoryapi.jar; %DB_DRIVERS_HOME%/../com-stc-bpms-common.jar; %DB_DRIVERS_HOME%/../com-stc-log4j.jar; %DB_DRIVERS_HOME%/otd/com.stc.otd.fwbuildapi.jar; %DB_DRIVERS_HOME%/stc/ewaycommon/com.stc.ewayutils.jar; %DB_DRIVERS_HOME%\oracleadapter\oraclebuilder.jar; %DB_DRIVERS_HOME%/sqlserveradapter/sqlserverbuilder.jar; %DB_DRIVERS_HOME%/sybaseadapter/sybasebuilder.jar;

• CR 6694617

  Importing eTL 5.1.x projects with fixed width tables fails at runtime. Runtime test resulted in a java.sgl.SQLException.

  To work around this issue, check whether the execution of the imported eTL project fails due to the exception java.sql.SQLException: LOADTYPE property required in organization clause. If so, open the ETL Collaboration file and verify that the ORGPROP_LOADTYPE attribute is listed for each flat file table that is used. If the ORGPROP_LOADTYPE attribute is missing, then manually add it, save the Collaboration, and then rerun the project. For example:

  <attr name="ORGPROP_LOADTYPE" type="java.lang.String" value="FIXEDWIDTH" /> <attr name="ORGPROP_LOADTYPE" type="java.lang.String" value="DELIMITED" />

• CR 6705843

  For a 5.1.x eTL project that was upgraded using the eTL Migration Tool and modified to use the JBI Bridge, command line codegen fails to create the EAR file.

  To work around this issue, use the NetBeans GUI to build and deploy migrated Data Integrator projects.

• CR 6707522

  Changing the sun-etl-engine setting in the Loggers properties does not change log and message levels in the server log file.

• CR 6669876

  If you import a 5.1.3 eTL project into a Java CAPS 6.x environment, modify the ETL Collaboration, and then re-import the project, the ETL Collaboration does not refresh. In other words, you still see the changes you made earlier, though they should have been overwritten by the import process.

  To work around this, do one of the following:

  • Restart NetBeans. When you open the ETL Collaboration, it will be the original, imported version.

  • Before you re-import the project, delete the ETL module from the Project window and then manually delete the directory JavaCAPSHome/.netbeans/caps/eTL/Imported Projects/ProjectName.

Known Issues for the Data Mashup Service Engine

The following are known issues for the Data Mashup Service Engine:

• Open-DM-DS Issue 161

  When querying an Axion database using the current_timestamp function in the WHERE clause, a parsing exception occurs.

  To work around this issue, use the now function instead.

  For example:

  WHERE DEPARTMENT.DEPTID=EMPLOYEES.DEPTID and EMPLOYEES.DEPTDATE <= NOW()

• Open-DM-DS Issue 165

  In the Collaboration Properties window for a Data Mashup project, the Response Type field is no longer a drop-down field. It accepts the following values:

  • WebRowset

  • RelationalMap

  • JSON

Known Issues for the Database Binding Component

The following are known issues for the Database Binding Component:

• Issue 431

  The ojdbc5.jar driver for Oracle does not support prepared statements. The following error message is given:

  java.sql.SQLException: Unsupported feature

  No resultset is populated, and java.lang.string is selected for every parameter, regardless of the datatype.

  To work around this issue, use DataDirect drivers instead of ojdbc5.jar.

• Issue 453

  No error message displayed if too many parameters are supplied in an insert prepared statement. For example, insert into table values(?,?,?,?,?) into a 3-column table causes a runtime exception, and no parameters are added.

• Issue 499

  When a prepared statement is used to update or delete parameters, the result displays the default java.lang.String datatype irrespective of the actual datatype. This is because the DataDirect connect of JDBC driver for Oracle does not support returning parameter metadata information for an update statement with mixed literal and parameterized arguments.

  To work around this issue, manually change the datatype of the parameter in the generated XSD.

• Issue 517

  Built-in functions require an alias to avoid misinterpreting names of elements with special characters. For example, the prepared statement select avg(float) from table where number in(...); yields the following error:

  ERROR: s4s-att-invalid-value: Invalid attribute value for 'name' in element 'element'. Recorded reason: cvc-datatype-valid.1.2.1: 'AVG(NUMBER)' is not a valid value for 'NCName'.

  To work around this issue, use an alias for the function. For example: select avg(float) avg from table where number in(...);

• Issue 533

  DataDirect driver does not return correct metadata, resulting in an incorrect resultset for output parameters of stored procedures. This is a driver error, and work ticket W809210001 has been filed with DataDirect about the metadata call getProcedureColumns() returning incorrect parameters.

• Issue 866

  A datetime value cannot be inserted for SQL Server 2005 using the sqljdbc.jar driver. This was caused by a syntax error involving spaces and parentheses.

  See the resolution at http://forums.microsoft.com/technet/ShowPost.aspx?siteid=17&amp;postid=4061403.

• Issue 1087

  Stored procedures do not support the BLOB (binary large object) datatype. Although the procedure runs without generating an error, a select statement fails to yield any BLOB data.

• Issue 1747

  When using a Derby database for polling in a clustered environment with the Number of Records option set to a low value, the following exception is thrown and the connection pool becomes unusable:

  java.sql.SQLException: Connection closed.

  To work around this issue, configure the number of records per poll to a high number; for example, 100 per 1000 records. A second workaround is to create all cluster-related tables in the same database

• Issue 1803

  When the Database BC is implemented in a clustered environment across multiple servers, failover does not always work because the message status in the polling table prevents the in-process messages from being picked up by another instance (or by the same instance when it resumes).

  To work around this issue, manually delete records in the polling table that are have a status of “In progress” or “SENT”. This allows running instances to pick up the messages and reprocess them.

• Issue 2269 (and CR 6882656)

  When the Database BC is used with a business process that has persistence enabled, the stored procedure fails and an exception is thrown.

• When you create a Database BC WSDL document using the wizard, an XSD file named table_name.xsd is also created. If there is already an existing XSD file by that name, it is overwritten.

  To work around this issue, make sure the table name is different from any existing XSD file names.

Known Issues for the Enterprise Service Bus

The following are known issues for the Enterprise Service Bus:

• CR 6670699

  When using Firefox, scrollbars do not appear when a Connectivity Map or Business Process is larger than the viewable canvas. You cannot view the portions of the Connectivity Map or Business Process that are not in the viewable area.

  To work around this issue, resize the Connectivity Map or Business Process to fit within the original frame.

• CR 6699303

  NetBeans throws a SocketTimeOutException when you create a new CAPS repository branch.

  To work around this, increase the repository connection timeout to 60000.

• CR 6700931

  Username token with password digest is not supported. You cannot open the properties to test the password digest for the username token. This support is not fully integrated across NetBeans, WSIT, and GlassFish security.

• CR 6706429

  If you enable persistence for alert management without restarting the domain, alerts that are generated into the persistence database do not reach the Enterprise Manager.

  To work around this issue, restart the domain after enabling alert management persistence.

• CR 6706921

  The env.sh command does not set the PATH on UNIX. It should set something similar to PATH=$ENGINE_HOME/BIN:$JAVA_HOME/BIN:$PATH to make samples and other executables available.

  To work around this issue, set the path manually.

• CR 6708514

  Java CAPS projects with imported WSDL files fail when the JCD loads (on Red Hat Enterprise Linux 5).

• CR 6695408

  The OTD Tester does not launch for transactions for OTD libraries. The OTD Tester does not handle dependent JAR files correctly, especially JAR files for Forest API-based OTDs and B2B OTDs.

  To work around this issue, modify the netbeans.conf as follows.

  1. Navigate to JavaCAPSHome/netbeans/etc and open netbeans.conf in a text editor.

  2. Locate the line that starts with netbeans_default_options=, and add the following option to the end of the line.

     --cp:p JavaCAPSHome/.netbeans/caps/modules/com-stc-antlrimpl.jar

     where JavaCAPSHome is the location of the Java CAPS home directory.

     ---

     Tip –

     Make sure this option is inside the closing double quote that is the last character of the line.

     ---

     This instructs NetBeans to prepend com-stc-antlrimpl.jar to the IDE's classpath so that the antlr classes supplied by this JAR file, which the B2B OTD libraries depend on, will take precedence over NetBean's default antlr.

  3. Add the following option to the netbeans_default_options= property:

     -J-Dantlrmaxaltblklines=3000

Known Issues for the File Binding Component

The following are known issues for the File Binding Component:

• The File BC supports encodings in UTF-8 format only; if the encoding is in non-UTF-8 format, the File BC fails to read the input data. However, data of any encoding style (either UTF or non-UTF-8) and binary data can both be forwarded as attachments.

  You can work around the UTF-8 limitation by doing the following:

  • To read non-UTF-8 data, employ a custom encoder upstream of the File BC and convert it to UTF-8 format, which in turn can be provided as input to File BC.

  • To write non-UTF-8 data, route the output from the File BC to a custom encoder and convert it from UTF-8 to the preferred encoding format. For more information, refer to Designing Custom Encoders.

• Issue 1206

  On the Windows operating system, when the File BC transforms XML text to bytes, an additional carriage return is added for each newline character. For example, \r\n is converted to \r\r\n.

• Issue 2025

  When using the File BC in on-demand mode and setting a normalized message property value for an assign activity, if you set the property value in the ReadOut node, it is not used by the application. You need to set the values in the ReadIn node.

Known Issues for the FTP Binding Component

The following are known issues for the FTP Binding Component:

• Issue 796

  When the messageCorrelate attribute is set to true in the ftp:transfer element of the FTP WSDL, the FTP BC expects the input file to match a fixed pattern (req.UUID) so the UUID can be used as the ID to correlate a request with a response.

• Issue 828

  A project with invalid FTP BC property values can be built using command-line builds (ant tasks) but fails validation in NetBeans and is not built. This happens because certain validations that are performed automatically by NetBeans when building a project are not performed by command-line builds (ant tasks). For example, a project with a non-positive or non-integer FTP BC poll value (pollIntervalMillis) fails validation in NetBeans but can be built using ant commands.

• Issue 832

  On all operating systems, the delimiter for path components specified for preReceiveLocation (in sendTo, receiveFrom, and so forth) is the forward slash (/). Using the backslash instead results in errors such as the following:

  FTPBC-E004026.

  Exception when preparing ftp connection parameters in inbound processor. java.lang.Exception:

  FTPBC-E004019.

  No directory name found in PreReceiveLocation [...] when PreReceiveCommand is RENAME or COPY.

• Issue 1926

  When the append attribute is set to true in the file:transfer element of the WSDL file, the FTP BC overwrites the existing output file instead of appending the information to the end of the file.

Known Issues for the IEP Service Engine

The following are known issues for the IEP Service Engine:

• Issue 449

  When using Oracle as the IEP database platform, 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.

• OJC Issue 608

  When a cluster instance is stopped using the asadmin stop-instance command, IEP processes that are currently running do not fail over to a live instance. This is due to the order in which methods are called during the stop process.

  To work around this issue, stop and restart the Service Assembly.

• Issue 1083

  The IEP SE might not work as expected in high availability and failover mode. When there are two instances of the IEP SE and a project is deployed on instance 1 and then on instance 2, instance 1 generates the output in normal conditions. If you undeploy the project from instance 2 and then from instance 1, and then redeploy the project on instance 2 and then on instance 1, instance 2 should generate the output. Instead, both instance 1 and instance 2 generate the output.

  To work around this issue, restart the IEP SE on instance 2.

• Issue 1184

  This issue applies only to upgrading from previous versions of Java CAPS. 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.

  To work around this issue, uninstall and then reinstall the IEP Service Engine by performing the following steps:

  1. In the Services window of the NetBeans IDE, expand Servers > GlassFish V2 > JBI > Service Engines .

  2. Right-click sun-iep-engine and select Uninstall. The IEP Service Engine is uninstalled.

  3. Launch the GlassFish Admin Console.

  4. In the Navigation panel on the left, expand Resources and expand JDBC, and select JDBC Resources.

  5. Delete the resources named jdbc/iepseDerbyXA and jdbc/iepseDerbyNonXA.

  6. If the iepseDB directory exists in the install-dir/.netbeans-derby directory, log out of the NetBeans IDE and remove the iepseDB directory.

  7. Restart the NetBeans IDE and then restart the GlassFish application server.

  8. In the NetBeans Services window, right-click Service Engines and select Install and Start.

  9. In the window that appears, browse to install-dir/appserver/domains/domain1/jbi/autoinstall and select the iepserviceengine.jar file.

  10. Accept the default configuration and click Install. The IEP Service Engine is installed and connected to Java DB (iepseDB) successfully.

• Issue 1187

  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.

• Issue 1311

  The relation aggregator does not work as expected for various operations, and the output is an incorrect number of events. For example, invalid aggregations are not removed for Oracle. In certain cases with Derby, aggregations are updated even if the aggregation has not changed, leading to extra events.

• Issue 1519

  When running the IEP SE on Solaris SPARC using an Oracle database, connection errors might occur.

  To work around this issue, restart the GlassFish server.

• Issue 1882

  When IEP SE is running on Solaris SPARC and using a Derby database, not all events are processed. This is due to an issue with a JDK method used by the IEP SE to get the current timestamp.

  To verify whether you are having this issue, send events to an IEP application and verify the timestamp.

• Issue 1986

  When the IEP SE is configured for Oracle and a RelationStream operator is used to retrieve events from an input relation, duplicate events may be produced.

  To work around this issue, use an InsertStream operator instead of RelationStream. Another option is to use a Distinct operator after the RelationStream operator to filter duplicates. Note that neither of these options may be able to completely replace RelationStream

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

  To work around this issue, manually create the connection pools and JDBC resources and then install the IEP Service Engine.

• An IEP Module project can have multiple event processors, and one database connection is created and kept open for each event processor. Therefore, each event processor has a dedicated database connection. When the event processors stop running (for example, when the Composite Application is stopped), this connection is released. Because the IEP SE uses database connections for other tasks, the maximum pool size of the connection pools should be larger than the number of event processors that are running in the IEP SE by a count of 10.

• By default, the IEP SE 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.

  Bindings and services created in the CASA Editor 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 are not updated after cloning. Over time, the cloned and edited WSDL deployed for the bindings becomes 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 binding components and connections 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 in the CASA Editor, and rebuild and redeploy the composite application. Run tests and repeat.

Known Issues for Java Application Projects for JAXB

The following is a known issue for Java Application projects with JAXB:

• NetBeans Issue 163169

  In Java Application projects for JAXB, JAXB class files are deleted at runtime and the application fails to run.

  To work around this issue, deselect Compile on Save in the Project Properties window. Compile on Save is located in the Build > Compiling properties node.

Known Issues for the JBI Bridge

The following are known issues for the projects containing a JBI Bridge:

• CR 6683017

  When a JCD calls the JBI Bridge, the Composite Application fail to deploy even though both the repository-based project and the JBI Bridge project build successfully. The deployment produces the following error message: ERROR: Starting service assembly failed.

  To work around this issue, manually start the service assembly using the JBI Mapper.

• CR 6646537

  The JBI Bridge does not work with abstract WSDL. The build process for the JBI Bridge only works if the WSDL file used by the business process contains the binding and service sections.

  To work around this issue, edit the WSDL file using the JBI WSDL Editor. Add the appropriate binding information and then reimport the WSDL file back to the repository-based project.

• CR 6654477

  Single-part input/output literals are not supported between BPEL 1.0 and BPEL 2.0 engines across the JBI Bridge.

Known Issues for the LDAP Binding Component

The following are known issues for the LDAP Binding Component:

• Issue 804

  When the authentication type is not agreed upon between the LDAP server and client, an AuthenticationNotSupportedExceptionoccurs. For example, the error occurs when a client specifies strong SSL authentication with a DSEE 6 server that handles none or simple authentication, but not strong authentication.

• Issue 924

  No design-time validation is performed when an invalid root DN is supplied (such as dc=sun instead of dc=sun,dc=com), and the user is (incorrectly) allowed to create LDAP WSDL files with the incorrect values. Such a project correctly fails at runtime with a No such object error message.

Known Issues for Sun Master Index

The following is a known issue for Sun Master Index projects:

• CR 6718625

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

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

• CR 6867017

  When a Master Index application is redeployed from NetBeans, updates to the deployment destination (for example, host name and port number) are not updated.

  To work around this issue, deploy from the GlassFish Admin Console or the command line. To deploy from NetBeans, open NetBeansProjects/ProjectName/nbproject/private/private.properties in a text editor and modify the j2ee.server.instance property. For example:

  j2ee.server.instance=[C:\\CAPS62\\appserver]deployer:Sun:AppServer::localhost:21048

• CR 6757529

  In the Sun Match Engine, the date comparison functions (dY, dM, dD, and so on) do not work correctly when used as a direct string comparison rather than a relative distance calculation. That is, the y option does not return the correct value.

  To work around this, use date comparison functions with a direct string comparison (the n option).

Known Issues for the XSLT Service Engine

The following are known issues for the XSLT Service Engine:

• Issue 1631

  A SEVERE error appears in the server log when running an XSLT project with an HTTP/SOAP binding. The error is:

  Unable to create envelope from given source because the root element is not named Envelope

  This is an erroneous log message and does not interfere with the running of the XSLT project.

  To prevent the message from being logged, set the SAAJ Logger for the XSLT SE to OFF.

• NetBeans Issue 161321

  If you change text in the XML editor, clicking Validate does not save the changes before compiling and validating the code. You need to click Save All before validating the XML.

• Issue 1760 and NetBeans Issue 162869

  The XSLT SE does not support catalog.xml, which is required for the correct Referenced Resources support. For example, when referencing a WSDL document from another project using Project Reference, the XSLT project fails to deploy.

Known Issues for Composite Applications

The following are know issues for Composite Application (CA) projects:

• NetBeans Issue 148024

  A test case cannot be created using the SOAP12 binding, even though GlassFish otherwise supports SOAP 1.2.

  To work around this issue, use a SOAP binding instead of SOAP12.

• NetBeans Issue 152455 (now 138971)

  When the design canvas of the CASA Editor is at certain sizes, the display of its scrollbars oscillates and CPU usage goes to 100%.

  To work around this issue, increase the size of the window or of the CASA Editor design canvas so scrollbars do not display.

• NetBeans Issue 152449

  When a new project type is freshly installed, the Composite Application project is initially unable to determine the service engine type and is thus unable to deploy the service unit. The following error message appears:

  Cannot add JBI module project_type. Its target component type engine_name is unknown.

  To work around this issue, stop and then restart the NetBeans IDE.

• NetBeans Issue 153537

  You cannot rebuild a Composite Application project after a Service Unit (SU) has been deleted from it.

  To work around this issue, manually edit the build-impl.xml file and delete all sections that operate on the deleted SU.

Known JBI Management Issues

The following are known issues in managing JBI components:

• Issue 884, Issue 885, and OJC Issue 559

  When a component is shut down while there are configuration errors, it cannot be restarted and its configuration settings cannot be edited within the NetBeans IDE or the web console.

  When this occurs, the state of the component changes to “Stopped”, and you can reconfigure the properties correctly. After you correct the property values, shutdown and then restart the component in order for the changes to take effect.

  For the BPEL Service Engine, when there is an error in the JDBC resource name, the engine will create the resource with the given name and assume that the default connection pools are used. If the Derby database is not started, the default connection pools are not created.

• NetBeans Issue 163169

  Selecting the Compile on Save option in a Java Application Project Properties window causes a JAXB class file to be deleted at runtime. The project fails at runtime with the following exception:

  Exception in thread "main" java.lang.NoClassDefFoundError

  To work around this issue, deselect the Compile on Save option. This option is located on the Java Application Properties window under Build > Compiling.

Known Localization Issues

The following are known localization issues:

• Issue 1138

  When you perform the following steps in a non-English locale, you cannot expand the GlassFish server tree to select the value.

  1. Launch the New File Wizard to create a new JCA message-driven bean.

  2. Complete steps 1 through 3 on the wizard.

  3. For the Connection URL in step 4, click the ellipses button and start the GlassFish server to obtain the JNDI value.

  To work around this issue, use the GlassFish Admin Console to retrieve the JNDI value to enter for the Connection URL. The value is located under Resources > Connectors > Admin Object Resources.

• CR 6883496

  When a Composite Application is created on a Chinese locale, the build process fails for the Composite Application.

Known Installation and Startup Issues

The following are known installation issues:

• CR 6706840

  When installing Java CAPS on Red Hat Enterprise Linux 5, the installer stops responding when the installation is complete.

  To work around this, select the 'X' button in the top right corner of the window. A new window appears with a message that says “Installation not complete”. Select OK on this window.

• CR 6684782

  Uploading SAR files fails on AIX 5.3 with JDK 6.

  To work around this issue, only use JDK 5 with AIX 5.3 and not JDK 6.

• CR 6710310

  Running the importProject.sh command fails on AIX 5.3.

  To work around this issue, only use JDK 5 with AIX 5.3 and not JDK 6.

• CR 6820147

  When running on OpenSolaris 2008.11, the GlassFish server times out on startup. When you run asadmin start-domain, the following message appears, even though the domain is actually started and functioning:

  Timeout waiting for domain domain1 to go to starting state.CLI156 Could not start the domain domain1.

• CR 6797262

  Before you install Java CAPS on OpenSolaris, make sure the following packages are installed for OpenSolaris. These are not included in the default package set, and Java CAPS installation will fail without them.

  • SUNWfontconfig

  • SUNWj6dev

  • SUNWj6rtx

  • SUNWxwplt

  • SUNWdbus

  • SUNWxcu4 (on OpenSolaris 2009.06)

• CR 6881305

  When using JDK 1.6.0_12 or later with Java CAPS, issues occur with the wizards and editors used to develop applications. In addition, the installation fails on Windows when using JDK 1.6.0_13 or 1.6.0_14. The Java CAPS Installer does not support JDK release 1.6.0_04 in 64–bit versions on Solaris SPARC or AMD environments. The installer also does not support JDK 1.6.0 or later on AIX 5.3.

  To work around this issue, only use JDK versions 1.6.0_03 to 1.6.0_11 when using JDK 6 with Java CAPS, with the exceptions noted above for Solaris SPARC, AMD, and AIX.

• CR 6881054

  On the installer, certain messages are truncated and the full text cannot be read. In some cases, you can expand the width of the installer window to view the entire message.

• CR 6865075

  When you import 5.0.x projects into Java CAPS 6.2, the connections in the Connectivity Map might not be brought forward correctly. If this occurs, you will see Connectivity Map errors when building the Project. The error messages provide information about the connections that need to be fixed.

• CR 6881054

  On the JDK selection section on the Java CAPS installer, messages are truncated and cannot be read.

Known Interoperability Issues

The following are known interoperability issues:

• CR 6707146

  The default Access Manager setup provided by Java CAPS does not work with Federated Access Manager 8.0.

• CR 6662622

  The Worklist Manager portlet from Java CAPS 5.1.3 does not deploy on Portal Server 7.

• CR 6761432

  You cannot undeploy amserver (under GlassFish V2 > Applications > Web Applications). When you try to undeploy amserver, the connection between NetBeans and GlassFish is broken.

• CR 6703514

  Access Manager is preconfigured for the localhost, causing remote accessibility issues when it is accessed through FQDN

  To work around this issue, perform the following steps:

  1. Stop GlassFish.

  2. Navigate to JavaCapsHome/appserver/domains/DomainName/applications/j2ee-modules/amserver/WEB-INF/classes and open AMConfig.properties in a text editor.

  3. Uncomment the com.sun.identity.server.fqdnMap[<invalid-name>]=<valid-name> property.

  4. Modify the property by substituting the proper values for <invalid-name> and <valid-name>.

  5. Restart GlassFish.

• CR 6882644

  Deployment of Web Space Server WAR files fails if GlassFish and Web Space Server were installed from different file-based distributions.

  To work around this issue, deploy the files manually by either using the Admin Console or copying the files to the domain autodeploy directory.

Known NetBeans Issues

• Java CAPS 6 is tested and certified to work with NetBeans plugins that are installed by the Java CAPS Installer. Installing any other NetBeans plugins or plugin updates to your NetBeans IDE can cause compatibility issues. This recommendation does not apply to plugins or updates that you get from Java CAPS Support.

  When starting NetBeans IDE, you may be prompted to install updates for the third-party plugins in your IDE. Do not install them. To avoid being prompted in the future, please follow the instructions below:

  1. On the NetBeans IDE, click Tools and then select Plugins.

  2. In the Plugins window, select the Settings tab.

  3. Select only CAPS Repository Update Center and deselect any other Update Centers.

  4. Click Close to save your changes and close the Plugins window.

  If you want to use other NetBeans plugins, backup the .netbeans directory, which can be found in the top level Java CAPS installation director. Alternatively, use a separate NetBeans installation to try other plugins that are not included with Java CAPS. If you need to restore a backed up .netbeans directory, make sure that your NetBeans IDE is not running. Then remove the current .netbeans directory and replace it with the backed up directory.

Known GlassFish Enterprise Server Issues

• CR 6684658

  The STCMS server does not shut down properly when GlassFish Enterprise Server is run as a Windows service. Even after stopping the service, STCMS is still present in the Windows task manager.

  To work around this issue if you install Java CAPS 6 on Windows and you intend to run Java CAPS as a Windows service, add the following line to domain.xml after installation:

  <jvm-options>-Dcom.sun.enterprise.server.ss.ASQuickStartup=false</jvm-options>

• CR 6744439

  The asadmin commands for creating and managing an STCMS instance are not listed in the output of asadmin help. The available STCMS commands are:

  • create-stcms

  • delete-stcms

  • list-stcms

  • show-stcms-status

  • enable-stcms

  • disable-stcms

  You can access the help information for these commands by typing asadmin help CommandName, where CommandName is one of the commands listed above.

  ---

  Note –

  You must have STCMS installed in order to access the help information for these commands. STCMS is not supported on Mac OS, and is thus not included as part of the default Java CAPS installation on Mac.

  ---

• CR 6785405

  In order to use the recycle-size feature to limit the number of server.log files that are created, you need to install the Sun GlassFish Enterprise Manager Performance Advisor. This patch can be downloaded from http://sunsolve.sun.com. The patch ID is 140751. Follow the installation instructions in the readme file. The readme file also provides links to additional information about the Performance Advisor.

• CR 6882939

  When you install Java CAPS on Mac OS using the Chinese locale, the default domain is not created correctly.

Known Issues for JBI Clustering

The following are known issues for working with Java CAPS JBI components in a clustered environment:

• Issue 1909

  When you configure cluster instances using the GlassFish Admin Console, the configuration does not propagate to any new cluster instances. This is because instances are configured individually. In some cases, this can cause deployment to fail.

  To work around this issue, configure each cluster instance individually or use the following asadmin command to configure all instances in the cluster:

  asadmin update-jbi-application-variable --component=sun-jms-binding name=value

  See asadmin help for usage information.

• CR 6883003

  A web application is unable to find the WSDL file on a second instance when the web service is deployed in a GlassFish cluster where the first node includes the DAS and a node agent, and the second node includes just a node agent.

  To work around this issue, on the second cluster instance create a directory hierarchy for DAS and copy or create a symbolic link to the WSDL file in the location where the web application expects to find it. For example:

  mkdirhier /opt/glassfish/domains/domain1/applications/j2ee-modules/WebAppName/WEB-INF/wsdl/client/WSDLName/

  cd /opt/glassfish/domains/domain1/applications/j2ee-modules/WebAppName/WEB-INF/wsdl/client/WSDLName/

  cp /opt/glassfish/nodeagents/ClusterNodeAgent/InstanceName/applications/j2ee-modules/WebAppName/WEB-INF/wsdl/client/WSDLName/WSDLName.wsdl

  ln -s /opt/glassfish/nodeagents/ClusterNodeAgent/InstanceName/applications/j2ee-modules/WebAppName/WEB-INF/wsdl/client/WSDLName/WSDLName.wsdl

Other Known Issues

• MySQL does not support microseconds, so if an incoming message contains any time or timestamp fields that drill down to the microsecond, the fractal part of the seconds is ignored in the database. For example, if the value of a timestamp is '2010–12–10 14:12:09.019473', the last six digits (019473) are ignored.

• CR 6761256

  The Enterprise Manager command stopserver throws an exception when Enterprise Manager is not running instead of letting you know it is not running.

• CR 6744536

  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.

  To work around this issue, create a file named XML.properties, and add the following line:

  enforceUnqPartAttrib=false

  Save the file to /.netbeans/caps/config/Preferences/com/stc/capsee/cor/utilities. This disables UPA checking. To enable UPA checking, remove the file or set the parameter to true.

• CR 6662117

  Release 6 does not support using components from previous 5.x releases with Release 6 components. For example, you cannot connect to a Release 6 Repository from a 5.1.3 Enterprise Designer, and you cannot connect to a 5.1.3 Repository from NetBeans. It is similar for Enterprise Manager.