Release Notes for Oracle WebCenter
Interaction Development Kit 10.3.0.0.0
Interaction Development Kit (IDK) 10.3.0.0.0 - released October
Interaction Development Kit (IDK) 6.0 - re-released January 2008
with signed dlls (originally released June 2007 for AquaLogic Ensemble 1.0
Development Kit (IDK) 5.4 - released January 2007 for Java 5.0 compatibility
Development Kit (IDK) 5.3 - released October 2006 for AquaLogic Interaction 6.1
Enterprise Web Development
Kit (EDK) 5.3 - released December 2005 for AIX, Solaris and SUSE Linux
Enterprise Web Development
Kit (EDK) 5.3 - released September 2005 for Windows and Red Hat Linux
The Oracle WebCenter
Interaction Development Kit (IDK) is used to build custom applications as part
of Oracle WebCenter Interaction architecture. The Oracle WebCenter Interaction
Development Kit (IDK) supports a variety of development tasks including:
pagelets using the proxy API, which supports Oracle WebCenter Ensemble 1.0
for all portlet API development scenarios.
- Custom portlets using the
- Applications using the SOAP
based APIs to access Oracle WebCenter Interaction, Oracle WebCenter
Collaboration and Publisher servers.
- Integration web services (IWS)
that integrate custom authentication, user profile, crawler, and search
services into Oracle WebCenter Interaction.
The Oracle WebCenter
Interaction Development Kit (IDK) supports these development scenarios in both
Java and .NET by providing JARs and assemblies that can be added to a development
These release notes cover
Oracle WebCenter Interaction Development Kit (IDK) version 10.1.3.4.0. Note:
The Oracle WebCenter Interaction Development Kit (IDK) was previously known as
the AquaLogic Interaction Development Kit (IDK) and the Plumtree Enterprise Web
Development Kit (EDK).
At the time of
release, Oracle WebCenter Interaction Development Kit (IDK) 10.3 supports
- Operating Systems: Windows
Server 2003 SP2, Windows 2000 Server SP4, Solaris 10, 9, 8 (SPARC), AIX
5.3 (Power 3, Power 4, Power 5), Linux RHEL 3.0-3, 3.0-4, 4 Update 3
(x86), SUSE Linux ES 9, HP-UX 11i v3 or v2 (Itanium), or OEL 5.1
- Remote Web Application Servers
- IIS 6.0 (with .NET 2.0 or
- Remote Web Application servers
- Apache Tomcat 6.0.14, 5.5.17
- BEA Weblogic 10.3.x, 10.2.x,
10.0.x, 9.2. 9.1 or 8.1 SP4 or SP5
- IBM WebSphere 6.1 or 6.0.1
- .NET Framework version 2.0.50727
- Oracle WebCenter Interaction
Development Kit (IDK) .NET PRC Collaboration and PRC Content (Publisher)
APIs also require .NET Web Services Enhancements 2.0SP3 to use document
- JDK version 5.0 or 1.4
- JDK version 5.0
At the time of release,
Oracle WebCenter Interaction Development Kit (IDK) 10.3 supports the following:
- Oracle WebCenter Interaction
- BEA AquaLogic Interaction
6.5.x, 6.1.x, 6.0, 6.0 SP1
- Oracle WebCenter Ensemble 10.3
or BEA AquaLogic Ensemble 1.0
- Oracle WebCenter
Collaboration: 10.3 or BEA AquaLogic Collaboration 4.5, 4.2 MP1, 4.2, 4.1
- BEA AquaLogic Interaction
Publisher: 6.5, 6.4, 6.3, 6.2
The following product
documentation is available on the Oracle Technology Network (http://www.oracle.com/technology/index.html):
Title and File Name
Describes how to install the
Oracle WebCenter Interaction Development Kit (IDK).
Documentation for Java and .NET
APIs provided by the Oracle WebCenter Interaction Development Kit (IDK).
Provides detailed information on
development using the Oracle WebCenter Interaction Development Kit (IDK).
This release included the
following new features:
- Signed dlls.
- Additional API methods for
AquaLogic Ensemble 1.0 compatibility.
When grabbing content items, if the
request takes longer than 60 seconds you get timeout exception (Issue: 65555).This
issue has been fixed.
- When using the IDK from a
standalone Java application, the Servlet API JAR version 2.2, 2.3, or 2.4
must be explicitly added to the classpath. (Issue #37348)
- The settings configuration
file described in the KB article titled "IDK Proxy Settings
Configuration File (IDK 6.0)" is released in Beta in IDK 6.0 and is
not yet supported. This feature may be replaced or removed in a future
- Multiple endpoints for AWS/PWS/CWS/SWS/SCI are no
longer supported in Java and have never been supported in .NET.
Prior to version 5.2.0, it was possible to define endpoints in Java by
declaring multiple bindings/ports in server-config.wsdd. For instance,
multiple CWS endpoints ContainerProviderSoapPort1 and
ContainerProviderSoapPort2 could be mapped to different implementations of
IContainerProvider. Though it is still possible to use an old
server-config.wsdd to create multiple SOAP endpoints for an IWS, this is
no longer supported. (Issue #43508)
- The IDK requires WSE 2.0 SP3.
Building against the .NET IDK causes the warning "dependency could
not be found," for the assembly: Microsoft.Web.Services2. As the
requirements indicate, this assembly from Microsoft Web Services
Enhancements is only needed by PRC Collaboration for Document Upload and
the warning can be ignored if this part of the IDK API is unused. (Issue
- .NET SOAP connections could be
closed due to one of the following errors: "System.Net.WebException:
The underlying connection was closed: An unexpected error occurred on a
receive." or "The underlying connection was closed. An
unexpected error occurred on send."
There is a bug in the Microsoft .NET framework that causes random
connection failures. See http://support.microsoft.com/default.aspx?scid=kb;EN-US;819450
- When uploading large files
(>4MB) in .NET using PRC Collaboration, PRC Content, or when using a
slow connection, you might need to add settings to your Web.config or
machine.config. The .NET IDK has a configuration snippet in app.config
that shows the maxRequestLength and executionTimeout parameters. When
added to the appropriate section of your Web.config, they can circumvent
ASP.NET timeouts and allow large file uploads. You may also need to
increase the responseDeadlockInterval attribute in the machine.config of
your Microsoft.NET Framework directory.
The following are the settings that can be added to Web.config or
∑ †<!-- Must configure section handler for microsoft.web.services section -->
∑ type="Microsoft.Web.Services2.Configuration.WebServicesConfiguration,Microsoft.Web.Services2,Version=184.108.40.206,Culture=neutral,PublicKeyToken=31bf3856ad364e35" />
∑ †<!-- The maximum file upload size supported by ASP.NET. The size specified is in Kilobytes.
∑ †A value of -1 means there is no limit. The default is 4096 KB (4 MB). -->
∑ †<!-- The maximum number of seconds that a request is allowed to execute before
∑ †being automatically shut down by ASP.NET. A value of -1 means
∑ †there is no limit. The default is 90 seconds. -->
∑ †<executionTimeout value="-1" />
- Publisher throws a
ContentException when attempting to publish a content item with a long
name or path.
Publisher imposes a limit on the length of file paths to published and previewed
content items. This is file system and thus OS dependent, though a 255
character limit is common. The file path length is determined by the path
to the published content directory, e.g.
C:\bea\alui\ptcs\publishedcontent, combined with the full Publisher path
to the item including folder and subfolder names. A content item nested
deep within a folder hierarchy may encounter this problem. Shortening the
folder hierarchy or names of folders or content items can prevent the
error. (Issue #41597)
- A ContentException could be
thrown if the WS Content internal Publisher session times out before the
portal login token.
If the Publisher session in the WS Content times out (the default is 24
hours) before the portal login token used by the IRemoteSession, then the
PRC Content will return an error. When using the default values for portal
login token time-out and Publisher session time-out, this problem will
never occur. However, this can occur if the Publisher session timeout is
shorter than the portal login token timeout. Simply refreshing the portal
login token and creating a new IRemoteSession will refresh the Publisher
session and resolve the issue. (Issue #43646)
throws an ArrayIndexOutOfBoundsException when it is called with the root
folder path ('/').
Use IFolderManager.getRootFolder to retrieve the root folder. (Publisher
issue# 43840) (Issue #43952)
- Publishable presentation
templates are not searchable. (Issue #44390)
- Rapid creation and removal of
Collaboration objects causes a NullPointerException from Collaboration
when search indexing is enabled.
Search is attempting to index Collaboration objects that have already been
removed. If rapid creation and removal of Collaboration objects is
required, the search indexing can be disabled by editing Collaboration's
ptcollab\4.0\settings\config\config.xml. In the section labeled
"Search settings" set search enabled="no".
Disabling search indexing of Collaboration objects is not recommended and
issues caused by this setting are not supported. (Issue #35222)
- Methods that take a long time
to complete can cause SOAP timeouts which will be thrown as exceptions in the
IDK. Copy operations continue to be processed by Collaboration, while
upload operations are aborted. This will be addressed in a future release.
The following methods are known to cause SOAP time-outs depending on
network conditions or size of the affected Collaboration object structure:
IDocumentManager.insertNewDocument (Issue #35300)
- If a copy operation has not
completed after 10 minutes, it is aborted. This is not a bug and will not
be fixed. This affects: IProjectManager.copyProjectContent,
ITaskListManager.copyTaskLists, IDocumentManager.copyToFolder (Issue
- PRC Collaboration calls result
in an exception: Call into WS Portal to authorize login token
SOME_LOGIN_TOKEN= failed. Details: java.lang.NullPointerException
Either Collaboration 4.0.2 must be installed or, if using 4.0.1, the
220.127.116.11486 Hotfix must be applied to Collaboration itself (not the IDK
client). In Collaboration 4.0.1, portal users that do not have read access
to the administrative folder in which they reside cannot make PRC
Collaboration method calls. A workaround that does not require the hotfix
is to grant all users read access to the folder in which they reside.
- It is not possible to query
ACLs on portal document folders. (Issue #26256) (Related issue #26257)
- Querying objects using
ObjectClass.Community does not function as expected. When performing object
queries using ObjectClass.Community, the community objects reside in their
own administrative folder and not the folder in which they visually appear
in the portal. This is due to the internal storage of communities in the
portal and will not change. (Issue #37349)
- MyPages queries for
non-administrator users do not work as expected.
- IDK does not return the
localized name for portal objects (e.g., Knowledge Directory folder
object) based on portalís current localized language setting. Users
must use ObjectProperty.Name to explicitly specify language setting in
order to get its corresponding localized name. (Issue #59058)
- Dates in the search server are
only accurate to within four minutes. Using Operator.Equals on Date fields
is discouraged. (Related issue #26926)
Using GreaterThan/LessThan or a date range is the recommended usage.
- Types of search exceptions
that are thrown when executing an IPortalSearchRequest with invalid
parameter values are mismatched between the Java and .NET IDKs. When
calling execute() after some methods of IPortalSearchRequest were called
with invalid values, for example, an empty IFilterClause or non-existent
fields, the .NET IDK throws a different exception than the Java IDK.
- Portal properties of type
double are truncated to floats in the search server. Using Operator.Equals
on float fields is discouraged.
Using a float range is the recommended usage. (Issue #32270) (Related
- The maximum http header size
enforced by a Web application server could truncate a portlet's essential
http header (CSP) information.
Increase the Web application server's maximum header size. (Issue #32446)
- Folder metadata is not loaded
during a crawl. The method IContainer.getMetaData() is not called during a
crawl, and thus folder metadata is not loaded. Folder metadata is visible
through the Edit view of the Knowledge Directory. This is a known
limitation of the Portal Crawl Provider and is unlikely to change.
Add folder metadata by editing each folder in the directory. (Issue
- .NET Crawlers operating in
DocFetch mode must use Document Literal SOAP encoding which can be set in
the Crawler Web Service editor. This is a known limitation and will not be
fixed. (Issue #29127)
- The portal does not send the
number of records to return as set by the Results Per Page parameter in
the Portal Search Preferences Page. The portal will return varying values
when ISearchQuery.GetMaxReturn() is called based upon the number of
concurrent searches requested. (Issue #20551)
- Logging does not function on
Windows machines with multiple network adapters running Windows versions
below XP SP2 or 2003 SP1.
Upgrade to Windows XP SP2, Windows 2003 SP1 or better, or disable the
additional network adapters. (Issue #42420)