iPlanet Portal Server: Instant Collaboration Pack Release 3.0 Installation Guide: Chapter 2 Installing iPlanet Instant Messaging Server on Solaris

Previous Contents Index DocHome Next

iPlanet Portal Server: Instant Collaboration Pack Release 3.0 Installation Guide

Chapter 2 Installing iPlanet Instant Messaging Server on Solaris

This chapter describes the steps to install iPlanet Instant Messaging Server on Solaris. Run the setup program by either using the graphical interface installation or using the command-line installation.
This chapter contains:

Installation Scenarios on Solaris

Using the Graphical Interface Installation on Solaris

Using the Command-Line Installation on Solaris

Post-Installation Steps for Solaris

Installation Scenarios on Solaris

You can install and configure iPlanet Instant Messaging Server on the Solaris platform in one of two ways:

As part of the iPlanet Portal Server environment, making iPlanet Instant Messenger available as an application in the iPlanet Portal Server Desktop Applications channel

As a standalone server
When installing iPlanet Instant Messaging Server with iPlanet Portal Server, you can either install all components on one host, or install iIM Server on one host and iPlanet Portal Server on another host.

Using Separate Hosts for iPlanet Instant Messaging Server and iPlanet Portal Server Overview

Most likely, you will install iPlanet Instant Messaging Server and iPlanet Portal Server components on the same host. However, this is not a requirement. You might have installed iPlanet Instant Messaging Server as a standalone server, and now you want to have it function within a portal framework. Or, you might want to separate the two servers for other reasons, such as load balancing.
In this type of configuration, you install iPlanet Instant Messaging Server and a "disabled" (not running) iPlanet Portal Server on one host, and the iPlanet Instant Messaging Server client component and an "enabled," or running version of iPlanet Portal Server on the other host. This is necessary because iIM Server authenticates the user's portal session using the iPlanet Portal Server session APIs.
Following are the high-level steps to install and configure iPlanet Instant Messaging Server and iPlanet Portal Server on separate hosts. In these steps, iim.i-zed.com represents the iIM Server host, and portal.i-zed.com represents the iPlanet Portal Server host.

On the iIM Server host iim.i-zed.com:

Install iPlanet Instant Messaging Server.

Install just the server component for iIM Server, and not the client component, which you will install on the iPlanet Portal Server host in Step 2.

Run the iIM Server setup program. At the Component Selection window, choose to install only the iPlanet Instant Messaging Server component.

Install iPlanet Portal Server.

You will not "run" this portal installation. It is necessary for the iPlanet Instant Messaging server to be able to access the remote iPlanet Portal Server profile service on the portal host. See the instructions at:

http://docs.iplanet.com/docs/manuals/portal.html

Note Specify the following during the iPlanet Portal Server installation:

"Yes" to Multi-server deployment.

This server does not run the profile service.

The profile service is located at hostB:portB, where hostB is the iPlanet Portal Server host in Step 2 below.

On the iPlanet Portal Server host portal.i-zed.com:

Assuming that iPlanet Portal Server has already been installed, install the iIM Server client component.

Run the iIM Server setup program. At the Component Selection window, choose to install only the iPlanet Instant Messenger component.

During the installation specify iim.i-zed.com as the host on which iPlanet Instant Messaging server is running.

On the iIM Server host iim.i-zed.com, edit the iPlanet Portal Server /etc/opt/SUNWips/platform.conf file. Change the value for ips.naming.url=http://iim.i-zed.com:portA/namingservice to ips.naming.url=http://portal.i-zed.com:portB/namingservice.

where portA is the portal server port for iim.i-zed.com, and portB is the portal server port for portal.i-zed.com.

You only need to change this manually if you did not specify the following during the iPlanet Portal Server installation on host iim.i-zed.com:

"Yes" to Multi-server deployment.

This server does not run the profile service.

The profile service is located at hostB:portB, where hostB is the iPlanet Portal Server host in Step 2 above.

On the iPlanet Portal Server host portal.i-zed.com, specify the name of the iPlanet Instant Messaging server by changing the servlet.iimlaunchservlet.initArgs attribute in the servlets.properties file of the web server.

You only need to do this if you did not specify host iim.i-zed.com as the machine on which iPlanet Instant Messaging server is running during the installation.

You can either stop the iPlanet Portal Server process on iim.i-zed.com, or leave it in a running state.

Restart the iPlanet Instant Messaging server on host iim-i.zed.com for the changes to take effect.

Using the Graphical Interface Installation on Solaris

The following steps describe how to use the graphical user interface installation program to install iIM Server.

Log in as root. You must have superuser privileges (that is, be logged in as root) to run the installation program.

Create a directory (such as /tmp/imsvr) on the server that will host iPlanet Instant Messaging Server installer. Download (or copy) the iIM Server installation file to that directory from the following location:

http://www.iplanet.com/downloads/download

Make sure that the download directory has adequate disk space to store the extracted files.

Caution
Do not download the installer package, nor extract it, into the directory where you plan to install the product. This will result in installation failures.

Change to the directory where you downloaded or copied the file and extract the contents. For example:

cd /tmp/imsvr

gunzip -c filename.tar.gz | /usr/bin/tar xvf -

where filename identifies the name of the file you downloaded or copied.

Note You must use /usr/bin/tar. This program should be the tar utility that is distributed with your operating system and not a third party tar utility, such as gnu.

In the installation directory in which you untarred the iIM Server archive file, type:

./setup

Note Do not run the installation in the background.
If you are installing on a remote machine, set the DISPLAY variable to your host name. For example in C shell:
setenv DISPLAY myhost:0.0

The Welcome window opens. Click Next to continue.

The Software License Agreement window opens.

Read the license agreement and click Yes (Accept License) to accept it and continue. (If you click No, the installation program will end without installing iIM Server.)

The Software Requirements window opens, listing other product dependencies.

Before continuing with this installation, you should already have installed:

iPlanet Portal Server, if you are installing iPlanet Instant Messaging Server in a portal deployment. (You do not need to install iPlanet Portal Server if you are installing iPlanet Instant Messaging Server in standalone mode.)

A web server, such as iPlanet Web Server, to serve up HTML to the client. (Portal deployments use the web server that ships with iPlanet Instant Messaging Server.)

A directory (LDAP) server, such as iPlanet Directory Server, for user authentication. (Ignore this requirement if you are using iPlanet Portal Server's internal directory.)

A messaging server (SMTP service), such as iPlanet Messaging Server, to send alerts by email when users are not currently logged in to iIM Server and are unable to receive instant messages.

Optionally, you may want to install:

A provisioning tool, such as iPlanet Delegated Administrator.

Note See the iPlanet Portal Server: Instant Collaboration Pack 3.0 Release Notes for information on supported software and versions.

If you have these products installed, click Next to continue the installation. Otherwise, Click Exit to quit the installation and install and configure the necessary products. Then restart the installation.

Two informational windows open saying the program is determining and verifying the system's host name and DNS domain name. On faster systems, you might not see these windows.

The installation program is automatically detecting the host name and DNS domain name of the system on which you are installing the server. If the installation program cannot detect the host name or DNS domain name, the "Unable to make network connection" window opens. Be sure that the host name and DNS domain name specified are correct, then click Next to continue the installation. The installation program will then try to establish a network connection using these values.

Note The Host Name or Domain Name fields will be blank if the installation program is unable to detect these values. In this case, you must enter a valid host name or DNS domain name, or both.

If a network connection cannot be made using the new values, you are asked again to supply a valid host name and DNS domain name.

If you have a previous version of iIM Server installed on this system, the Upgrade or Reinstall Existing Installation window opens.

Whether you decide to upgrade or reinstall, all running iIM Server services must be stopped. The installation program attempts to stop them for you. If it is unable to verify that all services are stopped, it opens a warning window. The warning window advises you that the installation may not be successful if any services are still running. If you are sure that all services have been stopped, click Continue; otherwise, click Cancel to return to the installation program. Stop all services before proceeding with the installation.

Caution
Be sure to stop all existing iIM Server services before proceeding with either the upgrade or reinstallation.

Upgrade vs. Reinstall Considerations

Table 2-1 summarizes the difference between upgrading and reinstalling.

Table 2-1 Upgrade vs. Reinstall Considerations

Type of Installation

Enables Changing Configuration Options?

Enables You to Add a Component to This Server?

Preserves Existing Database and Configuration?

Should You Back Up Existing iIM Server Files?

Upgrade

No.

No.

Yes.

Not necessary, but should be done as a precaution.

Reinstall

Yes. You can change all installation options.

Yes.

No.

Depends: Back up any customizations, configurations, or databases you want to keep.

Upgrading

Choose to upgrade only if you do not need to change any installation options.

For complete instructions on upgrading your system to a new version, see Appendix B "Upgrading iPlanet Instant Messaging Server."

Reinstalling

To remove the existing installation and install the new version, you must check the Reinstall Existing Components checkbox at the bottom of the window, and then click Next.

The Confirm: Reinstall message window opens asking if you want to continue with the reinstall operation. Click Continue (reinstall) to continue the operation, or click Cancel to return to the Upgrade or Reinstall Existing Installation screen, where you can reselect your option or exit the installer.

Caution

Check the Reinstall box only if you want to completely remove the existing installation and reinstall the new version from scratch.

If you choose to reinstall and want to keep your existing databases, configuration files, such as user profile data and preferences, server access control files, and any site-specific customizations, such as client index.html changes and images, you must back them up before proceeding with the reinstall.

Caution
If you choose the reinstall option, before proceeding, back up any existing databases, user profiles and preferences, and any other files you have customized.
Back up the following directory and its subdirectories (if you use the default directory, $RUNTIMEDIR = /var/opt/SUNWiim/default):
$RUNTIMEDIR/db
In addition, the following files are the most commonly customized files and should be included when you back up your files.
Config Files (if you use the default directories, $BASEDIR = /etc/opt/SUNWiim/default/):
$BASEDIR/config/iim.conf
$BASEDIR/config/acls/sysAdmin.acl
$BASEDIR/config/acls/sysTopicsAdd.ac
$BASEDIR/config/acls/sysRoomsAdd.acl
$BASEDIR/config/acls/sysSendAlerts.acl
$BASEDIR/config/acls/sysWatch.acl
$BASEDIR/config/acls/sysSaveUserSettings.acl
HTML Files (if the defaults were used, $HTMLDIR = /opt/SUNWiim/html):
$HTMLDIR/iim.html
$HTMLDIR/iim.jnlp
$HTMLDIR/index.html
$HTMLDIR/iimres.jnlp
$HTMLDIR/iimres.jar

The Component Selection window opens.

Select the software components to be installed (default is both):

iPlanet Instant Messenger - This component includes the client software and online help.

iPlanet Instant Messaging Server - This component includes both the server and the multiplexor software.

If you choose to install this component, with or without the client component, additional screens are presented to you. These steps are indicated as such in this guide.

Note If you are not installing iPlanet Instant Messaging Server on the same host as your web server, you should only install the server component at this time, and not the client component. Then, when this installation is over, start the installation process again and install the client component on the web server host. This is necessary so that the iPlanet Instant Messenger HTML, .jar, and online help files reside at the web server document root (the directory from which the web server is serving files).
If you choose not to install the client component at the web server document root (you will be asked to specify the directory in Step 20), you must edit the iim.jnlp and iimres.jnlp files to reflect the proper codebase.
For more information on customizing these files, see Chapter 3 in the iPlanet Portal Server: Instant Collaboration Pack Release 3.0 Administrator's Guide.

When you have finished making your selections, click Next to continue.

The Select Install Directory window opens.

If you do not want to install in the default directory, specify the directory where you want to install the iIM Server software. The default is /opt.

If you want to select another directory, click Browse, then select a directory and click OK.

If the directory you selected does not exist, a message window opens and you can either:

Click Create Directory to install iIM Server in the specified directory and continue the installation.

Click Choose New to return to the Select Install Directory window where you can select another installation directory.

When you have finished making your selection, click Next to continue.

The iPlanet Instant Messaging Services Configuration window opens.

If you do not want the default values, specify the following configuration information:

Domain Name. The logical instant messaging domain name you want this iIM server to support. If you are serving instant messaging to a wider group of people, this is not normally the TCP/IP host name of your system. This domain name does not have to be in the DNS. It is a name used by iIM Server, on this server only, to identify itself and its users.

Multiplexor Port. (Default is 9999.) The port number on which the iIM server accepts connections from multiplexors. The default port number should work for most installations.

Web Client Port. (Default is 9909). The port on which the multiplexor accepts connections from client requests. The default port should work for most installations. If you specify a port other than the default, iIM Server users will need to explicitly include this port number at login.

Disable Server Check Box. Check this box if you are installing the iIM Server on another (remote) host and you only want this local server to have the multiplexor enabled.

Remote Server Hostname. The host name where you are installing the iIM Server software. If you checked the "Disable Server" box then this is the remote server, otherwise it is the local host name.

If you want to use values other than the defaults, enter them now.

Note When installing just the client component, you see only the options for the Web Client Port (Multiplexor port accepting connections from clients) and the Remote Server Hostname.

If a port is already being used by another process running on the system, a Server (or Multiplexor) Port in use message window opens, giving you two choices:

Click Accept to keep the settings. After installation and before starting the server, you must free the port in use on the other service.

Click Choose New to be returned to the Instant Messaging Services Configuration window. Select a port number other than the one in use.

When you have finished making your selections, click Next to continue. You might experience a short delay while the installer works in the background.

(Optional, client installations only) The Integration with Existing Portal Installation window opens if the installer detects an installation of iPlanet Portal Server and you have chosen to install the iPlanet Instant Messaging Server client component.

If you are installing iPlanet Instant Messenger to run as an application in the iPlanet Portal Server Desktop Applications channel, continue with this step. If iPlanet Portal Server is not installed and you are installing iIM Server as a standalone server, skip to Step 16.

To enable iIM Server in the iPlanet Portal Server environment, check the box. If you want to run iPlanet Instant Messaging Server as a standalone server, uncheck the box.

When you have finished making your selection, click Next to continue.

If you decide now not to run iPlanet Instant Messenger in the portal environment, you can choose to install it as part of iPlanet Portal Server later with the im30_install_dir/SUNWiim/sbin/iimipsadmin script. See Chapter 2 in the iPlanet Portal Server: Instant Collaboration Pack Release 3.0 Administrator's Guide for details.

Note It might take some time for the installer to perform this step. Do not try to interrupt the installation.

(Optional, client installations only) If you checked the box to enable iPlanet Instant Messenger in the iPlanet Portal Server environment in Step 13, the Run iPlanet Instant Messaging Server in Secure Mode window opens. This window enables you to install iIM Server in the iPlanet Portal Server environment in either secure or non-secure mode.

In secure mode, iPlanet Instant Messenger uses the iPlanet Portal Server Netlet to set up an encrypted session between the user's computer and the iPlanet Portal Server. A lock icon appears in iPlanet Instant Messenger's Status area when you are running in secure mode. When running iPlanet Instant Messenger in non-secure mode, no encrypted session is set up between the user's computer and iPlanet Portal Server. See the iPlanet Portal Server documentation for more information on Netlet.

You can install iIM Server in secure mode only if the iPlanet Portal Server gateway (iPlanet Portal Server SRAP component) is configured. If the gateway is not configured, then the installer does not display this window and you should skip to Step 15.

This step adds Netlet rules to iwtNetletComponent and sets the iIMSecureMode attribute of the iwtiIM component to TRUE. If you have customized the Netlet rules for any domain, then you must add this new Netlet rule manually. See Chapter 2 in the iPlanet Portal Server: Instant Collaboration Pack Release 3.0 Administrator's Guide for more details.

To run iIM Server in secure mode, check the box. To run iIM Server in non-secure mode, uncheck the box.

(Optional) If you checked the box to enable iPlanet Instant Messenger in the iPlanet Portal Server environment in Step 13, the Selection of Directory Server window opens. This window enables you to choose either iPlanet Portal Server's internal directory (the Profile Service's internal LDAP store) or an external LDAP directory server.

When making your decision, consider the following:

If you use an external LDAP directory server, the uids contained in the directory become user IDs for iPlanet Instant Messenger users. iPlanet Instant Messenger performs both user authentication and user search with that directory. This means that when configured for external LDAP, iPlanet Instant Messaging users can log on directly to the iPlanet Instant Messaging Server (standalone mode) without first starting a session with iPlanet Portal Server.

If you use iPlanet Portal Server's internal directory, iPlanet Instant Messenger will not use the directory for user authentication, just user search. When configured for internal directory, iPlanet Instant Messaging users must first establish a session with iPlanet Portal Server to use iPlanet Instant Messaging. Users cannot log on to iIM Server in standalone mode.

To use iPlanet Portal Server's internal directory, check the box below.

Uncheck the box to use an external LDAP directory server.

(Server installations only) The LDAP Service Configuration window opens with default settings.

If you are using different settings, enter the following LDAP server information:

Host. Host name of the machine on which the LDAP server is running.

Port. Port number that the LDAP server listens to. The default is 389.

Base DN. Base DN (distinguished name) is the entry in your LDAP directory used as the starting point from which searches will occur. For example, if you specify a base DN of ou=people, o=i-zed.com, LDAP search operations executed by the iIM server will examine only the ou=people subtree in the o=i-zed.com directory tree. The installation program does not attempt to verify your entry.

The default is the fully qualified host name.

Note If the installation program does not detect an LDAP server running on the specified port, a Problem Connecting to LDAP message window opens stating that the iIM Server will not run if an LDAP server is not available. If this is acceptable at this point, click Accept, and install the LDAP server before starting iIM Server. Otherwise, click Choose New and re-enter the LDAP configuration parameters.

In a portal configuration, you will need the directory information from the configured authentication mechanism.

For a portal configured to use an external LDAP server, you can run the following command:

ipsadmin get domain /domain

where domain is the name of the desired domain. In the output, the values for iwtAuthLdap-server and iwtAuthLdap-baseDN provide the information you want. Each domain can use its own directory so there could be many of these values.

For a portal configured to use the internal iPlanet Portal Server directory, examine the /etc/opt/SUNWips/properties.file file. The LDAP server host and port are in the java.naming.provider.url field and the base DN is in the java.naming.security.principal field. The base DN is also the value you entered for the portal domain name when you installed iPlanet Portal Server.

When you have finished making your selections, click Next to continue.

(Server installations only) The SMTP Service Configuration window opens.

Identify the SMTP server to be used for sending alerts by email when the user is offline and unable to receive instant messages.The default is the local server you are installing onto.

If you specify your local host name, the installer tries to connect to the SMTP service. If an SMTP service cannot be found on your local host, an Unable to Connect to SMTP Host message window opens, giving you two choices:

Click Accept to keep the settings. You can edit the iim.conf file later to specify the correct SMTP host.

Click Choose New to be returned to the SMTP Service Configuration window. Type the correct host name. Click Next to continue.

The Instant Messaging Services Identity window opens, asking for user and group account names:

The User ID account default is inetuser.

The Group ID account default is inetgroup.

Access permissions on files, directories and system resources are controlled by this identity.

The iPlanet Instant Messaging Server will run with the identity you choose at this step. Additionally, all directories and files associated with this product will be installed on this system using this identity.

If you do not want to use these default accounts, enter the user and group identities that the iIM server will run as.

The installer verifies the User ID and Group ID. If the accounts you selected do not exist, a message window opens and you can either:

Click Create ID. The account is created automatically by the installation program.

Click Choose New to return to the previous window where you can select another ID.

Note Do not specify root for either the user or the group account.

(Server installations only) The Specify Runtime Files Directory window opens.

Specify the directory where you want to store runtime files, including the user profile database, logs, and other files created by the server and multiplexor at runtime.

The default is /var/opt/SUNWiim/default. (That is, the installer creates a directory named default under the path specified.)

If you want to select another directory, click Browse, then select a directory and click OK.

If the directory you selected does not exist, a window opens and you can either:

Click Create Directory to store the runtime files in the specified directory and continue the installation.

Click Choose New to return to the Specify Runtime Files Directory window where you can select another directory.

When you have finished making your selection, click Next to continue.

The installer verifies that the specified directory has the necessary read and execute permissions for $IIMUSER. If not, a message window opens telling you to change the directory or change the permissions on the directory selected.

Note The iPlanet Portal Server: Instant Collaboration Pack runtime files are owned by $IIMUSER (the user and group you enter during the installation). This user must have read and execute permissions to the path containing the runtime directory to be able to read and write files in the directory.

(Client installations only) The Web Server Document Root Directory window opens.

Specify the directory where you want to store the iPlanet Instant Messenger HTML, .jar, and the online help files, which is referred to as the Web Server Directory, or the Web Server Document Root.

These files must reside where the web server (or iPlanet Portal Server) is serving the files. If the web server is on the same host as the iIM Server, then use the top level docs directory (web server document root) for the web server. If the web server is on a host other than the iIM server, then install iPlanet Instant Messenger on the web server host instead of the iIM Server host.

The directory you specify for this step must be on the host you are currently installing to. The default is /opt/SUNWiim/html.

If you want to select another directory, click Browse, then select a directory and click OK.

If the directory you selected does not exist, a message box opens and you can either:

Click Create Directory to install client files in the specified directory and continue the installation.

Click Choose New to return to the Web Server Document Root Directory window where you can select another directory.

Note If you do not install these files in the web server document root (for example, in a subdirectory under the web server document root), you need to edit the iim.jnlp and iimres.jnlp files to reflect the proper codebase.
For example, if your web server's document root is /export/docroot/ and you choose to put your files into the subdirectory /export/docroot/iim/, then edit the iPlanet Instant Messaging Server .html and .jnlp files so that the iim subdirectory is appended to all the http://www.hostname.com entries, where hostname is your web server's host name. All the entries would then look like http://www.hostname.com/iim.
For more information on customizing these files, see Chapter 3 in the iPlanet Portal Server: Instant Collaboration Pack Release 3.0 Administrator's Guide.

When you have finished making your selection, click Next to continue.

(Server installations only) The Instant Messaging Services Startup window opens.

Select the options for automatically starting iIM Server.

You can choose to start the server after successful installation and, optionally, to start the server automatically at system startup. If you do not wish to start the server after the installation or upon server startup, uncheck the applicable box or boxes. When you have finished making your selections, click Next to continue.

The Checking disk space window opens.

The installer is verifying if there is adequate disk space. You might not see this window on faster systems.

The Ready to Install window opens.

Note that the size shown for the installation does not include the Java Runtime Environment, which is an additional 51 MB.

To complete the installation, click Install Now.

The Installing window opens and displays installation progress.

When the installation procedure has completed, an installation Summary window opens. Click Details if you want to review summary information about the installation. When you are finished, Click Dismiss to close the summary information window, then click Exit to exit the installation program.

Note Be sure to follow the post-installation instructions found in the section titled "Post-Installation Steps for Solaris".

Using the Command-Line Installation on Solaris

iPlanet Instant Messaging Server provides you the option of running the installation script without using the graphical interface. To run the command-line installation program, use the following steps:

In a local terminal window, log in as root. You must have superuser privileges (that is, be logged in as root) to run the installation program.

Create a directory (such as /tmp/imsvr) on the machine that will host the iPlanet Instant Messaging Server and download (or copy) the iIM Server installation file to that directory. Make sure that the download directory has adequate disk space to store the extracted files.

Download the software from:

http://www.iplanet.com/downloads/download/

Change to the directory where you copied the archive file and extract the contents, for example:

cd /tmp/imsvr

gunzip -c filename.tar.gz | /usr/bin/tar xvf -

where filename identifies the name of the file you downloaded or copied.

Note You must use /usr/bin/tar. This program should be the tar utility that is distributed with your operating system and not a third party tar utility, such as gnu.

In the installation directory in which you untarred the iIM Server archive file, type:

./setup -nodisplay

The installation program runs in the current window.

Text displays explaining how the command-line installation works. Press Enter to continue.

A welcome message displays. Press Enter to continue.

Preparatory text displays. Press Enter to display the iPlanet Software License Agreement.
From this point on the installation proceeds in the same order as Step 6-Step 25 in "Using the Graphical Interface Installation on Solaris".

Note To exit the installation, press CTRL-C.

Note Be sure to follow the post-installation instructions found in the section titled "Post-Installation Steps for Solaris."

Post-Installation Steps for Solaris

After installation, you might need to complete other steps described in this section.

Post-Installation Steps for Both Portal and Standalone Installations

Searching the Directory and Anonymous Users

iPlanet Instant Messaging Server needs to be able to search the directory to function correctly. If your directory is configured to be searchable by anonymous users, iIM Server has the capability it needs. If the directory is not readable by anonymous users, you must take additional steps to configure the iim.conf file with the credentials of a user ID that has at least read access to the directory.
See Chapter 2 of the iPlanet Portal Server: Instant Collaboration Pack Release 3.0 Administrator's Guide for the steps to enable iIM Server to search the directory as a specific (non-anonymous) user.

Note iPlanet Portal Server's internal directory does not allow anonymous bind. Thus, when using this directory, you must go through the procedure to enable iIM Server to search the directory as a specific (non-anonymous) user. If you are using an external LDAP directory (standalone or portal mode), you do not have to go through this additional step, if the external LDAP directory is configured for anonymous search.

Launching Java Web Start

To launch Java Web Start, you might 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:

/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.

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:

application/x-java-jnlp-file jnlp

Viewing Online Help

If you chose to install iPlanet Instant Messaging Server online help at the document root, in order to see it, you must edit the iPlanet Web Server file obj.conf, found at:
/usr/netscape/server4/https-xxx/config/obj.conf
where xxx is your web server instance name.
Comment out the following line:
NameTrans fn="pfx2dir" from="/help" dir="/export1/webserver
/manual/https/ug" name="es-internal"

Web Server Not Installed on Default Port

If your web server was not installed on the default port, you must edit the iim.jnlp and iimres.jnlp files as follows:
For both files, edit codebase="http://servername" to be:
codebase="http://host.domain:port"

Note For further information on editing the iim.jnlp and iimres.jnlp files, see the iPlanet Portal Server: Instant Collaboration Pack Release 3.0 Administrator's Guide.

Post-Installation Steps for Portal Installations

Restarting iPlanet Portal Server Web Server After Installation

Because the installer modifies the configuration files of the iPlanet Portal Server web server, you need to restart the iPlanet Portal Server web server to ensure that the configuration changes take effect.

To restart the iPlanet Portal Server web server:

/opt/SUNWips/bin/ipsserver start

You can also use the Administration Console to restart the web server.

If the iPlanet Portal Server gateway (SRAP component) is installed then it also needs to be restarted:

/opt/SUNWips/bin/ipsgateway start

Using External LDAP with iPlanet Portal Server

When using iPlanet Portal Server with an external LDAP server, add the iwtUser-iIMUserId attribute to the iwtExtLdap component's attribsMap.
To use external LDAP with iPlanet Portal Server:

From the iPlanet Portal Server Administration Console, click Manage Domains.

Click the appropriate domain.

Click External LDAP Configuration.

Click Attributes aliases Mapping.

If the iwtUser-iIMUserId=uid mapping is present and the attribute is marked "inherited," remove it, and save the configuration. Then go back to the external LDAP configuration page.

If the mapping is not present, go to Step 6.

Currently, to "customize" an iPlanet Portal Server attribute, you must delete it, save the change, then readd it. This is an iPlanet Portal Server issue. For more information, see the "Known Problems and Limitations" section in the iPlanet Portal Server: Instant Collaboration Pack 3.0 Release Notes.

Scroll down to the attributes mapping section and add the iwtUser-iIMUserId=uid mapping back in. Save the configuration.

Note iPlanet Portal Server supports many authentication mechanisms, such as Radius, Unix, Membership, and LDAP. When you are using an external LDAP directory in your iIM Server deployment, the uids of your users must reside in the external LDAP directory, regardless of the authentication mechanism used. Otherwise, users will not be able to log on to iIM Server.

Adding iPlanet Portal Server Desktop Links

When installing iPlanet Instant Messaging Server in the iPlanet Portal Server environment, the installer inserts the following three links in the Application channel of the iPlanet Portal Server Desktop:

iPlanet^TM Portal Server: Instant Messenger Quick Reference - Displays the iPlanet Instant Messaging Server Quick Reference in a new web browser window.

Launch iPlanet^TM Instant Messenger using Java plug-in - Starts iPlanet Instant Messenger using the Java Plug-in.

Launch iPlanet^TM Instant Messenger using Java Web Start - Starts iPlanet Instant Messenger using Java Web Start.
These links are displayed to users in their iPlanet Portal Server Desktop Applications channel only if they have not customized the iwtAppProvider component. If users do not automatically receive the iPlanet Instant Messenger links, then they must add them manually from the available Applications channel.
To manually add applications to the Applications Channel:

Click Edit on the Applications toolbar.

Select the iPlanet Instant Messenger applications you want displayed in the Applications channel.

Click Finished to return to the Portal Server Desktop page.

Type of Installation	Enables Changing Configuration Options?	Enables You to Add a Component to This Server?	Preserves Existing Database and Configuration?	Should You Back Up Existing iIM Server Files?
Upgrade	No.	No.	Yes.	Not necessary, but should be done as a precaution.
Reinstall	Yes. You can change all installation options.	Yes.	No.	Depends: Back up any customizations, configurations, or databases you want to keep.

Previous Contents Index DocHome Next
Copyright © 2001 Sun Microsystems, Inc. All rights reserved.

Last Updated December 04, 2001