Sun Java System Instant Messaging 7.2 Administration Guide

General Configuration Parameters

Table A–1 lists and describes the general configuration parameters.

Table A–1 General Configuration Parameters


Default Value  




The communication modules used. The possible values are iim_server and iim_mux. The default value is iim_server, iim_mux, which means both the server and multiplexor are used. The iim_mux value is useful for multiplexor.



SMTP server to send mail to end users who have set the option for forwarding their messages as emails or to pagers.



The installation directory root. 


Solaris: /var/opt/SUNWiim/default

Linux: /var/opt/sun/im/default

Sets the directory to contain runtime files, including the end-user profile database, logs, and other files created by the server and multiplexor at runtime. The name of the /default directory may vary if you created multiple instances of Instant Messaging.


inetuser for LDAP deployments.

root for portal deployment.

The end-user name with which the server processes run.

inetgroup for LDAP deployments.

root for portal deployment.

The group using which the server processes run. 



The maximum number heap size in MB the JVM running the server is allowed to use. Used to construct the -mx argument of the Java command.



This parameter specifies if the headers of the mail are in ASCII and not encoded. 

It contains the name of the character set to be used to encode the headers of the mail message sent out for offline alerts. 

For example: iim.mail.charset=iso-2022-jp



The location of the Java Runtime Executable (JRE).



The default installation directory, also referred to as the base directory, for Sun JavaTM System Access Manager.



The location of the JRE used by the Access Manager to run all its processes.



The URI using which the Portal Server war files are deployed in the Access Manager.


The host name of the server on which the Portal Server is running. Specify the port number if a non default port number is used. 



The protocol used to access the Portal Server. 



Defines the cache validity interval (in minutes) for a single user’s information. 

The Instant Messaging server saves the last date a single end-user’s information was cached. If the end-user’s information is accessed after the interval determined by this parameter, the server will recache the end user’s information and reset the cache date on the LocalUser object.



By default, LDAP is used for policy storage. Change the value to identity to indicate that Sun Java System Access Manager should be used for policy storage.



Defines the cache validity interval (in minutes) for all end-user information. 

The Instant Messaging server clears all cached end-user information on a regular basis in order to eliminate old end-user information. This parameter specifies the frequency at which the cached end-user information is cleared.


By default, user properties are stored in a user properties file if you chose not to use Access Manager for policy when you ran the configure utility. If you chose to use Access Manager for policy, the default is ldap. Change the value to change the location where user properties are stored. If you change this from file to ldap, you need to run imadmin assign_services to add required objectclasses to user entries in the directory.

This parameter is only significant when the service definitions for the Presence and Instant Messaging services have been installed.