Bug 950923 - To change the default datasource in dashbuilder
Summary: To change the default datasource in dashbuilder
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: BAM
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR4
: 6.0.0
Assignee: David Gutierrez
QA Contact: Jan Hrcek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-11 08:10 UTC by Ryan Zhang
Modified: 2014-08-06 20:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:12:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ryan Zhang 2013-04-11 08:10:19 UTC
Description of problem:
The default datasource console is "ExampleDS". Please change the jboss-web.xml to it as following.

<jboss-web>
 ...
        <res-ref-name>jdbc/dashbuilder</res-ref-name>
        <res-type>javax.sql.DataSource</res-type>
        <!--jndi-name>java:jboss/datasources/dashbuilderDS</jndi-name-->
        <jndi-name>java:jboss/datasources/ExampleDS</jndi-name>
    </resource-ref>
...
</jboss-web>

Version-Release number of selected component (if applicable):


How reproducible:
If not change this, dashbuilder can't be deployed.
Reproduced in BPMS 6.0.0 DR3.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Ryan Zhang 2013-04-11 09:00:31 UTC
This is a small fix. 
Sent a pull request: https://github.com/droolsjbpm/dashboard-builder/pull/2

Comment 2 David Gutierrez 2013-04-11 09:27:28 UTC
The following document document explains how to set-up an integrated installation of the Dashbuilder and the jBPM Human Tasks console. As you can see in the document the two modules use different data sources. 

https://github.com/droolsjbpm/dashboard-builder/blob/master/builder/src/main/jbossas7/README.md

For the Dashbuilder deployment you first need to create a custom data source as explained in the document, in order to have separated database schemas for the two modules.

So, what is the main reason to make Dashbuider use the ExampleDS?
Is not working after following the deployment instructions?

Comment 3 Lukáš Petrovický 2013-04-11 09:32:36 UTC
It would be preferrable for testing (and I think, subsequently, for users) if the product could be configured to work using both a single data source and optionally multiple.

Comment 4 Ryan Zhang 2013-04-11 11:56:43 UTC
(In reply to comment #2)
> The following document document explains how to set-up an integrated
> installation of the Dashbuilder and the jBPM Human Tasks console. As you can
> see in the document the two modules use different data sources. 
> 
> https://github.com/droolsjbpm/dashboard-builder/blob/master/builder/src/main/
> jbossas7/README.md
> 
> For the Dashbuilder deployment you first need to create a custom data source
> as explained in the document, in order to have separated database schemas
> for the two modules.
> 
> So, what is the main reason to make Dashbuider use the ExampleDS?
The main reason for this is to use an existed DS in AS7. Otherwise it can't be "predeployed", "preconfigured" in BPMS product.
It can't even be deployed without manually installed the datasource first. It breaks the requirement of "predeployed" and "preconfigured"   



> Is not working after following the deployment instructions?
I believe the steps are correct though I didn't realize where to find it before you point it out.

Sure, the guide definetly increase the value. 
Wouldn't it be better for dashbuild  use the same datasource as jbpm datasource as a default value?

Comment 6 David Gutierrez 2013-04-11 17:22:50 UTC
I agree on using the ExampleDS by default. Thus I've merged your pull request and also modified the deployment instructions onto JBoss in order to remove the dashbuilderDS datasource creation stuff. All these changes have been commited to github  already.

Comment 7 Jan Hrcek 2013-05-09 08:35:38 UTC
QA: Default datasource changed. Verified in BPMS 6.0.0 DR4


Note You need to log in before you can comment on or make changes to this bug.