To retrieve and update data, you employ JCA's CCI layer, a procedure resembling using JDBC to call stored procedures. A JCA resource adapter is not required to support the CCI layer (the resource adapter creators can choose their own API set), and, even if the resource adapter does support CCI, it may also support an API specific for that particular adapter.

The CCI APIs can be divided into four sections: First, the APIs related to ESTABLISHING a connection to an EIS, also referred to as the Connection Interfaces. The second area of the CCI APIs cover command execution on an EIS, referred to as theInteraction Interfaces. Third is the Record/ResultSet Interfaces,which encapsulate the query results to an EIS. The fourth area, referred to as the Metadata Interfaces, allows EIS's metadata (the type of data) to be queried.

After this brief overview of the CCI APIs, it is useful to look at an example that shows the query of an employee count from an EIS:

intcount; 
try
{ 
ConnectionSpec spec =newCciConnectionSpec(user, PASSWORD);
Connection con = cf.getConnection(spec);
Interaction ix = con.createInteraction(); 
CciInteractionSpec iSpec = new CciInteractionSpec();
iSpec.setSchema(user); iSpec.setFunctionName("EMPLOYEECOUNT");
RecordFactory RF =cf.getRecordFactory(); 
IndexedRecord iRec =rf.createIndexedRecord("InputRecord"); 
Record rec =ix.execute(iSpec, iRec); 
Iterator iter =((IndexedRecord)rec).iterator();
while(iter.hasNext())
{ 
Object obj = iter.next();
if(obj instanceof Integer)
{ 
count = ((Integer)obj).intValue();
} 
} 
con.close(); 
} 
catch(Exception E) 
{ 
e.printStackTrace(); 
}
System.out.println("Employee count is: " + count);...

To retrieve and update data, you employ JCA's CCI layer, a procedure resembling using JDBC to call stored procedures. A JCA resource adapter is not required to support the CCI layer (the resource adapter creators can choose their own API set), and, even if the resource adapter does support CCI, it may also support an API specific for that particular adapter.

The CCI APIs can be divided into four sections: First, the APIs related to establishing a connection to an EIS, also referred to as the Connection Interfaces. The second area of the CCI APIs cover command execution on an EIS, referred to as theInteraction Interfaces. Third is the Record/ResultSet Interfaces,which encapsulate the query results to an EIS. The fourth area, referred to as the Metadata Interfaces, allows EIS's metadata (the type of data) to be queried.

After this brief overview of the CCI APIs, it is useful to look at an example that shows the query of an employee count from an EIS:

intcount; 
try
{ 
ConnectionSpec spec =newCciConnectionSpec(user, password);
Connection con = cf.getConnection(spec);
Interaction ix = con.createInteraction(); 
CciInteractionSpec iSpec = new CciInteractionSpec();
iSpec.setSchema(user); iSpec.setFunctionName("EMPLOYEECOUNT");
RecordFactory rf =cf.getRecordFactory(); 
IndexedRecord iRec =rf.createIndexedRecord("InputRecord"); 
Record rec =ix.execute(iSpec, iRec); 
Iterator iter =((IndexedRecord)rec).iterator();
while(iter.hasNext())
{ 
Object obj = iter.next();
if(obj instanceof Integer)
{ 
count = ((Integer)obj).intValue();
} 
} 
con.close(); 
} 
catch(Exception e) 
{ 
e.printStackTrace(); 
}
System.out.println("Employee count is: " + count);...