Skip navigation

XMLP - Data Access Driver – What is it Used for?

The JD Edwards EnterpriseOne Data Access Driver (DAD) is a type 4 jdbc driver whose sole purpose is to access JD Edwards database from an outside source.  Applications such as Hyperion or BI Publisher can utilize the DAD to make such a connection.

NOTE:  The DAD provides the third party tool access to EnterpriseOne data in read only mode.


What are the Requirements to Use the DAD?

The DAD can only be utilized with applications that support “read-only” jdbc type 4 drivers.


How Complex is the Setup?

The setup is fairly straight forward involving placement of the dad driver jar files into the location of third party applications class path directory (Usually this will be the product’s lib directory where that application’s jar files exists).  Since JD Edwards EnterpriseOne is not a database in and of itself an environment is initialized which is then utilized to perform the queries on the JD Edwards data.  This is done via a URL that specifies the environment name.  To get this environment to work the jas.ini, jdbj.ini and files should be created on the third party application’s machine. This has to be done via server manager by registering that third party application machine and then creating a managed instance for type Data Access Driver.


For additional resources regarding Data Access Driver please see the following KM documents:

     E1: XMLP: Implementation Steps for Data Access Driver (DAD) with BI Publisher 11g and Above (Doc ID 1331667.1)

   UBE - Subsystem Jobs – What are they and Do They Increase Efficiency?

Imagine working at a batting cage where your sole responsibility is to pitch the baseball to all customers that are practicing batting. Your shift is 8 hours and you have to continuously pitch the baseball to customers. Eventually the muscles in your arm tire and you become exhausted and the same can be said about UBE processing on your system.


In contrast to the example above, when a UBE is run separately it must complete a series of initialization steps such as selecting an environment and loading specs. These steps must be completed each and every time the UBE is submitted also exhausting system resources such as CPU and RAM which is where a subsystem job is the better option.


What is a Subsystem UBE Job and how does it save system resources?

The Subsystem UBE Job loads the environment and specs only once and basically hibernates and checks for items to run as opposed to a scheduled UBE, for example, that would have to load these things each time it is submitted.

Use subsystem jobs to:

  • Off-load processor resources
  • Protect server processes
  • Perform repetitive and frequent processes to maximize output throughput


For additional resources regarding Subsystem UBE Jobs please see the following KM documents:

E1: SS: Overview of Subsystem Processing in EnterpriseOne (Doc ID 1265778.1)

E1: 40: Subsystem Processing (Doc ID 625418.1)

Filter Blog

By date: By tag:

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see for instructions.