[OPENIDM-13023] Include an out of the box Oracle specific bnd file in db/oracle/scripts Created: 11/Apr/19  Updated: 24/Jul/20  Resolved: 24/Jul/20

Status: Closed
Project: OpenIDM
Component/s: Module - Repository JDBC
Affects Version/s: 6.5.0,
Fix Version/s: 7.0.0

Type: Bug Priority: Minor
Reporter: Yinyan Cao Assignee: Emanuel Brici
Resolution: Fixed Votes: 0
Labels: CLARK, release-notes
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Target Version/s:
Verified Version/s:
QA Assignee: Petr Bednar [X] (Inactive)
Story Points: 1
Sprint: 2019.11 - IDM


The current approach (https://backstage.forgerock.com/docs/idm/6.5/install-guide/#oracle-osgi-bundles-hikari) of creating an Oracle DB bundle is to copy sqljdbc4.bnd from db/mssql/scripts, and modify the contents with:

Export-Package: *;version=${version}
Bundle-Name: Oracle JDBC Driver 4.0 for SQL Server
Bundle-SymbolicName: Oracle JDBC Driver 4.0 for SQL Server
Bundle-Version: ${version}
Import-Package: *;resolution:=optional

The desired outcome is to have a default OOTB bnd file in db/oracle/scripts that looks like:

Export-Package: *;version=${version}
Bundle-Name: Oracle Database JDBC Driver
Bundle-SymbolicName: oracle.jdbc.OracleDriver
Bundle-Version: ${version}
Import-Package: *;resolution:=optional

Comment by Petr Bednar [X] (Inactive) [ 07/Aug/19 ]

Verified as fixed, file was add (openidm/db/oracle/scripts/ojdbc8.bnd)


Comment by Lana Frost [ 24/Jul/20 ]

Reopening to add to release notes

Generated at Sun Sep 27 23:16:39 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.