Bug 1189115 - DV specific configuration artifacts present in server's 'default' profile
Summary: DV specific configuration artifacts present in server's 'default' profile
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Configuration, Installer
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ER3
: 6.2.0
Assignee: Van Halbert
QA Contact:
URL:
Whiteboard:
Depends On: 1224333 1234831
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-04 13:40 UTC by Jan Stastny
Modified: 2016-02-10 08:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
DV-specific artifacts (DashboardDS, teiid-log-ds, security-domains created in installer, modeshape subsystem) are also inserted into the 'default' configuration profile in domain.xml. To workaround this issue, remove the default profile from the cli-script within the assembly phase.
Clone Of:
Environment:
Last Closed: 2016-02-10 08:48:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan Stastny 2015-02-04 13:40:49 UTC
Description of problem:
While examining contents of server configuration files I noticed, that dv specific artifacts (DashboardDS, teiid-log-ds, security-domains created in installer, modeshape subsystem) are also inserted into 'default' configuration profile in domain.xml.
Shouldn't it be only in the 'ha' related profiles as holds with teiid subsystem?

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

How reproducible:
always

Steps to Reproduce:
1. install dv
2. open JBOSS_HOME/domain/configuration/domain.xml
3. search for DashboardDS in document
4. notice that there are three occurences of such datasource definition, including the one in 'default' profile

Actual results:


Expected results:


Additional info:

Comment 1 Van Halbert 2015-02-04 16:28:27 UTC
This isn't a high priority because it doesn't impact any supported profile.   But this could be cleaned up for future releases.

Comment 2 Thomas Hauser 2015-02-04 17:14:42 UTC
Removing these is a matter of removing the default profile from the cli-script within the assembly.

Comment 3 Thomas Hauser 2015-05-13 15:47:08 UTC
I've removed any command that configures domain's default profile. There are still changes that need to be made in teiid-extensions since the scripts are brought in from that project and not the files in the assembly.

Comment 4 Jan Stastny 2015-06-16 11:29:00 UTC
Following element is still present in domain.xml in default profile:

<datasource jndi-name="java:/teiid-log-ds" pool-name="teiid-log-ds" enabled="true" use-java-context="true">
    <connection-url>jdbc:h2:file:${jboss.server.data.dir}/teiid-logging/teiid-logging-ds;DB_CLOSE_ON_EXIT=FALSE;DB_CLOSE_DELAY=-1</connection-url>
    <driver>h2</driver>
    <security>
       <user-name>sa</user-name>
       <password>${VAULT::teiid::dblogging.password::1}</password>
    </security>
</datasource>

Comment 5 Van Halbert 2015-06-24 14:33:38 UTC
(In reply to Jan Stastny from comment #4)
> Following element is still present in domain.xml in default profile:
> 
> <datasource jndi-name="java:/teiid-log-ds" pool-name="teiid-log-ds"
> enabled="true" use-java-context="true">
>    
> <connection-url>jdbc:h2:file:${jboss.server.data.dir}/teiid-logging/teiid-
> logging-ds;DB_CLOSE_ON_EXIT=FALSE;DB_CLOSE_DELAY=-1</connection-url>
>     <driver>h2</driver>
>     <security>
>        <user-name>sa</user-name>
>        <password>${VAULT::teiid::dblogging.password::1}</password>
>     </security>
> </datasource>

This related issue is covered by BZ:  https://bugzilla.redhat.com/show_bug.cgi?id=1234831  and has been done to be included in ER3.

Comment 6 Van Halbert 2015-06-30 15:45:38 UTC
It appears all the changes have been made.  Tom, based on his comments, did most of the changes related to default, and I made the change to teiid-extensions.

I'll flag this is modified for ER3.


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