These release notes cover release information for IBM WebSphere Business Integration Express for Item Synchronization, version 4.3.0. They contain the following sections:
Overview | Installation and configuration information |
Product compatibility | Known problems and workarounds |
Hardware and software requirements | Documentation |
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.
IBM WebSphere Business Integration Express for Item Synchronization is a mid-market supplier solution that meets trading partner supply chain integration requirements for integrating product information with the GLOBALregistry of UCCnet. With UCCnet connectivity, suppliers can add or update item data from internal systems and allow those changes to occur throughout their trading network, reducing the time and costs associated with item management.
The 4.3.0 version of WebSphere Business Integration Express for Item Synchronization is made up of these components:
Make sure no other version of InterChange Server is installed on the system on which you plan to install WebSphere Business Integration Express for Item Synchronization.
Hardware and software requirements are listed in Installing WebSphere Business Integration Express for Item Synchronization.
Whether you are installing the software from the CD or downloading it from Passport Advantage and installing it from a local directory, refer to Installing WebSphere Business Integration Express for Item Synchronization.
This guide also includes configuration information.
The following problems have been found in this release:
Component name |
Tracking number |
Description |
InterChange Server Express | 23066 | If an LLBP collaboration receives a response to an inbound service call while the collaboration is stopped, then the response is not processed when the collaboration is restarted. |
InterChange Server Express | 23248 | If validate database connection is selected from the Server View, error messages are printed in the InterChange Server Express log. No feedback is given in the GUI. |
InterChange Server Express | 23885 | If a collaboration is in an in-doubt state, InterChange Server Express System Monitor incorrectly displays the status color in red instead of yellow. |
InterChange Server Express | 24084 | For transactional collaboration groups, during server boot time recovery, although InterChange Server Express System Monitor incorrectly shows the state of the collaborations in the group to be active, they are inactive until the collaboration recovery is complete. |
InterChange Server Express | 24382 | If the ItemSync collaboration is in a paused state before shutting down
InterChange Server Express, the collaboration displays as inactive after
InterChange Server Express is restarted.
Workaround: Start the collaboration, then stop it and restart it again to enable recovery and to process events. |
InterChange Server Express | 26017 | The retry feature of connector agents does not work. The RestartRetryCount
is currently set to 0 (default) and should not be increased. Workaround: To restart the agent, use the OAD restart feature. In the connector configuration file, set OADAutoRestartAgent to true. |
InterChange Server Express | 26650 | You must install the WebSphere Business Integration Express for Item Synchronization product as a local administrator. |
Launchpad | Before installing the DB2 Express or WebSphere MQ component, you must disable
any real-time file-system protection features of installed antivirus software. 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. |
|
Launchpad | 27110 | If you are installing on a Windows XP machine and the Windows XP Welcome
Screen is enabled, you cannot log in as Administrator after installing
the DB2 Express component. This is because the DB2 Express component creates
a user with administrative rights, causing the Welcome Screen to stop displaying
the Administrator account. 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. |
Launchpad | 27198 | Sometimes when installing the Java 1.3.1 component from the Launchpad, you are prompted to insert javaw.exe into your CD-ROM drive. You can ignore this message. Click Continue. |
Launchpad | 27555 | When using MS SQL Server 2000, if a database named SMB_DB already exists on the database server, you must manually drop the database before proceeding with the Database Setup section in the Launchpad. |
Installer | When running the uninstaller, some files may remain on the system. Workaround: Remove the files manually. | |
Installer | 11600 | Initial startup of Installer may be slow during the initialization of a JVM. Do not try to start Installer multiple times. |
Installer | 26076 | The Naming Server panel should appear only if you select Toolset Express. However,
it may appear on other occasions.
Workaround: In the Naming Server panel, enter the IP address of machine on which the ItemSync collaboration will be installed. |
Installer | 27311, 27557
|
Silent install installs a typical setup type even if you specify a customized setup type in the Setup Type section of the settings_ItemSync_Windows.txt response file. Workaround: In the Setup Type section of settings_ItemSync_Windows.txt, clear the current setup type by using the following value: -W expressSetupTypesSelectedSetupTypeId= Then set all desired Feature section options to true and those not desired to false. Note: If you set any Adapters Feature option to true, also set the Item Sync Feature to true and include an option file. |
Installer | 27558 | Windows services configured during second and subsequent installations are not removed from the Services Control Panel during an uninstallation.
Workaround: Manually remove the service from the Windows registry and then reboot your machine so the Services Control Panel is updated. All adapter services are named CWInterchange WBIAdapterName (for example, CWInterchange WBIJTextAdapter). Also, a CWInterchange WICSExpress service is created when you install the ItemSync collaboration. To remove any of these services, make sure the service is set to manual execution in the Service Control panel and is not started. Use regedit to go to the registry editor. Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, and Services. Remove the folder entries for adapter and InterChange Server Express as needed:
|
Installer | 27714 |
The system environment variable MQ_LIB may be set to the incorrect value
\java\lib for the WebSphere MQ Java library location. It should be set
to C:\Program Files\IBM\WebSphere MQ\Java\lib. |
Toolset Express | 18986 | Connector Configurator, Business Object Designer
Express, Map Designer Express, and Relationship Designer Express show deleted projects
in their project lists.
Workaround: Close all designer tools before deleting a project from System Manager. |
System Manager | 18687 | For user-created folders inside a project, System Manager returns an error
when creating a collaboration object.
Workaround: Do not add, delete, or modify a project folder outside of System Manager. System Manager maintains the projects in the file system. |
Relationship Manager | 28022 | Only one participant instance is allowed for each participant definition of an identity relationship. However, the Add Participant item in the context menu is enabled when it should be disabled. As a result, you can add one more than participant instance to a participant definition of an identify relationship, which causes an error. |
Connector Configurator Express | You cannot create multiple values of a connector-specific property in the Connector-Specific Properties category. You must use the Connector-Specific Property Template wizard to create multiple values of a connector-specific property. | |
InterChange Server Express System Monitor | 23820 | When changing the color theme of graphs (Bar, Line, Stacked Bar), you must click on the large color box choice for the colors to be set properly. Do not use the small color boxes for choosing the color theme. |
InterChange Server Express System Monitor | 26180 | If you are running the Monitor with DBCS locales, do not change the font settings for the Line, Bar, Stacked Bar, and Meter charts. If you change the fonts for these charts, the DBCS characters will appear as squares. Workaround: To see the characters, clear the cookies in the browser. The settings for the Table and Table Tree can be changed. |
InterChange Server Express System Monitor | 27860 | If no adapters are installed, clicking the Connector View in the Monitor causes an error. |
Integrated Test Environment | The ITE console menu now color-codes the text depending on the message type: normal text in black, warnings in blue, and errors in red. | |
All adapters | 27452 | When executing the start script for any adapter, the error "Input
line too long" might be returned and the adapter will not start. The
problem is that the command line to start the adapter is too long. WorkAround: To avoid this problem, shorten the start script command to invoke the adapter by removing unnecessary or duplicate .jar files or DLLs from the class path of the start script. |
Adapter for JDBC | 23147 |
Using CLOB data types is restricted to retrieve operations because of restrictions in different JDBC drivers on writing CLOB data to the database. |
Adapter for JDBC | 26896 | An error occurs when executing event_package_db2.sql (a JDBC adapter dependency file). To compile this SQL script, first copy its contents and paste it in Development Center under DB2 Express, and then compile. |
Adapter for JDBC | 27326 | The error "Input line too long" might be returned when you execute the start script. Workaround: If this error is returned, remove all drivers you are not using from the JDBCDRIVERPATH and DATADIRECT variables in the start script. |
Adapter for JMS | 27717 | The samples for this adapter are incompatible with Toolset Express. The JMSConnector.cfg file in the samples subdirectory may not be loaded properly into Connector Configurator. |
Adapter for Web Services | 23993 | When the WSDL ODA encounters multiple inline schemas that import each other without providing schema locations, it logs warnings or errors. However, the business objects are generated properly. |
Adapter for Web Services | 24662 | When WebSphere MQ 5.3 CSD03 is used as the JMS provider, the adapter's JMS listener cannot read message bodies after moving the message from the input to the in-progress queue. This is a problem with the WebSphere MQ application. |
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 IBM WebSphere Business Integration Express for Item Synchronization InfoCenter. The following documents can be found on that Web site:
Quick Start
Installing WebSphere Business Integration Express for Item Synchronization
Business Object Development Guide
Map Development Guide
Data Handler Guide
User Guide for WebSphere Business Integration Express for Item Synchronization
Item Synchronization Collaboration
Generic Business Objects
Adapter for JDBC User Guide
Adapter for JMS User Guide
Adapter for JText User Guide
Adapter for WebSphere MQ User Guide
Adapter for Web Services User Guide
Adapter for XML User Guide
Adapter for iSoft Peer-to-Peer Agent User Guide
Adapter for mySAP.com User Guide
Adapter for e-Mail User Guide