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)