RIDC versus CIS

A question was recently posed on the Oracle WebCenter Content forum about whether to choose Content Integration Suite (CIS) or Remote Intradoc Client (RIDC) for WebCenter Content integration with third-party applications. The user specifically wanted to know the following:

  1. What is faster?
  2. What is simpler or better documented?
  3. What is used by Oracle to communicate between it’s products with ECM?
  4. What will be improved in the future by Oracle?

To try to answer these questions, let’s first examine what exactly CIS is.

The Content Integration Suite (CIS) API offers access to Oracle Content Server by exposing the content server services and data in a unified object model. The UCPM API is modeled into a set of Services APIs, which are API calls that communicate with the target server and the returned value objects from the server.


Now, let’s examine RIDC.

The RIDC communication API removes data abstractions to Oracle Content Server while still providing a wrapper to handle connection pooling, security, and protocol specifics. If you want to use a native Java API, then RIDC is recommended. RIDC has these key features:

  • Support is provided for Intradoc socket-based communication and the HTTP and JAX-WS protocols.
  • The RIDC objects follow the standard Java Collection paradigms, which makes them extremely easy to consume from a JSP/JSPX page.
  • Binders can be reused among multiple requests.
  • RIDC allows Secure Socket Layer (SSL) communication with Oracle Content Server.


My personal choice has always been RIDC. This is further supported by the fact that CIS is now deprecated in WebCenter Content 11gR1.

Content Integration Suite (CIS) has been deprecated. Developers and system integrators are directed to use Remote Intradoc Client (RIDC), which provides a thin communication API for communication with Oracle WebCenter Content Server. For details, see the Oracle WebCenter Content Remote Intradoc Client (RIDC) Java API Reference. For more information, see Section 23, “Using RIDC to Access Content Server.”


RIDC is generally considered more lightweight (and probably faster) than CIS. Both are fairly well documented but there seems to be more examples on the web about using RIDC. Oracle already uses RIDC to communicate between WebCenter Content and certain Oracle products/technologies such as WebCenter Portal and Site Studio for External Application (SSXA). Seeing as how CIS is now deprecated, RIDC is the technology that Oracle is choosing to continue to improve for the future.

You can download the latest RIDC JAR here (under Individual Component Downloads). The 11g version is backwards compatible with 10g. I would always recommend using the latest version of the RIDC library.

For a list of RIDC examples (including sample code), see my post, RIDC examples.

Leave a Reply

2 Comments on "RIDC versus CIS"

Notify of
Sort by:   newest | oldest | most voted