| Oracle® Collaboration Suite Readme Release 2 Patch Set 1 (9.0.4.2.1) for Windows Part Number B14386-02 |
|
|
View PDF |
| Oracle® Collaboration Suite Readme Release 2 Patch Set 1 (9.0.4.2.1) for Windows Part Number B14386-02 |
|
|
View PDF |
This chapter contains information on various new features of Oracle Collaboration Suite and its components included in patch set Release 2 Patch Set 1 (9.0.4.2.1).
This chapter includes the following topics:
Section 5.1, "Enabling New Language Translations (Optional)"
Section 5.4, "New and Updated Server Parameters for the Oracle Calendar Server"
The Oracle Collaboration Suite patch set Release 2 Patch Set 1 (9.0.4.2.1) provides new language translations for Hungarian, Russian, Czech, and Romanian.
If you intend to use one or more of these languages, you must enable them according to the instructions in this section.
|
See Also: Section 3.2.1, "Enabling Support for New Languages in Oracle Calendar" for enabling new language support in Oracle Calendar |
The following sections explain how to enable the new language translations for the infrastructure and the middle tier.
Infrastructure
|
Caution: Enabling the same language more than once in Oracle9iAS Single Sign-On will result in repository corruption. Select the language selection menu from the Oracle9iAS Single Sign-On login page to see which languages are enabled for the instance. |
Set the following environment variables:
Set the ORACLE_HOME
Set the PATH to include the following:
%ORACLE_HOME%\bin
Create a directory in the infrastructure, as follows:
mkdir %ORACLE_HOME%\sso\nlsres\ctl\language
where language is one of the following language codes:
hu: Hungarian
ru: Russian
cs: Czech
ro: Romanian
Copy the middle_tier_%ORACLE_HOME%\portal\admin\plsql \nlsres\ctl\language file to the infrastructure_%ORACLE_HOME%\sso\nlsres\ctl\language file.
|
Note: If using FTP, execute the transfer in binary mode. |
Enable Oracle9iAS Single Sign-On to support the new language by running the following command from the infrastructure (the following command is one continuous line):
%ORACLE_HOME%\jdk\bin\java -jar %ORACLE_HOME%\sso\lib\ossoca.jar langinst language 1 %ORACLE_HOME%
Middle Tier
|
Caution: Enabling the same language more than once in Oracle9iAS Portal will result in repository corruption. Enable the language selection portlet to display enabled languages. |
|
See Also: Oracle Application Server Portal Configuration Guide for more information |
Set the following environment variables:
Set the ORACLE_HOME
Set the PATH to include the following:
%ORACLE_HOME%\bin
Enable Portal to support the new language by running the following command from the middle tier (the following command is one continuous line):
%ORACLE_HOME%\assistants\opca\ptlasst.bat -mode LANGUAGE -s portal -sp portal_password -c host.domain.com:1521:SID -lang language -available -silent -m portal -verbose
where language is one of the following language codes:
hu: Hungarian
ru: Russian
cs: Czech
ro: Romanian
and portal_password is the Oracle9iAS Portal schema password. It can be retrieved from Oracle Internet Directory with dn:
OrclResourceName=portal_user,orclReferenceName=SID.host.domain.com, cn=IAS Infrastructure Databases,cn=IAS,cn=Products,cn=OracleContext
host.domain.com:1521:SID specifies the connect string to the infrastructure database. The format should be host_name:port:SID. Default port and SID are 1521 and iasdb respectively.
With this patch set, Oracle Collaboration Suite now supports Oracle Database 10g. Full instructions for using Oracle Database 10g with Oracle Collaboration Suite are provided in Chapter 4, "Additional/Optional Oracle Collaboration Suite Upgrade Scenarios".
This section describes the new Oracle Calendar features and includes the following topics:
Section 5.3.2, "New Features in the Oracle Calendar Administrator"
Section 5.3.3, "New Features in the Oracle Calendar Application System"
Section 5.3.4, "New Features in Oracle Connector for Outlook"
Section 5.3.5, "New Features in the Oracle Calendar Desktop Clients"
Section 5.3.6, "New Features in the Oracle Calendar Sync Clients"
This release of the Oracle Calendar server includes the following new features:
Performance enhancements
Server side security enforcement
Improved event retrieval
Improved low-level event searching
Decreased CPU usage through tuning of low-level database access
Decreased CPU usage through tuning of Global Address List construction
Scalability enhancements
Increased maximum number of contacts for each node to between 600000 and 1 million depending on your setup
Serialization of synchronization context refreshes
Tighter integration with Oracle Internet Directory
Access to more user attributes
Better support for users who have multiple e-mail addresses in Oracle Internet Directory (3299418)
Increased deployment flexibility through support for non-persistent (on demand) Directory Access Server connections
Support for coexistence between a standalone calendar server connected to an iPlanet directory server and an Oracle Calendar server connected to an Oracle Internet Directory server and linked through Oracle Directory Integration and Provisioning to an iPlanet directory server
Increased support for Oracle Connector for Outlook
Support for personal annotation of meeting details
Increased length of the country name and middle name attributes
Support for longer resource IDs
Support for longer resource names
Support for the following attributes in the user information dialog box:
Department
Display
Home (phone number)
Office
Address (office address)
City (office address)
State (office address)
Zip code (office address)
Pager (phone number)
Alias
Business 2 (phone number)
Home 2 (phone number)
Notes (phone number)
Assistant
Assistant (phone number)
Manager (organization)
Support for the capability to invite users by e-mail address or user ID
Support for the ability to restrict users from browsing the user directory when logging in (3266790)
The initials attribute is now mapped to middle name by default
Web conferencing notifications can be disabled
New languages supported for notification and reminder e-mails: Czech, Hungarian, Romanian and Russian
Support for longer lists of Oracle Calendar Web client favorites
Several server parameters have been added and updated to support new features. For a detailed listing of the changes see the Oracle Collaboration Suite Release Notes.
The capability to limit the maximum number of attendees for a meeting has been added. The default limit is 5000.
In this release of the Oracle Calendar Administrator you can search for resources by category using the advanced search.
This section includes the following topics:
New Features in the Oracle Calendar Web Client
This section lists new features of the Oracle Calendar Web client.
The Favorites list can now include more than 15 agendas, provided this is configured in the ocwc.conf and unison.ini files. See Section 3.2.4, "Increasing the Size of the Favorites List in the Oracle Calendar Web Client" for configuration instructions. (3138441)
The Web client now supports the following languages: Romanian, Russian, Hungarian and Czech. See Section 3.2.1, "Enabling Support for New Languages in Oracle Calendar" for configuration instructions. (3387489)
E-mail addresses can now be used to search for users. (3292710)
Pages have been optimized for faster performance. (3306569)
Opening remote users' agendas is now faster. (2984604, 3315169)
Supported default attachment types now include .zip, .bmp, and .png. See Section 3.2.2, "Reducing Page Size and Enabling Support for New Attachment Types in Oracle Calendar" for configuration instructions. (3140301)
Internet Explorer's Autocomplete feature is now disabled for text fields in Oracle Calendar; this is to increase security, particularly for users who share a computer. (3267536)
Various enhancements, such as a clearer subject line, have been implemented in Resource Approval e-mail messages. (3274584)
The Oracle Calendar portlet can now display meetings that last more than 24 hours. (3104320)
External users invited to meetings are now displayed in the attendees list. (3258432)
The time zone table under Preferences has been translated. (3125321)
The names of files attached to meetings are now displayed. (2634962)
The New Task page in Accessible mode is more clearly organized. (3402994)
New Features in Oracle Sync Server
This section lists new features of Oracle Sync Server.
The following devices have been certified for use with Oracle Sync Server:
Sony Ericsson P900 (with firmware R4A06)
Sony Ericsson T610/T616
Nokia 6600
Nokia 6820
Siemens M55
This release provides support for version 2.1.0.1 of the Synthesis SyncML client used on the following devices with Oracle Sync Server:
PocketPC:
HP iPAQ 5550
Dell Axium
Siemens SX56
Palm:
Sony Clie TG50
Palm Tungsten W
Palm Tungsten T3
This release provides support for Blackberry devices used with Oracle Sync Server and Research In Motion's Consilient2 SyncML solution.
New Features in Oracle Calendar Web Services
This section lists new features of Oracle Calendar Web services.
Summaries: Through Web services, users can now query the Oracle Calendar server for the number of unconfirmed events, number of open tasks, or number of overdue tasks, based on a date range.
Searches: Through Web services, users can now search the Oracle Calendar server for events based on criteria such as location, title, start time and attendees.
This section lists new features of Oracle Connector for Outlook.
Ability to add personal notes to an entry. The steps are as follows:
Type the text in the Notes section of the entry.
Save the entry.
Your personal note is displayed in the Notes section. To view the entry organizer's original notes, click Organizer's Notes.
If the entry owner modifies the original note, a bell icon will appear beside the Organizer's Note button. To view the organizer's modified note, click Organizer's Note. The bell icon will not be displayed after you view the modified note.
|
Note: This feature is only available for calendar entries created by other users. Users cannot add personal notes to entries they create. |
Use of an extensible time zone table. To address issues encountered by users of older versions of Windows in certain time zones, the way time zones are handled was re-architectured. This re-architecture enables Oracle Connector for Outlook to dynamically adapt to time zone discrepancies between the Windows' time zone and the calendar server's time zone. (3207187, 3197015)
To provide quick access to other users' folders, a list of most recently opened other users' folders is available by selecting File, then selecting Open. This list is also available by using a keyboard shortcut.
Additional GAL user attributes displayed in the Properties dialog box
User attributes displayed are more representative of the fields available in Oracle Internet Directory
Certain attributes can be hidden through the use of server-side parameters
|
Note: Display of direct reports is not yet supported. |
Significant decrease in e-mail notifications sent for Web conferences
E-mail notifications are only sent when a Web conference is created, the time is updated or if a new attendee is added
Selecting I am currently out of the office using the Out of Office Assistant defaults to the Reply only once to each sender option instead of the Reject sender's e-mail option
Support for Windows Server 2003
Support for ActiveSync to 3.7.1
Support for Czech, Russian and Romanian
This section includes the following topics:
Oracle Calendar Desktop Client for Windows
Ability to search for users based on their user IDs and e-mail addresses
Comma and tab-delimited exports include information from the Details field
Support for French
Oracle Calendar Desktop Client for Macintosh
Ability to search for users based on their user IDs and e-mail addresses
Comma and tab-delimited exports include information from the Details field
Oracle Calendar Desktop Client for Linux
Ability to search for users based on their user IDs and e-mail addresses
Comma and tab-delimited exports include information from the Details field
Oracle Calendar Desktop Client for Solaris
Ability to search for users based on their user IDs and e-mail addresses
Comma and tab-delimited exports include information from the Details field
This section includes the following topics:
Oracle Calendar Sync for Palm for Windows
Support for the Tungsten W
Support for French
Oracle Calendar Sync for Palm for Macintosh
Support for Mac OS 9.22 to 10.3
Oracle Calendar Sync for Pocket PC
Support for the HP IPAQ 5550 (2003) and Dell Axim 2003
Support for French
This section describes new and updated parameters for the Oracle Calendar server and contains the following topics.
Table 5-1 contains the new parameters that have been added to the unison.ini file.
Table 5-1 New parameters added to the unison.ini file
Controlling the Rate of Oracle Connector for Outlook Refreshes
Parameter: oc_minsendreceiverate
Section: [CLIENT]
Description: Specifies the minimum number of minutes before the next automatic call to the server to check for new agenda entries. This is used by Oracle Connector for Outlook only.
Accepted values: Any positive integer
Default value: 15
Specifying Client Application Search Methods
Parameter: searchorder_user
Section: [CLIENT]
Description: Specifies to the client which search methods to use and in what order when trying to find a calendar user account.
Accepted values: A comma delimited list of search methods enclosed in curly braces. The currently recognized search methods are: X400, USERID, EMAIL.
Default values: At installation, if e-mail is mapped to user ID then the default value is set to {USERID, X400}. Otherwise there is no default set.
Redirecting Web Conferencing URLs
Parameter: baseurl_join
Section: [CONFERENCING]
Description: Specifies the base URL to use to replace the base URL of the join URL provided by Web Conferencing when a meeting is created.
|
See Also: [CONFERENCING]url in the Oracle Calendar Reference Manual |
Accepted values: A base URL of the following format:
HTTP or HTTPSHTTP://localhost:80/ HTTPS://myhost.com:7815/
Default value: None
Disabling Web Conferencing Notification
Parameter: disablenotification
Section: [CONFERENCING]
Description: Specifies whether or not Web Conferencing sends e-mail notifications of changes made to meetings by Calendar client applications. This parameter applies to Oracle Connector for Outlook only.
Accepted values:
TRUE (Disables notification)
FALSE (Enables notification)
Default value: FALSE
Specifying the Directory Server Connection Model
Parameter: dir_connectmodel
Section: [DAS]
Description: Specifies the directory server connection model. In the persistent connection model, the directory server connection is established at startup and terminated at shutdown. In the on-demand connection model, the directory server connection is established for a transaction that requires directory access and is terminated at the end of the transaction.
Accepted values:
persistent
ondemand
Default value: persistent
Enabling Access to LDAP Directories
Parameter: dir_enableldappersonsearch
Section: [ENG]
Description: Enables or disables access to non-calendar users stored in an LDAP directory. To minimize the number of hits to the LDAP directory server in environments where all the LDAP users are provisioned for Oracle Calendar, set this parameter to FALSE. When this parameter is set to FALSE, the attribute "gal-enabledapsearch" in [ENG] is implicitly set to FALSE as well.
Accepted values
TRUE (Enables access to the LDAP directory)
FALSE (Disables access to the LDAP directory)
Default value: TRUE
Limiting the Number of Meeting Attendees
Parameter: maxattendees
Section: [ENG]
Description: Specifies the maximum number of attendees an event can have. This parameter does not apply to holidays, the unimvuser utility, or replication.
A value of 0 indicates that no limit should be enforced by the server.
Accepted values: Any positive integer or 0.
Default value: 5000
Setting Time Limits for Oracle Calendar Application System Sessions
Parameter: ocas_sessionexpiry
Section: [ENG]
Description: Specifies the amount of time, in minutes, before the connection between Oracle Calendar Application System and Oracle Calendar server is terminated. The actual expiry is set within plus or minus 30% of this value. This implies that, with a default setting of 2160 minutes (36 hours), the actual expiry will be within 1 or 2 days of the connection being established. A value of 0 indicates that no limit should be enforced by the server.
|
Note: Client applications are not affected by this connection loss. |
Accepted values: Any positive integer or 0.
Default value: 2160 (36 hours)
Specifying the LDAP Attribute for Assistant Phone Number
Parameter: attr_assistantphone
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the ASSISTANT-PHONE attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: None
Specifying the LDAP Attribute for Alias
Parameter: attr_alias
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the ALIAS attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: uid
Specifying the LDAP Attribute for Assistant Name
Parameter: attr_assistant
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the ASSISTANT attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: None
Specifying the LDAP Attribute for Department
Parameter: attr_department
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the DEPARTMENT attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: departmentnumber
Specifying the LDAP Attribute for Display Name
Parameter: attr_displayname
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the DISPLAYNAME attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value:
displayname (for Oracle Internet Directory)
" " (for LDAP directory servers)
Specifying the LDAP Attribute for Alternate Home Phone Number
Parameter: attr_homephone2
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the HOMEPHONE2 attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: None
Specifying the LDAP Attribute for Manager
Parameter: attr_managerdn
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for a user's managerdn attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value:
manager (for Oracle Internet Directory)
" " (for LDAP directory servers)
Specifying the LDAP Attribute for Notes
Parameter: attr_notes
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the notes attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: None
Specifying the LDAP Attribute for Business Address: Street
Parameter: attr_officeaddress
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the OFFICE-ADDRESS attribute (street name and address).
|
See Also:
|
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: street
Specifying the LDAP Attribute for Business Address: City
Parameter: attr_officecity
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the OFFICE-CITY attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: l (lowercase L)
Specifying the LDAP Attribute for Business Address: Building
Parameter: attr_officename
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the OFFICE-BUILDING attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: physicalDeliveryOfficeName
Specifying the LDAP Attribute for Business Address: Postal Code
Parameter: attr_officepostalcode
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the OFFICE-POSTALCODE attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: postalcode
Specifying the LDAP Attribute for Business Address: State
Parameter: attr_officestate
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the OFFICE-STATE attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: st
Specifying the LDAP Attribute for Pager
Parameter: attr_pager
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the PAGER attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: pager
Specifying the LDAP Attribute for Alternate Business Phone
Parameter: attr_phone2
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the secondary business telephone number "PHONE2" attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: None
This section contains a list of updated parameters and their descriptions.
Table 5-2 Parameters updated in release 9.0.4.2
| Section | Parameter | Description | Changes made |
|---|---|---|---|
[CWS] |
mailhdrtoname |
Enabling Name Display in E-Mail Headers |
The description has been modified. |
noreqsleep |
Setting CWS Waiting Time |
The description has been modified. | |
noreqsleep_replication |
Setting CWS Waiting Time for Replication Requests |
The description has been modified. | |
smsnotifymsgfile |
N/A | This parameter has been obsoleted. | |
[DAS] |
dir_connection |
N/A | This parameter has been obsoleted. |
[DB] |
db_pages |
Specifying the Number of Pages for the Database Cache |
The default value has been changed from 8 to 24. |
[ENCRYPTION] |
default |
Specifying the Default Encryption Method |
The default value has been changed from none to cs-light. |
[ENG] |
allowresourceconflict |
Allowing Resource Conflicts |
The description has been modified. |
gal_refreshinterval |
Refreshing the Global Address List |
The default value has been changed from 7200 to 21600. | |
itemextinfomaxsize |
Storing Web Client Preferences |
This parameter is now published. | |
sss_cachesize |
Specifying the Size of the Server-Side Security Records Cache |
The default value has been changed from 101 to maxsession * 100. |
|
sss_cacheexpiredelay |
N/A | This parameter has been renamed to sss_expiredelay. |
|
sss_expiredelay |
Specifying the Expiry Delay for the Server-Side Security Records Cache |
This parameter has been renamed from sss_cacheexpiredelay. |
|
[LDAP] |
attr_address |
Specifying the LDAP Attribute for User Address |
The description has been modified. |
attr_employeeid |
Specifying the LDAP Attribute for Employee ID |
The default value has been changed from None to +++. |
|
attr_fax |
Specifying the LDAP Attribute for Fax Number |
This parameter is now published. | |
attr_homephone |
Specifying the LDAP Attribute for Home Phone Number |
This parameter is now published. | |
attr_initials |
Specifying the LDAP Attribute for User Initials |
The default value has been changed from initials to middlename. |
|
attr_jobtitle |
Specifying the LDAP Attribute for Job Title |
This parameter is now published. | |
attr_orgunit1 |
Specifying the LDAP Attribute for Organizational Unit |
This parameter is now published. | |
attr_phone |
Specifying the LDAP Attribute for Business Phone Number |
This parameter is now published. | |
attr_timezone |
Specifying the LDAP Attribute for Time Zone |
This parameter is now published. | |
usealtexclusionfilter |
N/A | This parameter has been obsoleted. | |
LIMITS |
autocontrol |
Specifying the Minimum Interval for Checks for New Agenda Entries |
There was an error in the documentation of this parameter. |
resourceconflicts |
Allowing Resource Double-Booking |
The description has been modified. | |
userlist_login |
Enabling Browsing at Login |
The default value was changed from TRUE to FALSE. |
|
UTL |
ca_maxsearchresult |
Limiting the Number of Search Results |
The default value has been changed from 100 to 200. |
Enabling Name Display in E-Mail Headers
Parameter: mailhdrtoname
Section: [CWS]
Description: Determines whether or not to include names along with addresses in the e-mail address fields ("From:", "To:" and "Reply-To") of the mail header. While addresses are constructed using ASCII characters (and hence present no display problem for mail readers), names may contain non-ASCII characters. In cases where the mail reader is unable to display the non-ASCII characters properly, remove the names from the address field altogether.
Accepted values:
TRUE (Include names)
FALSE (Do not include names)
Default value: TRUE
Setting CWS Waiting Time
Parameter: noreqsleep
Section: [CWS]
Description: Specifies the number of seconds the Corporate-Wide Services daemon/service waits (sleeps) when there is no work to do. This setting affects how often certain operations, such as server-side reminders and replication, are done. A low value may slow down the uniengd but reduces any delays in processing reminders and Web conferencing replication requests.
If no replication requests remain in the CWS replication queue, the number of seconds to wait before checking for new replication requests will be the greater of noreqsleep and noreqsleep_replication.
Accepted values: A positive integer
Default value: 15
Setting CWS Waiting Time for Replication Requests
Parameter: noreqsleep_replication
Section: [CWS]
Description: Specifies the number of seconds the Corporate-Wide Services daemon/service waits (sleeps) when there are no replication requests in the queue. This setting affects how often certain operations, such as remote user replication, are done. A low value may slow down the uniengd but reduces any delays in processing reminders and Web conferencing replication requests.
If no replication requests remain in the CWS replication queue, the number of seconds to wait before checking for new replication requests will be the greater of noreqsleep and noreqsleep_replication.
Accepted values: A positive integer
Default value: 15
Specifying the Number of Pages for the Database Cache
Parameter: db_pages
Section: [DB]
Description: Specifies the number of pages for the database cache. The greater the value, the greater the amount of memory used and the better the performance. As the number increases beyond a certain point, the returns on performance enhancement diminish.
Accepted values: A positive integer
Default value: 24
Specifying the Default Encryption Method
Parameter: default
Section: [ENCRYPTION]
Description: Specifies the default encryption method the calendar server uses for clients.
Accepted values: Any method in the list specified by the [ENCRYPTION] supported parameter.
Default value: cs-light
Allowing Resource Conflicts
Parameter: allowresourceconflict
Section: [ENG]
Description: Specifies whether the server allows double-booking of resources. This parameter should always be set with the same value as the [LIMITS] resourceconflicts parameter.
If this parameter is set to FALSE, each resource either allows or disallows conflicts based on its ALLOW-CONFLICT attribute. If the ALLOW-CONFLICT attribute is set to FALSE, no conflict will be allowed.
If this parameter is set to TRUE, the server allows all resources to be double-booked. In this case, the ALLOW-CONFLICT resource attribute is ignored.
Accepted values:
TRUE (Allow double-bookings)
FALSE (Do not allow double-bookings)
Default value : FALSE
Refreshing the Global Address List
Parameter: gal_refreshinterval
Section: [ENG]
Description: Specifies the time interval in seconds between each refresh of the Global Address List (GAL). Searches for entries in the GAL are a drain on performance and frequently done. To improve performance, the search results are cached and reused by the server.
To make sure that the cache is updated, the CWS periodically (see [CWS] galsyncinterval) sends requests to the server to update the result set. The result set is only rebuilt if it was invalidated (if, for example, a new node was added to the network) or if the current revision is older than the value of the parameter gal_refreshinterval. The parameter [CWS] galsyncinterval is used to configure the interval between each refresh.
Accepted values: A positive integer
Default value: 21600 (6 hours)
Storing Web Client Preferences
Parameter: itemextinfomaxsize
Section: [ENG]
Description: Specifies the maximum length of the itemextinfo attribute used by the Web client to store calendar account preferences.
Accepted values: A positive integer larger than 1500
Default value: None
Specifying the Size of the Server-Side Security Records Cache
Parameter: sss_cachesize
Section: [ENG]
Description: Specifies the number of read access record entries in the cache. The server uses these records to determine whether a user has the right to read calendar data he does not own. This cache is used to speed up reading the security access records by the server for handling the server-side security. There is one cache for each user session.
|
See Also: [ENG] sss_expiredelay in Specifying the Expiry Delay for the Server-Side Security Records Cache |
Accepted values:
0 (Disables the cache)
A positive integer less than 1000003
Default value: maxsession * 100
Specifying the Expiry Delay for the Server-Side Security Records Cache
Parameter: sss_expiredelay
Section: [ENG]
Description: Specifies the number of seconds an entry is kept in the cache before it expires.
Accepted values: A positive integer
Default value: 900
Specifying the LDAP Attribute for User Address
Parameter: attr_address
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the calendar user address attribute LOC.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value:
postalAddress (for Oracle Calendar standalone)
homePostalAddress (for Oracle Collaboration Suite)
Specifying the LDAP Attribute for Employee ID
Parameter: attr_employeeid
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the "EMPL-ID" attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: employeenumber
Specifying the LDAP Attribute for Fax Number
Parameter: attr_fax
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the FAX attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: facsimileTelephoneNumber
Specifying the LDAP Attribute for Home Phone Number
Parameter: attr_homephone
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the HOMEPHONE attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: None
Specifying the LDAP Attribute for User Initials
Parameter: attr_initials
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the initials "I" attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: middlename
Specifying the LDAP Attribute for Job Title
Parameter: attr_jobtitle
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the job title "jt" attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: None
Specifying the LDAP Attribute for Organizational Unit
Parameter: attr_orgunit1
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the OU1 attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: ou
Specifying the LDAP Attribute for Business Phone Number
Parameter: attr_phone
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the business telephone number "PHONE" attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: phone
Specifying the LDAP Attribute for Time Zone
Parameter: attr_timezone
Section: [LDAP]
Description: Specifies the attribute name that the LDAP directory server uses for the time zone attribute.
Accepted values: Any attribute name defined in the LDAP directory server schema. If "" is used, this attribute will not be read nor written.
Default value: None
Specifying the Minimum Interval for Checks for New Agenda Entries
Parameter: autocontrol
Section: [LIMITS]
Description: Specifies the minimum number of minutes that a user can set as the interval between agenda refresh calls to the server (that is, between each check for new agenda entries).
If this value is less than [ENG]maxsessions/60, the value of [ENG]maxsessions/60 takes precedence, to a maximum value of 45. For example, if autocontrol = 15 and [ENG]maxsessions = 1200, no refresh occurs before 20 (that is, 1200/60) minutes has elapsed.
|
See Also: [ENG]maxsessions, [CLIENT]minrefreshrate in the Oracle Calendar Reference Manual |
Accepted values: Any positive integer up to the value of (216-1)
Default value: 15
Allowing Resource Double-Booking
Parameter: resourceconflicts
Section: [LIMITS]
Description: Specifies whether the client allows users to double-book resources. In release 5.4 and older where resource conflicts is a server wide setting, this parameter should always be set with the same value as the [ENG] allowresourceconflict parameter. This applies to the Oracle Calendar Desktop clients and the Oracle Calendar Web client.
If a per-resource conflict option is required and older clients are in use, set this parameter to TRUE so that the clients allow the double-booking but the server blocks it if the resource does not allow conflicts. This allows for per-resource configuration, however, the older clients may not gracefully handle the errors returned by the server enforcement.
Accepted values:
TRUE (Allow double-bookings)
FALSE (Do not allow double-bookings)
Default value: TRUE
Enabling Browsing at Login
Parameter: userlist_login
Section: [LIMITS]
Description: Specifies whether or not to show a list of matching users when more than one fits the specified sign-in credentials.
Accepted values:
TRUE (Displays the list of matching users)
FALSE (Do not display the list)
Default value: FALSE
Limiting the Number of Search Results
Parameter: ca_maxsearchresult
Section: [UTL]
Description: Specifies the maximum number of entries (users, resources and event calendars) that the LDAP directory will return to the Calendar Administrator that made a search request. This parameter applies only to the Calendar Administrator.
This parameter can be set to a higher value than the [LIMITS] maxsearchresult parameter because much fewer users will be using the Calendar Administrator.
|
See Also: [LIMITS] maxsearchresult in the Oracle Calendar Reference Manual |
Accepted values: Any positive integer up to the value of (232-1)
Default value: 200 (List only 200 entries at a time)
This section includes the following topics:
Oracle Webmail Spell Checker
A spell checker has been added to the Oracle Webmail client. The spell checker offers standard spell checking features for composing new e-mail messages, and is available on the e-mail message composition page. It currently supports spell checking for the following languages:
Brazilian Portuguese
Danish
Dutch
English
Finnish
French
German
Italian
Norwegian
Portuguese
Spanish
Swedish
New Shared Folder Listing Behavior
By default, shared folders are not displayed in the Folder drop-down boxes
Shared folders become available when the user explicitly selects the Shared tab of the All Folders list
New Oracle Email Migration Tool Features
The Oracle Email Migration Tool is certified to run with Microsoft Exchange 2000 server and the Microsoft Outlook 2000 client.
|
Note: When using the Microsoft Exchange 2000 plug-in, ensure that the name of the Exchange MAPI profile provided in the plug-in configuration file (esmigration.config) is the same as the username of the mailbox with Active Directory and Exchange server administration permissions that is entered in the Migration Wizard screens. For example, if the e-mail address of the administrator is admin@example.com, the MAPI profile used for migration must be named admin. |
The following new features for Oracle Files are included in this patch set:
Using Oracle Files with an Upgraded Oracle Database 10g
This section discusses upgrading your information storage database to Oracle Database 10g and post-upgrade steps pertaining to existing installations of Oracle Files.
Upgrading the Information Storage Database to Oracle Database 10g
Upgrade the information storage database, as follows:
Stop all Oracle Files processes on all the middle tiers.
Upgrade the information storage database to Oracle Database 10g.
Install the Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.1) to all the middle tiers and the infrastructure, as described in Chapter 2, "Installing the Patch Set".
|
Note: There is no need to apply the patchset on the information storage database since you have upgraded it to Oracle Database 10g. |
Perform the Oracle Files postinstallation tasks as specified in Section 3.5.
|
Note: Steps 5 and 6 in the following procedure require atnsnames entry in tnsnames.ora. |
From the Oracle Files middle tier computer, connect to Oracle Database 10g as the user who owns the Oracle Files schema (for example, IFSSYS) and execute the following commands:
cd %ORACLE_HOME%\ifs\files\admin\sql sqlplus files_schema/schema_password@tnsnames_entry @Upgrade9iTo10g_part1.sql files_schema
Connect to Oracle Database 10g as the SYS user and execute the following commands:
sqlplus 'sys/sys_password@tnsnames_entry as sysdba' @Upgrade9iTo10g_part2.sql files_schema
Restart all necessary Oracle Files processes.
Using Oracle Files with a New Oracle 10g Database
Follow these steps if you have a new Oracle Files installation and you want to use Oracle Database 10g for your information storage database:
Install Oracle Database 10g from the Oracle Database 10g CD pack.
Ensure that the following database parameters are set on the computer on which the Oracle Database 10g server is installed:
Table 5-3 Required Database Parameters
| Parameter Name | Minimum Value |
|---|---|
aq_tm_processes |
1 |
java_pool_size |
30 MB |
job_queue_processes |
10 |
open_cursors |
300 |
processes |
100 |
session_max_open_files |
50 |
shared_pool_size |
50 MB (52428800 bytes) |
The values listed in Table 5-3 are minimum values for these parameters. You may want to increase these values as appropriate for your deployment.
On the computer on which the Oracle Database 10g server is installed, restart the database and the database listener.
Install the Oracle Collaboration Suite Release 9.0.4.1.1 middle tier.
Do not select the Oracle Files components for configuration during installation of the middle tier.
If the Oracle Files configuration assistant appears, click Cancel.
Apply Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.1).
Configure Oracle Files by executing ifsca from the following location:
%ORACLE_HOME%\ifs\files\bin
For configuration instructions, see the Oracle Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1.1).
Enhancements to User Lookup
The User Lookup feature has been enhanced to allow searching for users by User ID, First Name, Last Name, or Email Address. Previously, only searching by User ID was allowed.
Enable/Disable Workspace Creation Feature
New for this release, the Subscriber Administrator can enable or disable workspace creation for the users in their Subscriber. If workspace creation is enabled, users in the Subscriber can create their own workspaces. If workspace creation is disabled, users in the Subscriber cannot create their own workspaces, and only the Subscriber Administrator can create workspaces. Users may, however, still request to join existing listed workspaces.
|
See Also: "Default Workspace Creation Settings" in the Oracle Files Subscriber Administrator help for information about how to use this feature |
OmniPortlet Support
New for this release, Oracle Files provides support for and integration with the OmniPortlet, a feature of Oracle Application Server Portal (OracleAS Portal).
The following sections provide instructions on how to set up Oracle Files for the OmniPortlet:
"Installing Oracle Application Server Portal Developer Kit (OracleAS PDK)"
"Registering the Files Searchlet in the OmniPortlet Framework"
Installing Oracle Application Server Portal Developer Kit (OracleAS PDK)
You can install OracleAS PDK on the Oracle Files middle tier computer, or on another computer. For information about system requirements, see the OracleAS PDK 9.0.4.0.2 Release Notes, available from
http://portalstudio.oracle.com
To install and configure OracleAS PDK, follow these steps:
Create a directory (for example, OracleAS_PDK) where you want to install OracleAS PDK.
From a Web browser, access http://portalstudio.oracle.com.
Download OracleAS PDK Release 9.0.4.0.2 to the directory you created in Step 1, by choosing the Download pre-configured standalone OC4J with PDK install option from the PDK Downloads page.
Unzip the downloaded files to install the Oracle Application Server Portal Developer Kit.
|
See Also: http://updates.oracle.com/unzips/unzips.html for information about obtaining the UnZip utility |
Download and install JDK 1.4.1 on this computer, if it is not there already. OracleAS PDK requires JDK 1.4.1.
Set the JAVA_HOME environment variable to point to JDK 1.4.1.
Add the JAVA_HOME\bin directory to the PATH environment variable.
Deploying the Files Searchlet
This section describes how to deploy the Files Searchlet. In the following instructions, oc4j_home refers to unzipped_directory\j2ee\home; for example, OracleAS_PDK\j2ee\home.
To deploy the Files Searchlet:
Create a directory called FilesSearchlet under the following directory:
oc4j_home\connectors
Copy the file files_searchlet.rar into the FilesSearchlet directory you just created. The files_searchlet.rar file is located on the Oracle Files middle-tier computer in the following directory:
%ORACLE_HOME%\ifs\files\lib
Navigate to the oc4j_home\config directory and open the file oc4j-connectors.xml for editing.
Add a <connector> tag for the Files Searchlet by adding the following lines to the <OC4J-connectors> section:
<connector name="FilesSearchlet" path="files_searchlet.rar"> </connector>
The relevant portion of the edited file should look like the following:
<oc4j-connectors> <connector name="FilesSearchlet" path="files_searchlet.rar"> </connector> </oc4j-connectors>
Save the file.
Start the OC4J instance using the startup script located in unzipped_directory\bin; for example, OracleAS_PDK\bin:
cd unzipped_directory\bin
startup
The files_searchlet.rar file is expanded under the directory oc4j_home\connectors\FilesSearchlet.
Configuring the Files Searchlet
This section describes how to configure the Files Searchlet. In the following instructions, oc4j_home refers to unzipped_directory\j2ee\home; for example, OracleAS_PDK\j2ee\home.
To configure the Files Searchlet:
Navigate to the oc4j_home\application-deployments\default\FilesSearchlet directory.
Open the oc4j-ra.xml file for editing.
Specify the JNDI name for the Files Searchlet by setting the location in the <connector-factory> tag, as follows:
<connector-factory location="eis\FilesSearchlet" connector-name="Files Search Adapter">
Set the value for the Search Web Service URL, as follows:
<config-property name="webServiceURL" value="http://files_host_ name:port/files/SearchServer"/>
For example:
<config-property name="webServiceURL" value="http://myhost.mycompany. com:7777/files/SearchServer"/>
Create a Search Web Service user, password, and realm, as follows:
<config-property name="SearchUser" value="user_name"/> <config-property name="SearchUserPassword" value="password"/> <config-property name="SearchUserRealm" value="files"/>
You must provide a value for password. Do not specify an empty string.
Note the values you provided for user_name and password. You will need these values when you follow the instructions for configuring the Search Web Service user in "Configuring and Verifying the Search Web Service User".
Save the file.
To verify that files is the correct value for the realm, use a Web browser to access the Search Web Service URL:
http://files_host_name:port/files/SearchServer
For example:
http://myhost.mycompany.com:7777/files/SearchServer
If the Files Searchlet is configured correctly, the realm value displayed in the basic authentication dialog box should be files. Cancel the authentication dialog after verifying the realm.
Shut down and restart the OC4J instance using the shutdown and startup scripts located unzipped_directory/bin; for example, OracleAS_PDK/bin:
cd unzipped_directory/bin
shutdown.bat
startup.bat
|
Note: Due to a known issue in OracleAS PDK, it generates an error message when stopped. Disregard the error message and continue with the configuration process. |
Registering the Files Searchlet in the OmniPortlet Framework
This section describes how to register the Files Searchlet in the OmniPortlet framework. In the following instructions, oc4j_home refers to unzipped_directory\j2ee\home; for example, OracleAS_PDK\j2ee \home.
To register the Files Searchlet:
Create a directory called Files under the following directory:
oc4j_home\applications\portalTools\omniPortlet\WEB-INF\plugins
\datasources
Navigate to the new folder.
Create a Datasource Descriptor file (datasource.xml) with the following content:
|
Note: If you cut and paste the text directly from this document, remove the extra carriage return and any extra spaces betweenoracle.webdb.reformlet.data.search and .SearchDataSourceDefinition. Otherwise, the Datasource Descriptor file will not work. |
<datasources> <datasource class="oracle.webdb.reformlet.api.plugin.DefaultDataSource"> <name>Files</name> <displayName>Files</displayName> <icon>webpage.gif</icon> <metadata class="oracle.webdb.reformlet.data.search .SearchDataSourceDefinition"> <name>Files</name> <displayName>Files</displayName> <contentDataSourceJndiName>eis/FilesSearchlet</contentDataSourceJndiName> </metadata> </datasource> </datasources>
Shut down and restart the OC4J instance using the shutdown and startup scripts located unzipped_directory\bin; for example, OracleAS_PDK\bin:
cd unzipped_directory/bin
shutdown.bat
startup.bat
Configuring and Verifying the Search Web Service User
The Search Web Service requires that a Search Web Service user be defined in OC4J. The Search Web Service user is used only to control access to the Search Web Service and is separate from other Oracle Files users.
The Files Searchlet needs to be configured with the Search Web Service user name and password in order to access the Search Web Service.
To configure the Search Web Service user:
Using a Web browser, access the Oracle Enterprise Manager Web site at http://host_name:port, where host_name is the name of the Oracle Files middle-tier computer. The port is typically 1810.
Enter the authentication information in the pop-up window. The user name is typically ias_admin.
Click the name of the application server instance where Oracle Files is running. The Oracle Application Server 10g (9.0.4) home page appears.
Click the name of the Oracle Files OC4J instance (OC4J_iFS_files).
Click the files link in the Application list.
Click the Security link in the Security section.
Click Add User.
Provide information for the Search Web Service user. Make sure to use the same user name and password you provided in the oc4j-ra.xml file in "Configuring the Files Searchlet".
Click OK on the Add User page.
In the Security Roles section, select the SearchServerRole.
Click Map Role to Principals.
In the Map Role to User section, select the new user you just added and click Apply.
Click OK on the Confirmation page.
Return to the Oracle Application Server 10g (9.0.4) home page.
Select OC4J_iFS_files and click Restart.
To make sure that the user was configured properly, access the Search Web Service URL using a Web browser:
http://files_host_name:port/files/SearchServer
For example:
http://myhost.mycompany.com:7777/files/SearchServer
In the login dialog, enter the Search Web Service user name and password.
If the Search Web Service user has been configured properly, the SearchServer responds with the following:
SearchServer Web Service Sorry, I don't speak via HTTP GET - you have to use HTTP POST to talk to me. Servlet Path: /SearchServer QueryString Info: null
Registering and Configuring the OmniPortlet
You must register and configure the OmniPortlet in OracleAS Portal. The registration steps may vary slightly, depending on which version of OracleAS Portal you are using.
|
Note: The version of Portal that was shipped with Oracle Collaboration Suite Release 2 is known as Oracle9iAS Portal. |
To register the OmniPortlet:
Using a Web browser, access OracleAS Portal at http://host_name:port/pls/portal, where host_name is the name of the middle-tier computer where OracleAS Portal resides.
Click Login. The Single Sign-On page appears.
Provide the credentials of an OracleAS Portal user with administrative permissions and click Login.
Click the Builder icon.
In the Providers portlet, click Register a Portlet Provider. The Registration Wizard appears.
By default, the Providers portlet should appear on this page. If it is not visible, choose Customize, then click the Add Portlets icon in order to add the portlet. The Providers portlet can be found under the Administration Portlets link.
In the Providers portlet, click Register a Portlet Provider. The Registration Wizard appears.
On the Register Provider page, enter the following values and click Next.
Name: OmniPortlet
Display Name: OmniPortlet Provider
Timeout: 200 seconds
Timeout Message: OmniPortlet provider timed out.
Implementation Style: Web
On the Define Connection page, provide the following values and click Next.
URL: http://server_name:port/portalTools/omniPortlet/providers/omniPortlet
Where server_name is the name of the machine where OracleAS PDK is installed. The value for port is typically 8888.
Select The user has the same identity in the Web providers application as in the Single Sign-On identity
Under User/Session Information, select User
For Login Frequency, select Never
If no proxy is required to contact the Provider Adapter, select No for Require Proxy
You can leave the other options blank.
On the Control Access page, add any users or groups to whom you want to give access.
This option may not appear, depending on which version of OracleAS Portal you are using. By default, only the user who registered the provider is authorized to see the provider and its portlets. After you register the portlet, navigate to the provider within the Portlet Repository to update provider privileges.
Click Finish.
After you have registered the OmniPortlet, you must configure it by choosing search criteria and deciding which fields to display.
To configure the OmniPortlet:
Create a page in OracleAS Portal. To do this, click Create Page from the OracleAS Portal home page and follow the Wizard instructions.
From your new page, click the Add Portlet icon and navigate to the OmniPortlet you registered. Then, select the portlet and click OK.
Click Define. The Type page appears.
Select Files and click Next.
On the Source page, click Next.
On the Filter page, provide search criteria for the OmniPortlet.
On the View page, click Next.
On the Layout page, enter the fields you want the OmniPortlet to return.
|
Note: If you select Size as one of the columns, the search will only return documents. Folders will not be returned. |
Click Finish.
Be aware of the following two issues when using the OmniPortlet:
If your OracleAS Portal instance uses a different Oracle Internet Directory than Oracle Files, you may experience authentication issues. To avoid these problems, ensure that the user information between the two Oracle Internet Directory instances is kept in sync.
When you click a folder link within the OmniPortlet, you may be asked to re-authenticate. This behavior does not appear if you click a document link.
The following new features have been added to Oracle Voicemail & Fax:
Oracle Voicemail & Fax Playback Controls
The following default playback controls have been added to Oracle Voicemail & Fax, accessible using the telephone keypad while listening to voice mail messages:
1: Increase playback volume
2: Increase message playback speed
3: Skip ahead 5 seconds
4: Decrease playback volume
5: Decrease message playback speed
6: Jump back 5 seconds
7: Delete message
8: Pause playback
9: Skip to end of message
0: Resume playback
Additional Language Support
Support for the following languages has been added to Oracle Voicemail & Fax:
The following new features for Oracle Web Conferencing are included in this release:
Web Conferencing Application
Users can now manually download the Web console tool from the New User page. The console window does not require the user to have administrator rights to his system in order to run a conference.
The Web conferencing system can handle numerous users simultaneously entering a conference; if the system receives more requests than it can handle, a message will let the user know how many seconds it will take before he enters the conference
System administrators can now customize several features of the Web conferencing interface for their company or for particular Web conferencing sites within their company. Administrators can:
Change the introductory text on the Welcome page that appears as users log in to Oracle Web Conferencing
Add to the Quick Links that appear on the Oracle Web Conferencing home page both before and after a user logs in
Add up to five custom fields to the Conference Details dialog that appears as users join a conference at a particular site
System administrators can now control system- and site-level conference properties. Administrators can:
Set the available conference modes (Cobrowse, Desktop Sharing, Whiteboard, or Document Presentation)
Set the default conference mode
Set the ability to make a conference public
Require a conference to use SSL security levels (when SSL security has been set off by default)
Set the ability to use Chat or Shared Control within a conference
New recordings showing how to use Web conferencing are available from the Quick Links area
When a user chooses Test from the New User pages, the diagnostics now analyze complete system compatibility, the ability to install the Web conferencing console, and the connection to the Oracle Web Conferencing server
Users can now delete or update details of conferences they have scheduled, using the new Update and Delete icons on the conference listing
Web Conferencing Console
The flow of events as users start a conference has been enhanced to be more user-friendly, especially for new hosts. As a host enters a conference, a conference details page appears confirming conference details such as the conference ID and any dial-in numbers. The console is now loaded with both of the upper toolbars and the tip text visible by default. The default mode is now set to desktop sharing, so a host automatically shares his desktop at the beginning of a conference.
The host can invite an attendee to present content from his desktop.
Users running Netscape 4.75 and above may now join conferences and start instant conferences from the Oracle Web Conferencing main page. You must have Java enabled (from the Edit menu, select Preferences, then select Advanced) to join and start conferences with Netscape. You must use Internet Explorer 5.5, or above, to use the Cobrowse, Document Presentation, and Voice conference features, to host a scheduled conference, or to use other features from the Oracle Web Conferencing main page, such as the Materials and Archives tabs.
When the host sets View attendee list off in Preferences, the alert windows that normally appear as attendees enter a conference are now suppressed
System administrators can restrict the ability to record voice data during a conference at both system and site levels
Oracle Web Conferencing System Services
Under the System tab, system administrators can now see a hierarchical view of all of the Oracle Web Conferencing components, and expand or collapse the details displayed about each component. For example, an administrator can display details about a particular Oracle Web Conferencing instance, such as what properties are set for it or what conferences are running on it. If any component is down, the hierarchical view is automatically expanded to display the faulty component. Each component's availability is shown with a status icon (for example, a green check appears when a component is available).
From the Reports tab, the Diagnostics link on each Conference Detail page now shows events and error incidents. Administrators can view all events or only errors, and can view events and errors by attendee or by type of event (event description).
The Attendees table under Reports now shows additional details for attendees that were previously available only in log files
Host rating and conference status columns can now be used to sort reports under the Reports tab
User information in the Oracle Internet Directory can be uploaded in bulk to the Oracle Web Conferencing system
User information in the Oracle Web Conferencing system is automatically synchronized with Oracle Internet Directory
Oracle Web Conferencing Integration Services
A new API lets you add Live Help links to any Web page, to start a Web conference for use in providing real-time help to customers for any application
New APIs let you access detailed conference information and attendee lists so you can include this data in reports and Web pages
New APIs let you display the lists of upcoming conferences and public conferences in any Web page
E-mail invitations for conferences scheduled through an integrated application will display the conference time in the conference host's preferred time zone
Over the Air Device Provisioning (OTA)
OTA is a newly supported feature in this patch set. It can be enabled or disabled by editing the system.properties file. By default, the feature is disabled.
Enable OTA and configure the required carrier and device information, as follows:
Use a text editor to modify the system.properties file located in the %ORACLE_HOME%\wireless\server\classes\oracle\panama\core \admin directory. Set the value of useOTA to true.
Modify the carriers.xml and devices.xml files located in the %ORACLE_HOME%\j2ee\OC4J_Portal\applications\marconi \marconi-web\WEB-INF directory to configure the information for carriers and devices according to the examples contained in each xml file.
Modify the default values for the following settings in the owi.properties file:
bookmarks MMSC email syncML WAP
|
Note: Thebookmarks setting has two default values: Google and Yahoo!. For OTA provisioning, you must change both the bookmarks setting name and URL values to those for Oracle Collaboration Suite.
If you want only one bookmark, you must comment out both the Online Help for the OTA feature is not included in this release; it will be included in the next release. |
Restart the middle tier to apply the changes.
