Changing the Default Currency for Analyses Archive the catalog object in the test environment using one of the following:

16-6 System Administrators Guide for Oracle Business Intelligence Enterprise Edition For more information about the currency.userPreference variable, see Oracle Fusion Middleware Users Guide for Oracle Business Intelligence Enterprise Edition 4. Save and close the userpref_currencies.xml file. 5. Restart Oracle Business Intelligence. For information, see Section 4.1, About Starting and Stopping Oracle Business Intelligence.

16.2.4 Example: Dynamic Mapping to Define User-Preferred Currency Options

The following example shows a userpref_currencies.xml file that uses a dynamic mapping to define user-preferred currency options: UserCurrencyPreferences currencyTagMappingType=dynamic UserPrefCurrencyLogicalSQL -- In this SELECT statement, column1 contains the values to set the PREFERRED_ CURRENCY variable, column2 contains the currency tag values, and column3 contains the values to set the currency.userPreference variable. -- SELECT markets.userpreferences, markets.currencyTag, markets.userpreferencename FROM userCurrencyPreference UserPrefCurrencyLogicalSQL UserCurrencyPreferences Table 16–1 shows sample results from the logical SQL statement. Figure 16–3 shows how the values that are generated dynamically from the SQL statement in the userpref_currencies.xml file are displayed in a drop-down list of currency options for the Currency box on the Preferences tab of the My Account dialog. The drop-down list is similar to what is displayed for a prompt on a dashboard page. Table 16–1 Sample Logical SQL Results Markets.UserPreference Markets.CurrencyTag Markets.UserPreferenceName varchar varchar varchar orgc1 loc:en-BZ Org currency gc2 int:euro-1 Global currency 2 lc1 int:DEM Ledger currency gc1 int:USD Global Currency 1 Configuring Currency Options 16-7 Figure 16–3 Dynamic Currency Options in the My Account Dialog 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\? 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. 17-4 System Administrators Guide for Oracle Business Intelligence Enterprise Edition

17.1.3 File System Guidelines for Catalogs

This section describes the following guidelines for working with objects in catalogs in file systems: ■ Section 17.1.3.1, Handling Users of the Catalog ■ Section 17.1.3.2, Handling Heterogeneous Nodes ■ Section 17.1.3.3, Handling Catalog Files on Various Platforms ■ Section 17.1.3.4, Known Issues with Catalog Files

17.1.3.1 Handling Users of the Catalog

The catalog is designed to scale to thousands of concurrent users. To achieve this scaling, the catalog adheres to the following guidelines: ■ The average user typically only reads from the catalog and rarely, if ever, writes to it. In Release 11g, each user is constantly and automatically updating his or her Most Recently Used file, but each users read operations still far outweigh the users writes operations. Therefore, the read-to-write ratio is typically at least 100 to 1. ■ While a locking mechanism guarantees that only one user can write to an object at a time, it is rare for multiple users to attempt to write simultaneously to the same object. A feature called lazy locking allows users to continue reading an object even when another user is updating that object. ■ Modern file systems cache small files directly inside the directory record, such that reading any information on a directory simultaneously loads all small files directly into the operating systems memory cache. Therefore, it is good practice to keep files in the catalog small, especially the frequently read .atr metadata files. When these metadata files remain small, then all the .atr files in a directory are loaded into memory with one physical hard disk read. Every file that exceeds the small threshold adds another physical hard disk read, which can cause a 100 degradation for each large file. In other words, use care when considering storing arbitrary Properties in .atr files. ■ Reading an objects .atr metadata file using NFS is far slower than reading it directly from a local disk. For this reason, Presentation Services additionally caches all .atr files internally. This cache can become briefly stale when another node in the cluster writes data to the file that is newer than the data that is cached by the current node. Therefore, all nodes are refreshed according to the MaxAgeMinutes element in the instanceconfig.xml, whose default for a cluster is 5 minutes. This default setting commonly achieves the best trade-off between the possibility of stale data and the known performance impact. The default for an environment without clusters is 60 minutes. You can modify the MaxAgeMinutes element for your system. Its parent elements are Cache and CatalogAttributes. Before you modify the element, ensure that you are familiar with the information in Section 3.4, Using a Text Editor to Update Configuration Settings.

17.1.3.2 Handling Heterogeneous Nodes

To allow heterogeneous nodes in a cluster, the catalog adheres to the following guidelines: ■ The maximum length for the name of an object on disk is 256 bytes, which is 64 Unicode characters. The logical name is restricted to 256 Unicode characters. To adhere to this restriction, logical names greater than 32 characters are hashed. Configuring and Managing the Oracle BI Presentation Catalog 17-5 ■ The maximum length for the name of a path on disk is 32KB, which is 8000 Unicode characters. The logical path is restricted to 16000 Unicode characters. ■ All path names on disk are all lowercase. The logical path name allows mixed case, but is still case-insensitive. ■ Certain characters are not allowed for path names on disk, while the logical path name allows all characters. For example, Windows systems disallow certain characters such as the colon :, so those characters are mapped using standard HTML escape sequences. For example, the period character . becomes 2e. ■ Certain file names are not allowed on disk, while the logical object name has no restrictions. For example, Windows systems disallow certain file names such as COM, so those names are mapped using standard HTML escape sequences. For example, com becomes co6d.

17.1.3.3 Handling Catalog Files on Various Platforms

Keep the following points in mind when handling catalog files on various platforms: ■ For UNIX Platforms: UNIX kernels must commonly be configured to allow more than 4000 subdirectories per directory. See Section 17.2.1, Manually Changing Additional Configuration Settings for the Catalog for information on the HashUserHomeDirectories element. ■ For Windows Platforms: When users want to navigate catalog files using a tool such as Microsoft Windows Explorer, then they want the catalog structure based on a short path name such as c:obidemo, rather than the long default path name. Note that such navigation is not recommended. – FAT is not supported, and NTFS is required. – Performance on Windows platforms degrades noticeably when more than 8000 files exist in a single directory. Because each catalog object has two files the data file and the .atr metadata file, it is strongly recommended that you not store more than 4000 catalog objects in a single directory. See Section 17.2.1, Manually Changing Additional Configuration Settings for the Catalog for information on the HashUserHomeDirectories element. – Windows Explorer does not handle long path names properly, and it is recommended to not use Windows Explorer to navigate the internal structure of the catalog. While the file system can handle path names as large as 32KB and Presentation Services is not negatively affected, you cannot use Windows Explorer with any path name that is longer than approximately 2KB. Because a single Unicode character can require as many as 4 bytes, you might be unable to use Windows Explorer with path names of only 500 Unicode characters. This limitation does not affect Presentation Services. Because of this limitation, place the catalog in a top-level directory, such as c:\mycatalog\sales.

17.1.3.4 Known Issues with Catalog Files

The following issues are known when working with catalog files: ■ Locking across NFS systems is difficult, but Presentation Services provides an effective locking mechanism in recent patches. Obtain key patches to update older versions of Oracle BI EE as necessary. For more information, see Section 17.2.4, Validating the Catalog. 17-6 System Administrators Guide for Oracle Business Intelligence Enterprise Edition ■ Various third-party FTP programs have issues handling escape sequences, which often results in a renamed file that is doubly escaped. For example, a file that is named sa2epaint whose logical name is SA.Paint is incorrectly renamed to sa252epaint whose logical name is SA2ePaint. Avoid using an FTP program directly against a catalog. Instead, download and use the 7-Zip utility to compress the catalog files, then use an FTP program to transfer the resulting compressed file.

17.2 Maintaining the Oracle BI Presentation Catalog

This section contains the following topics on maintaining a catalog: ■ Section 17.2.1, Manually Changing Additional Configuration Settings for the Catalog ■ Section 17.2.2, Manually Creating a New Oracle BI Presentation Catalog ■ Section 17.2.3, Deploying Catalogs and Objects to Production ■ Section 17.2.4, Validating the Catalog

17.2.1 Manually Changing Additional Configuration Settings for the Catalog

In addition to the presentation settings that you can change in Fusion Middleware Control, you can modify other settings manually. Use various elements in the instanceconfig.xml file to change these settings. Before you begin this procedure, ensure that you are familiar with the information in Section 3.4, Using a Text Editor to Update Configuration Settings . To manually change additional configuration settings for the catalog: 1. Open the instanceconfig.xml file for editing as described in Section 3.6, Where Are Configuration Files Located?

2. Locate the Catalog section in which you must add the following element:

■ HashUserHomeDirectories : Specifies the hashing of directories. If you have more than 4000 catalog users or if you intend to have more than 4000 catalog users in the future, then you must turn on the hashing of users home directories to address a file system limitation. To do so, set the HashUserHomeDirectories element to 2 from its default value of 0. When this element is turned on, for example, the default name for user Steves home directory would become usersststeve.

3. Include the element and its ancestor element as appropriate, as shown in the

following example: ServerInstance ps:Catalog xmlns:ps=oracle.bi.presentation.servicesconfigv1.1 Caution: Keep the following points in mind: ■ The HashUserHomeDirectories element must be set immediately after installing Oracle BI EE to be effective. ■ Include only one Catalog element in the instanceconfig.xml file or unexpected results might occur. Unless expressly noted, include most nodes in an XML document only once. Configuring and Managing the Oracle BI Presentation Catalog 17-7 ps:HashUserHomeDirectories2ps:HashUserHomeDirectories ps:Catalog ServerInstance 4. Save your changes and close the file. 5. Restart Presentation Services.

17.2.2 Manually Creating a New Oracle BI Presentation Catalog

You can manually create a new catalog. To manually create a new catalog: 1. Stop the service for Presentation Services. The Oracle BI Server and WebLogic Server must be running.

2. Specify a new location one that does not exist for the catalog on the Repository

tab of the Deployment page in Fusion Middleware Control. See Section 10.2, Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location.

3. Ensure that the new location for the catalog is empty.

4. Save your changes and close the file.

5. Restart Presentation Services.

When manually creating a new catalog in a clustered environment, you must restart each instance of Presentation Services separately using the Availability tab of the Capacity Management page in Fusion Middleware Control. Do not click Restart on the Business Intelligence Overview page. Wait a short time after restarting the first Presentation Services instance to give the system enough time to create the new catalog, then verify that the catalog was successfully created in the Presentation Services log file before restarting the other Presentation Services instances in the cluster.

17.2.3 Deploying Catalogs and Objects to Production

You can deploy catalogs and simple objects for example, a dashboard with privileges to a production environment from a test environment, as described in the following sections: ■ Section 17.2.3.1, Deploying Catalogs to Production ■ Section 17.2.3.2, Deploying Objects to Production

17.2.3.1 Deploying Catalogs to Production

Use the 7-Zip utility to archive an entire catalog in a test environment, then use the utility to unarchive the file in the production environment. Do not use Catalog Manager for archiving and unarchiving entire catalogs. You might deploy a catalog in a cluster configuration in which different security environments are used. Some servers in the cluster might share the same LDAP server, Caution: Include only one Catalog element in the instanceconfig.xml file or unexpected results might occur. Unless expressly noted, include most nodes in an XML document only once. 17-8 System Administrators Guide for Oracle Business Intelligence Enterprise Edition while others might not. If you deploy the catalog to a server that is communicating with a different LDAP server, then you must regenerate the user GUIDs for the catalog. See Regenerating User GUIDs in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition for information. Optionally, if you are deploying the catalog from test to a new production environment, then use Fusion Middleware Control to specify the location of the new catalog in the production environment. For information, see Section 10.2, Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location.

17.2.3.2 Deploying Objects to Production

You can deploy simple objects for example, a dashboard with privileges to a production environment from a test environment. Deploying a complex object for example, an object that includes references to external filters is a more advanced process. Oracle offers advanced training courses to guide you through this process. It is recommended that you attend one of these courses before you attempt to deploy a complex object to production. To deploy a simple catalog object to a production environment: 1. Optional If you are deploying a catalog object to a new production environment. Archive the catalog object in the test environment and unarchive it in the production environment as follows:

a. Archive the catalog object in the test environment using one of the following:

– Oracle BI Presentation Services. – Catalog Manager. For information, see Section 17.10, Archiving and Unarchiving Using Cat- alog Manager.

b. Copy the archived file to the production computer.

c. On the production computer, unarchive the object.

For information about how to unarchive an object, see Section 17.10, Archiving and Unarchiving Using Catalog Manager. d. Set the permissions on the object as appropriate. 2. Optional If you are deploying the catalog to an existing production environment. Copy and paste new or updated objects from the test catalog into the production catalog as follows: a. Open two Catalog Manager windows: one with the test catalog, and another with the production catalog. b. Selectively copy and paste the folders from the test catalog into the production catalog. If you copy and paste folders where the same content has been changed in the test or production environments, then test content overwrites the production content. 3. Optional If you are deploying the catalog from test to a new production environment, then use Fusion Middleware Control to specify the location of the new catalog in the production environment. Configuring and Managing the Oracle BI Presentation Catalog 17-9 For information, see Section 10.2, Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location.

17.2.4 Validating the Catalog

Over time, inconsistencies can develop in the catalog as links are broken, users are deleted, or NFS file system issues are encountered. These inconsistencies can eventually lead to incorrect behavior, such as the inability to edit an agents recipient list. You can periodically take the production system offline and validate the catalog, to be informed of and to take corrective action on inconsistencies.

17.2.4.1 Performing a Basic Validation of the Catalog

Use the following procedure to perform a basic validation of the catalog. To validate the catalog: 1. Stop Presentation Services. For information, see Section 4.3, Using Fusion Middleware Control to Start and Stop Oracle Business Intelligence System Components and Java Components. 2. In 11g only, regenerate the user GUIDs for the catalog. See Regenerating User GUIDs in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition for information 3. Back up the catalog by using the 7-Zip utility to create a compressed file for it. 4. Create a backup copy of the instanceconfig.xml file. For the location of the file, see Section 3.6, Where Are Configuration Files Located? 5. Edit the instanceconfig.xml file so that it contains the appropriate elements for performing the validation. For information on these elements, see Section 17.2.4.2, Specifying the Elements for Validating the Catalog. 6. Start Presentation Services to run the validation according to the values that you specified in the instanceconfig.xml file. 7. Stop Presentation Services. 8. Create a backup copy of the instanceconfig.xml file in which you added the validation elements, renaming the file similar to instanceconfig_validate.xml. In this way, you have a version of the file to use as a starting point for subsequent validations. 9. Restore the backup version of the instanceconfig.xml that you created earlier to use as the current version. 10. Start Presentation Services. Caution: Ensure that you regenerate the user GUIDs before validating the catalog. Failure to do so can result in the removal of all accounts, permissions, and privileges from the catalog. 17-10 System Administrators Guide for Oracle Business Intelligence Enterprise Edition

17.2.4.2 Specifying the Elements for Validating the Catalog

As part of the process of validating the catalog, you include elements in the instanceconfig.xml file that run the validation when you restart Presentation Services. The following procedure describes how to edit the instanceconfig.xml file to include these elements. Before you begin this procedure, ensure that you are familiar with the information in Section 3.4, Using a Text Editor to Update Configuration Settings. To specify the element for validating the catalog: 1. Open the instanceconfig.xml file for editing as described in Section 3.6, Where Are Configuration Files Located?

2. Locate the Catalog section in which you must add the elements that are described

in Table 17–1 .

3. Include the elements and their ancestor element as appropriate, as shown in the

following example. In this example, the validation runs when Presentation Services starts. Inconsistent accounts such as those for deleted users, links, and objects are removed. Inconsistent users home directory names are logged but directories are not removed. ServerInstance ps:Catalog xmlns:ps=oracle.bi.presentation.servicesconfigv1.1 ps:ValidateOnStartupAndExitps:Validate ps:ValidateAccountsCleanps:ValidateAccounts ps:ValidateHomesReportps:ValidateHomes ps:ValidateItemsCleanps:ValidateItems ps:ValidateLinksCleanps:ValidateLinks ps:Catalog ServerInstance

4. Save your changes and close the file.

Caution: Include only one Catalog element in the instanceconfig.xml file or unexpected results might occur. Unless expressly noted, include most nodes in an XML document only once. Configuring and Managing the Oracle BI Presentation Catalog 17-11 The elements have the values that are described in the following list: ■ None — Specifies that no validation is performed. ■ Report — Specifies that details about each inconsistent object are written to the sawlog.log file. For information, see Section 8.3.2, What Are Diagnostic Log Configuration Files and Where Are They Located? ■ Clean — Specifies that details about each inconsistent object are written to the sawlog.log file and that each object is removed from the catalog.

17.3 About Catalog Manager

Catalog Manager is a tool that lets you perform online and offline management of Oracle BI Presentation Catalogs. It should be installed on a secure computer that is accessible only to Oracle BI Administrators. Table 17–1 Elements for Validating the Catalog Element Description Default Value Validate Performs the validation of the catalog according to the values of the other Validate-related elements in this section. Values are described in the following list: ■ None — Performs no validation. ■ OnStartup — Performs the validation when Presentation Services starts. ■ OnStartupAndExit — Performs the validation when Presentation Services both starts and stops. This value allows re-running of the validation, performing as many cycles of Report and Clean until the catalog is as clean as appropriate. If this value is not None, then all privileges and each objects ACLs in the entire catalog are cleaned of terminated accounts, regardless of the settings of the other Validate-related elements. None ValidateAccounts Verifies that all information about users, roles, and groups in the catalog is consistent. Values are described in the list after this table. None ValidateHomes Verifies that all information about home directories in the catalog is consistent. Values are described in the list after this table. None ValidateItems Verifies that all information about objects in the catalog is consistent. Values are described in the list after this table. None ValidateLinks Verifies that all information about links in the catalog is consistent. Values are described in the list after this table. None 17-12 System Administrators Guide for Oracle Business Intelligence Enterprise Edition

17.3.1 Uses for Catalog Manager

You can use Catalog Manager to: ■ Manage folders, shortcuts, and objects analyses, filters, prompts, dashboards, and so on. For example, you can rename and delete objects, and you can move and copy objects within and between catalogs. ■ View and edit catalog objects in Extensible Markup Language XML. ■ Preview objects, such as analyses and prompts. ■ Search for and replace catalog text. ■ Search for catalog objects. ■ Create analyses to display catalog data. ■ Localize captions. See Section 15.2.2, Localizing Oracle BI Presentation Catalog Captions. Many of the operations that you can perform in Catalog Manager can also be performed through the Catalog page in Oracle BI Presentation Services. For information, see Managing Objects in the Oracle BI Presentation Catalog in Oracle Fusion Middleware Users Guide for Oracle Business Intelligence Enterprise Edition.

17.3.2 Guidelines for Working with Catalog Manager

Follow these guidelines when working with Catalog Manager: ■ Always make backup copies of the Oracle BI Presentation Catalogs that you are working with. ■ Be sure of changes that you plan to make. Catalog Manager commits changes immediately. There is no undo function nor are there any error messages to tell you that a particular change does not display well to users. However, if you do make any unwanted changes, then you can revert to your latest saved backup. ■ Do not copy and paste catalog contents into e-mail, as this is not supported.

17.3.3 Tips for Working with Catalog Manager

As you work with Catalog Manager, keep the following tips in mind: ■ While working in online mode, you can paste catalog contents into or out of a read-only folder by turning off the read-only property of the folder tree before copying, then re-apply the read-only attribute after pasting. ■ You cannot copy, archive, or drag files from the systemsecurity directory in the Catalog Manager. ■ Some keyboard shortcuts might not work properly. ■ Even if a resize indicator is not shown, Catalog Manager panes might still be resizable. ■ You can use Catalog Manager in languages other than English. For information, see Section 15.3, Setting the Current Locale in Catalog Manager. Configuring and Managing the Oracle BI Presentation Catalog 17-13

17.4 Starting Catalog Manager and Opening Catalogs

This section describes the following topics: ■ Section 17.4.1, Starting Catalog Manager ■ Section 17.4.2, Understanding the Two Catalog Modes ■ Section 17.4.3, Operations Available in Online Mode and Offline Mode ■ Section 17.4.4, Opening an Oracle BI Presentation Catalog

17.4.1 Starting Catalog Manager

Use the following procedure to start Catalog Manager. To start Catalog Manager: 1. Using the command line, change to the following directory: ORACLE_ INSTANCE\bifoundation\OracleBIPresentationServicesComponent\coreapplicati on_obipsn\catalogmanager then run the appropriate script: runcat.cmd on Windows runcat.sh on UNIX Figure 17–2 shows sample objects in the Catalog Manager for Windows. Figure 17–2 Sample Objects in Catalog Manager

17.4.2 Understanding the Two Catalog Modes

You can open a catalog in one of two modes — online or offline. Both modes can operate against an actual production catalog, with no need for any downtime.

17.4.2.1 Online Mode

In online mode, you connect to a catalog on a running Web server. In this mode your permissions are applied, you can select a locale, and you can see the effects of any localization on the catalog. You can see only those objects for which you have the appropriate permissions. Both Presentation Services and the Web Server must be running for you to open catalogs in online mode.