IBM WebSphere Adapter for Lotus Domino, version 7.0.0.4 notes

This document contains the following sections:

Enhancements and fixes

New and modified connector properties

Upgrade notes

This table lists the enhancements and fixes in fixpack version 7.0.0.4.

Enhancements

APAR

Title

Details

103301

Enhancing JCA Domino Adapter OutBound RetrieveAll with faster FTSearch

Symptom: RetrieveAll Outbound operation currently uses search() function on the Domino Client API. This is much slower when compared to the indexed search approach that Domino API provides.

Resolution: Provide an additional option to the customer to use indexed search so that they can benefit from the speed. This additional option 'Use Indexed Search' will be available as part of the External Service Discovery wizard.

Fixes

APAR

Title

Details

101456

Detecting illegal XML characters in SDO DESPI of Adapters.

Symptom: We are facing an issue in which a runtime exception is being thrown when the BO generated by the Adapter is being serialized down the line to be transferred over the wire during the BOXML serialization because of invalid xml characters in the BO.

Resolution: Provide options to let the user to make choices and add validation in SDO DESPI of Adapters. Currently we have 3 options: (a) Do not validate BO content for illegal XML characters (default); (b) Throw exceptions if BO content contains illegal XML charaters;(c) Discard illegal XML characters in BO content and log.

102613

JR38019

Enable JCA timer capability for inbound polling

Symptom: Adapter uses a polling thread in the runtime, which will poll as per the pollperiod. The polling thread will be only submitted once and always being in the runtime environment. When there are no events for a longer duration, the polling thread will be hung and throws a warning message from the JCA container.

Resolution: Use JCA timer to schedule the polling thread, so the polling thread would be submitted according to the JCA scheduler, which will solve the thread hang issue.

103162

JR39129

Duplicate messages are created in the event table due to unexpected database outage.

Symptom: During Adapter Inbound operation, after several unplanned database outages during event processing duplicate messages can be observed. This is due to the fact that the event is delivered but the overall transaction is marked failure and no rollback is called by the transaction manager.

Resolution: If the event is already delivered to the downstream components but the overall transaction is marked failure due to issues in downstream component, the event is deleted if no rollback is issued.

This table lists the enhancements and fixes in fixpack version 7.0.0.1.

Enhancements

APAR

Title

Details

There are no enhancements in this fix pack.

Fixes

APAR

Title

Details

100101

TVT: Hard-coded strings on EMD screen

Symptom: The message "All fields of the form are already included!" is hard-coded.

Resolution: Make the message support globalization.

100356

When BO name is same and BO namespace is different, inbound work may be failed.

Symptom: When adapter creates 2 or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException.

Resolution: Redefined the methods of "hashCode()" and "equals()" in the SDOV1Type class. Then individual adapter can distinguish those BO correctly by "namespace + name" if those BOs name are equal.

100406

Adapter will encoutner NPE after restart the app on server!

Symptom: For Adapter inbound and outbound operation(standalone deployment), after the application is restarted, the NullPointerException will appear when the adapter tries to query the ASI Infor from cache.

Resolution: The BO's namespace and name has been preserved as BO instance's fields. After the application is restarted, adapter can still get them from those instance's field rather than the stale data cache.

99888

Change to use PmiRmJmxService MBean to get arm transaction factory name

Symptom: When adapter gets ARM transaction factory name to process ARM transaction, a WAS internal private API is used for it, which need to be replaced with public interfaces.

Resolution: Switched to Invoke PmiRmJmxService MBean, a set of public interfaces exposed by WAS to get ARM transaction fatory name.

77930

Printing out the AdapterFoundationClasses version in the Logs/traces.

Symptom: Currently with all the adapters , The AFC version is not printed out in the logs/traces. It would be really helpful to have this information printed out to the logs/traces especially in debugging issues due to conflicting AFC being loaded at runtime.

Resolution: Print AFC version in the trace

100734

Update the bundled NCSO.jar to the 8.5.1 version of the Domino server

Symptom: Currently the version of the bundled NCSO.jar is 8.5

Resolution: Update the bundled NCSO.jar to the 8.5.1 version of the Domino server

This table lists new connector properties
#	Version	Platform	Add or Remove	Property (Note that property names are case sensitive)
There is no new connector property introduced/modified for this version of fix pack.

To upgrade to the fix pack version 7.0.0.4, do the following:

1. Ensure you have followed the 'Installation Instructions' section in the download link before proceeding further.

2. If you need to use the Fix Pack for EMD, delete the connector project in the WID, import the new rar and apply the EIS specific dependency files. The following steps describe how to do the same.

a. Open the Java Build Path for the SCA module and remove the Connector project selected on projects tab.

b. Open the dependency editor and remove the connector project.

c. Delete the connector project from workspace.

d. Import the new rar file. Add any dependency files from EIS specific APIs as needed.

e. Open Java build path for the SCA module and select the Connector project selected on projects tab.

f. Open the dependency editor and add the connector project if it is not already present and check "Deploy with Module".

3. To update deployed applications(that have an embedded adapter RAR file) on the WebSphere Process Server,use the following procedure

a. Stop the application that needs to be updated,using the WebSphere Process Server admin console

b. Select Update for the corresponding application in the WebSphere Process Server admin Console.

c. Select Replace or add a single file option with relative path as name of the rar file - LotusDomino.rar.

d. Click the Browse button to select the updated RAR file on your local file system.

e. Select the default values for the consecutive steps and select Finish.This will ensure that existing configurations e.g. MCF,are not changed and the JAR files are only updated.

July 08, 2011 6:00 PM