Configuring Delete All Interactions

The TopLink query and expression framework supports delete all queries. If your J2C adapter provides access to an EIS Delete All function, you can configure a delete all interaction to support TopLink delete all queries.

Using TopLink Workbench

To specify the DeleteAll interaction for an EIS one-to-many mapping, use this procedure:

1. Select the mapped attribute in the Navigator. Its properties appear in the Editor.

2. Click the Delete All Interaction tab. The Delete All Interaction tab appears.

   Figure 63-1 Delete All Interaction Tab

   
   Description of "Figure 63-1 Delete All Interaction Tab"
   
   

Use the following information to enter data in each field on the Delete All Interaction tab:

Field	Description
Function Name	The name of the EIS function that this call type (Read Object or Read All) invokes on the EIS.
Input Record Name	The name passed to the J2C adapter when creating the input record.
Input Root Element Name	The root element name to use for the input DOM.
Input Arguments	The query argument name to map to the interaction field or XPath nodes in the argument record. For example, if you are using XML records, use this option to map input argument name to the XPath name/first-name.
Output Arguments	The result record field or XPath nodes to map to the correct nodes in the record used by the descriptor's mappings. For example, if you are using XML records, use this option to map the output fname to name/first-name. Output arguments are not required if the interaction returns an XML result that matches the descriptor's mappings.
Input Result Path	Use this option if the EIS interaction expects the interaction arguments to be nested in the XML record. For example, specify arguments, if the arguments were to be nested under the root element exec-find-order, then under an arguments element.
Output Result Path	The name of the EIS function that this call type (Read Object or Read All) invokes on the EIS.
Properties	Any properties required by your EIS platform. For example, property name operation (from AQPlatform.QUEUE_OPERATION) and property value enqueue (from AQPlatform.ENQUEUE).