Release Notes for IBM WebSphere Business Integration Server Express, Version 4.3.0

• Repository creation can fail. When repository creation fails because of this issue, the Installer log includes the following message line: "No start database manager command was issued."
• Startup of InterChange Server Express can fail, because without the DB manager running, InterChange Server Express cannot connect to SMB_DB. When this failure occurs, the InterchangeSystem log file messages include this line: "No start database manager command was issued."

Both of these problems can be addressed by following these steps:

1. Open DB2 Control Center.
2. Expand the All Cataloged Systems folder, then expand the folder for your host, and then expand the Instances folder.
3. In the Instances folder, right-click the DB2 icon and choose Start.
   This DB2 message displays: "DB2START processing was successful."

After you have performed these steps, you can create a repository and successfully start InterChange Server Express.

Workaround: Manually delete the SMB_DB database before uninstalling and reinstalling DB2 Enterprise or DB2 Express. Deleting the actual database eliminates its alias.

Workaround: After installation, change the permissions on these files.

If you have Norton AntiVirus software installed, you can disable its real-time file-system protection feature by stopping the "Norton AntiVirus Client" Windows service. For other antivirus products, refer to the product's documentation for instructions on how to disable the real-time file-system protection feature. You can enable this software after the product has been installed.

Workaround: Disable the welcome screen. Go to Start > Control Panel > User Accounts > Change the way users log on or off. Clear the Use the Welcome screen box, then click Apply Options. To log in as the DB2 administrator if you are locked out, you can log in with the user ID db2admin and the password smbP4$$word.

Workaround: Extract electronic images to a location that does not contain spaces.

C:\IBM\WebSphereServer\connectors\EMail>REM start the Java connector under the Java Application End
The input line is too long.
The syntax of the command is incorrect.

Workaround: In the files \connectors\Email\start_Email.bat and start_Email_service.bat, remove %DataHandler_JAR% from the following line: set JCLASSES=.;%JCLASSES%;%JAVA_MAIL%;%XML_PARSER%;%DataHandler_JAR%;

Workaround: Configure unique InputFormat and InputQueue keys for each of the BusinessObjectType_verb attributes in the static meta-object.

31301

When retrieving a result set returned by a stored procedure, the adapter flags the following error: Attribute RS not found. The output attribute name is retrieved after the adapter checks that the attribute name is RS. The attribute name is now retrieved before the check, so that OP=RS is handled appropriately. Fixed in fix pack 2.4.3 of the adapters.

33394

During polling, multiple commits to the database update the status of events in the event and archive tables as soon as possible. This is required because some users filter events in the event table based on status. However, this can cause performance problems. Fixed in fix pack 2.4.3 of the adapters.

The solution makes the multiple commits configurable. A new connector specific property - SelectiveCommitForPoll - has been introduced. If its value is true, then there is only one commit - after an event has been processed. If its value is false, then the behavior is the same as before - commits to the database are done at each stage of event processing. The default value for the property is false.

Child update operations fail when they are sent along with new child create operations as part of an Update operation. This has been resolved. Now, the item count is obtained every time before updating or creating a child instance. Fixed in fix pack 2.3.2 of the adapter.

The application password value is not encrypted in the trace file, even though the property is encrypted. This has been resolved. Because all connector configuration properties are traced before entering the connector agent code, the second tracing of properties that do not undergo changes is removed. Fixed in fix pack 2.3.2 of the adapter.

• The self-extract capability has been restored.
• When the file extracts, two folders are created, CW_EVENT_V150 and CW_EVENT_V140, in the %CROSSWORLDS%\connectors\PeopleSoft\Dependencies\Projects directory. CW_EVENT_V140 is for PeopleTools 8.1x and the CW_EVENT_V150 is for PeopleTools 8.4x.
• For the CW_EVENT_V140 project, PeopleCode had been modified to include Modes U, L, and C. These modes are represented by the Update verb.

SiebelODA converts the Siebel data type DYE_NUMBER to Integer instead of Float. This has been fixed. Note: The adapter treats all data as String data type, so it does not use the data types converted by the ODA. Fixed in fix pack 4.4.2 of the adapter.

SiebelODA sets the application-specific information in a wrapper business object definition as ObjectName= <object name>, instead of ON=<object name>, where <object name> is the name of the Siebel business object. Fixed in fix pack 4.4.2 of the adapter.

Workaround: Modify the target to ProductDir\connectors\WebSphereCommerce\start_WebSphereCommerce.bat WebSphereCommerce WebSphereICS

Example: C:\IBM\WebSphereServer\connectors\WebSphereCommerce\start_WebSphereCommerce.bat WebSphereCommerce WebSphereICS

Workaround: If possible, regenerate the business object definitions using the latest version of XML ODA included in patch 2.5.2.

Workaround: Manually change the application-specific information for the attribute representing xml:lang in the business object definition to attr_name=lang;type=attribute;attr_ns=http://www.w3.org/XML/1998/namespace.

The first bulleted item of the example after step 4 should read as follows:

Add the IBM ORB property to the ORB_PROPERTY variable in the CWSharedEnv file: ORB_PROPERTY=-DORBNamingProvider=CosNaming
-Dorg.omg.CORBA.ORBClass=com.ibm.CORBA.iiop.ORB
-Dorg.omg.CORBA.ORBInitialPort=%ORB_PORT%
-Dorg.omg.CORBA.ORBInitialHost=%ORB_HOST%
-Dcom.ibm.CORBA.Debug.Output=nul
-Dcom.ibm.CORBA.ThreadPool.MaximumSize=100

• In step 4, the URL should be http://hostname:portnumber/ICSMonitor.
• In step 5, the URL should be http://hostname:portnumber/FailedEvents.

• "Installing WebSphere Business Integration Server Express and Express Plus using the GUI," in the third bulleted item in the list of assumptions.
• "Checking software requirements" in Table 4.