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 xml that is defined in the jdbcasi.xsd schema definition, where
  • TableName identifies the database table associated with the business object,
  • StatusColumnName is the name of the database column used to perform logical delete operations, and
  • StatusValue is the value that signifies that a business object is inactive or deleted.
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:
  • To logically delete the child data, the adapter uses the value of its StatusColumnName parameter to obtain the name of the status column and the text of the status value. For more information, see "Update operations."
  • When performing a delete operation, the adapter uses the value of its StatusColumnName parameter to determine whether to physically or logically delete the entire business object. If the StatusColumnName parameter contains a value, the adapter performs a logical delete operation. If the StatusColumnName parameter does not contain a value, the adapter performs a physical delete operation. For more information, see "Delete operations."

Parameters of the ASI that are enabled for use with bidirectional languages are TableName and StatusColumnName. The format for these parameters are transformed based on the attributes set for the BiDi.Metadata property. For more information on this property, see Configuration properties.


Terms of use |

Last updated: Thu Mar 23 13:24:30 2006

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