In the Source Type list, select Oracle Fusion, then click Create.

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. Configuring and Managing the Oracle BI Presentation Catalog 17-41 Replication log files are stored on disk indefinitely, until you periodically remove them. When performing replication operations, Presentation Services reads only replication log files from the time interval that is specified by the ReadLogRecordsSinceHoursAgo element in the instanceconfig.xml file. For information about this element, see Section 17.12.6, Editing the instanceconfig.xml File for Replication. While you might want to review replication log files, for example, for troubleshooting purposes, you should never edit log files manually.

17.12.1.1 Replication Log File Records

A replication log file contains different types of records, with each record consisting of several fields that are separated by commas. The most important types of records in a replication log file are described in Table 17–4 . The following list describes some fields in a replication log file: ■ Size. The size of the record in bytes and encoded as a hexadecimal number. ■ Type. The type of record, such as the following: – H. File header record – S. Presentation Services startup record – B. Before change record – A. After change Record – F. File finished record ■ Timestamp. The timestamp of the record, written as a hexadecimal number that represents the number of seconds from midnight 00:00:00, January 1, 1970 UTC. ■ Change sequence number. A sequence number that should be the same in the corresponding Before change and After change records. ■ Change type. The type of change, written as a hexadecimal number that represents a combination of the following flags: – 1. Insert – 2. Delete – 4. Write Table 17–4 Description of Records in Replication Log Files Type Written Contents File header record At the beginning of each log file Size, Type, Timestamp, Version, Flags Startup record Each time Presentation Services starts Size, Type, Timestamp Before change record When an Oracle BI Presentation Catalog object is about to be changed Size, Type, Timestamp, Change sequence number, Change type After change record Immediately after a catalog operation has been completed Size, Type, Timestamp, Change sequence number, Operation outcome File finished record As the last record in a replication log file Size, Type, Timestamp, Name of next log file