Installation of a properly executing Jabber Applet requires all applet related programs to be installed on the same machine. This is a general applet requirement, not a specific Jabber Applet requirement. In short (1) An applet must be served from the same machine that the html page that loads it and (2) the Jabber Applet must connect to a Jabber Server running on the same machine as itself.

Or a little more detailed explanation:

1. An applet gets served up by a web server
2. For security reasons the applet can ONLY establish connections with the web server that it came from
3. When a user calls the applet and tries to logon to Jabber it can only connect back to the web server
4. Jabber talks to clients over port 5222, but if there is no jabber server running on the same machine that is hosting the web server, then port 5222 will not be open and the applet will fail to connect with anything

1. Network:
• Port 80 open: The Web server communicates with browsers via port 80. The html page containing the applet (and the applet) will be loaded in the browser via this port.
• Port 5222 open: Clients connect to the server on TCP port 5222. The connection from the client to the server is persistent and maintains the presence state of the client after authentication. The server delivers all data to the client via this socket.


2. Jabber Server: used by the applet to connect to the jabber system.. Each server machine must provide its own Jabber Applet (if an applet client is to be used). For example an applet served from the jabber.org server must only connect to the jabber.org jabber server. An attempt to connect a jabber.org applet to another jabber server (such as jabber.com) will not be successful. note: this constraint doesn't prevent jabber.org users from communicating with jabber.com users via the applet.



3. Web Server: primary purpose is to deliver the html page (that in turn loads the applet).



4. Jabber Applet: is built and stored in the JabberApplet.jar file. This file is accessed using an html file as described below.



5. HTML page: primary purpose is to load the applet. The HTML page can also be used to surround the applet with miscellaneous text and graphics. Note: (1) this html file must be loaded from the Jabber Server machine (creating a local copy of this html file will not work), (2) Netscape has a problem with applets loading inside <table> tags.
• Loading the applet: The applet is loaded using the following text in an html page:

  <APPLET ARCHIVE="JabberApplet.jar" CODE="org/jabber/applet/JabberApplet.class" HEIGHT=200 WIDTH=200 VIEWASTEXT>
  <param name="xmlhostname" value="jabber.myserver.org">
  </APPLET>

  The HEIGHT and WIDTH settings are optional.

  If you want the applet to show up in an extra browser window without menu bars, put the code above in an applet.html and use

  <a href="javascript:(function(){window.open('http://myserver.net/applet.html','JabberApplet','width=200,height=300,location=no,menubar=no,resizable=no,scrollbars=no,status=no,toolbar=no'); })();">JabberApplet</a>

• Applet parameters: Optional parameters passed to the applet are used as follows:
• xmlhostname - The xmlhostname must be set to the Jabber server's hostname (such as jabber.myserver.org). Note Java Applets normally can only open connections to the server they are loaded from so the web server and the Jabber server have to match. When input parameters xmlhostname, user and pwd are all set the applet will automatically log the user into the jabber system. With the setting -host- the applet tries to determine the hostname of the web server it was loaded from as the Jabber server. This setting seems to cause trouble with some setups so avoid it.
• defaultColor - If a particular Background color is desired a defaultColor parameter must be included: <param name="defaultColor" value="R,G,B"> where R=red component, G=green component and B=Blue component. The R, G, B values must be integer 0-255 (not hex).
• help - Help documentation is not part of the JabberApplet. If help documentation is available it will be referenced via the URL passed in this parameter. <param name="help" value="http://jabber.com/applet/help.html">
• user - Automatic setting of the JID username is accomplished via setting of the user parameter. <param name="user" value="username">. When input parameters xmlhostname, user and pwd are all set the applet will automatically log the user into the jabber system.
• pwd - Automatic setting of the password is accomplished via setting of the pwd parameter. Setting both user and pwd parameters causes the applet to autologon using the inputs. <param name="user" value="username">. When input parameters xmlhostname, user and pwd are all set the applet will automatically log the user into the jabber system.