Carl,

 

My repository data is stored in an RDBMS. And I was able to make repository migration work also. I tried two things: migrating the database and XML export/import using the BRMS. Both worked fine. I also discovered that redeployment of packages is not required while moving from one server to another. So if you move the BRMS application from one app server to another, the URLs of the deployed packages on the new server reflect the name of that server.

 

>>>>I’m moving to Drools 4.0.7, maybe there are some new feature to handle this issue

 

I’m using Drools 4.0.7 and on the BRMS side the only thing I discovered was the XML export/import feature (in the Admin Area).

 

I still am having a hard time making the security work though (on Websphere 6.1).

 

Thanks a lot for your help.

 

Vikas

 

 

Vikas,

 

There IS a export/import feature in both Drools 4.0.7 and 4.0.4. See on the BRMS web app in the « Admin » section, in the « Import Export » tab, you can export the whole rules repository as an zip file.

Then you can import the unzipped xml file to your target BRMS, works fine, I’ve just move my entire 4.0.4 repository to my new 4.0.7 BRMS that way.

 

Regards,

Carl

 

 

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

 

 

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@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.