Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A000000A635p&sfdc.override=1 project_key: JBPAPP6 We are using domain mode and when we try to create a new datasource to a specific profile selected in the combo placed in the left corner, it only shows jdbc drivers deployed in running server, including servers from different profiles from the selected one. Also, it is possible to create the datasource in a profile without the reference to the driver on it, see code snipped domain.xml. <profile name="full-ha"> . . . <subsystem xmlns="urn:jboss:domain:datasources:1.1"> <datasources> <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true"> <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url> <driver>h2</driver> <security> <user-name>sa</user-name> <password>sa</password> </security> </datasource> <datasource jta="false" jndi-name="java:/bla" pool-name="bla" enabled="true" use-ccm="false"> <connection-url>haosdjoksada</connection-url> <driver-class>oracle.jdbc.OracleDriver</driver-class> <driver>oracle</driver> <validation> <validate-on-match>false</validate-on-match> <background-validation>false</background-validation> </validation> <statement> <share-prepared-statements>false</share-prepared-statements> </statement> </datasource> <drivers> <driver name="h2" module="com.h2database.h2"> <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class> </driver> </drivers> </datasources> </subsystem> In this example, I had the oracle jdbc driver defined in the default profile, and I had a running server based in the default profile. I chose full-ha in the combo when creating a new datasource, oracle jdbc driver was showed as an option to be selected and I was able to select it to create a new datasource. *Probably it happens because the Console shows drivers defined in running servers. IMHO it should maybe just shows drivers associated to the current profile selected on the combo in the left corner not in running servers.*
Moving to TBD EAP 6 as this is an RFE.
Docs QE Status: Removed: NEW
It can only show drives of running servers, because w/o a server instance it's mereley a blob to the content repository. The DC itself cannot disinguish the binaries it maintains as "deployments".
From my point of view this issue can be closed (as rejected)
Maybe some further clarification: try to answer this question yourself: What's are the drivers associated with selected profile?
JDBC Driver is a module, thus it's available to every profile. Sometimes the user doesn't want to start the server to configure a datasource. For instance, during a management schedule. User usually stop the server, change what he needs and start it again. With the current implementation, the JDBC driver will not be available if the server with the associated profile with the driver metadata is not up. Maybe it's not a UI issue, maybe it's the way AS7/EAP6 deals with datasources and drivers since its configurations are associated to a subsystem in a profile. It could be associated to a server settings in host.xml or to a server-group, not to a specific profile. Does it make more sense?
Moving to 6.4 as the issue is still valid for 6.3
if we agree this is an improvement and not a bug we should close the bug and raise an EAP7 Jira to get this new feature into an EAP version.
Once we get agreement its an RFE I think we should close this and raise an EAP7 Jira.