Posted on

How to connect with UCM in ADF using RIDC API

In order to get things started you need to install the WebCenter extensions for JDeveloper, create a WebCenter Portal project and configure a Content Server connection to point to a running instance of UCM 11g..

Once you have these in place, you can start programming RIDC. I will describe below the most useful operations that can be performed using the API.

            IdcContext idcContext = new IdcContext("weblogic", "welcome1");
            IdcClientManager clientManager = new IdcClientManager();
            try {
                // Create idc client
                IdcClient client = clientManager.createClient("idc://dummy.com:4444");
                // Create a new binder
                DataBinder dataBinder = client.createBinder();
                // set parameter for service call
               // dataBinder.putLocal(WCCConstants.KEY_IDC_SERVICE, "DELETE_REV");
                //
                dataBinder.putLocal(CWCCConstants.KEY_TIMESTAMP, ts.toString());            logger.fine("get response");
            result = response.getResponseAsBinder();
        } catch (IdcClientException e) {
            throw new ContentServiceException("Error in request IdcClient: " + e.getMessage(), e);
        }
        return result;

Using this way we can call the UCM service and get the result set.

Happy coding with Vinay in Techartifact.

Posted on

Multiple ways to integrate content into Webcenter Portal

Ways to integrate content into a WebCenter Portal application using any of the following methods:

■ Content data controls. Use JCR adapters to enable read-only access to content in an Oracle Content Server, Oracle Portal, or SharePoint content repository, and
maintain tight control over the way the content displays in a WebCenter Portal application. This functionality is available primarily for backward compatibility
with prior releases, and for requirements outside the capability of Content Presenter or the Documents service and its task flows.

■ Content Management REST APIs. Use CMIS (Content Management Interoperability Services) REST APIs to surface and manage content in Oracle Content Server.

■ Content Presenter. Enables you to precisely customize the selection and presentation of content in a WebCenter Portal application. The Content Presenter
task flow is available only when the connected content repository is Oracle Content Server and your WebCenter administrator has completed the prerequisite configuration. With Content Presenter, you can select an Oracle Site Studio file, a single item of content, multiple content items, query for content, or select content based on the results of a WebCenter Personalization Conductor scenario, and then select a template to render the content on a page in a WebCenter Portal application. Content Presenter has no dependency on the Documents service for
adding or managing the content it displays.

■ Documents service. Provides several task flows that offer a variety of formats to display folders and files on a page. You can choose the task flows appropriate for
your application to provide features for accessing, adding, and managing folders and files; configuring and viewing file and folder properties; and searching file
and folder content in the connected content repositories. The Documents service task flows are available when the connected content repository is Oracle Content
Server, Oracle Portal, or SharePoint, and your WebCenter administrator has completed the prerequisite configuration. Using Documents service task flows and document components (such as links, previews, and images), you can both add content to the application, and provide end users with content and Documents service task flows built into the application to manage, display, and search documents at runtime. The Documents service also supports wikis and blogs.