Previous Contents Index Next |
iPlanet Portal Server: Instant Collaboration Pack Release 3.0 Installation Guide |
Chapter 4 Configuring iPlanet Instant Messenger
This chapter describes the steps to configure a client for iPlanet Instant Messenger.
iPlanet Instant Messenger Launch Overview
Requirements to Run iPlanet Instant Messenger
iPlanet Instant Messenger Launch Methods
Configuring a Windows Client with Java Web Start
Configuring a Windows Client with the Java Plug-in
Configuring a Solaris Client with Java Web Start
Invoking iPlanet Instant Messenger
Removing iPlanet Instant Messenger
iPlanet Instant Messenger Launch Overview
This section describes what happens when iPlanet Instant Messenger is launched, starting with the client entering a URL on the web server.
Launching iPlanet Instant Messenger from Java Plug-in
If you are using the JavaTM Plug-in version of iPlanet Instant Messenger, then the iim.html file performs the following actions:
Downloads the following .jar files:
Passes to the iPlanet Instant Messenger applet the name and port of the server where the multiplexor is running.
The default iim_mux.listenport is used by the applet, unless a different port was chosen at installation, in which case that port is passed to the application.
Launching iPlanet Instant Messenger from Java Web Start
If you are using the JavaTM Web Start version of iPlanet Instant Messenger, the iim.jnlp file performs the following actions:
Downloads two .jar files:
References the iimres.jnlp file, which downloads iimres.jar.
Passes to the application the name of the server where the multiplexor is running.
If a port other than the default was chosen at installation, it is passed to the application.
Launching iPlanet Instant Messenger from iPlanet Portal Server
If you are launching iPlanet Instant Messenger as an iPlanet Portal Server application, the following occurs:
The user clicks the iPlanet Instant Messenger link (either using Java Plug-in or Java Web Start) in the iPlanet Portal Server Desktop Application channel.
The servlet file, iimcservlet.jar, uses the existing session ID from iPlanet Portal Server to set up a session with the iPlanet Instant Messaging multiplexor. The launch servlet fills in information taken from when the user logged into iPlanet Portal Server, for example: username, uid, token, if secure or not (SSL), whether the Java Plug-in or Java Web Start is being used, codebase, and so forth.
iPlanet Instant Messenger is launched.
iPlanet Instant Messenger connects to the iIM multiplexor and passes in the necessary credentials.
Requirements to Run iPlanet Instant Messenger
For the most recent information about software requirements for this product, see the iPlanet Portal Server: Instant Collaboration Pack 3.0 Release Notes, online at the following site:http://docs.iplanet.com/docs/manuals/portal.html
iPlanet Instant Messenger Launch Methods
iPlanet Instant Messenger, written in Java, is iPlanet Instant Messaging Server's client that can be configured as either browser-based, running as an applet, or independent of a browser, running as a Java Web Start application.The two ways to configure your client are:
Using Java Web Start (Solaris and Windows) - iPlanet Instant Messenger is launched from Java Web Start, which is an application launcher for Java 2 technology-based applications that are written to be web deployed. Once iPlanet Instant Messenger launches, your browser can be closed or used to locate other URLs without effecting the iPlanet Instant Messenger session.
If you will have Windows clients, the section below provides information to help you decide which configuration method is best for your site.Using the Java Plug-in (Windows only) - The applet is launched from the Java Plug-in, which is a code extension to the browser. To keep the iPlanet Instant Messenger session active, the browser window from which the applet was launched must remain open and cannot be used to locate any other URL.
Note Solaris clients must use the Java Web Start configuration. Windows clients can choose to implement either the Java Web Start or the Java Plug-in configuration.
Note To launch iPlanet Instant Messenger in the iPlanet Portal Server environment, click the appropriate link in the Applications channel in the iPlanet Portal Server Desktop.
Windows Launch: Java Web Start vs. Java Plug-in
The primary benefit of using the Java Plug-in is ease of installation. Microsoft Internet Explorer 5.0 will self-configure the plug-in the first time you launch iPlanet Instant Messenger by entering the appropriate URL in your browser. For Netscape Communicator, the plug-in must first be downloaded and installed.Once the iPlanet Instant Messenger session is established using the plug-in, the browser must be dedicated to its use; that is, you can not locate any other URLs with this browser window, nor can you shut down the browser without terminating the iPlanet Instant Messenger session. Inadvertently losing the iPlanet Instant Messenger connection is potentially very inconvenient, especially for conferenced chat sessions.
To launch iPlanet Instant Messenger using Java Web Start, both the Java Runtime Environment and Java Web Start must be downloaded and installed. Thus, the one-time configuring of your Windows client with Java Web Start will be more time consuming than with Java Plug-in. However, using Java Web Start might prove far more convenient in the long run due to its browser independence.
With Java Web Start, you can shut down the browser, or use it for locating another URL without losing your iPlanet Instant Messenger connection.
Java Web Start supplies other benefits by:
Providing Java Runtime Environment management capabilities, so that Java Runtime Environment does not interfere with other runtime environments required by other applications.
In summary, if browser independence is important, then configure the Windows client using Java Web Start. (See "Removing iPlanet Instant Messenger" for more information.)Automatically updating any .jar files that have changed on the server since the last run.
Being only slightly larger than the Java Plug-in.
Adding a desktop icon for iPlanet Instant Messenger for quick loading.
However, if initial ease of installation is of primary importance, and keeping a dedicated browser open for the iPlanet Instant Messenger session is not a problem, then configure the Microsoft Windows client with the Java Plug-in. (See "Configuring a Windows Client with the Java Plug-in" for more information.)
Configuring a Windows Client with Java Web Start
Use the following steps to configure a Windows client with Java Web Start:
Download the Java Web Start for Windows self-extracting file from the following location. You are not required to download and install the JRE separately. It is bundled into Java Web Start.
Install the Java Web Start.
- http://java.sun.com/products/javawebstart/download-windows.html
- Save the .exe file to a local disk directory, such as c:\temp.
Open the directory where the .exe file was saved.
See "Invoking iPlanet Instant Messenger" to run the iPlanet Instant Messenger client.Double click javaws-1_0_1-win-*.exe to start the install process.
- Follow the directions provided by the installer. It will update the Microsoft Windows registry and add an icon to your desktop. When done, you are then ready to run the iPlanet Instant Messenger client.
Configuring a Windows Client with the Java Plug-in
The following steps describe how to configure a Windows client with the Java Plug-in:
Download the Java Runtime Environment 1.3 for Windows, which includes the Java Plug-in, and save it to a local disk directory, such as c:\temp.
Double click the saved .exe file to start the install process.
- http://java.sun.com/products/archive/j2se/1.3.0/jre/index.html
- If you are using the Internet Explorer browser, it will handle this for you.
See "Invoking iPlanet Instant Messenger" to run the iPlanet Instant Messenger client.
- Follow the directions provided by the installer. When done, you are ready to run the iPlanet Instant Messenger client.
Configuring a Solaris Client with Java Web Start
Use the following steps to configure a Solaris client using Java Web Start. You will need to download and install both the Java Runtime Environment and Java Web Start software.
Note You should create two directories to hold the Java Runtime Environment and Java Web Start software. This example uses the directories /home/user1/JRE and /home/user1/JWS.
Download the Java Runtime Environment 1.3 for Solaris self-extracting binary file (j2re1_3_0-solsparc.bin) to a local disk directory, such as /home/user1/JRE, from the following location:
Download the Java Web Start .zip file to a local disk directory, such as /home/user1/JWS, from the following location:
- http://java.sun.com/products/archive/j2se/1.3.0/jre/index.html
Note While Java Web Start works with JRE 1.2, it is not recommended because of potentially serious performance issues.
Install the JRE. (For more information, download the Java Runtime Environment file, README.sparc.)
- http://java.sun.com/products/javawebstart/download-solaris.html
Change to the directory where you saved the self-extracting JRE binary file, for example:
Install Java Web Start.
Make sure that you set execute permissions on the JRE self-extracting file before trying to install, for example:
- cd /home/user1/JRE
Run the self-extracting file to install the JRE software, for example:
- chmod +x j2re1_3_0-solsparc.bin
- This example is for Java Runtime Environment 1.3.0. Be sure to check the exact file name that you downloaded.
Write down the full path to the subdirectory where the JRE is installed. You will need this path in Step 4.
- ./j2re1_3_0-solsparc.bin
- The JRE installs itself into the directory where you saved it earlier, in a subdirectory called j2re1_3_0.
- In this example, the path would be /home/user1/JRE/j2re1_3_0.
Change to the directory where you saved the Java Web Start .zip file, for example:
Close and exit any browsers to allow new registrations to be picked up.
Unzip the file, for example:
- cd /home/user1/JWS
Run the Java Web Start install script, install.sh. For example, to install JWS on the local disk as /home/user1/javaws:
- unzip javaws-1_0_1_01-solsparc-int.zip
- This example is for Java Web Start version 1.0.1_01. Over time, a newer version might be posted, so be sure to check the exact file name that was downloaded.
- Java Web Start files are extracted, including one called install.sh.
- cd /home/user1
- /home/user1/JWS/install.sh
- The installer asks you to supply the path to the Java Runtime Environment. You should have noted this path in Step 3.
See "Invoking iPlanet Instant Messenger" to run the iPlanet Instant Messenger client.
- Now you are ready to run iPlanet Instant Messenger.
Invoking iPlanet Instant Messenger
To invoke iPlanet Instant Messenger, you can use:
The index.html file, provided by iPlanet Instant Messenger. The index.html file provides buttons to launch both the Java Web Start and Java Plug- versions of iPlanet Instant Messenger. This file also has links to iPlanet Instant Messenger documentation.
A modified version of index.html, which you edit to your site's preferences.
An web page of your own design that provides a link to the version of iPlanet Instant Messenger you want your users to have access to.
An valid URL for iPlanet Instant Messenger, entered in the browser.
To Invoke iPlanet Instant Messenger
Use the following URL to invoke iPlanet Instant Messenger.
Depending on which version of iPlanet Instant Messenger Java Web Start or Java Plug-inyou are using, the following happens:
- http://webserver:webserverport/subdirectory/filename
- In this URL,
- For example, to invoke iPlanet Instant Messenger on Windows using Java Web Start, where the web server is i-zed.com, using port 123, with the default installation directory for the client files, the URL would be:
- http://i-zed.com:123/iim.jnlp
- To invoke iPlanet Instant Messenger on Windows using the Java Plug-in, where the web server is company22.com, using the default port (80), with an installation directory of iim, the URL would be:
- http://company22.com/iim/iim.html
Java Web Start - The first time you invoke the application, Java Web Start will download it into its cache, and a Security dialog will be presented. Accept the Security dialog.
For subsequent invocations of iPlanet Instant Messenger, you can:Java Plug-in - The first time you invoke the Java Plug-in, a Java Plug-in Security Warning window opens, asking you if you want to run the signed applet.
- You must choose between: Grant this session, Deny, or Grant always. If you choose to grant for only this session, this window will open every time you invoke the plug-in, until you choose Grant always. If you choose Grant always, this window will not open again.
Add the URL to your favorites.
Launch the application using the Java Web Start launcher icon on your desktop (Java Web Start version only).
Use the shortcut on your desktop. (Java Web Start asks if you want to put the icon on your desktop after the first or second time you invoke iPlanet Instant Messenger. Whether it asks the first or second time is a preference that can be set from the Java Web Start Edit menu.)
Removing iPlanet Instant Messenger
This section describes how to remove iPlanet Instant Messenger from both Solaris and Windows client platforms. Should you want to remove the application from your client machine, follow the platform appropriate procedure below.
To Remove iPlanet Instant Messenger from Windows (Java Web Start)
Launch Java Web Start Application Manager.
From the Applications menu, select:
- For example, double-click the Java Web Start icon on your desktop.
Close Java Web Start Application Manager.
To Remove iPlanet Instant Messenger from Windows (Java Plug-in)
Delete the java_plugin_AppletStore folder.
- For example, in Windows Explorer:
Click the java_plugin_AppletStore folder.
From the File menu, click Delete.
- For example, on Windows 98 the folder is located in: c:\WINDOWS\java_plugin_AppletStore
To Remove iPlanet Instant Messenger from Solaris
Launch Java Web Start Application Manager.
From the Applications menu, select: Remove from Cache.
- For example, double-click the javaws icon in the javaws directory.
Uninstalling Java Web Start or Java Runtime Environment
To uninstall either Java Web Start or Java Runtime Environment from your client machine, follow the platform appropriate procedure below.
To Uninstall Java Web Start or Java Runtime Environment on Windows
From the Start menu, choose Settings and then Control Panel.
Click the Install/Uninstall tab.
From the list of products, select either Java Web Start or Java Runtime Environment, and click Add/Remove.
To Uninstall Java Web Start on Solaris
Delete the javaws directory.
Edit your ~/.mailcap file.
- Remove any lines containing application/jnlp or application/x-java-jnlp-file.
- Remove any lines containing application/jnlp or application/x-java-jnlp-file.
To Uninstall Java Runtime Environment on Solaris
Delete the directory in which you installed the Java Runtime Environment. The default directory is: j2re1_3_1.
Troubleshooting iPlanet Instant Messenger Problems
Use the following information to help solve issues with client installations:
Difficulty Loading Resources - Proxy Settings
In a network environment, which has a firewall between your computer and the internet, if the Java Web Start has not been configured with the right proxy settings, you can experience difficulty loading resources.Java Web Start can typically pick proxy settings up automatically by querying the system or the default browser. However, if the settings are configured using a JavaScriptTM file this is not possible.
You can set the proxies manually by using the Preference panel in Java Web Start's Application manager.
Java Web Start Does Not Start - mime.types for JNLP
If, instead of Java Web Start starting, you get the iim.jnlp file displayed in the browser, then you need to edit the web server's mime.types file to include a line for JNLP.
For iPlanet Web Server, the default location for this file is:
For Apache Web Server, the mime.types file, located in the Apache Web Server configuration directory (its location is site-specific), should be edited to include the line:
- /usr/netscape/server4/https-xxx/config/mime.types
- where xxx is your web server instance name.
- If not already present, add the following line:
- type=application/x-java-jnlp-file exts=jnlp
- Restart the http-xxx server for this change to take effect.
- application/x-java-jnlp-file jnlp
Previous Contents Index Next
Copyright © 2001 Sun Microsystems, Inc. All rights reserved.
Last Updated December 04, 2001