Changing the default loading page advance client to basic client

[juan]

Hi,

how do i change the default page from the advanced client to basic client?

[mmorse]

Welcome to the forums,
Would making a url pointer to to http(s)://server.domain.com/h/ (or zimbra/h/) be enough?

Or there's a few 'disable advanced client' RFE's in.

[anthony.rasat]

I have add an entry in Zimbra Wiki on how to change default page Advanced Client mode to Basic Client mode. You can access it here

[mmorse]

awesome
also relavant/will be in v5: Bug 14181 - Force Basic HTML Client for Users based on COS
Bug 16134 - option to enable html client as default

[Rangga Kusuma]

i think this thread kind like i needed. but in my case I dont want to add new webserver (i dont want to add more presure to my server) and i want to add an alternative webclient (claros) for webclient UI (is this possible?...) which is using tomcat.

can u suggest what should i do. i know zimbra client is more than enough, but because my bos need a client that include jabber chat included, well u know the rest...

ok, back to my question what should i do to set in tomcat if port 80 is called than my webclient is viewed insted of zimbra default client and how to revert them if zimbra finally have jabber chat included.

thx in advance,

best regards
Rangga Kusuma

[mmorse]

Change the standard client to another port: Changing default page Advanced Client to Basic Client - ZimbraWiki You can then make url pointers to it (other links and/or your dns) and have the zimbra tomcat port 80 landing page redirect if you want.

This is already coming in v5: Bug 14181 - Force Basic HTML Client for Users based on COS

Check out the related blog post yesterday:
/blog/archives/2007/08/zimbra_standard_client_1.html

[Rangga Kusuma]

i think i have a problem. i try following procedure on the above wiki and yes after i execute ms [server_name] zimbraMailPort 8080. the setting on tomcat/conf/server.xml change from 80 to 8080.

but i cant get it up even after i use "tomcat restart" or even zmcontrol stop then start. only port 8080 was not active, for zimbraAdmin I still can access it using 7071. if i revert back to 80 all work as usual and i can access web page normally.

wandering why.... :?

[anthony.rasat]

Check if there is application already using port TCP/8080, e.g. Squid HTTP Cache usually using TCP/8080. Normally in Linux you can check it with command line (as root):

# lsof -P -i -n|grep 8080

Make sure there is no other application already using that particular port.

[Rangga Kusuma]

Check if there is application already using port TCP/8080, e.g. Squid HTTP Cache usually using TCP/8080. Normally in Linux you can check it with command line (as root):

# lsof -P -i -n|grep 8080

Make sure there is no other application already using that particular port.

thx for replying my question, antony.rasat .

ok about whether port 8080 is use, i have test it using "netstat -ap | grep :8080" but this return nothing. but if i use "netstat -ap | grep :7071" it returns showing 7071 is being use by java so it conclude that zimbraAdmin is up but zimbra still down.

but if i use "lsof -p -i -n| grep 8080" it returns like it should. after that i want to know what is lsof command use of. i only know that lsof is for list of open file. are u sure if lsof command returns true than port 8080 is realy up? because using netstat it returns nothing(my knowledge is low...).

but maybe there is more to set in the zimbra webapps? because if i revert back than port http is back up and normal.

please help.....

best regards,

rangga

[anthony.rasat]

About using lsof, I would say it is just matter of preference, I think I enjoy asking directly to kernel about child processes Your way would do just fine.

I'm gonna show you lsof result from my test machine. It's Pentium 4 2.4GHz, 1GB RAM, 80GB HDD running Zimbra Open Source edition 4.5.6_GA_1044.FC5 on Fedora Core 5 kernel Linux-2.6.20-1.2320.fc5. It contains 405 users and its Apache Tomcat constantly being pressured using Siege benchmark apps (emulate 150 concurrent user connections, ~1300 transactions per second). Its IP address is 192.168.10.70.

But first I'm gonna show you my iptables rules.

[root@mail ~]# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
[root@mail ~]#

None. Zip. "Look Ma, no firewall!" Check your firewall rule first, disable it if you have to.

Next, the processes.

[root@mail ~]# lsof -P -i -n
COMMAND   PID   USER   FD   TYPE DEVICE SIZE NODE NAME
sshd     1526   root    3u  IPv6   4876       TCP *:22 (LISTEN)
slapd   16783 zimbra    7u  IPv4 101972       TCP 192.168.10.70:389 (LISTEN)
slapd   16783 zimbra   20u  IPv4 115106       TCP 192.168.10.70:389->192.168.10.70:51086 (ESTABLISHED)
mysqld  17354 zimbra   13u  IPv4 102929       TCP 127.0.0.1:7307 (LISTEN)
mysqld  17479 zimbra   27u  IPv4 103239       TCP 127.0.0.1:7306 (LISTEN)
mysqld  17479 zimbra   40u  IPv4 784998       TCP 127.0.0.1:7306->127.0.0.1:50183 (ESTABLISHED)
clamd   18111 zimbra    5u  IPv4 111697       TCP *:3310 (LISTEN)
amavisd 18182 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18203 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18204 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18205 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18206 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18207 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18208 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18209 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18210 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18211 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18212 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18212 zimbra   14u  IPv4 115105       TCP 192.168.10.70:51086->192.168.10.70:389 (ESTABLISHED)
master  18260   root   11u  IPv4 103974       TCP *:25 (LISTEN)
master  18260   root   14u  IPv4 103977       TCP *:465 (LISTEN)
master  18260   root  101u  IPv4 104091       TCP 127.0.0.1:10025 (LISTEN)
java    19026 zimbra    5u  IPv6 784705       TCP *:80 (LISTEN)
java    19026 zimbra    7u  IPv6 784733       TCP *:7071 (LISTEN)
java    19026 zimbra   14u  IPv6 784939       TCP *:110 (LISTEN)
java    19026 zimbra   15u  IPv6 784940       TCP *:995 (LISTEN)
java    19026 zimbra   16u  IPv6 784941       TCP *:143 (LISTEN)
java    19026 zimbra   17u  IPv6 784942       TCP *:993 (LISTEN)
java    19026 zimbra   25u  IPv6 784997       TCP 127.0.0.1:50183->127.0.0.1:7306 (ESTABLISHED)
java    19026 zimbra   27u  IPv6 785015       TCP *:7035 (LISTEN)
java    19026 zimbra   30u  IPv6 785017       TCP *:7025 (LISTEN)

You should notice TCP 80 is listening for connection attempts. Now, I'm going to change web client port to TCP 8080 as in your situation.

[root@mail ~]# su zimbra
[zimbra@mail root]$ zmprov
prov> ms mail.kaltimpost.net zimbraMailPort 8080
prov> exit
[zimbra@mail root]$ tomcat restart
[zimbra@mail root]$ exit
[root@mail ~]# lsof -P -i -n
COMMAND   PID   USER   FD   TYPE DEVICE SIZE NODE NAME
sshd     1526   root    3u  IPv6   4876       TCP *:22 (LISTEN)
slapd   16783 zimbra    7u  IPv4 101972       TCP 192.168.10.70:389 (LISTEN)
slapd   16783 zimbra   11u  IPv4 796228       TCP 192.168.10.70:389->192.168.10.70:52801 (ESTABLISHED)
slapd   16783 zimbra   20u  IPv4 115106       TCP 192.168.10.70:389->192.168.10.70:51086 (ESTABLISHED)
slapd   16783 zimbra   22u  IPv4 796232       TCP 192.168.10.70:389->192.168.10.70:52802 (ESTABLISHED)
mysqld  17354 zimbra   13u  IPv4 102929       TCP 127.0.0.1:7307 (LISTEN)
mysqld  17479 zimbra   27u  IPv4 103239       TCP 127.0.0.1:7306 (LISTEN)
mysqld  17479 zimbra   40u  IPv4 796243       TCP 127.0.0.1:7306->127.0.0.1:33005 (ESTABLISHED)
clamd   18111 zimbra    5u  IPv4 111697       TCP *:3310 (LISTEN)
amavisd 18182 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18203 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18204 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18205 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18206 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18207 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18208 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18209 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18210 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18211 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18212 zimbra    5u  IPv4 103768       TCP 127.0.0.1:10024 (LISTEN)
amavisd 18212 zimbra   14u  IPv4 115105       TCP 192.168.10.70:51086->192.168.10.70:389 (ESTABLISHED)
master  18260   root   11u  IPv4 103974       TCP *:25 (LISTEN)
master  18260   root   14u  IPv4 103977       TCP *:465 (LISTEN)
master  18260   root  101u  IPv4 104091       TCP 127.0.0.1:10025 (LISTEN)
java    26893 zimbra    5u  IPv6 796220       TCP *:8080 (LISTEN)
java    26893 zimbra    7u  IPv6 796224       TCP *:7071 (LISTEN)
java    26893 zimbra   12u  IPv6 796227       TCP 192.168.10.70:52801->192.168.10.70:389 (ESTABLISHED)
java    26893 zimbra   13u  IPv6 796231       TCP 192.168.10.70:52802->192.168.10.70:389 (ESTABLISHED)
java    26893 zimbra   14u  IPv6 796235       TCP *:110 (LISTEN)
java    26893 zimbra   15u  IPv6 796236       TCP *:995 (LISTEN)
java    26893 zimbra   16u  IPv6 796237       TCP *:143 (LISTEN)
java    26893 zimbra   17u  IPv6 796238       TCP *:993 (LISTEN)
java    26893 zimbra   25u  IPv6 796242       TCP 127.0.0.1:33005->127.0.0.1:7306 (ESTABLISHED)
java    26893 zimbra   27u  IPv6 796245       TCP *:7035 (LISTEN)
java    26893 zimbra   30u  IPv6 796247       TCP *:7025 (LISTEN)

Web client is now listening on port TCP 8080.
Now let us see yours.