© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This release notes file contains late-breaking information about limitations and known problems and workarounds for the following WebSphere® Integration Developer enterprise discovery wizards:
- Enterprise service discovery
- Enterprise data discovery
When you successfully connect with security to a WebSphere Service Registry and Repository server for the first time, the server caches the keystore and truststore files.
The server refers to these cached files on subsequent connections. Because of this cache, you cannot connect to the server using a different keystore or truststore file in the same session.
If you want connect to the server using a different keystore or truststore file, do the following:
1. Shut down WebSphere Integration Developer, and then restart it.
2. Select Windows > Preferences > WebSphere Service Registry and Repository.
3. Type the new connection information for the WebSphere Service Registry and Repository server, including the path to the new keystore and truststore files.
4. To create a connection and cause the server to cache the new keystore and truststore files, click Test Connection.
You can now search the WebSphere Service Registry and Repository server using the new keystore and truststore files.
During each WebSphere Integration Developer session, the tools can use only one instance of the resource adapter that uses native libraries.
For example, if you import a resource adaptor that uses native libraries into two connector projects, A and B, then you will have created two instances of this resource adapter in the workspace. If you try to run the Enterprise Service Discovery wizard and select the resource adapter from connector project A, everything will function as usual. However, if you then try to run the Enterprise Service Discovery wizard again, this time choosing connector project B, you will receive an error message similar to the following, where the name of the resource adapter and library name would differ for your situation, when you attempt to connect to the Enterprise Information System (EIS):
The resource adapter named 'JDBC EMD Adapter' returned the following error: 'Failure in connection to EIS java.lang.UnsatisfiedLinkError: db2jdbc (Library is already loaded in another ClassLoader)'
This error occurs because of a Java™ Virtual Machine (JVM) limitation. Each JVM allows only one class loader to load a native library at a time. Each connector project has its own class loader to load the classes that the connector provides. Therefore, only the first connector project can load the native library until that library is released.
To use the second resource adapter instance, you need to exit WebSphere Integration Developer, and then restart it.
When you import the data structure to create a business object, note that the C importer does not correctly handle anonymous structure declarations, such as in the following code:
typedef struct {
char loanId[20];
double loanAmount;
char date[20];
struct {
char taxPayerId[10];
char firstname[20];
char lastname[20];
char email[50];
} Customer[1];
} LoanInfo;To enable the code to import correctly, modify the declaration to put the anonymous structure declaration outside the main structure declaration as a named structure.
The following declaration is equivalent to the above code but will import correctly:
typedef struct {
char taxPayerId[10];
char firstname[20];
char lastname[20];
char email[50];
} Taxpayer;typedef struct {
char loanId[20];
double loanAmount;
char date[20];
Taxpayer Customer[1];
} LoanInfo;
To give you more options when you are use JMS and EIS bindings with your exports, asynchronous reliability and interaction style properties were added to these export bindings.
To deploy an application that uses these properties to WebSphere Process Server 6.0.1 or earlier, you will need to add APAR JR23428 - TOLERATION OF ENHANCED ARTIFACTS IN WPS/WESB FIX PACK 1 to the server. This interim fix is available on the WebSphere Process Server Support Web site.