note: all modeshape content needs to have the clarification that it only applies to 5.1 and onwards. 

Hi, it was suggested that you were the best person to assign this to.

We need enough info to get started with being able to go through the processes ourselves to document them.

I realize that we probably won't have complete info on this for a while, but anything to get started would be good.

The work on Drools Guvnor and ModeShape is currently being done in in it's own branch ( http://anonsvn.jboss.org/repos/labs/labs/jbossrules/branches/kstam_guvnor_modeshape/ ). I will post the status of the completion of this work here. Currently there are still some failing tests that are being worked on.

Development and testing for ModeShape integration is not completed yet. We should be getting some docs from Kurt Stam hopefully end of next week. At this point we need to look into what docs are available and what we want to provide to the customer.

Link: Added: This issue related BRMS-396

Hi Tihomir, I have checked in the modeshape integration code. To switch from JR to MS do the following:

1. drools-repo/jcr-ms-impl, if you have a ModeShape 2.3-SNAPSHOT, then run 'mvn clean install'
2. drools-repo/drools-repository: change dependency from jr to ms in the pom, and change the settings in the drools_repository.properties (see attachment), then run 'mvn clean install'
3. drools-guvnor should now pick up ModeShape due to the change in 2.

The ModeShape configuration lives in drools-repository/src/test/resources/modeshape, make sure this is on your classpath if you run the tests in step 3 (or copy this directory into guvnor-drools/src/main/resources). I still need to address the complete guvnor configuration solution in BRMS-407 and BRMS-408.

I hope this gets you going.

Cheers,

--Kurt

Switch to MS by using the settings as in this file.

Attachment: Added: drools_repository.properties

Release Notes Text: Added: test

Release Notes Text: Removed: test 

Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage

Security: Removed: Public 

content has been added to BRMS Admin guide - still need to add clarification about using org.drools.repository.secure.passwords

added password encoding optional step

this content has been removed from the BRMS admin guide & will ship as a smaller doc when the modeshape files are made available separately

Labels: Removed: rn-dlesage rn-not-needed 

Database configuration info for jackrabbit and modeshape: https://access.redhat.com/kb/docs/DOC-37076

more content here too: https://access.redhat.com/kb/docs/DOC-43075

doc updated: http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_BRMS_Platform/5/html/BRMS_Administrator_Guide/index.html

needs review

I read and tried the instructions described in doc and the modeshape was installed successfully (and BRMS was correctly running). But the instructions are only for standalone version. In case of deployable there are some major or minor changes depending on container used. In case of EAP and SOA-P it's probably only different names for properties files, but for EWS or WAS the changes will be much bigger, as they are nonJBoss containers.

The doc includes steps to install modeshape in a standalone BRMS distribution, but not for installing to another container such as EWS, EAP, SOA-P.  The differences are very small, probably the properties file name (brms-roles vs jmx-roles),

On EAP, SOA-P the names are jmx-{roles,users} by default. In case of EWS, tomcat handles JAAS differently, so the EWS installation will have to be updated.

Open issues:

* EWS install - I'll ping EWS QE about this
* Installing/Configuring Modeshape when BRMS is deployed to IBM WAS7 - I'd vote to document this in a separate KB article