1
Suite-Level Issues

This chapter provides information about general issues affecting Oracle Collaboration Suite. It contains the following sections:

• Oracle Collaboration Suite Web Client
• Registering the Single Sign-On Photo as User Information
• Creating or Editing User Information
• File Not Found Error Occurs During Execution of the root.sh Script
• Upgrade Not Supported
• Oracle Collaboration Suite Quick Installation Guide for AIX Based Systems
• Resource Kit Documentation
• Documentation Errata

  Note: These release notes are accurate to the best of our knowledge at the time of publication. You can access the latest information on the Oracle Technology Network at http://otn.oracle.com

1.1 Oracle Collaboration Suite Web Client

The following sections describe issues affecting Oracle Collaboration Suite Web Client.

1.1.1 Error Accessing Date Portlet

The following error message appears when you access the Date portlet on the Oracle Collaboration Suite home page:

Portlets not displayed, based on the severity

The portlet does show any error on the web page, but displays the default time zone instead of the preferred time zone. The SecurityException error is logged in the opmn logs.

Workaround: Edit the jazn-data.xml file, located in the
$ORACLE_HOME/config directory, and add the following XML text after the line containing the <jazn-policy> tag, replacing ORACLE_HOME with the value of the Oracle home directory:

   <grant>
     <grantee>
       <codesource>
         <url>file:ORACLE_HOME/webclient/lib/webclient_common.jar</url>
       </codesource>
     </grantee>
     <permissions>
       <permission>
         
<class>oracle.ias.repository.schemaimpl.CheckRepositoryPermission</class>
         <name>connectAs</name>
       </permission>
     </permissions>
   </grant>

1.1.2 Portlets Not Displaying

Portlets might not display properly in Oracle Collaboration Suite release 2 (9.0.4). To correct the problem, you need to delete the cached JSPs, increase the provider timeout, and restart opmn on the middle tier.

Correct the problem as follows:

1. Log on to the middle tier where the Web client is installed.
2. Stop opmn by running the following command:

   $ORACLE_HOME/opmn/bin/opmnctl stopall
   
   

3. Change directory to:

   $ORACLE_HOME/j2ee/OC4J_Portal/application-deployments
   
   

4. Delete the following folders:
   • webclient-common
   • webclient-imeeting
   • webclient-calendar
   • marconi
5. Increase the provider timeout to 120 seconds by adding the following lines to the _default.properties files in the folders specified in the list below:

   executionKillTimeout=120
   executionWarningTimeout=120
   
   

   The _default.properties files are in the following directories:

   • $ORACLE_HOME/j2ee/OC4J_Portal/applications/webclient-common/webclient-common-web/WEB-INF/deployment/
   • $ORACLE_HOME/j2ee/OC4J_Portal/applications/webclient-calendar/webclient-calendar-web/WEB-INF/deployment/
   • $ORACLE_HOME/j2ee/OC4J_Portal/applications/webclient-imeeting/webclient-imeeting-web/WEB-INF/deployment/
   • $ORACLE_HOME/j2ee/OC4J_Portal/applications/marconi/marconi-web/WEB-INF/deployment/
6. Increase the Java heap size for OC4J_Portal instance, as follows:
   1. Open the opmn.xml file, located in the $ORACLE_HOME/opmn/conf directory.
   2. Search for the line containing gid="OC4J_Portal"
   3. Replace
      <java-option value="-server -Xincgc -Xnoclassgc -Xmx256m "/>

      with
      <java-option value="-server -Xincgc -Xnoclassgc -Xmx512m "/>

7. Enter the following command to update the configuration:

   $ORACLE_HOME/dcm/bin/dcmctl updateConfig
   
   

8. Enter the following command to start opmn:

   $ORACLE_HOME/opmn/bin/opmnctl startall
   
   

Oracle has assigned bug number 3011905 to track this problem.

1.1.3 Files Portlet Automatic Installation Failure

After installing the Oracle Files middle-tier, the Files domain is not started by default. Consequently, the Web Client configuration assistant is unable to contact the Files portlet during Web Client configuration, and the automatic registration of the Files portlet will fail.

There are two workarounds to this problem:

1. If Files and the Web Client are configured on different hosts, you can avoid the problem by configuring Files before configuring Web Client. As part of Files configuration, you must start local components for the Files domain. Refer to the Administrator's Guide for instructions on how to start local components for Files. If the Web Client is configured after Files has been completely configured (including starting local components), the Web Client configuration assistant will be able to correctly register the Files portlet automatically.
2. If Files and the Web Client are configured on the same host in the same installer session, automatic registration of the Files portlet will fail for the reasons outlined above. In this case, you must first start local components for the Files domain (see the Administrator's Guide for instructions on how to do this), then verify that the Files-related URLs are correctly set in the $ORACLE_HOME/webclient/classes/oracle/collabsuite/webclient/resources/webclient.properties file, and re-run the Web Client configuration assistant from the command line:

   $ORACLE_HOME/webclient/bin/webclient_installer.sh

1.1.4 Broken Images on UNIX

The Web Client uses Oracle UIX (User Interface XML) technology to generate Web pages. UIX dynamically generates many images (such as buttons and tabs) appearing throughout the UI. Due to limitations in Java 2 Standard Edition (J2SE) before version 1.4, UIX requires an X-Windows X server process to generate dynamic images on UNIX platforms.

To locate the X-Windows X server, the UIX runtime uses the value of the DISPLAY environment variable. If the Web Client is running on a UNIX host, and some of the images in the UI appear broken or inconsistent, the value of the DISPLAY environment variable for the Web Client process might be set incorrectly. (A common symptom of this problem is that UI pages are rendered using native browser buttons rather than Oracle buttons.) To verify the value of the DISPLAY environment variable for the Web Client process, open the
$ORACLE_HOME/opmn/conf/opmn.conf file in a text editor, and locate the entry for the instance called \OC4J_Portal\:

<oc4j maxRetry="3" instanceName="OC4J_Portal" gid="OC4J_Portal" numProcs="1">
  <environment>
    <prop name="DISPLAY" value="your-host-name:0.0"/>
  </environment>
</oc4j>

The value of the DISPLAY environment variable should point to a running X-Windows X server.

Note: During installation, the Oracle Universal Installer automatically sets the value of the DISPLAY environment variable in the opmn.xml file using the value of the DISPLAY environment variable detected during the installation session. If you are running OUI remotely (for example, from a desktop PC with X emulation software such as Hummingbird Exceed), this auto-detected value is incorrect, as it points to a remote X-Windows X server which is not guaranteed to be available. The safest approach is to create an X-Windows X server on the middle-tier host and set the DISPLAY property to point to it. Consult your UNIX documentation for information about how to start an X-Windows X server on your platform.

1.1.5 Broken Link on Collaboration Suite Welcome Page

In the Oracle Collaboration Suite welcome page (at http://host:port/), the link in the End-User Login portlet works only on the host where Oracle Portal is configured; on other middle-tier hosts, the link will be broken.

1.1.6 Editing the webclient.properties File

Because the Webmail online help file name has changed, you must edit the webclient.properties file.

Edit the webclient.properties file, located in the
$ORACLE_HOME/webclient/classes/oracle/collabsuite/webclient/resources directory, by replacing:

mail.help.url = http://%MAIL_HOST%:%MAIL_PORT%/um/help/_MAIL_LOCALE_TOKEN_/ \ 
What_is_the_WebMail_Client_.htm

with:

mail.help.url = http://%MAIL_HOST%:%MAIL_PORT%/um/help/_MAIL_LOCALE_TOKEN_/ \ 
The_All_Messages_Subtab.htm

1.2 Registering the Single Sign-On Photo as User Information

The current release does not allow a photo of a single sign-on user to be uploaded. Oracle assigned bug number 2429849 to track this.

1.3 Creating or Editing User Information

If the Create or Edit button of Resource Access Information in the Delegated Administration Service is clicked, previously filled columns are cleared. To correct the problem, enter user columns after setting user resource information. Oracle assigned bug number 2487223 to track this.

1.4 File Not Found Error Occurs During Execution of the root.sh Script

When you are running the root.sh script, you might receive an error that the $ORACLE_HOME/rdbms/filemap file could not be found. This error occurs because a file does not exist. You can ignore this error.

1.5 Upgrade Not Supported

Oracle Collaboration Suite release 9.0.3.1.0 is released on AIX 4.3.3 only. Oracle Collaboration Suite release 9.0.4.0.0 is the first release of Oracle Collaboration Suite on AIX 5L. Because AIX 4.3.3 and AIX 5L are not binary compatible, upgrade of Oracle Collaboration Suite release 9.0.3.1.0 on AIX 4.3.3 to Oracle Collaboration Suite release 9.0.4.0.0 on AIX 5L is not supported.

1.6 Oracle Collaboration Suite Quick Installation Guide for AIX Based Systems

Even though the document title does not include it, the Oracle Collaboration Suite Quick Installation Guide release 2 (9.0.4) for hp-ux PA-RISC (64-bit), Linux x86, and Solaris Operating Environment (SPARC 32-bit) is for AIX Based Systems also.

1.7 Resource Kit Documentation

The following resource kit documents are not available on the Oracle Collaboration Suite Product CD_ROM:

• Oracle Collaboration Suite Using Oracle iMeeting (Part No. B10869-01)
• Oracle Collaboration Suite Setting Preferences (Part No. B10899-01)
• Oracle Collaboration Suite Using the Search Feature (Part No. B10902-01)
• Oracle Collaboration Suite Using Oracle Voicemail (Part No. B10898-01)
• Oracle Collaboration Suite Using Oracle Webmail (Part No. B10897-01)
• Oracle Collaboration Suite Using Oracle9iAS Wireless (Part No. B10901-01)

You can get these documents on the Oracle Technology Network:

http://otn.oracle.com/

1.8 Documentation Errata

This section describes documentation issues in the Oracle Collaboration Suite Installation and Configuration Guide:

1.8.1 Chapter 9: Configuring Oracle Email

1.8.1.1 Registering the Database with Oracle Internet Directory

This section applies only if you are not using the Oracle Collaboration Suite installed database.

1.8.1.2 Configuring the Oracle Email Middle Tier

The following steps are no longer applicable:

Note: If the UMADMIN password and the domain name were specified during the information store configuration, the next screen that displays is the Configuration Tool screen. Otherwise, you must specify the UMADMIN password and the domain name.

5. Click Next. The UMADMIN Password screen displays.

6. Enter and confirm the UMADMIN password. If a password is not entered, the default value "welcome" is stored in both Oracle Internet Directory and the database as the UMADMIN password.

Note: UMADMIN is an administrator account created in the Oracle Internet Directory server during the application server installation of Oracle Email. The account owns specific Oracle Email entries in the directory. After installation, administrators should log in to the administration tool using the UMADMIN account and create an initial Oracle Email user. Thereafter, they can delegate system and domain administration responsibilities to other users.