Previous Fixes

The following list of problems have been addressed with previously-released fixes. These previously-released fixes are included in this cumulative fix.

Interim Fix 001 - General Fixes

• IMS Connector for Java v9.1.0.1- IMS Connector for Java v9.1.0.1 repackages IMS Connector for Java v2.2.2 into IMS v9.1.  IMS Connector for Java v2.2.2 is a Data Management tool offering shipped as a component of IMS Connect v2.2.  IMS Connector for Java v9.1.0.1 is functionally equivalent to IMS Connector for Java v2.2.2.
• IMS Connector for Java Limitations - IMS Connector for Java (also known as the IMS resource adapter) has the following limitations, which have been added to the Limitations section of the help:
  • Currently the SSL support only supports TLSV1.0 protocol, X.509 certificates, and JKS keystores.
  • Limitations of the MFS support can be found in the HowTo.html file that is installed with the run-time component of IMS Connector for Java.
  • IMS Connector for Java attempts to reconnect a socket after IMS Connect fails and is restarted. This means that most interactions will execute successfully following the restarting of IMS Connect. However, in some cases, a SYNC_SEND (send only) interaction will appear to execute successfully, but the message will not be received by IMS. This occurs when a SYNC_SEND interaction is the first interaction that attempts to use a socket after IMS Connect fails and is restarted.
• Process editor updates:
  • A correction to the transformer service support addresses incorrect generation of aggregate messages.
  • A process using a resource adapter and complex business objects occasionally would take a very long time to generate and issue an error at run time. This error has been corrected.
  • Occasionally, generation of a BPEL process using the SOAP/HTTP for IBM Web Service deployment options would fail. This interim fix corrects the problem.
  • Occasionally, if a sub process had more than one partner link type of a "my role" kind, the generate deploy code wizard would request an endpoint. This behavior has been corrected.
  • A process created with a correlation set would fail to deploy in the previous version. The problem has been corrected.
  • A message would sometimes fail to completely expand in a tree view in the editor. The problem has been corrected. 
  • Improvements have been made to syntactical error checking.
  • A null pointer exception that was thrown when generating a WSDL interface has been corrected.
  • Sometimes at the point of generating a new process, a message would be returned telling you to replace the WSDL interface. This error has been fixed.
• A correction was made to prevent an exception being occasionally thrown when code was generated by a wizard.
• When generating deploy code after building a service from a service, occasionally an error was issued. This problem has been corrected.
• An EJB deployment descriptor occasionally was generated incorrectly with an empty message selector element. This problem has been corrected.
• Several limitations have been added to the help. They include:
  • Hyphens are not supported in XSD names when a service is deployed as a SOAP service.
  • For deployment with a SOAP binding, only IBM Web Service or Apache SOAP deployment versions are supported. Apache Axis is not supported.
  • XML Schema anyType data type is not supported. The XML Schema anyType data type is not supported by the Business Integration tools. It cannot appear in the schema types which are
    to be used within the tools. Should you use anyType, this problem surfaces itself as the compilation error "Unable to resolve the class org.w3.www._2001.XMLSchema.WSIFFormatPartImpl". A workaround for this is to use the IBM Web Services tools to provide the access to the web service.
  • In a synchronous process, the Web Services Invocation Framework (WSIF) Java provider does not support Duration or Timeout expressions for EJB or Java WSDL bindings. You can work around this in one of the two following ways:
    1. Use an asynchronous process.
    2. Specify the timeout as a WSIF property.
• Generated message driven beans sometimes had some irregularities caused by invoked methods. The problem has been resolved.
• A failure sometimes occurred while importing files needed to create a service. A correction has been made.
• The Client Web Services wizard has been corrected to allow users to select any client type. Previously, you could only select a web client for WebSphere Application Server v5.1 Enterprise Edition UTE.
• Helper classes that were generated for a SOAP service occasionally appeared to handle dateTime formats incorrectly. This error has been corrected.