Browse Prior Art Database

SDO-based Query Model for WebSphere Adapters

IP.com Disclosure Number: IPCOM000178020D
Original Publication Date: 2009-Jan-13
Included in the Prior Art Database: 2009-Jan-13
Document File: 8 page(s) / 114K

Publishing Venue

IBM

Abstract

Many WebSphere adapters, like their WBI counterparts, are required to support outbound retrieve operations against the target EIS based on user specified criteria that is semantically similar to a database SQL query. Given the variety of EIS integration interfaces that support this function, providing a common query model that fits all adapters has proven difficult. This invention provides a model for defining queries based on the common adapter data model, SDO.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 30% of the total text.

Page 1 of 8

SDO-based Query Model for WebSphere Adapters

Many WebSphere adapters, like their WBI counterparts, are required to support outbound retrieve operations against the target EIS based on user specified criteria that is semantically similar to a database SQL query. Given the variety of EIS integration interfaces that support this function, providing a common query model that fits all adapters has proven difficult. This invention provides a model for defining queries based on the common adapter data model, SDO.

Other solutions/ideas:

The query string approach, based on existing standards like SQL and XQuery: Pros:
standards based
could be used as a common interface for all adapters, as long as expressed in SDO terms, so all adapters can understand it
Cons:
no existing tooling to construct an SDO based query string; the closest would be the RAD SQL builder, but that goes against actual database tables, not SDOs requires each adapter whose EIS does not directly support that particular query format to parse the incoming string in order to retrieve the data necessary to execute the EIS query
Current solution(s) that use the query string approach are not generic; the query string is just a parameterized native EIS query, not built against data object definitions.

  WBI Adapters Retrieve support
The WBI adapters used Business Objects (BO) to specify criteria for Retrieve operations as well. However, the approach used significantly limited the functionality provided to, in most cases, a subset of EIS query capabilities.

This invention allows the definition of complex parameterized queries based on the adapter specific data objects representing the EIS entities to be queried / retrieved. Advantages:
uses the common adapter "language" for data representation - SDO - to define the queries; this makes the query easier to process than if it was represented as a string that needs to be parsed and evaluated
full build time tooling support through Enterprise Service Discovery (ESD) - all query elements are defined through ESD, no external prerequisite artifacts (such as the query string) required
support for complex query criteria, multiple cardinality operands such as parameters, multiple queries per EIS entity

The invention provides a model of defining and using parameterized SQL-like queries against EIS exposed entities.

Two scenarios are addressed:
Query is defined at design time and saved for runtime use.

Query is constructed on the fly, at runtime.

1

Page 2 of 8

Design Time Query Definition

The parameterized query is defined as a BO definition at design time, as part of the adapter ESD. Business objects are being generated during ESD that represent EIS data types (for example: a database table) that may be query targets. These will be called Data BOs. The query generation feature of ESD supports the definition of multiple query objects p...