project_key: JBPAPP6 (11:44:33 PM) ozizka-ntb: Regarding the JDBC drivers and Datasources - (11:44:58 PM) ozizka-ntb: perhaps we could have a maven-based "installer" (11:45:16 PM) ozizka-ntb: So we wouldn't ship jdbc drivers, (11:45:39 PM) ozizka-ntb: rather a pom with jdbc as deps in profiles (11:46:02 PM) ozizka-ntb: which would activate through -Dds=postgresql (11:46:28 PM) ozizka-ntb: there would be dependency:copy-dependencies, which would copy the JDBC jar to AS (11:46:36 PM) ozizka-ntb: and set the datasource (11:46:59 PM) ozizka-ntb: Maven's role in this would be to get the driver All the remaining ways (CLI or console) need the developer/admin to manually provide the jar.
Forgot to add - something like this is in the testsuite. Minus the copying.
Related: https://docspace.corp.redhat.com/docs/DOC-82405 EAP Graphical Installer Requirements
to be discussed as an installer feature
[per JIRA triage] this issue should remain in the EAP6 TBD for now. We are discussing the relevance of this and would have a higher impact if we decide to remove H2 from the distribution. There has also been a discussion on how it can be implemented but the work is not a priority at this time based on the other Installer work in progress.
Link: Added: This issue is a dependency of JBPAPP-8085
Link: Added: This issue is a dependency of JBPAPP-9555
Link: Removed: This issue is a dependency of JBPAPP-8085
This feature has been added for 6.1. Screenshots to follow.
Attachment: Added: datasourceprototype.png Attachment: Added: jdbcdriverno.png Attachment: Added: jdbcdriveryes.png Attachment: Added: jdbcinstalled.png
Attached are screenshots of the JDBC installation feature. The installer uses the CommandContext API to add the drivers to EAP. The server is started (in either standalone or domain, user chooses at an earlier step in the installation process), and the correct commands are issued. The server is then shutdown. A datasource using the newly installed driver is also installed during the process. It is also possible to select multiple jars in the file browser during JDBC driver installation, and all given jars will be copied to an appropriate location. The driver is installed as a core module. A few things still need to be done: a) Translation work for all strings b) A proper description of the Datasource installation page needs to be created
Docs QE Status: Removed: NEW
This feature is available in EAP 6.2.0 ER1 and further. Found this issue while cleaning up BZs.
Verified on EAP 6.2.0.ER3.