| Oracle® Collaboration Suite Release Notes 10g Release 1 (10.1.1) for Solaris Part Number B14488-07 |
|
|
View PDF |
| Oracle® Collaboration Suite Release Notes 10g Release 1 (10.1.1) for Solaris Part Number B14488-07 |
|
|
View PDF |
This chapter summarizes release note issues associated with Oracle Real-Time Collaboration. This chapter contains the following sections:
Section 9.2, "Known Limitations and Workarounds in Oracle Real-Time Collaboration"
Section 9.3, "Known Issues in Oracle Real-Time Collaboration"
Section 9.4, "Globalization Issues in Oracle Real-Time Collaboration"
Section 9.5, "Documentation Issues in Oracle Real-Time Collaboration"
Note:
This document was updated on October 7, 2005.The following sections describes the new features of Oracle Real-Time Collaboration 10g Release 1 (10.1.1).
Section 9.1.2, "New Oracle Web Conferencing Real-Time Collaboration Console Features"
Section 9.1.3, "New Oracle Real-Time Collaboration Web Client Features"
Section 9.1.4, "New System Services for Oracle Real-Time Collaboration"
Section 9.1.5, "New Oracle Real-Time Collaboration Integration Services"
Section 9.1.6, "New Oracle Real-Time Collaboration Add-In for Microsoft Office"
Oracle Real-Time Collaboration now includes Oracle Messenger, a full-featured presence and messaging system built on the industry-standard XMPP protocol. For details about Oracle Messenger features, see the Oracle Real-Time Collaboration Administrator's Guide.
Secure chats: Oracle Real-Time Collaboration manages all communications using Secure Sockets Layer (SSL) connections. Therefore, unlike other instant messaging programs, all Oracle Messenger instant messages and chat conferences are secure.
Group presence: An administrator can create a group of contacts to perform some particular task or process; for example, a group might be created to receive chat requests from guest user customers needing support. Users can participate in a queued chat with the group, so that available members of the group can monitor and respond to the requests as appropriate. Individuals can broadcast messages to the entire group.
Chat conferences: Users can participate in text-based chat conferences with several participants, and a user can easily start a full Web conference from the chat conference.
Chat archives: Archives of individual user chat sessions can be saved on the Oracle Messenger server and on each client's server. Archives are stored by date and by person contacted, and contain the full text of all messages.
Support for Oracle Messenger features in the Oracle Real-Time Collaboration Web Client: Oracle Real-Time Collaboration Web Client pages are updated to include information about Oracle Messenger wherever appropriate.
Firewall support for guest chat users: Guest users can chat with persons using Oracle Real-Time Collaboration from outside the corporate firewall, optionally using a secure connection with HTTPS, using an Oracle Real-Time Collaboration integrated service.
Create groups from database or directory: Administrators can create a "community group" from groups in a directory or database. Such groups are created by default when users are provisioned using Oracle Internet Directory.
Create groups based on management hierarchy: Administrators can create community groups based on the company's management hierarchy, such as lists of direct reports, or all members reporting to a particular manager. Such groups are created by default when users are provisioned using Oracle Internet Directory.
Chat with colleagues: Chat with one colleague or start a chat conference to chat with multiple colleagues.
Start Web Conferences from chat: Start a Web conference directly from Oracle Messenger or from a chat conference.
Set status indicators: Display a status message showing your current availability for chat.
Exchange files while chatting: Send and receive files while chatting.
Start a voice chat: Hold a two-way voice chat with a colleague.
Broadcast chat messages: Broadcast chat messages to several users or to community groups.
Manage contact lists: Add or remove contacts, create groups of contacts, and easily move contacts from one group to another.
The most popular third-party messenger clients (on a variety of platforms) have been tested with Oracle Messenger, and will work with this version.
For third-party XMPP clients to connect to the Oracle Presence Server, they must support the IM domain (server name) being different from the host name of the applications tier. For example, if the Oracle Presence Server running on host.company.com is configured to route on company.com, the client must open a socket connection to the connect host (host.company.com), and over that connection, send the IM domain (company.com) in the stream:stream initiation. This is supported by most third-party clients in one of the following ways:
by having an independent setting for IM domain, different from connect host, or
by requiring users to sign in with their IM address (Jabber-ID, JID) user@company.com; the IM domain is stripped out from this sign-in information.
SSL connections fail for a small number of third-party clients due to incompatibilities in the SSL implementations. In such cases, users have the option of connecting to the Oracle Presence Server in non-SSL mode (if the applications tier is configured to allow non-SSL XMPP connections).
Oracle Presence Server is largely compliant with XMPP 1.0, but TLS and SASL are not supported in this release. In order to connect to the secure XMPP port, third-party clients must connect through SSL.
The following functionality through third-party clients is supported in this release:
User Sign-in
Rosters (sometimes called Buddy Lists, but not including Community Lists)
Instant messaging to any two-tier buddies
Chat Conferencing (Group Chat)
File Transfer
The Oracle Web Conferencing console has been updated to improve usability and allow more flexibility for hosts and other administrators scheduling conferences.
Usability improvements to Oracle Web Conferencing Real-Time Collaboration Console:
Cobrowse mode has been replace with expanded sharing options within Desktop Sharing
Desktop Sharing now uses a menu rather than icons to show different sharing options
Conference poll results can now be shown dynamically to attendees as results are recorded, rather than after a poll has been halted
Entering a conference no longer displays a dialog, so browser pop-up blocking no longer prevent users from joining conferences
New voice features: New voice options let hosts use their computer microphone to broadcast voice to attendees, who can listen using their computer speakers.
Acting host key lets someone other than the host schedule a conference: A person can schedule a conference and assign an acting host key to the conference. The first user to enter the conference with the acting host key is made the host.
Hosts can suppress all attendee alerts: Conference hosts can use expanded preference settings in the conference console to control which alerts attendees can see.
Send the exit poll to a different Web page: Administrators can create custom Web pages that display to conference hosts or attendees.
Chat row can be hidden: A meeting host can now suppress the Chat interface in the Console toolbar at the start of a conference. Administrators can also set this option as a default for a system or site.
Control whether a host can make a guest a presenter during a conference: An administrator can set the EnableGuestForPresenterRole property to either allow or prevent a host from making a guest a "presenter." This controls whether a guest has privileges to change or interact with the host's desktop.
Let hosts choose to publish as they exit a conference: An administrator can set the PublishOption property to add fields to the Exit Conference dialog, to let the host choose to publish this conference when exiting.
Display the record conference prompt when entering a conference: An administrator can set the ShowRecordOption property to display an additional dialog as the host enters the conference, asking whether it should be recorded.
New graphics and branding images: The Oracle Real-Time Collaboration graphics and branding images (such as the image on the Oracle Web Conferencing Real-Time Collaboration splash page) have been updated.
You use the Oracle Real-Time Collaboration Web Client to manage the system, including monitoring running processes, viewing historical and statistical reports, checking log files, and administering sites. The Web Client pages have been updated to improve usability and to support all appropriate Oracle Messenger administrative tasks.
New prelogin and postlogin home pages: New tabs are added for listing conferences in progress, scheduled conferences, and the user's upcoming conferences.
Conference enrollment and enrollable archives: Hosts can require that users enroll to participate in a conference or to view conference archives.
New choices to control types of attendees and publishing options: The former conference type field, which controlled the types of users who could be invited and whether a conference was published on a public Web site, has been replaced. There are now two new fields available:
Audience: Lets hosts choose whether non-registered users (users outside Oracle Internet Directory), only registered users, or only those registered users you specifically invited may attend.
Visibility: Lets hosts choose whether the conference is included in the public list on the Oracle Web Conferencing Home page.
Hosts can modify Web conference titles and IDs: Hosts can now edit Web conference archives to change the title or ID for a conference.
Online Help based on user roles: Online Help is divided into three sets of topics based on the user role an administrator assigns. End users will see only topics for the end-user features of the Web Client. Business monitor users will see end-user topics as well as topics for the business monitor tabs (Monitor and Reports), and business administrators will see topics for all available Web Client features.
Preferences page aligned with Preferences dialog: The page of preferences that can be modified from the Preferences link on the Web Client pages has been reorganized to align it with the preferences available within the Oracle Web Conferencing console.
Graphical user interface for setting site properties: Site properties can be modified using the Conference Properties under Sites.
Updated and new reports: See Chapter 6, "Historical and Statistical Reports for Oracle Real-Time Collaboration" of Oracle Real-Time Collaboration Administrator's Guide for details about new reports and report features.
System administrators can use the following new or updated services to manage the Oracle Real-Time Collaboration system.
Support for E1 lines: The Voice Conversion server now supports ISDN E1 lines.
Purge deleted meetings from the database: A new PL/SQL package lets administrators purge deleted meetings from the information storage database.
Integrated Administration: All components of the Oracle Real-Time Collaboration system, including Oracle Web Conferencing, Oracle Messenger, and Voice and Document servers, can be started, stopped, and administered using the rtcctl utility.
Integrated Administration with Enterprise Manager: All components of the Oracle Real-Time Collaboration system, including Oracle Web Conferencing, Oracle Messenger, and Voice and Document servers, can be started, stopped, and monitored using the Oracle Enterprise Manager Application Server Control for Collaboration Suite.
Oracle Messenger servlets: Service availability for the Oracle Messenger is integrated into the Oracle Real-Time Collaboration servlet framework. System administrators can add the servlet into their own monitoring software.
Access to log files through the Oracle Real-Time Collaboration Web Client: System log files can be viewed by clicking the System tab and choosing Logs.
The following integrated services are available for developers who want to create custom applications for Oracle Real-Time Collaboration.
Office desktop integration: The new Oracle Real-Time Collaboration Add-In for Microsoft Office allows users to perform Oracle Real-Time Collaboration tasks from within Microsoft Office applications.
Web services converted to WSDL-based SOAP APIs: Existing Web services for conference management and reporting have been converted from XML/HTTP-based APIs to WSDL-based Web services.
Web services for authentication: Web services to let applications authenticate against Oracle Real-Time Collaboration using S2S authentication for Oracle Collaboration Suite Components. Used by Oracle Calendar and Oracle Portal.
Web services for presence management: New Web services display contact presence from within Web sites, email, or integrated applications.
URL-based interface: A URL-based interface displays presence information in the form of an image or text.
SSO between applications: Single-sign on information is passed between Oracle Messenger, the Oracle Real-Time Collaboration Add-In for Microsoft Office, and the Oracle Real-Time Collaboration Web Client.
Site enhancements: Several new features support Oracle Real-Time Collaboration sites, which are used when integrating with another application.
See the Integration Services link under Quicklinks in the Oracle Real-Time Collaboration Web Client pages for more details about any integrated service.
The new Oracle Real-Time Collaboration Add-In for Microsoft Office allows users to perform Oracle Real-Time Collaboration tasks from within Microsoft Office applications such as Outlook, PowerPoint, Word, and Excel. Users can:
Start an instant web conference from any Microsoft Office application.
Schedule a web conference from Microsoft Outlook.
Join a web conference from Microsoft Outlook.
Update and delete web conferences scheduled in Microsoft Outook.
View Oracle Messenger online contacts and start a text chat from Microsoft Office (if they are signed in to Oracle Messenger).
View web conference archives.
Specify default settings for web conferences they host.
The following sections describe known limitations and workarounds for Oracle Real-Time Collaboration:
Section 9.2.3, "Oracle Real-Time Collaboration Reported Memory Usage"
Section 9.2.4, "Enabling Oracle Messenger to Work With the JAWS® Screen Reader"
Section 9.2.5, "Joining a Web Conference as the Acting Host"
Section 9.2.8, "Resolving Invalid Password Error When Upgrading to Version 10.1.2"
The IM Domain is derived from the user sign-in name. For example, if a user signs in as john.smith@mycompany.com, then the domain name is assumed to be mycompany.com. If mycompany.com is not the configured domain name on the server side, the user will get a sign in failure error. If a user signs in without a domain name in their sign-in (for example, just enters john.smith in the login field), then the IM Domain is defaulted to be identical to the host name of the server (set in the Connection Option dialog).
In this release, there is no support for specifying a default domain name for users when they do not supply a domain name.
If you use a load balancer, then all applications-tier instances (active and standby instances) must be configured to use the same domain name.
To install or upgrade to the latest version of the Oracle Real-Time Collaboration Add-In for Microsoft Office, or if the message "Error in loading module" appears when you try to select any of the Oracle Real-Time Collaboration Add-In for Microsoft Office menu options, follow these steps:
Exit from all Microsoft Office applications, and close any Web browser windows that display Microsoft Office documents.
Sign out and exit from Oracle Messenger. Make sure that the Oracle Messenger icon does not appear in your system tray (in the lower right corner of your screen).
If the Oracle Real-Time Collaboration Add-In for Microsoft Office is already installed, remove it. To remove it, from the Windows Start menu, choose Settings, then choose Control Panel, and then choose Add or Remove Programs. Otherwise, you can skip this step.
If you removed the Oracle Real-Time Collaboration Add-In for Microsoft Office, restart your computer. Otherwise, you can skip this step.
To install or upgrade to the latest version of the Oracle Real-Time Collaboration Add-In for Microsoft Office, log in to Oracle Real-Time Collaboration and click Download RTC Add-in for MS Office under Quicklinks.
In Oracle Enterprise Manager, the memory usage that is reported for Oracle Real-Time Collaboration consists only of the memory usage for the Process Manager.
To enable Oracle Messenger to work with JAWS 5.0 or later, you must copy some script files into your $JAWS_HOME/settings/enu directory. The script files will be made available on Oracle MetaLink (http://metalink.oracle.com/) shortly after the release of Oracle Real-Time Collaboration 10g Release 1 (10.1.1).
If a Web conference requires enrollment, and you have already enrolled or have been invited to attend, you are not given the opportunity to enter the acting host key, which is required to join the conference as the acting host. If the Web conference does not require enrollment, you can join the conference as the acting host as follows:
Log in to Oracle Real-Time Collaboration.
If it is not already selected, select the Home tab.
Under Join Conference on the right side of the page, enter the Conference ID.
Instead of entering the conference key, enter the acting host key provided to you by the person who originally scheduled the conference.
Click Join Conference.
After upgrading Oracle Collaboration Suite version 9.0.4.2 to version 10.1.1, the previously defined user roles for businessadmin and businessmonitor are not preserved.
To restore these user roles after upgrading, use the modifyRole command as follows:
rtcctl> modifyRole -username username -rolename rolename
The user's name is that shown in Oracle Internet Directory, such as john.smith@mycompany.com. For role name, enter either businessmonitor or businessadmin.
To get user names for users assigned to businessadmin or businessmonitor roles, use the following SQL script:
SQL> select user_name, CASE WHEN default_role_id IN(6,7) THEN 'businessmonitor' WHEN default_role_id IN(4,8) THEN 'businessadmin' END "Role Name" from rtc_users where default_role_id in (6,7,4,8);
By default, Oracle Messenger users can transfer files during text chat sessions. Since the Oracle Messenger File Exchange feature transfers files non-securely, you may want to disable this feature. You can use the FileTransferEnabled property to disable the File Exchange feature. Setting this property will only affect subsequent downloads of the Oracle Messenger client; it has no affect for already installed Oracle Messenger clients.
Description: Enables or disables the Oracle Messenger File Exchange feature. By default, this feature lets Oracle Messenger users transfer files, but files are transferred non-securely. Setting this property to false will disable the File Exchange feature. You must set this property before users download the Oracle Messenger client.
Default Value: true
Valid Value: false, true
Scope: system
Example: To disable the Oracle Messenger File Exchange feature, enter:
rtcctl> setProperty -system true -pname FileTransferEnabled -pvalue false
If you are upgrading from Oracle Real-Time Collaboration version 10.1.1 to version 10.1.2, you may encounter an invalid password error during the infostore upgrade, if the schema passwords for the RTC, RTC_APP, RTC_REP, and RTC_IM schema accounts are different.
To resolve the invalid password error:
Run the change_schema_passwd.pl script, which is located in the $ORACLE_HOME/imeeting/install/db directory. This script resets all schema account passwords to be the same as the password that was used when Oracle Real-Time Collaboration was installed or upgraded to version 10.1.1.
Rerun the infostore upgrade for Oracle Real-Time Collaboration version 10.1.1 to version 10.1.2.
The following table lists known issues in Oracle Real-Time Collaboration.
Table 9-1 Known Issues in Oracle Real-Time Collaboration
| Description | Action | Bug Number |
|---|---|---|
|
If you update a Web conference that was originally scheduled with the Audience set to "Registered Users" or "Registered Users by Invitation Only", the Audience gets reset to "All Users". |
When you update a Web conference, you must set the Audience to "Registered Users" or "Registered Users by Invitation Only" on the Update Conference: Details page. |
4475659 |
|
Components cannot be restarted using the Restart option in Oracle Enterprise Manager Application Server Control for Oracle Collaboration Suite. |
To restart components using Oracle Enterprise Manager Application Server Control for Oracle Collaboration Suite, open the Application Server Control page for Oracle Collaboration Suite tools. Click RTC. Click the Stop button, and then click the Start button. |
4485710 |
|
After upgrading from a previous version of Oracle Collaboration Suite, or if you configure Oracle Real-Time Collaboration using the Configuration Assistant, the checkbox for the Real-Time Collaboration component listed under System Components in Oracle Enterprise Manager Application Server Control for Oracle Collaboration Suite is disabled and is not selectable. |
To enable the checkbox for the Real-Time Collaboration component, restart Oracle Enterprise Manager Application Server Control for Oracle Collaboration Suite. |
4473350 |
|
When using the desktop sharing mode in a conference, the Click to share button and red outline are not rendered on certain application windows. |
Use the new feature providing a list of applications to select which ones should be shared or not shared |
4314687 |
|
After upgrading, the previously defined user roles for businessadmin and businessmonitor are not preserved. |
Use the workaround described in Section 9.2.6, "Restoring User Roles After Upgrading" |
4477138 |
|
When direct XMPP/XMPPS connections are disabled, end-to-end Oracle Messenger tests will fail. Disabling direct XMPP connections is controlled by the property IMXMPPDirectConnEnabled. |
None. |
4529188 |
|
Direct manual connection using third-party XMPP; provided for interoperability testing. |
None. |
4430183 |
|
By default, the Oracle Messenger File Exchange feature lets users transfer files non-securely. |
Disable the File Exchange feature using the FileTransferEnabled property, as described in Section 9.2.7, "Disabling Oracle Messenger File Exchange". |
4147260, 4147059 |
|
Infostore upgrade from 10.1.1 to 10.1.2 may fail with invalid password error if 10.1.1 schema account passwords are not all the same. |
Run the script as described in Section 9.2.8, "Resolving Invalid Password Error When Upgrading to Version 10.1.2", and then rerun the infostore upgrade from 10.1.1 to 10.1.2. |
4638217 |
The following table lists Oracle Real-Time Collaboration globalization issues.
Table 9-2 Globalization Issues in Oracle Real-Time Collaboration
| Description | Action | Bug Number |
|---|---|---|
|
For the Oracle Real-Time Collaboration Add-In for Microsoft Office, the following text strings are not translated and appear in English: "A newer version of the Add-In is available. Please update your Add-in." "The server is incompatible with this version of the Add-in." |
None. |
4472602 |
|
Translated help text for the four usage reports (Key Usage Metrics, Web Conferencing, Presence and Chat, and Integration Services) incorrectly defines the Week period as "26 days". The English help text correctly defines the Week period as "26 weeks". |
None. |
4384125 |
|
For the "Create Oracle Real-Time Collaboration Host" and "Update Oracle Real-Time Collaboration Host" application Web pages, the translated help text for these pages does not match the user interface. The translated help pages refer to the "Add/Update" page, but this page does not exist. The English help pages contain the correct information. |
None. |
4368093 |
|
When the Usage, Feedback, and Security reports are displayed for Asian, Arabic, and other multi-byte language locales, the month names and legends in the report charts are displayed as empty squares. |
None. |
4394870 |
|
When the Join Time and Network Latency graphs found on the QoS Reports tab are displayed for Asian, Arabic, and other multi-byte language locales, some text labels may be displayed as empty squares. |
None. |
4485121 |
|
For Asian, Arabic, and other multi-byte language locales, and some single-byte language locales, clicking Download Source or Preview on the Embeddable Presence page displays extraneous "?" characters. |
None. |
4473997 |
|
On the Embeddable Presence page, when you copy the presence URL into a new browser window, the status text appears in English. |
None. |
4487997 |
|
The Oracle Messenger guest user chat client is only supported in English. |
None. |
4482045 |
|
Multi-sheet Microsoft Excel documents that contain multi-byte characters display incorrectly in document presentation mode during a Web conference or when the document name is clicked in the Materials tab. |
During a Web conference, the workaround is that the host should open the Microsoft Excel document and share his desktop instead of using document presentation mode. |
4478990 |
|
Oracle Messenger is unable to start a chat conference for the Arabic language locale. |
None. |
4495508 |
|
For Chinese, Taiwanese, Japanese, French, Italian, and Spanish language locales, after clicking the New User tab on the Oracle Web Conferencing prelogin page, and then clicking Troubleshoot, users cannot download the Direct X compatibility patch. |
Download the appropriate Direct X patch from the Microsoft Web site. |
4467711 |
Information in the following sections is provided as a supplement to the Oracle Real-Time Collaboration Administrator's Guide:
Description: Controls the number of rows that appear in any tables shown on Oracle Real-Time Collaboration Web pages.
Default Value: 1000
Valid Value: -1 to display all meetings, or any positive integer.
Scope: user
Example: To set the maximum number of rows shown in tables on all of your Oracle Real-Time Collaboration pages to 30, enter:
rtcctl> setProperty -pname MaxTableRows -pvalue 30
To determine the role that was assigned to a user using the modifyRole command, you can use the getProperty command as follows:
rtcctl> getProperty -pname SiteRoleId -userid userid|-username username -siteId site-id
The value returned is either 2 (enduser role), 4 (businessadmin role), or 6 (businessmonitor role).
