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.

Refreshing child node in the tree in ADF

Requirement – To refresh the tree child node. Executing the top level view object instance alone is not enough. This is because when you expand a parent node, if the
framework identifies any existing query collection for the row filter supplied by the parent row, the existing query collection cache will be reused for displaying
child nodes. To refresh specific child nodes, you will have to find the appropriate child row set and refresh it by calling the executeQuery() method.

For example. We have displaying country in tree node. In Child node we are displaying the states. For we will taking out the country id and fetch the row on basis of countryID and get the rowset
and call executeQuery() method and it will refresh the child node as well.

Below is the code.

public void refreshChildStates(Number CountryId) {
//Gets the VO used for parent node
ViewObjectImpl vo = getCountry();
//Read the row using Key CountryId
Row[] countryRow= vo.findByKey(new Key(new Object[] { CountryId}), 1);
RowSet childRows =
(RowSet)stateRow[0].getAttribute("States")';
childRows.executeQuery();
}

Happy coding with Techartifact…