Release Notes for Version 4.1.0 of the IBM WebSphere Business Integration Adapter for Portal Infranet 6.x

These release notes cover release information for version 4.1.0 of the IBM WebSphere Business Integration Adapter for Portal Infranet 6.x.

Important notes

Before starting the adapter for Portal Infranet, you must copy some files to the product installation.

In a UNIX environment:

  • Copy the following files:
pcm.jar
pcmext.jar

from the Portal Server directory $INFRANET/jars to the product installation directory ProductDir/connectors/Portal/dependencies.

  • Copy the file classes12.zip from the Oracle Server directory $ORACLE_HOME/jdbc/lib to the product installation directory ProductDir/lib.
  • Change the following lines in ProductDir/bin/CWSharedEnv.sh:
THIN_DRIVER=ProductDir/lib/classes12_01.zip

to:

THIN_DRIVER=ProductDir/lib/classes12.zip

In a Windows environment, copy the following files:
  • pcm.jar
  • pcmext.jar
from the Portal Server directory %INFRANET%\jars to the product installation directory ProductDir\connectors\Portal\dependencies.

Notes on adapter functionality:
  • Before posting an event to the integration broker, the connector agent checks for event subscription. If the event is unsubscribed, the event status is modified to UNSUBSCRIBED or is archived with that status.
  • During subscription delivery (posting an event to the integration broker), if any of the following occurs:
  • If there is a problem with retrieving the event
  • If there is a problem building the complete event message
  • If the event type becomes unsubscribed
the status of the event is changed to Error Posting Event and the adapter continues processing events from the event store.
  • During subscription delivery, if the connector controller becomes inactive, the status of the event is changed to Error Posting Event, a FATAL error message is logged, and the adapter stops processing events.
In all cases, the agent remains active.

The release notes contain the following sections:

New in this release WebSphere Business Integration Adapters API and run time
Product fix history Known problems and workarounds
Hardware and software requirements Documentation updates
Installation, migration, upgrade, and configuration information

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

In this release, the multiple levels of VERB ASI support have been removed.

Refer to the Adapter for Portal Infranet User Guide for detailed information about the adapter.

Product fix history

Between adapter releases 4.0.0 and 4.1.0, the following CRs, based on customer-reported cases, were fixed.
CR
number
Description
14590 Removed the support for multiple levels of VERB ASI.
21761 UNIX files were not in UNIX format. This has been fixed.
21863 Fixed spelling in text in trace messages.
23257 Added code to handle version 6.5.0 of the Portal Infranet application.

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 information

Installation information

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:

Upgrade notes

WebSphere Business Integration Adapters API and run time

Make sure that you run adapters with WebSphere Business Integration Adapters (WBIA) run-time version 1.5.0 or later.

Verifying the version of WBIA run time

To check the version of WBIA 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.5.0
Implementation version indicates the current version of WBIA API.

If the version is not 1.5.0 or later, you must download the latest WBIA run time.

Downloading the WBIA run time

To download the latest version of the WBIA run time:

  1. Go to http://www.ibm.com.
  2. Click the Support and downloads tab.
  3. Under the Downloads heading, click All downloads & drivers.
  4. In the Enter search terms field, type "wbia api" and click Submit.

After you download and install the 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
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 InterChange Server

To enable an adapter to work with various versions of ADK or InterChange Server, follow the appropriate procedure below:

InterChange Server versions 4.0.1 and 4.1.0, ADK versions 2.0.x

Windows: In CWConnEnv.bat, set the CWVERSION variable to 4.X.

set CWVERSION="4.X"

UNIX: In CWConnEnv.sh, set the CWVERSION variable to 4.X.

set CWVERSION="4.X"
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"
Running an Object Discovery Agent (ODA) against InterChange Server versions 4.0.1 and 4.1.x, ADK versions 2.0.x and 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"

Known problems and workarounds

The event notification module (FmCw.dll) verifies the USERID of any Portal event sent to it (defined in the pin_notify_cw file). If the module finds no PIN_FLD_USERID associated with the event, it returns an error and causes problems saving the object online. You can check for these errors in the log file defined in the crossworlds.cnf configuration file. Events with no USERID must be adjusted (f-lists or the storable classes) to include such an ID. All events sent to the module are listed in the pin_notify_cw configuration file, and they are compared with the constraints defined in the event_code.txt file. The \event\customer\billinfo is an event type where such a problem exists.

The event notification module verifies the USERID to prevent events sent by the adapter from being added to the event queue and sent back to the adapter (called ping-ponging).

Documentation updates

Product documentation is not included as part of the product package, either by CD or 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, 2003