J2EE connector (J2C) tools Release Notes

© 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.

Release notes

1.0 Limitations
   1.1 The J2EE connector (J2C) tools support a limited versions of resource adapters
   1.2 PL/I importer is not supported on Linux
   1.3 Limitation for having multiple adapters on the same runtime server
2.0 Known problems and workarounds
   2.1 Error message pops up when selecting display entry in migration summary page
   2.2 Limitation for Web Service deployment option in J2C wizards
   2.3 PL1_TO_Java/MPO_PL1_Mapping shows up on Linux
   2.4 Migrating J2C V6013 ant script to J2C ant script in Version 7.0

1.0 Limitations

1.1 The J2EE connector (J2C) tools support a limited versions of resource adapters

These are the current supported Resource adapters:
JCA 1.0                       JCA 1.5                      
IMSICO91014.rar IMSICO91023.rar      
IMSICO91013a.rar   IMSICO91022a.rar    
IMSICO91013.rar        IMSICO91022.rar      
IMSICO91012.rar       IMSICO91021.rar       
IMSICO91011.rar       IMSICO9102.rar      
ECIResourceAdapter 5.1.0.1                  ECIResourceAdapter 6.0.1                          
ECIResourceAdapter 5.0.1                 ECIResourceAdapter 6.0.2
  ECIResourceAdapter 6.0

 The CICS® Transaction Gateway version that is currently supported is V6.0.2.

For the support software for CICS Transaction Gateway, please refer to

 http://www-1.ibm.com/support/docview.wss?uid=swg21239203

1.2 PL/I importer is not supported on Linux®

 PL/I importer is not supported on Linux platform.

1.3 Limitation for having multiple adapters on the same runtime server

Multiple resource adapters should not be installed standalone in WebSphere® Application Server, especially if they are for the same EIS type (For example, CICS ECI 5.1 and CICS ECI 6.0). This is because all standalone resource adapters share the same class loader. 

2.0 Known problems and workarounds

2.1 Error message pops up when selecting display entry in migration summary page

An error message will display when you click on the J2C migration summary page after you migrate your Service WSDL file using the J2C migration wizard.

Workaround: Do not click on the migration summary page after you migrate your service WSDL file using the J2C Migration wizard. You can save it into a file if you want further reference.

2.2 Limitation for Web Service deployment option in J2C wizards

For the Web Service deployment option in the J2C Wizard, if you do not start the target server, the port specified for the Web Service endpoint address may not be determined correctly.

Workaround: Start the target server for the Web Project where you plan to generate the Web Service from J2C Java bean before performing the generation step. Although it is not required for actual generation, if the target server is not started, the port specified for Web Service endpoint address may not be determined correctly. If you choose not to start the server, make sure you verify that the endpoint port specified in the generated Web Service WSDL file corresponds to the correct port on the WebSphere server, before deploying the Web Service to the server.

2.3 PL1_TO_Java/MPO_PL1_Mapping shows up on Linux

The PL/I Importer features is not supported on Linux®.

However if you go through the J2C wizards, you will still see PL1_TO_Java/MPO_PL1_Mapping on the importer page.

If you select them, you will get a NULL Pointer Exception.

Workaround: Just ignore the options and do not select them on Linux platform.

2.4 Migrating J2C V6013 ant script to J2C ant script in Version 7.0

If you have used J2C V6013 ant scripts and want to migrate your J2C ant scripts to J2C ant script in Version 7.0 of the product, this will be applicable to you.

The following is the interface binding section of the J2C Ant script where <input> is used. There is a name collision between the J2C ant task <input> in the following script and the default Ant task <input>:

         <createBinding package="com.ibm.test" class="Taderc99Interface">
              <methodElement>
                  <name value="gettaderc99"/>
                  <input value="\${project}\com\ibm\test\Taderc99.java"/>
                  <output value="\${project}\com\ibm\test\Taderc99.java"/>
                  <interactionSpec>
                      <propertyElement name="functionName" value="TADERC99"/>
                  </interactionSpec>
               </methodElement>
               <connectionSpec>
                     <propertyElement name="ServerName" value="rubicon"/>
                     <propertyElement name="ConnectionURL" value="rubicon.torolab.ibm.com"/>
                     <propertyElement name="UserName" value="sysad"/>
                     <propertyElement name="Password" value="sysad"/>
                     </connectionSpec>
               <resourceAdapter project="CICS ECI"/>
         </createBinding>

The J2C ant task <input> script overwrites the default ant task. The default Ant task cannot be executed.

In J2C V6013, a fix is provided to solve the name collision. The J2C <input> task in the above script is changed to <j2cinput> for both to function correctly.

Since the J2C Ant scripts in Version 7.0 of the product have a new layout, a migration tool has been provided. The above name change will affect the migration tool that does not recognize the <j2cinput> name. To correctly migrate the J2C Ant scripts from Version 6.0.x of the product to the new layout recognized in Version 7.0, the <j2cinput> task name must be changed back to <input>.