Sunday, June 23, 2013

How to configure Apache as a Reverse Proxy with SAP BO BI 4.0?


  • SAP BusinessObjects Business Intelligence Platform 4.0
  • Apache 2.2


  1. In the Apache installation directory, edit the file httpd.conf
  2. Uncomment the following two lines :
  • LoadModule proxy_module modules/
  • LoadModule proxy_http_module modules/
  1. Configure the ProxyPass for every web application that is deployed behind the reverse proxy server.
  2. Configure the ProxyPassReverseCookiePath for every web application that is deployed behind the reverse proxy server.
Example :
ProxyPass /BI4/BOE http://localhost:8080/BOE
ProxyPassReverseCookiePath / /BI4/BOE
ProxyPass /BI4/AdminTools http://localhost:8080/AdminTools
ProxyPassReverseCookiePath / /BI4/AdminTools

Hope you find this useful.

Umang Patel
SAP BO BI Solution Architect/Consultant

How to rename the BOE web application or the web application source tree in SAP Business Objects Business Intelligence Platform 4.0


SAP Business Objects Business Intelligence Platform 4.0

The source tree folder is located in: <BOE_INSTALL_DIR>/SAP BusinessObjects/SAP BusinessObjects/warfiles/webapps

  • Locate the BOE web application configuration file, in : <BOE_INSTALL_DIR>/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/wdeploy/conf/apps

  • Rename so that it reflects the new name for the web application WAR file. For example, rename the web application from BOE to MYBOE, and so the BOE.war will be already renamed to MYBOE.war. Rename to

  • Use a text editor to update the contents of the newly named .properties file. Update the web application information in the configuration file. For example, rename the web application from BOE to MYBOE, replace <WEB_APP_NAME> with MYBOE.

  • Rename BOE.xml so it reflects the new name for the web application WAR file. For example, rename the web application from BOE to MYBOE, and so the BOE.war or BOE.ear will be already renamed to MYBOE.war or MYBOE.ear. Rename BOE.xml to MYBOE.xml. The WDeploy tool can now deploy the newly-named web application to the web application server.

Hope you find this useful.

Umang Patel
SAP BO BI Solution Architect/Consultant

List of services included in SAP BO BI 4.0 Web Applications

BOEOSGi archive of core web applications, including:
• Analytical Reporting
• SAP Crystal Reports
• BI launch pad (formerly InfoView)
• Eclipse IDE support
• Lifecycle Manager
• Monitoring
• OpenDocument
• BI workspace (formerly Dashboard Builder)
• Platform search
• Platform services
• Visual difference
• SAP BusinessObjects Dashboards (formerly Xcelsius)
BusinessProcessBIThis web application is deprecated. It provides support for
legacy Crystal Reports web services and SDK components,
• Crystal Enterprise
• Crystal Reports Report Application Server (RAS)
• SAP BusinessObjects Dashboards (formerly Xcelsius)
• SAP BusinessObjects Analysis, OLAP edition
clientapiSAP Crystal Reports JavaScript API support.
dswsbobjeWeb Services components, including:
• Session
• BI platform
• BI catalog
• Federation Administration tool
• Live Office
• Web service query tool (formerly Query as a Web Service)
• Publishing
• Report Engine
• SAP BusinessObjects Web Intelligence (formerly Web
• SAP BusinessObjects Dashboards web services (formerly
jsfplatformJava Server Faces support and examples.
MobileOTA14Web application for mobile client support.
OpenSearchOpenSearch support.
AdminToolsQuery Builder support.

Hope you find this useful.
Umang Patel
SAP BO BI Solution Architect/Consultant

In SAP BusinessObjects XI 3.1 Which servers are involved while scheduling a Crystal/Web Intelligence/Desktop Intelligence Publication?

In BusinessObjects XI 3.1 , Below listed servers are in the picture to do the specific tasks:

All Publishing tasks
 The following servers must be installed, configured, and running:
  •  Publication Job Server, especially:
              Publication Scheduling Service
  • Adaptive Processing Server, especially:
              Publishing Service
              Publishing Post Processing Service
  • Destination Job Server
Publishing Crystal reports publications
The following servers must be installed, configured, and running:
  •  Crystal Reports Job Server
  • Report Application Server
Publishing Desktop Intelligence document publications
 The following servers must be installed, configured, and running:
  • Desktop Intelligence Job Server
  • Desktop Intelligence Processing Server
 Publishing Web Intelligence document publications
The following servers must be installed, configured, and running:
  • Web Intelligence Processing Server
  • Adaptive Job Server, 
  • Web Intelligence Scheduling and Publishing Service
Hope you find this useful.

Umang Patel
SAP BO BI Solution Architect/Consultant

Saturday, June 22, 2013

How to improve Web application server performance in case of SAP BI platform running on WACS

To improve the server performance of a WACS, you can change the amount of memory that is allocated to the server through the Central Configuration Manager (CCM).
1.Starting the CCM, and click the Manage Servers icon .
2. Specify the logon credentials for the CMC.
3. On the "Manage Servers" screen, stop the WACS.
4.Click the Web Tier Configuration icon .
The Web Tier Configuration icon is only enabled when you select a WACS that is stopped.
The "Web Tier Configuration" screen appears.
5. Under "Command Line Parameters", specify a new memory value by editing the command line:
a. Find the -Xmx option. This option normally has a value specified.
For example “-Xmx1g”. This setting allocates one giga byte of memory to the server.
b. Specify a new value for the parameter.
• To specify a value in mega bytes, use “m”. For example, “-Xmx640m” allocates 640 mega bytes of memory to the WACS.
• To specify a value in giga bytes, use “g”. For example, “-Xmx2g” allocates two giga bytes of memory to the WACS.
c. Click OK.
6. On the "Manage Servers" screen, start the WACS.

Hope you find this useful.
Umang Patel
SAP BO BI solution architect / consultant

Tuesday, June 18, 2013

How to Install / Deploy / Configure Tomcat 6 externally on a SAP BO BI 4.0 server.

  • Tomcat 6.0.24
  • SAP BO BI Platform 4.0

  1. Following is the link to download Tomcat 6.0.24
  2. Run the executable “apache-tomcat-6.0.24.exe”. The Welcome screen will appear. Click Next.
  3. Click “I Agree” on the License Agreement screen.
  4. Select the install type from drop down box & click Next.
  5. Enter the destination folder where Tomcat 6 is to be installed. Click Next.
  6. Enter the user name & password for Administrator login & click Next.
  7. Enter the below mentioned path that points to JRE supplied with BI 4.0, Click Install:
    Install Dir:C:\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\jdk\jre
  8. Uncheck the “Show Readme” check box. Click Finish.
  9. Tomcat will now start. There will be a small icon in the system tray as shown below.
  10. Right click on the icon & click Configure.
  11. The Apache Tomcat Properties screen will appear. Click on Java tab.
  12. Add the path C:\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\jdk\lib\tools.jar” in Java Classpath field after the existing entry separated by a semi-colon(;).
  13. Add the value 2048 in Maximum memory pool field and 1024 in Thread stack size.
  1. Add the following values in the Java Options field(Assuming SAP Business Objects is installed on E drive ):
    -Djava.library.path=C:\Windows\SysWOW64\;E:\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\
    -Dbobj.enterprise.home=E:\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\
  2. Click on Apply and OK  & restart the Tomcat service.
  3. Open the file config.tomcat6 in Notepad. It can be located in Wdeploy directory.
  4. Assign the following values to the respective variables:
    as_dir=<installation directory of Tomcat 6>
  5. Save & close the file.
  6. Open Command Prompt by clicking Start > Run > type “cmd” & click OK.
  7. Navigate to wdeploy
  8. Run the command “wdeploy tomcat6 deployall”.
  9. A BUILD SUCCESSFUL message will appear once deployment of all WAR files is successful.

Hope you find this useful.

Umang Patel
SAP BO BI Solution Architecture/Consultant

Monday, June 17, 2013

What is Platform Search Application in BI 4.0 and How Search Application Indexing works?


SAP BusinessObjects Business Intelligence Platform 4.0


Platform Search Application Indexing is a continuous process that involves the following sequential tasks:

1. Use Crawling mechanism to poll the CMS repository and identifies objects that are published, modified, or deleted. It can be done in two ways: continuous and scheduled crawling. 

2. Use Extracting mechanism to call the extractors based upon the document type. There is a dedicated extractor for every document type that is available in the repository. There are following extractors:

  •  Metadata Extractor 
  • Crystal Reports Extractor 
  • Web Intelligence Extractor 
  • Universe Extractor 
  • BI Workspace 
  • Agnostic Extractor (Microsoft Word/Excel/PPT, Text, RTF, PDF) 

3. The extracted content will be stored in the local file system 

(<BI 4.0 Install folder>\Data\PlatformSearchData\workplace\Temporary Surrogate Files) in an xml format called as Surrogate files.

4. These surrogate files will be uploaded to Input File Repository Server (FRS) and will be removed from the local file system

5. The content of the surrogate files will be read and will be indexed by using specific index Engine into temporary location called as Delta Indexing Area(<BI 4.0 Install folder>\Data\PlatformSearchData\workplace\DeltaIndexes).

6. The Delta index will be uploaded to Input FRS and will be deleted from the local file system.

7. The Delta Index will be read and will be merged into Master Indexed Area

(<BI 4.0 Install folder>\Data\PlatformSearchData\Lucene Index Engine\index) which is the final indexed area in the local file system.

8. After completing the Indexing task the following things will be generated:

•  Content store: The content store contains information such as id, cuid, name, kind, and instance extracted from the master index in a format that can be read easily. This helps to quicken the search.

Each AdaptiveProcessingServer creates its own content store.
<BI 4.0 Install folder >\Data\PlatformSearchData\workplace<NodeName>.AdaptiveProcessingServer\ContentStores

•  Speller/Suggestions: The similar words will be created from the master indexed data and will be indexed. The speller folder will be created under “Lucene Index Engine” folder (<BI 4.0 Install folder>\Data\PlatformSearchData\Lucene Index Engine\speller)

9. The Delta index files which were uploaded to the Input FRS will be removed from Input FRS after a few hours.


BI 4.0 Platform Search Application supports indexing in a clustered environment.

  • The search and indexing will be active in all nodes, but only one node can merge the delta index to master index. This master index can be used in all the nodes for search operation.
  • All nodes share the same master index, however, each node builds its own content store.  
  • Master Index location needs to be shared by all nodes, it’ s not necessary to share Persistent data location and Non-persistent data location. 
Hope you find this useful.
Umang Patel
SAP BO BI Solution Architect/Consultant

Sunday, June 16, 2013

Configure Tomcat 7 With BI 4 SP04

 Tomcat 7 can be downloaded from following location
A.  Installing Tomcat 7:
1. Extract the contents of file to C:\Program Files(x86)\SAP BusinessObjects folder. Rename the folder apache-tomcat-7.0.29 thus created to Tomcat7.
2. Create a folder Catalina in C:\Program Files (x86)\SAP BusinessObjects\Tomcat7\conf folder.
3. Create a folder localhost in C:\Program Files (x86)\SAP BusinessObjects\Tomcat7\conf\Catalina folder.
4.Open a Command Prompt in elevated mode if you are using MS Windows Server 2008. Navigate to the directoryC:\Program Files (x86)\SAP BusinessObjects\Tomcat7\bin.
5. Run command service install BOEXI40Tomcat.
You should get an output like this:
6.Go to C:\Program Files (x86)\SAP BusinessObjects\Tomcat7\bin through Windows Explorer. Create a shortcut here forTomcat7w.exe. Rename this shortcut as Tomcat Configuration.
7. Right click on the Tomcat Configuration file & click Properties. The Shortcut tab will be displayed by default. Add text //ES//BOEXI40Tomcat in Target field after the existing entry separated by a space. Click on Apply OK.
8. Copy this Tomcat Configuration file to C:\Documents and Settings\All Users\Start Menu\Programs\Tomcat folder. Copy this file to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Tomcat if you are using MS Windows Server 2008. Click on Yes if the Confirm File Replace dialog box appears. If you are using MS Windows Server 2008, click on Copy and Replace.
B. Configuring Tomcat:
  1. Click on Start > All Programs > Tomcat > Tomcat Configuration. This will launch the Apache Tomcat BOEXI40TomcatProperties tool. You will have to open this tool in elevated mode if you are using MS Windows Server 2008
  2. On the General tab, change the Display name to Apache Tomcat 7.0.29. Delete all contents in the Description field. Change the Startup type to Automatic. Click on Apply.
  3. Click on the Logging tab. Change the Level to Error. Delete contents of Log-prefix field.
  4. Copy line “C:\Program Files (x86)\SAP BusinessObjects\Tomcat7\logs\stdout.log” to the Redirect Stdout field
  5. Copy line “C:\Program Files (x86)\SAP BusinessObjects\Tomcat7\logs\stderr.log” to the Redirect Stderror field. Click on Apply
  6. Click on the Java tab. Add the path “C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\jdk\lib\tools.jar” in Java Classpath field after the existing entry separated by a semi-colon(;)
  7. Add the value 2048 in Maximum memory pool field
  8. Delete following parameters from the Java Options field\Program Files (x86)\SAP BusinessObjects\Tomcat7\temp
-Djava.util.logging.config.file=C:\Program Files (x86)\SAP BusinessObjects\Tomcat7\conf\
  1. Add following parameters to the Java Options field.
    -Djava.library.path=C:\Windows\SysWOW64\;C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\
    -Dbobj.enterprise.home=C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\
  2. Click on Apply. You may add some additional parameters to the Java Options field apart from the above mentioned if they were present on previous Tomcat. We have saved Java Options of previous Tomcat in a text file.
  3. Click on Startup tab. Copy the path “C:\Program Files (x86)\SAP BusinessObjects\Tomcat7″ to the Working Path field. Click on Apply.
  4. Click on Shutdown tab. Copy the path “C:\Program Files (x86)\SAP BusinessObjects\Tomcat7″ to the Working Path field. Click on Apply OK
C. Deploying web applications (WAR files):
  1. Open the file config.tomcat7 in Notepad. It can be located in C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\wdeploy\conf folder.
    2.  Assign the following values to the respective variables:
      as_dir= C:\Program Files (x86)\SAP BusinessObjects\Tomcat7
      Save & close the file.
    3. Open a Command Prompt in elevated mode if you are using MS Windows Server 2008.       Navigate to the directoryC:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\wdeploy.
   4. Run the command wdeploy tomcat7 validateconfig to check if you have made the correct changes  in config.tomcat7 file.
    5. A BUILD SUCCESSFUL message will appear if the validation is successful.
    6. Now run the command wdeploy tomcat7 deployall to deploy the WAR files of SAP BO BI 4.0 on Tomcat 7.
    7.  A BUILD SUCCESSFUL message will appear once all the WAR files are successfully deployed.
    8. Click on Start > All Programs > Tomcat > Tomcat Configuration. This will launch the Apache Tomcat 7.0.29 Properties tool. Start Tomcat by clicking on Start button available on General tab. You will have to open this tool in elevated mode if you are using MS Windows Server 2008.
   9. Wait for 10 – 15 minutes until the Catalina servlet initializes itself & starts all applications.
   10. Now test BI Launchpad, CMC & Query Builder & Web Services to check if they are working fine with Tomcat 7.0.29 as Web Application Server.

Hope you find this useful.
Umang Patel
SAP BO BI Solution Architect/Consultant

How to preserve custom settings for BOE java apps in BI 4.0

After applying a patch, customizations added to ..\Tomcat6\webapps\BOE\WEB-INF\config\custom are lost
BI 4.0
Tomcat 6
1) Make changes to <BOE_HOME>\Tomcat6\webapps\BOE\WEB-INF\config\default\<app name>.properties
2) Copy the modified file to <BOE_HOME>\Tomcat6\webapps\BOE\WEB-INF\config\custom
3) apply a patch
4) Obverse that the modifications to <BOE_HOME>\Tomcat6\webapps\BOE\WEB-INF\config\default\<app name>.properties are reverted and the copied file in <BOE_HOME>\Tomcat6\webapps\BOE\WEB-INF\config\custom is no longer present.
When the patch is applied the BOE web application is redeployed
In order to preserve these changes, you will need to modify the files in both locations below:
<BOE_HOME>\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\BOE\WEB-INF\config
 This is the location where changes will be merged.  Files in this directory are modified by the patch and not replaced.  The patch will then use wdeploy to deploy the modified application to Tomcat.

Hope you find this useful.
Umang Patel
SAP BO BI Solution Architect/Consultant

Login delay from external web application server after CMS restart

After restarting the Central Management Server (CMS) there is a login delay up to several minutes until the login finally proceeds. This is happening from an external web application server (WAS).
SAP BusinessObjects (any version)
Microsoft Windows Server 2008 R2 (hosting the CMS)
External Web Application Server (WAS)
The cause for this behaviour is the Microsoft Windows Server 2008 R2 Stealth Mode:
Stealth mode blocks outgoing ICMP unreachable and TCP reset messages for a port when no application is listening on that port.
Having Stealth Mode Enabled will cause the Windows Server not to respond with a TCP RESET to the connection attempt by the WAS but rather
to drop the packet leaving the other host waiting for a timeout.
There are 2 possible resolutions to this problem.
(1) Disable Stealth Mode
If you do not require to use Microsoft Windows Stealth Modeyou can disable it as described in the following TechNet Article:
(2) Fix the CMS Request Port
If you dowant to keep Microsoft Windows Stealth Modeenabled you can manually set the CMS Request Port on your SAP BusinessObjects
installation. This causes the CMS to always bind to the same port and will not cause any problems as the cached request port will be re-used. To
set the Request Port, please see the Administration Guide of your SAP BusinessObjects solution.
  •  For SAP BO XI 3.1: 3. Configuring server settings, Server host identification options 
  •  For SAP BO BI 4.0: Server host identification options 

Hope you find this useful.
Umang Patel
SAP BO BI Solution Architect/Consultant

Restrict access to non-SSL links for BO web applications deployed on Apache Tomcat

  • Apache Tomcat 5.5.x
  • SAP BusinessObjects Enterprise Xi 3.1 (applicable to all SP/FP)
  • Supported Windows Server
After the SSL is successfully configured, users will be able to access the SSL as well as the non-SSL links for BO web applications; which might be a security vulnerability.
  1. Take a backup of the “server.xml”file located at <INSTALL_DIR>\Program Files\Business Objects\Tomcat55\conf\
  2. Edit the server.xml and search for the line : “Connector URIEncoding=”UTF-8″
  3. Comment this line, as : <!– <Connector URIEncoding=”UTF-8″ acceptCount=”100″ connectionTimeout=”20000″ disableUploadTimeout=”true” enableLookups=”false” maxHttpHeaderSize=”8192″ maxSpareThreads=”75″ maxThreads=”150″ minSpareThreads=”25″ port=”8080″ redirectPort=”8443″/> –>
  4. Save and close the file.
  5. Stop the SIA from CCM ; SIA -> Properties -> Protocol :: Ensure that “Enable SSL” is unchecked. Start SIA
  6. Restart Tomcat from CCM
Now you can logon to the CMC and Infoview only through SSL. Try to access the non- SSL link and you'll get a “Page cannot be displayed” error.

Hope you find this useful.
Umang Patel.
SAP BO BI Solution Architect/Consultant

SAP BusinessObjects Enterprise Backup and Recovery Best Practices

This document describes procedures for performing a back up of the Web and SAP BusinessObjects Server system and data files, as well as the procedures to be followed to recover from data loss or hardware failure.
The plan execution requires an experienced SAP BusinessObjects BI professional, operating system administrator,and database administrator.
The backup and recovery process is similar for all environments within a staged system; development, test, and production. Therefore, this document does not refer to any specific environment. It is recommended to backup all environments.
Backup and Recovery Process Concept
A backup and recovery plan consists of precautions to be taken in the event of a full system failure due to a natural disaster or a catastrophic event. The plan aims to minimize the effects of the disaster on the daily operations so that the organization is able to maintain or quickly resume mission-critical functions. It is recommended, as part of a BusinessObjects Enterprise (BOE) disaster recovery plan, to involve an implementation of redundant servers in a back up system, which mirrors the primary system. In the event that the primary system goes down, the back up system is still available and becomes the operational system.
It is a best practice to back up BusinessObjects servers on a daily basis.
The Importance of a Proper Backup Sequence Without backing up the Enterprise system databases and the file repository, no restoration of the environment is possible.
Good backup integrity requires shutting down certain BusinessObjects services prior to capturing the backup. Under certain conditions, failure to follow a proper service shutdown sequence before backing up could result in one or both of the following consequences:
  •  False sense of security in the quality/integrity of the backup.
  • Inability to fully recover BusinessObjects if the backup is of poor integrity.
Types of Backups
A backup can be conducted in multiple ways:
1. Enterprise Content backup vs. server backup
A server backup is the deepest type of backup. Typically, this is a full backup that captures every byte on every local hard disk in a server. This type of backup insures the server’s operating system as well as any applications and data stored on the server’s local drives. Server backups are infrequent, typically only necessary after a stable installation/configuration is achieved and anytime major updates to any of the server components are made.
Enterprise content backup is a subset of a server backup and focuses on the essential components of BOE only. With an Enterprise content back up, one can recover a SAP BusinessObjects environment from scratch on a different hardware environment if necessary.
Enterprise content backup does not insure the operating system or any applications, including the Enterprise executables and DLLs; however, it does insure all of the intellectual content that is created and customized by users of the Enterprise system, which is the most important thing. Content backup also will not insure one against corrupted or deleted Enterprise application DLLs/EXEs or other operating system problems, but these can be resolved by performing a re-installation of operating systems or SAP BusinessObjects BI Backup and Recovery Best Practices.
2. Incremental backup vs. full backup
The choice between incremental backup and full backup is typically a decision made by the disaster recovery team. A full backup captures every targeted byte. Full backups require longer system down time to achieve (in the case of cold backups) but are the safest and least complex type of backup to restore. Because full backups are the slowest and most expensive to capture and maintain,SAP BusinessObjects advises capturing full backups on a weekly basis, where resources allow.
Incremental backups can be performed on a more frequent basis. It begins as a full backup, but each subsequent backup thereafter captures only those files changed since the last backup. They are faster and less expensive to capture than full backups, but are less robust. Because of this, incremental backups are usually acceptable for daily backups.
3. Cold backup vs. hot backup
Using a cold or hot backup strategy is typically dependent on whether a system can tolerate the
downtime required to perform a cold backup. Prior to running a cold backup, the Central Management Server (CMS) service must be stopped so that a backup of the CMS system database and File Repository Server (FRS) can occur. Stopping the CMS will prevent users from accessing the Enterprise system, a factor which must be taken into consideration when scheduling cold backups. This assures an accurate snapshot of the system occurs, since no transactions can occur during the backup procedure.
Cold backups must be done in off peak hours, thereby limiting the frequency at which the backups can occur and sometimes requiring choreography of schedules with other dependencies. Hot backups tend to be the preferred method in global or highly available environments where there is not a feasible window of downtime, as backups can occur while a system is still running, thereby keeping usage of the system unaffected. This enables the narrowing of the gap between the period of time when the last backup was run and when the system experiences failure, as backups can occur more frequently, reducing the amount of work lost in the event of a failure. Because the backup occurs on a live system, a hot back up exposes the possibility that the CMS and FRS will be captured in a state of change; furthermore, the FRS, CMS and PM tables could be captured in an out-of-sync state, a situation which could compromise the integrity and usefulness of the back up.
It is recommended to backup the CMS system database and PM repository once daily with incremental backups and full backup only once per week. The frequency of backups may be revised based on an acceptable amount of time for recovery to satisfy your organization’s requirements. This rest of this paper will focus on the procedures necessary for conducting a backup of enterprise content.
What to Back Up
There are several content-oriented elements that must be backed up daily in order to recover from a disaster. Routinely backing up all of the following content elements will enable you to recover from virtually any type of disaster (virus, hardware failure, natural disaster, and so on).
Database Central Management Server (CMS) System Tables
The CMS contains all the user rights and metadata information about reports and universes, as well as data connection information. The CMS is the heart of the BusinessObjects environment, so it’s critical to frequently back up this database. The environment cannot be restored without a properly backed up CMS database. physical database as the CMS system tables, making it easy to capture during a routine backup of the CMS tables. This database should be captured at the same frequency as the CMS system database.
File Repository Server (FRS)
This is a standard OS file share that contains all the report templates and instances for the environment. The file repository typically ranges in size from 1 GB to 100 GB depending on the size and complexity of the deployment. Since the FRS is designed to exist synchronously with the CMS tables, it should be backed up at exactly the same time as the CMS system tables.
Failure to capture the file repository and CMS system tables simultaneously, when the CMS and FRS services are stopped, could result in poor back up integrity. This is because of the increased risk for orphaned report objects or report pointers in the CMS system database if a database restore becomes necessary. Orphaned report pointers are those records in the CMS system database that do not point to a valid input or output file in the Enterprise Input or Output FRS. If a user were to select a report object or report instance that was orphaned, an error message would occur and they would not be able to access that object or instance. Orphaned input or output files in the file repository are a benign problem compared to orphaned pointers in the CMS tables. Only the Input and Output subfolders need to be backed up (the Temp
folder can be ignored).
Local audit log files
When auditing servers is enabled, each BusinessObjects server writes audit records to a log file local to the server. At regular intervals, the CMS communicates with the audited servers to request copies of records from the local log files.
Auditing Tables
This database contains usage statistics and auditing information for the environment. A back up of this database is not necessary for recovery from a disaster. However, recovery of a CMS database without recovery of the auditing tables from the same backup might result in a corrupt auditing database due to the presence of duplicate event IDs. It’s highly recommended that the auditing tables be included as part of the backup procedure.
Hope you find this useful.

Umang Patel.
SAP BO BI Solution Architect/Consultant