Error HTTP Status 500 While Accessing CMC/BI Launchpad in SAP BI 4.0

Environment:

• Windows
• Tomcat 6
• SAP BusinessObjects BI 4.0
• Possibly the installation of SAP BusinessObjects Explorer 4.0

Resolution:

1. Stop Tomcat
2. Go to the Tomcat Work directory (usually C:\Program Files\SAP BusinessObjects\Tomcat\work) and continue down to Catalina\localhost.
3. Delete the BOE directory - this gets recreated on startup.
4. Start Tomcat
5. Wait a few minutes while Tomcat recreates the directory and regenerates it's cache.
6. Attempt to log into the CMC.

If this fails, then try redeploying the WAR file once again, initially without using wdeploy as follows:

1. Stop Tomcat
2. Go to the Tomcat Web App directory (usually C:\Program Files\SAP BusinessObjects\Tomcat\webapps)
3. Delete the BOE directory - this gets re-deployed by tomcat due to the BOE.xml file in tomcat\conf\Catalina\localhost\.
4. Go to the Tomcat Work directory (usually C:\Program Files\SAP BusinessObjects\Tomcat\work) and continue down to Catalina\localhost.
5. Delete the BOE directory - this gets recreated on startup.
6. Start Tomcat
7. Wait a few minutes while Tomcat recreates the directory and regenerates it's cache.
8. Attempt to log into the CMC.

If this fails, then try redeploying the WAR file using wdeploy.

1. Go to the wdeploy directory in the BusinessObjects directory
2. Check that the config.tomcat6 file points to the right location
3. Run the following command: wdeploy.bat tomcat6 deployall
4. Attempt to log into the CMC.

Hope you find this useful.

Cheers,
Umang Patel
+919979084870
SAP BO BI Solution Architect/Consultant

SAP BI 4.0 + SSL

1. Execute the following from a command line to create a .keystore file:

Windows User :

%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA
 

2. Upon executing the above command, you will be prompted for a keystore password, your full name, organizational unit, organization, city, state and country. At the end, you will be prompted for the keystore password again. This has to be the same password as the password you entered previously. Newer versions of the keytool will prompt you to hit ENTER to keep it the same.

3. Once finished, a self signed .keystore file will have been created in your user"s home directory:

For example: C:\Program Files\Documents and Settings\Administrator

4. Move this file from this directory to one in the Business Objects folder structure:

For example: C:\Program Files\Business Objects

5. Browse to Tomcat's server.xml file and create a backup file:

For example: C:\Program Files\Business Objects\Tomcat\conf\server.xml

6. Open and edit the server.xml file in wordpad.

7. Uncomment the section below and add the two commands after keystorePass & keystoreFile. This section needs to reference the new location of the .keyfile and the password you specified when creating it.

<!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->
 
<Connector port="8443"
          maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
          enableLookups="false" disableUploadTimeout="true"
          acceptCount="100" debug="0" scheme="https" secure="true"
          clientAuth="false" sslProtocol="TLS" keystorePass="password" keystoreFile="C:\Program Files\Business Objects\.keystore"/>

8. Restart Tomcat and it should now be accessible using:

https://servername:8443

Hope you find this useful.

Cheers,
Umang Patel
+919979084870
SAP BO BI Solution Architect/Consultant

Best Practices for using the Import Wizard to migrate Repository Objects across SAP Business Objects XI 3.1

• The Import Wizard in Business Objects Enterprise uses a combination of CUID(Cluster Unique Identifiers) and Object Names to move or update Objects from a Source 3.1x/XI-R2 Environment to a target 3.1x/XI-R2 environment.

• When moving the objects over, there are three distinct scenarios that determine how the import wizard would migrate the objects over -

          a.   The object to be migrated has the same CUID and same Object Name in both the source and the Target Environment.

          b. The objects to be migrated has the same CUID but different Objects Name in the Source and the Target Environment

          c. The object to be migrated has different CUID but the same object Name in the source and the Target Environment.

• The newly created target environment i.e. a new CMS would not have any objects and hence the three scenarios would not apply to such an environment. The import wizard can be used to move objects to a newly created target environment without being concerned about the three scenarios above. However, successive migrations after the initial move will require keeping the above scenarios in mind prior to moving the objects over.

•  The import wizard allows for two options during the migration phase of the objects from a source to a target environment - 'Merge' and 'Update'. In a environment that has been managed in compliance with Best Practices, scenario (2.a) in the above would always exist i.e. CUID and Objects names will always be in sync. In such a scenario, using either a Merge or Update options should produce identical results.

•  However, in a target enviornment, that has been updated with incosistent sources, scenarios (2.b) and (2.c) can exist. In order to avoid this situation, it is good to comply with the following best practices -

• Ensure that the source and target environments are always in sync. This can be accomplished by using a single tool to perform the migration e.g. always use the Import wizard to carry out the migration.

• Ensure that successive  migrations are performed with the 'update' option of the import wizard. This will ensure that the existing CUID and Objects are updated if they eixst and duplicated are not created.

• Ensure that when using 'biar' files to move the content over, the files are the latest copies from the source system. Ensuring version management of the biar files will help minimize any human errors in the import process when using the biar files. If version management of the biar files is not feasible, switch to online migration from source to target system..

• Always ensure proper backups of the BusinessObjects Enterprise system with a backup copy a CMS database and FRS File System. In the event of inconsistency betweend CUID's and Objects Names between source and target environment, it may be quicker to restore the system from backup then fixing individual objects.

Hope you find this useful.

Cheers,
Umang Patel
+919979084870
SAP BO BI Solution Architect/Consultant

Actions needed when restoring only the CMS database when it is crashed in SAP BI 4.0.

Note:

Only perform this procedure if only the CMS database has crashed. If the database is corrupted or other components have been compromised you must perform a full system restore.
Repair or replace the CMS database host-machine. If replaced, ensure that it has the same system name as the previous host-machine, as well as the same port settings and database credentials.

Note:

If it is not possible to restore the machine using the same name and credentials, you will need to use the CCM to update this database connection information for each node in the cluster and restart those nodes.

1. Stop all BI platform nodes using the CCM.
2. Locate the latest CMS database backup set.
3. Using your database tools, restore the CMS database.
4. Locate the most recent CMS database transaction log—that is, the log that contains transactions performed after the last backup.
5. Replay the entire transaction log for the CMS database.
6. Use the CCM to start the BI platform nodes.

 Once you have verified the system is working properly, take the following actions:

•  Run the Repository Diagnostic Tool to remove any unused temporary files and check repository consistency.
• Any publishing jobs in process at the time the system was backed up will display as failed. Do not rerun these instances, start a new publishing jobs.

Hope you find this useful.
Cheers,
Umang Patel
+919979084870
SAP BO BI Solution Architect/Consultant

SAP BO Disaster Recovery in clustered enviroment

Issue

• Take a backup of the Production System's database and then create a new ODBC connection pointing to this database.
• On a new server that has SAP BusinessObjects XI 3.1 installed, take the existing Server Intelligence Agent (SIA) and then point the database to the prod backup.
• Start up the SIA. 
• In the Central Management Console (CMC) for your DR system, you will now see SIA nodes for the Production System. 
• In the CMC, you will now see the new SIA that you added. 

Cause

• The backup of the Central Management Server (CMS) repository contains remote node information for the existing database. 
• Even though the CMS is using a separate physical database, the remote nodes contained within the metadata will connect to each other and show up in the CMC. 
• They will link each other when the SIA is started on the DR system. 

Solution

• The goal of these steps is to prevent the DR system from connecting to the Prod system. As an added precaution, you can create loop backs in your local hosts file that will return 127.0.0.1 when Production SIA nodes are referenced. 
• Take a backup of the Production System's database and then create a new ODBC connection pointing to this database. 
• On a new server that has SAP BusinessObjects XI 3.1 installed, create a new SIA and point it to the prod backup. 
• Open the Central Configuration Manager (CCM), go to the properties of the newly created SIA. 
• Click on Startup and you should see remote CMS nodes from your production environment. Remove these remote nodes. 
• Start up the SIA. 
• In the Central Management Console (CMC) for your DR system, you will now see SIA nodes for the Production System, you will now have to remove these. 
• In the CCM, create a new SIA with exactly the same SIA name for each of the SIA nodes from your production environment. 
• Once the SIA is created, click delete and then delete it from this DR system. 
• Repeat this until all the production nodes are cleaned up. You will be left with a system that only has DR servers on it now. 

Hope you find this useful.Cheers,
Umang Patel
+919979084870
SAP BO BI Solution Architect/Consultant

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

Environment

• SAP BusinessObjects Business Intelligence Platform 4.0
• Apache 2.2

solution

1. In the Apache installation directory, edit the file httpd.conf
2. Uncomment the following two lines :

• LoadModule proxy_module modules/mod_proxy.so
• LoadModule proxy_http_module modules/mod_proxy_http.so

3. Configure the ProxyPass for every web application that is deployed behind the reverse proxy server.
4. 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.

Cheers,

Umang Patel

+919979084870

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

Environment

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, BOE.properties in : <BOE_INSTALL_DIR>/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/wdeploy/conf/apps

• Rename BOE.properties 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 BOE.properties to MYBOE.properties.

• 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.

Cheers,

Umang Patel

+919979084870

SAP BO BI Solution Architect/Consultant

List of services included in SAP BO BI 4.0 Web Applications

WEB APPLICATION	LIST OF SERVICES
BOE	OSGi archive of core web applications, including:
	• Analytical Reporting
	• CMC
	• 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)
BusinessProcessBI	This web application is deprecated. It provides support for
	legacy Crystal Reports web services and SDK components,
	including:
	• Crystal Enterprise
	• Crystal Reports Report Application Server (RAS)
	• SAP BusinessObjects Dashboards (formerly Xcelsius)
	• SAP BusinessObjects Analysis, OLAP edition
clientapi	SAP Crystal Reports JavaScript API support.
dswsbobje	Web 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
	Intelligence)
	• SAP BusinessObjects Dashboards web services (formerly
	Xcelsius)
jsfplatform	Java Server Faces support and examples.
MobileOTA14	Web application for mobile client support.
OpenSearch	OpenSearch support.
AdminTools	Query Builder support.

Hope you find this useful.

Cheers,
Umang Patel
+919979084870
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.

Cheers,

Umang Patel

+919979084870

SAP BO BI Solution Architect/Consultant