| Oracle® Collaboration Suite Release Notes Release 2 (9.0.4.1.1) for Windows Part Number B12240-02 |
|
|
View PDF |
| Oracle® Collaboration Suite Release Notes Release 2 (9.0.4.1.1) for Windows Part Number B12240-02 |
|
|
View PDF |
This chapter summarizes release note issues associated with Oracle Web Conferencing. The following sections are included in the chapter:
The following features have been introduced in release 2.0.4.2:
Update and delete meeting functionality are now accessible from the post-login Home tab
A link to integration services is now visible in the Quicklinks bin
Improved performance in rendering the Usage summary reports due to the inclusion of new materialized views
New User flow now has more checks, such as a display driver check
Oracle Web Conferencing installation could fail due to incorrect inputs that cannot be validated and, hence, cannot be prevented during installation. Installation could fail during the configuration phase due to a variety of reasons. This section addresses how to recover from some of these failures and configure Oracle Web Conferencing by hand.
Installation of Oracle Web Conferencing assumes that the Web Conferencing host machine is freely accessible on all ports for all traffic from users' computers trying to access Web Conferencing. For most enterprises, this translates to the Web Conferencing server machines on the intranet without any internal firewalls. If your installation does not fall into this category, you might not be able to access Web Conferencing immediately at the end of installation without further post-installation configuration.
|
See Also: Oracle Web Conferencing Administrator's Guide for information on how to configure Oracle Web Conferencing for various other cases |
Follow the post-installation steps for the most common configurations required for enabling e-mail invites to conferences and other basic functionality listed later in the Oracle Collaboration Suite Installation and Configuration Guide.
Reinstallation and deinstallation of Oracle Web Conferencing is not supported in this release. In most cases you will need to start the installation all over after restoring the installation environment to the exact state before the installation was started, so that the new attempt is a clean new installation.
This section does not discuss how to clean up the Oracle Collaboration Suite installation. However, you might need to remove the Real-Time Collaboration repository in some cases. To do so, you will need to delete all Real-Time Collaboration objects from the database, including the RTC tablespaces.
|
See Also: Oracle Database Administrator's Guide for information on carrying out some of these commands for your particular database |
Log in to the database as SYSTEM user or user with similar privileges.
Alter the system to disallow access to the database by RTC and RTC_APP users, so that those users may start no new sessions.
Discontinue all sessions by RTC and RTC_APP users.
Drop RTC_APP followed by RTC:
Drop user RTC and RTC_APP including all the database objects owned by them
Drop tablespaces RTC_DATA, RTC_INDEX, RTC_BIG_DATA, and RTC_LARGE_DATA and the data files used for those tablespaces. Depending on how the RTC repository was created, you will have either RTC_BIG_DATA or RTC_LARGE_DATA present in the database. If both are present, drop both.
Oracle Web Conferencing needs to use the Oracle Real-Time Collaboration (RTC) repository residing in an Oracle9i (9.2 or later) database. This database may be a customer database, or it can be the Oracle Collaboration Suite 9.0.4.1.0 information store database in which the RTC repository is already seeded at the time the information store is installed. Each of the following cases requires slightly different steps to make the RTC repository available in working condition.
Installation fails against a customer database—If the installation fails before you create the repository, you might need to edit the install_schema.cmd script by hand to substitute correct values of Oracle home and the SID for the database to which you plan to connect for the RTC repository.
Issue the following command:
%ORACLE_HOME%\imeeting\install\db\install_schema.cmd connect_string_for_ database password_for_user_SYSTEM rtc rtc_password_of_your_choice rtc_app rtc_app_password_of_your_choice RTC_DATA RTC_LARGE_DATA RTC_INDEX directory on_the_database_host_where_the_datafiles_for_tablespaces_will_be_created (typically the oradata\instance_name subdirectory in the Oracle home on the database host)
Example:
\private\i902\midm72\imeeting\install\db\install_schema.cmd (description=(address=(host=crmdev07.us.oracle.com)(protocol=tcp)(port=1521)) (connect_data=(sid=ia902dbd))) manager rtc rtc rtc_app rtc_app RTC_DATA RTC_LARGE_DATA RTC_INDEX \u04\DBs\iA902DBD\oradata
The installation fails against the Oracle Collaboration Suite information store: If the installation is interrupted before reaching the RTC repository dialogs, you might need to edit the scripts used here to substitute appropriate values for Oracle home, etc.
Issue the following command:
%ORACLE_HOME%\imeeting\install\db\unlock_schema.cmd connect_string_for_ the_information_store_database SYSTEM_password rtc rtc_app
Example:
\private\i902\midm71\imeeting\install\db\unlock_schema.cmd (description=(address=(host=isunaaa17.us.oracle.com)(protocol=tcp) (port=1521))(connect_data=(sid=infom7))) manager rtc rtc_app
Next, issue the following command:
%ORACLE_HOME%\imeeting\install\db\change_passwd_schema.cmd connect_string_ for_information_store_database SYSTEM_password rtc rtc_password_of_your_ choice rtc_app rtc_app_password_of_your_choice
Example:
\private\i902\midm71\imeeting\install\db\change_schema_passwd.cmd (description=(address=(host=isunaaa17.us.oracle.com)(protocol=tcp) (port=1521))(connect_data=(sid=infom7))) manager rtc rtc rtc_app rtc_ app
The RTC repository must be available for use for the following step to succeed. If the installation is interrupted before reaching the configuration phase, you might need to edit the imtctl script used here to substitute appropriate values for your Oracle home, etc.
Edit the %ORACLE_HOME%\imeeting\conf\imtint.conf file and make sure it has a valid value for oracle.imt.instancename. It should be ORACLE_HOME name.fully_qualified_host_name_for_the_middle_tier. For example, orahome1.bigsun1.mycompany.com.
Invoke %ORACLE_HOME%\imeeting\bin\imtctl updateDatabaseInfo -dbsid SID_for_the_RTC_repository_database -dbhost host_name_for_RTC_repository_database -dbport port_for_the_RTC_repository_database -dbschema rtc_app -dbpassword rtc_app_password.
For the Real-Time Collaboration Core Components instance, issue the following command:
%ORACLE_HOME%\imeeting\bin\imtctl addInstance -installtype midtier -instancename oracle_home_name.host_name.domain_name (for example, midm71.isunaaa18.us.oracle.com) -hostname host_name.domain_name (for example, isunaaa18.us.oracle.com) -imthome %ORACLE_HOME%\imeeting -mxport any_available_port_between_1025-49151 (for example, 2400) -webhost Host_name_used_by_OHS (for example,isunaaa18.us.oracle.com) -webport Oracle_HTTP_Server_or_Web_Cache_listen_port (for example, 7777. Use the Web Cache port if Web Cache is enabled.) -websslport Oracle_HTTP_Swerver_or_ Web_Cache_SSL_listen_port (for example, 4443 use the Web Cache port if Web Cache is enabled) -ldaphost OCS_infrastructure_OID_hostname (for example, isunaaa17.us.oracle.com) -ldapport OCS_infrastructure_OID_port (for example 4032) -oc4jname OC4J_imeeting -imtpm_httpport any_available_port_between_ 1025-49151 (for example, 2402) -appname imeeting -em_integrate (true or false based on whether you want integration with EM Web site or not for the status display of Oracle Web Conferencing\iMeeting)
For the Document Conversion Server and Voice Conversion Server, issue the following commands:
%ORACLE_HOME%\imeeting\bin\imtctl.cmd addInstance -installtype (voice if voice server\conveter if document conversion server) -instancename oracle_ home_name.host_name.domain_name (for example, ocsm7dv1.st- avenet-02.us.oracle.com) -hostname host_name.domain_name (for example, st-avenet-02.us.oracle.com) -imthome %ORACLE_HOME%\imeeting -orclhome %ORACLE_HOME% -voice_httpport any_ available_port_between_1025-49151 (for example, 2402) -imtpm_httpport any_ available_port_between_1025-49151 (for example, 2403) -appname imeeting
This step is to be done only on the Core Components instance host. If the installation is interrupted or fails before proper creation of the files or scripts involved, you might need to edit the files and scripts involved to appropriately substitute the values for the Oracle home, etc. Additional files used by this script are located in the same directory as the script.
Set the environment variables as follows:
ORACLE_HOME=the_Oracle_Home LD_LIBRARY_PATH=%ORACLE_HOME%\lib
Then execute:
%ORACLE_HOME%\jdk\bin\java -Xmx512m -Djava.io.tmpdir=\tmp -classpath %ORACLE_HOME% \lib\xmlparserv2.jar:%ORACLE_HOME%\dcm\lib\dcm.jar:%ORACLE_HOME%\jdbc\lib\class es12.jar:%ORACLE_HOME%\lib\dms.jar:%ORACLE_HOME%\j2ee\home\oc4j.jar:%ORACLE_HOME% \j2ee\home\jaznplugin.jar:%ORACLE_HOME%\lib\xschema.jar:%ORACLE_HOME%\opmn\lib \ons.jar:%ORACLE_HOME%\jlib\emConfigInstall.jar:%ORACLE_HOME%\dcm\lib\oc4j_deploy_ tools.jar-Doracle.ias.sysmgmt.logging.logdir=%ORACLE_HOME%\j2ee\home\log oracle.j2ee.tools.deploy.Oc4jDeploy -oraclehome %ORACLE_HOME% -verbose -inifile %ORACLE_HOME%\imeeting\install\oui\imt.ini -timeout 120 -postdeploysleep 15
|
Note: Before issuing the above command, verify that the%ORACLE_HOME%\j2ee\deploy.ini file exists. The %ORACLE_HOME%\j2ee\deploy.ini file might have been backed up by the installer as %ORACLE_HOME%\j2ee\deploy.ini.some_number.bak. Make a copy of it and save it as %ORACLE_HOME%\j2ee\deploy.ini. |
All of the following modifications are to the mod_osso.conf file in the Web Conferencing Oracle home.
|
Note: Oracle Corporation recommends settingOssoIPCheck to off in mod_oss.conf. |
If your deployment uses HTTPS, you must edit the mod_osso.conf file in order to enable downloading of the Web Conferencing Console, logs, materials, and recordings.
<Location \imtapp\res>
OssoSendCacheHeaders off
<\Location>
<Location \imtapp\logs>
OssoSendCacheHeaders off
require valid-user
AuthType Basic
<\Location>
<Location \imtapp\app>
OssoSendCacheHeaders off
<\Location>
<Location \imtapp\console>
OssoSendCacheHeaders off
<\Location>
Users with Internet Explorer 5.5 might find that images are missing from documents they are viewing from the Web Conferencing Application or during Document Presentation mode in a conference. To prevent this, turn off image compression for PNG files in OracleAS Web Cache.
To turn off image compression:
Access the OracleAS Web Cache administrator pages for the installation of Oracle9iAS. By default, it is at http:\\apache_web_host:4000 \webcacheadmin.
Log in as the administrator. The default value username and password is administrator.
In the post-login page, you will see the Administration section on the left. Scroll down and locate the General Configuration section. In that section, under Cacheability Rules, click Compression.
Select the radio button for the rule that contains a reference to the compression of PNG images. It is the second set of rules in the default installation.
Click Change Selector Association.
In the window that pops us, click the rule that refers to the compression of the PNG images.
Click Remove Association. The pop-up window closes.
Click Apply Changes on the main page.
Click Restart. This causes the changes to take effect.
Chapter 5 of the Oracle Web Conferencing Administrator's Guide explains the imtreport script that is used to set up Oracle Web Conferencing reports. To configure report options, you edit variables at the top of the report script.
Edit the imtreport script as follows to configure usage reports to be e-mailed to recipients.
Change the export IMT_USE_BI_CLASSES line in imtreport to export IMT_USE_REPORT_CLASSES. Failure to edit this line results in a NoClassDefFound error
Set the SITE_ID parameter to a specific site ID or 100 for all sites. Setting it to an empty string results in the following error: TODAYSDATE is an invalid identifier
Remove any spaces after the commas in the comma-separated list of recipients. Failure to do so results in the e-mailing of the report to the first person in the list of recipients only.
Set the DISPLAY variable at the top of imtjvm. Failure to do so results in the following error: Problem with constructor javax.swing.plaf.FontUIResource...
The following exception occurs while the RTC configuration assistant "Create Oracle Real-Time Collaboration Repository" is running during installation, if you choose to install the Web Conferencing schema on a custom database:
Connected.
Connected.
Importing seeded demo conferences
LRM-00116: syntax error at 'address' following '('IMP-00022: failed to process
parameters, type 'IMP HELP=Y' for help
IMP-00000: Import terminated unsuccessfully
You can safely ignore this exception. After installation, follow the steps below to upload the demo.
Make sure the Oracle database import utility, %ORACLE_HOME%\bin\imp, is available in the Oracle home for the Oracle database on the database host you are using for RTC repository.
Get the %ORACLE_HOME%\imeeting\install\db\imtseed.dmp file from any RTC Core Components Oracle home to the database host.
Issue the following command on the database host from the shell:
%ORACLE_HOME%={database_oracle_home};export ORACLE_HOME
%PATH=%PATH:%ORACLE_HOME\bin;export PATH imp
RTC_ACCT_NAME\password_for_schema_rtc@database_connect_string
file=imtseed.dmp ignore=y commit=y buffer=40960000 grants=n indexes=n show=n
touser=%RTC_ACCT_NAME fromuser=rtc
Oracle Web Conferencing uses Oracle Internet Directory for user management. For performance reasons, Oracle Web Conferencing maintains a local copy of the following attributes for the user:
User Name—The one the user types when logging in. This attribute is set by the Oracle Internet Directory administrator.
User GUID—Global Unique Identifier. This is an internal field not visible to users
First Name
Middle Name
Last Name
E-mail Address
Currently, there is no synchronization between the user data in Oracle Internet Directory and the RTC Repository. This section lists the scenarios in which you might encounter problems.
This scenario presents no issues. The first time the user logs in to Oracle Web Conferencing, the user information is queried from Oracle Internet Directory and the local RTC Repository is populated.
There are certain situations in which one change affects multiple attributes. For example, when Oracle Internet Directory is configured such that user name is mapped to e-mail address, the change of an employee's last name could result in changes to the e-mail address, last name, and user name. In such cases, the fixes from all applicable scenarios should be applied.
The user gets an error when logging in to Oracle Web Conferencing. Oracle Web Conferencing contains the user's GUID with the old user name, which results in a conflict.
Old User Name: JANE.DOE@ORACLE.COM
New User Name: 'ANE.YOUNG@ORACLE.COM
Fix: Run the following SQL statements while connected to the RTC Repository as rtc_app account:
SQL> update rtc_users set user_name = 'JANE.YOUNG@ORACLE.COM'
where user_name = 'JANE.DOE@ORACLE.COM';
SQL> commit;
There are no major issues in this case. The user can still use Oracle Web Conferencing. The only issue is that the user's first name will show up incorrectly in Oracle Web Conferencing.
Old First Name: Jane
New First Name: Jane2
Fix: Run the following SQL statements while connected to RTC Repository as rtc_app account:
SQL> update rtc_persons set first_name = 'Jane2'
where person_id in (select person_id from rtc_users where
user_name = 'JANE.DOE@ORACLE.COM');
SQL> commit;
There are no major issues in this case. The user can still use Oracle Web Conferencing, but the user's last name will show up incorrectly in Oracle Web Conferencing.
Old Last Name: Doe
New First Name: Young
Fix: Run the following SQL statements while connected to RTC Repository as rtc_app account:
SQL> update rtc_persons set last_name = 'Young'
where person_id in (select person_id from rtc_users where
user_name = 'JANE.DOE@ORACLE.COM');
SQL> commit;
There are no major issues in this case. The user can still use Oracle Web Conferencing, but the user's e-mail address will show up incorrectly in Oracle Web Conferencing, and the user cannot receive conference invites through e-mail.
Old E-mail: JANE.DOE@ORACLE.COM
New E-mail: JANE.YOUNG@ORACLE.COM
Fix: Run the following SQL statements while connected to RTC Repository as rtc_app account:
SQL> update rtc_persons
set email_address = 'JANE.YOUNG@ORACLE.COM'
where person_id in (select person_id from rtc_users where
user_name = 'JANE.DOE@ORACLE.COM');
SQL> commit;
There are no potential issues in this case. The user could never log in to Oracle Web Conferencing, since the user will not be able to authenticate through Oracle Application Server Single Sign-On.
If the user never logged in to Oracle Web Conferencing the first time, then there are no potential issues.
If the user had logged in to Oracle Web Conferencing the first time, and the user's account was deleted and recreated, the user will get an error while trying to log in to Oracle Web Conferencing.
The reason for this is that the user got a new GUID when the user account was recreated. Oracle Web Conferencing has information about this account with the old GUID and hence will run into a conflict when the user tries to log in to Oracle Web Conferencing again with a different GUID.
Fix: Run the following SQL statements while connected to the RTC Repository as rtc_app account:
SQL> delete from rtc_persons
where person_id in (select person_id from rtc_users where
user_name = 'JANE.DOE@ORACLE.COM');
SQL> delete from rtc_users
Where user_name = 'JANE.DOE@ORACLE.COM';
SQL> commit;
The following are known issues with this release of Oracle Web Conferencing.
Table 8-1 Oracle Web Conferencing Known Bugs
| Bug No. | Description | Workaround |
|---|---|---|
| 3019653 | The date does not display properly when Arabic is selected. | None |
| 3033626 | When Oracle Collaboration Suite Release 2 is installed, some of the Web Conferencing (Real-Time Collaboration) configuration assistants are run during installation, even if the user chooses not to configure Oracle Web Conferencing. The configuration assistants report failure to complete. | Ignore the reported failures |
| 3124505 | iMeeting appears in the Oracle Enterprise Manager Middle-tier site, but the page does not display. This is a known issue. | Stopping and starting the Oracle Enterprise Manager Web site resolves this issue. |
| 3133297 | After upgrading from Oracle Collaboration Suite release 1 to Oracle Collaboration Suite release 2, user cannot start a Web conference from the portlet in the Oracle Collaboration Suite home page. |
|
| 3117475 | Site=0 has no authentication key. | No workaround is available at this time. |
| 3095910 | Some English strings appear in the Web Conferences portlet of Oracle Collaboration Suite when Korean is selected. | No workaround is available at this time. |
| 3166787 | The Oracle Web Conferencing Quick Tutorial and Oracle Collaboration Suite Using Oracle Web Conferencing state that the personal materials repository has a 40 MB limit. | See Section 8.5.1 for more information. |
| 3263919 | An error occurs when the user launches the demo if the Oracle Web Conferencing schema has been installed on a custom database. | See Section 8.2.6 for more information. |
The following errors were found in the Oracle Web Conferencing documentation set.
These documents state that the personal materials repository has a 40 MB limit. In fact, there is no limit at this time.
The script is listed as:
imtctl> $ORACLE_HOME\imeeting\bin> imtctl < ../scripts/sample.imt
This should be:
$ORACLE_HOME\imeeting\bin> imtctl < scripts/sample.imt
The command in step 2 is listed as:
$ORACLE_HOME\dcm\bin\dcmctl -v updateConfig -ct ohs
The command should be:
$ORACLE_HOME\dcm\bin\dcmctl updateConfig -ct ohs -v
In step 4, the imtctl script is listed as:
$ORACLE_HOME\imeeting\bin\scripts\Redirect.imt
This should be:
$ORACLE_HOME\imeeting\bin\scripts\redirect.imt
This section contains instructions on configuring SSL. In addition to those steps, you need to obfuscate the wallet password and set the MxWalletPassword property.
Steps:
Obfuscate the Microsoft Windows user's password with:
$ORACLE_HOME\Apache\Apache\bin\apobfuscate
Set a property in the Oracle Web Conferencing system:
$ORACLE_HOME\imeeting\bin\imtctl setProperty -pname MxWalletPassword -pvalue obfuscated_password
