| Sun ONE Instant Messaging 6.1 |
Chapter 3
Managing Sun™ ONE Instant MessengerThis chapter describes how to customize and administer Sun™ ONE Instant Messenger.
This chapter contains the following:
Configuring Sun ONE Instant MessengerThere are two ways to configure and invoke Sun ONE Instant Messenger:
Using Java Web Start In this configuration, Sun ONE Instant Messenger is launched as an application from the Java Web Start. The browser is no longer necessary once Sun ONE Instant Messenger is launched.
Using the Java Plug-in In this configuration, Sun ONE Instant Messenger is run as a Java applet. To keep the Instant Messenger session active, the browser window from which the applet was launched must remain open and cannot be used to locate any other URL.
For more information on how to configure the Java software that enables Sun ONE Instant Messenger, see the Sun One Instant Messaging Installation Guide.
Invoking Instant MessengerYou can invoke Sun ONE Instant Messenger using:
- The index.html file that provides you the options to launch both the Java Web Start and Java Plug-in versions of the Sun ONE Instant Messenger. This file also contains links to Sun ONE Instant Messenger documentation.
- The web page that you have designed with a link to Sun ONE Instant Messenger.
- A direct URL for either the im.html or im.jnlp files.
To Invoke Sun ONE Instant Messenger
Use the following URL to invoke the Instant Messenger.
http://webserver:webserverport/subdirectory/filename
In this URL,
You can also, do the following:
Solving Web Server IssuesThis section describes web server issues that apply to LDAP deployments and also to portal deployments, where Instant Messenger is not installed on the Portal Server host and uses a different Web Server to provision Sun ONE Instant Messenger.
Changing the Codebase
The web-server-resource directory can be the same directory as the instant-messaging-resource directory. However, they do not need to be the same. If they are not the same for your site, use the appropriate method from the following to enable the web server to download the Sun ONE Instant Messenger resources:
- URL to launch Sun ONE Instant Messenger - The URL that is used by end users to access the index.html (and im.html and im.jnlp files). This URL needs to reference the Sun ONE Instant Messenger installation directory.
For example, if the Sun ONE Instant Messaging server host is iim.i-zed and the Sun ONE Instant Messenger files are installed in the /opt/SUNWiim/html directory, you need to create a symbolic link, such as iim, in the web-server-resource directory which points to /opt/SUNWiim/html. End users can access the Sun ONE Instant Messenger main page index.html using the following URL:
- Launch the Instant Messenger using Java Web Start- If the Instant Messaging Codebase specified during the installation is changed then you need to change the codebase parameter in the im.jnlp file to reference the web server and the Sun ONE Instant Messenger path. The following is the change to the codebase parameter:
codebase= http://servername:port/path/
You need to include the port number of the web server if it is not configured to the default value 80.
For example, if the Instant Messaging server host is iim.i-zed and the Sun ONE Instant Messenger files are installed in the /opt/SUNWiim/html directory, you can create a symbolic link such as iim which points to /opt/SUNWiim/html in the web-server-resource directory. Then change the codebase parameter in the im.jnlp file to the following:
codebase="http://iim.i-zed.com/iim/"
Changing Web Server Port
If your web server is installed on a port other than the default (80), you need to know the following details:
Customizing Sun ONE Instant MessengerSun ONE Instant Messenger is customizable. HTML and JNLP files can be customized to suit an organization's specific needs.
You can customize the Instant Messenger to meet your requirements in the following ways:
This section describes the Instant Messaging server files you can modify to customize Sun ONE Instant Messenger. The files that you can customize are all located in the html directory. For example, on Solaris the HTML files are located in the instant-messaging-resource directory.
Instant Messenger ResourcesSun ONE Instant Messenger Files
The Sun ONE Instant Messenger files are located within the directory referred to as the instant-messaging-resource directory, which is also simply referred to as the resource directory.
Table 3-1 contains the list of Sun ONE Instant Messenger files in the instant-messaging-resource directory. It also contains the description and the customization information of these files.Within the instant-messaging-resource directory, is the locale subdirectory represented generically in a directory path as lang, but specifically as abbreviations of languages, such as, en_US, jp, and fr_FR.
Customizing the index.html and im.html Files (Only LDAP Deployments)
The Instant Messenger allows you to modify the “static” portion of the index.html and im.html files to produce a fully customized user interface. These HTML files contain both text and markups describing how the text is formatted and handled. Markup is implemented through a set of tags, which specify formats for headers, indents, font size, and font style.
Some of the page elements that can be modified are:
The index.html file launches both the Sun ONE Instant Messenger applet and the Java Web Start application. If you are running the Sun ONE Instant Messenger applet, modify the im.html file. The im.html file is called by index.html, and invokes the Instant Messenger applet. The im.html file is generated during the installation and contains an applet argument that points to the multiplexor.
Launching Instant Messenger Using Sun ONE Identity Server SSO:
To launch the Sun ONE Instant Messenger client using single sign-on with Identity Server use jnlpLaunch.jsp and pluginLaunch.jsp. These files are in the resource directory. To launch the Instant Messaging server enter the following in the browser:
instant-messaging-codebase/jnlpLaunch.jsp?server=muliplexor-hostname:muliplexor-port
or
intant-messaging-codebase/pluginLaunch.jsp?server=www.example.com:49909
where,
intant-messaging-codebase is the codebase from which the Instant Messenger resources are downloaded. For example, http://www.example.com.
(multiplexor)-hostname is the name for the mulitplexor. For example, http://www.compnay22.com.
(multiplexor) port is the multiplexor port number. For example, 49909
jnlpLaunch.jsp is used for launching Instant Messenger using Java Web Start.
pluginLaunch.jsp is used for launching Instant Messenger using Java Plug-in.
Customizing the Application (Java Web Start)
If you are running Sun ONE Instant Messenger using Java Web Start, you can modify the im.jnlp, imres.jnlp, and imres.jar files to customize the user interface. The following are modifications that can be made to these HTML files:
Code Example 3-1 shows a sample im.jnlp file with the HTML code that can be customized in bold typeface.
Note
In the im.jnlp file, the argument <argument>servername</argument> represents the Sun ONE Instant Messaging multiplexor host and port. If you change the default value of iim_mux.listenport parameter, you need to change the servername value to host.domain:port.
- imbrand.jar - This file contains the image and audio files, and the properties that can be customized. You need Java Developers Kit 1.3(JDK) to extract the contents from the imres.jar file using the jar command. For more information on the imbrand.jar file contents, see Contents Listing of imbrand.jar file.
The following is the syntax for the jar command:
jar xvf imbrand.jar
This command creates a directory tree where the resource files are copied. This directory structure has to be maintained when you modify the individual files in the jar file.
You can substitute your version of .gif files or .au files, without changing the file names and then place the changed files back to the directory using the following jar command:
jar -uf imbrand.jar com/Sun/im/client/images/*.gif
This command updates the imbrand.jar file with the modified .gif files. The same is possible with the audio files (.au files).
Contents Listing of imbrand.jar
Table 3-2 lists the files in the imbrand.jar file and their description. The imbrand.jar file contains the image and audio files that can be used to re-brand the Sun ONE Instant Messenger.
Table 3-2 Contents Listing of imbrand.jar file.
File Name
Description
Angry_16.gif
An emoticon used to show angry emotion graphically.
Devil_16.gif
An emoticon used to show devilish emotion graphically.
Laugh_16.gif
An emoticon used to show laugh emotion graphically.
Angel_16.gif
An emoticon used to show angelic emotion graphically
Smiley_16.gif
An emoticon used to show smile emotion graphically.
Love_16.gif
An emoticon used to show love emotion graphically
Grin_16.gif
An emoticon used to show grin emotion graphically.
Wink_16.gif
An emoticon used to show wink emotion graphically.
Sad_16.gif
An emoticon used to show sad emotion graphically.
Suprise_16.gif
An emoticon used to show suprise emotion graphically.
Away_13.gif
Icon for away status that appears in the Change Status menu.
Online_13.gif
Icon for online status that appears in the Change Status menu.
Offline_13.gif
Icon displayed when an end user is away or not connected that appears in the Change Status menu.
Idle_13.gif
Icon to show idle status, appears in the status bar and contact list.
Forwarded_13.gif
Icon displayed against end users when they are offline and have set alerts to be forwarded to email. This icon appears in the contact list.
Away_24.gif
Icon for away status that appears in the status bar.
Online_24.gif
Icon for online status that appears in the status bar.
Offline_24.gif
Icon for offline status that appears in the status bar.
tray_icon.ico
Instant Messenger icon that appears on the task bar.
app_icon.gif
The Instant Messenger application icon.
logon_splash.gif
The Sun ONE logo displayed in the Login and About boxes
alert.au
Sound when an end user receives an alert.
away.au
Sound when an end user changes status to away.
soundon.au
Sound when an end user exits Instant Messenger.
soundoff.au
Sound when an end user logs on to Instant Messenger.
send.au
Sound when an end user sends an instant message.
receive.au
Sound when an end user receives an instant message.
Rebranding Instant Messenger
The imbrand.jar file contains all images and the properties that control the look and feel of the Instant Messenger. You can customize the appearance of the Instant Messenger by modifying the images and the properties in the imbrand.jar file.
To re-brand the Instant Messenger:
- Copy imbrand.jar file to a working directory and change to this directory. For example:
cp instant-messaging-resource-directory/lang/imbrand.jar working_directory
- Extract the imbrand.jar file.
jar xf imbrand.jar
This command creates a directory tree where the resource files are copied. This directory structure has to be maintained when you modify the individual files in the jar file.
- Update the imbrand.jar file with the modified .gif files and .au files.
jar cf imbrand.jar .
- Copy the imbrand.jar file to the resource directory. For example:
cp imbrand.jar instant-messaging-resource-directory/lang/.
Customizing User Name Display
The User Name display can be customized in the tooltip and the search results.
Customizing User Name Display in Search Results
When two end users have the same first name and last name, it is impossible to know which end user has to be added to the contact list. You can customize the Instant Messenger to display more information in the search results for the user search. For displaying more information in the user search results, in the imbrand.jar file you need to add dialogs.searchresults.format attribute to the brand.properties file at:
com/sun/im/client/
For more information on how to modify imbrand.jar, see Customizing the Application (Java Web Start).
More information can be displayed in the user search results by including additional LDAP attribute values in the dialogs.searchresults.format attribute.
The LDAP attributes are specified in the following format:
${attr:attribute-name}
The following example shows the LDAP attribute in dialogs.searchresults.format attribute:
dialogs.searchresults.format=(${attr:title})
To use arbitrary attributes from the LDAP user entry, the list of these custom attributes needs to be specified in the server configuration file iim.conf. These custom attributes need to be specified as values for the attribute iim_ldap.userattributes.
The following example shows the iim_ldap.userattributes with the list custom attributes as value:
iim_ldap.userattributes=title,department,telephonenumber
Customizing User Name Display in Tooltip
You can customize the Instant Messenger to display additional information in the Contact tooltip.
For example, to display the phone number of the Contact when the mouse is placed over the Contact:
- Change to the following directory:
com/sun/im/client/
- Open the brand.properties file.
- Add the contact.tooltip.format.html attribute to the file.
- Save the changes to the file
- Change to the following directory.
cd instant-messaging-resource-directory
- Add the contact.tooltip.format.html attribute and the telephonenumber attribute as its value in the HTML code of the imbrand.jar file:
contact.tooltip.format.html=mailto: ${attr:mail} tel: ${attr:telephonenumber}
For information on customizing the imbrand.jar file, see Customizing the Application (Java Web Start).
Administering Sun ONE Instant Messenger Conference Rooms and News ChannelsListed below are tasks that you can perform in Sun ONE Instant Messenger to administer the conference rooms and the news channels. For more information on performing these tasks, see the Sun ONE Instant Messenger Online Help.
- Administering conference rooms
- Administering and managing news channels
- Assigning conference room access levels to end users
- Assigning news channel access levels to end users
- Assigning end users to conference rooms
- Assigning end users to news channels (subscribing)
- Creating new conference rooms
- Creating new news channels
- Configuring end user settings
- Deleting conference rooms
- Deleting messages from news channels
- Deleting news channels
- Posting messages in news channels
- Removing end users from conference rooms
- Removing end users from news channels
Granting End Users the Privilege to Create Conference Rooms and News Channels
The administrator can create conference rooms and news channels for end users. However, with the proper privileges, end users can do this also. For more information about adding policies to give end users access to create conference rooms and news channels, see Chapter 4, "Managing Instant Messaging and Presence Policies". End users who create a conference room or a news channel by default have Manage access, enabling them to administer the conference room or the news channel. For more information on managing end-user privileges, see "Managing End-User Privileges".
Modifying Sun ONE Instant Messenger Proxy SettingsSun ONE Instant Messaging messages can contain embedded URLs. For example, http://stocks.yahoo.com?id=sunw. If you are using proxy servers, you need to resolve such embedded URLs by modifying the Instant Messenger proxy settings in the Java Web Start configuration.
This is likely to happen if your organization has a firewall, and you need to go through the proxy server before connecting your client hosts to internet, and if Java Web Start has not been configured with the right proxy settings.
To Modify Sun ONE Instant Messenger Proxy Settings
Java Web Start can automatically configure the proxy settings by querying the system or the default browser. However, it is not possible for the Java Web Start to automatically configure these settings if the proxy settings are configured using a JavaScript file.
To set the proxy settings manually:
HTTP Proxy. Enter the Name or the IP address of the proxy server.
HTTP Port. Enter the port number of the proxy server.
No Proxy_Hosts. Enter the name of any domain that you can connect directly, bypassing the proxy server. Use commas to separate multiple host names.
Controlling the Exposed Messenger Feature SetThe exposed feature set of the Instant Messenger can be controlled by the administrator by configuring the Instant Messaging applet parameters in the applet descriptor files.
Table 3-3 shows the Instant Messenger applet parameters in the applet descriptor files. It also contains the description and the default values of these parameters.
Table 3-3 Instant Messenger Applet Parameters
Parameter
Default Value
Description
server
127.0.0.1
The Instant Messaging server host and port.
debug
FALSE
If this parameter is set to true, the applet records all the task performed on java console.
uid
This parameter is used for SSO.
token
This parameter contains SSO token and is used for auto-logon.
secure
FALSE
Indicates to the Instant Messenger that it is run in SRA mode. It displays a security indicator.
usessl
FALSE
Tells Instant Messenger to use SSL when connecting to server.
allow_alert_only
FALSE
Tells Instant Messenger to let end user display neither the contact list nor the news channel.
This parameter is used in CHAT and POPUP flavors.
allow_file_transfer
TRUE
Allows file attachment and transfer.
enable_moderator
TRUE
If set to true, enables the moderated conference feature.
messenger_bean
This parameter contains a list of messenger beans to be used. You can enter multiple factory class names with each separated by a comma.
domain
null
This parameter is used in multi-domain Sun ONE Identity Server deployments. The value of this parameter should be the logical domain name of the organization in which this end user is present.
gateway_url
null
This parameter contains the URL of the gateway component of portal SRA.
Instant Messenger Data Stored in the End User’s SystemInstant Messenger caches a limited amount of information on the end user’s system for auto-login. This information can be located at:
home-directory/.sunmsgr
home-directory is the end user's home directory. The home directory of the end user can be obtained from the user.home parameter in the Java system property.
Table 3-4 shows the directories and files containing the cached data. It also contains the description of the files and the directories.
Table 3-4 The directory and files containing the cached data
File/Directory Name
Type
Description
.sunmsgr/messenger.properties
file
The file containing the auto-logon properties
.sunmsgr/<user_domain>/
directory
Directory containing data specific to a particular {log-in name, domain name} combination.
.sunmsgr/<user_domain>/messenger.properties
file
This file contains auto-logon options specific to particular <user_domain>. This file is not used.
.sunmsgr/<user_domain>/messages/
directory
This directory contains cached messages. This directory is not used.
Table 3-5 shows the auto-logon properties for Instant Messaging. It also contains the description and the default values of these properties.
Table 3-5 The Auto-logon Properties
Parameter
Default Value
Description
net.server
127.0.0.1
Instant Messaging server host name and port.
net.server.n
(Where n is a digit used to distinguish one entry from another)
The secondary servers' host names and port numbers.
net.user
The default user id
net.pass
The encoded user password that enables auto-logon.
