Step 2: Ensuring that Secure Enterprise Search is Available

Configuring and Managing the Oracle BI Presentation Catalog 17-39

17.11.4.9 Step 9: Allowing Users to Access the Full-Text Catalog Search

When you have configured Secure Enterprise Manager to crawl and index the Oracle BI Presentation Catalog, you can notify content designers and users that the Search page is available for performing the full-text catalog search.

17.11.4.9.1 Providing Designers with the URL You can provide designers with the URL to

display the page for the full-text catalog search. Designers can bookmark this page and use it with actions or as a shortcut on a dashboard page. The person who installs Secure Enterprise Search sees a page that provides the URL in the following form: http:host:portsearchquerysearch where host is the computer on which Secure Enterprise Search is installed and port is the port for the administration tool. The default port is 7777.

17.11.4.9.2 Making the Shortcut Available from the Oracle BI EE Home Page You can

configure the Oracle BI EE Home page to include a shortcut in the All Content area that allows users to display the page for the full-text catalog search. To do so, edit the instanceconfig.xml file to include the SESSearchURL element, as described in the following procedure. 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 add the shortcut for the full-text catalog search to the Home page: 1. Open the instanceconfig.xml file for editing, as described in Section 3.4, Using a Text Editor to Update Configuration Settings. 2. Locate the section in which you must add the SESSearchURL element. The value for the SESSearchURL element is the URL for the Secure Enterprise Manager page. Table 17–3 Configuration Properties for the Full-Text Catalog Search Name Description Default Value BIServerURL Specifies the URL for the Oracle BI Server. NA BISearchServerURL Specifies the URL for the servlet for the full-text catalog search. NA BIServerSSOURL Specifies the SSO URL for the Oracle HTTP Server instance that is configured to handle URL requests for Oracle BI EE. NA CrawlingUserKey Specifies the key for the credentials that are used to crawl the catalog. You should not edit this value. NA ExcludePaths Specifies the list of directories from the catalog that should not be crawled. Delimit directories with a semicolon ;. system;sha red IncludePaths Specifies the list of directories from the catalog that should be crawled. Delimit directories with a semicolon ;. RootNode Specifies the node from which all crawling originates. 17-40 System Administrators Guide for Oracle Business Intelligence Enterprise Edition 3. Include the element and its ancestor elements as appropriate, as shown in the following example: Server ps:SESSearchURL xmlns:ps=oracle.bi.presentation.servicesconfigv1.1http:myhost:7777searc hquerysearchps:SESSearchURL Server 4. Save your changes and close the file. 5. Restart Oracle Business Intelligence.

17.12 Replicating Oracle BI Presentation Catalogs

You can copy and merge the contents of selected catalog folders between instances of Presentation Services. You can split the replication configuration into individual tasks. The replication task is an instruction to periodically merge catalog contents for specified catalog folders from one server to another. Two-way replications are possible. A typical scenario where replication is useful is when you use one instance of Presentation Services to prepare and publish shared analyses, and you use two or more production instances to support the users. In this scenario, you share the catalog from Instance 1 to two production instances and share the catalogs on each production instance with the other. To perform this sharing, you configure the following replication tasks in the configuration file for the Presentation Services Replication Agent: ■ shared: Instance1 to Instance2 ■ shared: Instance1 to Instance3 ■ users: Instance2 to Instance3 ■ users: Instance3 to Instance2 When an instance of Presentation Services participates in replication, either as a publisher or as a subscriber, it tracks changes made to catalog objects that are marked to be replicated and keeps them internally in replication log files. Another instance of Presentation Services can make a SOAP call to request to export those changes to a file or to import and replay modifications recorded in a file exported earlier from another instance. The Presentation Services Replication Agent uses SOAP to manage replication-related activities on all instances of Presentation Services and performs import and export operations. For information about these SOAP calls, see Oracle Fusion Middleware Integrators Guide for Oracle Business Intelligence Enterprise Edition.

17.12.1 About Replication Log Files

Replication log files record modifications made to catalog objects that are subject to replication. There are two types of replication log files: ■ Change log files — Contain records of modifications to catalog objects that were made locally. These files are stored in presentationcatalogpathreplicationchangelog folder, where presentationcatalogpath is the full path to the catalog folder. ■ Playback log files — Contain records of modifications to catalog objects that were replayed from other instances of Presentation Services. These files are stored in presentationcatalogpathreplicationplayback folder.