WebLogic Administration Portal content management enables you to integrate, manage, and personalize content in a portal environment. Task 4 focuses on managing content within a single instance of the native content repository. The personalized delivery of content will be covered in Task 5: Setting Up Personalization.

Content is a key component of any portal. Content can be defined as unstructured or semi-structured data. A common example is an image file and associated metadata; for example, date created, date modified, author, and subject. In WebLogic Administration Portal, a content type defines the shape of a content item. A content type can be any combination of binary, integer, calendar, string, Boolean, and properties. Interaction Management personalizes the delivery of content based upon these non-binary properties.

Content can be organized into a content hierarchy. The top-level node is defined as the Virtual Content Repository. Under the Virtual Content Repository, you can plug in multiple, heterogeneous content repositories. This task is based on a single instance of the native BEA repository. Repositories can contain multiple hierarchy and content nodes. Hierarchy nodes function primarily as organizational units while content nodes function primarily as content items.

The task takes about 10 minutes to complete.

Task Goals

At the end of this task you will have the knowledge necessary to create and manage content in the BEA repository.

Task Overview

In this task you will start the Content Management tools, create new hierarchy and content nodes, and edit content hierarchy and content properties.

Steps in This Task

Step 1: Start the WebLogic Administration Portal

In this step you will open the WebLogic Administration Portal.

Step 2: Add Hierarchy Nodes (2a: BulkLoader or 2b: WebLogic Administration Portal)

In this step you will create a content hierarchy and populate it with content nodes.

Step 3: Edit Content Hierarchy and Content Properties

In this step you will reorganize your content hierarchy and edit content properties.