Legacy connectivity refers to how Java components interact with a legacy system.
Typical properties of a legacy system are :
• developed in another programming language
• runs in an environment that doesn’t support Java
• limited connectivity – e.g. a mainframe that only supports physical connections
Generally, components can interact with software/services on a legacy system in the following ways :
• in-process – e.g. independent software processes collaborating
• out-of-process (physical connection) – e.g. serial IO over local cable / leased-line
• out-of-process (virtual connection) – e.g. over the network; serial IO over dialup; etc.
• out-of-process (broker) – e.g. via a middle-man such as an ORB, MQ, etc.
The JCA comprises a resource adapter, connection management contracts, a transaction management contract, a security contract, and the CCI.
A JCA adapter interacts with a J2EE server via system contracts. Three types of system contracts can be used: