Hi Seema,
I am attaching the repository.xml we had used. Yes, it could be possible that
JackRabbit would need to be configured for clustering.(I guess we missed that
one). (You will need to change repository.xml in that case as specified).
The main reason we cannot use the BRMS for our current project is that our
deadlines do not allow us to wait till the GA of Release 5 (when we can get
enterprise support for it) and we cannot use 4.0.7 as it does not have some
features important to us(like Security etc).
Release 5 of the BRMS is really good and if you can use it, you should go for
it.
Cheers,
Vikrant
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Seema Manivannan
Sent: Saturday, November 15, 2008 7:36 AM
To: Rules Users List
Subject: Re: [rules-users] BRMS in a WAS cluster
Vikrant,
Thanks for the prompt reply. It would be surely helpful if you can post the
samples which worked for you. What are the license and support issues that made
you decide against BRMS? My understanding is that we need to enable JackRabbit
clustering when we have JackRabbit running in all nodes of the app server
cluster. Oracle RAD would handle only clustering at the DB level. Please
correct me if I'm wrong.
Thanks,
Seema
On Thu, Nov 13, 2008 at 1:18 PM, Vikrant Yagnick <[EMAIL
PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
Hi Seema,
We had initially tried using the BRMS for rules using WAS 6.1 and Oracle in
clustered modes.
While, we are not going for the BRMS right now due to license and support
issues, from that experience I can answer some of the questions, below.
From: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> [mailto:[EMAIL
PROTECTED]<mailto:[EMAIL PROTECTED]>] On Behalf Of Seema Manivannan
Sent: Thursday, November 13, 2008 6:15 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [rules-users] BRMS in a WAS cluster
hi,
I would appreciate any replies at least confirming that my approach below is
right.
Thanks,
Seema
On Sun, Nov 9, 2008 at 11:16 PM, seemamani <[EMAIL PROTECTED]<mailto:[EMAIL
PROTECTED]>> wrote:
We use Drools 4.0.7 in our application which is deployed on a WAS 6.1 cluster
and it is working fine. Now we want to deploy the Drools BRMS also in the
WAS cluster. I went through the Drools and Jackrabbit mailing lists and
documentation. Please confirm if my understanding of how this can be
implemented is correct.
1. By default, JackRabbit uses Apache Derby in-memory database which does
not support clustering
That is correct
2. We need to configure a persistence manager in JackRabbit that stores data
in a RDBMS like Oracle
Yes. If you need a sample, I can send it to you. (Though, I am sure there is a
lot of material on this on the web).
3. I need to follow the instructions for JackRabbit clustering given here
http://wiki.apache.org/jackrabbit/Clustering
I am not sure, why you need Jack Rabbit clustering. If the tables are stored in
the database, then I am assuming RAC should handle clustering at the DB level.
Though, do correct me if I am wrong.
4. Also, the Drools documentation says that "The BRMS will create the
tables the first time it is started up if it is running against a fresh
(empty) RDBMS - so its important to note that the user credentials supplied
have permissions to create tables (at least initially, on first run, after
that they could be locked down)."
Is it not possible to create the Oracle tables before running the BRMS (we
have permission issues in creating the tables from the application)? I
assume that the DDL for creating the tables is available with the JackRabbit
distribution.
One Q&D way may be to just create the tables in a test database and then make
the schema into DDL scripts for use before installation.
5. Is there anything else I'm missing? Will BRMS work fine in the cluster
with the above setup?
My assumption is that the BRMS is just a web-app using the database as it's
back-end and hence do not know of any issues it could face.
Thanks,
Seema
--
View this message in context:
http://www.nabble.com/BRMS-in-a-WAS-cluster-tp20408825p20408825.html
Sent from the drools - user mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
[email protected]<mailto:[email protected]>
https://lists.jboss.org/mailman/listinfo/rules-users
MASTEK LTD.
Mastek is in NASSCOM's 'India Top 20' Software Service Exporters List.
In the US, we're called MAJESCOMASTEK
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Opinions expressed in this e-mail are those of the individual and not that of
Mastek Limited, unless specifically indicated to that effect. Mastek Limited
does not accept any responsibility or liability for it. This e-mail and
attachments (if any) transmitted with it are confidential and/or privileged and
solely for the use of the intended person or entity to which it is addressed.
Any review, re-transmission, dissemination or other use of or taking of any
action in reliance upon this information by persons or entities other than the
intended recipient is prohibited. This e-mail and its attachments have been
scanned for the presence of computer viruses. It is the responsibility of the
recipient to run the virus check on e-mails and attachments before opening
them. If you have received this e-mail in error, kindly delete this e-mail from
desktop and server.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
rules-users mailing list
[email protected]<mailto:[email protected]>
https://lists.jboss.org/mailman/listinfo/rules-users
MASTEK LTD.
Mastek is in NASSCOM's 'India Top 20' Software Service Exporters List.
In the US, we're called MAJESCOMASTEK
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Opinions expressed in this e-mail are those of the individual and not that of
Mastek Limited, unless specifically indicated to that effect. Mastek Limited
does not accept any responsibility or liability for it. This e-mail and
attachments (if any) transmitted with it are confidential and/or privileged and
solely for the use of the intended person or entity to which it is addressed.
Any review, re-transmission, dissemination or other use of or taking of any
action in reliance upon this information by persons or entities other than the
intended recipient is prohibited. This e-mail and its attachments have been
scanned for the presence of computer viruses. It is the responsibility of the
recipient to run the virus check on e-mails and attachments before opening
them. If you have received this e-mail in error, kindly delete this e-mail from
desktop and server.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<?xml version="1.0"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!DOCTYPE Repository PUBLIC "-//The Apache Software Foundation//DTD Jackrabbit 1.2//EN"
"http://jackrabbit.apache.org/dtd/repository-1.2.dtd";>
<!-- Example Repository Configuration File -->
<Repository>
<!--
virtual file system where the repository stores global state
(e.g. registered namespaces, custom node types, etc.)
-->
<FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
<param name="path" value="${rep.home}/repository"/>
</FileSystem>
<!--
security configuration
-->
<Security appName="Jackrabbit">
<!--
access manager:
class: FQN of class implementing the AccessManager interface
-->
<AccessManager class="org.apache.jackrabbit.core.security.SimpleAccessManager">
<!-- <param name="config" value="${rep.home}/access.xml"/> -->
</AccessManager>
<LoginModule class="org.apache.jackrabbit.core.security.SimpleLoginModule">
<!-- anonymous user name ('anonymous' is the default value) -->
<param name="anonymousId" value="anonymous"/>
<!--
default user name to be used instead of the anonymous user
when no login credentials are provided (unset by default)
-->
<!-- <param name="defaultUserId" value="superuser"/> -->
</LoginModule>
</Security>
<!--
location of workspaces root directory and name of default workspace
-->
<Workspaces rootPath="${rep.home}/workspaces" defaultWorkspace="default"/>
<!--
workspace configuration template:
used to create the initial workspace if there's no workspace yet
-->
<Workspace name="${wsp.name}">
<!--
virtual file system of the workspace:
class: FQN of class implementing the FileSystem interface
-->
<FileSystem class="org.apache.jackrabbit.core.fs.db.OracleFileSystem">
<param name="url" value="jdbc:oracle:thin:@172.16.231.148:1521:LANDGDEV"/>
<param name="user" value="test_rules"/>
<param name="password" value="rules123"/>
<param name="schemaObjectPrefix" value="rep_"/>
<!-- <param name="tableSpace" value="default"/> -->
</FileSystem>
<!--
persistence manager of the workspace:
class: FQN of class implementing the PersistenceManager interface
-->
<PersistenceManager class="org.apache.jackrabbit.core.persistence.bundle.OraclePersistenceManager">
<param name="url" value="jdbc:oracle:thin:@172.16.231.148:1521:LANDGDEV"/>
<param name="user" value="test_rules"/>
<param name="password" value="rules123"/>
<param name="schemaObjectPrefix" value="version_"/>
<!-- <param name="tableSpace" value="default"/> -->
</PersistenceManager>
<!--
Search index and the file system it uses.
class: FQN of class implementing the QueryHandler interface
-->
<SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
<param name="path" value="${wsp.home}/index"/>
</SearchIndex>
</Workspace>
<!--
Configures the versioning
-->
<Versioning rootPath="${rep.home}/version">
<!--
Configures the filesystem to use for versioning for the respective
persistence manager
-->
<FileSystem class="org.apache.jackrabbit.core.fs.db.OracleFileSystem">
<param name="url" value="jdbc:oracle:thin:@172.16.231.148:1521:LANDGDEV"/>
<param name="user" value="test_rules"/>
<param name="password" value="rules123"/>
<param name="schemaObjectPrefix" value="rep_"/>
<!-- <param name="tableSpace" value="default"/> -->
</FileSystem>
<!--
Configures the persistence manager to be used for persisting version state.
Please note that the current versioning implementation is based on
a 'normal' persistence manager, but this could change in future
implementations.
-->
<PersistenceManager class="org.apache.jackrabbit.core.persistence.bundle.OraclePersistenceManager">
<param name="url" value="jdbc:oracle:thin:@172.16.231.148:1521:LANDGDEV"/>
<param name="user" value="test_rules"/>
<param name="password" value="rules123"/>
<param name="schemaObjectPrefix" value="version_"/>
<!-- <param name="tableSpace" value="default"/> -->
</PersistenceManager>
</Versioning>
<!--
Search index for content that is shared repository wide
(/jcr:system tree, contains mainly versions)
-->
<SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
<param name="path" value="${rep.home}/repository/index"/>
</SearchIndex>
</Repository>
_______________________________________________
rules-users mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/rules-users
