Scalix Forums

It's out!!
I've already downloaded it and I'm reading the installation guide.
Coupla questions:

1. Do I need to uninstall my existing Scalix Connect (version 9.4.2) on each client PC and re-install the new one?
Or can I just do an auto-update?
Or will the 9.4.2 connector work with V10 server?

2. Is it really a seamless upgrade from 9.4.2 to 10?

3. I notice that the web interface for both SAC and SWA are now on port 80, not 8080. Will this interfere with my existing apache configs? I have another web-based app running on my server, and I don't want Scalix server to mess with it.

4. Will all my other Scalix configs remain when I upgrade? I presume I will have to bacckup the custom configs for smtpd.cfg etc., but what about server-side rules? What about SpamAssassin integration?

Dear Scalix Support,

I have just updated to Scalix 10 and have been eager to play with Scalix Connect for Evolution but can only find a binary i386 RPM for it.

I take it that a source tarball and/or a source RPM will be forthcoming from Scalix ?

Regards,
Terry

Hi leigh,

1. You do not need to uninstall Scalix Connect 9.4.2 to upgrade to 10. You can still configure /var/opt/scalix/nls/C/mapi.cfg to do an auto-upgrade. Remember to increase the file version number at the top of the file and to specify the correct minimum version number of Scalix Connect (10.0.0.352)

2. Yes, it is :)

3. Scalix Installer now automatically configures Apache to use jk connector for tomcat. To access SWA use http://hostname.domain.com/webmail and SAC http://hostname.domain.com/sac.

The installer also installs a new tomcat instance under /opt/scalix-tomcat/ and disables ports 8080 and 8443 for that instance. If your application is installed on a different tomcat instance you need to either move it to the newly installed instance and then uncomment the port config in the /opt/scalix-tomcat/config/server.xml (look for "DISABLED BY SCALIX INSTALLER") or change the default port number of the original instance and restart that instance.

4. In our testing all the configuration remained after an upgrade, but it is always a good idea to back it up :)

Hope that helps,
Yuri

Hi Tez,

The tarball is coming. Watch this space for updates.

http://www.scalix.com/products/scalixco ... ution.html

Cheers,
Yuri

Just installed Scalix 10 over 9
I had custom tomcat and mod_jk, so I had to edit config files monualy
now everything is working just fine :D

I'm currently running v9.4.2 Enterprise. I have Tomcat set to use SSL on port 8443, and I had to modify the server.xml file to make that happen. I am also using an external LDAP server to authenticate users.

1) Will I have to modify Tomcat to use SSL again, and will I still have to append :8443 to the URL (or remove the port mapping on my firewall that maps 443 to 8443 on the internal host)?

2) Will I have to re-configure the ual.remote|local and om_ldap.conf again, or will the config files be retained?

Thanks,
Kenny

Hi Kluss0,

1. Try accessing SWA via https://domain.com/webmail and if it comes up you don't need to do any additional tweaks. As explained before v10 scalix isntaller will configure apache/tomcat mod_jk connector automatically.

2. I believe the config files will be retained but backing custom config files up is always a good practice.


Cheers,
Yuri
Scalix Corp

crazy_russian wrote:You can still configure /var/opt/scalix/nls/C/mapi.cfg to do an auto-upgrade. Remember to increase the file version number at the top of the file and to specify the correct minimum version number of Scalix Connect (10.0.0.352)

I just upgraded our test server to v10. the file /var/opt/scalix/nls/C/mapi.cfg does not exist on that server (a full restore then upgrade from one of our live servers) or on either live server at v9.4.2.

How does auto-upgrade work?

nevermind - i read the instructions . heh.