Defining User-Preferred Currency Options Using a Dynamic Mapping

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\? Configuring and Managing the Oracle BI Presentation Catalog 17-3 Use care when building a catalog path. It is very common to see code that assumes the forward slash is always a path separator. Always verify your path code with an object name such as Profit Loss. ■ When you pass a catalog search filter using SOAP, you must escape the following characters: Forward slash Backward slash \ Tilde ~ Asterisk Question mark ? Caret Dollar sign ? The following search filters are all valid: Hello World Profit \ Loss Sales \ \ Cost \~\~ \ Expense\?

17.1.1.2 Attribute Files for Objects

Each object has a corresponding attribute file. For example, the analysis called Analysis1 would have a corresponding attribute file named Analysis1.atr. The attribute file contains the objects full name, access control list ACL, description, and so on. To access an object in the catalog, users must have appropriate ACL entries for that object. All objects in the catalog use ACL entries.

17.1.1.3 Lock Files for Objects

To guarantee that only one user can write to a file at one time, a lock file is created when an object is being written to. On rare occasions for example, after a power outage, temporary lock files in the catalog might not be removed completely. If Presentation Services reports of such a lock file, then you must delete it manually.

17.1.2 Locations for the Catalog

The following list provides the default locations for the directory that holds catalog files: ■ On Windows systems: ORACLE_ INSTANCE\bifoundation\OracleBIPresentationServicesComponent\coreapplicati on_obipsn\catalog ■ On UNIX systems: ORACLE_ INSTANCEbifoundationOracleBIPresentationServicesComponentcoreapplicati on_obipsncatalog You are not required to store the catalog in its default location. You can store the catalog in other locations. When you work in a cluster configuration, you store the catalog on a shared file system that all nodes in the cluster can access. For information, see Section 5.4.2, Sharing the Oracle BI Presentation Catalog. See Section 17.1.3.3, Handling Catalog Files on Various Platforms for more information on catalog directory names.