Contents

Release Notes

- New Features

- Chat Room Participation Based on LDAP Group Membership

- Server-to-Server Federation Support between XMPP Server and SIP/SIMPLE Federation Service Gateway

- Fixes in This Release

- Known Problems

- Pidgin BOSH Client Is Not Able to Log In if DIGESTMD5 Enabled in Pool Environment

- Server-to-Server Whitelisting Is Not Supported After an Upgrade from Instant Messaging 8 Releases to Instant Messaging 9

- Comments in the iim.conf File Need to Be Removed Before Upgrading

- Space Next to Equal Sign (=) in iim.conf File Is Not Handled Correctly in Upgrade to Instant Messaging Server 9

- Parameters Are Not Migrated in Upgrade From Instant Messaging Server 8 Patch 6 to Instant Messaging Server 9

- Parameters in Instant Messaging Server 8 Patch 6 Need to Be Set Manually After Upgrading to Instant Messaging Server 9

- SMF Status Is Not Preserved After Upgrade

- Communication Delay During Multi-User Chat Room Join Phases Under Load

- Delay In Affiliation Change in Multi-User Chat Room Under Load

- Delay in 1:1 Chat and Multi-User Chat Room When Users Are Connected Through HTTPBIND

- Presence of Contacts Does Not Show Correctly When User Logs Out and Logs In

- Could Not Load Roster for User Error

- Communication Break Occurs Between Peers When Run in Solaris Non-Global Zones or LDOMs

- Deprecated and Removed Features

- Documentation Updates

- Documentation Accessibility

Oracle® Communications Instant Messaging Server

Release Notes

Release 9.0.2

E53653-01

August 2014

This document provides release notes for Oracle Communications Instant Messaging Server Release 9.0.2, consisting of the following sections:

- New Features

- Fixes in This Release

- Known Problems

- Deprecated and Removed Features

- Documentation Updates

- Documentation Accessibility

New Features

The new features in this release of Instant Messaging Server are:

- Chat Room Participation Based on LDAP Group Membership

- Server-to-Server Federation Support between XMPP Server and SIP/SIMPLE Federation Service Gateway

For information on how to configure and use these new features, see Instant Messaging Server System Administrator's Guide.

Chat Room Participation Based on LDAP Group Membership

Starting with Instant Messaging Server 9.0.2.6.0, you can assign/affiliate LDAP groups as members of a restricted chat room. When Instant Messaging Server creates the multi-user chat room, it loads the chat room's affiliations from LDAP. Instant Messaging Server determines if the user is a member of any of the groups authorized for the multi-user chat room. Instant Messaging Server then allows the users to join if they are members and otherwise forbids users from joining.

Server-to-Server Federation Support between XMPP Server and SIP/SIMPLE Federation Service Gateway

Starting with version 9.0.2.6.0, Instant Messaging Server can provide server-to-server federation support between any standard XMPP server and the SIP/SIMPLE Federation Service Gateway. The Instant Messaging Server SIP Gateway uses either Jabber Component Protocol or Server-to-Server federation for interoperability. The SIP/SIMPLE support using Jabber Component Protocol is only supported with Oracle Communications Instant Messaging server and not with any other third-party XMPP server. For any other third-party XMPP server, you must configure the Server-to-Server federation option.

Fixes in This Release

This section lists the fixed issues in this release of Instant Messaging Server.

Table 1 Fixed Issues

Service Request (SR) Number

BugDB Number

Description

NA

18900246

Remove properties related to legacy SSL

NA

18899896

Remove deprecated options in imadmin command

NA

18759210

Instant Messaging avatar is not displayed in server-to-server (server federation)

NA

18684027

Presence status update for httpbind users showing offline when peer is restarted

NA

18635453

Make parameters restricted because they are deployment specific

NA

18556566

Rename configuration options for SIP outbound blacklist and whitelist domains

NA

18481931

Add CollabAPI level logging to log4j

NA

18431105

Showing incorrect presence of federated user, after blocking and unblocking the federated user

NA

18401213

Ping support between peers in server pool

NA

18400991

Changing password of other user is not handled properly

NA

18375031

Creation of SIP war file should not depend on existence of iim.conf.xml file

NA

18356402

Stream reopen fails after SASL negotiation is successful in OutServerConnection

NA

18318001

Peer users shown offline and split conference seen when network interface is restarted

NA

18266836

Use of dynamic groups in multi-user chat is not working in hosted domain

NA

18265097

Server should log out existing sessions if a user is removed from store

NA

18261965

Conversion of persistent public room to restricted room is not working

NA

18244356

Provide imconfutil command support for setting process queue

NA

18244339

Server-to-server server id printed as null in logs, difficult to debug the problematic connection

NA

18159671

Group chat enters into invalid state when no LDAP contexts are available

NA

18140560

Server-to-server federation support in SIP Gateway

NA

18101394

Peer server connection retry when an incoming connection is made

NA

18093101

Clean up Instant Messaging Server schema and make corresponding changes in code

NA

17955884

Presence API should respond immediately to the request if user does not exist

NA

17907851

IMQ shared dependency removal

NA

17809951

Duplicate messages in multi-user chat when peer user joins the room

NA

17787231

Not allowed to participate in this room error seen in performance tests

NA

17781761

With SE Linux in Permissive mode, imadmin command does not start because of permissions

NA

17730106

Change the log level for error messages in the xmppd.log to WARN mode

NA

17673679

In pool presence probe to a user not in roster returns the user's presence

NA

17574885

Server restarts and hangs during performance test, all threads blocked on LDAP

NA

17558390

Duplicate messages are received when federated (JabberD) users join the multi-user chat

3-7705300151

17344758

Allow using LDAP groups in a member-only room

NA

17238742

XMPPD log keeps rotating indefinitely, when wrong peer id is specified in pool

NA

17203175

Presence probe to user not in roster list is not getting presence

NA

17203133

Presence probe to contact who has blocked notification returns type=unavailable

NA

16970287

JSS dependency removal

NA

16925009

Stop bundling AIM related jars, IMPS, python gateways, remove ENS support

NA

14502397

Group messaging not working between federated servers

NA

13845159

Offline messages are not received if they are sent before server-to-server session established

NA

13463977

The search must be modified for groups, currently it searches entire user base

NA

13463895

Group messaging does not work in hosted domains

NA

12713942

SIP federation does not work in server pool setup

NA

12304931 (SUNBT7005044)

Provide help description for the parameters

NA

12287918

Users not able to enter the room while they are logged with different resources

NA

12287854 (SUNBT6924610)

Administrator cannot grant moderator privileges to a member in a conference room

NA

12287151 (SUNBT6920854)

Issues with managing conference and discussion history

NA

12265683 (SUNBT6820693)

Conference history should not be loaded while it is disabled on server

NA

12263857 (SUNBT6812313)

Messages are not deleted in LDAP

Known Problems

This section lists the known problems in this release of Instant Messaging Server.

Pidgin BOSH Client Is Not Able to Log In if DIGESTMD5 Enabled in Pool Environment

SR number: NA

Bug number: 18787873

The XMPP RFC specifies the MD5 check should use a domain name for the URI. The Pidgin BOSH client uses a host name according to Digest MD5 RFC1321. Digest MD5 does work with Strophe clients.

Server-to-Server Whitelisting Is Not Supported After an Upgrade from Instant Messaging 8 Releases to Instant Messaging 9

SR number: NA

Bug number: 17155860

During an upgrade, server-to-server coserver configuration migrates to Instant Messaging Server 9.0.1.4.0, even though the coserver-based system of defining whitelists is not supported in Instant Messaging Server 9.0.1.4.0.

Workaround:

1. After an upgrade from Instant Messaging Server 8 release to Instant Messaging Server 9.0.1.4.0, remove the server-to-server coserver properties manually, by using the following command:

imconfutil delete-coserver -c iim.conf.xml coserver1,coserver2

2. If you want to make server-to-server federation work as it did in Instant Messaging Server 8, perform the following steps:

1. Set iim_server.federation.policy=CLOSED.

2. Set whitelisted domains as exceptions, as in the following full imconfutil command, where domain1.com and domain2.com were whitelisted domains in Instant Messaging Server 8:

imconfutil -c iim.conf.xml iim_server.federation.policy=CLOSED iim_server.federation.exceptions=domain1.com,domain2.com

For more details on server-to-server configuration, see the topic on federating Instant Messaging Server 9 deployments with external servers on XMPP or non-XMPP networks in Instant Messaging Server System Administrator's Guide.

Comments in the iim.conf File Need to Be Removed Before Upgrading

SR number: NA

Bug number: 17608554

If the first line in the iim.conf file is a comment introduced by !!, it must be removed before upgrading to Instant Messaging Server 9. Otherwise, it results in an unusable iim.conf file with minimal contents.

Space Next to Equal Sign (=) in iim.conf File Is Not Handled Correctly in Upgrade to Instant Messaging Server 9

SR number: NA

Bug number: 17613019

In an Instant Messaging Server 8 iim.conf file, if there is a space before or after the equal sign in a property=value pair, upgrading to Instant Messaging Server 9 treats the equal sign as part of the value in the iim.conf.xml file. For example yim_gateway.jid = "yim.idc.oracle.com" in an Instant Messaging Server 8 iim.conf file becomes <jid>="yim.idc.oracle.com"</jid> in an Instant Messaging Server 9 iim.conf.xml file.

Parameters Are Not Migrated in Upgrade From Instant Messaging Server 8 Patch 6 to Instant Messaging Server 9

SR number: NA

Bug number: 17608577

The following parameters are not migrated in an upgrade from Instant Messaging Server 8 Patch 6 to Instant Messaging Server 9:

iim_server.port.45222.worker-in
iim_server.port.45222.worker-out

You need to add the parameters to Instant Messaging Server 9 manually, as in the following example:

imconfutil set-listener-prop -u -c /opt/sun/comms/im/config/iim.conf.xml c2s port=45222 worker-out=muxout worker-in=muxin protocols=c2s

Parameters in Instant Messaging Server 8 Patch 6 Need to Be Set Manually After Upgrading to Instant Messaging Server 9

SR number: NA

Bug number: 17613731

The following parameters are in Instant Messaging Server 8 Patch 6, but are not in Instant Messaging Server 9:

iim_mux.jvm.maxmemorysize
iim_server.deliverofflinechat
iim.policy.cachevalidity
iim_ldap.conferencecontainer

If you upgraded from Instant Messaging Server 8 Patch 6 to Instant Messaging Server 9 and are now upgrading from Instant Messaging Server 9 to Instant Messaging Server 9.0.1.4.0, you must set these parameters manually, as in the following example:

imconfutil set-prop -u -c /opt/sun/comms/im/config/iim.conf.xml iim_server.deliverofflinechat=true iim_mux.jvm.maxmemorysize=2048 iim_ldap.conferencecontainer="ou=sunConferences" iim.policy.cachevalidity=3600

SMF Status Is Not Preserved After Upgrade

SR number: NA

Bug number: 19163612

After upgrading Instant Messaging Server, Service Management Facility (SMF) becomes unregistered. To re-register SMF, run the following command:

imadmin smf-register

Communication Delay During Multi-User Chat Room Join Phases Under Load

SR number: NA

Bug number: 18956613

A communication delay can occur between users in a multi-user chat room when many users are joining the chat room.

Delay In Affiliation Change in Multi-User Chat Room Under Load

SR number: NA

Bug number: 18956566

A delay in affiliation can occur between users in a multi-user chat room when many users are joining the chat room.

Delay in 1:1 Chat and Multi-User Chat Room When Users Are Connected Through HTTPBIND

SR number: NA

Bug number: 18944756

A small communication delay can occur between users when first connecting by using HTTPBIND.

Presence of Contacts Does Not Show Correctly When User Logs Out and Logs In

SR number: NA

Bug number: 18799534

When a user logs out and logs in, the presence of contacts does not show correctly. After the user logs out, the user's contacts change status, but that status is not reflected in the user's roster when the user logs in again.

Could Not Load Roster for User Error

SR number: NA

Bug number: 18724264

The following message, if observed in the xmppd.log, is not a cause for concern:

xmppd.log.3:[06 May 2014 11:27:44,757] WARN  xmppd [default-iim_server-worker
1] Could not load roster for user: user1@ihost1.example.com : null

This message should not be printed as a warning because it misleads the user into thinking there is a problem.

Communication Break Occurs Between Peers When Run in Solaris Non-Global Zones or LDOMs

SR number: NA

Bug number: 18192309

A communication break can occur between peers on different zones or LDOMs.

Deprecated and Removed Features

The following features have been removed from this release:

- Access Manager

- Third-party instant-messaging gateways that are bundled with the Instant Messaging Server:

- AIM gateway

- MSN gateway

- Yahoo gateway

- Storing gateway data on MySQL Server

- Multiplexor with SSL

- Instant Messaging Server calendar pop-up/reminder support with Calendar Server 6.3

- The Instant Messaging and Presence Service (IMPS) Web application

- Support for file propstore for storing user data and conferences in a file system instead of LDAP

- The following commands belonging to the iwadmin tool:

- deploy

- redeploy

- undeploy

- generate

- list

- The following command options for specifying Web components to iwadmin commands:

- imps

- all

Support for the following imconfutil calendar-agent parameters has been removed as of Instant Messaging Server 9.0.1.4.0 and replaced by the new imconfutil add-jmqbroker command. For more information, see the topic on displaying availability based on calendar entries in Instant Messaging Server System Administrator's Guide.

- agent-calendar.broker.address

- agent-calendar.broker.user

- agent-calendar.broker.password

Documentation Updates

Beginning with this release of Instant Messaging Server, product documentation is published to the Oracle Documentation site at:

http://www.oracle.com/technetwork/indexes/documentation/oracle-communications-185806.html

Product documentation is no longer published to the Oracle Wiki site at:

https://wikis.oracle.com

However, documentation previously published to the Oracle Wiki site continues to be available.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Oracle Communications Instant Messaging Server Release Notes, Release 9.0.2

E53653-01

Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.