Changing name to alfresco.war makes Share login to fail

[jlabuelo]

Hi there

We have an alfresco 3.0 configuration in our Ubuntu server, however we have changed the name in /tomcat/webapps of the alfresco.war and "alfresco" folder to "tomcat/webapps/instance1.war" and so the folder is "/tomcat/webapps/instance1". Alfresco Explorer works with no problem after this name change, however this makes Alfresco Share Login to fail.

I have been searching in the forum, and I have found that if you change the name of the folder and war file in tomcat/webapps from alfresco and alfresco.war for example to "instance1" and "instance1.war", then users will not be able to access the default installation of Alfresco Share as Alfresco Share will look for "http://localhost:8080/alfresco" which will not exist.

Which configuration files do I must modify to tell Share to access "http://localhost:8080/instance1" instead of "http://localhost:8080/alfresco".??

Thanks a lot in advance.

[afaust]

Hello,

look for share-config-custom.xml - there should be a configuration section for "Remote" in there with endpoint URL definitions. In that you need to change /alfresco to /instance1.

BTW: Why not upgrade to a more up-to-date Alfresco + Share? Version 3.0 was ages ago and there have been a lot of improvements.

Regards
Axel

[jlabuelo]

Hi Alex

Thanks a lot for your help, will give it a try. Regarding upgrading from 3.0 to 4.2 or to 5 as you say, it is something we are considering, however we have quite a few customizations in Alfresco 3.0 Explorer, and we are not sure if this will work in 4.2 or 5. We have created a set of wizards and processes in JAVA (all of them stored in an amp file) and we are not sure if this will work the same in Alfresco 4.2 or 5. What do you think?

Thanks once more!

[afaust]

Hello,

well, if you absolutely rely on those Alfresco Explorer customizations, then Alfresco 5 may be out of the question in the short term since Explorer has been removed in that version. Upgrading to 4.2 should be possible with some (minor) changes. Since you already packaged the old features in an AMP I reckon you aimed for relevatively loose coupling and should not depend on many internals / should not override any default screens - that would make it easier…
If by "processes" you mean jBPM workflows, then these are still supported in both 4.2 and 5 - but jBPM in general has been deprecated and may be removed in any future version.

In the long run (2+ years from now, when Alfresco 4.2 is waaay outdated), you may want to ponder re-factoring your custom UI parts and integrating them in the Share client.

Regards
Axel