| Oracle Content Management SDK Release Notes 10g (9.0.4) Part Number B10691-01 |
|
10g (9.0.4) for Solaris Operating System (SPARC 32-bit and SPARC 64-bit)
November 2003
Part No. B10691-01
This document is accurate to the best of our knowledge at the time of publication. Information that is discovered subsequent to publication will be available through regular support channels. You can access the latest information and additions to Release Notes on the Oracle Technology Network at:
http://otn.oracle.com/
This document is specific to Oracle Content Management SDK 10g (9.0.4) for Solaris Operating System (SPARC 32-bit and SPARC 64-bit). It covers the following topics:
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle Corporation is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at:
http://www.oracle.com/accessibility/
Oracle Content Management SDK (Oracle CM SDK) is a robust development platform for building content management applications. It provides a set of Java APIs for versioning, check-in/check-out, security, searching, extensible metadata and other standard content management operations. Oracle CM SDK provides:
These features and capabilities are designed to help developers bring content management-based applications to market faster and better than with any other platform.
Prior to version 9.0.3, Oracle CM SDK was known as Oracle Internet File System (Oracle 9iFS).
A significant difference between Oracle CM SDK 10g (9.0.4) and earlier versions of the Oracle Internet File System (9.0.2 and before) is that the default Web user interface has been replaced with the Web Starter Application. For more information, see the ReadMe file included with the Web Starter Application sample code.
In addition, the Windows UI is not available in this release.
Before you upgrade from earlier versions of Oracle 9iFS (9.0.2 and earlier) to Oracle CM SDK 10g (9.0.4), be aware that if you are depending on features unavailable in 10g (9.0.4) (such as the Web UI or the Windows UI), you should not upgrade. Once you have upgraded the schema to Oracle CM SDK 10g (9.0.4), you cannot run components certified against Oracle 9iFS versions 9.0.2 and earlier.
Please note the following recommendations:
See the Oracle Content Management SDK Installation and Configuration Guide for detailed upgrade information.
Oracle Content Management SDK 10g (9.0.4) provides the following new features:
Oracle CM SDK provides a platform for building custom applications. To remain compatible with future releases of Oracle CM SDK, follow these guidelines:
Use Oracle9i Database Server release 9.0.1.4 or 9.2.0.3 (or later) as the database tier for Oracle CM SDK. Oracle CM SDK is certified with Oracle Workflow 2.6.2 and 2.6.3.
To find out which versions of Oracle Application Server, Infrastructure are certified, see the latest Oracle Application Server 10g certification information on OracleMetaLink at http://metalink.oracle.com.
The following client software has been tested and certified for Oracle CM SDK. Higher operating system and application service pack and minor version number releases are supported.
In some versions of the Internet Explorer browser or Windows 2000 operating system, the links in the Oracle CM SDK Javadoc do not work. To avoid this problem, do not use the following browsers:
To view the Javadoc, Oracle recommends that you use one of the following:
As the Oracle CM SDK Java API grows to take advantage of new features and technology, certain classes, attributes, and methods might be deprecated. You should expect these deprecated elements to be deleted in the following major release. This provides you with a full release cycle to modify your applications to use the supported classes, attributes, and methods.
To see what is deprecated in this release, go to the "Deprecated" link in the Javadoc. Each deprecation has a comment indicating the equivalent supported usage. You can also check if your application is using any deprecated classes, fields, or methods by compiling your Java application with the -deprecation flag.
Some of the significant changes and deprecations are described below.
AppleTalk Filing Protocol (AFP) will not be supported in future releases of Oracle CM SDK. In future releases, Mac users will be able use SMB or WebDAV.
The following FTP QUOTE commands are deprecated in this release, and will be deleted in a future release:
The SearchObject class and its related classes have been deprecated. Due to the restriction that a SearchObject is only guaranteed to work within the same version of Oracle CM SDK and is not upwardly compatible, its benefits are limited, and the classes will be deleted in a future release.
If your application uses SearchObject, your options are to modify your application to either:
SearchSpecification each time as needed.
The next major release of Oracle CM SDK will include changes to the use of Definition classes. Definition classes are the subclasses of oracle.ifs.beans.LibraryObjectDefinition that are used to create new and to modify existing Oracle CM SDK instances. In previous versions of Oracle CM SDK, these Definition classes had an unpublished zero argument constructor defined. This meant that a statement such as the following would compile and (in most cases) execute successfully:
DocumentDefinition def = new DocumentDefinition();
This has never been a legal or recommended variant of construction, but in most circumstances it would yield reasonable results. In some circumstances, using definition instances constructed in this manner could result in obscure exceptions.
The correct method of constructing definition objects is to use the published constructor variant that takes a single LibrarySession argument.
In the next major version of Oracle CM SDK, these zero argument variants will be removed, and any code that attempts to use them will result in compilation errors.
Additionally, in the next major version of Oracle CM SDK, the published constructor variant will be changed from taking a oracle.ifs.beans.LibrarySesssion argument to a oracle.ifs.common.LibrarySessionInterface argument. Since LibrarySession implements the LibrarySessionInterface, no code changes are necessary. However, this change will require a re-compilation of any code written against Oracle CM SDK that constructs definition instances.
A new class, LockObject, was introduced with the 9.0.3 release. This class is used to manage the following lock types available to a PublicObject:
See the LockObject Javadoc for more information.
Most Oracle CM SDK protocol servers (FTP, SMB, etc.) no longer perform parsing and rendering as a side effect of transferring files. In previous releases, an XML document uploaded through the protocols was parsed automatically. Starting with the 9.0.3 release, this is no longer the case.
An exception to this deprecation is the Command-Line Utilities Protocol (CUP) server. To continue parsing and rendering XML files, you can use the CUP server. To create Oracle CM SDK objects through XML files, upload your XML file using CUP. CUP also continues to render out objects in XML.
The purpose of the parsing/rendering framework in Oracle CM SDK was to allow application developers to inject behavior changes into the protocol servers when they were transferring files. Since the protocol servers no longer support this feature, the following deprecations apply for this release.
oracle.ifs.beans.parsers.Parser oracle.ifs.beans.parsers.ParserCallback oracle.ifs.beans.parsers.XmlParserInterface oracle.ifs.server.renderers.Renderer
oracle.ifs.beans.parsers.IfsSimpleXmlParser oracle.ifs.beans.parsers.IfsXmlParser oracle.ifs.beans.parsers.LiteralDocumentParser oracle.ifs.beans.parsers.ParserInputStream oracle.ifs.server.renderers.BaseRenderer oracle.ifs.server.renderers.SimpleXmlRenderer oracle.ifs.server.renderers.XmlRenderer
Application developers who need to modify the contents of files as they are stored and/or retrieved can still do so by directly modifying the input stream as the document is being uploaded or downloaded.
This attribute has been deprecated. It was designed to allow for a "working copy" of a versioned document to be maintained inside Oracle CM SDK while a versioned document was checked out. All protocol servers have been enhanced to recognize the existence of this object, but not to create them. If you have a custom application that makes use of this attribute, you are encouraged to develop an alternative implementation before upgrading to the next major release of Oracle CM SDK.
See the Oracle Internet Directory Release Notes for complete information on all known issues. This section covers only those issues specific to Oracle CM SDK. Note that several bugs listed in Table 1, " Installation and Configuration Bugs" can be fixed by upgrading the database instance supporting Oracle Internet Directory to release 9.0.1.4 of the Oracle9i Database Server.
Oracle CM SDK relies on the Provisioning Integration Service provided by the Directory Integration Platform to be notified of user and group changes in Oracle Internet Directory. These changes are stored in the Oracle Internet Directory change log and are appropriately filtered by the Provisioning Integration Service before being delivered as change events to this application. Even if you are not deploying the Oracle Internet Directory server in replication mode, make sure that the directory administrator starts up the replication server in order to periodically purge unnecessary change-log entries.
This can be done by starting the replication server using the following command:
$ oidctl connect=<net_service_name> server=oidrepld instance=1 flags="-p <ldapserver_port_number>" start
Without this periodic cleanup, the Oracle Internet Directory change log can potentially grow to occupy the entire file system, which can cause unavailability of the Oracle Internet Directory service. The need to start the replication server to purge the change log is only a temporary restriction and will be removed in a future release.
For more information on starting and stopping the replication server, see the Oracle Internet Directory Administrator's Guide.
The following bugs are known to exist in this Oracle CM SDK release. Workarounds are given when appropriate. The known bugs are grouped by process or component:
Table 1 Installation and Configuration Bugs
| Bug # | Description | Action |
|---|---|---|
|
2391425 |
NLS: IFSCONFIG fails in Japanese environment on AL32UTF8 database. Oracle Text does not support Japanese lexer on AL32UTF8 databases. Because of this, Oracle CM SDK does not support AL32UTF8 databases for Asian languages. |
Use UTF8 for the database instead of AL32UTF8. |
|
2677722 |
"OPMN timeout exceeded" error occurs during configuration. The OPMN timeout value is too low. |
Increase the OPMN timeout value. The default value is 30 minutes. |
|
2960519 |
Re-use of the Oracle CM SDK schema configured and set up with the same middle tier is not supported. If you run the Oracle CM SDK Configuration Assistant twice in the same Oracle home, against the same Oracle CM SDK domain and schema, the Agents in the local node become deactivated if the following are true: |
It is strongly recommended that the Oracle CM SDK Configuration Assistant not be run more than once per Oracle home, per Oracle CM SDK domain and schema. If you have already run the Configuration Assistant twice and your Agents have become deactivated, you can solve the problem by going to the Application Server Control and setting all the Agents to "Active" for the affected node. |
|
3016906 |
Oracle CM SDK configuration against Windows 64-bit Oracle9i Database Server 9.2 database fails.
The database is missing the |
There are two possible solutions:
|
|
3163780 |
ifsshell script must have execute permission for the CUP client on Solaris.
The |
If you cannot run the CUP client, use the following command to make the
The ifsshell script is located in the |
|
3038101, 3113355 |
Configuring Oracle CM SDK against a 9.2.0.3 or 9.2.0.4 DBMS fails. When trying to configure against a 9.2.0.3 or 9.2.0.4 database, the following error occurs in the log when trying to create Advanced Queues:
The problem is that some of the stored procedures are still at the 9.2.0.1 level, yet the software was upgraded to 9.2.0.3 or 9.2.0.4. |
|
|
3151323 |
The Configuration Assistant fails to launch in a Simplified Chinese environment if IME is on. This is caused by a JDK 1.4.1_05 bug which causes the Input Method Editor (IME) to interfere with Java applications. |
Turn off the IME and then re-run the Configuration Assistant. |
|
3195013 |
Running the Configuration Assistant and reusing an existing schema disables the Web Starter Application. The Web Starter Application is automatically configured when you set up the HTTP node in an Oracle CM SDK instance. When you reuse a schema on a mid-tier and choose to run Agents on this new node, the Web Starter Application on the previous mid-tier gets deactivated. |
Log into the Application Server Control and reactivate the Web Starter Application. |
|
3163079 |
Product Languages button is not used during Oracle CM SDK installation. There is no way to select languages when installing Oracle CM SDK. |
You do not need to click the Product Languages button during installation since all languages are automatically installed with Oracle CM SDK. |
|
1857689 |
If custom classes conflict with new out-of-the-box Oracle CM SDK classes, the upgrade fails. If custom classes created with an earlier release of Oracle Internet File System or Oracle CM SDK conflict with any classes that are new in Oracle CM SDK, the upgrade to Oracle CM SDK fails. |
Prior to upgrading, the conflicting custom classes must be deleted and re-created with new names that do not conflict. The new classes added in Oracle CM SDK are: |
|
3175218 |
After upgrading Oracle CM SDK, the protocol servers fail to come up if you are using Oracle Internet Directory for credential management. This is caused by the fact that the Oracle CM SDK application entity needs to be added to some OID DAS groups. |
Run the
See the Oracle Content Management SDK Administrator's Guide for more information about |
|
3214142 |
Java Command for regular nodes needs to be changed for Solaris 2.9. The current Java Command for Oracle CM SDK regular nodes includes the following argument: This argument is only valid if you are running on Solaris 2.8. If you are running on Solaris 2.9, this argument should be removed. Retaining this argument on Solaris 2.9 can cause problems. |
If you are running on Solaris 2.9, perform the following steps:
For more information about changing node configurations and restarting regular nodes, see the Oracle Content Management SDK Administrator's Guide. Caution: Make sure that any new node configuration you create does not include this argument. |
| Bug # | Description | Action |
|---|---|---|
|
2386806 |
URLs with '%' in them do not work. URLs that have '%' embedded will cause problems. |
Do not use '%' in URLs. |
|
2393968 |
URLs with '#' in them do not work. URLs that have '#' embedded will cause problems. |
Do not use '#' in URLs. |
|
2337719 |
URLs with ';' in them do not work. URLs that have ';' embedded will cause problems. |
Do not use ';' in URLs. |
|
3006494 |
Cannot create multiple Web Folder mappings that use different user credentials on the same client computer. Because of a Web Folders limitation, Oracle CM SDK does not support logging in to Web Folders as different users from the same Windows client. Web Folders caches user credentials, so if you first create a Web Folders mapping as user1, and then create a second mapping as user2, after user1's connection is disconnected, user2 is able to access user1's content. |
Do not create Web Folder mappings that use different user accounts from the same client computer. Alternatively, you can restart the Windows client machine. |
|
2955251 |
Cannot connect to Oracle CM SDK through WebDAV cookie-less client. If multiple Oracle CM SDK middle tiers are fronted by a load balancer that relies on cookies to load balance requests, WebDAV clients that do not store cookies will not be able to access that Oracle CM SDK instance via the load balancer. This may be particularly noticeable on Macintosh client machines. |
Configure the load balancer to use IP addresses instead of cookies for load balancing. |
|
2697262 |
WebDAV drag-and-drop download can result in 0-byte file. Dragging a file from a Web Folder on Oracle CM SDK to the local PC file system can result in a 0-byte file if the file is locked by another user on Oracle CM SDK. This appears to be caused by MSDAIPP.DLL version 8.103.2402. |
Upgrade Internet Explorer to the latest Service Pack. Ensure the client environment conforms to the supported configuration listed in Client Certifications for WebDAV: Web Folders. |
|
3225450 |
Cannot authenticate through WebDAV if Oracle CM SDK is configured to run using https. If you have set up Oracle CM SDK to run using https, Web Folders cannot be used due to authentication problems. This is caused by a default security check that prevents the ability to authenticate using basic authentication. |
For more information about setting server configuration parameters, reloading servers, and restarting the OC4J instance, see the Oracle Content Management SDK Administrator's Guide. |
| Bug # | Description | Action |
|---|---|---|
|
1859056 |
Binary Documents are not indexed. Binary documents are not content indexed and hence are not located in a search. |
None. This feature is planned for a later release. |
Oracle is a registered trademark, and Oracle9i and OracleMetaLink are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.
Copyright © 1999, 2003 Oracle Corporation.
All Rights Reserved.
|
|
![]() Copyright © 1999, 2003 Oracle Corporation. All Rights Reserved. |
|