Release Notes for Version 5.5.0 of the IBM WebSphere Business Integration Adapter for JText

These release notes cover release information for version 5.5.0 of the IBM(R) WebSphere(R) Business Integration Adapter for JText. These release notes contain the following sections:
New in this release WebSphere Business Integration Adapters API and run time
Product fix history Limitations
Backward compatibility Known problems and workarounds
Hardware and software requirements Documentation
Installation, migration, upgrade, configuration

Note: Important information about this product may be available in Technical Support Flashes issued after these release notes were published. These can be found on the WebSphere Business Integration support Web site, http://www.ibm.com/websphere/integration/wbiserver/support. Select the component area of interest and search the flashes section. 


New in this release

The following new features and improvements were made in this release: Refer to the Adapter for JText User Guide for detailed information about the adapter and the new features.

Product fix history

Between release 5.4.0 and 5.5.0, the following CRs, based on customer-reported cases, were fixed.
Tracking number Description
23371 Error messages were too generic in JText.
24803 MVS FTP site commands were not supported. Support has been added in this release.
27304 In the connector start script for the JText connector (start_JText.sh), the directory for the NetComponents.jar is hardcoded to the connector directory name JText. Fixed in this release.
28151 Allocation in JText Adapter has been reduced through improved StringBuffer usage.
28152 JText memory usage was reduced due to an improvement in file reading..
30237 The JText adapter failed to poll an FTP site that used a Swedish locale. Fixed in patch 5.4.1.
30838 The JText Adapter did not pass the file name to the data handler. Fixed in patch 5.4.3.
31418 The JText adapter did not poll event files based on a timestamp. Fixed in patch 5.4.2.
31747 When the FTPKeepConnectionOpen property was set to "true," and the FTP server timed out, the first service call would be consumed for re-establishing the connection to the remote FTP server; therefore, the first request would not be processed. Fixed in patch 5.4.5.
31768 The Archiver is not fully turned off when setting the archiving enabled flag to "true."
32426 The JText adapter went into an infinite loop when polling from an FTP site if a file with the same name existed in the local event directory.
32690 During request processing, when an FTP URL was specified for the OutFileName property of the dynamic child meta-object, the connector failed to put the file on the FTP site. Fixed in patch 5.4.4.
33411 When two files with the same file mask existed, and one of them was still being modified, the connector picked up the files that were not locked and processed them, but did not archive or delete them. It would keep polling the same files repeatedly in a loop, until all the files with the same mask were retrieved for processing. Fixed in patch 5.4.5.
34051 A problem occurred when polling an FTP site if the JText adapter used a Swedish locale. Fixed in this release..
34613 JText 5.4.2 failed to poll a remote FTP server when SortFilesOnTimestamp was set to "true." Fixed in patch 5.4.6.

Backward compatibility

This version is not backward compatible with previous versions of the Adapter Development Kit (ADK), and needs the ADK 4.2.2.2 patch to function.

Hardware and software requirements

Hardware and software requirements are included in the product documentation. See Installation, migration, upgrade, and configuration information for links to those guides.

Installation, migration, upgrade, and configuration

Whether you are installing the software from the CD or downloading it from Passport Advantage and installing it from a local directory, refer to the appropriate guide: These guides also include general migration, upgrade, and configuration information.

For hardware and software requirements and configuration information specific to this adapter, refer to the Adapter for JText User Guide.


WebSphere Business Integration Adapters API and run time

Make sure that you run this version of the adapter with WebSphere Business Integration Adapters run-time version 1.7.0 or later.

The WebSphere Business Integration Adapters API .jar files and the associated scripts (CWConnEnv.bat and CWODAEnv.bat for Windows(R); CWConnEnv.sh and CWODAEnv.sh for UNIX platforms) are installed by the WebSphere Business Integration Adapters API. Before installing the adapter, make sure that the WebSphere Business Integration Adapters run time is installed. If the version is not 1.7.0 or later, you must download the latest WebSphere Business Integration Adapters API. This section provides instructions for verifying the API version, downloading the latest version, and enabling the adapter to run on various versions of WebSphere InterChange Server and Adapter Development Kit (ADK).

Verifying the run-time version

To check the version of the run time, locate the manifest file (ProductDir\lib\WBIA.jar) and open it in a suitable Java JAR editor. Look for the following lines:
Implementation-Title: "CWConnectorAPI"
Implementation-Version: 1.7.0
The line Implementation-version indicates the installed version of the API. If the version is not 1.7.0 or later, you must download the latest run time.

Downloading the run time

To download the latest version of the run time:
  1. Go to http://www.ibm.com.
  2. Click the Support & downloads tab.
  3. Under the Downloads heading, click Downloads & drivers.
  4. In the Enter search terms field, type "wbia api" and click Submit.
After you download and install the run time, you should see the following files:
lib\WBIA.jar
lib\WBIA\3.0.0\WBIA.jar
lib\WBIA\4.0.0\WBIA.jar
lib\WBIA\4.1.1\WBIA.jar
lib\WBIA\4.2.0\WBIA.jar
bin\CWConnEnv.bat (Windows)
bin/CWConnEnv.sh (UNIX)
bin\CWODAEnv.bat (Windows)
bin/CWODAEnv.sh (UNIX)
connectors\messages\CwConnectorAgentMessages.txt

Enabling adapters for earlier versions of Adapter Development Kit and WebSphere InterChange Server

To enable an adapter to work with various versions of ADK or WebSphere InterChange Server, follow the appropriate procedure below:
InterChange Server versions 4.1.x (except 4.1.0), ADK versions 2.1.x
Windows: In CWConnEnv.bat, set the CWVERSION variable to 4.1.X:
set CWVERSION="4.1.X"

UNIX: In CWConnEnv.sh, set the CWVERSION variable to 4.1.X:
set CWVERSION="4.1.X"

InterChange Server versions 4.2.0 and 4.2.1, ADK versions 2.3.0 and 2.3.1
Windows: In CWConnEnv.bat, set the CWVERSION variable to 4.2.:
set CWVERSION="4.2"

UNIX: In CWConnEnv.sh, set the CWVERSION variable to 4.2:
set CWVERSION="4.2"

Running an Object Discovery Agent (ODA) against InterChange Server versions 4.1.x (except 4.1.0), ADK versions 2.1.x
Windows: In bin\CWODAEnv.bat, set the CWVERSION variable to 4.1.X:
set CWVERSION="4.1.X"

UNIX: In bin/CWODAEnv.sh, set the CWVERSION variable to 4.1.X:
set CWVERSION="4.1.X"

Running an Object Discovery Agent (ODA) against InterChange Server versions 4.2.0 and 4.2.1, ADK versions 2.3.x
Windows: In bin\CWODAEnv.bat, set the CWVERSION variable to 4.2:
set CWVERSION="4.2"

UNIX: In bin/CWODAEnv.sh, set the CWVERSION variable to 4.2:
set CWVERSION="4.2"


Limitations


Known problems and workarounds

The following problems have been found in this release:
   
Tracking
number
Description
31633 In a UNIX environment, a connector_manager_adapter script is generated by the installer program. The script references adapterEnv.sh, which was introduced with version 2.4.0 of Adapter Framework. If you are running an older version of Adapter Framework, adapterEnv is not available. To run this version of the adapter with an older version of the Framework, change the reference from adapterEnv.sh to CWSharedEnv.sh in the connector_manager_adapter script.
46569 In MVS SDS, when a value is given for both FTPArchiveDir and FTPRenameExt, the connector tries to append a timestamp, but even for a small file name this scenario will not create an archived file because the file naming convention exceeds the MVS limitations. To work around this, prevent a timestamp append by keeping FTPArchiveDir as blank, and provide a value for FTPRenameExt.
46570 When the same input file is added to the event folder in MVS SDS, during the second poll, the event file does not overwrite the existing archived file. Because the event file is not moved from the events folder, this file is polled repeatedly. This scenario occurs when FTPArchiveDir is "/" and FTPRenameExt has a value. As a workaround, you can archive the event file with a timestamp. To do this, either set FTPArchiveDir as "/" and FTPRenameExt as blank, or give a path to FTPArchiveDir and a value to FTPRenameExt.
46499 If there are a couple of files that match the event mask in MVS PDS and FTPRenameExt  is specified, the connector archives only one file and is not able to be rename and archive the second file. To work around this, delete the MVS event file without renaming it. Specify both FTPArchiveDir and FTPRenameExt as blank.

Documentation

Product documentation is not included as part of the product package, either by CD or by electronic product distribution. The documentation for this product can be found in the following InfoCenters: To obtain the product documentation, visit the Web site and download the current documentation set for the release that you are using. Follow the instructions provided on the InfoCenter page to complete the installation.

Copyright IBM Corp. 1997, 2004