New Installation and upgrading

[eswbitto]

Hello All,

This question might be geared more toward the Alfresco engineers, but maybe someone can help. Our company is really close to launching Alfresco in a production environment. I've been testing Alfresco for the last month and have been making changes and adding add-on's all that good stuff. What I have done is uncompressed the alfresco and share war files and added or modified some files (for add-on's…etc) compressed them back and created backups for those war files.

My question is…If I decide to completely go with a fresh server to install alfresco on no data to be carried over. Could I just use the same war files from the other installation?

Are the war files initially created based on the server where the installation took place? or are they transferable to a new server?

[abarisone]

Hi,
the things you might want to do are quite different.
If you have to modify the original Alfresco or Share war files I would suggest you to put all these modification into an AMP file.
Then use Maven along with a continuous delivery software (like Jenkins) to build your final package starting from an original war file and keep all your configurations outside these packages, putting them in the tomcat/shared and loading them at startup.
It allowed us to build only one artifact which is the same while moving from test servers to certification servers and towards production servers.

Conversely, if for upgrading you meant to change the Alfresco version you are using, you have to compare the teo versions in order to find out if something changed..

Regards,
Andrea

[eswbitto]

Hey Andrea,

Thank you for the input! The only thing I question is if I have to go to that much trouble. The reason I say that is the extent of the modifications only go to making one line edits in some xml files and also inserting a couple of jar files. All the other changes have been done via amp files. I'm not sure I would still need to do all that from the suggestion you gave. Thoughts?


Best Regards,

Josh