If you clicked Create and Customize, then on the Documents tab, add the RTF

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 17-42 System Administrators Guide for Oracle Business Intelligence Enterprise Edition – 8. Change catalog object information – 16. Change owner – 32. Change security ■ Operation outcome. The operation result, which is one of the following: – 0. Fail – 1. Success

17.12.2 Configuring to Replicate an Oracle BI Presentation Catalog

To enable replication of an Oracle BI Presentation Catalog, perform the steps that are described in the following sections: ■ Section 17.12.3, Copying Oracle BI Presentation Catalog Files ■ Section 17.12.4, Using the Oracle BI Presentation Services Replication Agent ■ Section 17.12.5, Creating the config.xml File for Replication ■ Section 17.12.6, Editing the instanceconfig.xml File for Replication

17.12.3 Copying Oracle BI Presentation Catalog Files

The Presentation Services Replication Agent copies changes made to an Oracle BI Presentation Catalog. Because it copies only changes and not the entire contents, you must first make a copy of the source catalog on each of the subscribing instances of Presentation Services.

17.12.4 Using the Oracle BI Presentation Services Replication Agent

You can run the Replication Agent on any computer that has network access to both instances of Presentation Services. This agent handles all the replication tasks and provides command-line options. The Replication Agent whose file name is sawrepaj is a utility that performs common replication tasks such as copying, exporting, importing, and marking for replication. The Replication Agent requires information about the instances of Presentation Services and the replication tasks. This information is stored in the config.xml file, and described in Section 17.12.5, Creating the config.xml File for Replication. The command line for the Replication Agent uses the following format: ■ In UNIX: sawrepaj.sh [C path] command [command parameters] The sawrepaj.sh file is located in ORACLE_HOME\bifoundation\web\bin\sawrepaj. ■ In Windows sawrepaj.bat [C path] command [command parameters] The sawrepaj.bat file is located in ORACLE_HOME\bifoundation\web\bin\sawrepaj. The path following the C specifies the path to the config.xml file. The command options are described in the following sections: