Resolution:
First, the OneWorld Adapter gets notification of the new transaction via JDE's event-based Interoperability Engine.  In contrast, ADB would have to poll the Z-file(s).

Also, the JDE Adapter has transaction context, meaning that you can select which transactions to publish and under which subject. If you use ADB there's no way to distinguish between different transactions that happen to use the same Z-files; it would just publish the new database rows.

The JDE Adapter gets the transaction information through JDE's JDE-DB API. ADB uses ODBC. Therefore the JDE Adapter will work with *any* DBMS supported by JDE.  In contrast, ADB has a set of DBMS's it will work with.

Finally, the method of access to data that the OneWorld adapter employs is within J.D. Edwards' recommendations. Going directly to the tables is not recommended by JDE and
should be minimized.

If the adapter uses Z-files for publishing, then what are the advantages versus ADB?