If you want to replicate design-time artifacts too then configuring Guvnor to use a database and replicating the database to each location might be your best option.

If you only want to replicate the runtime artifacts (i.e. a compiled package) you should be able to use a KnowledgeAgent to retrieve the PKG files. You should only need to re-build a package if you observe source artifacts.

You could also consider https://community.jboss.org/wiki/PublishDroolsArtifactsFromAProductionEnvironment.

On 15 April 2013 17:37, ciberg2 <joaoguerra72@gmail.com> wrote:

Hi,

I have a application that will be installed in several locations, and
because of connection constraints, each location will run its own
Drools-Guvnor server with a deployed package consisting of decision tables
and BPMN processes.

I want to make possible that when some asset is changed centrally, this
change can be deployed (or replicated) across all Drools servers.

I read about KnowledgeAgent to make hot deployments, but as far as I
understood someone has to still build the package in each of the servers.

Is it possible to do what I want? If yes please give me some tips on how to
do it.
If not what can I do to solve the deployment across multiple servers
problem?

--
View this message in context: http://drools.46999.n3.nabble.com/Deploy-package-across-several-Drools-Guvnor-servers-unattended-tp4023348.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users