...ummm, about that suggestion of being a "newbie"...well, yea - but don't worry we were all there once (except Dave, he learned Linux while in the womb).
That output from your "ps" would explain it. Tomcat isn't running - and it needs to be for SWA and SAC to work. You haven't set Tomcat to start automatically upon reboot. In the Admin Resource Kit (it's a subdirectory of the Scalix software, created when it was untarred), there is a file called Tomcat. Open it and read it, follow the instructions, it will explain how you can make Tomcat start automatically.
In the interim, you can go to the directory where tomcat was installed (typically this is something like /var/opt/jakarta-tomcat-5.0.28). Go the the /bin directory under the jakarta-tomcat-5.x.x directory and execute...
./startup.sh
That will get Tomcat running for this session. If you then do your "ps -ef | grep tomcat" you should see output like...
Code: Select all
[root@mail /]# ps -ef | grep tomcat
root 2607 1 0 Feb07 ? 00:00:19 /usr/java/j2sdk1.4.2_08/bin/java
-Djava.endorsed.dirs=/var/opt/jakarta-tomcat-5.0.28/common/endorsed -classpath
/usr/java/j2sdk1.4.2_08/lib/tools.jar:/var/opt/jakarta-tomcat-5.0.28/bin/bootstr
ap.jar:/var/opt/jakarta-tomcat-5.0.28/bin/commons-logging-api.jar -Dcatalina.bas
root 13523 13478 1 15:44 pts/2 00:00:00 grep tomcat
Notice there's two processes, the Tomcat process, and then the second one, which is really the "ps -ef | grep tomcat" process itself.
Hope that helps, let us know if you need anything else...
Cheers
Karl