WebSphere Adapter for JDBC

Application-specific information at the business-object level

Application-specific information at the business object level is used to specify the name of the corresponding database table and to provide information necessary to perform a physical or logical Delete operation.

At the business object level, application-specific information format consists of eXtensible Markup Language (XML) code that is defined in the jdbcasi.xsd schema definition. The adapter supports the business object level application-specific information listed in the following table.

Table 1. Business object level application-specific information
Application-specific information Type Description Bidirectional transformation supported
MaxNumberOfRetRS String The number of result sets that the stored procedure returns No
ResultSet Boolean The value that indicates whether the stored procedure will return a result set No
ReturnValue String The name of the corresponding attribute in the stored function business object No
SelectStatement String The select statement Yes
SPName String The name of the stored procedure Yes
StatusColumnName String The name of the database column used to perform logical Delete operations Yes
StatusValue String The value that signifies whether a business object is inactive or deleted No
TableName String The name of the database table associated with the business object Yes
For example, assume that a Customer business object has the following value specified for its business object application-specific information:
<jdbcasi:TableName>customer</jdbcasi:TableName>
<jdbcasi:StatusColumnName>status</jdbcasi:StatusColumnName>
<jdbcasi::StatusValue>deleted</jdbcasi:StatusValue>
Assume that the adapter receives a request to delete a customer. Such a request causes the adapter to issue the following SQL statement:
UPDATE customer set status = ’deleted’ where pkey = . . . .

If the StatusColumnName is not included or no value is specified for it, the adapter physically deletes the business object from the database. In other words, if the business object includes the StatusColumnName parameter in its application-specific information, the adapter performs a logical delete operation. If the business object does not include the StatusColumnName parameter in its application-specific information, the adapter performs a physical delete operation.

Both Update and Delete operations can use the value of the StatusColumnName property:

Parameters of the application-specific information that are enabled for use with bidirectional languages are TableName, StatusColumnName, SPName and SelectStatement. The format for these parameters is transformed based on the attributes set for the BiDiEIS, BiDiMetadata, BiDiSkip, and BiDiSpecialFormat properties. For more information on these properties, see Adapter configuration properties.


Terms of use |

Last updated: Tue 12 Dec 2006 03:32:38

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)