Skip Headers

# Creating an EIS Interaction for a Named Query

Previous

Next

For an EIS root descriptor, you can define EIS interactions to invoke methods on an EIS.

You can use TopLink to define an interaction as a named query for read object and read all object queries, as described here. These queries are not called for basic persistence operations ("Configuring Custom EIS Interactions for Basic Persistence Operations"); you can call these additional queries by name in your application for special purposes.

Use this tab to define an interaction as a named query for read object and read all object queries.

Use the following information to complete each field on the tab:

Field | Description
--- | ---
Interaction Type | Using TopLink Workbench, you can only use XML Interactions. You cannot change this field.
Function Name | Specify the name of the EIS function that this call type (Read Object or Read All) invokes on the EIS.
Input Record Name | Specify the name passed to the J2C adapter when creating the input record.
Input Root Element | Specify the root element name to use for the input DOM.
Input Arguments | Specify 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 | Specify the result record field or XPath nodes to map 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 | Use this option if the EIS interaction result record contains the XML data that maps to the objects in a nested structure. For example, specify `order`, if the results were return under a root element `results`, then under an `order` element.
Properties | Specify any properties required by your EIS platform. For example, property name `operation` (from `AQPlatform.QUEUE_OPERATION`) and property value `enqueue` (from `AQPlatform.ENQUEUE`).