jawahar raj wrote:
> http://www.nabble.com/file/p22662344/jackrabbit-mysql-search-mysql-pooled.xml
> jackrabbit-mysql-search-mysql-pooled.xml 
> http://www.nabble.com/file/p22662344/jackrabbit-mysql-search.xml
> jackrabbit-mysql-search.xml 
>
> hi david,
> another information on this regard. what i have is the apache tomcat5.5.20
> folder dump from the production server. i am trying to run the site locally
> in my machine. i am getting the errors while running the tomcat. Is there
> any specific way to redeploy the production code-base locally?
> This is what I did..
>
> i have copied the ROOT folder from the prod server and I have pasted it
> inside my local tomcat WebApp.Am I following the correct steps?Kindly give
> ur suggestions...I have attached the jackrabbit config files but the
> context.xml files is empty in the prod folder dump which I have...Thanks in
> advance
>   
I'm guessing you are having both the local copy and the production copy
look at the same MySQL database.  I think you should be able to copy the
entire webap, clearing out the local repositories folder.  Indexes
should be rebuilt automatically.  Working this way, there needs to be a
<Resource ... /> element in the local <Context ... > element for your
magnolia.  Take a close look at your production setup for that and copy
it to your local magnolia.  That should take care of the problems
getting a datasource from JNDI.

Otherwise if you are looking to have your local magnolia look at a local
repository, you'll need to export the repositories from the production
magnolia and import them in the local.  Do not do this if you are having
both magnolias accessing the same mysql database.  Personally I would
not have both looking at the same database just to protect the
production environment.

--David

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to