Table of Contents

Search

  1. Preface
  2. Starting Data Archive
  3. System Configuration
  4. Database Users and Privileges
  5. Source Connections
  6. Target Connections
  7. Archive Store Configuration
  8. Datatype Mapping
  9. Database Optimization
  10. SAP Application Retirement
  11. z/OS Source Data Retirement
  12. Seamless Data Access
  13. Data Discovery Portal
  14. Security
  15. SSL Communication with Data Vault
  16. LDAP User Authentication
  17. Auditing
  18. Running Jobs from External Applications
  19. Salesforce Archiving Administrator Tasks
  20. Upgrading Oracle History Data
  21. Upgrading PeopleSoft History Data
  22. Data Archive Maintenance
  23. Storage Classifications
  24. Appendix A: Datetime and Numeric Formatting
  25. Appendix B: Data Archive Connectivity

Administrator Guide

Administrator Guide

Generic JDBC Source Connections

Generic JDBC Source Connections

Use a generic JDBC source connection to connect to a source database through a generic JDBC driver.
To use a generic JDBC source connection, such as a MySQL database, you must first upload the JDBC driver JAR file. When you upload the JAR file, Data Archive copies it to the following directories:
  • <ILM Products Installation Directory>\webapp\WEB-INF\lib
  • <ILM Products Installation Directory>\webapp\edm\lib
Data Archive prefixes the JAR file name with "zz_." For example, if you upload a driver file named GenJdbc.jar, Data Archive names the file zz_GenJdbc.jar in the
lib
directories. Data Archive signs the JAR file in the
…\edm\lib
directory.
Data Archive also adds the driver location to the classpath. For the classpath changes to take effect, you must restart the ILM application server on the machine that hosts Data Archive.
After you restart the ILM application server, create the source connection and specify the connection properties.

0 COMMENTS

We’d like to hear from you!