Defining User-Preferred Currency Options Using a Static Mapping Example: Static Mapping to Define User-Preferred Currency Options

16-8 System Administrators Guide for Oracle Business Intelligence Enterprise Edition 17 Configuring and Managing the Oracle BI Presentation Catalog 17-1 17 Configuring and Managing the Oracle BI Presentation Catalog This chapter describes how to configure and manage the Oracle BI Presentation Catalog and provides information about basic maintenance procedures and configuring for full-text searching. This chapter includes the following topics: ■ Section 17.1, About the Oracle BI Presentation Catalog ■ Section 17.2, Maintaining the Oracle BI Presentation Catalog ■ Section 17.3, About Catalog Manager ■ Section 17.4, Starting Catalog Manager and Opening Catalogs ■ Section 17.5, Using the Catalog Manager Workspace ■ Section 17.6, Working with Objects in Catalog Manager ■ Section 17.7, Viewing and Editing Catalog Objects in XML ■ Section 17.8, Searching for and Replacing Catalog Text Using Catalog Manager ■ Section 17.9, Creating Reports to Display Catalog Data Using Catalog Manager ■ Section 17.10, Archiving and Unarchiving Using Catalog Manager ■ Section 17.11, Configuring for Full-Text Catalog Search ■ Section 17.12, Replicating Oracle BI Presentation Catalogs

17.1 About the Oracle BI Presentation Catalog

The Oracle BI Presentation Catalog stores the content that users create in a directory structure of individual files. This content includes folders, shortcuts, Oracle BI EE objects such as analyses, filters, prompts, and dashboards, and Oracle BI Publisher objects such as reports and templates. This section contains the following topics: ■ Section 17.1.1, Objects in the Catalog ■ Section 17.1.2, Locations for the Catalog ■ Section 17.1.3, File System Guidelines for Catalogs

17.1.1 Objects in the Catalog

Figure 17–1 shows sample objects in the catalog, as seen in Presentation Services. 17-2 System Administrators Guide for Oracle Business Intelligence Enterprise Edition Figure 17–1 Sample Objects in the Catalog in Presentation Services

17.1.1.1 Guidelines for Object Names

Each object in the catalog is stored in its own file. For example, an analysis called Analysis 1 is stored in a file named Analysis1. The object name that is visible to users, such as Analysis 1, is referred to as the logical object name. The following list provides guidelines for object names: ■ No restrictions exist on which characters are allowed in the logical name of an object in the catalog, provided that the characters are valid Unicode characters. The following are valid logical names: Hello World Profit Loss Sales Cost ~~ Expense? ■ The length of the logical object name must not exceed 256 Unicode characters. For more information on Unicode, see Section 17.1.3, File System Guidelines for Catalogs. ■ The length of the logical path name for an object must not exceed 16000 Unicode characters. ■ The number of directory segments in a logical path name for an object must be not exceed 255 segments. For example, a directory with a name such as n1n2n3n4….n253n254n255 is acceptable, while a name such as n1n2n3n4….n254n255n256 is unacceptable. ■ When you pass the path name of an object using SOAP, you must escape the following characters: Forward slash Backward slash \ Tilde ~ Asterisk Question mark ? The following logical path names are all valid: sharedtestHello World sharedtestProfit \ Loss sharedtest Sales \ Cost \~\~ Expense\?