 | IMS TM Resource Adapter 
|
The IMS TM resource adapter, previously known as IMS Connector for Java, is part of the IMS SOA Integration Suite of middleware functions and tools. The IMS TM resource adapter enables you to quickly and easily create Java applications that access new and existing IMS transactions over the Internet. Using the IMS TM resource adapter within a WebSphere® or Rational-family development environment, you can: - Develop components of business processes in support of Service Oriented Architecture
- Create Java EE (or J2EE) applications from Java beans
- Develop service-based applications
The development version of the IMS TM resource adapter is included in the following integrated development environments: - Rational Application Developer for WebSphere Software
- WebSphere Integration Developer
- WebSphere Transformation Extender
- Rational Developer for System z (formerly known as WebSphere Developer for System z)
- Rational Software Architect
You can download the runtime of the IMS TM resource adapter from this website. The runtimes of the IMS TM resource adapter are also available via APARs.
|
|
- Based on Sun's J2EE Connector Architecture (JCA) 1.5 for the IMS TM resource adapter (Version 10 and Version 9.1.0.2.x), and JCA 1.0 (version V9.1.0.1.x and V2.2.x)
- Leverages existing IMS assets in service-oriented architecture (SOA)
- Supports development of applications that can submit transactions to IMS Transaction Manager through IMS Connect
- Provides tooling support for development of Java EE applications, Web services, and business processes that access IMS transactions in various Rational and WebSphere integrated development environments
- Provides a JCA Resource Adapter (RAR) for deployment to the WebSphere Application Server and WebSphere Process Server (WPS) runtime environment on many platforms including z/OS and Linux on System z
- Supports connection pooling and reuse
- Supports global transaction processing (two-phase commit)
- Supports component-managed and container-managed security, including support for run-as thread identity
- Supports SSL communication between the IMS TM resource adapter and IMS Connect, including support for SSL null encryption
- Supports most types of interactions with IMS application programs including the retrieval of asynchronous output messages
- Supports for IMS applications to invoke Java EE applications asynchronously (Callout)
|
|
Runtimes for Version 10 and Versions 9 of the IMS TM resource adapter are available for download from this Web site. The following table shows runtime versions and updates to the corresponding development environments. | JCA 1.5 IMS TM
Resource Adapter | JCA 1.0 IMS TM
Resource Adapter |
|---|
Rational Application Developer
(RAD) 7.0.0.x | *V10.2
V9.1.0.2.5a | V9.1.0.1.5b |
|---|
WebSphere Integration Developer
(WID) Version 6.1 | *V10.2
V9.1.0.2.5a | V2.2.5a
V9.1.0.1.5b |
|---|
WebSphere Integration Developer
Version 6.0.1 | V9.1.0.2.2d | V2.2.5a
V9.1.0.1.3b |
|---|
WebSphere Transformation Extender
(WTX) Version 8.2.0.2 or later | *V10.2 | |
|---|
J2EE Connector Tools Feature for IBM
Rational Application Developer Version
6.0.1.x | V9.1.0.2.2d | V9.1.0.1.3b |
|---|
WebSphere Studio Application
Developer Integration Edition Version
5.1.1 - Cumulative Fix 011 J2EE
Connector Tools | | V2.2.5a |
|---|
* For V10, you need to import the RAR into your J2C project manually. Rational Application Developer V7.0.0.4 is required. To use the new functionality, you might need to have the appropriate APARs applied to both IMS Connect and IMS. See the readme.html included in the IMS TM resource adapter download for more information.
|
|
 | Recommendations for Socket Connections Currently, the IMS TM resource adapter only supports persistent socket connections to IMS Connect. In a managed environment, persistent socket connections are serially reused by application components, without the overhead of disconnecting and reconnecting the socket between each use. Application components can choose to use either dedicated or shareable persistent socket connections between the IMS TM resource adapter and IMS Connect. Typically, a dedicated persistent socket connection is serially reused by a single application. However, a dedicated persistent socket connection can be serially reused by multiple applications that obtain the socket using the same client ID. If different applications attempt to use a dedicated persistent socket connection using the same clientID at the same time, the first attempt will succeed and any subsequent attempt(s) will receive a duplicate client error (DUPCLNT). The duplicate client error will also occur when an application that obtains a dedicated persistent socket connection using a given clientID runs in an environment where the dedicated persistent socket connection can originate from multiple WebSphere Application Server instances. For these reasons, it is strongly recommended that your application not be deployed to this type of environment. An example of an environment that can lead to duplicate client errors would be multiple WebSphere Application Server instances managed by a workload manager. For more information please refer to IMS TM Resource Adapter documentation. |
|
|
Current Releases
The IMS TM resource adapter implements Sun's J2EE Connector Architecture (JCA) and supports both Version 1.0 and 1.5 of the J2EE Connector Architecture. The Version 9.1.0.1.x and 2.2.x adapters are based on JCA Version 1.0 and the Version 10 and Version 9.1.0.2.x adapters are based on Version 1.5 of JCA. The version of the IMS TM resource adapter that you use depends on which J2EE Connector Architecture version you need to use for your application. IBM recommends that you use the latest version of the JCA specification for your applications whenever possible because it will always contain the most recent updates and the richest feature set. Maintenance-only Releases
In addition to the current releases listed above, IBM provides maintenance-only releases for customers using previous versions or down level releases of the supported development environments and application servers such as WebSphere Studio Application Developer Integration Edition 5.1.1 used with WebSphere Application Server 5.1.1 and Rational Application Developer 6.0. These products will be updated from time to time with critical maintenance updates but will not have any new function added to them.
* IBM is discontinuing service for IMS Connector for Java Version 2.2 on November 5, 2008 (see announcement letter 907-162).
|
|
IBM recommends using the latest version of the IMS TM resource adapter. If you need a previous version of the IMS TM resource adapter, contact your IBM service representative.
|
|
The IMS TM resource adapter uses IMS Connect which is provided as the integrated IMS Connect function of IMS Version 10 and Version 9. For more information about IMS Connect, see the IMS Connect Web site. Application Development Environment - Runtime Environment| IDE | IMS TM Resource Adapter Version | Target IMS Connect Version | Target IMS Version | Target Application Server Version | Remarks |
|---|
| WID V6 | 10 | V10, V9, V2.2* | V10 | WPS V6 | - Uses SCA/SDO programming model |
|---|
| V10, V9 | V9 | | V10, V2.2* | V8 | 9.1.0.2.x | V9.1 | V9 | | WTX V8 - Design Studio(V8.2.0.2 or later) | 10 | V10 | V10 | WTX V8.2.0.2 or later | -Uses WTX programming model |
|---|
| RAD V7 | 10
(RAD V7.0.0.4 or later required) | V10, V9, V2.2* | V10 | WAS 6.0.2
WAS 6.1 | - Use J2C Java bean programming model |
|---|
| V10, V9 | V9 | | V10, V2.2* | V8 | 9.1.0.2.x
9.1.0.1.x | V9.1 | V9 | | RAD V6 | 9.1.0.2.x | V9.1 | V9 | WAS V6 | - Use J2C Java bean programming model |
|---|
| 9.1.0.1.x | V9.1 | V9, V8 | WAS V6
WAS V5.1** | | V2.2* | V9, V8 | WAS V6
WAS V5.1** | | WSADIE 5.1.1 | 9.1.0.1.x | V9.1 | V9, V8 | WBI-SF 5.1.0
WAS-E 5.1**
WAS V5.1 for z/OS** | - Use Enterprise Service / WSIF programming model
- Include MFS support |
|---|
| V2.2* | V9, V8 | WBI-SF 5.1.0
WAS-E 5.1**
WAS V5.1 for z/OS** | | 2.2.x* | V9.1 | V9, V8 | WBI-SF 5.1.0
WAS-E 5.1**
WAS V5.1 for z/OS** | | V2.2* | V9, V8 | WBI-SF 5.1.0
WAS-E 5.1**
WAS V5.1 for z/OS** | | WSADIE 5.1 | 2.2.1* | V2.2* | V9, V8 | WBI-SF 5.1.0
WAS-E 5.1**
WAS V5.1 for z/OS** |
|---|
* IBM is discontinuing service for IMS Connect Version 2.2, including IMS Connector for Java Version 2.2, on November 5, 2008 (see announcement letter 907-162). ** IBM is discontinuing service for Version 5.1 of WebSphere Application Server for both distributed and z/OS platforms in September 2008. See the WebSphere product lifecycle page for the dates.
Note - WID includes RAD. Applications developed with WID run only on WebSphere Process Server (WPS). The target application server versions for applications developed using RAD in WID are the same as those listed for RAD.
- WTX includes RAD.
- The target application server versions for RAD apply to both distributed and z/OS platforms
- Applications developed with a given level of WID, RAD, or WSADIE are supported for deployment on the target application server version and later versions.
- RAD only targets base WAS as a server platform. However, because WebSphere Application Server Enterprise (WAS-E), WebSphere Business Integration Server Foundation (WBI-SF) and WPS are supersets of base WAS, applications that run on base WAS should also run on WAS-E, WBI-SF and WPS.
- Listed versions of the IMS TM resource adapter are supported with listed or later versions of IMS Connect and WAS.
|
|
Runtime same as the target WebSphere application server where the IMS TM resource adapter is deployed.
|
| |
|
