Bug 724110 (BRMS-53)

Summary: Handling default location of customer repo
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Len DiMaggio <ldimaggi>
Component: Documentation, ConfigurationAssignee: Dana Mison <dmison>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: high    
Version: 5.0.0 EA1   
Target Milestone: ---   
Target Release: 5.0.0.CR2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/BRMS-53
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-02 18:11:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Len DiMaggio 2009-02-17 19:46:23 UTC
Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2009-04-08 05:22:47

What will we tell users about reconfiguring the BRMS - for example, moving the repository directory?

The issue here is that the user has to be informed/instructed to move the repository data outside of the server dir tree. Right now, the default
location is /bin under the server. Can this be moved to /data?

We will have to document how the user can move the repo - they will likely want to have the repo outside of the server dir tree as it is their data. Is there any way to do this other than other than exploding the BRMS .war file and hand editing config files>

Comment 1 Dana Mison 2009-04-08 09:22:47 UTC
Editing the component.xml in the .war would seem to be the only way.

Also the default config uses derby for data storage.  What's the position on using other databases, eg MySQL, Oracle etc.  Are we supporting external databases in this capacity ?

Comment 2 Dana Mison 2009-04-28 01:04:22 UTC
Installation instructions have been updated to specify deploying as exploded war for configuration purposes.

configuration instructions have been added, specifically changing repository location and setting up workspace & versions database config.  Added an appendix for sample configurations, I can currently only test mysql & the generic JDBC connector.  I don't think there is a great deal of difference but I will need verified Oracle, DB2 and MSSQL configurations as well.

Still to do: more specifics on supported app servers, databases and JVM

Comment 3 Dana Mison 2009-05-07 02:46:45 UTC
persistenceManager configuration examples added for generic JDBC BundleDbPersistenceManager , Oracle, MySQL & PostgreSQL

Comment 4 Dana Mison 2009-05-07 02:52:43 UTC
content has been updated in source

Comment 5 Len DiMaggio 2010-03-02 18:11:46 UTC
Verified in the 5.0.1 user guide.