Oracle Application Server InterConnect Adapter for J.D. Edwards OneWorld XE Installation and User's Guide 10g (9.0.4) Part Number B10418-01 |
|
This chapter explains the limitations and workarounds when connecting to the J.D. Edwards OneWorld XE adapter. The following topics are discussed:
The J.D. Edwards communication architecture is a single message, single reply architecture. You cannot return a list of messages or an array. The underlying code is C++, which calls with a pointer to a single structure, makes changes in the structure, and exits.
You cannot query and retrieve lists of records based on a search criteria using the J.D. Edwards OneWorld XE adapter due to a limitation with the J.D. Edwards business function architecture.
In J.D. Edwards, database connectivity is provided by using a set of proprietary (and complex) internal function calls. These calls mask the underlying database version by requiring very explicit and low-level calls to create lists of columns to retrieve or update, and create specialized structures for sorting or selection. The sets of APIs are not exposed through the Java (or any other) connectivity method, therefore, recordsets cannot be handled through business functions.
The J.D. Edwards database access APIs are not usable through the Java connector, therefore, managing lists of items (such as customers) can be challenging. It is relatively easy to create business functions in J.D. Edwards that handle a single record, or operate on a group of records, provided that all of the work is performed within the bounds of the J.D. Edwards toolset, but accessing lists of items outside the J.D. Edwards tools is more difficult.
To workaround this limitation you can create a custom business function in J.D. Edwards that returns a list of record keys based on a query. You must segment the lists because JDENET (J.D. Edwards' internal proprietary messaging API) has a limitation on the message buffer size for managing large or effectively unbounded result sets. The client code must iterate (loop) through successive calls to the business function, until an indicator is returned stating that the list is complete.
All calls to J.D. Edwards business functions are stateless; therefore, the business function cannot maintain an open cursor and return more rows on request. Positioning information must be passed to the J.D. Edwards business function on each call.
The following is a list of techniques for controlling iteration:
AN8
field (short address number) and is visible in the return buffer. This number can then be written to a reference field on the original customer record, or stored into a custom cross-reference table.
|
![]() Copyright © 2002, 2003 Oracle Corporation. All Rights Reserved. |
|