IBM Rational Application Developer Version 6.0.0.1 J2EE Connector Tools Feature - Release notes

© Copyright IBM Corporation 2000, 2005. All Rights Reserved.

Welcome to the IBM® Rational® Application Developer Version 6.0.0.1 J2EE Connector feature, powered by Eclipse technology release 3.0.1.

To view the latest version of this readme file, go to this Web address: www3.software.ibm.com/ibmdl/pub/software/rationalsdp/rad/6001/J2C/html/readme.html

This file is available in the following national languages:

French Brazilian Portuguese German
Simplified Chinese Italian Spanish
Japanese Traditional Chinese Korean

Table of contents

1.0 About this release
2.0 Installation information
2.1 Hardware requirements
2.2 Supported software
2.2.1 WebSphere® Application Server
2.2.2 Resource Adapters
2.2.3 IMS
3.0 Known limitations, problems, and workarounds
3.1 Limitations
3.1.1 IMSTM Connector for JavaTM TCP/IP and Local Option Connections
3.1.2 IMS Connector for Java MFS Support and the J2C Update to Rational Application Developer
3.1.3 Multiple Resource Adapters installed on the same runtime server instance
3.2 Known problems and workarounds
3.2.1 Deployment of J2C implementation bean as Session EJB, with data binding classes coming from utility jar
3.2.2 Deployment time exception
3.2.3 ConnectionSpec Changes cannot be done through J2C wizards
3.2.4 Undelivered output cannot be retrieved using IMS Connector for Java application
3.2.5 WebSphere Application Server for z/OS® servant region may restart if IMS Connector for Java executionTimeout property is "wait forever"
3.2.6 IMS Connector for Java properties purgeAsyncOutput and reRoute are ignored for dedicated persistent socket connections
4.0 Documentation updates
5.0 Contacting customer support
6.0 About Eclipse
7.0 Notices and trademarks

1.0 About this release

The J2EE Connector (J2C) Architecture tools allow you to create J2EE applications that integrate and extend operations and data on their existing Enterprise Information Systems (EIS).

Benefits of using the J2C tools to access EIS systems include:

Shorter development time
The J2C wizard creates code for the targeted EIS using the appropriate managed connection factory.
Standardization
Access your EIS through standards-compliant J2C infrastructure (for example, resource adapters and Common Client Interface).
Simplification
Quick and direct creation of Java beans. Each method corresponds to an EIS operation. With the created Java beans, you can take advantage of the rest of the Rational Application Developer capabilities to develop Web pages, Web services, and EJBs.

The J2C tools consist of the following major components:

Wizards
Java bean editing
Tutorials

Once you have installed the J2C feature, you can access the tutorials by clicking Help > Tutorials Gallery > Do and Learn from the main menu. Tutorials include:

For more information about the J2C tools, refer to the online help documentation by clicking Help > Help Contents then expanding Developing enterprise applications > Connecting to enterprise information systems.

2.0 Installation information

For information about installing the Rational Application Developer J2C feature, refer to www.software.ibm.com/ibmdl/pub/software/rationalsdp/rad/6001/install_instruction/ifeature_j2c/install_6001.html

2.1 Hardware requirements

Refer to the installation instructions for the hardware requirements for installing the Rational Application Developer J2C feature.

2.2 Supported software

If you develop an application using the J2C tools in Rational Application Developer and run it on WebSphere Application Server Version 5, ensure that you have the required maintenance applied to WebSphere Application Server Version 5. Refer to Section 2.2.1 WebSphere Application Server for details.

Refer to the installation instructions for more details on software and specifications that are supported by the Rational Application Developer J2C feature.

For details on software and specifications that are supported by a specific tool in Rational Application Developer, refer to the online help.

You must have IBM Rational Application Developer Version 6.0.0.1 installed before installing this feature.

2.2.1 WebSphere Application Server

WebSphere V5.0 and WebSphere V5.1 support J2C 1.0. The WebSphere Application Server service levels required to use the J2EE Connector Tools are listed in the table below. The Legacy Test Environments available with Rational Application Developer V6.0 require the service listed under WAS Distributed Service Level Required column in the table. WebSphere Application Server cumulative fixes, for example WAS 5.0.2.8, are available from the WebSphere Application Server support site (www.ibm.com/software/webservers/appserv/was/support). The Integration Edition RunTime Fixes for 5.0 and 5.1 are available from www.ibm.com/support/docview.wss?rs=180&context=SSEQTP&dc=D410&dc=D420&uid=swg24004796&loc=en_US&cs=utf-8&lang=en. WebSphere Application Server for z/OS PTFs are available from the WebSphere Application Server for z/OS support site /www.ibm.com/software/webservers/appserv/zos_os390/support/

WebSphere Application Server WAS Distributed Service Level Required WAS for z/OS Service Level Required
5.0.x
  • Cumulative Fix 5.0.2.8
  • Integration Edition RunTime Fixes for 5.0
W502023 (PTF UK00329)
5.1.x
Integration Edition RunTime Fixes for 5.1
W510205 (PTF UK0028)

WebSphere V6 supports J2C 1.5 applications.

2.2.2 Resource Adapters

The following resource adapters are supported in the J2C Tools:

2.2.3 IMS

The following classes are deprecated in IMS Connector for Java Version 9.1.0.1.1 and IMS Connector for Java Version 9.1.0.2:

3.0 Known limitations, problems, and workarounds

Release notes cover release-specific information (such as problems and limitations) that did not become available until after the product documentation was finalized.

For information about known problems and workarounds in the Eclipse base, refer to readme_eclipse.html located in the eclipse\readme subdirectory of the product installation directory. This information is only available in English.

3.1 Limitations

3.1.1 IMS Connector for Java TCP/IP and Local Option Connections
3.1.2 IMS Connector for Java MFS Support and the J2C Update to Rational Application Developer
3.1.3 Multiple Resource Adapters installed on the same runtime server instance

3.1.1 IMS Connector for Java TCP/IP and Local Option Connections
3.1.2 IMS Connector for Java MFS Support and the J2C Update to Rational Application Developer
The J2C tools provided with Rational Application Developer currently do not include wizards to generate Java data bindings from MFS source. However, enterprise applications created from MFS source using WebSphere Studio Application Developer Integration Edition can still be run on WebSphere Application Server V6. For information on how to do this, refer to the technote entitled "Migrating MFS-based IMS applications to run on WebSphere Application Server 6.0" on the IMS MFS Web Support page (www.ibm.com/software/data/ims/toolkit/mfswebsupport/)
3.1.3 Multiple Resource Adapters installed on the same runtime server instance
Multiple standalone versions of the same EIS resource adapter should not be installed in WAS, especially if they are for the same EIS type. For example, if you install both a CICS ECI 5.1 and CICS ECI 6.0, there may be a conflict. This is because all standalone resource adapters share the same class loader.

3.2 Known problems and workarounds

3.2.1 Deployment of J2C implementation bean as Session EJB, with data binding classes coming from utility jar
3.2.2 Deployment time exception
3.2.3 ConnectionSpec Changes cannot be done through J2C wizards
3.2.4 Undelivered output cannot be retrieved using IMS Connector for Java application
3.2.5 WebSphere Application Server for z/OS servant region may restart if IMS Connector for Java executionTimeout property is "wait forever"
3.2.6 IMS Connector for Java properties purgeAsyncOutput and reRoute are ignored for dedicated persistent socket connections


3.2.1 Deployment of J2C implementation bean as Session EJB, with data binding classes coming from utility jar
When a J2C implementation bean, generated using the J2C Tools, uses data binding types that reside in separate Java Projects in the workspace (which is equivalent to runtime dependency on EAR scoped utility JAR), the MANIFEST.MF file for the EJB project is not automatically updated to reflect such dependency. To avoid runtime errors, users should manually update "Class-Path" attribute in META-INF/MANIFEST.MF file of the EJB project to include EAR scoped utility JARs where data binding types are located. This should be done before the EJB project is deployed to the runtime server.
3.2.2 Deployment time exception
During the creation of Web pages, EJBs or Web Services, you may notice an exception in the WAS V6 server console. This does not affect normal operation of the server or J2C bean. This problem has been fixed in WebSphere Application Server version 6.0.1 available from www.ibm.com/software/webservers/appserv/was/support/

[2/21/05 18:55:49:781 EST] 00000017 SystemErr R java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.ibm.ws.ffdc.DiagnosticModule.getDataForDirective(DiagnosticModule.java:316) at com.ibm.ws.ffdc.DiagnosticModule.getDataForDirectives(DiagnosticModule.java:287) at com.ibm.ws.ffdc.DiagnosticModule.dumpComponentData(DiagnosticModule.java:143) at com.ibm.ws.ffdc.DiagnosticEngine.processIncident(DiagnosticEngine.java:159) at com.ibm.ws.ffdc.FFDCFilter.filterEngine(FFDCFilter.java:434) at com.ibm.ws.ffdc.FFDCFilter.processException(FFDCFilter.java:195) at com.ibm.ws.management.AdminServiceImpl.outputWarningAndFFDC(AdminServiceImpl.java:1660) at com.ibm.ws.management.AdminServiceImpl.checkForOpDeprecation(AdminServiceImpl.java:1737) at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:1670) at com.ibm.ws.management.AdminServiceImpl.access$400(AdminServiceImpl.java:100) at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:899) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:817) at com.ibm.ws.management.connector.AdminServiceDelegator.invoke(AdminServiceDelegator.java:139) at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.ibm.ws.management.connector.soap.SOAPConnector.invoke(SOAPConnector.java:325) at com.ibm.ws.management.connector.soap.SOAPConnector.service(SOAPConnector.java:193) at com.ibm.ws.management.connector.soap.SOAPConnection.handleRequest(SOAPConnection.java:55) at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:641) at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:469) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code)) Caused by: java.lang.NullPointerException at com.ibm.ws.management.dm.JmxDM.processAdminService(JmxDM.java:50) at com.ibm.ws.management.dm.JmxDM.ffdcDumpDefaultJmx(JmxDM.java:34) ... 28 more


3.2.3 ConnectionSpec Changes cannot be done through J2C wizards
The J2C Wizard does not provide any UI support for users to make changes to ConnectionSpec. Users have to change it directly in the generated implementation Java code. What they need to do is to open up the generated implementation Java file in an editor, navigate to the method that they need to modify and then change/add/remove the doclets for that method.
3.2.4 Undelivered output cannot be retrieved using IMS Connector for Java application
In order to allow retrieval of undelivered output on shareable persistent socket connections using SYNC_RECEIVE_ASYNCOUTPUT interactions in the same application, IMS Connector for Java allows a value of FALSE for both the purgeAsyncOutput property and the reRoute property of IMSInteractionSpec. If, however, the SYNC_RECEIVE_ASYNCOUTPUT interaction does not successfully retrieve the output in the application that queued the output, the undelivered output will remain queued on the OTMA TPIPE whose name is that of the shareable persistent socket connection. This output cannot be retrieved using an IMS Connector for Java application, hence care must be used when setting both purgeAsyncOutput and reRoute to FALSE.
3.2.5 WebSphere Application Server for z/OS servant region may restart if IMS Connector for Java executionTimeout property is "wait forever"
In WebSphere Application Server for z/OS application work dispatched into servant regions, is, by default, timed. In general, when an application in dispatch reaches its timeout, the servant region where it is dispatched is abended and then restarted. For this reason, it is strongly recommended that you do not use the value -1 ("wait forever") for executionTimeout when your application is running in WebSphere Application Server for z/OS.
3.2.6 IMS Connector for Java properties purgeAsyncOutput and reRoute are ignored for dedicated persistent socket connections
The IMSInteractionSpec properties purgeAsyncOutput and reRoute are not applicable for interactions on dedicated persistent socket connections. You cannot purge or reroute undelivered output messages on a dedicated persistent socket connection. If, however, you perform an interaction on a dedicated persistent socket connection and provide values for purgeAsyncOutput and reRoute, the values will be ignored by IMS Connector for Java. Your Java application will not receive an exception.

4.0 Documentation updates

Both the product home page and IBM developerWorks have Library sections that provide updates to tutorial documents and other documentation.

The IBM Rational  zone at www.ibm.com/developerworks/rational offers technical articles, "how to" information, tutorials, samples, and previews of new technology.

5.0 Contacting customer support

The product home page for Rational Application Developer is www.ibm.com/software/awdtools/developer/application/index.html. For FAQs, lists of known problems and fixes, and other support information, visit the Support page on the product home page.

6.0 About Eclipse

Eclipse is an open-source project that delivers a framework for developing plug-ins that make it easier to create, integrate, and use software tools. By collaborating and sharing core integration technology, tool producers can concentrate on their areas of expertise and the creation of new development technology. The Eclipse platform is written in the Java language and comes with extensive toolkits and examples for construction plug-ins. It has already been deployed on a range of operating system environments including Linux®, Mac OS X, QNX, and Windows®-based systems. Full details of the Eclipse community and white papers documenting the design of the Eclipse platform are available at www.eclipse.org.

Plug-in tools from other vendors, also built using the open-source Eclipse platform, integrate with the Rational Developer environment to provide additional value.

7.0 Notices and trademarks

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this documentation in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this documentation. The furnishing of this documentation does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Intellectual Property Dept. for Rational Software
IBM Corporation
3600 Steeles Avenue East
Markham, Ontario
Canada L3R 9Z7

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this documentation and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples may include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. 2000, 2005. All rights reserved.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Programming interface information

Programming interface information is intended to help you create application software using this program.

General-use programming interfaces allow you to write application software that obtain the services of this program's tools.

However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.

Trademarks and service marks

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product or service names, may trademarks or service marks of others.