| Oracle® Collaboration Suite Release Notes 10g Release 1 (10.1.1) for Linux Part Number B19091-07 |
|
|
View PDF |
| Oracle® Collaboration Suite Release Notes 10g Release 1 (10.1.1) for Linux Part Number B19091-07 |
|
|
View PDF |
This chapter describes suite-level release note information affecting all components of Oracle Collaboration Suite. This chapter contains the following sections:
Section 3.2, "Known Limitations and Workarounds in Oracle Collaboration Suite"
Section 3.4, "Globalization Issues in Oracle Collaboration Suite"
Section 3.5, "Documentation Issues in Oracle Collaboration Suite"
Note:
This document was updated on October 7, 2005.New look and feel for improved usability
Oracle Discussions
Oracle Workspaces
Oracle Web Access Client for improved browser-based access and usability
Built on the Oracle Application Server 10g Release 2 Phase 2 platform
Centralized user provisioning console - create, provision, edit, and delete users one at a time, or manage them using bulk processing
Expanded documentation library featuring suite-level guides for concepts, deployment, installation, upgrade, administration, security, and licensing
Oracle Voicemail & Fax is now fully integrated with Oracle Enterprise Manager Grid Control, for easier management and administration
Oracle Metadata Repository is now integrated into the Collaboration Suite Database as a default configuration, so you can run your deployment on a single database
New customizable End-User Documentation Portal available to assist users in getting started with Oracle Collaboration Suite
Oracle Enterprise Manager Application Server Control for Collaboration Suite - a customized management tool providing:
Topology view of the Oracle Collaboration Suite environment
Support for viewing and changing Infrastructure Services for Identity Management
Views of all performance metrics and metric details
Complete integration of OracleAS Web Cache administration
Support for querying from a database log repository
Ability to change the port values of Enterprise Manager components
Oracle Database 10g and Enterprise Manager Database Control for the Oracle Collaboration Suite Database
Improved cross-application integration
New Oracle Collaboration Suite control script sample ocsctl_sample for single-command command-line startup and shutdown of Oracle Collaboration Suite
The following sections describes suite-level limitations and workarounds for Oracle Collaboration Suite:
Section 3.2.2, "Component Administration URL Does Not Appear in Oracle Enterprise Manager"
Section 3.2.4, "Kernel Parameter Conflict with Chipsets and Java 2 SDK 1.4.2_06"
Section 3.2.7, "Configuring Oracle Voicemail & Fax in an Existing Deployment"
Section 3.2.10, "Adding Applications to your Oracle Collaboration Suite Deployment"
The default password policy set by Oracle Internet Directory is to expire user passwords after 60 days. Please see "Changing the Default Password Policies" in Chapter 4 of Oracle Collaboration Suite Administrator's Guide to determine the appropriate expiry time, warning time and grace login count for your organization.
After you configure an Oracle Collaboration Suite component using the Oracle Enterprise Manager Oracle Application Server Control for Collaboration Suite, click the Refresh Data icon in the upper right corner of the Application Server Control for Collaboration Suite Home page. This causes the Administration URL for the configured component to appear in the Administration column of the System Components table.
Do not use the Deploy Ear File or Deploy War File options in Oracle Enterprise Manager Application Server Control for Collaboration Suite to deploy a new J2EE application on your Oracle Collaboration Suite OC4J instances.
Deploying a new application could cause problems with the Oracle Collaboration Suite JVM or Oracle Collaboration Suite environment, including introducing incompatibility problems with the Oracle Collaboration Suite user applications.
Recently manufactured Intel Xeon and AMD64 chipsets, when combined with a very recent kernel build, can exhibit unexpected issues due to a recent kernel parameter (kernel.use-nx=1). Customers with this configuration will encounter a bug in version 1.4.2_06 of Java 2 SDK (shipped with Oracle Collaboration Suite) that will cause Content Services and Calendar Server configuration failures, excessive consumption of processing power by Collaboration Suite Control, and possible other negative effects. Customers should disable this parameter by adding noexec=off to the boot parameters of the kernel until version 1.4.2_08 of Java 2 SDK is certified for use with Oracle Collaboration Suite 10g Release 1 (10.1.1). At that point, the Java 2 SDK of installed Oracle Collaboration Suite instances can be replaced with version 1.4.2_08, and the No Execute (NX) flag re-enabled in the kernel.
Oracle Collaborative Portlets uses HTTP internally to communicate with Oracle Collaboration Suite component application Web services (such as Oracle Mail and Oracle Calendar) to obtain application data. The use of SSL is not supported at this level.
In addition, if you configure SSL for Oracle Collaboration Suite and turn off the non-SSL (HTTP) port, then Oracle Collaborative Portlets will stop functioning. In other words, Oracle Collaborative Portlets requires the Web Cache non-SSL (HTTP) port to remain open.
Note:
This is applicable for internal HTTP communication only. This does not affect external HTTP-based communication between browsers and Oracle Collaboration Suite.After configuring Oracle Mail with Oracle Enterprise Manager, Oracle WebMail is no longer accessible. To correct this, do the following:
Append:
$ORACLE_HOME/um/client/config/toolkit.properties
onto:
$ORACLE_HOME/j2ee/OC4J_OCSClient/config/oc4j.properties
For example:
cat $ORACLE_HOME/um/client/config/toolkit.properties >> $ORACLE_HOME/j2ee/OC4J_OCSClient/config/oc4j.properties
Restart the OC4J_OCSClient container:
$ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=OC4J_OCSClient
You must perform a workaround before configuring Oracle Voicemail & Fax in an existing Oracle Collaboration Suite deployment.
Perform this workaround on the first Applications tier, and also on any additional Applications tiers you are configuring with the New PBX option:
Edit %ORACLE_HOME%\um\scripts\ovf_config1.bat, and insert the following line:
CALL %1\um\scripts\editVerifierProfile.bat %1 %3 %4 %5 1 >> %2
below the line:
CALL %1\um\scripts\loadOVFProvisioning.bat %1 %3 %4 %5 1 >> %2
Edit %ORACLE_HOME%\um\scripts\ovf_config2.bat, and insert the following line:
CALL %1\um\scripts\create_um_ldap.bat %1 newpbx_new.ldif >> %2
below the line:
CALL %1\um\scripts\create_um_ldap.bat %1 vmail_new.ldif >> %2
Edit create_scvsto.bat to replace %hostname% with the actual host name of the Applications tier.
If you configure Oracle Application Server Portal using Oracle Enterprise Manager, you must perform some additional steps to complete the configuration. These are described in "Configuring OracleAS Portal After Installation" in Oracle Application Server Administrator's Guide. (4526828)
If you enable SSL (HTTPS) within your Oracle Collaboration Suite environment, and then later change the SSL port number as described in "Changing the HTTP Server Port on Identity Management" in Chapter 14 of Oracle Collaboration Suite Administrator's Guide, you must perform an additional step to update OracleAS Portal with the new port number.
In Task 12, "Update the Applications Tier Instances to Use the New Port Number", the wizard you invoke in Step 1c is failing to perform an important task. After running the wizard, but before performing step 2, run the following command:
ORACLE_HOME/portal/conf/ptlconfig -dad <dad> -pw <Portal schema password or
OID Admin Password> -sso [-host <portal_site_name> -port <portal_site_port>
[-ssl]
In the above example, the <dad> should be portal. Use the new Applications tier SSL port number when you specify -port, and be sure to use the -ssl flag if you have enabled SSL. Run this command on every Applications tier which is hosting an instance of OracleAS Portal.
Whenever you configure a new component on an existing Applications tier, as described in "Adding Applications to your Oracle Collaboration Suite Deployment", in Chapter 5 of Oracle Collaboration Suite Administrator's Guide, you must perform an additional step (Bug 4439419).
In Step 5 of the procedure, the text indicates that "If you are configuring Oracle Web Access Client or Oracle Collaboration Suite Search, you must restart the OC4J_OCSClient and HTTP_Server processes."
Actually, you must restart the OC4J_OCSClient process after configuring any Oracle Collaboration Suite component on any Applications tier. This is necessary to update the Oracle Collaboration Suite Welcome page to show a link for the newly-configured component.
The following table lists suite-level known issues in Oracle Collaboration Suite.
Table 3-1 Suite-Level Known Issues in Oracle Collaboration Suite
| Description | Action | Bug Number |
|---|---|---|
|
Using Mozilla-based browsers (including Netscape 7, Mozilla, and Firefox), in the Oracle Calendar portlet, customizing the portlet to select 'Week View' causes the portlet to appear stretched too wide. |
None |
3394423 |
|
Signing out of Oracle Collaboration Suite sometimes fails when using Mozilla or Firefox browsers. |
Close the browser window to protect private information. |
4454918 |
|
The Oracle Content Services portlet will not be available in the initial release of Oracle Collaboration Suite 10.1.1. However, the Oracle Collaborative Portlets online help contains help topics discussing the Oracle Content Services portlet. |
None |
4427994 |
|
After using Oracle Enterprise Manager to configure the Oracle Calendar application system, the Oracle Calendar application system link does not appear in the Oracle Enterprise Manager welcome page. |
Restart OC4J_OCSClient. |
4472791 |
|
In the Search Log Repository tab of Oracle Enterprise Manager, clicking a Calendar Server link in the Component column results in an error. |
None — the Oracle Calendar server does not have a home page and should not appear as a link in the enterprise manager Search Log Repository tab. |
4528775 |
|
After configuring Oracle Mail with Enterprise Manager, Oracle WebMail is no longer accessible. |
Follow the steps in Section 3.2.6, "Configuring Oracle Mail and Oracle WebMail". |
4539993 |
|
You must perform a workaround before configuring Oracle Voicemail & Fax in an existing Oracle Collaboration Suite deployment. |
Follow the steps in Section 3.2.7, "Configuring Oracle Voicemail & Fax in an Existing Deployment". |
4500591 |
|
You must perform an additional step after changing the SSL HTTPS port number to update OracleAS Portal with the new port number. |
Follow the step in Section 3.2.9, "Additional Step When Changing SSL HTTPS Port Number to Update Oracle Application Server Portal". |
4496201 |
|
Using Oracle Collaboration Suite Search against some applications may cause OCSClient to become unresponsive and the Apache server to time out. |
For more information, and to download patch 4492522, navigate to Oracle MetaLink at: |
4492522 |
|
If a previous Infrastructure Tier was installed on a new Infrastructure tier node, the Oracle Application Server Provisioning Console user creation screen may be displayed instead of Oracle Collaboration Suite Provisioning Console user creation screen. |
This is a browser cache issue. You should clear the browser cache before attempting to provision users on an Infrastructure tier if you had a previous Infrastructure tier installation on that host. |
4558314 |
|
After configuring a new component on an existing Applications tier, the Oracle Collaboration Suite Welcome page does not show a link for the new component. |
Follow the steps in Section 3.2.10, "Adding Applications to your Oracle Collaboration Suite Deployment" |
4439419 |
The following table lists Oracle Collaboration Suite globalization issues.
Table 3-2 Globalization Issues in Oracle Collaboration Suite
| Description | Action | Bug Number |
|---|---|---|
|
When performing bulk provisioning, you must use the same character set as the server's default character set |
Encode the LDIF file in the same character set as is used by the server. |
4430542 |
|
In Greek, the provisioning console in the welcome page is displayed as html code rather than as a URL. |
None |
4519614 |
|
In French (fr) and French Canadian (fr_CA) locales, clicking on the Menu icon of the "Groupe d'instances (farm)" node or selecting a link to the Farm page (such as from the Topology viewer) causes a Javascript error and fails to pop up the menu for that node |
Navigate to the Farm page directly and perform actions from that page. |
4490348 |
|
Several encoding and globalization issues, especially affecting Japanese locales, have been found that can be resolved by downloading a patch from Oracle MetaLink. |
Download patch 4482824 from Oracle MetaLink at: |
4482824, 4430973, 4419614, 4436078, 4224482, 4456593 |
|
The XML log cannot be shown directly in HTML format because the encoding is in the locale of the server, rather than UTF-8. |
Instead of clicking the log link, use the Oracle Enterprise Manager log viewer to view the XML log. |
4539871 |
The following Oracle Collaboration Suite documents have known issues:
Section 3.5.1, "Documentation Issues in Oracle Collaboration Suite Administrator's Guide"
Section 3.5.2, "Documentation Issues in Oracle Collaboration Suite Security Guide"
Please note the following issues in the Oracle Collaboration Suite Administrator's Guide.
Configuring the Single Sign-On Server for Multiple Realms
The procedure described in "Configuring the Single Sign-On Server for Multiple Realms" in Chapter 7 of Oracle Collaboration Suite Administrator's Guide is confusing. (4333951)
In Step 5, you update the Single Sign-On log in page by searching for a block of markup and uncommenting it. To help you find the block of text, search for the following string in the file:
<%-- UNCOMMENT THE FOLLOWING BLOCK TO ENABLE MULTI-SUBSCRIBER SUPPORT --%>
Moving Identity Management to a New Host
The procedure described in "Moving Identity Management to a New Host" in Chapter 12 of Oracle Collaboration Suite Administrator's Guide is missing a step and contains an inaccuracy. (4525024)
After completing Task 1 of the Procedure, you should stop all Applications tier instances. Stop all Applications tier instances that use Oracle Internet Directory. Using the Oracle Collaboration Suite Control Console, navigate to the Instance Home Page for each Applications tier instance and click Stop All. Be sure to leave Oracle Collaboration Suite Control running.
In Task 3, Step 5, the location provided for ldap.ora is incorrect. Edit ORACLE_HOME/ldap/admin/ldap.ora
Changing the HTTP Server Port on Identity Management
A step was omitted from Task 3 of the procedure described in "Changing the HTTP Server Port on Identity Management", in Chapter 14 of Oracle Collaboration Suite Administrator's Guide.
In Task 3, you are instructed to modify the Oracle HTTP Server Listen and Port directives. In the manual steps provided for the HTTPS port, you are instructed to edit the ssl.conf file located at ORACLE_HOME/Apache/Apache/conf/ssl.conf.
In addition to editing the Listen and Port directives as indicated, you must also edit the <VirtualHost _default_:4443></Virtual> directive. For example, if you were changing the port number to 4445, you would set the following:
Listen 4445 Port 4445 <VirtualHost _default_:4445></Virtual>
All three directives must be set to use the same port number.
Changing Oracle Internet Directory Ports
Labels for certain procedures in Task 3 of the procedure described in "Changing Oracle Internet Directory Ports", in Chapter 14 of Oracle Collaboration Suite Administrator's Guide are incorrect.
In Task 3, Step 1, you are instructed to create a file called mod.ldif and then run the ldapmodify command. Different syntax is provided "For HTTP" and "For HTTPS".
"For HTTP" means "For Oracle Internet Directory non-SSL port".
"For HTTPS" means "For Oracle Internet Directory SSL port.
Task 3, Step 3d is "Change the value of OIDport (for an HTTP port change) or OIDsslport (for an HTTPS port change) to the new port number, and then save the file."
"HTTP port change" means "Oracle Internet Directory non-SSL port change".
"HTTPS port change" means "Oracle Internet Directory SSL port change".
Changing the OracleAS Web Cache Listen Port
The procedure described in "Changing the OracleAS Web Cache Listen Port" in Chapter 14 of Oracle Collaboration Suite Administrator's Guide is missing steps, including steps required for single-box installations (4523464, 4523491).
After completing Task 7: Update OracleAS Portal Configuration, you should re-register OracleAS Portal. To do this:
Ensure that the ORACLE_HOME environment variable is set.
Register the URLs using the Portal Dependency Settings tool (available in ORACLE_HOME/portal/conf):
ptlconfig –dad dadname –wc –site
where dadname is the name of the OracleAS Portal Database Access Descriptor.
After completing Task 9: Update Mobile Collaboration, you need to update the Oracle Internet Directory Service Registry with the new port number. Perform the following steps:
Start the Oracle Directory Manager and enter connection information for your instance of Oracle Internet Directory:
ORACLE_HOME/bin/oidadmin
Host: <infrahost.yourdomain.com>
Port: 389
Username: cn=orcladmin
Password: <password>
To access the Service Registry, select the following items in order in the System Objects pane:
Entry Management
cn=OracleContext
cn=Services
Select each configured component in the System Objects pane to display its attributes. Components which have been configured will contain a cn=VirtualServices object, which in turn contains one or more child objects. These child objects contain virtual services URIs, including port numbers.
Check each component, changing each URI containing connection information to the old OracleAS Web Cache Listen Port to the new port number. Save your changes and close Oracle Directory Manager.
Changing Oracle Internet Directory from Dual Mode to SSL Mode
A step was omitted from the procedure described in "Changing Oracle Internet Directory from Dual Mode to SSL Mode", in Chapter 12 of Oracle Collaboration Suite Administrator's Guide, and a file location indicated in this procedure is incorrect. (4524939)
Before beginning this procedure, you should shut down all Applications tiers using this instance of Oracle Internet Directory. Be sure to leave the Oracle Collaboration Suite Control (emctl) process running on all Applications tiers.
You can shut down the tiers using Oracle Collaboration Suite Control by navigating to each Applications tier home page and clicking Stop All.
The location of the file ldap.ora has been wrongly specified as $ORACLE_HOME/network/admin/ldap.ora. This file is specified in Task 1, Step 4, and in Task 2, Step 7.
The correct location is $ORACLE_HOME/ldap/admin/ldap.ora.
Replacing the Default Logo on the Oracle Collaboration Suite Portal Home Page
The procedure provided in "Replacing the Default Logo on the Oracle Collaboration Suite Portal Home Page", in Chapter 15 of Oracle Collaboration Suite Administrator's Guide is inaccurate.
The correct procedure to replace the default logo is as follows:
Log in to Portal as an administrator (such as orcladmin)
Select the Navigator global button
Select the Page Groups tab
Click the Oracle Collaboration Suite link
Click the Navigation Pages link
Locate "Oracle Collaboration Suite:Banner" and click the edit link next to it
Locate the region containing the default Oracle Collaboration Suite logo, and select the Edit icon immediately to the left of the logo image
On the Item Attributes screen, select Browse to upload a custom logo image
When you have finished, select OK to save your settings.
Changing the Default Colors and Fonts on the Oracle Collaboration Suite Portal Home Page
The procedure "Changing the Default Colors and Fonts on the Oracle Collaboration Suite Portal Home Page" in Chapter 15 of Oracle Collaboration Suite Administrator's Guide contains an error. (4519963)
In Step 4, the page group "OCS_V2_PAGE_GROUP" does not exist. Instead, locate the Oracle Collaboration Suite page group.
In Step 6, the "OCS_V2_PAGE_GROUP" style does not exist. Instead, locate the OCSHomePageStyle style and edit it.
Customizing the Oracle WebMail Logo
The information provided in "Customizing the Oracle WebMail Logo", in Chapter 15 of Oracle Collaboration Suite Administrator's Guide is out of date and contains inaccuracies and omissions.
In Step 1, the location of the logo is incorrect. The OC4J_UM container was used for earlier versions of Oracle Collaboration Suite. In Oracle Collaboration Suite 10g Release 1, Oracle WebMail is part of the OC4J_OCSClient container.
Another copy of the image is stored in /um/admin/pages. You should replace this image with your custom image as well.
After placing a new image, you must restart OracleAS WebCache in order for the new image to be loaded into the cache. Until you restart OracleAS WebCache, clients accessing the image will continue to load the cached, older version of the image.
Customizing Oracle WebMail Colors and Fonts
The information provided in "Customizing Oracle WebMail Colors and Fonts", in Chapter 15 of Oracle Collaboration Suite Administrator's Guide is out of date and contains an inaccuracy. (4519980)
The location of the .xss files provided is incorrect. The OC4J_UM container was used for earlier versions of Oracle Collaboration Suite. In Oracle Collaboration Suite 10g Release 1, Oracle WebMail is part of the OC4J_OCSClient container. The correct location is:
ORACLE_HOME/j2ee/OC4J_OCSClient/...
Please note the following issues in the Oracle Collaboration Suite Security Guide.
Enabling or Disabling SSL for Oracle Enterprise Manager connections to Oracle Internet Directory
Please note the following correction to the "Securing Oracle Voicemail & Fax Connections" section in the Oracle Collaboration Suite Security Guide. (Bug 4515736)
In the subsection, "Enterprise Manager Connections," there is a See Also note with a link to "Enabling SSL in Oracle Voicemail & Fax." This linked information is incorrect. Instead, refer to the procedure below to disable SSL for Enterprise Manager connections.
To enable or disable SSL for Enterprise Manager connections to Oracle Internet Directory:
Log in to Enterprise Manager Grid Control, and navigate to the home page.
In the Target Search section, select Oracle Voicemail & Fax in the Search list and click Go.
Select the Voicemail & Fax target from the All Targets list and click Configure.
In the Configure Voicemail & Fax: name_of_Voicemail_&_Fax_target page, select Always require SSL for connections to enable SSL for all connections from Enterprise Manager to Oracle Internet Directory for this target.
To disable SSL connections for this target, deselect Always require SSL connections.
Click Finish.
Running the SSL Script on the Applications Tier
The script described in the procedure "Running the SSL Script on the Applications Tier" in Oracle Collaboration Suite Security Guide is missing a True or False parameter. (4516978)
The script should appear in the document as follows:
$ORACLE_HOME/bin/midtierSSLConfigTool.<sh|bat> <oid hostname> <oid port> <oid admin dn> <oid admin password> <http server SSL port> <https> <hostname of the computer> <True | False>
Where True | False is the boolean flag that determines the communication to OID.
True: Communication to the Oracle Internet Directory using SSL only
False: Normal communication to Oracle Internet Directory
This section should also contain the following commands for stopping and starting OC4J_OCSClient. OC4J_OCSClient should be restarted after enabling SSL.
./opmnctl stopproc process-type=OC4J_OCSClient ./opmnctl startproc process-type=OC4J_OCSClient
This chapter summarizes release note issues associated with the Oracle Web Access client. This chapter contains the following sections:
Section 3.6.2, "Known Limitations and Workarounds in the Oracle Web Access Client"
Section 3.6.3, "Known Issues in the Oracle Web Access Client"
Section 3.6.4, "Globalization Issues in the Oracle Web Access client"
The Oracle Web Access client is a browser-based application that looks, feels and performs like a desktop application. It provides access to various features of Oracle Collaboration Suite, including:
E-mail with support for HTML text editing
Personal and shared Address Books with Corporate Directory (Global Address Book) integration and support for shared contacts
TimeBar view of calendar appointments and reminders, with direct access to the Oracle Calendar Web client for creating and editing meetings
The Oracle Web Access client supports standard Web browsers, including Internet Explorer, Mozilla and Mozilla Firefox. Your personal preferences are stored on the server so you can access your mail wherever and whenever you want, through a secure, familiar interface on the supported browser of your choice. Work with and manage your information using drag-and-drop functionality, cascading menus, context menus, and resizable panes.
The following sections describe known limitations and workarounds for the Oracle Web Access client.
Section 3.6.2.2, "Placing Constraints on Directory Entries Returned by the Oracle Web Access Client"
Section 3.6.2.3, "Searches of Attachments in Different Character Sets"
Section 3.6.2.4, "Delivery Receipts Not Supported with OJMA"
Section 3.6.2.5, "Arabic and Other Bidirectional Languages Not Supported"
Some Oracle Internet Directory fields (such as displayname) are not indexed by default. Because of this, some Corporate Directory searches will appear to return no results in the Oracle Web Access client, or will cause errors. Affected attributes could include:
displayname givenname middlename sn title departmentnumber telephonenumber homephone facsimiletelephonenumber mobile pager homepostaladdress c l postalcode st street mail
To find out which of these attributes is not being searched, try querying them with a tool such as ldapsearch and see which returns an error code 53.
You can either manually index the affected attributes so that they can be searched with the Oracle Web Access client, or silently exclude them from queries so that search errors will no longer occur. Oracle recommends indexing the attributes, since excluding them from searches may lead to confusion for users.
Manually indexing an attribute
Before you index attributes, you must shut down Oracle Internet Directory or set it to Read Only mode. See Oracle Internet Directory Administrator's Guide for more information.
Note:
These steps are written with the understanding that the following environment variables are used:ORACLE_HOME: The Infra ORACLE_HOME path
On Solaris and Linux: LD_LIBRARY_PATH: This should include $ORACLE_HOME/lib32:$ORACLE_HOME/lib
On HP-UX: LD_LIBRARY_PATH: This should include $ORACLE_HOME/lib;SHLIB_PATH: This should include $ORACLE_HOME/lib32.
ORACLE_SID: The SID of the Infra database
Change to the /ldap/bin directory as follows:
cd $ORACLE_HOME/ldap/bin
Index the attribute as follows:
./catalog.sh -connect $ORACLE_SID -add \
-attr attribute_name
Where attribute_name is the attribute you want to index; for example, displayname.
Repeat the previous step for each attribute you want to index.
Open oc4j.properties; this file can be found at a location similar to the following:
$ORACLE_HOME/j2ee/OC4J_OCSClient/config/oc4j.properties
For each attribute you indexed (as described in steps 2 and 3), update the appropriate entry in oc4j.properties as follows:
oracle.ocsclient.directory.capability.search.attr.attribute_name=enabled
Where attribute_name is the attribute you want to index; for example, displayname.
Excluding Attributes from Queries
To exclude attributes from queries, update the appropriate entry in oc4j.properties as follows:
oracle.ocsclient.directory.capability.search.attr.attribute_name=disabled
Where attribute_name is the attribute you want to exclude; for example, displayname.
(4409722)
Note:
For the latest updates to this and other procedures in this document, navigate to the following location and open the appropriate release notes document for your platform:The Oracle Web Access client uses a connection pool that connects as the e-mail container entity (cn=EmailServerContainer,cn=Products,cn=OracleContext). This means that Corporate Directory queries executed in the Oracle Web Access client may reveal entries that are normally hidden from end-users. Until this connection method is restructured, a special configuration has been provided so that administrators can define an 'AND' criteria restricting the LDAP objects that are returned. Whenever access controls are added to restrict the visibility of end-user directory data, Oracle Web Access client administrators should consider overriding these values. (4495854)
Currently, there are only two types of objects returned by the Oracle Web Access client Corporate Directory:
Public Users
Public Distribution Lists
There are two available configurations, one for each data type. They can be overridden in oc4j.properties (located in $ORACLE_HOME/j2ee/OC4J_OCSClient), and should be formatted as follows:
# <dl_condition> and <user_condition> should be replaced by # RFC 2254-compliant query strings. oracle.ocsclient.directory.ldap.dlobjectandcondition=dl_condition oracle.ocsclient.directory.ldap.userobjectandcondition=user_condition
The default value of dl_condition is (objectclass=orclmailgroup) whereas the default value for user_condition is (objectclass=orclUserV2). The value of each of these and conditions determines the constraints that will be placed on each end-user query. When overriding this value, you must always include a condition that ensures a distinct objectclass for the two supported object types (usually composed of the defaults values above).
The following are examples of custom search constraints; notice that objectclass=condition is retained for all customized values.
# hide all users which have '_hidden@' as part of their e-mail address. oracle.ocsclient.directory.ldap.userobjectandcondition=(&(objectclass=orclUserV2)(!(mail=*_hidden*)))
# hide all users that have been disabled in oiddas oracle.ocsclient.directory.ldap.userobjectandcondition=(&(objectclass=orclUserV2)(!(orclisenabled=DISABLED)))
# use an objectclass other than 'orclmailgroup' for DLs # (to support older OID setups).oracle.ocsclient.directory.ldap.dlobjectandcondition=(objectclass=mailgroups)
For more information on LDAP or LDAP query strings, see Oracle Internet Directory Administrator's Guide.
When you perform a search for attachment names, search behavior is determined by the character set used by the Oracle Mail server to build the search index. In other words, if the characters you are searching for are not found in the character set used by the Oracle Mail server to build the search index, the attachment will not be found.
Delivery receipts can be requested with messages sent using a Mail Transfer Agent such as sendmail, or an SMTP server. However, the Oracle Web Access client has an option to send messages using Oracle Javamail Service Provider (OJMA) instead of SMTP, in which case messages are placed directly in the database for sending. With this transport mode, delivery receipts cannot be requested. Accordingly, the controls for requesting receipts in the Oracle Web Access client are disabled when using OJMA.
The Oracle Web Access client does not support Arabic and other bidirectional languages.
With heavy use, the number of database connections from the Oracle Web Access client can become very high.
You can change the database connection pool scheme used by the Oracle Web Access client to a fixed scheme by making the following property change:
oracle.mail.sdk.esmail.cache_scheme=2
The maximum number of connections can then be set using the property
oracle.mail.sdk.esmail.connpool_max_limit
With the fixed scheme, the number of database connections from the Oracle Web Access client to the database will never exceed the maximum limit specified. However, this might degrade the performance of the Oracle Web Access client. (4485215)
The following tables list known issues in the Oracle Web Access client:
Table 3-3, "Mail-Related Issues in the Oracle Web Access client"
Table 3-4, "Contact-Related Issues in the Oracle Web Access client"
Table 3-5, "Various Known Issues in the Oracle Web Access client"
Table 3-6, "Browser-Related Issues in the Oracle Web Access client"
The following table lists mail-related issues in the Oracle Web Access client:
Table 3-3 Mail-Related Issues in the Oracle Web Access client
| Description | Action | Bug Number |
|---|---|---|
|
Attachments OK and Cancel buttons do not function as expected in the Attach Files page. |
None |
4386982 |
|
Deleting mail In the Deleted Items folder (or a subfolder thereof), if you open a message in a new window and choose Delete, you will not be warned before the message is permanently removed. |
None |
4484000 |
|
Drafts New and existing drafts are always saved in the default Draft folder. |
None |
4487141 |
|
Drafts Delivery receipt notification flags are not saved with drafts. |
None |
4360082 |
|
Drafts Can open multiple compose windows for one draft. |
None |
4376551 |
|
Drafts External images in Web pages are not saved in drafts. |
None |
4482623 |
|
Drafts Cannot save drafts in a non-draft folder more than once. |
None |
4498431 |
|
Drafts Drafts are not recognized correctly in IMAP mode. |
None |
4497930 |
|
Composing mail Pressing the |
None |
4484184 |
|
Composing mail When browsing for recipients, users with no display names are shown as "Untitled." |
None |
4394487 |
|
Composing mail Alt text is not added to inline images. |
None |
4495082 |
|
Flags Flag indicators in the Reading pane and message window are out of sync. |
None |
4463648 |
|
Folders Unread message count is shown for currently opened folder and Inbox. |
None |
3597128 |
|
Folders Default message sort order for a returning user is not saved. |
None |
4230266 |
|
Folders Users can remove drafts from shared folders. |
None |
4484904 |
|
Folders Prefixes such as "RE", "FW", and "FWD" are not ignored when sorting by subject. |
None |
4396789 |
|
Folders When viewing a shared Drafts folder, the To column is displayed as the From column. |
None |
4474359 |
|
Folders When you share a folder with a newly created user, that user may not immediately appear in the list of users with whom the folder is shared. |
Restart the OC4J_OCSClient container: $ORACLE_HOME/opmn/bin/opmnctl restartproc gid=OC4J_OCSClient |
4540149 |
|
Gmail messages Plain text messages from Gmail are treated as inline part. |
None |
4484289 |
|
HTML Text mode The most recently used style is not retained if the message was not saved or sent. |
None |
4399389 |
|
HTML Text mode The cursor does not appear in the right place when there is an inline message in the composition window. |
None |
4502678 |
|
HTML Text mode HTML / Plain Text mode cannot be saved as (an implicit) preference. |
None |
4496553 |
|
HTML Text mode Saving messages with inline images causes an error. |
None |
4495467 |
|
Oracle Workflow messages Messages forwarded from Oracle Workflow have blank bodies. |
None |
4489598 |
|
Receipts Users are re-prompted to send read receipts every session. |
None |
4483934 |
|
Search shared folders Search results from shared folders do not identify users in folder path. |
None |
4453559 |
|
Search shared folders Cannot search for unread messages in shared folders. |
None |
4490821 |
|
Sending mail If a recipient's e-mail address includes invalid characters such as square brackets, it is possible that an unspecific error message will result and the user will not be given a chance to correct the problem. |
None |
4445255 |
|
URLs URLs with commas are not linkable. |
None |
4478171 |
|
Viewing mail In the List pane, message entries are not updated after the character set is changed. |
None |
4208604 |
|
Viewing mail In the List pane, HTML entities (strings beginning with '&' and ending in ';', for example, |
None |
4440474 |
|
Viewing mail Viewing messages that have unrecognized field formats (such as, occasionally, the From field in drafts created by other mail clients) may result in an error. |
None |
4497927 |
The following table lists contact-related issues in the Oracle Web Access client:
Table 3-4 Contact-Related Issues in the Oracle Web Access client
| Description | Action | Bug Number |
|---|---|---|
|
Search Some Oracle Internet Directory fields (such as |
Refer to Section 3.6.2.1, "Corporate Directory Searches" for post-install workaround instructions. |
4409722 |
|
Search Address book search does not support nicknames. |
None |
4473775 |
|
Search Long Corporate Directory queries do not time out. |
None |
4414275 |
|
Search Searching for flagged contacts returns inaccurate results. |
None |
4460161 |
|
Distribution lists The Oracle Web Access client does not display an error message when a distribution list contains circular references. |
None |
4394689 |
|
Distribution lists List members created through Oracle Connector for Outlook are not shown correctly. |
None |
4503870 |
|
Distribution lists Cannot send mail to another user's shared distribution list. |
None |
4410035 |
|
Distribution lists Cannot view public distribution lists' members. |
None |
4485407 |
|
Various Deleting contact clears the Show Only field. |
None |
4488009 |
|
Various Simultaneous browsing of shared address books causes an error. |
None |
4473303 |
|
Various Contact and distribution list flags are not correctly synchronized with Oracle Connector for Outlook flags. |
None |
4411038 |
|
Various Web site information created through Oracle Connector for Outlook does not appear in the Oracle Web Access client. |
None |
4493978 |
|
Various The format hint for birthday and anniversary dates is missing. |
None |
4455476 |
|
Various Unable to reassign same speed dial number to personal contacts or distribution lists. |
None |
4485895 |
The following table lists various known issues in the Oracle Web Access client, including issues with accessibility, performance, user interface, contacts, and preferences.
Table 3-5 Various Known Issues in the Oracle Web Access client
| Description | Action | Bug Number |
|---|---|---|
|
Accessibility JAWS screen reader software reads the "Insert Hyperlink" and "Insert Image" buttons as "Button." |
None |
4473582 |
|
Accessibility Some accessible pages are missing |
None |
4298640 |
|
Accessibility The accessible shortcut key for "Forward Message" is not working. |
None |
4473599 |
|
Accessibility Accessible radio and checkbox elements in Preferences are missing labels. |
None |
4466485 |
|
Accessibility The browser display becomes corrupted if the user changes the browser font size, such as by typing "Ctrl +". |
None |
4302722 |
|
High availability Email does not logout properly after |
None |
4378321 |
|
High availability Unable to create contacts after Oracle Internet Directory failover. |
None |
4431445 |
|
Performance Large message body with many email addresses is slow to render. |
None |
4383491 |
|
Performance Typing in HTML Text mode causes unexpectedly high processor use on a user's computer. |
None |
4501586 |
|
User interface Using online help after closing the Oracle Web Access client main window causes a JavaScript error. |
Close the online help before exiting the Oracle Web Access client. |
4396787 |
|
User interface Keyboard navigation of the contact hierarchy is unpredictable. |
Use the mouse to navigate within the contact hierarchy. |
4281898 |
|
User interface If you use a context menu to paste in text to the Search field, the Search button is not enabled. |
Paste the text with a keyboard shortcut such as |
4397835 |
|
User interface Column widths reset to default after switching folders. |
None |
4452887 |
|
User interface The composition window's header may not resize correctly if attachments are present. |
None |
4461000 |
|
User interface Drop-down controls may not be positioned correctly. |
None |
4250498 |
|
User interface When using the 'Reply All' feature, if a contact appears multiple times with different aliases in the To: or Cc: lists, they will be listed multiple times in the new message's To: list. |
Delete extra occurrences of the same contact in the To: field after selecting 'Reply All' |
4454043 |
|
User interface When using the Tab key to navigate, the focus can be difficult to see on some items. |
None |
4323410 |
|
User interface You cannot use the Tab key to select the New menu. |
None |
4270210 |
|
User interface Toolbar items do not wrap, and are not shown if the size of the window is reduced too much. |
Resize the window until all toolbar items are visible |
4312705 |
The Oracle Web Access client supports most current browsers (such as Internet Explorer 6.0 and later, Mozilla 1.7.3 and later, all versions of Firefox), but a small number of browser-specific issues have been identified. The following table summarizes these issues.
Table 3-6 Browser-Related Issues in the Oracle Web Access client
| Description | Action | Bug Number |
|---|---|---|
|
Firefox Cannot insert hyperlinks into a signature. |
None |
4473369 |
|
Firefox Folder context menus do not work. |
Use the Oracle Web Access client main menu. |
4479515 |
|
Firefox Unable to create new folders. |
None |
4479547 |
|
Firefox If "Smooth Scrolling" is enabled on Firefox, scrolling through lists in the Oracle Web Access client may have unexpected results. This is a browser issue. |
Turn "Smooth Scrolling" off (it is off by default) as follows:
|
4639994 |
|
Firefox and Mozilla Browser scrollbars show through interface items. |
None |
4359428 |
|
Firefox and Mozilla The keyboard shortcut |
None |
4432638 |
|
Internet Explorer The cursor is hidden when you tab to the Locate People tool. |
Click inside the Locate People field. |
3873261 |
|
Internet Explorer When composing mail, you cannot delete text from the message body after attaching files or opening and closing the "Insert Image" or "Insert Link" dialog boxes. |
Click in the message body field. Text editing can then proceed as expected. |
4446919 |
|
Internet Explorer Sorting thousands of items can take a long time. |
None |
4321955 |
|
Internet Explorer The whole user interface can be selected from certain parts of a message header. |
None |
4432888 |
|
Internet Explorer The names of attached files may wrap incorrectly in the composition window. |
None |
4460198 |
|
Internet Explorer Some messages may wrap incorrectly. |
None |
4496171 |
|
Internet Explorer 6.0.2800 with Windows 2000 Some contact fields become blank. |
None |
4495322 |
|
Mozilla Virtual tree scrolls up on selecting bottom tree node. |
None |
4068067 |
|
Mozilla Cannot drag and drop unless the cursor is over text. |
None |
4175054 |
|
Mozilla Selection problems occur in text fields and text areas. |
None |
3811308 |
|
Mozilla Resizing preview pane resets scroll position. |
None |
4301536 |
|
Mozilla Inline images are not cached. |
None |
4307189 |
|
Mozilla The "Clear" button is truncated on the "Create Distribution List" page. |
None |
4371738 |
|
Mozilla Built-in shortcuts are not blocked when focus is in message pane header. |
None |
4391301 |
|
Mozilla Pressing shortcut key |
None |
4493073 |
The following table lists Oracle Web Access client globalization issues. Most of these issues are related to ISO-2022-JP character set variant support (Japanese).
Table 3-7 Globalization Issues in the Oracle Web Access client
| Description | Action | Bug Number |
|---|---|---|
|
In multibyte character-set installations, if a user's Display Name contains a single-byte space character, the auto-complete feature will truncate the address in the address bar fields. |
Enter the full address manually to work around this issue. |
4486102 |
|
ISO 2022-JP issues:
|
None |
4501041 4505834 4488120 |
|
Japanese text / plain text messages are encoded incorrectly with JDK character converter. |
None |
4461722 |
|
URLs with multiple-byte characters may not display properly in plain text composition. |
None |
4454375 |
|
Multiple-byte display names that contain single-byte spaces are truncated in auto-complete. |
None |
4486102 |
|
Certain shift-JIS characters are not supported. |
None |
3614135, 4055059 |
|
Character set determination mechanism assumes that the message header and message body are always encoded with the same character set. |
None |
4226129 |
|
Characters in a message subject may be indecipherable if the original message was sent without a well-defined encoding character set. |
None |
4506621, 4445458 |
|
Characters in some non-ASCII attachment names may be indecipherable. |
None |
4261860, 4472482 |
|
Characters in attachment names may be indecipherable when the attachment locale is different from the client's operating system locale. |
None |
4356184 |
|
In French on Mozilla and Firefox, the drop-down arrows for new message and new folder are truncated. |
None |
4431198 |
|
Text in From and To fields encoded with ISO-8859-8-I is not shown. |
None |
4468753 |
|
Traditional Chinese delivery receipts message are indecipherable. |
None |
4519675 |
|
Translation issues:
|
None |
4394619 4496439 4485456 |
