Oracle® Collaboration Suite Release Notes Release 2 (9.0.4) for AIX Based Systems Part Number B12116-01 |
|
|
View PDF |
This chapter provides information about issues associated with Oracle Files. It contains the following sections:
The following features are new for Oracle Files Release 2 (9.0.4.1).
Oracle Files comes with a default workflow process. Additionally, with this release you can now define a custom workflow process in Oracle Workflow, then register it with Oracle Files. You can design and register any number of custom workflow processes.
For information on how to design and register custom workflows for use in Oracle Files, see the Oracle Files Administrator's Guide, Chapter 7, "Customizing Oracle Files."
Some organizations have "look and feel" standards, such as the requirement to use a particular company logo or color scheme. You can customize the Oracle Files Web User Interface to match those standards.
You can make the following customizations to the Oracle Files Web UI:
For more information on custom branding, see the Oracle Files Administrator's Guide, Chapter 7, "Customizing Oracle Files."
The domain controller is an important component of the Oracle Files domain.
In Oracle Collaboration Suite Release 1, the domain could not be easily shut down, started, monitored, or configured in the following situations (although the domain would continue to run):
The first problem was due to the domain controller using a derived JDBC thin driver URL for communication between the domain controller and the database. To handle this problem, you can now specify a database URL in the registry.xml
file. This can then be used to specify a JDBC thick driver URL, which supports Transparent Application Failover (TAF).
To correct the second problem, you can migrate the domain controller to another middle-tier host. For more information on migrating the domain controller, see the Oracle Files Administrator's Guide, Chapter 5, "Administrative Operations in Oracle Enterprise Manager."
In Oracle Files Release 1 (9.0.3.1), users created in Oracle Internet Directory were automatically provisioned in Oracle Files every 24 hours. Shortening this interval required a series of manual steps.
For the current release, the interval has been reduced to 15 minutes. Additionally, users created in Oracle Internet Directory are automatically provisioned in Oracle Files when they log in to Oracle Files for the first time.
In Oracle Files 9.0.4.1, the default service configurations have been changed from allowing unlimited number of sessions to now specifying a maximum number of sessions which can connect to the service. This was done to reduce the likelihood of experiencing java.lang.
The OutOfMemory
errors in the oc4j_opmn.log
or application.log
.
After this change you might see the following errors:
oc4j_opmn.log
or application.log: "IFS-20127: Service too busy (maximum concurrent sessions)"If you see either of these errors, change the Service Configuration from Small to Medium or from Medium to Large, or create your own custom Service Configuration. If you use the Large Service Configuration, or if you make your own customer Service Configuration, you will also need to adjust your Xmx
setting.
If you see any java.lang.OutOfMemory
errors in your oc4j_opmn.log
or application.log files, then you also need to adjust your Xmx
setting.
See the following table for more information about why the Xmx
setting might need to be changed.
Service Configuration | Setting for IFS.SERVICE.Maximum |
Expected number of peak concurrent connected users (PCCUFoot 1) | Recommended size for Xmx (Java maximum memory) |
Need to change the default Xmx setting of 256MB? |
---|---|---|---|---|
Small |
40 |
25 |
64 MB |
No |
Medium |
70 |
45 |
162 MB |
No |
Large |
200 |
125 |
430 MB |
Yes |
See the Oracle Files Planning Guide and the Oracle Files Administrator's Guide for more information about sizing and performance tuning.
A general guideline for calculating the Xmx
setting is:
Xmx
= PCCU * 2.8MB
or more exactly,
Xmx
= (PCCU * 1.6 sessions per PCCU * 1MB per session) + (DATACACHE.Size * 3KB per data cache object).
Note that the Xmx
cannot exceed 4GB. Oracle recommends the Xmx
should not exceed 2GB for Oracle Files.
To change the Xmx
setting for an Oracle Files HTTP node:
$ORACLE_HOME/opmn/conf/opmn.xml
file.-Xmx256m
" to the appropriate value in the OC4J instance. Here is an example to change the java maximum heap size to be 430 MB of memory:
<oc4j instanceName="OC4J_iFS_files" gid="OC4J_iFS_files"> <config-file path="/private/9iASHome/j2ee/OC4J_iFS_files/config/server.xml"/> <java-option value="-Xmx430m"/> <oc4j-option value="-properties"/> <port ajp="3001-3100" rmi="3101-3200" jms="3201-3300"/> <environment> <prop name="LIBPATH" value="/private/9iASHome/lib32:/private/9iASHome/lib"/> <prop name="DISPLAY" value=":0.0"/> <prop name="NLS_LANG" value=".UTF8"/> <prop name="LD_LIBRARY_PATH" value="/private/9iASHome/lib32:/private/9iASHome/lib"/> <prop name="SHLIB_PATH" value="/private/9iASHome/lib32:/private/9iASHome/lib"/> </environment> </oc4j>
To change the Xmx
setting for an Oracle Files regular node:
http://myserver.mycompany.com:1810
ias_admin
user name and password.-Xmx
setting. For example, enter "-Xmx430m
" to specify 430 MB of memory for the Java heap.When your peak concurrent connected users (PCCU) exceeds 125, general guidelines for adjusting the IFS.SERVICE
settings in the Service Configurations are:
MaximumConcurrentSessions
= 1.6 * PCCU
DATACACHE.Size
= 400 * PCCU
DATACACHE.EmergencyTrigger
= 0.80 * DATACACHE.Size
DATACACHE.UrgentTrigger
= 0.75 * DATACACHE.Size
DATACACHE.NormalTrigger
= 0.65 * DATACACHE.Size
DATACACHE.PurgeTarget
= 0.55 * DATACACHE.Size
CONNECTIONPOOL.WRITEABLE.MaximumSize
= 0.05 * PCCU
CONNECTIONPOOL.WRITEABLE.TargetSize
= 0.04 * PCCU
CONNECTIONPOOL.WRITEABLE.MinimumSize
= 5
CONNECTIONPOOL.READONLY.MaximumSize
= 0.05 * PCCU
CONNECTIONPOOL.READONLY.TargetSize
= 0.04 * PCCU
CONNECTIONPOOL.READONLY.MinimumSize
= 5
The other settings in the Service Configuration do not generally need to be adjusted.
Oracle Files requires either the Oracle Collaboration Suite Release 2 Information Storage database or an external 9.2.0.3 version of the Oracle database. If you are using an external database, you should upgrade to the 9.2.0.3 release of the database if you have not done so already.
The following client software has been tested and certified for the various protocol servers offered by Oracle Files. Higher operating system and application service pack and minor version number releases are supported.
If a valid SMTP server is not specified during Oracle Files configuration, or a user has a null or invalid e-mail address, any Oracle Files operation that involves an e-mail notification will fail, including Workspace creation.
As the Subscriber Administrator's password is sent to the Subscriber Administrator by e-mail, the Subscriber Administrator will not be able to perform any administrative tasks if a valid SMTP server is not specified during configuration. For example, the Subscriber Administrator will not be able to manage users, quota, or categories, specify Subscriber settings, or restore files.
See bug 2520112 for more information about this issue.
If Oracle9iAS Web Cache is enabled, Netscape or Mozilla browsers might not be able to access Oracle Files. See bug 2960325 and bug 2615650 for information on how to resolve this issue.
In addition, using Oracle9iAS Web Cache to cache any content located under /files/content
is prevented due to a variety of security issues.
See the Oracle Internet Directory Release Notes for complete information on all known issues. This section covers only those issues specific to Oracle Files.
Sometimes, users created in Oracle Internet Directory fail to be provisioned in Oracle Files, or you might not be able to add newly provisioned users to Oracle Files Workspaces.
If these problems occur, they are likely due to a failure to set required user attributes in Oracle Internet Directory. The following Oracle Internet Directory user attributes must be non-null for all users:
The user name attribute is specified by the orclCommonNicknameAttribute
in the Subscriber's OracleContext. See the Oracle Internet Directory Administrator's Guide for more information on viewing the orclCommonNicknameAttribute
.
Here are some issues relevant to Oracle Files Globalization Support, formerly known as National Language Support (NLS).
When running in Japanese, Simplified Chinese, Traditional Chinese, and Korean environments, bold or italicized fonts in the Configuration Assistants appear jagged, and are difficult to read.
This issue is caused by problems in the 1.3.1_02b version of the JDK, and can be resolved by moving to JDK 1.3.1_04. This problem will be corrected in future releases of Oracle Files.
See bug 2377003 and base bug 2220343 for more information.
Oracle Files does not support AL32UTF-8 databases for Asian languages, because Oracle Text does not support Chinese, Japanese, and Korean lexers on AL32UTF-8 databases. On such databases, Chinese, Japanese, and Korean documents will not be indexed or searchable. UTF-8 is the recommended character set for Unicode-based file systems. See also bug 2391425.
This section covers issues relating to Oracle Files or Oracle Collaboration Suite documentation.
The Oracle Collaboration Suite Installation and Configuration Guide includes a section called "Making Oracle Files Searchable" on page 11-7. You do not need to perform the steps listed in this section because the Oracle Files Configuration Assistant sets up the job to perform indexing automatically.
The Oracle Files Administrator's Guide provides instructions on how to set up the Oracle Workflow Notification Mailer on page 7-10. These instructions apply only to administrators who are creating and registering custom workflows for use in Oracle Files.
Step 1 of these instructions asks administrators to make sure that UNIX Sendmail is configured on the middle-tier host where Oracle Workflow is installed. The following additional information is available to help administrators perform this step.
To determine if Sendmail is running:
$ ps -ef | grep sendmail
If Sendmail is running, it returns a valid Sendmail process.
To start Sendmail if it is not running:
To test if Sendmail is configured correctly:
telnet localhost 25 helo localhost mail from : <>
You must get a response of "Sender OK."
rcpt to : <email address of recipient>
You must get a response of "Recipient OK."
data subject : xxx yyy zzz . quit
The following bugs apply to this Oracle Files release. Workarounds are given when appropriate. The known bugs are grouped in tables by the following processes or components: