Reference

The following is an example application working with the JDBC-specific implementation of a Database Table Mapping service and the XML files needed to run it. As shown in the example, the reuse of the application code with a different implementation of a table service depends on reference to the TableService interface instead of explicitly use using the JDBCTable object implementing this interface. This example is implemented for a local environment, but you can easily adapt it to a client/server environment by implementing a toolkit client operation. The client operation should start the server operation that calls for the table services. In this example, the application requests the connection to be automatically set by the service, and also lets the service commit and roll back the database changes automatically. It is assumed that the appropriate JDBC driver is loaded.

<kColl id="myTableOperationData"/>
  <field id="ACCOUNT_NUMBER"/>
  <field id="AMOUNT"/>
  <field id="THE_DATE"/>
  <field id="DESCRIPTION"/>
  <field id="RECID"/>
</kColl>

<context id="myTableOperationContext" type="op" >
<refKColl refId="myTableOperationData">
</refKColl>
</context>

<JDBCTable id="myTableName" autoCommit="true"
autoConnect="true"
  databaseURL="jdbc:db2://myhostname:8888/mydatabasename"
  user="myuser" password="mypassword"
  table="DatabaseTable">
</JDBCTable>

<fmtDef id="tableFormatName">
  <hashtable>
    <fObject dataName="ACCOUNT_NUMBER"/>
    <fObject dataName="AMOUNT"/>
    <fObject dataName="THE_DATE"/>
    <fObject dataName="DESCRIPTION"/>
    <fObject dataName="RECID"/>
  </hashtable>
</fmtDef>

RECID INTEGER
ACCOUNT_NUMBER CHAR(14)
AMOUNT INTEGER
DESCRIPTION VARCHAR(50)
THE_DATE DATE

public static void main(String args[]) throws java.io.IOException,
DSEObjectNotFoundException {
Context tableContext;
HashtableFormat tableFormat= null;
// Initializing toolkit for Java
if(!InitManager.isInitialized()){
InitManager.reset("file:///c:\\btt\\btt.xml");
}
// Working with the table service
TableService table = null;
try {
TableContext=ContextFactory.createContext("myTableOperationContext");
System.out.println(">>> Creating a Table Service Instance...");
table = (TableService)Service.readObject("myTableName");
// Because of the service definition, no connection to the database
// is explicitly done
int nbrOfRecords = 3;
Trace.trace(Trace.Information, ">>> Filling the Table with " + nbrOfRecords
+ " records...");
for (int i = 1; i <= nbrOfRecords ; i++) {
tableContext.setValueAt("ACCOUNT_NUMBER", "0007000" + i);
tableContext.setValueAt("AMOUNT",new Integer(200000 + i));
tableContext.setValueAt("THE_DATE", new java.sql.Date(98,4,16));
tableContext.setValueAt("DESCRIPTION", "Adding record " + i + " in table...");
tableContext.setValueAt("RECID",new Integer(i));
tableFormat= (HashtableFormat)FormatElement.readObject("tableFormatName");
// Call the format method with argument the operation context
Hashtable dataTable1 = new Hashtable();
dataTable1 = (Hashtable) tableFormat.format(tableContext);
Trace.trace(Trace.Information, ">>> Adding a record to the database table...");
table.addRecord(dataTable1);
} // End for
// Display Table content
Vector aDataVector = null;
Hashtable aDataHashtable = new Hashtable();
aDataVector= table.retrieveRecordsMatching("THE_DATE=DATE('1998-05-16')");
Enumeration aDataVectorEnum = aDataVector.elements();
while (aDataVectorEnum.hasMoreElements()) {
tableFormat.unformat((Hashtable)aDataVectorEnum.nextElement(), tableContext);
System.out.println("Record retrieved with identification:" +
tableContext.getValueAt("RECID"));
} // End while
// Delete record number 1
table.deleteRecordsMatching("RECID=1");
// Retrieving data of 2st record;
aDataVector = table.retrieveRecordsMatching("RECID=2");
if ( !aDataVector.isEmpty()) {
aDataVectorEnum = aDataVector.elements();
TableFormat.unformat((Hashtable)aDataVectorEnum.nextElement(), tableContext);
System.out.println("Record retrieved with identification:" +
tableContext.getValueAt("RECID"));
}
else {
System.out.println("No records found for this search criteria");
}
tableContext.setValueAt("DESCRIPTION", "Updated description");
// Updating last Record in the database
table.updateRecordsMatching("RECID=(SELECT MAX(RECID)
FROM"+table.getTableName()+")",tableContext,"tableFormatName");
} // End try
catch (Exception e ) {
System.out.println(e.getMessage());
try {
table.disconnect(); }
catch (Exception ex){
System.out.println(ex.getMessage());}
return;
}
}

The DataSource object name to be used by all requests to get a connection. This should be specified when working with the connection pooling provided by WebSphere Application Server or with any other JDBC implementation of the connection pooling. This name requires a context part and a logical name part, since it will be used to do a lookup in the naming context. A typical string might look something like "jdbc/sample," where the context is "jdbc" and the logical name is "sample." This information can be supplied by the WebSphere Application Server administrator, and it identifies the DataSource object placed in the naming service.