Oracle UCM Architecture 2-13
As a rule, each web page includes the following resources:
■
A standard page header
■
A standard page beginning
■
A standard page ending Because all of the Oracle Content Server resources are cached in memory at startup,
Oracle Content Server has a definition for the standard pieces that appear on the page. Oracle Content Server then combines the standard resources with the unique resources
specified in the template to create the web page.
For dynamic server pages, the template page and custom resource files are checked into Oracle Content Server. When one of these pages is requested by a web browser,
Oracle Content Server recognizes the file extension as a dynamic server page, which enables special processing. At that point, the page assembly process is the essentially
the same as the standard process, except that the page can use both the standard resources in the resources directory and the custom resources that are checked in to
Oracle Content Server.
2.3.5 Database Interaction
Some databases, such as Oracle Database, return all column names in uppercase characters. Therefore, when Oracle Content Server receives query results from these
databases, column names must be mapped from the uppercase characters to the values used in Oracle Content Server.
Because of this case mapping issue, custom components created for an Oracle Content Server instance using one database might not work correctly on an Oracle Content
Server instance using a different database.
To map column names, the IdcHomeDirresourcescoreresourcesupper_clmns_ map.htm file contains a mapping table named ColumnTranslation. Add the query
values to this file when you create a component that accesses fields that are not Oracle Content Server database fields for example, if you create a component that accesses a
custom table within the Oracle Content Server database.
For information about using the upper_clmns_map.htm file, see Section 5, Modifying
System Functionality.
2.3.6 Localized String Resolution
Localized strings are the means by which the user interface and error messages are presented in the language specified by the users locale. Oracle Content Server loads
the string resource files for a base language and also loads resource files for every supported language. Instead of presenting hard-coded text, the template pages,
applets, and error messages reference string IDs in these resource files, which are then resolved using the ExecutionContext that contains the locale information for the user.
2-14 Oracle Fusion Middleware Developers Guide for Oracle Universal Content Management
3
Working with Standard, Server, and Custom Components 3-1
3
Working with Standard, Server, and Custom Components
This chapter describes how to work with Oracle Universal Content Management Oracle UCM components, which are programs used to modify Oracle Content Server
functionality.
This chapter includes the following sections:
■
Section 3.1, Components Overview
■
Section 3.2, About Directories and Files
■
Section 3.3, Development Recommendations
■
Section 3.4, Component File Detail
■
Section 3.5, Resources Detail
■
Section 3.6, Installing Components
3.1 Components Overview
Components are modular programs designed to interact with Oracle Content Server at runtime. Standard components, system components, and custom components are
included with Oracle Content Server to add or change the core functionality of the standard Oracle Content Server instance. You can create and use custom components
to modify an Oracle Content Server instance without compromising the system integrity. Custom components can alter defaults for your system, add new
functionality, or streamline repetitive functions.
This section provides an overview of component management and the files and directory structure associated with components. It covers these topics:
■
Section 3.1.1, Component Wizard
■
Section 3.1.2, Advanced Component Manager
■
Section 3.1.3, ComponentTool
■
Section 3.1.4, Component Files Overview
■
Section 3.1.5, Enabling and Disabling Components
