"Connection refused' when accessing SWA rules wizard

[bluemike]

I just the post instructing me how to tuen on the rules wizard for SWA. I followed the instructions by editing the PARTNER.XML file to read as 'true' under 'ruleswizard'. Then I stopped and restarted Tomcat using the shutdown.sh and then the startup.sh commands.

Now the 'rules wizard' does indeed appear under the tools menu, but when I access it, I get a pop-up window and the error 'connection refused'. Is there a special port that has to be open for this? SWA has always worked before this....

[ScalixSupport]

Hi Mike,

There are a couple of things you need to look at. First, in your /etc/opt/scalix/webmail/partner.xml file is your rulesWizardURL= value valid? It should be your Scalix server's FQDN plus /Scalix/rw. For example, if your Scalix server is scalix.bluemike.com, then then your URL should be "http://scalix.bluemike.com/Scalix/rw". To test it, copy the URL and try to access it with your browser. Did you get a Scalix Rules Wizard logon page?

If not, perhaps you've moved Tomcat to be on socket 80. If you did that, did you also move Apache to be on socket 8080? If so, the correct URL would be something like: "http://scalix.bluemike.com:8080/Scalix/rw" in the example above.

Thanks,
Rachel

[bluemike]

I found the entry in the XML file you mentioned, and it is using teh FQDN as you said. As far as the Tomcat port, I don't know. I just accepted all the defaults during installation. I do know that when I access the admin page I have to put the":8080" after the domain to gain access.

I tried adding the :8080 to the FQDM as you described, but I could still not get to the rules wizard. Do I have to restart Tomcat or something?

[bluemike]

I have restarted Tomcat, and even went as far as to reboot the system. The result is that now I am getting different error message. Instead of just the 'connection refused' browser error, I am getting the Apache/Tomcat 404 error screen.

I guess that could be considered progress.

Any ideas of what to try now? All I want to do take specific monthly email from one user and always forward it to another. Is there a way to write that kind of rule manually on the server?

[ScalixSupport]

What platform have you installed this on ?

By default, the URL (as Rachel said) should be http://scalix.bluemike.com/Scalix/rw.

The Rules Wizard doesn't use tomcat so you should be able to enter that URL into the browser and have the Rules Wizard login screen displayed.

If this doesn't get displayed, i.e. you get a 404 Apache error, this would indicate that the Apache configuration is not correct.

First of all, try stopping and restarting Apache in case the configuration changes that Scalix made were not picked up.

For RHEL and FC, there will be a file in /etc/httpd/conf.d called scalix-web-client.conf. This will be a symbolic link to /opt/scalix/global/httpd/scalix-web-client.conf.

For SuSE, the file /etc/sysconfig/apache2 should contain reference to /opt/scalix/global/httpd in the APACHE_CONF_INCLUDE_DIRS variable.

If this isn't present, try running the script /opt/scalix/bin/omwebconf. This should add the appropriate configuration settings. This will also stop/start Apache again.

Cheers

Dave

[ScalixSupport]

Hi Mike,

You should change it back in the partner.xml so it doesn't have the :8080. Once done, restart tomcat and you should be back to the original error you were getting before.

Follow Dave's instructions to verify that the Apache web server is configured and running on your server. If you type:

ps -aef|grep -i apache

do you see several lines that have /usr/sbin/httpd or /usr/sbin/httpd2... at the end of them? If not, then the Apache web server isn't running.

Once you're started it, try going to http://scalix.bluemike.com/Scalix/rw (or whatever your Scalix server is called) and you should get a Scalix Rules Wizard logon page. Now, go into SWA and try Tools, Rules Wizard. You should the Rules Wizard page.

Thanks,
Rachel

[bluemike]

Kudos to all the support people who helped me on this!

I am rules-wizarding the crap out of my users now!

I changed the XML file, removing the :8080 part. And started Apache. I figured it running since I was able access webmail, but I guess it wasn't this whole time. You guys didn't actually tell me how to stop and restart Apache, but I Googled it and found out how. It still wasn't working, so I just rebooted the server (I couldn't remember how to force Scalix to restart) and now it works awesomely!!!!

Thanks again to all you guys and gals at Scalix.