These release notes cover release information for version 1.1.0 of the IBM(R) WebSphere(R) Business Integration Adapter for Manugistics. These release notes contain the following sections:
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.
This section lists the new features and improvements made in this release.
Refer to the Adapter for Manugistics User Guide for detailed information about the adapter and the new features.
Between release 1.0.0 and 1.1.0, the following CRs, based on customer-reported cases, were fixed.
Tracking number |
Description |
32508/ 14585 |
The Manugistics connector uses the default value for polling if the object key uses a name-value pair. |
28588 | Traceable SQL messages are built only if tracing is enabled. |
28591 | Improvements are needed in the tracing mechanism. |
28594 | DeltaUpdate verb support should be added in the ODA. |
28868 | Stored procedures should be supported for the DeltaUpdate verb. |
29080 | Manugistics adapter calls are not obeying the timeout. |
29822 | The Manugistics connector generates an unsupported ObjectEventID format. |
30774 | Performance improvements are needed for the Manugistics adapter. |
30436 | Manugistics causes a null pointer exception to occur when the event or archive time is blank. |
31569 | The Manugistics adapter should return output parameters even when the result set is "true" and empty. |
32390 | Issues with SQL scripts in the dependencies subdirectory should be resolved. |
32392 | When the database goes down, the polling connection is not refreshed in the Event Monitor. |
32473 | The ODA should expose nicknames. |
32484 | The connector's treatment of date fields should be modified. |
32647 | The sample needs to be changed, so that a NumberFormat exception does not occur. |
34612 | A means to reduce the number of commits in the Manugistics connector is needed. |
Hardware and software requirements are included in the product documentation. See Installation, migration, upgrade, and configuration information for links to those guides.
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 Manugistics User Guide.
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 API. This section provides instructions for verifying the API version, downloading the latest version, and enabling the adapter to run on various versions of InterChange Server and Adapter Development Kit (ADK).
To check the version of run-time version, 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
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.
To download the latest version of the run time:
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
To enable an adapter to work with various versions of ADK or InterChange Server, follow the appropriate procedure below:
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"
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"
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"
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"
The following problems have been found in this release:
Tracking number |
Description |
35033 | The Manugistics Connector places commas in integers of a retrieved business
object. The WebSphere Business Integration Adapters component's setInt
method applies the default locale settings on the numbers before setting
attributes on the business object. This applies default number formatting
on the number and inserts the commas. Use WebSphere Business Integration Adapters API 1.6.2 Fix Pack and add or set the following adapter properties to "true:" DisableNumberFormatGrouping and DisableLocaleFormating. If set to "true," the DisableNumberFormatGrouping alone will handle the commas in the numbers. The DisableLocaleFormating is a master property that overrides all formatting. It can be used if any other problems are encountered due to formatting. |
41966 | The OracleApps ODA cannot generate a business object from the nickname of a stored procedure when using the Oracle thin driver, because the driver does not support analysis of Synonyms to StoredProcedures. To work around this, either use the actual stored procedure name to generate the business object using the ODA, or construct the business object manually. |
41967 | The framework cannot process more than 20,000 property values either when displaying the ODA configuration properties or when asking the user for business object definition-specific properties. Ensure that no more than 10,000 values are returned in the drop down list, or the ODA will hang. |
46118 | For a RetrieveByContent request that returns MULTIPLE_HITS, the following exception occurs: "An unexpected exception occurred during the construction of a business object. Reason: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1." This will be fixed in Fix Pack 2.4.0.1 of the Adapter Runtime, scheduled to be published in early July, 2004. |
If you are using a DataDirect JDBC driver, you will see the following issues: | |
41977 | When using the DataDirect SQL driver, the OracleApps ODA does not generate appropriate application-specific information for stored procedures that return result sets. The driver does not support analysis of the return type when the stored procedure returns a result set. For example, the stored procedure returns @RETURNVALUE, which the ODA cannot use to generate an attribute. To work around this, manually add the attribute in the business object definition. |
The DataDirect Oracle driver does not provide information on keys when the business object is generated from the nickname of a table, and it does not support analysis of nicknames. To work around this, you will have to modify the business object after it is generated. |
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:
http://www.ibm.com/websphere/integration/wicserver/infocenter
http://www.ibm.com/websphere/integration/wbicollaborations/infocenter (for collaborations)
http://www.ibm.com/websphere/integration/wbiadapters/infocenter
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.