Query Execution during Runtime
To enable the execution of queries during runtime, the connector developer has three options:
...
1. Build query as hierarchical tree structure
2. Use free text
3. Enable use of EIS native queries and/or functions directly in back-end application

The following options are among the capabilities encapsulated by the connector framework ICapabilities interface.
Interface IOperation is the base interface for encapsulating the data and metadata required from performing an operation at the back end. Typically, for building queries using automatic tools (such as a wizard), the package com.sapportals.connector.execution.objects.language is used to define the query tree, or hierarchy.
The creator of the connector supplies the implementation that assembles the query (represented by IOperation as a tree) into a language that the back end understands. For this IExecution must be implemented.
INativeQuery, enables the free-text input of queries. The difference between this option and option 1, is that option 1 returns output objects that implement the connector framework structure package connector.execution.structure, while option 2 returns back-end native objects (for example, the JDBC connector returns java.sql.resultset).

The information here applies function as well as query execution.
INative is returned by IConnection, which is the entry point for all available types of connections. INative returns a physical connection to the EIS.
● For some business users it may be preferable to work directly in the back-end application.
● Using INative enables the re-use of existing code, already interacting with the back-end native interfaces.
Misuse of may interfere with connection pool management of the Web Application Server (WAS). For specific information about this, refer to SAP Note 720995.