- The author made a great work. I use UCanAccess every time I need to program in Java
- I have benefited from this project a lot .. because Java is no longer supporting access odbc .. Thank you authors but there are some features do not exist .... Thank you
- Really useful project, if you need to use MS Access databases; some important feature is not present yet, but people involved in the project are always quick and helpful on the forum. Thanks to these people!
- Developers seem to be very motivated. Projects works, some things are not perfect yet, but it's much better than a few years ago.
Relational Junction MS Access JDBC Driver Documentation. The connection URL is jdbc:relationaljunction:mdb:path_to_mdb_file, where path_to_mdb_file is.
Read more reviews >![Driver Driver](/uploads/1/2/5/8/125846580/781858077.gif)
It is important to note that the Data Access Driver differs from the existing Data Access Server. In addition to implementation differences, the Data Access Driver utilizes a different, more efficient, read-only JDBC driver to access the database.
Tip:
For integration with BI Publisher, the recommended configuration is the Data Access Driver.For implementation details, refer to the JD Edwards Interoperability Guide on the Oracle Technology Network:
This chapter discusses:
18.1 Prerequisites and Recommendation Installation Sequence for the Data Access Driver
This list shows the prerequisites and recommended installation sequence for the JD Edwards EnterpriseOne Data Access Driver:
- Prerequisite: Management Agent is installed on target machine.Refer to Install a Management Agent.
- Prerequisite: The Data Access Driver Software Component is uploaded to the Management Console.Refer to Upload Software Components.
- Prerequisite: The Data Access Driver Software Component is distributed to the target Managed Home.Refer to Distribute or Delete Managed EnterpriseOne Software Components.
- Prerequisite: Create a Data Access Driver.Refer to Create a Data Access Driver.
See Also:
- Refer to the JD Edwards EnterpriseOne Interoperability Guide in the chapter Using Java Database Connectivity for additional tasks and topics related to the Data Access Driver.
- JD Edwards EnterpriseOne BI Publisher for JD Edwards EnterpriseOne Guide
18.2 Create a Data Access Driver
You must use Server Manager to create a Data Access Driver.
See Also:
To install a JD Edwards EnterpriseOne Data Access Driver:
- Select the Managed Home in which you wish to install the Data Access Driver.
- Click the Create a New Managed Instance button to create the Managed Instance in the Managed Home.
- On Create/Register a Managed Instance, Instance Type, select this radio button:EnterpriseOne Data Access DriverTip:Ensure you choose the correct instance type for your intended installation. That is, there are two similar appearing instance types, one for Data Access Server and one for Data Access Driver.
- Click Continue.Note:The Propagate Enterprise Server Config drop-down appears only if any enterprise server is registered within the Server Manager console. The Propagate Enterprise Server Config drop-down contains the available enterprise server instances registered with the SM console within a particular selected server group. NONE is added to the drop-down by default.
- On Create/Register a Managed Instance, Instance Properties, complete these fields:
- Server GroupUse the pull-down to select the Server Group to which you want this instance to belong.Also refer to Chapter 21, 'Administer Management Console Users and User Groups'.
- Instance NameEnter a unique name for the instance name.Tip:A good business practice is to name your instances so that they are easily and consistently identifiable. For example:
PRODUCT_SERVER_PORT
wherePRODUCT
is the JD Edwards EnterpriseOne instance type, such asData_Access_Driver
, andwhereSERVER
is the machine on which the instance is installed, andwherePORT
is the HTTP port which is defined for use by this server. - Usage TypeUse the pull-down to select the usage type for this Data Access Driver.If you choose BI Publisher, that application must already be installed. By default, Server Manager populates this field with the typical value for a BI Installation location, where you must manually complete this variable value for your installation:
<BIPUB_ROOT>
For example, a typical completed location to a BI Publisher installation might be:z:OraBIPuboc4j_bi_j2eehomeapplicationsxmlpserverxmlpserverWEB-INFlib
If you choose Generic, you must provide the complete path to the application directory into which you wish to install the Data Access Driver. For example:C:jde_generic_read_only_driver_application
This location must be unique, must be empty, and must not be within the Management Agent directory structure. - Software ComponentUse the dropdown to select the version of this Software Component that you wish to install. For example:
EnterpriseOne Data Access Driver Version 8.98.0.5_09225
- Click Continue.Note:This example illustrates an installation by selecting an enterprise server to be propagated.Note:This example illustrates an installation by selecting NONE under Propagate Enterprise Server Config.
- On Create/Register a Managed Instance, Confirmation, review the key configuration items. The values on this form must be manually confirmed. You must validate or update, as appropriate, all configuration items.Tip:For help, click the Information icon next to the title of a field.See Also:
- After you have validated and updated all configuration items, click Continue to proceed to the next installation step.
- On Create/Register a Managed Instance, Finish, click the Create Instance button to complete the installation of the EnterpriseOne Data Access Driver.
![Jdbc Jdbc](/uploads/1/2/5/8/125846580/611249394.jpg)
Once the installation is complete the browser is redirected to the Management Console page for the newly registered Data Access Driver. This driver also appears as a Managed Instance within the corresponding Managed Home.
For each registered Managed Instance, the Management Console displays appropriate information at the top of the page:
- General
- StatusValid values are:
- RunningThis status is set whenever the Management Agent on the machine where the Data Access Driver is installed reports that the Java class is loaded for use by BI Publisher or the Generic application. The agent checks and reports status periodically so the status shown by Server Manager will be accurate within a few minutes.Note that unlike Managed Instances for Servers, there is no option to Stop the driver from Server Manager. Therefore, no Stop button is displayed.
- StoppedThis status is set whenever the Management Agent on the machine where the Data Access Driver is installed reports that the Java class is unloaded by BI Publisher or the Generic application. The agent checks and reports status periodically so the status shown by Server Manager will be accurate within a few minutes.Note that unlike Managed Instances for Servers, there is no option to Start the driver from Server Manager. Therefore, no Start button is displayed.
- Software Component VersionDisplays the version of this Software Component.You must stop the system using the Data Access Driver (BI Publisher or Generic) before you can change the Software Component Version.
See Also:
- Instance Properties
- Install LocationThe location where the Data Access Driver was installed.
- Instance Usage TypeIdentifies the usage type of the Data Access Driver as either BI Publisher or Generic.
- Instance NameThe unique name assigned to the Managed Instance at the time it was created or registered.
For information on log files, refer to the chapter entitled: Available Log Files.