Remote Intradoc Client (RIDC) provides a thin communication API for communication with Content Server. This API removes data abstractions to the 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.
Key features of RIDC include:
Support is provided for Intradoc socket-based communication and the HTTP protocol.
Client configuration parameters include setting the socket timeouts, connection pool size, and so forth.
All calls to RIDC require some user identity for authentication. For Intradoc URLs, no credentials are required because the request is trusted between the content server and the client. For HTTP URLs, the context requires credentials.
To invoke a service, use the ServiceRequest object, which can be obtained from the client.
The RIDC client pools connections, which requires that the caller of the code close resources when done with a response.
Streams are sent to the content server via the TransferStream interface.
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 Content Server.
For details, see Oracle Fusion Middleware Developer's Guide for Remote Intradoc Client for Oracle Enterprise Content Management Suite.