Safely duplicating/isolating a 3.2 installation

[rikitiki]

Hi there, kind of a weird question.

I'm trying to duplicate a production Alfresco 3.2/Share application into a development environment.  I'm not familiar with this application's custom configuration, and I want to make sure the new dev installation doesn't try to contact the production environment in any way once I start it up for the first time.

I'm looking for a list of configuration files (for both Alfresco and Share) that may specify hostnames, IP addresses, etc for the database and repository (such as alfresco-global.properties).  I just don't want to miss anything and have changes in the development application affect data on the production server.

Thanks!

[mrogers]

Your configuration should all be neatly isolated in the the alfresco/shared folder so grep for your hostname there.

Your alfresco-global.properties file should be the only you need to change for Alfresco.   And possibly your share-config-custom.xml file for Share.

Assuming that you are on Tomcat also check whether Tomcat/conf/server.xml has been changed by the installer.