Instant Messaging Configuration Parameters in iim.conf

{anchor:achfp}
{anchor:top}
h1. Instant Messaging Configuration Parameters in {{iim.conf}}

This chapter explains the Instant Messaging configuration parameters in the {{iim.conf}} file in the following sections:

{toc:minLevel=2|maxLevel=2}{anchor:gbopk}

h2. {{iim.conf}} File Location{anchor:gbopb} {anchor:indexterm-738}

Instant Messaging stores configuration settings in the {{iim.conf}} file within the Configuration Directory (_im-cfg-base_).
* On Solaris:
{{/etc/opt/SUNWiim/default/config/iim.conf}}
* On Linux:
{{/etc/opt/sun/im/default/config/iim.conf}}

If you created multiple instances of Instant Messaging, the name of the {{/default}} directory will vary depending on the instance. See [Creating Multiple Instances from a Single Instant Messaging Installation|http://wikis.sun.com/display/CommSuite/Configuring+Instant+Messaging+After+Installation#ConfiguringInstantMessagingAfterInstallation-indexterm68] for more information.{anchor:achfq}

h2. {{iim.conf}} File Syntax{anchor:indexterm-739} {anchor:indexterm-740}

This file is a plain ASCII text file, with each line defining a server parameter and its value(s):
* A parameter and its value(s) are separated by an equal sign (=) with spaces and tabs allowed before or after the equal sign.
* A value can be enclosed in double quotes (" "). If a parameter allows multiple values, the entire value string must be enclosed in double quotes.
* A comment line must have an exclamation point ( ! ) as the first character of the line. Comment lines are for informational purposes and are ignored by the server.
* If a parameter appears more than once, the value of the last parameter listed overrides the previous value.
* A backslash ( \ ) is used for continuation and indicates the value(s) are longer than one line.
* Each line is terminated by a line terminator ({{\n}}, {{\r}}, or {{\r\n}}).
* The key consists of all the characters in the line starting with the first non-whitespace character and up to the first ASCII equal sign ( = ) or semi-colon ( ; ). If the key is terminated by a semi-colon, it is followed by “{{lang-}}” and a tag that indicates the language in which this value is to be interpreted. The language tag is followed by an equal sign (=). All whitespace characters before and after the equal sign are ignored. All remaining characters on the line become part of the associated value string.
* Multiple values in the value string are separated using commas (,).
* Within a value, if any special characters like comma, space, newline, tab, double quotes, or backslash are present, the entire value needs to be within double quotes. In addition, every carriage return, line feed, tab, backslash, and double quotes within the value must specified with a backslash ( \ ).
* If you make changes to {{iim.conf}}, you must refresh the Instant Messaging server in order for the new configuration settings to take effect.

{info:title=Note} The {{iim.conf}} file is initialized by the installation process and should be modified only as described in this guide.{info}{anchor:achfr}

[Top|#top]
h2. General Configuration Parameters

[Table A-1|#fvcbq] lists and describes the general configuration parameters.

h5. {anchor:fvcbq} Table A-1 General Configuration Parameters
||Parameter ||Default Value ||Description ||
|_iim.comm.modules_ |{{iim_server,iim_mux}} |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. |
|_iim.smtpserver_ |{{localhost}} |SMTP server to send mail to end users who have set the option for forwarding their messages as emails or to pagers. |
|_iim.instancedir_ |{{/opt}} |The installation directory root. |
|_iim.instancevardir_ |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. |
|_iim.user_ |{{inetuser}} for LDAP deployments.{{root}} for portal deployment. | The end-user name with which the server processes run. |
|_iim.group_ |{{inetgroup}} for LDAP deployments.{{root}} for portal deployment. |The group using which the server processes run. |
|_iim.jvm.maxmemorysize_ |{{256}} |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. |
|_iim.mail.charset_ |None |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}} |
|_iim.jvm.command_ |{{/usr/j2se/bin/java}} |The location of the Java Runtime Executable (JRE). |
|_iim.identity.basedir_ |{{/opt}} |The default installation directory, also referred to as the base directory, for Sun Java System Access Manager. |
|_iim.identity.jre_ |{{/usr/java_1.3.1_04}} |The location of the JRE used by the Access Manager to run all its processes. |
|_iim.portal.deployuri_ |{{/portal}} |The URI using which the Portal Server {{war}} files are deployed in the Access Manager. |
|_iim.portal.host_ |{{imhostname}} |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. |
|_iim.portal.protocol_ |{{http}} |The protocol used to access the Portal Server. |
|_iim.policy.cache.validity_ |10 |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. |
|_iim.policy.modules_ |{{iim_ldap}} |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. |
|_iim.policy.resynctime_ |{{720}} |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. |
|_iim.userprops.store_ |{{file}} |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. |
{anchor:achfs}

[Top|#top]
h2. LDAP and User Registration Configuration Parameters{anchor:indexterm-741}

[Table A-2|#fvcch] lists and describes the parameters used by Instant Messaging for LDAP, user registration, and user source configuration.

h5. {anchor:fvcch} Table A-2 LDAP, User Registration, and Source Configuration Parameters
||Parameter ||Default Value ||Description ||
|_iim_ldap.host_ |{{localhost:389}} |LDAP server name and port used by Instant Messaging server for end-user authentication. |
|_iim_ldap.searchbase_ |{{o=internet}} |The string used as base to search for the end users and groups on the LDAP server. |
|_iim_ldap.usergroupbinddn_ |None (the server performs anonymous searches) |Specifies the DN to use to bind to the LDAP server for searches. |
|_iim_ldap.usergroupbindcred_ |None (the server performs anonymous searches) |Specifies the password to use with the {{iim_ldap.usergroupbinddn}} DN for LDAP searches. |
|_iim_ldap.loginfilter_ | (&\(\|\(objectclass=inetorgperson\)\(objectclass=webtopuser\)\)\(uid=\{0\}\)\) |Search filter used during end-user login. The entire filter is entered as one line. |
|_iim_ldap.usergroupbyidsearchfilter_ | \(\|\(&\(objectclass=groupofuniquenames\)\(uid=\{0\}\)\) \\ \(&\(\|\(objectclass=inetorgperson\)\(objectclass=webtopuser\)\)\(uid=\{0\}\)\)\) |The search filter used to search for end users and groups in the directory, under the base specified by ID. The entire filter is entered as one line. |
|_iim_ldap.usergroupbynamesearchfilter_ | \(\|\(&\(objectclass=groupofuniquenames\)\(cn=\{0\}\)\) \\ \(&\(\|\(objectclass=inetorgperson\)\(objectclass=webtopuser\)\)\(cn=\{0\}\)\)\) |The search filter used to search for end users and groups in the directory, under the base specified by name. |
|_iim_ldap.allowwildcardinuid_ |{{False}} |Determines if wildcards should be enabled for UIDs while performing a search. As most directory installations have UIDs indexed for exact searches only, the default value is {{False}}. Setting this value to {{True}} can impact performance unless UIDs are indexed for substring search. |
|_iim_ldap.userclass_ |{{inetOrgPerson,webtopuser}} |The LDAP class that indicates that an entry belongs to an end user. |
|_iim_ldap.groupclass_ |{{groupOfUniqueNames}} |The LDAP class that indicates that an entry belongs to a group. |
|_iim_ldap.groupbrowsefilter_ |{{(objectclass=groupofuniquenames)}} |The search filter used to browse all groups in the directory under the specified search base. |
|_iim_ldap.searchlimit_ |{{40}} |Maximum number of entries to be returned by a search. A value of {{-1}} means search is disabled on this server and a value of {{0}} indicates unlimited search. |
|_iim_ldap.userdisplay_ |{{cn}} |LDAP attribute to use for display name of end users. |
|_iim_ldap.groupdisplay_ |{{cn}} |LDAP attribute to use for display name of groups.|
|_im_ldap.useruidattr_ |{{uid}} |LDAP attribute used as end users' UID. |
|_im_ldap.groupmemberattr_ |{{uniquemember}} |LDAP attribute that gives the list of members of a group. |
|_iim_ldap.usermailattr_ |{{mail}} |LDAP attribute that should contain end users' provisioned email addresses. Used when the email message is sent to an offline end user. |
|_iim_ldap.userattributes_ |None |LDAP attribute that contains the list of custom attributes from the LDAP user entry. |
|_iim_ldap.groupattributes_ |None |LDAP attribute that contains the list of custom attributes from the LDAP group entry. |
|_iim_ldap.groupmemberurlattr_ |None |The membership attribute of a dynamic group, which contains the LDAP filter or the LDAP URL. |
|_iim_ldap.useidentityadmin_ |The default value is {{true}} if you chose to leverage an Access Manager deployment for policy when you ran the {{configure}} utility. Otherwise, the default value is {{false}}. |If the value is {{true}} then the Access Manager Administrator credentials will be used to bind to the Directory \\ Server. |
|_iim.register.enable_ |None |If {{TRUE}}, the server allows new Instant Messaging end \\ users to register \\ themselves (add themselves to the directory) using Instant Messenger. |
|_iim_ldap.register.basedn_ |None |If self-registration is enabled, the value of this parameter is the DN of the location in the LDAP directory in which \\ person entries are stored. For example: {{"ou=people,dc=siroe,dc=com"}} |
|_iim_ldap.register.domain_ |None |The domain to which new users will be added. For example, {{directory.siroe.com}}. |
{anchor:achft}

[Top|#top]
h2. Logging Configuration Parameters{anchor:indexterm-742}

[Table A-3|#fvcca] lists and describes the logging configuration parameters for both log4j-based logging and {{iim.conf}} parameter-based logging.

h5. {anchor:fvcca} Table A-3 Logging Configuration Parameters
||Parameter ||Default Value ||Description ||
|_iim.log.iim_server.severity_ |{{INFO}} |Level of logging required for the server module. The possible values from highest to lowest are: {{FATAL}}, {{ERROR}}, {{WARNING}}, {{INFO}}, and {{DEBUG}}. If a lower level of logging is chosen, it is implied that you get the higher levels too. For example, if you choose {{WARNING}} you get {{FATAL}}, {{ERROR}}, and {{WARNING}}. |
|_iim.log.iim_server.url_ |{{_im-runtime-base_/log/xmppd.log}} |Location of the server log file. This file needs to be periodically trimmed to prevent disk space from filling up. |
|_iim.log.iim_mux.severity_ |{{INFO}} |Level of logging required for the multiplexor module. The possible values from highest to lowest are: {{FATAL}}, {{ERROR}}, {{WARNING}}, {{INFO}}, and {{DEBUG}}. If a lower level of logging is chosen, it is implied that you get the higher levels too. For example, if you choose {{WARNING}} you get {{FATAL}}, {{ERROR}}, and {{WARNING}}. |
|_iim.log.iim_mux.url_ |{{_im-runtime-base_/log/mux.log}} |Location of the multiplexor log file. This file needs to be periodically trimmed to prevent disk space from filling up. |
|_iim.log.iim_mux.maxlogfiles_ |10 |The maximum number of log files to store for the multiplexor. Once this number is exceeded, the oldest multiplexor log file is deleted. |
|_iim.log.iim_mux.maxlogfilesize_ |10 MB |This parameter contains the maximum size of a multiplexor log file. If the log files exceeds the size specified in this parameter then a new log file is created. |
|_iim.log.iim_server.maxlogsize_ | |This parameter contains the maximum size of a server log file. If the log files exceeds the size specified in this parameter then a new log file is created. |
|_iim.log.iim_wd.severity_ |{{INFO}} |Level of logging required for the watchdog. The possible values from highest to lowest are: {{FATAL}}, {{ERROR}}, {{WARNING}}, {{INFO}}, and {{DEBUG}}. If a lower level of logging is chosen, it is implied that you get the higher levels too. For example, if you choose {{WARNING}} you get {{FATAL}}, {{ERROR}}, and {{WARNING}}. |
|_iim.log.agent-calendar.severity_ |{{INFO}} |Level of logging required for the Calendar agent. The possible values from highest to lowest are: {{FATAL}}, {{ERROR}}, {{WARNING}}, {{INFO}}, and {{DEBUG}}. If a lower level of logging is chosen, it is implied that you get the higher levels too. For example, if you choose {{WARNING}} you get {{FATAL}}, {{ERROR}}, and {{WARNING}}. |
|_iim.log4j.config_ |_im-cfg-base_ |Specifies the location and name of the log4j configuration file. If no value exists for this parameter, the logger will look for {{log4j.conf}} in _im-cfg-base_. If the logger does not find {{log4j.conf}} in _im-cfg-base_, it uses the parameter-based logging method, instead of log4j. |
{anchor:achfu}

[Top|#top]
h2. Instant Messaging Server Configuration Parameters{anchor:indexterm-743}

[Table A-4|#fvcbm] lists and describes the Instant Messaging server configuration parameters.

h5. {anchor:fvcbm} Table A-4 General Instant Messaging Server Configuration Parameters
||Parameter ||Default Value ||Description ||
|_iim_server.autosubscribe_ |{{FALSE}} |Indicates whether subscriptions are automatically authorized by the server. The possible values are {{TRUE}} and {{FALSE}}. If {{TRUE}}, subscribe requests are automatically followed by a subscribed response generated by the server. The server then sends the modified roster to the subscriber and the user the subscriber added as a contact. The user and the contact must be in the same domain to use this feature. |
|_iim_server.domainname_ |_host’s domain name_ |The logical Instant Messaging server domain name you want this server to support. This is the name that is used by other servers in the network to identify this server. It is also the name used by this server to identify its end users to other servers. This is not necessarily the Fully Qualified Domain Name of the system running the Instant Messaging server.For example, if the system {{iim.xyz.com}} is the only Instant Messaging server for a company {{xyz.com}}, then the domain name is likely to be {{xyz.com}}. |
|_iim_server.port_ |{{5269}} |IP address and port for the server to bind to, and to listen for connections from other servers. IP address setting is useful for multi homed machines when you want to use only one particular IP address. If no IP address is listed, this indicates a value of {{INADDR_ANY}} on {{localhost}}. |
|_iim_server.useport_ |{{TRUE}} |Indicates whether the server should listen on the server-to-server communication port. The possible values are {{TRUE}} and {{FALSE}}. If {{TRUE}}, the server listens on the port defined by _iim_server.port_ or on port 5269, if that is not explicitly defined. |
|_iim_server.clienttimeout_ |{{15}} |Specifies the time, in minutes, before the server discards client connections that are no longer active. For example, when a machine is turned off. The minimum accepted value is 5. |
|_iim_server.usesso_ |The default value is {{1,}} if you chose to leverage an Access Manager deployment for SSO when you ran the {{configure}} utility. Otherwise, the default value is {{0}}. |This parameter tells the server whether or not to depend on the SSO provider during authentication. An SSO provider is a module the server uses to validate a session ID with a SSO service.TheAccess Manager Session API provides the Instant Messaging server with the ability to validate session IDs sent by the client.The value for this parameter can either be 0 or 1. Use SSO provider only without attempting LDAP authentication even when the SSO validation fails.The _iim_server.usesso_ parameter is used in conjunction with the _iim_server.ssoprovider_ parameter. |
|_iim_server.ssoprovider_ |None |Specifies the class implementing the {{com.sun.im.provider.SSOProvider}} interface. If {{iim_server.usesso}} is not equal to {{0}} and this option is not set, the server uses the default Access Manager-based SSO Provider. |
|_iim.policy.modules_ |The default value is {{identity,}} if you chose to leverage an Access Manager deployment for policy when you ran the {{configure}} utility. Otherwise, the default value is {{iim_ldap}}. |If the value is {{identity}}, indicates that Sun Java System Access Manager is used for policy storage. If the value is {{iim_ldap}}, directory is used. |
|_iim.userprops.store_ |{{file}} |If the value is {{file}}, indicates that the user properties are stored in a user properties file. If the value is {{ldap}}, directory is used. |
|_iim_server.msg_archive_ |{{false}} |This parameter specifies whether the archive provider should be enabled or disabled. Set this value to {{false}} to disable all archiving. Set the value to {{true}} to enable all archiving, including Portal, email, and any custom archive provider you want to use. |
|_iim_server.msg_archive.provider_ |None |This parameter contains the list of archive providers. This parameter allows multiple values and each value is separated by a comma ({{,}}). If you are using the Portal Server Search based archive, the value should be {{com.iplanet.im.server.IMPSArchive}}. If you are using email archiving, the value should be {{com.iplanet.im.server.EmailIMArchive}}. |
|_iim_server.conversion_ |{{false}} |This parameter specifies whether message conversion should be enabled. It specifies whether the configured list of Message Conversion Providers should be used for message conversion. |
|_iim_server.conversion.provider_ |None |This parameter contains the list of Message Conversion Providers to be used for message conversion.This parameter allows multiple values with each value is separated by a comma ( , ). |
|_iim_server.servertimeout_ |-1 |The server can be configured to automatically close the connection opened by a remote server, if the remote server is inactive. This is performed by periodically measuring the time the last request was made by the remote server to the server. The connection to the remote server is terminated, if the time of the last request made by the remote server exceeds the value of the _iim_server.servertimeout_ parameter.The parameter value is in minutes. |
|_iim_server.enable_ |{{true}} |This value defines whether or not the Instant Messaging server is enabled. This parameter is set false to enable the Instant Messaging multiplexor. |
|_iim_server.conversion.external.command_ |None |This parameter contains the external command used for message conversion. |
|_iim_server.stat_frequency_ |{{1}} |This parameter contains the frequency at which the server logs the summary of activities to the log file. The server logs the summary of activities to the log file only if the server minimum log severity is set to {{INFO}} or lower. The value is in minutes. |
|_iim_server.certnickname_ |{{Server-Cert}} |This value should contain the name of the certificate you entered while installing the certificate.The certificate name is case-sensitive. |
|_iim_server.sslkeystore_ |None |Contains the relative path and filename for the server's Java keystore (JKS). For example,
{{/im-cfg-base/server-keystore.jks}}|
|_iim_server.keystorepasswordfile_ |{{sslpassword.conf}} |This value should contain the relative path and the name of the file containing the password for the key database. This file should contain the following line:{{Internal (Software) Token:}}_password_Where _password_ is the password protecting the key database. |
|_iim_server.requiressl_ |{{false}} |If true, the server will terminate any connection that does not request a TLS connection after the initial stream session is set up. This includes connections from clients, other servers, and server components, such as the XMPP/HTTP Gateway and agents, except the multiplexor. |
|_iim_server.trust_all_cert_ |{{false}} |If this value is true than the server will trust all certificates and will also add the certificate information into the log files. |
{anchor:achfv}

[Top|#top]
h2. Multiple Server Configuration Parameters{anchor:indexterm-744}

For communication between multiple Instant Messaging servers in your network, you need to configure your server to identify itself with the other servers and identify itself with each coserver, or cooperating server, which will have a connection to your server. The coserver identifies itself with its Instant Messaging domain name, host and port number, server ID, and password.

Each cooperating server is given a symbolic name, which is a string consisting of letters and digits, for example, {{coserver1}}. Using the symbolic naming convention you can specify multiple servers.

When Instant Messaging servers are configured in this manner, you can form a larger Instant Messaging community. Therefore, end users on each server can do the following:
* Communicate with end users on every other server
* Use conferences rooms on other servers
* Subscribe to news channels on other servers (subject to access privileges)

[Table A-5|#fvccg] lists and describes the multiple server configuration parameters.

h5. {anchor:fvccg} Table A-5 Multiple Server Configuration Parameters
||Parameter ||Default Value ||Description ||
|_iim_server.serverid_ |None |String used by this server to identify itself to all other servers. |
|_iim_server.password_ |None |Password used by this server to authenticate itself to all other servers. |
|_iim_server.coservers_ |None |Comma separated list containing symbolic names of the servers that can connect to \\ this server. Any meaningful names are allowed, but they must match what you use for the \\ {{\*.serverid}} , {{\*.password}} , and {{*.host}} parameters. Examples:{{iim_server.coservers=coserver1,coserver2}} \\ or {{iim_server.coservers=abc,xyz,ntc}} |
|_iim_server.__coserver1__.serverid_ |None |String that identifies the cooperating server represented by the name, _coserver1_ \\ to authenticate to this server. For example, if you used {{abc}} \\ in the _iim_server.coservers_ list, then the corresponding name for \\ its _serverid_ would be {{iim_server.abc.serverid}}. |
|_iim_server.__coserver1__.password_ |None |Password used by cooperating server represented by the \\ name, _coserver1_ to authenticate to this server. For example, \\ if you used {{abc}} in the _iim_server.coservers_ list, then the corresponding name for its password would be \\ {{iim_server.abc.password}}. |

h2. Shoal Configuration Parameters{anchor:indexterm-755}

You can use the Shoal clustering framework to automatically discover and add peer servers in a server pool.
[Table A-6|#fvceg] lists and describes the shoal configuration parameters.

h5. {anchor:fvceg} Table A-6 Shoal Configuration Parameters
||Parameter|| Default||Required?|| Description
|iim_server.peer.autodiscover| {{false}}| No| The parameter that enables auto-discovery using Shoal. It is recommended to delete all static co-server definitions before setting this to {{true}}.
| iim_server.serverid| None| Yes| The ID that uniquely identifies the server instance within the pool. It could be an identifier such as {{server1}}, or a host name.
|iim_server.password| None| Yes| The password that is shared across the pool and enables identification of members of one pool from the other. Also ensures that unidentified members of a Shoal group can not join the pool.
|iim_server.hostname| {{local-hostname:5269}}| No| The connection string that the other pool members can establish connections with. It is the host name and port of the specified server.
|iim_server.pool.groupname| {{iim.server.pool}}| No| The Shoal group name that the peers will attempt to join. You will need to change the default only if multiple clusters of peer servers need to run on the same subnet.

For Shoal Across Subnets
||Parameter|| Default||Required?|| Description
| relay.imadmin.enable| {{true}}| Yes| Starts the relay server.
| relay.listen_address=<address of relay server> | None| Optional| Specifies the address of the relay server.
| relay.uri_list | None| Yes | Displays the list of relay servers added.


[Top|#top]
h2. Multiplexor Configuration Parameters{anchor:indexterm-745}

[Table&nbsp;A-7|#fvcbh] lists and describes the multiplexor configuration parameters.

h5. {anchor:fvcbh} Table&nbsp;A-7 Multiplexor Configuration Parameters
||Parameter ||Default Value ||Description ||
|_iim_mux.listenport_ |_multiplexorname or IP address:_{{5222}} |IP address or FQDN and listening port on which the multiplexor listens for \\ incoming requests from Instant Messenger. \\ The value format is _IPaddress_{{:}}_port_ or _multiplexorname_{{:}}_port_. \\ If no IP address or domain name is listed, {{INADDR_ANY}} on {{localhost}} \\ is assumed.If you change this value, also change the {{im.html}} and {{im.jnlp}} files \\ so that they match the port value. |
|_iim_mux.serverport_ |{{45222}} |The Instant Messaging server and port the multiplexor \\ communicates to. The value format is \\ _servername_:_port_ or _IPaddress_:_port_. |
|_iim_mux.numinstances_ |{{1}} |Number of instances of the multiplexor. This \\ parameter is valid only for Solaris platforms. |
|_iim_mux.maxthreads_ |{{5}} |Maximum number of threads per instance of the multiplexor. |
|_iim_mux.maxsessions_ |{{2000}} |Maximum number of concurrent connections per multiplexor process. |
|_iim_mux.usessl_ |{{off}} |If the value is set to {{on}}, the multiplexor requires \\ an SSL handshake for each connection it accepts, before exchanging any \\ application data. |
|_iim_mux.secconfigdir_ |{{/etc/opt/SUNWiim/default/config}} |This directory contains the key and certificate databases. \\ In addition, it also usually contains the security module \\ database. The name of the {{/default}} directory may vary if you \\ created multiple instances of Instant Messaging. |
|_iim_mux.keydbprefix_ |None |This value should contain the \\ key database filename prefix. The key database file name \\ must always end with {{key3.db}}. \\ If the Key database contains a prefix, for example {{This-Database-key3.db}}, \\ then value of this parameter is {{This-Database}}. |
|_iim_mux.certdbprefix_ |None |This value should contain the certificate database filename \\ prefix. The certificate database file name must always end with {{cert7.db}}. \\ If the certificate database contains a prefix, for example {{Secret-stuff-cert7.db}}, then value of this \\ parameter is {{Secret-stuff}}. |
|_iim_mux.secmodfile_ |{{secmod.db}} |This value should contain the name of the security \\ module file. |
|_iim_mux.certnickname_ |_Multiplexor-Cert_ |This value should contain the name of the certificate you entered while installing the certificate. The certificate name \\ is case-sensitive. |
|_iim_mux.keystorepasswordfile_ |{{/etc/opt/SUNWiim/default/config/sslpassword.conf}} |This value should contain the relative path and the name \\ of the file containing the password for the key database. \\ This file should contain the following line:
{{Internal (Software) Token:password}}
Where _password_ is the \\ password protecting the key database. The name of the \\ {{/default}} directory may vary if you created multiple \\ instances of Instant Messaging. |
|_iim_mux.stat_frequency_ |{{600}} |This value should contain the frequency at which \\ the multiplexor logs the summary of activities to the log file. \\ The minimum value is 10 seconds. |
|_iim_mux.enable_ |{{true}} |If the value is {{true}} then the multiplexor will run for this instance. \\ If the value is {{false}} then the multiplexor will \\ not run for this instance. |
{anchor:geqbd}

[Top|#top]
h2. Redirect Server Parameters

[Table&nbsp;A-8|#geqbj] lists the parameters you use to administer the Instant Messaging redirect server.

h5. {anchor:geqbj} Table&nbsp;A-8 Redirect Server Parameters
||Parameter ||Default Value ||Description ||
|_iim_server.redirect.provider_ |None |Comma-separated list of redirect provider names or classes that implement the {{com.sun.im.provider.Redirector}} interface. Any value for this parameter defines the server instance as a redirect server. Supported values include {{db}}, {{roundrobin}}, {{regex}}, and class names that implement the {{com.sun.im.provider.Redirector}} interface. |
|_iim_server.redirect.to_ |None |Comma-separated list of nodes to which this redirect server may redirect client connections. Node names can be any alphanumeric string. This list may be a superset of the hosts defined in _iim_server.redirect.to.nodename.host_. |
|_iim_server.redirect.to.nodename.host_ |None |Where _nodename_ is the name of the node as it exists in _iim_server.redirect.to_. This attribute is required for nodename to be used by the redirect server. |
|_iim_server.redirect.to.nodename.usessl_ |False |If true, then _nodename_ is configured to use legacy SSL. See [Overview of Using TLS and Legacy SSL in Instant Messaging|http://wikis.sun.com/display/CommSuite/Securing+Instant+Messaging+Using+TLS+and+Legacy+SSL#SecuringInstantMessagingUsingTLSandLegacySSL-OverviewofUsingTLSandLegacySSLinInstantMessaging] for more information. |
|_iim_server.redirect.db.users_ |{{im-db-base/redirect.db}} |Name and location of the redirect database. |
|_iim_server.redirect.db.partitions_ |{{im-cfg-base/redirect.partitions}} |Name and location of the redirect partitions file. |
|_iim_server.redirect.db.partitionsize_ |5000 |The maximum number of users in a partition. |
|_iim_server.redirect.roundrobin.partitions_ |{{im-cfg-base/redirect.partitions}} |Name and location of the redirect partitions file. |
|_iim_server.redirect.pollfrequency_ | |The interval between connections made by the redirect server to the hosts defined in the {{redirect.hosts}} file. The redirect server polls these hosts to determine if they are online and able to accept client connections. |
{anchor:gamqf}

[Top|#top]
h2. Archive Parameters

[Table&nbsp;A-9|#fvcaz] lists the parameters you use to manage Instant Messaging archiving.

h5. {anchor:fvcaz} Table&nbsp;A-9 Archive Parameters
||Parameter ||Default Value ||Description ||
|_iim_arch.title.attr_ |{{Title}} |This parameter contains the name of the field equivalent to the {{Title}} field in the default schema of the Portal Server Search. |
|_iim_arch.keyword.attr_ |{{Keyword}} |This parameter contains the name of the field equivalent to the {{Keyword}} field in the default schema of the Portal Server Search. |
|_iim_arch.readacl.attr_ |{{ReadACL}} |This parameter contains the name of the field equivalent to the {{ReadACL}} field in the default schema of the Portal ServerSearch. |
|_iim_arch.description.attr_ |{{Description}} |This parameter contains the name of the field equivalent to the {{Description}} field in the default schema of the Portal Server Search. |
|_iim_arch.fulltext.attr_ |{{Full-Text}} |This parameter contains the name of the field equivalent to the {{Full-Text}} field in the default schema of the Portal Server Search. |
|_iim_arch.category.attr_ |{{Category}} |This parameter contains the name of the field equivalent to the {{Category}} field in the default schema of the Portal Server Search. |
|_iim_arch.readacl.admin_ |None |This parameter contains the administrator&rsquo;s DN. Multiple values should be separated by a semi colon ( ; ). |
|_iim_arch.readacl.adminonly_ |{{false}} |This parameter will contain {{true}} or {{false}}. \\ {{true}} - Only the administrator&rsquo;s DN specified by the parameter _iim_arch.readacl.admin_ will be added to the {{ReadACL}} field overwriting the default behavior of the {{ReadACL}} field. \\ {{false}} - The administrator&rsquo;s DN specified by the parameter {{iim_arch.readacl.admin}} will be added to the {{ReadACL}} field in addition to the default behavior. |
|_iim_arch.categories_ |{{all}} |This parameter contains a list of message types that can be archived.The value can be:{{poll}}{{alert}}{{chat}}{{conference}}{{news}}Multiple values can be specified separated by commas (,). |
|_iim_arch.categoryname_ |None |If a category name is not assigned for any of the categories then the value of this parameter is used as the category name. |
|_iim_arch.alert.categoryname_ |None |This parameter contains the name of the category containing the archived alert messages.It is not required to dedicate a category to alert messages. |
|_iim_arch.poll.categoryname_ |None |This parameter contains the name of the category containing the archived poll messages.It is not required to dedicate a category to poll messages. |
|_iim_arch.conference.categoryname_ |None |This parameter contains the name of the category containing the archived conference messages.It is not required to dedicate a category to conference messages. |
|_iim_arch.chat.categoryname_ |Name |This parameter contains the name of the category containing the archived chat messages.It is not required to dedicate a category to chat messages. |
|_iim_arch.news.categoryname_ |None |This parameter contains the name of the category containing the archived news messages.It is not required to dedicate a category to news messages. |
|_iim_arch.conference.quiettime_ |{{5}} |This parameter contains the maximum duration of silence between two consecutive messages in a room (both public and private) after which the RD expires and a new RD is created for archiving the message. The value is in minutes. |
|_iim_arch.poll.maxwaittime_ |{{15}} |This parameter contains the (maximum) time for which poll data is buffered in the server. The value is in minutes. |
|_iim_arch.ignoreexplicitdeny_ |{{true}} |This parameter will contain {{true}} or {{false}}. \\ {{true}} - For Poll and Conference category the data with explicit deny access will not be archived. Each time when these messages are not archived this information will be logged into the {{xmppd.log}} file. \\ {{false}} - For Poll and Conference category the data with explicit deny access will not be archived and the message will be added to the Portal Server Search database.Note: If you do not explicitly deny access to a room or a news channel then the default access is either {{READ}} or {{WRITE}} or {{MANAGE}}. Some end users can also be granted {{NONE}} access. |
|_iim_arch.portal.search_ |None |The value of the this parameter should be the URL of the Portal Server Search servlet. For example: http://www.example.com/portal/search. If this parameter is not present then the Archive Provider determines the value of the Portal Server Search URL based on the {{AMConfig.properties}} file present on the system. |
|_iim_arch.portal.admindn_ |None |The value of this parameter should be the DN of the admin user. For example: {{uid=amadmin,ou=People,o=internet}}. This parameter is required when the Document level Security in the Portal Server Server is on. |
|_iim_arch.portal.adminpassword_ |None |The value of this parameter should be the password of the administrative user as specified by the _iim_arch.portal.admindn_ parameter. This parameter is required when the Document level Security in the Portal Search Server is on. |
|_iim_arch.portal.search.database_ |None |The value of this parameter should be the name of the database where the Instant Messaging server stores archived messages. If this parameter is not defined then all messages are stored in the default database of Portal Server Search. |
|_iim_arch.admin.email_ |Empty String |Comma-separated list of administrator email addresses. |
|_iim_arch.alert.admin.email_ |None |Comma-separated list of administrator email addresses to which all archived alert messages will be sent. This parameter overrides _iim_arch.admin.email_ for alert messages. |
|_iim_arch.chat.admin.email_ |None |Comma-separated list of administrator email addresses to which all archived chat messages will be sent. This parameter overrides _iim_arch.admin.email_ for chat messages. |
|_iim_arch.conference.admin.email_ |None |Comma-separated list of administrator email addresses to which all archived conference messages will be sent. This parameter overrides _iim_arch.admin.email_ for conference messages. |
|_iim_arch.poll.admin.email_ |None |Comma-separated list of administrator email addresses to which all archived poll messages will be sent. This parameter overrides _iim_arch.admin.email_ for poll messages. |
|_iim_arch.news.admin.email_ |None |Comma-separated list of administrator email addresses to which all archived news messages will be sent. This parameter overrides _iim_arch.admin.email_ for news messages. |
|_iim_arch.email.archiveheader.name_ |None |Name of the extended RFC 822 header. |
|_iim_arch.email.archiveheader.value_ |{{all}} |Value corresponding to the header name for _iim_arch.email.archiveheader.name_. |
{anchor:achfx}

[Top|#top]
h2. Watchdog Parameters

The watchdog monitors the server process and attempts to restart the server if it determines that the server is not running. See [Managing the Watchdog Process|http://wikis.sun.com/display/CommSuite/Troubleshooting+and+Monitoring+Instant+Messaging#TroubleshootingandMonitoringInstantMessaging-ManagingtheWatchdogProcess]

[Table&nbsp;A-10|#fvccb] lists and describes the watchdog configuration parameters.

h5. {anchor:fvccb} Table&nbsp;A-10 Watchdog Configuration Parameters
||Parameter ||Default Value ||Description ||
|_iim_wd.enable_ |{{true}} |Enables the watchdog feature. To reset this parameter or disable the watchdog, set this to {{false}}.To avoid conflicts, you should disable the watchdog if you are monitoring the Instant Messaging server using the operating system administration console. |
|_iim_wd.period_ |{{300}} (seconds) |The watchdog periodically polls the server to check whether it is running. This parameter sets the interval between two status polls. |
|_iim_wd.maxRetries_ |{{3}} |Sets the number of retries, times the watchdog will attempt to contact the Instant Messaging server, before shutting down and restarting the server. The maximum is ten retries. |
{anchor:gamsf}

h2. Monitoring Parameters

The parameter in [Table&nbsp;A-11|#gamsh] configures how the server interacts with the Sun Java Enterprise System Monitoring Framework.

h5. {anchor:gamsh} Table&nbsp;A-11 Monitoring Parameters
||Parameter ||Default Value ||Description ||
|_iim_server.monitor.enable_ |{{false}} |Used by the Sun Java Enterprise System Monitoring Framework. If {{true}}, configures the server to make its activities available to {{mfwk}}. Otherwise, the server does not make its activities available. |
|_iim_server.monitor.htmlport_ |None |If specified, opens the JMX HTML adaptor port on the specified port. By default, this port is not enabled as opening this port can present a security risk. |
{anchor:achfy}

[Top|#top]
h2. Agent Parameters

Agents, such as the Calendar agent, enable functionality within the Instant Messaging server and enhance its interoperability with other Sun Java System servers.

[Table&nbsp;A-12|#fvccd] lists and describes agent configuration parameters.

h5. {anchor:fvccd} Table&nbsp;A-12 Agent Configuration Parameters
||Parameter ||Default Value ||Description ||
|_jms.consumers_ |None |Used with the Calendar agent. Contains the name of the alarm. The value for this parameter must be set to:{{cal_reminder}} |
|_jms.consumer.cal_reminder.destination_ |None |Used with the Calendar agent. Destination of the alarm. This must be the same as the value of the _caldb.serveralarms.url_ configuration parameter in the {{ics.conf}} file. For example,{{enp:///ics/customalarm}} |
|_jms.consumer.cal_reminder.provider_ |None |Used with the Calendar agent. The name of the provider. Typically, this is set to {{ens}}. The value for this parameter must be the same as the name in the _jms.providers_ parameter. |
|_jms.consumer.cal_reminder.type_ |None |Used with the Calendar agent. The type of alarm to set. The value for this parameter must be set to:{{topic}} |
|_jms.consumer.cal_reminder.param_ |None |Used with the Calendar agent. The alarm parameter. The value for this parameter must be set as follows including the quotes:{{"eventtype=calendar.alarm"}} |
|_jms.consumer.cal_reminder.factory_ |None |Used with the Calendar agent. A listener that registers itself for the new calendar reminder messages. The value for this parameter must be set to:{{com.iplanet.im.server.JMSCalendarMessageListener}} |
|_jms.providers_ |None |Used with the Calendar agent. The name of the provider. Typically, you set the value of this parameter to {{ens}}. This must be the same as the value for the _jms.consumer.cal_reminder.provider_ parameter. |
|_jms.provider.ens.broker_ |None |Used with the Calendar agent. Hostname of the ENS and the port number on which the ENS listens for incoming requests. Set to the port specified in the {{ics.conf}} file _service.ens.port_ parameter. The default is 57997. For example:{{jms.provider.ens.broker=cal.example.com:57997}} |
|_jms.provider.ens.factory_ |None |Used with the Calendar agent. Factory class used for creating the topic connection objects. The value for this parameter must be set as follows. Enter the value on a single line:{{com.iplanet.ens.jms.EnsTopicConnFactory}} |
|_iim_agent.enable_ |{{False}} |If {{TRUE}}, {{iim.conf}}, enables Instant Messaging agents. Set the value to {{FALSE}}, or remove the parameter from {{iim.conf}} to disable all agents. |
|_iim_agent.agent-calendar.enable_ |None |Used with the Calendar agent. If {{TRUE}} or absent from {{iim.conf}}, loads a component that enables the Calendar agent specifically. |
|_agent-calendar.jid_ |None |The JID of the Calendar agent. |
|_agent-calendar.password_ |None |Defines the password with which the Calendar agent connects to the Instant Messaging server. |
|_iim_server.components_ |None |Describes the Calendar agent as a component of the Instant Messaging server. The value of this parameter must be set to:{{agent-calendar}} |
|{{agent-calendar.imadmin.enable}}| "false"| Start the agent-calendar by using the {{imadmin}} command if set to {{true}}.|
| {{agent-calendar.iim_server.host}}| | Host name of the Instant Messaging server with which the agent calendar
communicates.|
| {{agent-calendar.iim_server.port}}| | Port number of the Instant Messaging server with which the agent calendar
communicates.|

h2. HTTP/XMPP Gateway Parameters

[Table&nbsp;A-13|#gamsh1] lists the parameters you use to bind to the HTTP/XMPP gateway.

h5. {anchor:gamsh1} Table&nbsp;A-13 HTTP/XMPP Gateway Parameters
||Parameter ||Default Value ||Description ||
|_iim_agent.httpbind.enable_|false|Set to {{true}} to enable the HTTP/XMPP gateway.
|_httpbind.jid_| | A jabber ID (JID) to bind the HTTP/XMPP gateway.
|_httpbind.password_| |Password to authenticate the HTTP/XMPP gateway to the Instant Messaging server.


h2. SMS Integration Parameters

[Table&nbsp;A-14|#gamsh2] lists the SMS integration parameters.

h5. {anchor:gamsh2} Table&nbsp;A-14 SMS Integration Parameters
||Parameter ||Default Value ||Description ||
|_smsgw.imadmin.enable_|false | Enables or disables the SMS gateway. If set to {{true}}, you can start the SMS gateway by using the {{imadmin}} command.
|_smsgw.jid_| None | A jabber ID (JID) to bind the SMS gateway to the Instant Messaging server. The value of this parameter should be the same as the value that you define for the {{smppbind.jid}} parameter.
|_smsgw.password_| | Password to authenticate the SMS gateway to the Instant Messaging server. The value of this parameter should be the same as the value that you define for the {{smppbind.password}} parameter.
|_smsgw.iim_server_ | None | Hostname and port number of the Instant Messaging server.
|_smsgw.sms_limit_| -1 | Number of messages that can be sent per hour. The default value is {{-1}} and it indicates that unlimited number of SMS messages that can be sent per hour.
|_smsgw.sms_queue_capacity_|512 | Maximum number of messages that can be queued for SMS delivery.
|_smsgw.im_char_limit_|500 | Maximum number of characters that you can specify in one message. If the number of characters is greater than the specified value, the message is rejected.
|_smpp.smsc_ip_address_|None | IP address or hostname of the SMSC.
|_smpp.smsc_port_| {{2775}} | Port number of the SMSC.
|_smpp.bind_id_|None | Identifier used to bind the SMS gateway to the SMSC.
|_smpp.bind_password_| | Password to authenticate the SMS gateway to the SMSC.
|_smpp.sender_id_| None | Sender ID of the outgoing SMS.
|_iim_server.components_ |None | List of component identifiers that should have {{smppbind}}. For example, httpbind, smppbind.
|_iim_agent.smppbind.enable_|false | Enables the Instant Messaging server to identify the SMS gateway.
|_smppbind.jid_| None | A jabber ID (JID) for binding the SMS gateway to the Instant Messaging server.
|_smppbind.password_| | Password to authenticate the SMS gateway to the Instant Messaging server.

h2. MSN Gateway Integration Parameters

[Table&nbsp;A-15|#gamsh3] lists the MSN gateway integration parameters.

h5. {anchor:gamsh3} Table&nbsp;A-15 MSN Gateway Integration Parameters
||Parameter ||Default Value ||Description ||
|_iim_agent.msn_gateway.enable_| {{false}} | Set to {{true}} to enable the MSN gateway on IM server.
|_msn_gateway.jid_ | {{msn.$domainname}} | A jabber ID (JID) for binding the MSN gateway to the Instant Messaging server.
|_msn_gateway.password_| {{changeit}} | Password to authenticate the MSN gateway to the Instant Messaging server.
|_msn_gateway.imadmin.enable_| {{false}} | If set to {{true}}, you can start the MSN gateway by using the {{imadmin start}} command.

h2. AOL Gateway Integration Parameters

[Table&nbsp;A-16|#gamsh4] lists the AOL gateway integration parameters.

h5. {anchor:gamsh4} Table&nbsp;A-16 AOL Gateway Integration Parameters
||Parameter ||Default Value ||Description ||
|_iim_agent.aim_gateway.enable_| {{false}} | Set to {{true}} to enable the AIM gateway on IM server.
|_aim_gateway.jid_ | {{aim.$domainname}} | A jabber ID (JID) for binding the AIM gateway to the Instant Messaging server.
|_aim_gateway.password_ | {{changeit}} |Password to authenticate the AIM gateway to the Instant Messaging server.
|_aim_gateway.imadmin.enable_ | {{false}} |If set to {{true}}, you can start the AIM gateway by using the {{imadmin start}} command.

h2. YAHOO Gateway Integration Parameters
[Table&nbsp;A-17|#gamsh5] lists the YAHOO gateway parameters.

h5. {anchor:gamsh5} Table&nbsp;A-17 YAHOO Gateway Parameters
||Parameter ||Default Value ||Description ||
|_iim_agent.yim_gateway.enable_| {{false}}| Set to {{true}} to enable the YAHOO gateway on IM server.
|_yim_gateway.jid_| {{yim.$domainname}} | A jabber ID (JID) for binding the YAHOO gateway to the Instant Messaging server.
|_yim_gateway.password_ | {{changeit}} |Password to authenticate the YAHOO gateway to the Instant Messaging server.
|_yim_gateway.imadmin.enable_ | {{false}} |If set to {{true}}, you can start the YAHOO gateway by using the {{imadmin start}} command.

h2. IMPS Gateway Parameters

[Table&nbsp;A-18|#gamsh5] lists the IMPS gateway parameters.

h5. {anchor:gamsh5} Table&nbsp;A-18 IMPS Gateway Parameters
||Parameter ||Default Value ||Description ||
|_iim_ldap.sasl.mechanism.factories_|"com.iplanet.im.server.sasl.IMPSSASLProviderFactory"|Parameter to specify the mechanism that will be used for authentication.
|_iim_ldap.userpasswordattr_|"userpassword" | Specifies the field that should be used for authentication. By default, {{"userpassword"}} is used for authentication.

h2. Java Message Queue (JMQ) Parameters

[Table&nbsp;A-19a|#gamslt1] lists the JMQ parameters
This table lists some of the Java Message Queue (JMQ) parameters that need to be specified.

h5. {anchor:gamslt1} Table&nbsp;A-19a JMQ Parameters
||Parameter||Value\\(including the quotation mark)||Description||
|*JMS Consumers section*| | |
|{{jms.consumers}}|{{"cal_reminder2"}}|Name of the alarm. By default, {{jms.consumers}} is commented out in the {{iim.conf}} file. Make sure to uncomment this line.
|{{jms.consumer.cal_reminder2.provider}}|{{"jmq"}}|Name of the provider. Java Message Queue should be mentioned as a provider. The string {{jmq}} is used in the agent code to instantiate the Java Message Queue specific classes.
|{{jms.consumer.cal_reminder2.type}}|{{"topic"}}| The type of the alarm to set.
|{{jms.consumer.cal_reminder2.factory}}|{{"com.iplanet.im.server.JMSCalendarMessageListener"}}|The name of the C++ factory.
|{{jms.consumer.cal_reminder2.destination}}|{{"testTopic"}}|Destination of the alarm. The destination type is {{topic}}. The {{topic}} can be administratively created or the Java Message Queue provider can be configured to create a topic for publishing a message to it. When the Calendar agent starts, it tries to subscribe to the configured {{topic}}. If the topic is not already present in the Java Message Queue broker, the Calendar agent fails to subscribe to the {{topic}}. Therefore, it is necessary to start the Java Message Queue broker and create the {{topic}} before starting the Calendar agent. For the commands to start the Java Message Queue broker and create a {{topic}}, see [Some Useful Java Message Queue Commands|http://wikis.sun.com/display/CommSuite/Configuring+JMS+Support+for+Calendar+Server+Alerts#ConfiguringJMSSupportforCalendarServerAlerts-SomeUsefulJavaMessageQueueCommands].
|*JMS Providers section*| | |
|{{jms.providers}}|{{"jmq"}}|The name of the provider.
|{{jms.provider.jmq.broker}}|{{"yourJMQserver:port"}}|Port number that the Java Message Queue server listens to. {{jms.provider.jmq.broker}} should be the fully qualified host name or IP address and port that your Java Message Queue server is listening on. For example, {{localhost:7676 or jmqhost.beta.comms.com}}
|{{jms.provider.jmq.factory}}|{{"com.sun.messaging.TopicConnectionFactory"}}|Name of the C++ factory.
|{{jms.provider.jmq.jmsuser}}|{{"guest"}}|The user ID of the JMS user. A Java Message Queue user is created in the Java Message Queue provider user database. If access to the Java Message Queue provider or the topic is controlled, specify the username. The username is provided by the Calendar agent while establishing connection with the Java Message Queue provider. If this parameter is not specified, the agent tries to connect anonymously.
|{{jms.provider.jmq.jmspswd}}|{{"passwd"}}|The password of the JMS user.
|{{iim_agent.enable}}| {{"true"}} |Enables agents for Instant Messaging. Set the value to {{iim_agent.enable="true"}}.
|{{iim_agent.agent-calendar.enable}}|{{"true"}} |Loads a component that enables the Calendar agent. Set the value to {{iim_agent.agent-calendar.enable="true"}}.
|{{agent-calendar.jid}}| {{calendar.siroe.com}} | Java ID of the Calendar agent. Set the value to {{agent-calendar.jid=calimbot.server.domain}}.
|{{agent-calendar.password}}| | Password you want the Calendar agent to use to connect to the Instant Messaging server. Set the value to {{agent-calendar.password=password}}.
|{{iim_server.components}}| {{agent-calendar,httpbind}} | Set the value to {{iim_server.components=agent-calendar}}.
|{{agent-calendar.imadmin.enable}}| "false"| Start the agent-calendar by using the {{imadmin}} command if set to {{true}}.|
| {{agent-calendar.iim_server.host}}| | Host name of the Instant Messaging server with which the agent calendar
communicates.|
| {{agent-calendar.iim_server.port}}| | Port number of the Instant Messaging server with which the agent calendar
communicates.|