RE: [rules-users] BRMS - Migrating packages from one server to another

Vikas, I've tried on Drools 4.0.4 copying the repository.xml file and the repository directory on another physical server and it worked fine but I am not satisfied of this method. I was expected some enhanced export feature that would produce a zip file for each package that could be loaded in another BRMS via the web interface. I'm moving to Drools 4.0.7, maybe there are some new feature to handle this issue, but I"ve checked the documentation and there is nothing about moving packages. Regards, Carl _____ De : rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] De la part de Vikas Phonsa Envoyé : mardi 20 mai 2008 15:15 À : Rules Users List Objet : [rules-users] BRMS - Migrating packages from one server to another Hi Everybody, I need to migrate my deployed packages from one BRMS instance to another (different Servers). Would migrating the repository data be sufficient? What happens to the package URLs ? Those URLs have server names in them, so would I have to redeploy the packages and regenerate the URLs on the new server? Thanks, Vikas This email and/or any files or attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and/or any files or attachments transmitted with it is strictly forbidden. If you have received this email in error, please delete the e-mail and/or any files or attachments, and also notify the system manager (PostMaster(a)mercuryinsurance.com) of the error. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email and/or any files or attachments transmitted with it.