An Oracle WebCenter Content Server service is a window for accessing the content and content management functions within Oracle WebCenter Content. For example, one simple integration option is to reference content that is managed within Oracle WebCenter Content by a persistent URL. Some other integration options enable you to use the Java API, the Microsoft Component Object Model (COM) interface, or the ActiveX control.
For more information about integrations options, see Getting Started with Integrating WebCenter Content into Your Environment in Developing with Oracle WebCenter Content.
This chapter discusses the following topics:
5.1 IdcCommand Utility
The IdcCommand utility is a standalone Java application that executes Oracle WebCenter Content Server services. Almost any action you can perform from the Oracle WebCenter Content Server browser interface or administration applets can be executed from IdcCommand.
The program reads a specifying command file, which contains service commands and parameters, and then calls the specified services. A log file can record the time that the call was executed, whether the service was successfully executed, and if there were execution errors.
The IdcCommand utility returns only information about the success or failure of the command. To retrieve information from Oracle WebCenter Content Server in an interactive session, use the Java COM wrapper IdcCommandX, available on Microsoft Windows platforms.
5.2 COM API
You can use a COM interface to integrate Content Management with Microsoft environments and applications. An ActiveX control and an Object Linking and Embedding Control Extension (OCX) component are provided as interface options to gain access to the content and content management functions within Oracle WebCenter Content Server.
Using the IntradocClient OCX Component
An OCX control is provided for connecting to a remote Oracle WebCenter Content Server instance and executing Oracle WebCenter Content Server services. The IdcClient OCX control is used within a Windows Visual Basic development environment to gain access to the content and content management functions within Oracle WebCenter Content Server.
You can call Oracle WebCenter Content Server services with the IdcClient OCX control. The
IdcClient.ocx control is used to connect to a remote Oracle WebCenter Content Server instance and perform typical server functions.
5.3 Remote Intradoc Client (RIDC)
As mentioned earlier, RIDC provides a thin communication API for communication with Oracle WebCenter Content Server. This API removes data abstractions to the Oracle WebCenter Content Server while still providing a wrapper to handle connection pooling, security, and protocol specifics.
RIDC supports Intradoc socket-based communication and the HTTP protocol.
Intradoc communication is handled via the Oracle WebCenter Content Server Intradoc port. This communication method requires a trusted connection between the client and Oracle WebCenter Content Server. Intradoc communication can also be configured to run over SSL.
The implementation of the HTTP protocol uses Apache's Jakarta HttpClient. Communication with the content server using the HTTP protocol requires authentication credentials for each request.
For more information, see Using RIDC to Access Content Server in Developing with Oracle WebCenter Content.