Need to change the way Alfresco creates links to the server

[davidan]

We have Alf Comm Ed 4.2, running on a virtualized CentOS 6.5 server. Also, We have recently integrated LDAP.

I have found that in all invitations and notices that Alfresco sends out, the link back to the server contains a URL that is formed with an IP address that seems to have been defaulted-in to the configuration during the install. The problem is that this IP address  (127.0.0…) is not the correct IP address for the server; consequently all links that alfresco send's out are broken.

I am looking for solid guidance on how to enter a correct value for how the server should be addressed. but I am afraid that any changes that I make to the Config will cause Alfresco to crash. Can someone point me to a reliable resource on how to safely affect changes to config settings that control how the server forms links back to itself?

[jpotts]

Have you tried setting alfresco.host and share.host in alfresco-global.properties? There is an entire section in alfresco-global.properties dedicated to setting host names, ports, and protocols for the alfresco and share apps.

Jeff

[davidan]

I have not I am afraid to jack-up my config file. I did make a change to allow SPMTP e-mail, but I am worried about wrecking my install. I think the thing that I need to work-on first is backing-up everything. but can you recommend a link to a reliable article for modifying these global properties?
…and thanks for the reply…We're just getting started and I'ma bit lost. 

[eswbitto]

If you look at your alfresco-global.properties file you will see something close to the top like this.

alfresco.context=alfresco
alfresco.host=somefqdn.domain.net
alfresco.port=443
alfresco.protocol=https

share.context=share
share.host=somefqdn.domain.net
share.port=443
share.protocol=https
‍‍‍‍‍‍‍‍‍‍‍

As long as your host name (I would avoid using just an IP address) is defined you shouldn't be having any issues.

[jpotts]

Thanks, ESWBitto.

Your caution is well-founded for certain things, and I admire your restraint, but this is a very painless and low-risk thing to test. Make a backup of your alfresco-global.properties, then make the changes, restart, and see if it worked. If it didn't, shutdown, copy over your backed up alfresco-global.properties and restart.

Or, you could always test the alfresco-global.properties file that ESWBitto is proposing on a completely separate server (make sure you change the database so you don't end up pointing at your production database!) to see if it works, then move the change into production. You ought to have a test server for doing that kind of thing anyway.

Good luck,

Jeff