Skip Headers
Oracle® Fusion Middleware Developer's Guide for Content Server
11g Release 1 (11.1.1)

Part Number E10807-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Go to current chapter
Go to next page
View PDF

5.2 Using Components

Components are modular programs that are designed to interact with the Content Server at run time. The component architecture model is derived from object-oriented technologies, and encourages the use of small modules to customize the Content Server as necessary, rather than creation of a huge, all-inclusive (but cumbersome) application.


You can create custom components by manually creating the necessary files and resources. However, the Component Wizard has no limitations compared to the manual method and using it prevents many common mistakes.

Any type of file can be included in a component, but the following file formats are used most often:

Components are typically used to alter the core functionality of the Content Server. For example, a component could be used to:

The advantages of using component architecture with the Content Server include the following:

Keep the following constraints in mind when deciding whether to use custom components:

Components must be installed and enabled to be used by Content Server. Components provided with Content Server are automatically installed, and they are enabled or disabled by default. Custom components must be installed and enabled to be usable. Several tools are available for working with components:

For information on component architecture and creation, see Chapter 3, "Working with Components."