Table of Contents. Table of Contents

Transcription

1

2 Table of Contents Table of Contents Preface 8 About this Guide 8 Intended Audience 8 Using this Guide 8 For Further Reading 9 Chapter 1: Getting Started 10 Roambi ES Overview 10 About the Installation Process 11 System Requirements 11 Chapter 2: Installing the Prerequisite Software on Windows 17 Installing Java 17 Installing the JRE 17 Installing the JDK 18 Installing Tomcat 18 Downloading Tomcat 18 Installing Tomcat 18 Modifying the Tomcat Memory Settings 18 Disabling Tomcat Watched Resources 20 Changing the Tomcat Connector Max Post Size 20 Installing MySQL 20 Downloading MySQL 20 Installing MySQL 21 Running the Configuration Wizard 23 Increasing the Maximum Allowed Packet Size 30 Installing OpenOffice 31 Installing wkhtmltoimage 32 Chapter 3: Installing and Deploying Roambi ES on Windows 33 Overview 33 About the Files Included with the Installation 34

3 Installing Roambi ES 34 Deploying Roambi ES on Tomcat 36 Configuring the Database Drivers 37 Installing the MySQL Connector 37 Installing the Microsoft SQL Server Connector 37 Configuring the OpenOffice API 38 Configuring the NTLM HTTP Filter (Optional) 38 Creating the Roambi Database 39 Running the Roambi ES Configuration Wizard 39 Chapter 4: Installing Roambi ES on CentOS, RedHat, and Oracle Linux 45 Installing the Java Runtime Environment (JRE) 45 Installing Tomcat 6 46 Installing MySQL Server 47 Installing OpenOffice 48 Installing wkhtmltoimage 48 Installing Roambi ES 48 Chapter 5: Installing Roambi ES on Ubuntu 51 Installing the Java Runtime Environment (JRE) 51 Installing Tomcat 7 52 Installing MySQL Server 53 Installing OpenOffice 53 Installing wkhtmltoimage 54 Installing Roambi ES 54 Chapter 6: Installing Roambi ES on OpenSUSE 56 Installing the Java Runtime Environment (JRE) 56 Installing Tomcat 6 57 Installing MySQL Server 58 Installing OpenOffice 58 Installing wkhtmltoimage 59 Installing Roambi ES 59 Chapter 7: Configuring Roambi ES Portals 61 Configuring Roambi ES Portals 61 Adding New Portals to Roambi ES 61 Importing Portals from Roambi ES3, ES4 to ES5 64 Adding and Deleting Portals 66 Adding Portals 66 Deleting Portals 67 Creating a Roambi Flow Working Directory 68 Adding Portals for the Supported Portals and Connectors 70 IBM Cognos 71 Configuring Roambi ES for IBM Cognos 71 Configuring an IBM Cognos Portal in Roambi ES 71 Refresh on Download for Cognos based Roambi Reports 73 Liferay Portal 73 Configuring Roambi ES for Liferay Portal 73 Configuring the Liferay Portal 74 Adding the Liferay Portal 75 Microsoft SharePoint 76

4 Installing the SSRS Plugin in Microsoft SQL Server for Integrated Mode (Optional) 76 Configuring a Microsoft SharePoint Portal 76 Creating a Working Folder in SharePoint for Roambi Flow 78 Microsoft SQL Server Analysis Services (SSAS) 78 Configuring HTTP Access on IIS 78 Configuring a SSAS Portal in Roambi ES 78 Microsoft SQL Server Reporting Services (SSRS) 79 Installing the Roambi Reporting Services Plugin for Microsoft SQL Server 2008/ Configuring Roambi with Microsoft SharePoint 2010 and Reporting Services 2012 in Integrated Mode 81 Configuring a Microsoft SQL Server Reporting Services Portal in Roambi 82 QlikView 84 SAP BusinessObjects 85 Configuring the Application for SAP BusinessObjects 85 Installing the BOE Connector JAR file for Roambi 87 Configuring Windows AD Authentication with BOE 87 Configuring Trusted Authentication with BOE 89 Configuring SiteMinder and Trusted Authentication with BOE 91 Configuring the BOE XI 3.1 SAP Integration Kit with Roambi (BOE XI 3.1 and BOE XI 4.0) 94 Creating a Working BOE Directory for Roambi 94 Configuring an SAP BusinessObjects Portal 95 Chapter 8: Roambi ios Simulator 97 About the Roambi ios Simulator 98 Preparing to Install the Roambi ios Simulator 98 Joining the Apple ios Developer Program 98 Preparing to Install the ios SDK or Xcode 98 Installing ios SDK 5 on Mac OS X 10.6 or Xcode Installing ios SDK 5 on Mac OS X 10.7 or Xcode Installing ios SDK 6 on Mac OS X x Yosemite or Xcode 6.x 99 Installing the Roambi ios Simulator 99 ZIP File Structure for Roambi Analytics Visualizer Simulator 99 ZIP File Structure for Roambi Flow Simulator 100 Installing the Simulator 100 Installing the Simulator on Mac OS x Yosemite 100 Starting the Roambi ios Simulator 102 Starting the Roambi ios Simulator with Xcode 4.2 or Older 102 Starting the Roambi ios Simulator on Mac OS X 10.7 Lion 102 Chapter 9: Validating the Roambi Installation 104 Validation Checklist for Roambi ES 104 Roambi Publisher 104 Roambi Flow Publisher 104 Mobile Devices 105 Troubleshooting 105 License Key 105 MacOS X 106 MySQL 106

5 Chapter 10: Roambi ESX 107 About Public Portals 107 Important Notes About Public Portals 107 Adding a Public Portal 108 Adding Authentication Credentials to a Public Portal 109 Configuring a Public Portal 111 Enabling a Public Portal 113 Publishing Roambi Files to Public Portals 113 Appendix A: Deploying Roambi ES on JBoss 115 Downloading JBoss 115 Installing JBoss 115 Modifying JBoss Initialization Parameters 115 Changing the JBoss Connector Maximum Post Size 116 Deploying Roambi ES on JBoss 116 Completing the Configuration 116 Appendix B: Deploying Roambi ES on WebLogic 117 Installing the Java Persistence API 117 Deploying Roambi ES on WebLogic 117 Using the Admin Console 117 Appendix C: Installing Tomcat Manually on Linux 119 Downloading Tomcat 119 Installing Tomcat 119 Modifying Tomcat Initialization Parameters 119 Disabling Tomcat Watched Resources 120 Changing the Tomcat Connector Max Post Size 120 Appendix D: Configuring Roambi ES to Use a SQL Server Database 121 Installing Microsoft SQL Server 121 Configuring Microsoft SQL Server 121 Configuring Tomcat 122 Configuring JBoss 122 Configuring WebLogic 123 Creating the JDBC Data Source 123 Appendix E: Configuring Roambi ES to Use Kerberos 125 Enabling Kerberos for Your Application Server 125 Appendix F: Adding a Bypass URL for Roambi Flow 129 Appendix G: SAP BusinessObjects JAR File Requirements 130 SAP BusinessObjects XIR 2.X 131 SAP BusinessObjects XIR SAP BusinessObjects XIR 3.X 132 SAP BusinessObjects XIR 4.0 (SP2 Patch 11) 133 SAP BusinessObjects XIR 4.0 (SP2 Patch 12) 137 SAP BusinessObjects XIR 4.0 (SP2 Patch 14) 141 SAP BusinessObjects XIR 4.0 (SP4) 145 SAP BusinessObjects XIR 4.0 (SP5) 149 SAP BusinessObjects XIR 4.0 (SP6) 153 SAP BusinessObjects XIR 4.0 (SP7 Patch 1) 157 SAP BusinessObje 161 SAP BusinessObjects XIR

6 SAP BusinessObjects XIR 4.1 (SP1) 165 SAP BusinessObjects XIR 4.1 (SP2), (SP3), (SP4), (SP5), (SP6) 169

7 Preface This preface introduces you to the SAP Roambi ES5 & ESX Installation Guide. It provides you with a list of chapters with an overview of the information each chapter contains. In addition, it includes a list of the document conventions used in this guide, as well as a selected list of other pertinent Roambi Analytics documentation. About this Guide This guide describes the SAP Roambi ES installation process. It provides detailed system requirements and step-by-step instructions for installing both the prerequisite software and Roambi ES on supported versions of Windows and Linux. Intended Audience This guide is intended for technology professionals who will be responsible for planning, deploying and securing Roambi ES in your corporate environment. In order to get the most out of this document, readers will require a strong understanding of Windows and/or Linux. In addition, readers should will require understanding from an IT-perspective with relational databases, Business Intelligence (BI) systems, authentication methods, and network and data security. Using this Guide This document is divided into the following chapters: l Chapter 1: Getting Started. This chapter introduces you to Roambi ES. It provides an overview about the Roambi Enterprise Server and includes a list of system requirements. It also summarizes the installation process. l Chapter 2: Installing the Prerequisite Software on Windows. This chapter describes how Roambi ES relies on several prerequisite software applications. You must install these prerequisites on Windows before installing the Roambi ES application on the server. l Chapter 3: Installing Roambi ES on Windows. This chapter provides instructions for installing and deploying Roambi ES on Windows. l Chapter 4: Installing Roambi ES on CentOS, RedHat, and Oracle Linux. This chapter provides a very concise procedure to install Roambi ES on RedHat based Linux distributions

8 Preface l Chapter 5: Installing Roambi ES on Ubuntu. This chapter details the process for installing Roambi ES for Linux distributions using the Debian (DEB) Package Manager, such as Ubuntu. l Chapter 6: Installing Roambi ES on OpenSUSE. This chapter details the process for installing Roambi ES for Linux distributions using OpenSUSE. l Chapter 7: Configuring Roambi ES Portals. This chapter discusses how to add and configure portals for the BI tools supported by Roambi. l Chapter 8: Roambi ios Simulator. This chapter provides instructions for installing and starting the Roambi ios Simulator: l Chapter 9: Validating the Roambi Installation. This chapter provdies a checklist that you can use to validate your Roambi ES installation. l Chapter 10: Roambi ESX. This chapter discusses features and functionality that are only available in Roambi ESX. This document also includes the following appendices: l Appendix A: Deploying Roambi ES on JBoss. Provides instructions for deploying Roambi ES on JBoss. l Appendix B: Deploying Roambi ES on WebLogic. Provides instructions for deploying Roambi ES on WebLogic. l Appendix C: Installing Tomcat Manually on Linux. Provides step-by-step instructions for manually installing Tomcat on Linux. l Appendix D: Configuring Roambi ES to Use a SQL Server Database. Provides instructions for configuring a Microsoft SQL Server database for organizations that choose to use SQL server instead of MySQL. l Appendix E: Configuring Roambi ES to Use Kerberos. Provides instructions for configuring Kerberos authentication on the Application Server. l Appendix F: Adding a Bypass URL for Roambi Flow. Provides instructions setting up a Bypass URL for Roambi ES configurations including SSL, SSO, and/or a Reverse Proxy

9 Chapter 1: Getting Started This chapter introduces you to SAP Roambi ES. It provides an overview about the Roambi Enterprise Server and includes a list of system requirements. It also summarizes the installation process. Included in this chapter: l Roambi ES Overview l About the Installation Process l System Requirements Roambi ES Overview The SAP Roambi Enterprise Server (ES) is a Java-based web application that runs on Windows, Linux and Mac OS X. Roambi ES enables you to create dashboard-style Roambi analytics for mobile devices. Roambi integrates with the following Business Intelligence (BI), cube, and portal data sources: IBM Cognos Liferay Portal Microsoft SQL Server Analysis Services Microsoft SQL Server Reporting Services Microsoft SharePoint SAP BusinessObjects The SAP Roambi ES5 Installation Guide explains how to install all prerequisite software, install Roambi ES, and perform post-installation configuration steps that are specific to your BI tool. Roambi Flow is an information publishing platform that is available for purchase with the Roambi Enterprise Server. Roambi Flow enables users to easily create dynamic reports that embed Roambi analytics and that can be shared on the ipad. If your Roambi license agreement includes a Roambi Flow license, Roambi Flow will be automatically installed with the Roambi server. Roambi Flow requires that each Flow user has a separate account Chapter 1: Getting Started

10 About the Installation Process Before installing SAP Roambi ES, you will install several prerequisite software components. Then, you deploy the Roambi ES WAR file to an application server. Once deployed, you will perform additional configuration steps to customize Roambi ES for your BI portals. The chapters in this document provide instructions for each step of the installation process: 1. Review the system requirements and verify that your systems meet these requirements. 2. Install the prerequisite software on the server: a. Install the Java platform. b. Install the application server platform. c. Install MySQL or Microsoft SQL Server as the metadata repository. d. Install Apache OpenOffice and wkhtmltoimage. 3. Install and configure Roambi ES: a. Install the Roambi ES application. b. Deploy the Roambi WAR file to your application server. c. Configure the database drivers. d. Configure the OpenOffice API. e. Create the database. f. Run the Roambi Configuration Wizard from a web browser. g. Perform any additional configuration steps for your BI tool: Install API dependencies Configure communication ports Adjust security 4. Use the Administrator's Console to set up the portals for the BI tools to be used with Roambi. System Requirements For the latest information on system requirements and technical prerequisites, refer the PAM here. SAP Americas Proprietary and Confidential

11 Chapter 2: Installing the Prerequisite Software on Windows This chapter describes how SAP Roambi ES relies on several prerequisite software applications. You must install these prerequisites on Windows before installing the Roambi ES application on the server. Included in this chapter: l Installing Java l Installing Tomcat l Installing MySQL l Installing OpenOffice l Installing wkhtmltoimage Installing Java Roambi ES requires the installation of both the 32-bit Java Runtime Engine (JRE) and the 64-bit Java Development Kit (JDK). Download both installers from the Oracle web site: The following topics describe how to install the JRE and JDK for Windows. Installing the JRE Roambi ES requires the 32-bit Java Runtime Engine (JRE) during the installation process or whenever an upgrade is required. To install the JRE on Windows: 1. Download the latest Windows Offline 32-bit JRE installer from the above link. 2. Using an account with the appropriate administrative permissions, run the JRE installer. 3. Follow the on-screen prompts, and accept all defaults to install the JRE

12 Chapter 2: Installing the Prerequisite Software on Windows Installing the JDK Roambi ES requires the 64-bit Java Development Kit (JDK) to run the application server. To install the JDK on Windows: 1. Download the latest Windows 64-bit JDK installer from the above link. 2. Using an account with the appropriate administrative permissions, run the JDK installer. 3. Follow the on-screen prompts, and accept all defaults to install the JDK. Installing Tomcat Roambi ES requires a Java application server. This topic presents detailed instructions on how to install and configure Tomcat for Roambi ES. Tomcat is an open source software implementation of the Java Servlet and JavaServer Pages technologies. Note: If you choose to install JBoss or WebLogic, instead of Tomcat, refer to the appropriate vendor's web site for installation instructions. Downloading Tomcat You may download the version that best fits your requirements from the Apache Software Foundation at: l Version 6.0.x: l Version 7.0.x: Installing Tomcat To install Tomcat on Windows, download the EXE installer file. After downloading the file, double-click the EXE and follow the Tomcat Installation Wizard using the default settings. Note: Double check Tomcat installer correctly chose the 64-bit jvm.dll file during the Java configuration step. Note: Tomcat is installed as a Windows service under the name: Apache Tomcat <Version> Modifying the Tomcat Memory Settings To configure the Java memory settings in Tomcat in Windows: 1. Go to Start > All Programs > Apache Tomcat > Configure Tomcat to open the Tomcat Properties window

13 Installing Tomcat 2. On the Tomcat Properties window, click the Java tab: 3. Set the initial and maximum memory pool to these values: 4GB If your server memory is... 8GB (or larger) Enter these values in MB... Initial Memory Pool: 2048 Maximum Memory Pool: 2048 Initial Memory Pool: 4096 Maximum Memory Pool: 4096 SAP does not recommend setting values greater than 4096 MB. Instead, consider using a scale out strategy. 4. In Java Options, scroll down to the bottom of the list and add the following two lines, depending upon the size of your system. If your server memory is... 4GB 8GB (or larger) -XX:MaxPermSize=256m -XX:PermSize=256m -XX:MaxPermSize=512m -XX:PermSize=512m 5. Click OK to close the Tomcat Properties window. Add these lines... SAP Americas Proprietary and Confidential

14 Chapter 2: Installing the Prerequisite Software on Windows Disabling Tomcat Watched Resources Tomcat monitors specific static resources. By default, these watched resources are each web application context file (web.xml). Note: You must disable the default watched resources behavior as Tomcat will automatically reload the context file whenever it changes. This behavior can both negatively impact performance and cause fatal behavior for Roambi ES libraries. To disable the watched resources behavior: 1. Navigate to the [ApplicationServer]\conf\ directory. 2. Open [ApplicationServer]\conf\context.xml in a text editor. 3. Locate and comment out the WatchedResources element as shown: <!--<WatchedResource>WEB-INF/web.xml</WatchedResource> --> 4. Restart the Tomcat application service. Changing the Tomcat Connector Max Post Size Roambi requires an increase on Tomcat's default maxpostsize attribute in the connector definition. To increase the maxpostsize: 1. Navigate to the [ApplicationServer]\conf directory. 2. Open the [ApplicationServer]\conf\server.xml file in a text editor. 3. Locate the XML <connector> tag on port Add the attribute: maxpostsize=" " Installing MySQL Roambi ES requires a relational database to store administrative data. This section provides instructions for installing a MySQL Server database. Note: If you will be using a Microsoft SQL Server database, skip this section. Included in this section: l Downloading MySQL l Installing MySQL l Running the Configuration Wizard l Increasing the Maximum Allowed Packet Size Downloading MySQL Download the Windows 64-bit MySQL Server MSI installer at:

15 Installing MySQL Note: If you are running MySQL 5.5.x and for any reason need to uninstall and then reinstall the server, you will need to manually delete the existing /programdata/mysql directory before reinstalling the server or the server will not start successfully. Installing MySQL To install and configure MySQL: 1. Double-click the MSI installer to start the Setup Wizard. 2. Click the Next button to go to the License Agreement screen. 3. Accept the license agreement and click Next to go to the Setup Type screen. SAP Americas Proprietary and Confidential

16 Chapter 2: Installing the Prerequisite Software on Windows 4. On the Setup Type screen, choose Typical and click Next to proceed to the Ready to Install screen. 5. On the Ready to Install screen, click the Install button to start the installation. 6. Wait for the installation process to complete and click Next as prompted until you reach the Wizard Completed screen. 7. On the Wizard Completed screen, leave the Configure the MySQL Server now box checked and click Finish

17 Installing MySQL After you click Finish, the Server Instance Configuration Wizard automatically starts. Running the Configuration Wizard The Configuration Wizard helps initially setup the MySQL server instance. During this step, you define, among others, the MySQL port and the root account password. 1. On the Welcome screen, click Next to choose a configuration maintenance option. 2. Click Next to go to the configuration type choices. SAP Americas Proprietary and Confidential

18 Chapter 2: Installing the Prerequisite Software on Windows 3. From the configuration type options, choose Detailed Configuration and click Next to select a server type. 4. Select one of these server type options: If MySQL will be running on a development system, choose Developer Machine. This is not recommended. If MySQL will be running on the Roambi server, choose Server Machine. If MySQL will be running on a dedicated system, choose Dedicated MySQL Server Machine

19 Installing MySQL 5. On the server type screen, choose the appropriate server type for your setup and click Next to specify the database usage type. 6. For Roambi ES, choose the Transactional Database Only option and click Next to proceed to the datafile settings screen. SAP Americas Proprietary and Confidential

20 Chapter 2: Installing the Prerequisite Software on Windows 7. Leave the datafile settings as the default settings and click Next to select an option for concurrent connections

21 Installing MySQL 8. From the concurrent connections options, choose the default Decision Support (DSS) /OLAP option unless you know that you will need a different configuration option for your organization. Click Next to select networking options. 9. Leave the networking options settings as their default values and click Next to select the default character set. SAP Americas Proprietary and Confidential

22 Chapter 2: Installing the Prerequisite Software on Windows 10. From the list of default character set options, choose Best Support for Multilingualism and click Next to select Windows options

23 Installing MySQL 11. On the Windows options screen, check the Include Bin Directory in Windows PATH so the client tools can easily be called from the command line. Click Next to set up the security options for MySQL. 12. On the security options screen, create a password for the root account for MySQL Server. Click Next to complete the configuration. SAP Americas Proprietary and Confidential

24 Chapter 2: Installing the Prerequisite Software on Windows 13. On the Ready to execute screen, click Execute, then wait for the configuration process to complete and click Finish. Note: MySQL is installed as a Windows service, under the name My SQL. Increasing the Maximum Allowed Packet Size In order to support SAP Roambi ES and Roambi Flow, you must increase the maximum allowed packet size for MySQL to 30MB. To increase the maximum allowed packet size for MySQL: 1. Open the Services window. 2. Right-click the MySQL Server and choose Properties > MySQL Service. 3. Identify the default file MySQL is using under Path to Executable

25 Installing OpenOffice The full path to the file appears after the --defaults-file parameter. 4. Open the file in a text editor. 5. Under the [mysqld] group, change the value of the max_allowed_packet parameter to 30M. Depending on your version of MySQL, your my.ini file might not contain this parameter. If your my.ini file does not contain this parameter,manually add the line max_allowed_ packet=30m to the file. This parameter should be added to the [mysqld] group. 6. Save your changes. 7. Restart the MySQL service. Installing OpenOffice SAP Roambi ES requires Apache OpenOffice to convert Microsoft Excel files to Roambi visualizations. To install OpenOffice: 1. Download the Apache OpenOffice Windows Intel en-us MSI installer from: SAP Americas Proprietary and Confidential

26 Chapter 2: Installing the Prerequisite Software on Windows You can alternatively use the archive link at: 2. Double-click the MSI to start the installation process. 3. Choose custom install, and ONLY select the OpenOffice Calc component. 4. Accept all other defaults. Installing wkhtmltoimage SAP Roambi ES requires the wkhtmltoimage program to support the conversion of PDF documents in Roambi Flow. It is strongly recommended that you always install this program on the Roambi server, whether or not you plan to use Roambi Flow. To install wkhtmltoimage on Windows: 1. Download the wkhtmltoimage EXE file: 2. Double-click the EXE file to install the wkhtmltoimage software. Use the default settings

27 Chapter 3: Installing and Deploying SAP Roambi ES on Windows This chapter provides instructions for installing and deploying Roambi ES on Windows. Included in this chapter: l Overview l About the Files Included with the Installation l Installing Roambi ES l Deploying Roambi ES on Tomcat l Configuring the Database Drivers l Configuring the OpenOffice API l Configuring the NTLM HTTP Filter (Optional) l Creating the Roambi Database l Running the Roambi Configuration Wizard Overview

28 After completing the steps described in the previous chapter, Installing the Prerequisite Software, you can install the SAP Roambi ES software on the application server. The following list provides an overview of the installation steps for Roambi ES: 1. Install the Roambi ES software on the application server. 2. Deploy the Roambi WAR file to the application server. 3. Configure the third-party Java libraries. 4. Create a Roambi repository. 5. Run the Roambi Configuration Wizard from a web browser. 6. Make the appropriate changes to the application server in order to connect to the required BI tools. Note: You might need to restart Tomcat several times during the configuration process. Go to Start > Control Panel > Administrative Tools > Services. The Tomcat application server runs under the service name Apache Tomcat <VERSION>. Installing Roambi ES When you purchased Roambi ES, you should have received an containing a link to download the software and the software license key. Click the link to download the Roambi ES installation package to your computer. To install the Roambi ES software on Windows:

29 Installing Roambi ES 1. Double-click the downloaded.exe file for Roambi to start the Setup Wizard. 2. Click the Next button to proceed to the License Agreement screen. 3. Accept the license agreement, and click Next to go to the Select Destination Directory screen. SAP Americas Proprietary and Confidential

30 Chapter 3: Installing and Deploying Roambi ES on Windows 4. Specify the Destination directory for the installation and click Next. SAP recommends creating a new directory for each version of Roambi ES that you install to preserve older versions. Include the version number in the path, for example, C:\Program Files\RoambiES You can easily identify the version number at the top-right of the dialog box title. The Setup Wizard extracts a series of files to the specified destination directory. When the files have been successfully extracted, the wizard displays a Completion screen. 5. Click Finish to complete the installation and exit the Setup Wizard. After installing the Roambi ES software, deploy the application and customize it for your backend BI system. Deploying Roambi ES on Tomcat Use the instructions below to deploy Roambi ES on Tomcat. Note: To deploy Roambi ES on JBoss or WebLogic, see Appendix A: Deploying Roambi ES on JBoss or Appendix B: Deploying Roambi ES on WebLogic. After installing the Roambi ES software, you must deploy the WAR file to Tomcat, and copy any required third-party libraries to the Roambi ES deployment folder. 1. Navigate to the directory where you installed Roambi ES. On Windows, the default location for Roambi is C:\Program Files(x86)\RoambiES-X.Y.ZZZZZ Where X.Y.ZZZZZ is the Roambi ES version number

31 Configuring the Database Drivers 2. Make a backup copy of the roambi-es-4.x.war file. 3. Rename the copy to roambi.war. 4. Move the roambi.war file to the Tomcat deployment folder at [ApplicationServer] Caution: /webapps. If the target folder contains a previous deployment, you must move the previous deployment's WAR file and deployment folder to an archive location. It is critical to note that Roambi ES must not be deployed with any other Roambi ES application on the same application server, as this scenario can potentially corrupt both deployments. 5. Start Tomcat (if it is not running). You can monitor the deployment progress using Windows Task Manager. Note: If you deploy Roambi ES to a location other than ROOT, the Roambi favicon.ico will not display in the web browser. To enable the Roambi favorite icon, copy the favicon.ico file under {ApplicationServer} /webapps/[roambicontext] and overwrite the file that exists in [ApplicationServer]/webapps/ROOT. Note: The remaining of this chapter will refer to Roambi deployment location as [RoambiDeployment]. Configuring the Database Drivers Installing the MySQL Connector Install the MySQL connector driver so that the Application Server can communicate with MySQL. To install the MySQL driver connector: 1. Download the driver file for MySQL: 2. Extract the downloaded file and copy the MySQL JAR file (mysql-connector-java bin.jar) to the Roambi \lib directory at: [RoambiDeployment]\WEB-INF\lib You should now be able to use MySQL as a repository for Roambi ES. Installing the Microsoft SQL Server Connector To install the jtds driver for Microsoft SQL Server: 1. Download the jtds driver for SQL Server (other drivers are not supported): 2. Extract the downloaded file and copy the jtds JAR file (jtds jar) to the Roambi lib directory at: SAP Americas Proprietary and Confidential

32 Chapter 3: Installing and Deploying Roambi ES on Windows [Application Server]\lib Note: In JBoss, this is the \lib folder under a particular JBoss configuration. In WebLogic, this is the \lib folder under a particular WebLogic domain. To complete the integration of Microsoft SQL Server with your Application Server, refer to Appendix D: Configuring Roambi ES to Use a SQL Server Database. Configuring the OpenOffice API 1. Copy the following API files from the OpenOffice installation directory to Roambi lib at: [RoambiDeployment]\WEB-INF\lib List of API Files: [OpenOffice]\ure\share\java\juh.jar [OpenOffice]\ure\share\java\jurt.jar [OpenOffice]\ure\share\java\ridljar [OpenOffice]\basis\program\classes\unoil.jar 2. Update the openoffice.properties file, if necessary. You do not need to make any changes unless you installed OpenOffice to a location other than the default installation directory. If you installed OpenOffice in a different location, you need to update the openoffice.properties file for your application server with the new location: a. Navigate to: [ApplicationServer]\webapps\[RoambiContex t]\web- INF\classes\com\mellmo\roambi\data\plugin s\ooexcel b. Open the openoffice.properties file in a text editor. c. Under #OpenOffice location, uncomment the line for Windows by deleting the # symbol, and type the appropriate path for OpenOffice. Note: Even though the common convention for Windows is to use backslashes, for this path, the slashes must be forward slashes. Edit the default path if necessary. The following example path shows the correct format for Windows: C:/OpenOffice/OpenOffice.org 3/program/soffice.exe Configuring the NTLM HTTP Filter (Optional) Roambi uses two different NTLM provider implementations. You may need to install this library if connecting against a backend system using the NTLM protocol. It is recommended that you only install this library if you encounter authentication issues. To install the filter:

33 1. Download the jcifs jar file:

34 Creating the Roambi Database 2. Copy the jcifs jar file to: [RoambiDeployment]\WEB-INF\lib Creating the Roambi Database This procedure details how to create a MySQL database for Roambi ES. If you plan to use Microsoft SQL Server, refer to Appendix D: Configuring Roambi ES to Use a SQL Server Database. To create a MySQL database: 1. Open the Windows CMD line and execute the command below: mysqladmin -u root -p create roambi This creates a database named: "roambi" Note: MySQL is case sensitive. Avoid mixing upper and lowercase in the database name to avoid confusion later on. The MySQL client utility, although running in text mode, is a full-feature client for MySQL that is useful when performing troubleshooting activities. You also have the option to use MySQL Workbench, if you don't feel comfortable with the Windows CMD line. In order to quickly check the database was correctly created: 1. Open the Windows CMD line and execute the command below to start the MySQL client: mysql -u root -p 2. From the MySQL client console: show databases; Note: You should get a response with all existing databases. If you do not, verify that the database named "roambi" exists. 3. Type exit to quit the MySQL console and return to the Windows CMD line. Running the SAP Roambi ES Configuration Wizard To run the Roambi ES Configuration Wizard: 1. In a web browser, navigate to the Roambi Server URL: Note: By default, Tomcat uses port The Roambi ES Server Setup Page appears. You are prompted to ensure that a valid license file exists. SAP Americas Proprietary and Confidential

35 Chapter 3: Installing and Deploying Roambi ES on Windows 3. Copy a valid Roambi ES license file to the path presented on the screen. Depending upon how you copy the license file to the folder, Windows may block, encrypt or compress the file. If this occurs, right-click it and choose Properties. Then, under the General tab, follow the appropriate tip: To unblock the file: Click the Unblock button. Then, click Apply in the Properties sheet. To decrypt the file: Click the Advanced button and then remove the checkmark from the Encrypt option. Then, click OK to close the Advanced dialog box and click Apply in the Properties sheet. To decompress the file: Click the Advanced button and then remove the checkmark from the Compress option. Then, click OK to close the Advanced dialog box and click Apply in the Properties sheet. 4. Copy the following files from the wkhtmltoimage installation folder and then paste them to the same folder where you copied the license key. wkhtmltoimage.exe libgcc_s_dw2-1.dll ssleay32.dll libeay32.dll mingwm10.dll 5. Click the Check File button to validate the license. Click Continue. 6. Click Continue. The Database Setup options appear

36 Running the Roambi ES Configuration Wizard 7. From the Database Type list, choose MySQL (or Microsoft SQL Server, if applicable). If you choose Microsoft SQL Server, skip step 8-9 and continue with step Click Continue. The Database Setup options appear. 9. Enter the setup information as follows: a. In the Database Type list, choose MySQL. b. In the Database Host box, type: localhost c. In the Database Name box, type: roambi d. In the Database User box, type: root e. In the Database Password box, enter the password for the account. 10. Click Save Settings. SAP Americas Proprietary and Confidential

37 Chapter 3: Installing and Deploying Roambi ES on Windows The Setup Database button appears. This procedure assumes you do not have an empty database. If this is not the case, SAP strongly recommends that you create a backup. 11. Click Setup Database. After the database setup is complete, the Company Information options appear. 12. Enter the Company Information as follows: a. In the Company Name box, type your organization name. b. In the Company Domain box, type your organization's domain name. 13. Click Save Settings. The Administrator Account Information options appear

38 Running the Roambi ES Configuration Wizard 14. Enter the Administrator Account information: a. First Name: Type the first name of the administrator. b. Last Name: Type the last name of the administrator. c. Administration Type the address for the administrator account. d. Administrator Password. Define the password for the administrator account. e. Confirm Password. Confirm the administrator account password. 15. Click Create Account. When the Wizard completes, the Roambi Login page appears. SAP Americas Proprietary and Confidential

39 Chapter 3: Installing and Deploying Roambi ES on Windows 16. Type the administrator account information in the Username and Password boxes. Then, click Login. The Add Portal page appears. 17. Click Add Portal. Refer to Chapter 7 to learn more about adding portals and how to configure Roambi against the supported backed BI systems

40 Chapter 4: Installing SAP Roambi ES on CentOS, RedHat, and Oracle Linux This chapter provides a very concise procedure to install SAP Roambi ES on RedHat based Linux distributions. Note: A seasoned Linux Administrator always considers the consequences before running a command. This is an important rule to apply here. Although Chapter 2 and Chapter 3 detail the Roambi ES installation on the Windows platform, it is strongly recommended that you review these chapters for insight into the installation process. Included in this chapter: l Installing the Java Runtime Enviroment (JRE) l Installing Apache OpenOffice l Installing Tomcat l Installing MySQL l Installing wkhtmltoimage l Installing Roambi ES Installing the Java Runtime Environment (JRE) Use this procedure to download the latest version of the Sun Java Runtime Environment (JRE) 1.7 from the Oracle web site, install it to the standard Linux JRE location, and to make it the default one. To install the required JRE: 1. Navigate to the Oracle Java SE download page: 2. Select the JRE download. 3. Accept the terms of the License Agreement

41 Chapter 4: Installing Roambi ES on CentOS, RedHat, and Oracle Linux 4. Download the Linux x64 tarball to the /tmp directory. 5. Open the Terminal (ensure there is no other JRE tarball in the /tmp directory). Then, run: cd /tmp JAVA_HOME=/usr/lib/jvm/sunjre x86_64 tar -xvf /tmp/jre* sudo mkdir -p ${JAVA_HOME} sudo mv /tmp/jre*/* ${JAVA_HOME} sudo update-alternatives --install /usr/bin/java java ${JAVA_HOME} /bin/java 1 sudo update-alternatives --set java ${JAVA_HOME}/bin/java Installing Tomcat 6 You have two options to install Tomcat on Linux. You can leverage the package management system or download and extract the.tar.gz file. If you choose to leverage the package management system, use the procedure below to install Tomcat 6 from the Linux RPM repository, change the memory settings, change the connector maxpostsize attribute, and disable Tomcat watched resources. Note: Bear in mind that RedHat 5.x and similar only provide Tomcat 5 through the official repositories. You have to download the.tar.gz in this scenario as Roambi ES is not compatible with Tomcat 5. Note: If you choose to manually install Tomcat, see Appendix C: Installing Tomcat Manually on Linux. To install Tomcat 6: 1. Open the Terminal and run this to install Tomcat : sudo yum install tomcat6 2. In the Terminal, run these commands to change the memory settings: JAVA_MEM_SIZE=2 048m JAVA_HEAP_SIZE= 512m sudo service tomcat6 stop sudo echo "

42 JAVA_OPTS=\"\${JAVA_OPTS} -Djava.awt.headless=true -server -Xmx${JAVA_ MEM_SIZE} -Xms${JAVA_MEM_SIZE} -XX:MaxPermSize=${JAVA_HEAP_SIZE} -

43 Installing MySQL Server XX:PermSize=${JAVA_HEAP_SIZE}\" " >> /etc/tomcat6/tomcat6.conf 3. Open /etc/tomcat6/server.xml in a text editor. a. Find the XML <connector> tag on port b. Add the attribute: maxpostsize=" " 4. Open /etc/tomcat6/context.xml in a text editor. 5. Find the XML <watchedresources> tag and comment it out using XML standard open (<!--) and close (-->) comment tags. 6. If the firewall service is running, enable Tomcat port in iptables: a. Open /etc/sysconfig/iptables in a text editor. b. Add a new rule with this entry: -A INPUT -m state --state NEW -m tcp -p tcp --dport j ACCEPT Installing MySQL Server Use this procedure to install MySQL 5.1 from the Linux RPM repository, secure the MySQL installation, increase the MySQL maximum allowed packet size, and to create the Roambi database and user. To install MySQL Server: 1. Open the Terminal and run this command to install MySQL: sudo yum install mysql-server 2. In the Terminal, run this command to secure MySQL: sudo service mysql start sudo /usr/bin/mysql_secure_installation 3. Open /etc/mysql/my.cnf in a text editor. 4. Find the attribute max_allowed_packet under [mysqld] group and increase its value to 30M. Add a new attribute pair/value line if it doesn t exist. 5. Open the Terminal and create the Roambi database and user by running: MYSQL_ROAMBI_DATA=r oambi MYSQL_ROAMBI_USER=r oambi MYSQL_ROAMBI_PASS=r oambi echo "

44 create database ${MYSQL_ROAMBI_DATA}; grant all on ${MYSQL_ROAMBI_ DATA}.* to identified by '${MYSQL_ROAMBI_ PASS}'; SAP Americas Proprietary and Confidential

45 Chapter 4: Installing Roambi ES on CentOS, RedHat, and Oracle Linux " mysql -u root -p Installing OpenOffice Use this procedure to download Apache OpenOffice. Then, install the OpenOffice dependencies and required OpenOffice installation packages. To install Apache OpenOffice: 1. Navigate to the Apache OpenOffice download site: 2. Download the en-us Linux x86-64 RPM tarball to the /tmp directory. 3. Open the Terminal and run: cd /tmp tar --wildcards -xvf /tmp/apache_openoffice_incubating_3.4.?_linux_x86-64_install-rpm_en-us.tar.gz *openoffice.org-ure* *ooobasis3.4-core* *oo-obasis3.4-calc* *ooobasis3.4-images* *openoffice.org3-3.4.* *op-enoffice.org3-calc* *ooobasis3.4-en-us-res* *ooobasis3.4-en-us-3.4* *ooobasis3.4-en-us-calc* sudo yum install freetype libsm libxext sudo rpm -Uvh /tmp/en-us/rpms/*.rpm Installing wkhtmltoimage Use this procedure to download wkhtmltoimage, and install it to the /usr/local/bin directory. 1. Open the Terminal and run to download and install: cd /tmp wget wkhtmltopdf.googlecode.com/files/wkhtmltoimage _rc1-static-amd64.tar.bz2 tar -xvf /tmp/wkhtmltoimage* sudo yum install libxrender fontconfig sudo mv /tmp/wkhtmltoimage-amd64 /usr/local/bin/wkhtmltoimage Installing SAP Roambi ES Use this procedure install Roambi ES to the /opt/roambies directory, deploy the Roambi WAR file to Tomcat, copy the required JAR dependencies to the Roambi WAR lib folder, and configure the.roambi folder.

46 - 48 -

47 Installing Roambi ES It is assumed that both the Roambi ES Linux installer and the Roambi ES license key (es.license) are already in the /tmp directory. Please contact your Account Manager for the download link and license. To install Roambi ES: 1. Open the Terminal and run these to install and deploy. Accept all the defaults but be sure the destination folder is: /opt/roambies chmod +x /tmp/roambies* sudo /tmp/roambies* -c sudo apt-get install unzip sudo unzip /opt/roambies/roambi*.war -d /var/lib/tomcat6/webapps/roambi 2. Open the Terminal and run these to configure the MySQL JDBC driver: cd /tmp wget downloads.mysql.com/archives/mysql-connector-java- 5.1/mysql-con-nector-java tar.gz tar --wildcards -xvf /tmp/mysql-connector-java tar.gz *bin.jar INF/lib sudo mv /tmp/mysql-connector-java /mysql-connectorjava bin.jar /var/lib/tomcat6/webapps/roambi/web- 3. Open the Terminal and run these to configure the OpenOffice connector: sudo cp /opt/openoffice.org/ure/share/java/juh.jar /var/lib/ tomcat6/webapps/roambi/web-inf/lib sudo cp /opt/openoffice.org/ure/share/java/jurt.jar /var/lib/ tomcat6/webapps/roambi/web-inf/lib sudo cp /opt/openoffice.org/ure/share/java/ridl.jar /var/lib/ tomcat6/webapps/roambi/web-inf/lib sudo cp /opt/openoffice.org/basis3.4/program/classes/unoil.jar /var/lib/tomcat6/webapps/roambi/web-inf/lib 4. Open the Terminal and run these to configure the.roambi folder: sudo mkdir /usr/share/tomcat6/.roambi

48 sudo ln -s /usr/local/bin/wkhtmltoimage /usr/share/ tomcat6/.roambi/wkhtmltoimage sudo mv /tmp/es.license /usr/share/tomcat6/.roambi sudo chown -R tomcat:tomcat /usr/share/tomcat6/.roambi /var/lib/ SAP Americas Proprietary and Confidential

49 Chapter 4: Installing Roambi ES on CentOS, RedHat, and Oracle Linux tomcat6/webapps/roambi sudo service tomcat6 start

50 Chapter 5: Installing SAP Roambi ES on Ubuntu This chapter details the process for installing SAP Roambi ES for Linux distributions using the Debian (DEB) Package Manager, such as Ubuntu. Note: A seasoned Linux Administrator always considers the consequences before running a command. This is an important rule to apply here. Although Chapter 2 and Chapter 3 detail the Roambi ES installation on the Windows platform, it is strongly recommended that you review these chapters for insight into the installation process. Included in this chapter: l Installing the Java Runtime Environment (JRE) l Installing Tomcat l Installing MySQL Server l Installing Apache OpenOffice l Installing wkhtmltoimage l Installing Roambi ES Installing the Java Runtime Environment (JRE) Use this procedure to download the latest version of the Sun Java Runtime Environment (JRE) 1.7 from the Oracle web site, install it to the standard Linux JRE location, and to make it the default one. To install the required JRE: 1. Navigate to the Oracle Java SE download page: 2. Select the JRE download. 3. Accept the terms of the License Agreement. 4. Download the Linux x64 tarball to the /tmp directory. 5. Open the Terminal and ensuring there is no other JRE tarball in this folder, run:

51 Chapter 5: Installing Roambi ES on Ubuntu cd /tmp JAVA_HOME=/usr/lib/jvm/sunjre x86_64 tar -xvf /tmp/jre* sudo mkdir -p ${JAVA_HOME} sudo mv /tmp/jre*/* ${JAVA_HOME} sudo update-alternatives --install /usr/bin/java java ${JAVA_HOME} /bin/java 1 sudo update-alternatives --set java ${JAVA_HOME}/bin/java Installing Tomcat 7 You have two options to install Tomcat on Linux. You can leverage the package management system or download and extract the.tar.gz file. If you choose to leverage the package management system, use the procedure below to install the Tomcat 7 from the Linux RPM repository, change the memory settings, change the connector maxpostsize attribute, and disable Tomcat watched resources. Note: If you choose to manually install Tomcat, refer to Appendix C: Installing Tomcat Manually on Linux. To install Tomcat 7: 1. Open the Terminal and run this to install Tomcat: sudo apt-get install tomcat7 2. In the Terminal, run these commands to change the memory settings: JAVA_MEM_SIZE=2 048m JAVA_HEAP_SIZE= 512m sudo service tomcat7 stop sudo echo " JAVA_OPTS=\"\${JAVA_OPTS} -Djava.awt.headless=true -server - Xmx${JAVA_ MEM_SIZE} -Xms${JAVA_MEM_SIZE} - XX:MaxPermSize=${JAVA_HEAP_SIZE} -XX:PermSize=${JAVA_HEAP_SIZE}\"

52 " >> /etc/default/tomcat7 3. Open /etc/tomcat7/server.xml in a text editor. a. Find the XML <connector> tag on port b. Add the attribute: maxpostsize=" "

53 Installing MySQL Server 4. Open /etc/tomcat7/context.xml in a text editor. 5. Find the XML <watchedresources> tag and comment it out using XML standard open (<!--) and close (-->) comment tags. 6. If the firewall service is running, enable Tomcat port in iptables: a. Open /etc/sysconfig/iptables in a text editor. b. Add a new rule with this entry: -A INPUT -m state --state NEW -m tcp -p tcp --dport j ACCEPT Installing MySQL Server Use this procedure to install MySQL 5.1 from the Linux RPM repository, secure the MySQL installation, increase the MySQL maximum allowed packet size, and to create the Roambi database and user. To install MySQL Server: 1. Open the Terminal and run this command to install MySQL: sudo apt-get install mysql-server 2. In the Terminal, run this command to secure MySQL: sudo service mysqld start sudo /usr/bin/mysql_secure_installation 3. Open /etc/mysql/my.cnf in a text editor. 4. Find the attribute max_allowed_packet under [mysqld] group and increase its value to 30M. Add a new attribute pair/value line if it doesn t exist. 5. Open the Terminal and run these to create the Roambi database and user: MYSQL_ROAMBI_DATA=r oambi MYSQL_ROAMBI_USER=r oambi MYSQL_ROAMBI_PASS=r oambi echo " create database ${MYSQL_ROAMBI_DATA}; grant all on ${MYSQL_ROAMBI_ DATA}.* to $ {MYSQL_ROAMBI_USER}@localhost identified by '${MYSQL_ ROAMBI_PASS}'; " mysql -uroot -p

54 Installing OpenOffice Use this procedure to download Apache OpenOffice. Then, run the RPM tarball from Apache to install OpenOffice dependencies and required OpenOffice installation packages. To install Apache OpenOffice: SAP Americas Proprietary and Confidential

55 Chapter 5: Installing Roambi ES on Ubuntu 1. Navigate to the Apache OpenOffice download site: 2. Download the en-us Linux x86-64 RPM tarball to the /tmp directory. 3. Open the Terminal and run the commands: cd /tmp tar --wildcards -xvf /tmp/apache_openoffice_incubating_3.4.?_linux_x86-64_install-deb_en-us.tar.gz *openoffice.org-ure_* *ooobasis3.4-core* *oo-obasis3.4-calc_* *ooobasis3.4- images_* *openoffice.org3_* *op-enoffice.org3-calc_* *ooobasis3.4-en-us-res_* *ooobasis3.4-en-us_* *ooobasis3.4- en-us-calc_* sudo apt-get install libfreetype6 US/DEBS/*.deb Installing wkhtmltoimage Use this procedure to download wkhtmltoimage, and install it to the /usr/local/bin directory. 1. Open the Terminal and run to download and install: cd /tmp wget libice6 libsm6 sudo dpkg -i /tmp/en- wkhtmltopdf.googlecode.com/files/wkhtmltoimage _rc1-static-amd64.tar.bz2 tar -xvf /tmp/wkhtmltoimage* sudo apt-get install libxrender1 libfontconfig1 sudo mv /tmp/wkhtmltoimage-amd64 /usr/local/bin/wkhtmltoimage Installing SAP Roambi ES Use this procedure install Roambi ES to the /opt/roambies directory, deploy the Roambi WAR file to Tomcat, copy the required JAR dependencies to the Roambi WAR lib folder, and configure the.roambi folder. It is assumed that both the Roambi ES Linux installer and the Roambi ES license key (es.license) are already in the /tmp directory. Please contact your Account Manager for the download link and license. To install Roambi ES:

56 1. Open the Terminal and run these to install and deploy. Accept all the defaults but be sure the destination folder is: /opt/roambies

57 Installing Roambi ES chmod +x /tmp/roambies* /tmp/roambies* -c apt-get install unzip unzip /opt/roambies/roambi*.war -d /var/lib/tomcat7/webapps/roambi 2. Open the Terminal and run these to configure the MySQL JDBC tar.gz MYSQL_JDBC} tar --wildcards -xvzf /tmp/${asset_mysql_jdbc} *bin.jar mv driver: cd /tmp ASSET_MYSQL_JDBC=mysql-connector-java- wget downloads.mysql.com/archives/mysql-connector-java- 5.1/${ASSET_ /tmp/mysql-connector-java /mysql-connector-java bin.jar /var/lib/tomcat7/webapps/roambi/web-inf/lib 3. Open the Terminal and run these to configure the OpenOffice connector: cp /opt/openoffice.org/ure/share/java/juh.jar /var/lib/ tomcat7/webapps/roambi/web-inf/lib cp /opt/openoffice.org/ure/share/java/jurt.jar /var/lib/ tomcat7/webapps/roambi/web-inf/lib cp /opt/openoffice.org/ure/share/java/ridl.jar /var/lib/ tomcat7/webapps/roambi/web-inf/lib cp /opt/openoffice.org/basis3.4/program/classes/unoil.jar /var/lib/ tomcat7/webapps/roambi/web-inf/lib 4. Open the Terminal and run these to configure the.roambi folder: sudo mkdir /usr/share/tomcat7/.roambi sudo ln -s /usr/local/bin/wkhtmltoimage /usr/share/ tomcat7/.roambi/wkhtmltoimage sudo mv /tmp/es.license /usr/share/tomcat7/.roambi

58 sudo chown -R tomcat7:tomcat7 /usr/share/tomcat7/.roambi tomcat7/webapps/roambi /var/lib/ sudo service tomcat7 start SAP Americas Proprietary and Confidential

59 Chapter 6: Installing SAP Roambi ES on OpenSUSE This chapter details the process for installing Roambi ES for Linux distributions using OpenSUSE. Note: A seasoned Linux Administrator always considers the consequences before running a command. This is an important rule to apply here. Although Chapter 2 and Chapter 3 detail the Roambi ES installation on the Windows platform, it is strongly recommended that you review these chapters for insight into the installation process. Included in this chapter: l Installing the Java Runtime Environment (JRE) l Installing wkhtmltoimage l Installing Apache OpenOffice l Installing MySQL Server l Installing Tomcat l Installing Roambi ES Installing the Java Runtime Environment (JRE) Use this procedure to download the latest version of the Sun Java Runtime Environment (JRE) 1.7 from the Oracle web site, install it to the standard Linux JRE location, and to make it the default one. To install the required JRE: 1. Navigate to the Oracle Java SE download page: 2. Select the JRE download. 3. Accept the terms of the License Agreement. 4. Download the Linux x64 tarball to the /tmp directory. 5. Open the Terminal and run these command, ensuring there is no other JRE tarball in this folder:

60 Chapter 6: Installing Roambi ES on OpenSUSE cd /tmp JAVA_HOME=/usr/lib/jvm/sunjre x86_64 tar -xvf /tmp/jre* sudo mkdir -p ${JAVA_HOME} sudo mv /tmp/jre*/* ${JAVA_HOME} sudo update-alternatives --install /usr/bin/java java ${JAVA_HOME} /bin/java 1 sudo update-alternatives --set java ${JAVA_HOME}/bin/java Installing Tomcat 6 You have two options to install Tomcat on Linux. You can leverage the DEB Package Manager or download and extract the.tar.gz file. If you choose to leverage the package manager, use the procedure below to install the Tomcat 6 from the Linux RPM repository, change the memory settings, change the connector maxpostsize attribute, and disable Tomcat watched resources. Note: To install Tomcat 6: If you choose to manually install Tomcat, see Appendix C: Installing Tomcat Manually on Linux. 1. Open the Terminal and run this to install Tomcat: sudo zypper install tomcat6 2. In the Terminal, run these commands to change the memory settings: JAVA_MEM_SIZE=2 048m JAVA_HEAP_SIZE= 512m sudo service tomcat6 stop sudo echo " JAVA_OPTS=\"\${JAVA_OPTS} -Djava.awt.headless=true -server - Xmx${JAVA_ MEM_SIZE} -Xms${JAVA_MEM_SIZE} - XX:MaxPermSize=${JAVA_HEAP_SIZE} -XX:PermSize=${JAVA_HEAP_SIZE}\" " >> /etc/tomcat6/tomcat6.conf

61 3. Open /etc/tomcat6/server.xml in a text editor. a. Find the XML <connector> tag on port b. Add the attribute: maxpostsize=" "

62 Installing MySQL Server 4. Open /etc/tomcat6/context.xml in a text editor. 5. Find the XML <watchedresources> tag and comment it out using XML standard open (<!--) and close (-->) comment tags. 6. If the service is running, enable Tomcat port in iptables: a. Open /etc/sysconfig/iptables in a text editor. b. Add a new rule with this entry: -A INPUT -m state --state NEW -m tcp -p tcp --dport j ACCEPT Installing MySQL Server Use this procedure to install MySQL 5.1 from the Linux RPM repository, secure the MySQL installation, increase the MySQL maximum allowed packet size, and to create the Roambi database and user. To install MySQL Server: 1. Open the Terminal and run this command to install MySQL: sudo zypper install mysql-community-server 2. In the Terminal, run this command to secure MySQL: sudo service mysql start sudo /usr/bin/mysql_secure_installation 3. Open /etc/mysql/my.cnf in a text editor. 4. Find the attribute max_allowed_packet under [mysqld] group and increase its value to 30M. Then, add a new attribute pair/value line if it doesn t exist. 5. In the Terminal, create the Roambi database and user: MYSQL_ROAMBI_DATA=r oambi MYSQL_ROAMBI_USER=r oambi MYSQL_ROAMBI_PASS=r oambi echo " create database ${MYSQL_ROAMBI_DATA}; grant all on ${MYSQL_ROAMBI_ DATA}.* to $ {MYSQL_ROAMBI_USER}@localhost identified by '${MYSQL_ ROAMBI_PASS}'; " mysql -uroot -p

63 Installing OpenOffice Use this procedure to download Apache OpenOffice. Then, run the RPM tarball from Apache to install OpenOffice dependencies and required OpenOffice installation packages. To install Apache OpenOffice: SAP Americas Proprietary and Confidential

64 Chapter 6: Installing Roambi ES on OpenSUSE 1. Navigate to the Apache OpenOffice download site: 2. Download the en-us Linux x86-64 RPM tarball to the /tmp directory. 3. Open the Terminal and run the commands: cd /tmp tar --wildcards -xvf /tmp/apache_openoffice_incubating_3.4.?_linux_x86-64_install-rpm_en-us.tar.gz *openoffice.org-ure* *ooobasis3.4-core* *oo-obasis3.4-calc* *ooobasis3.4-images* *openoffice.org3-3.4.* *op-enoffice.org3-calc* *ooobasis3.4-en-us-res* *ooobasis3.4-en-us-3.4* *ooobasis3.4-en-us-calc* zypper install libfreetype6 xorg-x11-libsm xorgx11-libxext sudo rpm -Uvh /tmp/en-us/rpms/*.rpm Installing wkhtmltoimage Use this procedure to download wkhtmltoimage, and install it to the /usr/local/bin directory. 1. Open the Terminal and run to download and install: cd /tmp wget wkhtmltopdf.googlecode.com/files/wkhtmltoimage _rc1-static-amd64.tar.bz2 tar -xvf /tmp/wkhtmltoimage* zypper install xorg-x11-libxrender fontconfig sudo mv /tmp/wkhtmltoimage-amd64 /usr/local/bin/wkhtmltoimage Installing Roambi ES Use this procedure install Roambi ES to the /opt/roambies directory, deploy the Roambi WAR file to Tomcat, copy the required JAR dependencies to the Roambi WAR lib folder, and configure the.roambi folder. It is assumed that both the Roambi ES Linux installer and the Roambi ES license key (es.license) are already in the /tmp directory. Please contact your Account Manager for the download link and license. To install Roambi ES: 1. Open the Terminal and run these to install and deploy. Accept all the defaults but be sure the destination folder is: /opt/roambies

65 - 59 -

66 Installing Roambi ES chmod +x /tmp/roambies* sudo /tmp/roambies* -c sudo apt-get install unzip sudo unzip /opt/roambies/roambi*.war -d /var/lib/tomcat7/webapps/roambi 2. Open the Terminal and run these to configure the MySQL JDBC driver: cd /tmp wget downloads.mysql.com/archives/mysql-connectorjava-5.1/mysql-connector-java tar.gz tar --wildcards -xvf /tmp/mysql-connector-java tar.gz *bin.jar INF/lib sudo mv /tmp/mysql-connector-java /mysql-connectorjava bin.jar /srv/tomcat6/webapps/roambi/web- 3. Open the Terminal and run these to configure the OpenOffice connector: sudo /opt/openoffice.org/ure/share/java/juh.jar /srv/ tomcat6/webapps/roambi/web-inf/lib sudo /opt/openoffice.org/ure/share/java/jurt.jar /srv/ tomcat6/webapps/roambi/web-inf/lib sudo /opt/openoffice.org/ure/share/java/ridl.jar /srv/ tomcat6/webapps/roambi/web-inf/lib cp cp cp sudo /opt/openoffice.org/basis3.4/program/classes/unoil.jar /srv/ tomcat6/webapps/roambi/web-inf/lib 4. Open the Terminal and run these to configure the.roambi folder: cp sudo mkdir /usr/share/tomcat6/.roambi sudo ln -s /usr/local/bin/wkhtmltoimage /usr/share/ tomcat6/.roambi/wkhtmltoimage sudo mv /tmp/es.license /usr/share/tomcat6/.roambi

67 sudo chown -R tomcat:tomcat /usr/share/tomcat6/.roambi tomcat6/webapps/roambi /srv/ sudo service tomcat6 start SAP Americas Proprietary and Confidential

68 Chapter 7: Configuring SAP Roambi ES Portals This chapter discusses how to add and configure portals for the BI tools supported by Roambi. Included in this chapter: l Configuring Roambi ES Portals l Adding New Portals to Roambi ES l Importing Portals from Roambi ES3, ES4 to ES5 l Adding and Deleting Portals l Creating a Roambi Flow Working Directory l Adding and Configuring Portals for the Supported Tools Configuring Roambi ES Portals If you have successfully installed Roambi ES5, connected to the Roambi server with a web browser, and set up the Roambi database using the administrator's console, you can start adding portals for your BI tools. This chapter discusses how to add and configure portals for the BI tools supported by Roambi: Importing portal settings from a previous Roambi ES3, ES4 installation Adding new portals and deleting portals Creating a working directory (Roambi Flow only) Setting the required parameter values for your portals The parameters for each portal vary depending on which BI tool you are using for a data source. In this chapter, the section for each individual BI tool discusses the required parameters and valid values for that tool. Adding New Portals to Roambi ES If you have not previously installed Roambi ES3, ES4 and will be creating new portals for your BI tools, start by creating your first portal from the Add Portal screen. This screen displays just after setting up the Roambi ES Administrator Account and logging in as the Administrator

69 Chapter 7: Configuring Roambi ES Portals If you have previously used Roambi ES3, ES4 and want to import your existing portals, see Importing Portals from Roambi ES3, ES4 to ES5. To create your first BI portal for Roambi ES5: 1. Click the Add Portal button. An Add Portal window opens

70 Adding New Portals to Roambi ES 2. On the Add Portal window, specify the information for the new portal. 3. Click Add. From the Portal Source drop-down list, select the BI tool that will be used as a data source for this portal. In the Portal Name text box, type a unique name for the portal. Roambi creates the portal and displays a dashboard of available portals. The example below shows a dashboard with a single portal for SAP BusinessObjects: SAP Americas Proprietary and Confidential

71 Chapter 7: Configuring Roambi ES Portals Each BI tool has unique configuration parameters required for associated portal. See the individual section for your portal type to learn how to configure the portal after creating it. Importing Portals from Roambi ES3, ES4 to ES5 If you previously used Roambi ES3, ES4 and already have BI portals configured, you can simply import the settings from the XML configuration file used by ES3, ES4 into ES5. Note: You will need a copy of the roambi-settings.xml file used by ES3, ES4 to import your portals to ES5. Start the import process from the Add Portal screen that displays just after setting up the Roambi ES5 administrator account and logging in as the administrator.

72 - 64 -

73 Importing Portals from Roambi ES3, ES4 to ES5 To import your Roambi ES3, ES4 portals into Roambi ES5: 1. On the Add Portal screen, click the click here link that follows the Upgrading from Roambi ES version 3.0 text. An Import Portal Settings window opens: 2. Click the Upload Settings button. SAP Americas Proprietary and Confidential

74 Chapter 7: Configuring Roambi ES Portals A File Upload window opens. 3. Select and upload the roambi-settings.xml file. The Import Portal Settings window displays a Success or Warning message for each portal that you imported. If a portal has a Warning message associated with it, you might need to modify some of the configuration parameters to successfully use that portal with Roambi ES5. 4. Click Close. The Roambi dashboard now displays all of your portals: From the list on the left of the dashboard, you can click on a portal to select it, which displays the portal in the right pane. After you select a portal, you can click the General, Configuration, Security, or Foldersbuttons on the right pane to modify the configuration parameters for the portal. Adding and Deleting Portals If you have at least one portal already created or imported for Roambi ES, you can add more portals or delete a portal from the Roambi dashboard. Adding Portals To add a portal to Roambi ES: 1. Click the Add Portal button in the lower left corner of the dashboard: An Add Portal window opens:

75 Adding and Deleting Portals 2. From the Portal Source drop-down list, select the BI tool that will be used as the data source for the portal. Depending on which portal you choose, the portal may also be used to store RBI files. 3. In the Name text box, type a unique name for the Portal. 4. Click Add. After adding the portal, you will need to configure the portal. Each portal type has different configuration requirements. See the individual section for the new portal type to learn about the configuration parameters for that portal. Important: Roambi ES requires that you have at least one portal with Primary Login enabled. Failure to designate a portal with Primary Login will result in an inability to login from a device. Deleting Portals You can delete a portal by selecting it on the left pane then clicking the Delete Portal button in the lower right corner of the dashboard: SAP Americas Proprietary and Confidential

76 Chapter 7: Configuring Roambi ES Portals Creating a Roambi Flow Working Directory If your organization will be using Roambi Flow, you will need to set up a working directory for each portal after you have created and configured the portal. Roambi uses the working directory to store temporary files for Roambi Flow documents. Any user with Administrator rights can create the working directory for a portal. To create a working directory for a portal for Roambi Flow: 1. On the Administrator's Console, click the Portals tab to display the list of available portals on the left side of the screen. 2. From the list of portals, select the portal that you want to work with. The Console displays the Portal Details: 3. Above the Portal Details, click the Folders tab. The Console displays the Portal Folders:

77 Creating a Roambi Flow Working Directory 4. Under Roambi Flow Working Directory, click the Select Folder button. An Add Working Directory window opens: SAP Americas Proprietary and Confidential

78 Chapter 7: Configuring Roambi ES Portals 5. Browse to the folder that you want to use as a working directory and click Select Folder. The selected folder is now listed as the working directory: 6. In the BI tool that is associated with the portal, you will need to give Roambi Flow users read and write access to this folder on the network. One way to do this would be to set up a Roambi Flow users group within the BI tool, assign Roambi Flow users to that group, and then give the group read and write access to the folder on the network. The following sections contain instructions and recommendations for setting up the working directory for individual BI tools. See the section for your BI tool for detailed instructions on how to best set up this directory. Adding Portals for the Supported Portals and Connectors To learn how to add a portal in Roambi ES to support a specific portal or connector, see a topic below:

79 Adding Portals for the Supported Portals and Connectors l IBM Cognos l Liferay Portal l Microsoft SharePoint l Microsoft SQL Server Analysis Services (SSAS) l Microsoft SQL Server Reporting Services (SSRS) l QlikView l SAP Business Objects IBM Cognos This section discusses the required configuration changes that you must make to use IBM Cognos with Roambi ES. Configuring Roambi ES for IBM Cognos If you will be using an IBM Cognos portal, Roambi ES requires access to specific JAR. The following table lists the files required by Roambi. which varies by IBM Cognos version: IBM Cognos 8.3 Cognos_axis. IBM Cognos 8.4 IBM Cognos 10.x IBM Cognos 11.x 8.3.jar Cognos_axis.8.4.jar Cognos_axis.10.0.jar Cognos_axis.11.0.jar Cognos_client Cognos_client.8.4 Cognos_client jar.jar Cognos_client.10.0.jar.0.jar To configure your application server for IBM Cognos: 1. After installing Roambi ES and copying the Roambi WAR file to the /webapps folder of your application server (see Deploying the Roambi WAR to Tomcat), locate the JAR files that are listed in the table for your version of Cognos. These files should be available in Cognos SDK. 2. Copy the appropriate files to C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\[RoambiInstallation]\WEB-INF\lib or the equivalent folder for your application server. 3. Restart the application server. Configuring an IBM Cognos Portal in Roambi ES An IBM Cognos portal requires that you configure several parameters before the portal can be enabled. To configure an IBM Cognos portal: 1. After creating the portal, click the Configuration tab to display the Cognos configuration parameters:

80 SAP Americas Proprietary and Confidential

81 Chapter 7: Configuring Roambi ES Portals 2. Edit the Portal Parameters: In the Dispatcher URL field, type the URL for the Cognos server that handles the Dispatcher. In the Gateway URL field, type the URL assigned to the portal by the web server. For example, if you use IIS with a gateway named Cognos8, the gateway points to [server_name]/cognos8/cgi-bin/cognos.cgi. (For ISAPI, replace "cognos.cgi" with "cognosisapi.dll".) In the Namespace field, type the Name Space ID for the Authentication provider that is configured in the Security section of Cognos Administration (value is case sensitive). If you are using Cognos v7 "Access Manager" as your namespace, do not specify Access Manager as your namespace in the Roambi Namespace field. Instead, specify the nampespace default, which is the CAMID in Cognos. In the Version field, type the Cognos version. Valid values are 83 (Cognos 8.3), 84 (Cognos 8.4), C10 (Cognos 10.x), C11 (Cognos 11.x). 3. Verify the portal settings as prompted. 4. When the Enable Portal button becomes visible, toggle the button to ON. 5. Optionally, on the Security tab, you can enable the Primary Login. Important: Roambi ES requires that you have at least one portal with Primary Login enabled. Failure to designate a portal with Primary Login will result in an inability to login from a device. 6. If you are using SiteMinder to manage SSO, go to System > Security to select your Single Signon type

82 Adding Portals for the Supported Portals and Con-nectors 7. After configuring the required parameters, click the Folders tab to set up the folders for the portal. Refresh on Download for Cognos based Roambi Reports When using Cognos reports as a source for a Roambi Report with NO refresh, the source Cognos report is always executed on Download, which means the report will be refreshed on the first download. For use cases in which the refresh on download needs to be disabled, please follow the next instructions: Edit the portal.properties file located in <tomcat>/webapps/<roambi_context>/web-inf/classes/portal.properties add the following line to the portal.properties file: cognos.alwaysrefreshondownload=false Save and restart Tomcat. Liferay Portal The topics in this section describe the basic configuration steps for setting up the Liferay Portal and also shows how to add the Liferay Portal to Roambi ES. Configuring Roambi ES for Liferay Portal After installing the application server and deploying the Liferay Portal, the Roambi ES web application requires access to the portal-client.jar file. You can download the JAR file from the Liferay web site: Note: When deploying the Liferay Portal to the application server, the Liferay Portal must run under the ROOT context path so it is available under the >:<Port>/. For example, if you are using Tomcat as the servlet container, the Tomcat /webapps directory should contain a folder named ROOT so that the Liferay Portal is accessible under context path /. To configure your Roambi application server for Liferay Portal: 1. Navigate to the [ApplicationServerDirectory]\webapps\ROOT\WEB-INF\lib directory. SAP Americas Proprietary and Confidential

83 Chapter 7: Configuring Roambi ES Portals 2. Copy the portal-client.jar file located in the above folder to the [ApplicationServerDirectory]/webapps/roambi/WEB-INF/lib directory. 3. Restart the application server. Configuring the Liferay Portal After configuring the Application Server for Liferay Portal, use the Setup Wizard to specify the basic configuration information for the Liferay Portal. To complete the basic configuration information for the Liferay Portal: 1. Launch the Liferay setup wizard by navigating to this URL: Where ServerName is the locale host for your Liferay Portal. 2. Under Portal, enter the Liferay Portal's basic configuration information.: Portal Name: This is the name of the Liferay Portal site. For best results, do not use the IP address as the portal name. Default Language. This is the default local where your portal web site resides. 3. Under Administrator User, enter information for the administrator account: First Name Last Name Address 4. Click Finish Configuration. 5. Enter the Password and set up a security question and answer. 6. In Liferay Portal, go to the Control Panel > Server > Portal Instances. 7. Write down the Web ID. You will need this information when Adding the Liferay Portal to Roambi ES. 8. Choose <Portal Name> > Documents and Media. 9. Click the Home folder and choose Access from Desktop. 10. Write down the WebDAV URL. You will need this information when Adding the Liferay Portal to Roambi ES. 11. Create the initial folder structure for the Liferay Portal. 12. Navigate to the Liferay Home folder and open the portal-wizard.properties file in a text editor. 13. Append the content below to the end of the file: # allows all ip to access axis servlet axis.servlet.hosts.allowed= Note: You also have the option to only add Roambi IP address on the line above.

84 - 74 -

85 Adding Portals for the Supported Portals and Connectors Adding the Liferay Portal A Liferay portal requires that you configure several parameters before the portal can be enabled. To add the Liferay Portal to Roambi ES: 1. Log in to Roambi ES. 2. Under Portals, add a new portal for the Liferay Portal (see Adding New Portals to Roambi ES). 3. Click the Configuration tab. You will enter the Liferay Portal parameters. 4. Under Portal Parameters, enter and save the information that you wrote down in Configuring the Liferay Portal: Web Service URL. This the WebDAV URL for the Liferay Portal. Web ID. The is the ID that was assigned to the Liferay Portal during set up. 5. Under Portal Status, click Verify. 6. When the Enable Portal button becomes visible, toggle the button to ON. SAP Americas Proprietary and Confidential

86 Chapter 7: Configuring Roambi ES Portals 7. When the Enable Portal button becomes visible, toggle the button to ON. 8. (Optional) Click the Security tab and enable the Primary Login option, if desired. Important: Roambi ES requires that you have at least one portal with Primary Login enabled. Failure to designate a portal with Primary Login will result in an inability to login from a device. 9. After the portal parameters are configured, click the Folders tab. Then, set up the folders for the portal. Microsoft SharePoint This section discusses the required configuration changes that you must make to use Microsoft SharePoint with Roambi ES. Installing the SSRS Plugin in Microsoft SQL Server for Integrated Mode (Optional) If you will be using Reporting Services in SharePoint Integrated mode, you will need to also install the SSRS plugin. See Microsoft SQL Server Reporting Services for SSRS installation instructions. Configuring a Microsoft SharePoint Portal A Microsoft SharePoint portal requires that you configure several parameters before the portal can be enabled. To configure a Microsoft SharePoint portal:

87 Adding Portals for the Supported Portals and Connectors 1. After creating the portal, click the Configuration tab to display the SharePoint configuration parameters: 2. Edit the Portal Parameters: In the Context Path field, type path to the web site that Roambi will access. The path should start with a "/". To determine the correct context path: a. Navigate to the target SharePoint site. b. Go to Site Actions > Site Settings. c. The context path will be in the following place in the site URL: In the Windows NT Domain field, type the default Windows NT domain for authentication. This parameter allows users who belong to this domain to skip typing the domain as part of their User ID. Users who do not belong to the domain will need to use the format [domain]/[user_name] when typing their User IDs. In the Web Service URL field, type the SharePoint server URL without the context path. 3. Verify the portal settings as prompted. 4. When the Enable Portal button becomes visible, toggle the button to ON 5. Optionally, on the Security tab, you can enable the Primary Login option. Important: Roambi ES requires that you have at least one portal with Primary Login enabled. Failure to designate a portal with Primary Login will result in an inability to login from a device. SAP Americas Proprietary and Confidential

88 Chapter 7: Configuring Roambi ES Portals 6. After configuring the required parameters, click the Folders tab to set up the folders for the portal. Creating a Working Folder in SharePoint for Roambi Flow You should create a working folder to store your published Roambi Flow documents on your SharePoint portal. To create a Roambi Flow working folder in SharePoint: 1. On your SharePoint portal, create these folders: A parent folder. A child folder within the parent folder. 2. For the child folder, edit the permissions to grant users Full Control. 3. For the parent folder, edit the permissions and remove all the permissions for other users, granting only the Administrator Full Control. 4. In the Roambi ES Administrator's Console, set the child folder to be the working directory as described in Creating a Roambi Flow Working Directory. Microsoft SQL Server Analysis Services (SSAS) This section discusses the required configuration changes that you must make to use Microsoft SQL Server Analysis Services with Roambi ES. Configuring HTTP Access on IIS In order to enable HTTP access to SSAS, you must configure the msdmpump.dll running in Internet Information Services (IIS). For instructions, refer to the instructions below on the Microsoft Developer Network: Configuring a SSAS Portal in Roambi ES A Microsoft Analysis Services portal requires that you configure several parameters before the portal can be enabled. To configure a Microsoft Analysis Services portal: 1. After creating the portal, click the Configuration tab to display the Microsoft Analysis Services configuration parameters:

89 Adding Portals for the Supported Portals and Connectors 2. Edit the Portal Parameters: In the Windows NT Domain field, type the default Windows NT domain for authentication (optional). In the Server Type field, type the Analysis Services OLAP source. This parameter should contain "SSAS". In the Server URL field, type the URL where the Microsoft Multidimenstional Pump application is installed. For example: /msmdpump.dll. 3. Verify the portal settings as prompted. 4. When the Enable Portal button becomes visible, toggle the button to ON. Microsoft SQL Server Reporting Services (SSRS) This section discusses the required configuration changes that you must make to use Microsoft SQL Server Reporting Services with Roambi ES. Included in this topic: l Installing the Roambi Reporting Services Plugin for Microsoft SQL Server 2008/2012/2014 l Configuring Roambi with Microsoft SharePoint 2010 and Reporting Services 2012 in Integrated Mode l Configuring a Microsoft SQL Server Portal in Roambi SAP Americas Proprietary and Confidential

90 Chapter 7: Configuring Roambi ES Portals Installing the Roambi Reporting Services Plugin for Microsoft SQL Server 2008/2012 This Roambi Reporting Services plugin is required to integrate Roambi ES with Microsoft SQL Server.You must install the Roambi Reporting Services plugin (roambireportingservices-plugin.dll) on Microsoft SQL Server when the following is true: When using Microsoft SQL Server Reporting Services in Native Mode When using Microsoft SharePoint in Integrated Mode. To install the Roambi Reporting Services plugin: 1. Locate the SSRS folder created during the deployment of the Roambi ES server. 2. Copy the roambi-reportingservices-plugin.dll file to [SQL_Installation_folder] \MSRS10.MSSQLSERVER\Reporting Services\ReportServer\bin. 3. Locate the rssrvpolicy.config file. For Reporting Services 2008, this file is located at: [SQL_Installation_folder] \MSRS10.MSSQLSERVER\ReportingServices\ReportServer For Reporting Services 2012, this file is located at: [SQL_Installation_folder] \MSRS11.MSSQLSERVER\ReportingServices\ReportServer 4. Edit the rssrvpolicy.config file and add the following bold CodeGroup element as the first item to <CodeGroup> element from the following example: <CodeGroup class="firstmatchcodegroup" version="1" PermissionSetName="Nothing"> <IMembershipCondition class="allmembershipcondition" version="1" /> <CodeGroup class="unioncodegroup" version="1" PermissionSetName="FullTrust" Name="RoamBI Render" Description="This code group grants RoamBI Renderer code full trust."> <IMembershipCondition Url="C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\ReportingServices\ReportServer\bi n\roambi-reportingservices-plugin.dll" class="urlmembershipcondition" version="1" /> </CodeGroup> 5. In the [SQL_Installation_folder]\MSRS10.MSSQLSERVER\Reporting Services\ReportServer folder, open the rsreportserver.config file in a text editor. 6. In the Render section, add the following element (in bold) before the </Render> closing tag (non-bold tags are included for context): <Extension Name="WORD" Type="Microsoft.ReportingServices.Rendering.WordRender er. WordDocumentRenderer,Microsoft.ReportingServices.WordR endering"/>

91 <Extension Name="ROAMBI" Type="RoamBI.ReportingServices.MellmoReportingServicesPl ugin,roambi-reportingservices-plugin" />

92 Adding Portals for the Supported Portals and Connectors </Render> 7. In the [SQL_Installation_folder]\MSRS10.MSSQLSERVER\Reporting Services\ReportServer folder, open the web.config file in a text editor. 8. Replace the existing httpruntime element with the following httpruntime element or add these attribute/value pairs to the element: <httpruntime maxrequestlength="102400" executiontimeout="9000' usefullyqualifiedredirecturl="false" minfreethreads="8" minlocalrequestfreethreads="4" apprequestqueuelimit="5000" /> 9. Restart the SSRS service. You can verify that the SSRS plugin is working correctly by opening a web browser and typing the URL for the SSRS server's Reports folder, for example: Run a report, and under the Export Format options, you should see Roambi Renderer. Clicking Export should now generate an XML file. Configuring SAP Roambi with Microsoft SharePoint 2010 and Reporting Services 2012 in Integrated Mode With the release of Microsoft SQL Server 2012, Reporting Services can now be configured as a service application inside Microsoft Sharepoint. With 2012, Reporting Services Configuration Manager is no longer required or supported to configure and administer Reporting Services SharePoint mode. Instead, use SharePoint Central Administration to configure a report server in SharePoint mode. Note: For more information about installing Microsoft SQL Server Reporting Services in SharePoint Mode, see the Microsoft TechNet article: Once Microsoft Sharepoint 2010 is configured to run Reporting Services, follow these steps to register the Roambi renderer: 1. Copy the roambi-reportingservices-plugin.dll file in the SSRS folder of the Roambi ES Deployment to SharePoint 2010 Reporting Services bin Folder. The default path of the bin folder is: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\Reporting\bin 2. Edit the rssrvpolicy.config file. The default location is C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\Reporting and add the following bold CodeGroup element as the first item to <CodeGroup> element from the following example: <CodeGroup class="firstmatchcodegroup" version="1" PermissionSetName="Nothing"> <imembershipcondition class="allmembershipcondition" version="1" /> <CodeGroup class="unioncodegroup" version="1"

93 SAP Americas Proprietary and Confidential

94 Chapter 7: Configuring Roambi ES Portals PermissionSetName="FullTrust" Name="RoamBI Render" Description="This code group grants RoamBI Renderer code full trust."> <imembershipcondition Url="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\Reporting\bin\roambi-reportingservices-plugin.dll" class="urlmembershipcondition" version="1" /> </CodeGroup> 3. Run the following script in PowerShell: Add-PSSnapin Microsoft.SharePoint.PowerShell $apps = Get-SPRSServiceApplication foreach ($app in $apps) { New-SPRSExtension -identity $app -ExtensionType "Render" - name "ROAMBI" -TypeName "RoamBI.ReportingServices.MellmoReportingServi cesplugin, roambi-reportingservices-plugin" } 4. You can verify that the Roambi Renderer plugin is working correctly by executing a Reporting Services report located in the Sharepoint Server. Once you run the report, select the Export option and verify the Roambi Renderer is there. Select that option and make sure the export saves an XML file. 5. Locate the web.config file in this folder: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\Reporting\ 6. Open the web.config file in a text editor and replace the existing httpruntime element with the following httpruntime element or add these attribute/value pairs to the element: <httpruntime maxrequestlength="102400" executiontimeout="9000' usefullyqualifiedredirecturl="false" minfreethreads="8" minlocalrequestfreethreads="4" apprequestqueuelimit="5000" /> Configuring a Microsoft SQL Server Reporting Services Portal in Roambi A Microsoft SQL Server Reporting Services portal requires that you configure several parameters before the portal can be enabled. To configure a Microsoft Reporting Services portal: 1. After creating the portal, click the Configuration tab to display the Microsoft Reporting Services configuration parameters:

95 - 82 -

96 Adding Portals for the Supported Portals and Connectors 2. Edit the Portal Parameters: In the Windows NT Domain field, type the Windows domain that you use to log into Windows. If you do not specify this domain, you can log into any Windows domain, but you will need to manually enter the Windows domain on the Roambi Publisher login screen. In the Time Zone field, type the time zone used by the server. In the Web Service URL field, type the value of the Web Service URL specified in the Report Services Configuration Manager. If the report server instance has a name other than ReportServer, add the instance name at the end of the URL. For example: 3. Verify the portal settings as prompted. 4. When the Enable Portal button becomes visible, toggle the button to ON. 5. Optionally, on the Security tab, you can enable the Primary Login option. Important: Roambi ES requires that you have at least one portal with Primary Login enabled. Failure to designate a portal with Primary Login will result in an inability to login from a device. 6. After configuring the required parameters, click the Folders tab to set up the folders for the portal. SAP Americas Proprietary and Confidential

97 Chapter 7: Configuring Roambi ES Portals QlikView This section discusses the required configuration changes that you must make to use QlikView with Roambi ES. Note that QlikView portals in Roambi ES are source-only portals and cannot store RBI files. SAP recommends using QlikView in conjunction with another portal, such as Microsoft SharePoint, SSRS Express, or Liferay Portal. To configure a QlickView portal: 1. After creating the portal, click the Configuration tab to display the QlickView configuration parameters: 2. In the Server URL field, type the QlikView AJAX URL.The typical format for this URL is [ServerName]/[AJAXContextPath]. To locate the AJAXContextPath: a. Open the QlikView management console, and select the System tab. b. On the left pane, expand the QlikView Web Servers folder, and select your server. c. On the right pane, select the Web tab. The AJAXContextPath is the third entry in the Root Folders section at the bottom of the tab:

98 Adding Portals for the Supported Portals and Connectors For example, the full server URL might be something like: 3. Verify the portal settings as prompted. 4. When the Enable Portal button becomes visible, toggle the button to ON. SAP BusinessObjects This section discusses the required configuration changes and security options for using SAP BusinessObjects with Roambi ES. Configuring the Application for SAP BusinessObjects Important: Roambi ES requires access to some BusinessObjects library files if you will be using an SAP BusinessObjects portal. For a complete list of the required JAR files for your version of SAP BusinessObjects, see Appendix G: SAP BusinessObjects JAR File Requirements. To configure your application server for BusinessObjects: 1. Complete the steps in Deploying the Roambi WAR to Tomcat. 2. Locate the required JAR files listed below. Most of these files are located in the \ folders on the BOE Server. SAP Americas Proprietary and Confidential

99 Chapter 7: Configuring Roambi ES Portals JAR File Folder (BOE 4 Location) Additional Notes If you have deployed BusinessObjects in a ant-launcherdistributed jar \webdeploy\ant\lib environment, the JAR file will be on the web node. This JAR is available after dswsreportengine.jar web services\en\dsws_ installing consumer\data\dswsjavaapi the Client Tools warfiles\webapps\dswsbobje\ dsws-webishared- WEBprovider.jar INF\lib geronimo-staxapi_ \external\axis2\ _spec jar xmlbeans jar \\external 3. Copy the required JAR files to C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\[RoambiInstallation]\WEB-INF\lib or the equivalent folder for your application server. 4. If you are using BOE4, install the Client Tools 4.0 SP2 utility to the BOE4 server. This plugin is required to make the BOE4 files available for Roambi. 5. Restart the application server.

100 - 86 -

101 Adding Portals for the Supported Portals and Connectors Installing the BOE Connector JAR file for Roambi The Roambi installation folder includes versions of a connector.jar file that is used by BOE to communicate with Roambi. To install the BOE connector.jar file for Roambi: 1. Navigate to the directory where you originally installed Roambi ES (not the /roambi directory under your application server), and open the BOE folder. 2. Locate the connector.jar file that is appropriate for your version of BOE: BOE XIR 2.x: roambi-boe-plugins snapshot.jar BOE XIR 3.x: roambi-boe-plugins snapshot.jar BOE XIR 4.0: roambi-boe-plugins snapshot.jar BOE XIR 4.1: roambi-boe-plugins snapshot.jar BOE XIR 4.2: roambi-boe-plugins snapshot.jar 3. Copy the.jar file to [ApplicationServerDirectory]\webapps\[RoambiInstallation] \WEB-INF\lib. 4. Restart the application server. Configuring Windows AD Authentication with BOE If you want to use Windows AD authentication security with a BusinessObjects portal, you might need to perform a few additional steps to set up Kerberos integration: If you installed Roambi ES on the same Tomcat application server where InfoView is deployed and have already configured and have been using WinAD authentication there, you do not need to perform any additional steps and can skip the rest of this section. If you installed Roambi ES to a dedicated server without a preexisting Java Kerberos configuration, complete the following steps in this section to enable Kerberos Windows AD authentication. l The configuration instructions for Kerberos Windows AD differ slightly from the general Kerberos configuration instructions in Appendix E: Configuring Roambi ES to Use Kerberos. To enable Kerberos Windows AD authentication for BusinessObjects: 1. Create a folder C:\WINNT on the Roambi server. This folder will act as a mirror for some of the files in the BOE C:\WINNT folder. 2. On the server where BusinessObjects web tier is installed, browse to the C:\WINNT folder. If this folder doesn't exist, check the Tomcat configuration tool for the folder location. You can obtain the location using one of these arguments: -Djava.security.krb5.conf Or -Djava.security.auth.login.conf SAP Americas Proprietary and Confidential

102 Chapter 7: Configuring Roambi ES Portals 3. From the original C:\WINNT or equivalent folder (this folder is called C:\Windows on some versions of Windows), copy the following files into the \WINNT folder that you just created: bsclogin.conf krb5.ini 4. In Tomcat (or do the equivalent for your application server), go to the Windows Start menu and go to Monitor Tomcat. The Tomcat Properties window opens. 5. On the Tomcat Properties window, click the Java tab: 6. Scroll down to the bottom of the Java Options list, and add the following lines of text: -Djava.security.auth.login.config=C:/WINNT/bscLogin.conf - Djava.security.krb5.conf=C:/WINNT/krb5.ini 7. Restart Tomcat. 8. If UDP preferences apply to your configuration, in your C:/WINNT/krb5.ini file, add the following line under [libdefaults], if the line is not already there: udp_preference_limit=1 9. When you create the SAP Business Objects portal using the web-based Administrator's Console, set the value for the Authentication parameter to secwinad

103 Adding Portals for the Supported Portals and Connectors Configuring Trusted Authentication with BOE Trusted Authentication security is an authentication proprietary to BusinessObjects that allows users to log in without using passwords when BusinessObjects uses Enterprise authentication. Using Trusted Authentication with Roambi ES facilitates the creation of batch views in Roambi because passwords are not exposed in the batch script. To set up BOE Trusted Authentication for Roambi: 1. Open the [TomcatDirectory]/webapps/[RoambiInstallation]/WEB-INF/web.xml file in a text editor. 2. In the section containing the <filter> elements, locate the following comment: <!-- uncomment the following block to enable SSO integration using HTTP Header and Trusted Auth. --> 3. As instructed in the XML code, uncomment the block following the comment. This block contains the following code: <!-- <filte r> <filtername>httpheaderauthfilter</filter-name> <filterclass>com.mellmo.roambi.servlet.filter.httpheader AuthFilter </filter-class> <init-param> <description><![cd ATA[ specifies the name of the header to use to get the user name. ]]></description> <paramname>name</param-name> <param-value>sm_user</paramvalue> </init-param> <init-param> <description><![cdata[ specifies where the filter is going to get the name of the authenticated user. Possible values are: header - the value is supplied by the HTTP Header. See "name" param remoteuser - the value is supplied by the REMOTE_USER variable by the app server

104 ]]></description> <paramname>authtype</param-name> <paramvalue>header</param-value> </initparam> </filter> SAP Americas Proprietary and Confidential

105 Chapter 7: Configuring Roambi ES Portals <filter-mapping> <filtername>httpheaderauthfilter</filter-name> <url-pattern>/*</url-pattern> </filtermapping> --> 4. Set the values for the two <param-value> elements: If your BOE configuration is not using the BOE REMOTE_USER variable, set the param-value for the authtype parameter to header. In the <param-value> element for the name parameter, replace the string SM_USER with the name of the header that is used to retrieve the the user name. If your BOE configuration uses the BOE REMOTE_USER variable, set the param-value for the authtype parameter to remoteuser. The name parameter will then be ignored by Roambi. 5. Save your changes and close the file. 6. Add the location of the TrustedPrincipal.conf file to your application server: a. In Tomcat (or do the equivalent for your application server), go to the Windows Start menu and go to Monitor Tomcat. The Tomcat Properties window opens. b. On the Tomcat Properties window, click the Java tab:

106 - 90 -

107 Adding Portals for the Supported Portals and Connectors c. Scroll down to the bottom of the Java Options list, and add the following lines of text: -Dbobj.trustedauth.home=PathToTrustedPrincipal.confFile d. Replace the italicized text with the path to your TrustedPrincipal.conf file. Copy this file from a configured BOE server and place it in a location that is useraccessible and owned by Tomcat. The TrustedPrincipal.conf file must contain the line: SharedSecret=password The password is configured in your internal BOE system. See your BOE documentation for details. e. Restart Tomcat. 7. When you create the SAP BusinessObjects portal using the web-based Administrator's Console, set the value for the Authentication parameter to secenterprise. Configuring SiteMinder and Trusted Authentication with BOE Roambi is compatible with a BOE configuration that uses SiteMinder for user authentication. When using SiteMinder, BOE should also be configured to use Trusted Authentication and secenterprise authentication. For this configuration, the Apache web server, Roambi and BOE nad BOE should both be protected by a SiteMinder web agent (with version 4.x support). If you tried to connect to an unprotected Tomcat server from a SiteMinder-protected BOE server, authorization would fail. To set up SiteMinder with BOE for Roambi: 1. Open the [TomcatDirectory]/webapps/[RoambiInstallation]/WEB-INF/web.xml file in a text editor. 2. In the section containing the <filter> elements, locate the following comment: <!-- uncomment the following block to enable SSO integration using HTTP Header and Trusted Auth. --> 3. As instructed in the XML code, uncomment the block following the comment. This block contains the following code: <!-- <filter> <filter-name>httpheaderauthfilter</filter-name> <filterclass>com.mellmo.roambi.servlet.filter.httpheaderauthf ilter </filter-class> <init-param> <description><![cdata[

108 SAP Americas Proprietary and Confidential

109 Chapter 7: Configuring Roambi ES Portals specifies the name of the header to use to get the user name. ]]></description> <paramname>name</param-name> <param-value>sm_user</paramvalue> </init-param> <init-param> <description><![cd ATA[ specifies where the filter is going to get the name of the authenticated users. Possible values are: header - the value is supplied by the HTTP Header. See "name" param. remoteuser - the value is supplied by the REMOTE_USER variable by the app server. ]]></description> <paramname>authtype</param-name> <paramvalue>header</param-value> </filter> <filter-mapping> <filtername>httpheaderauthfilter</filter-name> <url-pattern>/*</url-pattern> </filtermapping> --> 4. Set the values for the two <param-value> elements: If your BOE configuration is not using the BOE REMOTE_USER variable, set the param-value for the authtype parameter to header. In the <param-value> element for the name parameter, replace the string SM_USER with the name of the header that is used to retrieve the the user name. If your BOE configuration uses the BOE REMOTE_USER variable, set the param-value for the authtype parameter to remoteuser. The name parameter will then be ignored by Roambi. 5. Save your changes and close the file. 6. Add the location of the TrustedPrincipal.conf file to your application server: a. In Tomcat (or do the equivalent for your application server), go to the Windows Start menu and go to Monitor Tomcat. The Tomcat Properties window opens. b. On the Tomcat Properties window, click the Java tab:

110 - 92 -

111 Adding Portals for the Supported Portals and Connectors c. Scroll down to the bottom of the Java Options list, and add the following lines of text: -Dbobj.trustedauth.home=PathToTrustedPrincipal.confFile d. Replace the italicized text with the path to your TrustedPrincipal.conf file. Copy this file from a configured BO server and place it in a location that is useraccessible and owned by Tomcat. The TrustedPrincipal.conf file must contain the line: SharedSecret=password The password is configured in your internal BOE system. See your BOE documentation for details. e. Restart Tomcat. 7. When you create the SAP BusinessObjects portal using the web-based Administrator's Console, set the following values for the BOE parameters: a. On the Configuration tab, set the value for the Authentication parameter to secenterprise. b. Go to System > Security, and set the value for Single Sign-on Type to SiteMinder (not Trusted Auth). SAP Americas Proprietary and Confidential

112 Chapter 7: Configuring Roambi ES Portals Configuring the BOE XI 3.1 SAP Integration Kit with Roambi (BOE XI 3.1 and BOE XI 4.0) Roambi ES is compatible with the BOE XI 3.1 integration kit for SAP; however you will need to enable Authentication to an InfoView portal using the SAP PIK. These same instructions apply to BOE XI 4.0. To use Roambi with the BOE XI 3.1 SAP Integration kit: 1. Copy the secsapr3.jar file located in C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\warfiles\WebApps\dswsbobje\WEB-INF\ to the [TomcatDirectory]/webapps/[RoambiInstallation]/WEB-INF/lib folder. The secsapr3.jar file is part of the SAP PIK for InfoView. 2. Copy the sapjco.jar file (or the sapjco3.jar file for JCO 3.0) located in C:\Program Files\SAP\SAP Java Connector 2.x\ to the [TomcatDirectory]/webapp/ [RoambiInstallation]/WEB-INF/lib folder. The sapjco.jar file is part of the SAP Java Connector When you create the SAP BusinessObjects portal, using the web-based administrator's console, set the value for the Authentication parameter to secsapr3. Creating a Working BOE Directory for Roambi You will need to create a working directory for Roambi to save temporary files for creating and refreshing Roambi analytics reports. Specifically, this folder will store parameter values for a report that contains parameters. The working directory needs to have access rights to "Create or add Objects" and to view objects. You can choose to hide the main working directory and create a subfolder with the "Add Objects" rights, which will hide the folder from end users. Roambi does not support setting the SAP Public Folders directory as the working directory because Roambi cannot save anything to the root directory of a BOE portal. To set up the working BOE directory for Roambi: 1. Navigate to the following directory: [TomcatDirectory]/webapps/[RoambiInstallation]/WEB- INF/classes/com/mellmo/roambi/portal/plugins 2. Under the /plugins directory, create a directory named boe. 3. In the /boedirectory, create a file named BOERepository.properties. 4. Open the BOERepository.properties file in a text editor, and add the following code: temp_folder_id=[cuid] 5. Set the CUID to the CUID of the hidden public folder in BOE's Content Management System (CMS). 6. Save your changes and restart Tomcat

113 Adding Portals for the Supported Portals and Connectors Configuring an SAP BusinessObjects Portal An SAP BusinessObjects portal requires that you configure several parameters before the portal can be enabled. Configure the portal immediately after creating the portal from the Roambi administrator's console. To configure an SAP BusinessObjects portal: 1. After creating the portal, click the Configuration tab to display the two SAP configuration parameters: 2. Edit the Portal Parameters: In the Authentication field, type the BOE authentication type to be used by Roambi. Valid values are secenterprise, secldap, secwinad, and secsapr3. You can define multiple SAP BusinessObjects portals and specify a different authentication type for each portal. If you are using secenterprise, you must also set up Trusted Auth (as described in the preceding sections.) If you are using secldap, do not set up Trusted Auth because this type of authentication does not work with secldap. In the Server Name field, type the name of the server where the Content Management System (CMS) is deployed. This differs from the Roambi server, which will most likely be an Apache or IIS webserver using mod_jk (Apache) or isapi_ redirect (IIS). SAP Americas Proprietary and Confidential

114 Chapter 7: Configuring Roambi ES Portals If this portal points to a BusinessObjects Enterprise version 4.0/4.1 server, specify the Web Service URL for BOE in the Web Service URL field. To locate the Web Service URL: a. In the Central Management Console for BOE, select Applications from the top drop-down list. b. Scroll down to the bottom of the displayed list, and select Web Service. The Web Service Properties tab displays. c. Copy the Access URL from Web Service Properties, and paste it into the Web Service URL field on the Roambi Administrator's Console. d. Add the ending /services to the URL that you just pasted. If this portal points to a BusinessObjects Enterprise version 4.2 server, specify the RESTful Web Service URL for BOE in the Web Service URL field. To locate the RESTful Web Service URL: a. In the Central Management Console for BOE, select Applications from the top drop-down list. b. Scroll down to the bottom of the displayed list, and select RESTFul Web Service. The Web Service Properties tab displays. c. Copy the Access URL from Web Service Properties, and paste it into the Web Service URL field on the Roambi Administrator's Console. d. Add the ending /services to the URL that you just pasted. 3. Verify the portal settings as prompted. 4. When the Enable Portal button becomes visible, toggle the button to ON. 5. Optionally, on the Security tab, you can enable the Primary Login. Important: Roambi ES requires that you have at least one portal with Primary Login enabled. Failure to designate a portal with Primary Login will result in an inability to login from a device. 6. If you are using Single Signon, go to System > Security to set your Single Signon type. 7. After configuring the required parameters, click the Folders tab to set up the Root and Auto Sync folders for the portal

115 Chapter 8: Roambi ios Simulator This chapter provides instructions for installing and starting the Roambi ios Simulator: l About the Roambi ios Simulator l Preparing to Install the Roambi ios Simulator l Installing the Roambi ios Simulator l Starting to Roambi ios Simulator

116 About the Roambi ios Simulator Roambi ES includes a Roambi ios Simulator utility that enables you to test out new Roambi Visualizer functionality before users update the Roambi Visualizer application on their mobile devices. The Roambi ios Simulator enables you to test new versions of Visualizer before updates appear in the Apple App store. Before you can install Roambi ios Simulator, you must install the ios Simulator application from Apple, which is part of the ios Software Develoment Kit (SDK) or Xcode. You can only install the ios SDK to supported versions of Mac OS X. You will need to join the Apple ios Developer Program to gain permission to download the Xcode and ios Installer. Preparing to Install the Roambi ios Simulator Before you can install and use the Roambi ios Simulator, you will need to join the Apple ios Developer Program and install the ios SDK or Xcode. Joining the Apple ios Developer Program You can enroll in the Apple ios Developer Program for a small fee. The Apple ios Developer Program grants access to technical resources and support, including the ios SDK and ios Simulator. To enroll in the Apple ios Developer Program: 1. Go to the Developer Program website: 2. Click the Enroll Now button. 3. Follow the instructions as prompted. If you are a new member who is running Mac OS X Lion, you will need to download Xcode from the Mac App Store before proceeding. Preparing to Install the ios SDK or Xcode Depending on which version of Roambi ES you are running, you might need a specific version of the ios SDK or Xcode

117 Installing ios SDK 5 on Mac OS X 10.6 or Xcode 4.2 To install ios SDK 5 on Mac OS X 10.6 or Xcode 4.2: 1. Download the Apple Disk Image (DMG) file for the iphone SDK 5: 2. Double-click the DMG file, and follow the prompts to install the SDK with all of the default settings. The iphone Simulator will be installed as part of the SDK package. Installing ios SDK 5 on Mac OS X 10.7 or Xcode 4.3 To install ios SDK 5 on Mac OS 10.7 or Xcode 4.3: 1. If you are running Mac OS X 10.7 Lion, you will need to install Xcode 4.3 from the Mac App Store. 2. Copy the Xcode 4.3 app to the Applications folder on your Mac. 3. Start Xcode Go to Preferences... > Downloads, and download the ios Simulator application. Installing ios SDK 6 on Mac OS X x Yosemite or Xcode 6.x To install ios SDK 6 on Mac OS x Yosemite or Xcode 6.x: 1. If you are running Mac OS X x Yosemite, you will need to install Xcode 6.x from the Mac App Store. 2. Copy the Xcode 6.xapp to the Applications folder on your Mac. 3. Start Xcode 6.x. You can now install the Roambi application to the ios Simulator as described in Installing the Roambi ios Simulator. Installing the Roambi ios Simulator The Roambi Simulator is delivered via ZIP file. Depending on whether you are installing the Roambi Analytics Visualizer Simulator or the Roambi Flow Simulator, the contents of the Roambi ZIP file differ slightly. The following sections describe the contents of the Roambi Simulator ZIP files, how to install the Simulator, and how to update the Simulator to the latest Roambi build. ZIP File Structure for Roambi Analytics Visualizer Simulator The ZIP file for the Roambi Analytics Visualizer Simulator is named Roambi.zip and contains the following folders and files:

118 Installing the Roambi ios Simulator /roambi/roambi.app /roambi/roambi.sb /roambi/tmp ZIP File Structure for Roambi Flow Simulator The ZIP file for the Roambi Flow Simulator is named RoambiFlowSimulator.zip and contains the following folders and files: /RoambiFlowSimulator/RoambiFlow.app /RoambiFlowSimulator/RoambiFlow.sb /RoambiFlowSimulator/tmp Installing the Simulator To install the Roambi Simulator: 1. If you are using OS X.7, 8 or 9, unhide the ~/Library folder on your system: a. Open Finder, press your alt key, and select Go to from the top menu. b. Select Go to folder..., and type ~/Library The /Library folder is temporarily unhidden and opens. You can permanently unhide the /Library folder by opening a Terminal window and typing the following command: $ chflags nohidden ~/Library The /Library folder will now appear in Finder. 2. Place the Roambi ZIP file on your desktop, and unzip its contents to the desktop.. 3. In Finder, locate the ~/Library/Application Support/iPhone Simuator/5.0 directory. 4. Create an Applications directory under the 5.0 directory. 5. Copy the unzipped /roambi or /RoambiFlowSimulator(as appropriate) to the Applications directory that you just created. The Roambi Simulator should now appear in your Applications folder and in Spotlight. 6. Start the Roambi Simulator. See Starting the Roambi ios Simulator. Installing the Simulator on Mac OS x Yosemite To install the Roambi Simulator: Set up the terminal environment to make sure you're using the right version of Xcode: sudo xcode-select --switch /Applications/Xcode.app Download and extract the.app bundle for the app you want to install SAP Americas Proprietary and Confidential

119

120 List the available simulator environments. You may see more or fewer of them depending on how your Xcode install is set up. xcrun simctl list devices == Devices == -- ios iphone 4s (3B5E478A-5B B805-06B217BE0398) (Shutdown) iphone 5 (33FF8B21-3BD5-41D3-A275-C5D85FCCA0C0) (Shutdown) iphone 5s ( C-F06A-40C FB E) (Shutdown) ipad 2 (6CF764C6-238D-4AB9-B1F6-2E1B63E057C8) (Shutdown) ipad Retina (E77199A BC-B B55C83F88) (Shutdown) ipad Air (753ED94D-CF95-450C-9C70-D84A8B931126) (Shutdown) -- ios iphone 4s (3D C82-4AB4-AF0A-33F03EC4774F) (Shutdown) iphone 5 (1F93D B C2B4C1A2D86A) (Shutdown) iphone 5s (3B8C5577-E001-46A7-ABE6-00DE904C2935) (Shutdown) iphone 6 Plus (11270F3D-A874-47D4-95DA-02C697E885E0) (Shutdown) iphone 6 (D40B9FA2-31EA AC9-59B2DE1F8DC2) (Shutdown) ipad 2 (C3F18D6D-EAF8-45EA-A26D-FFD058190F7A) (Shutdown) ipad Retina (A132BCDD-E91D-4D6F-AE31-BF61D0F92A2C) (Shutdown) ipad Air (A902203A-C99B-46B ED9F47050D7) (Shutdown) Resizable iphone (1EB72B98-449A-4BAE-BE66-D100257A6E61) (Shutdown) Resizable ipad (36A1B11F-B466-4E56-BAAA-19F5F56818AA) (Shutdown) Boot the simulator environment, identified by its UUID: xcrun simctl boot 1EB72B98-449A-4BAE-BE66-D100257A6E61 Install the app to the environment. You can drag and drop the app from the Finder to the Terminal window to automatically insert the path to the app: xcrun simctl install 1EB72B98-449A-4BAE-BE66-D100257A6E61 /path/to/roambi.app Note: if you have a simulator running (i.e. Booted ) then you can use the word booted in place of a UDID. xcrun simctl install booted /path/to/roambi.app Shutdown the simulator environment within terminal, using the same UUID from step 4:

121 Starting the Roambi ios Simulator xcrun simctl shutdown 1EB72B98-449A-4BAE-BE66-D100257A6E61 Close Terminal and Launch ios Simulator from Xcode 6. Starting the Roambi ios Simulator This section describes how to start the Roambi ios Simulator, depending on the configuration of your Mac. Starting the Roambi ios Simulator with Xcode 4.2 or Older To start the Roambi ios Simulator with Xcode 4.2 or older: 1. Open Finder, and click the Mac HD icon under Devices. 2. Navigate to the following directory: /Developer/Platforms/iPhoneSimulator.platform/Developer/Ap plications 3. Double-click the.app file for the Roambi Simulator. You can also copy this file to the user /Applications folder for easy access. Starting the Roambi ios Simulator on Mac OS X 10.7 Lion To start the Roambi ios Simulator on Mac OS X 10.7 Lion: 1. Locate your Xcode.app file, right-click the file, and select Show package contents from the context menu. A Finder window opens. 2. Browse to the following folder: /Contents/D e- veloper/platforms/iphonesimulator.platform/developer/appli cations 3. Copy the iphonesimulator.app file to your user Applications folder. 4. Double-click the application file to start the application. You might need to restart the ios Simulator before the Roambi Analytics Visualizer Simulator and Roambi Flow Simulator appear in the ios Simulator. You can switch the ios Simulator between iphone, Retina Display, and ipad modes by going to Hardware > Device, and selecting a device. You can also select ios version by going to Hardware > Version. The Version menu contains other options such as left and right rotation. You can zoom the ipad display between 50, 75, and 100% using the Windows > Scale menu.

122 SAP Americas Proprietary and Confidential

123 Chapter 9: Validating the SAP Roambi Installation After you have installed and configured the Roambi ES on your server, use the validation checklist in this chapter to ensure that Roambi is operating as expected. This chapter also includes troubleshooting topics for common installation problems. Included in this chapter: l Validation Checklist for Roambi ES l Troubleshooting Validation Checklist for Roambi ES Use this basic checklist to validate your Roambi ES installation. Not all of the recommended steps on this checklist will apply to every Roambi configuration; omit any steps that do not pertain to your configuration. Roambi Publisher Perform the following tasks to verify your configuration for Roambi Publisher: Using a valid user name and password, can you log into the portals that you configured in Roambi Publisher? (Log in using your credentials for the BI system.) Can you successfully import a report from the BI tool to Publisher? If you will be using MS Excel as a data source, can you successfully import an Excel file to Publisher? Can you map and regroup your Excel data successfully? Can you successfully publish a Roambi analytics report? If you configured your SMTP settings (discussed in the Roambi ES5 Administration Guide), can you successfully Roambicast a Roambi analytics report? Roambi Flow Publisher If your organization has a Roambi Flow license, perform the following tasks to verify your configuration for Roambi Flow Publisher:

124 Chapter 9: Validating the Roambi Installation Can you successfully access Roambi Flow Publisher, which should appear as an additional tab in the Administrator's Console? Are you able to create and publish a Roambi Flow test document? Do images, including thumbnails, properly render in Roambi Flow Publisher? Mobile Devices Perform the following tasks to verify access from a client mobile device: Using a Roambicast sent by an administrator, can you install your Roambi portals? Using a Roambicast sent by an administrator, can you display a View? Is the SWF display rendering correctly? Does the device connectivity appear to work? Can you render Views that you access through your Roambi portal? Can you refresh a View? Troubleshooting This section contains recommendations for common installation issues. For more extensive information about troubleshooting Roambi ES, see the SAP Roambi ES5 Administration Guide, which contains an extensive chapter on troubleshooting. License Key If Roambi displays a "License key not valid" error, perform the following checks to troubleshoot the issue: Navigate to the license.es file in the./roambi directory, and make sure that the file name is not colored green. If the file name is colored green, this means that the file is encrypted. Go to the Properties for the file and uncheck the File encryption option. Clean the Tomcat directories: 1. Shut down Tomcat. 2. Delete the roambi folder from [TomcatDirectory]/work/Catalina/localhost. 3. Delete all files under [TomcatDirectory]/temp. 4. Restart Tomcat. Close and open your web browser. Clear your browser cache. If you transferred the file from Windows to Linux, make sure that you used SFTP or that FTP was in binary mode. If none of these suggestions work, the file could be corrupt and you might need to talk to SAP support to regenerate the file

125 Troubleshooting MacOS X If you attempt to launch the installer (install4j) on a system running Mac OS X Mountain Lion, the Gatekeeper security settings may not be set to permit the installation application to run.to change the settings, go to the Security & Privacy preferences' General tab. Then, under Allow Applications Downloaded From, choose the Anywhere option button as pictured below. MySQL If you needed to reinstall MySQL 5.5 for any reason, the service will fail when you start MySQL unless you delete the following items: C:\Program Files\MySQL folder Win 2008: C:\Users\administrator\appdata\roaming\mysql might be invisible) Win 2008: C:\ProgramData\mysql Win 2003: C:\Documents and Settings\All Users\Application Data\MySQL MySQL service in regedit SAP Americas Proprietary and Confidential

126 Chapter 10: SAP Roambi ESX This chapter discusses features and functionality that are only available in SAP Roambi ESX. Roambi ESX consists of Roambi Analytics and Roambi Flow, specially licensed for sharing free, 'external' Roambi content with the general public. From next-generation product collateral to interactive financial reports, Roambi ESX lets you deliver unsecured Roambi content to the general public, utilizing a Public Portal. Public Portals eliminate the need for end user credentials and provide a seamless user experience for public-facing Roambi Analytics reports and Roambi Flow publications. Note: When enabling public access to a portal storing your source data and Roambi files, your organization is responsible to maintain its compliance with its portal license. Included in this chapter: l About Public Portals l Adding a Public Portal l Adding Authentication Credentials to a Public Portal l Configuring a Public Portal l Enabling a Public Portal l Publishing Roambi Files to Public Portals About Public Portals When you designate a portal as public, users can gain access to the Roambi report files (RBIs) and Roambi Flow publications published to the portal using the public account information. To create and publish Roambi reports and Roambi Flow publications, authors must log into the Public Portal using their personal access credentials and not the public account. To download and access reports and publications on mobile devices, end users can access Roambi files using the public account information which does not require access credentials. Enabling the Public Portal option does not prevent users from logging into the portal with credentials other than what you specify for the public account. Important Notes About Public Portals Important things to note about Public Portals:

127 Chapter 10: Roambi ESX The Public Portal option is not available for portals that use Single Sign-On (SSO). The Public Portal option must be enabled when you add a portal. If you would like to designate a portal that has already been added to Roambi, you must delete the portal from Roambi and then add it again it as a Public Portal. Adding a Public Portal This procedure shows you how to add a public portal to Roambi ESX. To add a portal: 1. Click the Add Portal button in the lower left corner of the dashboard: An Add Portal window opens: 2. From the Portal Source drop-down list, select the portal that will be used as the data source for the portal. Depending on which portal you choose, the portal may also be used to store Roambi RBI files and Flow publications. 3. In the Name text box, type a unique name for the portal source. When creating a Public Portal, it is recommended that you include "public" in the portal name. This will ensure report authors know that they are importing data from and publishing reports to a Public Portal. For more details, see Publishing Roambi Files to Public Portals. 4. Check the Enable Public Portal box. 5. Click Add

128 Adding Authentication Credentials to a Public Portal You have successfully enabled a Public Portal for Roambi ESX. Next, see Adding Authentication Credentials to a Public Portal. Adding Authentication Credentials to a Public Portal Next, add the public authentication credentials to the portal as follows: 1. Add the public authentication credentials to the portal: 2. On the left pane of the Administrator's Console, select the portal. 3. Click the Configuration tab: 4. On the Configuration tab, enter the required parameters for your portal type. The fields requiring data entry will vary from portal to portal. For details, see the section that pertains to your portal type in this guide. The Portal Status section displays a message prompting you to verify your settings. SAP Americas Proprietary and Confidential

129 Chapter 10: Roambi ESX 5. Click the Verify button to open a Verify Portal window: 6. Type the credentials that you use to access the portal. These credentials do not need to be the same credentials as the username and password for the public account. 7. Click Verify to close the Verify Portal window. The Portal Status section of the configuration tab displays a message prompting you to configure the Public Portal

130 Configuring a Public Portal Configuring a Public Portal To configure a Public Portal: 1. Click the Security tab for the portal. The section is now visible. This section will not be visible unless you enabled the Public Portal option when you created the portal: 2. In the Public Account field, click the Attach Account button: SAP Americas Proprietary and Confidential

131 Chapter 10: Roambi ESX 3. Enter the account credentials for your portal's public account. By specifying the account's access credentials here, end users will be permitted to access the Roambi reports (RBIs) and Roambi Flow publications on the portal without being prompted for credentials. 4. Click Attach to attach the account. The Public Account field now displays the username for the public account:

132 Enabling a Public Portal 5. If you want to select a custom logo for the portal, click the Select button for Small Logo and/or Large Logo and follow the prompts to change the logo. 6. If you want to allow users to browse the contents of the portal, rather than only being able to access Roambi reports sent via Roambicast or Roambi Flow documents sent via Flow Cast, toggle the Enable Browsing switch to ON. (Browsing is disabled by default.) 7. If you enable browsing, two more options become available: Available For and Public Portal URL: 8. In the Available For field, select whether you want users to be able to browse Analytics files (RBIs), Roambi Flow files, or both. The Public Portal URL contains the URL that you can copy and to users or integrate with another application. Enabling a Public Portal To enable a Public Portal: 1. Click the Configuration tab for the portal. The Portal Status section now displays a message about enabling the portal. 2. Toggle the Enable Portal switch to ON. You have enabled the portal. The Roambi files published to the portal can now be accessed by users via the public account credentials. Publishing Roambi Files to Public Portals If you have more than one portal integrated with Roambi, ensure that your report authors are aware that if they want to provide mobile end users with public access to a Roambi file, they must always choose the Public Portal as the publishing location. This is true for both Roambi reports (RBIs) and Roambi Flow publications. SAP Americas Proprietary and Confidential

133 Chapter 10: Roambi ESX In order to avoid confusion in environments where portals may have similar names, SAP recommends that you always assign your Public Portal a unique name to clearly identify it as public. For more information see the recommendation in Adding a Public Portal

134 Appendix A: Deploying SAP Roambi ES on JBoss Downloading JBoss You may download JBoss from Source Forge at: GA/ Download the jboss ga-jdk6.zip file. Installing JBoss To manually install JBoss, unzip the package to a folder without spaces in the path: Windows - SAP suggests C:\ Linux - SAP suggests /opt This folder is named by default jboss ga. This Appendix refers to it as [ApplicationServer]. JBoss also allows different configuration options to coexist in such a way that each configuration works as a standalone JBoss Application Server. The remaining procedures in this Appendix assumes the default configuration located at [ApplicationServer]/server/default. Modifying JBoss Initialization Parameters 1. Open the [ApplicationServer]/bin/run.conf file in a text editor. 2. Double-check the JAVA_HOME variable is correctly defined, and points to an existing JRE 64-bit home folder 3. Double-check the JAVA_OPTS variable contains these entries defined: -Djava.awt.headless=true -server -Xmx[memorySize] -Xms[memorySize]

135 Appendix A: Deploying Roambi ES on JBoss -XX:MaxPermSize=[heapSize] -XX:PermSize=[heapSize] 4. Change both the [memorysize] and [heapsize] placeholders to: If the total system memory is 4GB: [memorysize]=2048m [heapsize]=256m If you re total system memory is 8GB or greater: [memorysize] = 4096M [heapsize] = 512M Changing the JBoss Connector Maximum Post Size 1. Open the [ApplicationServer]/server/default/deploy/jbossweb.deployer/server.xml file in a text editor. 2. Locate the XML <connector> tag on port Add the attribute maxpostsize= Deploying Roambi ES on JBoss 1. JBoss expects a deployment folder named roambi.war under [ApplicationServer] /server/default/deploy. 2. Navigate to the directory where you installed Roambi ES: Windows - Usually at C:\program files (x86)\roambies-x.y.zzzz Linux - Usually at /opt/roambies-x.y.zzzz 3. Extract roambi-es-4.x.war to [ApplicationServer] /server/default/deploy/roambi.war. Note: The remaining steps for Deploying Roambi ES on JBoss refer to Roambi deployment location as [RoambiDeployment]. Completing the Configuration To complete with the configuration process, go to Chapter 3 and complete the Configuring the OpenOffice API. Then, complete the remaining procedures in Chapter

136 Appendix B: Deploying SAP Roambi ES on WebLogic If you are using Oracle WebLogic as your application server, install the server according to the WebLogic documentation. Installing the Java Persistence API To ensure that WebLogic works successfully with Roambi ES, perform the following configuration steps: 1. Install the following patch for Support for Java Persistence API (JPA) 2.0 Providers: 2. Open the WebLogic Server Administration Console. 3. Navigate to Home > base_domain> General > JPA > Default JPA Provider. 4. Set the domain JPA provider to Top Link. Deploying Roambi ES on WebLogic 1. Use the WebLogic deploy folder for explode roambi.warfile. 2. Copy the roambi.war to this folder and then in this folder execute: mkdir roambi cd roambi jar -xvf../roambi.war Using the Admin Console 1. Click Deployments. 2. In the right panel select Install. 3. Using the Install Application Assistant, locate the directory where the roambi.war file was exploded. 4. Click Next. 5. Select Install this deployment as an application

137 Appendix B: Deploying Roambi ES on WebLogic 6. Click Next. 7. Click Next. 8. Review the configuration and click Finish. 9. Optionally update settings about the deployment

138 Appendix C: Installing Tomcat Manually on Linux Downloading Tomcat You may download the version that best fits your requirements from the Apache Software Foundation at: l Version 6.0.x - l Version 7.0.x - Installing Tomcat To manually install Tomcat on Linux, download the.tar.gz file. Tomcat requires a compatible Oracle Java Runtime Engine. This appendix assumes you already installed Oracle JRE using the procedure described on your Linux distribution chapter, and Oracle JRE exists in /usr/lib/jvm/sunjre- [VersionArch] as instructed on these chapters. You can decompress Tomcat tarball to any location of your preference but /opt/apachetomcat-x.y.zz is usually the preferred location where x.y.zz is the Tomcat version. Modifying Tomcat Initialization Parameters To customize Tomcat to use the correct Oracle JRE and optimize the memory settings: 1. Navigate to: [ApplicationServer]/bin 2. Create the file setenv.sh with this content: JAVA_HOME=[PathToJRE] JAVA_MEM_SIZE=[Memory Size] JAVA_HEAP_SIZE=[HeapS ize] JAVA_OPTIONS="${JAVA_OPTS} -Djava.awt.headless=true -server -Xmx${JAVA_ MEM_SIZE} -Xms${JAVA_MEM_SIZE} - XX:MaxPermSize=${JAVA_HEAP_SIZE} -XX:PermSize=${JAVA_HEAP_SIZE}"

139

140 Appendix C: Installing Tomcat Manually on Linux 3. Replace the 3 placeholders with this information: [PathToJRE] - Path to the JRE home folder [MemorySize] - Defines JRE initial and maximum memory size Use 2048m if your total memory is 4GB Use 4096m if your total memory is 8GB or higher [HeapSize] - Defines JRE heap size Use 2048m if your total memory is 4GB Use 4096m if your total memory is 8GB or higher Disabling Tomcat Watched Resources Tomcat monitors specific static resources. By default, these watched resources are each web application context file (web.xml). Note: You must disable the default watched resources behavior as Tomcat will automatically reload the context file whenever it changes. This behavior can both negatively impact performance and cause fatal behavior for Roambi ES libraries. To disable the watched resources behavior: 1. Navigate to the [ApplicationServer]\conf\ directory. 2. Open [ApplicationServer]\conf\context.xml in a text editor. 3. Locate and comment out the WatchedResources element as shown: <!--<WatchedResource>WEB-INF/web.xml</WatchedResource> --> 4. Restart the Tomcat application service. Changing the Tomcat Connector Max Post Size Roambi requires an increase on Tomcat's default maxpostsize attribute in the connector definition. To increase the maxpostsize: 1. Navigate to the [ApplicationServer]\conf directory. 2. Open the [ApplicationServer]\conf\server.xml file in a text editor. 3. Locate the XML <connector> tag on port Add the attribute: maxpostsize=" "

141 Appendix D: Configuring SAP Roambi ES to Use a SQL Server Database Roambi ES supports the optional use of a SQL Server database to replace the MySQL database that serves as the repository for Roambi administration and security data. Installing Microsoft SQL Server You will need install Microsoft SQL server. For instructions, refer to the Microsoft web site at: Configuring Microsoft SQL Server The following tasks must be completed by the database administrator prior to configuring SQL Server: 1. Create a SQL Server database. SAP suggests naming it: roambi 2. Change the database collation to: Latin1_General_CI_AS 3. Create a user choosing SQL Server Authentication Mode. SAP suggests naming the user: roambi 4. Assign this user db_owner rights on the roambi database. 5. Enable the SQL Server TCP/IP protocol. 6. Share the following information with the Roambi Administrator: a. Server Name b. Server Instance TCP/IP Port c. Database Name d. User Name e. Password Roambi ES support for SQL Server leverages application server support for the Java Naming and Directory Interface (JNDI) and JDBC. Before you can connect to the SQL Server database, you will need to create a JNDI datasource for your application server

142 Appendix D: Configuring Roambi ES to Use a SQL Server Database Configuring Tomcat 1. Read the documentation on the Tomcat web site for details on how to configure a JNDI data source. 2. Configure the JNDI data source: a. Identify the Roambi web application context path (usually roambi or ROOT). b. Create the file [ROAMBI_CONTEXT_PATH].xml (context path is case sensitive) in [ApplicationServer]/conf/Catalina/localhost c. Copy and paste this content. Pay close attention to the placeholders: <Context> <Resource name="jdbc/roambidatasource" type="javax.sql.datasource" description="roambi.datasource" driverclassname="net.sourceforge.jtds.jdbc.driver" maxactive="8" maxidle="4" url="jdbc:jtds:sqlserver://[server]:[port]/[database];" username="[username]" password="[password]" /> </Context> a. Replace these placeholders with the information provided by the database administrator: [Server]with the server name [Port] with the TCP/IP port [Database] with the database name [Username] with the username [Password] with the password 2. Restart Tomcat. Configuring JBoss 1. Read the documentation on the Red Hat JBoss web site for details on how to configure a JNDI data source 2. Configure the JNDI data source a. Identify the Roambi web application context path (usually roambi or ROOT) b. Create the file [ROAMBI_CONTEXT_PATH]-ds.xml (context path is case sensitive) in JBoss deployment folder that is usually at: $JBOSS_HOME/server/[DEPLOY_ INSTANCE]/deploy c. Copy and paste this content. Play close attention to the placeholders.

143

144 Configuring WebLogic <?xml version="1.0" encoding="utf-8"?> <datasources> <local-tx-datasource> <jndiname>roambidatasource</jndi-name> <connection-url> jdbc:jtds:sqlserver://[server]:[port]/[ Database] </connection-url> <driverclass>net.sourceforge.jtds.jdbc.driver</driverclass> <user-name>[username]</user-name> <password>[password]</password> <check-validconnection-sql>select getdate()</check-valid-connection-sql> </local-tx-datasource> </datasources> a. Replace the following placeholders with the information provided by the database administrator: [Server] with the server name [Port] with the TCP/IP port [Database] with the database name [Username] with the username [Password] with the password b. Navigate to: [Roambi Deployment Folder]/WEB-INF 2. Restart JBoss. i. Open jboss-web.xml on a text editor. ii. Uncomment the resource-ref element. iii. Open web.xml in a text editor. iv. Uncomment the resource-ref section. Configuring WebLogic Creating the JDBC Data Source 1. Set the Java Classpath in setdomainenv script to use the JDBC driver using the EXT_POST_ CLASSPATH environment variable: SET EXT_POST_CLASSPATH=%DOMAIN_HOME%\lib\jtds jar 2. Log in to the WebLogic Server Administration Console to configure your Java Naming and Directory Interface (JNDI) data source. 3. In the Domain Structure tree, select Services > Data Sources. 4. In the right panel select New > Generic Data Source. 5. Enter the following information:

145 SAP Americas Proprietary and Confidential

146 Appendix D: Configuring Roambi ES to Use a SQL Server Database Name: JDBC Data Source - Roambi JNDI Name: jdbc/roambidatasource (this is case sensitive) Database Type: MS SQL Server Database Driver: Other 6. Click Next. Then, click Next again. 7. Enter the following information: Database Name Host Name Port User Name Password 8. Click Next. 9. Enter the following information: Drive Class: net.sourceforge.jtds.jdbc.driver URL: jdbc:jtds:sqlserver://<hostname>:<db port>;databasename=<dbname> Properties: user=<username> 10. Click Test Configuration. 11. Click Next. 12. In the Select Targets page, select the name of the server where Roambi was deployed. 13. Click Finish. 14. In Roambi installation, open the web.xml file located in the [RoambiInstallation]/WEB-INF folder and uncomment the resource-ref section. 15. Restart the application server

147 Appendix E: Configuring SAP Roambi ES to Use Kerberos If you will be running Roambi ES in a Windows environment and plan to use Kerberos authentication, you will need to enable your application server to use Kerberos authentication. Enable Kerberos authentication by creating two configuration files for the application server and then pointing the application server to those files. Enabling Kerberos for Your Application Server To create the necessary configuration files and enable Kerberos authentication in your application server: 1. If you have not already done so for your server instance, create a file named login.conf in a text editor. The Java Authentication and Authorization Service (JAAS) uses the login.conf file for client authentication. The JVM settings for a server instance reference this file. 2. In the login.conf file, add your login module information: If you are not using Threat Management Gateway (TMG), add the following text: com.sun.security.jgss.initiate { com.sun.security.auth.module.krb5loginmodule required debug=true; }; com.sun.security.jgss.login { com.sun.security.auth.module.krb5loginmodule required debug=true; }; If you are using Threat Management Gateway (TMG), add the following lines of text: com.mellmo.roambi.http.spnego { com.mellmo.roambi.security.auth.activedirectoryloginmodule required

148 125 -

149 Appendix E: Configuring Roambi ES to Use Kerberos debug=true ldap.account=account ldap.password=password ldap.realm=example.com ldap.server=dc1.example.com debug=true; }; 3. Save your changes and close the file. 4. If it does not already exist, create a file named krb5.conf in your text editor. 5. The krb5.conf file contains Kerberos configuration information, including the following information: Location of Key Distribution Centers (KDCs) Administration servers for the Kerberos realms of interest Default settings for the current realm and Kerberos applications Mappings of host names to Kerberos realms 6. Add the following lines of text to the krb5.conf file: [libdefaults] udp_preference_limit = 1 default_realm = WindowsRealmName dns_lookup_kdc = true dns_lookup_realm = true forwardable = true proxiable = false [realms] WindowsRealmName = { default_domain = WindowsDomainName kdc = KeyDistributionServerName } The entries in the krb5.conf file must meet the following requirements: You must have a single space (and only a single space) before and after equals signs (=). You cannot have any spaces before the definition of a realm (WindowsRealmName). You must have a single tab (and only a single tab) before the entries for kdc = and default_domain =. 7. Replace the italicized text with the values for your Windows realm and Windows domain. All domain names and the KDC must be in uppercase. For example: [libdefaults] default_realm = MYCOMPANY.COM dns_lookup_kdc = true

150

151 Enabling Kerberos for Your Application Server dns_lookup_realm = true forwardable = true proxiable = false [realms] MYCOMPANY.COM = { } default_domain = MYCOMPANY.COM kdc = KDC.MYCOMPANY.COM 8. Copy these files to the server machine, and add their paths to the Java options for the application server: a. For Tomcat, go to the Windows Start menu and go to Monitor Tomcat. The Tomcat Properties window opens. b. On the Tomcat Properties window, click the Java tab: c. Scroll down to the bottom of the Java Options list, and add the following lines of text. Replace the italicized text with the correct paths for your login.conf and krb5.conf files: -Djava.security.auth.login.config=login.confPath\login.conf - Djava.security.krb5.conf=krb5Path\krb5.conf SAP Americas Proprietary and Confidential

152

153 Appendix E: Configuring Roambi ES to Use Kerberos -Dsun.security.krb5.debug=true d. Click OK and exit the Tomcat Properties window. 9. Verify that the Windows server where Roambi ES is installed has a Service Principal Name (SPN) defined and that the Tomcat service is using a valid Domain account. Note: If you want to provide complete end-to-end Kerberos authentication, disable the NT LAN manager (NTLM) in Windows

154 Appendix F: Adding a Bypass URL for Roambi Flow If Roambi Flow users experiences issues creating screen captures, and your Roambi ES configuration includes SSL, SSO, and/or a reverse proxy, you might need to set up a Bypass URL so that the Roambi server can access itself. To enable Tomcat so that wkhtmltoimage can communicate with Roambi ES: 1. In the directory where Tomcat is installed, navigate to the /conf directory and open the server.xml file in a text editor. 2. Add a new <Connector> element to the server.xml file. This new connector should be HTTP-only. 3. Configure your Windows firewall to block the new connector port from outside communication. 4. Edit the.roambi\config.json file to add the following attribute-value pair: "poc_host":"

155 Appendix G: SAP BusinessObjects JAR File Requirements If you will be using an SAP BusinessObjects portal, Roambi ES requires access to library files. This appendix details the JAR file requirements for each SAP BusinessObjects version. Included in this appendix: l SAP BusinessObjects XIR 2.X l SAP BusinessObjects XIR 3.0 l SAP BusinessObjects XIR 3.X l SAP BusinessObjects XIR 4.0 (SP2 Patch 11) l SAP BusinessObjects XIR 4.0 (SP2 Patch 12) l SAP BusinessObjects XIR 4.0 (SP2 Patch 14) l SAP BusinessObjects XIR 4.0 (SP4) l SAP BusinessObjects XIR 4.0 (SP5) l SAP BusinessObjects XIR4.0 (SP6) l SAP BusinessObjects XIR4.0 (SP7 Patch 1) l SAP BusinessObjects XIR 4.1 l SAP BusinessObjects XIR 4.1 (SP1)

156 Appendix G: SAP BusinessObjects JAR File Requirements l SAP BusinessObjects XIR 4.1 (SP2), (SP3), (SP4), (SP5),(SP6) l SAP BusinessObjects XIR 4.2 (SP2), (SP3), (SP4) SAP BusinessObjects XIR 2.X The following table details the JAR file requirements for SAP BusinessObjects XIR 2.X. Required JAR Files ebus405.jar boconfig.jar rasapp.jar cecore.jar rascore.jar celib.jar rebean.jar ceplugins.jar rebean.common.jar cereports.jar rebean.wi.jar cesession.jar serialization.jar corbaidl.jar wilog.jar SAP BusinessObjects XIR 3.0 The following table details the JAR file requirements for SAP BusinessObjects XIR 3.0.

157

158 SAP BusinessObjects XIR 3.X biplugins.jar boconfig.jar cecore.jar celib.jar ceplugins_core.jar ceplugins_cr.jar cereports.jar cesession.jar corbaidl.jar ebus405.jar jtools.jar Required File Names legacy_sl_plugins.jar logging.jar rasapp.jar rascore.jar rebean.jar rebean.common.jar rebean.wi.jar serialization.jar wilog.jar SAP BusinessObjects XIR 3.X The following table details the JAR file requirements for SAP BusinessObjects XIR 3.X.

159

160 Appendix G: SAP BusinessObjects JAR File Requirements biplugins.jar boconfig.jar cecore.jar celib.jar ceplugins_core.jar ceplugins_cr.jar cereports.jar cesession.jar corbaidl.jar ebus405.jar Required File Names jtools.jar logging.jar rasapp.jar rascore.jar rebean.jar rebean.common.jar rebean.wi.jar serialization.jar sl_plugins.jar wilog.jar SAP BusinessObjects XIR 4.0 (SP2 Patch 11) The following table details the JAR file requirments for SAP BusinessObjects XIR 4.X (SP2 Patch 11)

161 SAP BusinessObjects XIR 4.0 (SP2 Patch 11) Location JAR File Name aspectjrt.jar backport-util-concurrent-2.2.jar bcm.jar biplugins.jar boconfig.jar cdz_cluster_mgmt_types_idl.jar cdzidl.jar ceaspect.jar cecore.jar celib.jar ceplugins_core.jar ceplugins_cr.jar cereports.jar cesession.jar corbaidl.jar cryptojfips.jar CrystalReportsSDK.jar CTPlugin_idl.jar cvom.jar dsl_engine.jar dsl_sdk_commands.jar dsl_sdk_requests.jar dsl_sdk_server.jar dsl_sdk_services.jar dsws-biplatform.jar

162 Appendix G: SAP BusinessObjects JAR File Requirements Location dsws-common-util.jar dsws-common.jar dsws-session.jar ebus405.jar GenericContainer_idl.jar GenericContainer_proxy.jar guice-1.0.jar ie_proxies.jar IEPlugin_idl.jar inproc_container.jar jaxen jar jtools.jar logging.jar JAR File Name org.eclipse.emf.common_2.4.0.v jar org.eclipse.emf.ecore_2.4.2.v jar org.eclipse.emf.ecore.xmi_2.4.1.v jar org.eclipse.equinox.common_3.4.0.v jar org.eclipse.equinox.registry_3.4.0.v jar org.eclipse.osgi_3.4.3.r34x_v jar protobuf.jar pub_common.jar ras21core.jar ras21proc.jar

163 SAP BusinessObjects XIR 4.0 (SP2 Patch 11) Location JAR File Name ras21sdk.jar rebean.common.jar rebean.wi.adapter.jar rebean.wi.jar rebean.wi.model.jar rebean.wi.server.commands.jar rebean.wi.server.jar rebean.wi.server.requests.jar rom.jar sdk.core.jar sdk.core.server.common.jar sdk.core.server.corba.jar sdk.core.server.jar sdk.core.session.cms.jar sdk.core.session.jar SL_plugins.jar stax-api jar TraceLog.jar webi_proxies.jar wilog.jar wsdl4j jar wstx-asl jar xalan.jar xercesimpl.jar

164 Appendix G: SAP BusinessObjects JAR File Requirements Location \external \external\axis2\1.4 warfiles\webapps\dswsbobje\web-inf\lib wdeploy\ant\lib web services\en\dsws_consumer\data\dswsjavaapi JAR File Name xml-apis.jar XmlSchema jar xmlbeans jar geronimo-stax-api_1.0_spec jar dsws-webishared-provider.jar ant-launcher.jar dsws-reportengine.jar SAP BusinessObjects XIR 4.0 (SP2 Patch 12) The following table details the JAR file requirments for SAP BusinessObjects XIR 4.X (SP2 Patch 12)

165 SAP BusinessObjects XIR 4.0 (SP2 Patch 12) Location JAR File Name aspectjrt.jar backport-util-concurrent-2.2.jar bcm.jar biplugins.jar boconfig.jar cdz_cluster_mgmt_types_idl.jar cdzidl.jar ceaspect.jar cecore.jar celib.jar ceplugins_core.jar ceplugins_cr.jar cereports.jar cesession.jar corbaidl.jar cryptojfips.jar CrystalReportsSDK.jar CTPlugin_idl.jar cvom.jar dsl_engine.jar dsl_sdk_commands.jar dsl_sdk_requests.jar dsl_sdk_server.jar dsl_sdk_services.jar dsws-biplatform.jar

166 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name dsws-common-util.jar dsws-common.jar dsws-session.jar ebus405.jar GenericContainer_idl.jar GenericContainer_proxy.jar guice-1.0.jar ie_proxies.jar IEPlugin_idl.jar inproc_container.jar jaxen jar jtools.jar logging.jar org.eclipse.emf.common_2.4.0.v j ar org.eclipse.emf.ecore_2.4.2.v ja r org.eclipse.emf.ecore.xmi_2.4.1.v jar org.eclipse.equinox.common_3.4.0.v jar org.eclipse.equinox.registry_3.4.0.v jar org.eclipse.osgi_3.4.3.r34x_v jar protobuf.jar pub_common.jar ras21core.jar ras21proc.jar ras21sdk.jar rebean.common.jar

167

168 SAP BusinessObjects XIR 4.0 (SP2 Patch 12) Location \external JAR File Name rebean.wi.adapter.jar rebean.wi.jar rebean.wi.model.jar rebean.wi.server.commands.jar rebean.wi.server.jar rebean.wi.server.requests.jar rom.jar sdk.core.jar sdk.core.server.common.jar sdk.core.server.corba.jar sdk.core.server.jar sdk.core.session.cms.jar sdk.core.session.jar SL_plugins.jar stax-api jar TraceLog.jar webi_proxies.jar wilog.jar wsdl4j jar wstx-asl jar xalan.jar xercesimpl.jar xml-apis.jar XmlSchema jar xmlbeans jar

169 Appendix G: SAP BusinessObjects JAR File Requirements Location \external\axis2\1.4 warfiles\webapps\dswsbobje\web-inf\lib wdeploy\ant\lib JAR File Name geronimo-stax-api_1.0_spec jar dsws-webishared-provider.jar ant-launcher.jar web services\en\dsws_consumer\data\dswsjavaapi dswsreportengine.jar SAP BusinessObjects XIR 4.0 (SP2 Patch 14) The following table details the JAR file requirements for SAP BusinessObjects XIR 4.X (SP2 Patch 14).

170

171 SAP BusinessObjects XIR 4.0 (SP2 Patch 14) Location JAR File Name Path aspectjrt.jar \aspectjrt.jar backport-util-concurrent- 2.2.jar \backport-util-concurrent- 2.2.jar bcm.jar \bcm.jar biplugins.jar \biplugins.jar boconfig.jar \boconfig.jar cdz_cluster_mgmt_types_idl.j ar \cdz_cluster_mgmt_types_idl.jar cdzidl.jar \cdzidl.jar ceaspect.jar \ceaspect.jar cecore.jar \cecore.jar celib.jar \celib.jar ceplugins_core.jar \ceplugins_core.jar ceplugins_cr.jar \ceplugins_cr.jar cereports.jar \cereports.jar cesession.jar \cesession.jar corbaidl.jar \corbaidl.jar cryptojfips.jar \cryptojfips.jar CrystalReportsSDK.jar \CrystalReportsSDK.jar CTPlugin_idl.jar \CTPlugin_idl.jar cvom.jar \cvom.jar dsl_engine.jar \dsl_engine.jar dsl_sdk_commands.jar \dsl_sdk_commands.jar dsl_sdk_requests.jar \dsl_sdk_requests.jar dsl_sdk_server.jar \dsl_sdk_server.jar dsl_sdk_services.jar \dsl_sdk_services.jar dsws-biplatform.jar \dsws-biplatform.jar

172

173 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name Path dsws-common-util.jar \dsws-common-util.jar dsws-common.jar \dsws-common.jar dsws-session.jar \dsws-session.jar ebus405.jar \ebus405.jar GenericContainer_idl.jar \GenericContainer_idl.jar GenericContainer_proxy.jar \GenericContainer_proxy.jar guice-1.0.jar \guice-1.0.jar ie_proxies.jar \ie_proxies.jar IEPlugin_idl.jar \IEPlugin_idl.jar inproc_container.jar \inproc_container.jar jaxen jar \jaxen jar jtools.jar \jtools.jar logging.jar \logging.jar org.eclipse.emf.common_ v jar org.eclipse.emf.ecore_ v jar org.eclipse.emf.ecore.xmi_ v jar org.eclipse.equinox.common_ v jar org.eclipse.equinox.registry _ v jar org.eclipse.osgi_3.4.3.r34x_ v jar \org.eclipse.emf.common_ v jar \org.eclipse.emf.ecore_ v jar \org.eclipse.emf.ecore.xmi_ v jar \org.eclipse.equinox.common _ v jar \org.eclipse.equinox.regist ry_ v jar \org.eclipse.osgi_3.4.3.r34 x_ v jar protobuf.jar \protobuf.jar pub_common.jar \pub_common.jar

174

175 SAP BusinessObjects XIR 4.0 (SP2 Patch 14) Location JAR File Name Path ras21core.jar \ras21core.jar ras21proc.jar \ras21proc.jar ras21sdk.jar \ras21sdk.jar rebean.common.jar \rebean.common.jar rebean.wi.adapter.jar \rebean.wi.adapter.jar rebean.wi.jar \rebean.wi.jar rebean.wi.model.jar \rebean.wi.model.jar rebean.wi.server.commands.ja r \rebean.wi.server.commands. jar rebean.wi.server.jar \rebean.wi.server.jar rebean.wi.server.requests.ja r \rebean.wi.server.requests. jar rom.jar \rom.jar sdk.core.jar \sdk.core.jar sdk.core.server.common.jar \sdk.core.server.common.jar sdk.core.server.corba.jar \sdk.core.server.corba.jar sdk.core.server.jar \sdk.core.server.jar sdk.core.session.cms.jar \sdk.core.session.cms.jar sdk.core.session.jar \sdk.core.session.jar SL_plugins.jar \SL_plugins.jar stax-api jar \stax-api jar TraceLog.jar \TraceLog.jar webi_proxies.jar \webi_proxies.jar wilog.jar \wilog.jar wsdl4j jar \wsdl4j jar wstx-asl jar \wstx-asl jar xalan.jar \xalan.jar

176

177 Appendix G: SAP BusinessObjects JAR File Requirements \external\axis2\1. 4 warfiles\webapps\dswsbobje \WEB- geronimo-stax-api_1.0_spec jar \external\axis2\1.4\geronim o-staxapi_1.0_spec jar Location JAR File Name Path xercesimpl.jar \xercesimpl.jar xml-apis.jar \xml-apis.jar XmlSchema jar \XmlSchema jar \external xmlbeans jar \external\xmlbeans jar dsws-webishared-provider.jar warfiles\webapps\dswsbobje\web- INF\lib\dsws-webisharedprovider.jar INF\lib wdeploy\ant\lib ant-launcher.jar wdeploy\ant\lib\ant-launcher.jar web services\en\dsws_ consumer\data\dswsjavaapi dsws-reportengine.jar SAP BusinessObjects XIR 4.0 (SP4) The following table details the JAR file requirements for SAP BusinessObjects XIR 4.X (SP4). web services\en\dsws_ consumer\data\dswsjavaapi\dswsreportengine.jar

178

179 SAP BusinessObjects XIR 4.0 (SP4) Location JAR File Name Path aspectjrt.jar \aspectjrt.jar backport-util-concurrent- 2.2.jar \backport-util-concurrent- 2.2.jar bcm.jar \bcm.jar biplugins.jar \biplugins.jar boconfig.jar \boconfig.jar cdz_cluster_mgmt_types_idl.ja \cdz_cluster_mgmt_types_idl.j r ar cdzidl.jar \cdzidl.jar ceaspect.jar \ceaspect.jar cecore.jar \cecore.jar celib.jar \celib.jar ceplugins_core.jar \ceplugins_core.jar ceplugins_cr.jar \ceplugins_cr.jar cereports.jar \cereports.jar cesession.jar \cesession.jar corbaidl.jar \corbaidl.jar cryptojfips.jar \cryptojfips.jar CrystalReportsSDK.jar \CrystalReportsSDK.jar CTPlugin_idl.jar \CTPlugin_idl.jar cvom.jar \cvom.jar dsl_engine.jar \dsl_engine.jar dsl_sdk_commands.jar \dsl_sdk_commands.jar dsl_sdk_requests.jar \dsl_sdk_requests.jar dsl_sdk_server.jar \dsl_sdk_server.jar dsl_sdk_services.jar \dsl_sdk_services.jar dsws-biplatform.jar \dsws-biplatform.jar

180

181 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name Path dsws-common-util.jar \dsws-common-util.jar dsws-common.jar \dsws-common.jar dsws-session.jar \dsws-session.jar ebus405.jar \ebus405.jar GenericContainer_idl.jar \GenericContainer_idl.jar GenericContainer_proxy.jar \GenericContainer_proxy.jar guice-1.0.jar \guice-1.0.jar ie_proxies.jar \ie_proxies.jar IEPlugin_idl.jar \IEPlugin_idl.jar inproc_container.jar \inproc_container.jar jaxen jar \jaxen jar jtools.jar \jtools.jar logging.jar \logging.jar org.eclipse.emf.common_ v jar org.eclipse.emf.ecore_ v jar org.eclipse.emf.ecore.xmi_ v jar \org.eclipse.emf.common_ v jar \org.eclipse.emf.ecore_ v jar \org.eclipse.emf.ecore.xmi_ v jar org.eclipse.equinox.common_ \org.eclipse.equinox.common_ v jar v jar \org.eclipse.equinox.registry org.eclipse.equinox.registry v jar v jar org.eclipse.osgi_3.4.3.r34x_ \org.eclipse.osgi_3.4.3.r34x_ v jar v jar protobuf.jar \protobuf.jar pub_common.jar \pub_common.jar

182

183 SAP BusinessObjects XIR 4.0 (SP4) Location JAR File Name Path ras21core.jar \ras21core.jar ras21proc.jar \ras21proc.jar ras21sdk.jar \ras21sdk.jar rebean.common.jar \rebean.common.jar rebean.wi.adapter.jar \rebean.wi.adapter.jar rebean.wi.jar \rebean.wi.jar rebean.wi.model.jar \rebean.wi.model.jar \rebean.wi.server.commands.ja rebean.wi.server.commands.jar r rebean.wi.server.jar \rebean.wi.server.jar \rebean.wi.server.requests.ja rebean.wi.server.requests.jar r rom.jar \rom.jar sdk.core.jar \sdk.core.jar sdk.core.server.common.jar \sdk.core.server.common.jar sdk.core.server.corba.jar \sdk.core.server.corba.jar sdk.core.server.jar \sdk.core.server.jar sdk.core.session.cms.jar \sdk.core.session.cms.jar sdk.core.session.jar \sdk.core.session.jar SL_plugins.jar \SL_plugins.jar stax-api jar \stax-api jar TraceLog.jar \TraceLog.jar webi_proxies.jar \webi_proxies.jar wsdl4j jar \wsdl4j jar wstx-asl jar \wstx-asl jar xalan.jar \xalan.jar xercesimpl.jar \xercesimpl.jar

184

185 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name Path xml-apis.jar \xml-apis.jar XmlSchema jar \XmlSchema jar \external\axis2\1.4\geronimo- \external\axis2\1. geronimo-stax-api_1.0_spec- stax jar api_1.0_spec jar warfiles\webapps\dswsbobje warfiles\webapps\dswsbobje\web- \WEB- INF\lib\dswsdsws-webishared-provider.jar INF\lib webishared-provider.jar wdeploy\ant\lib ant-launcher.jar wdeploy\ant\lib\ant-launcher.jar web services\en\dsws_ consumer\data\dswsjavaapi dsws-reportengine.jar SAP BusinessObjects XIR 4.0 (SP5) The following table details the JAR file requirements for SAP BusinessObjects XIR 4.X (SP5). web services\en\dsws_ consumer\data\dswsjavaapi\dswsreportengine.jar

186

187 SAP BusinessObjects XIR 4.0 (SP5) Location JAR File Name Path aspectjrt.jar \aspectjrt.jar backport-util-concurrent- 2.2.jar \backport-util-concurrent- 2.2.jar bcm.jar \bcm.jar biplugins.jar \biplugins.jar boconfig.jar \boconfig.jar cdz_cluster_mgmt_types_idl.ja \cdz_cluster_mgmt_types_idl.j r ar cdzidl.jar \cdzidl.jar ceaspect.jar \ceaspect.jar cecore.jar \cecore.jar celib.jar \celib.jar ceplugins_core.jar \ceplugins_core.jar ceplugins_cr.jar \ceplugins_cr.jar cereports.jar \cereports.jar cesession.jar \cesession.jar corbaidl.jar \corbaidl.jar cryptojfips.jar \cryptojfips.jar CrystalReportsSDK.jar \CrystalReportsSDK.jar CTPlugin_idl.jar \CTPlugin_idl.jar cvom.jar \cvom.jar dsl_engine.jar \dsl_engine.jar dsl_sdk_commands.jar \dsl_sdk_commands.jar dsl_sdk_requests.jar \dsl_sdk_requests.jar dsl_sdk_server.jar \dsl_sdk_server.jar dsl_sdk_services.jar \dsl_sdk_services.jar dsws-biplatform.jar \dsws-biplatform.jar

188

189 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name Path dsws-common-util.jar \dsws-common-util.jar dsws-common.jar \dsws-common.jar dsws-session.jar \dsws-session.jar ebus405.jar \ebus405.jar GenericContainer_idl.jar \GenericContainer_idl.jar GenericContainer_proxy.jar \GenericContainer_proxy.jar guice-1.0.jar \guice-1.0.jar ie_proxies.jar \ie_proxies.jar IEPlugin_idl.jar \IEPlugin_idl.jar inproc_container.jar \inproc_container.jar jaxen jar \jaxen jar jtools.jar \jtools.jar logging.jar \logging.jar org.eclipse.emf.common_ v jar org.eclipse.emf.ecore_ v jar org.eclipse.emf.ecore.xmi_ v jar \org.eclipse.emf.common_ v jar \org.eclipse.emf.ecore_ v jar \org.eclipse.emf.ecore.xmi_ v jar org.eclipse.equinox.common_ \org.eclipse.equinox.common_ v jar v jar \org.eclipse.equinox.registry org.eclipse.equinox.registry v jar v jar org.eclipse.osgi_3.4.3.r34x_ \org.eclipse.osgi_3.4.3.r34x_ v jar v jar protobuf.jar \protobuf.jar pub_common.jar \pub_common.jar

190

191 SAP BusinessObjects XIR 4.0 (SP5) Location JAR File Name Path ras21core.jar \ras21core.jar ras21proc.jar \ras21proc.jar ras21sdk.jar \ras21sdk.jar rebean.common.jar \rebean.common.jar rebean.wi.adapter.jar \rebean.wi.adapter.jar rebean.wi.jar \rebean.wi.jar rebean.wi.model.jar \rebean.wi.model.jar \rebean.wi.server.commands.ja rebean.wi.server.commands.jar r rebean.wi.server.jar \rebean.wi.server.jar \rebean.wi.server.requests.ja rebean.wi.server.requests.jar r rom.jar \rom.jar sdk.core.jar \sdk.core.jar sdk.core.server.common.jar \sdk.core.server.common.jar sdk.core.server.corba.jar \sdk.core.server.corba.jar sdk.core.server.jar \sdk.core.server.jar sdk.core.session.cms.jar \sdk.core.session.cms.jar sdk.core.session.jar \sdk.core.session.jar SL_plugins.jar \SL_plugins.jar stax-api jar \stax-api jar TraceLog.jar \TraceLog.jar webi_proxies.jar \webi_proxies.jar wsdl4j jar \wsdl4j jar wstx-asl jar \wstx-asl jar xalan.jar \xalan.jar xercesimpl.jar \xercesimpl.jar

192

193 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name Path xml-apis.jar \xml-apis.jar XmlSchema jar \XmlSchema jar \external\axis2\1.4\geronimo- \external\axis2\1. geronimo-stax-api_1.0_spec- stax jar api_1.0_spec jar warfiles\webapps\dswsbobje warfiles\webapps\dswsbobje\web- \WEB- INF\lib\dswsdsws-webishared-provider.jar INF\lib webishared-provider.jar wdeploy\ant\lib ant-launcher.jar wdeploy\ant\lib\ant-launcher.jar web services\en\dsws_ consumer\data\dswsjavaapi dsws-reportengine.jar SAP BusinessObjects XIR 4.0 (SP6) The following table details the JAR file requirements for SAP BusinessObjects XIR 4.X (SP6). web services\en\dsws_ consumer\data\dswsjavaapi\dswsreportengine.jar

194

195 SAP BusinessObjects XIR 4.0 (SP6) Location JAR File Name Path aspectjrt.jar \aspectjrt.jar backport-util-concurrent- 2.2.jar \backport-util-concurrent- 2.2.jar bcm.jar \bcm.jar biplugins.jar \biplugins.jar boconfig.jar \boconfig.jar cdz_cluster_mgmt_types_idl.ja \cdz_cluster_mgmt_types_idl.j r ar cdzidl.jar \cdzidl.jar ceaspect.jar \ceaspect.jar cecore.jar \cecore.jar celib.jar \celib.jar ceplugins_core.jar \ceplugins_core.jar ceplugins_cr.jar \ceplugins_cr.jar cereports.jar \cereports.jar cesession.jar \cesession.jar corbaidl.jar \corbaidl.jar cryptojfips.jar \cryptojfips.jar CrystalReportsSDK.jar \CrystalReportsSDK.jar CTPlugin_idl.jar \CTPlugin_idl.jar cvom.jar \cvom.jar dsl_engine.jar \dsl_engine.jar dsl_sdk_commands.jar \dsl_sdk_commands.jar dsl_sdk_requests.jar \dsl_sdk_requests.jar dsl_sdk_server.jar \dsl_sdk_server.jar dsl_sdk_services.jar \dsl_sdk_services.jar dsws-biplatform.jar \dsws-biplatform.jar

196

197 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name Path dsws-common-util.jar \dsws-common-util.jar dsws-common.jar \dsws-common.jar dsws-session.jar \dsws-session.jar ebus405.jar \ebus405.jar GenericContainer_idl.jar \GenericContainer_idl.jar GenericContainer_proxy.jar \GenericContainer_proxy.jar guice-1.0.jar \guice-1.0.jar ie_proxies.jar \ie_proxies.jar IEPlugin_idl.jar \IEPlugin_idl.jar inproc_container.jar \inproc_container.jar jaxen jar \jaxen jar jtools.jar \jtools.jar logging.jar \logging.jar org.eclipse.emf.common_ v jar org.eclipse.emf.ecore_ v jar org.eclipse.emf.ecore.xmi_ v jar \org.eclipse.emf.common_ v jar \org.eclipse.emf.ecore_ v jar \org.eclipse.emf.ecore.xmi_ v jar org.eclipse.equinox.common_ \org.eclipse.equinox.common_ v jar v jar \org.eclipse.equinox.registry org.eclipse.equinox.registry v jar v jar org.eclipse.osgi_3.4.3.r34x_ \org.eclipse.osgi_3.4.3.r34x_ v jar v jar protobuf.jar \protobuf.jar pub_common.jar \pub_common.jar

198

199 SAP BusinessObjects XIR 4.0 (SP6) Location JAR File Name Path ras21core.jar \ras21core.jar ras21proc.jar \ras21proc.jar ras21sdk.jar \ras21sdk.jar rebean.common.jar \rebean.common.jar rebean.wi.adapter.jar \rebean.wi.adapter.jar rebean.wi.jar \rebean.wi.jar rebean.wi.model.jar \rebean.wi.model.jar \rebean.wi.server.commands.ja rebean.wi.server.commands.jar r rebean.wi.server.jar \rebean.wi.server.jar \rebean.wi.server.requests.ja rebean.wi.server.requests.jar r rom.jar \rom.jar sdk.core.jar \sdk.core.jar sdk.core.server.common.jar \sdk.core.server.common.jar sdk.core.server.corba.jar \sdk.core.server.corba.jar sdk.core.server.jar \sdk.core.server.jar sdk.core.session.cms.jar \sdk.core.session.cms.jar sdk.core.session.jar \sdk.core.session.jar SL_plugins.jar \SL_plugins.jar stax-api jar \stax-api jar TraceLog.jar \TraceLog.jar webi_proxies.jar \webi_proxies.jar wsdl4j jar \wsdl4j jar wstx-asl jar \wstx-asl jar xalan.jar \xalan.jar xercesimpl.jar \xercesimpl.jar

200

201 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name Path xml-apis.jar \xml-apis.jar XmlSchema jar \XmlSchema jar \external\axis2\1.4\geronimo- \external\axis2\1. geronimo-stax-api_1.0_spec- stax jar api_1.0_spec jar warfiles\webapps\dswsbobje warfiles\webapps\dswsbobje\web- \WEB- INF\lib\dswsdsws-webishared-provider.jar INF\lib webishared-provider.jar wdeploy\ant\lib ant-launcher.jar wdeploy\ant\lib\ant-launcher.jar web services\en\dsws_ consumer\data\dswsjavaapi dsws-reportengine.jar web services\en\dsws_ consumer\data\dswsjavaapi\dswsreportengine.jar SAP BusinessObjects XIR 4.0 (SP7 Patch 1) The following table details the JAR file requirements for SAP BusinessObjects XIR 4.0 (SP7 Patch 1).

202

203 SAP BusinessObjects XIR 4.0 (SP7 Patch 1) Location JAR File Name Path aspectjrt.jar \aspectjrt.jar backport-util-concurrent- 2.2.jar \backport-util-concurrent- 2.2.jar bcm.jar \bcm.jar biplugins.jar \biplugins.jar boconfig.jar \boconfig.jar cdz_cluster_mgmt_types_idl.ja \cdz_cluster_mgmt_types_idl.j r ar cdzidl.jar \cdzidl.jar ceaspect.jar \ceaspect.jar cecore.jar \cecore.jar celib.jar \celib.jar ceplugins_core.jar \ceplugins_core.jar ceplugins_cr.jar \ceplugins_cr.jar cereports.jar \cereports.jar cesession.jar \cesession.jar corbaidl.jar \corbaidl.jar cryptojfips.jar \cryptojfips.jar CrystalReportsSDK.jar \CrystalReportsSDK.jar CTPlugin_idl.jar \CTPlugin_idl.jar cvom.jar \cvom.jar dsl_engine.jar \dsl_engine.jar dsl_sdk_commands.jar \dsl_sdk_commands.jar dsl_sdk_requests.jar \dsl_sdk_requests.jar dsl_sdk_server.jar \dsl_sdk_server.jar dsl_sdk_services.jar \dsl_sdk_services.jar dsws-biplatform.jar \dsws-biplatform.jar

204

205 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name Path dsws-common-util.jar \dsws-common-util.jar dsws-common.jar \dsws-common.jar dsws-session.jar \dsws-session.jar ebus405.jar \ebus405.jar GenericContainer_idl.jar \GenericContainer_idl.jar GenericContainer_proxy.jar \GenericContainer_proxy.jar guice-1.0.jar \guice-1.0.jar ie_proxies.jar \ie_proxies.jar IEPlugin_idl.jar \IEPlugin_idl.jar inproc_container.jar \inproc_container.jar jaxen jar \jaxen jar jtools.jar \jtools.jar logging.jar \logging.jar org.eclipse.emf.common_ v jar org.eclipse.emf.ecore_ v jar org.eclipse.emf.ecore.xmi_ v jar \org.eclipse.emf.common_ v jar \org.eclipse.emf.ecore_ v jar \org.eclipse.emf.ecore.xmi_ v jar org.eclipse.equinox.common_ \org.eclipse.equinox.common_ v jar v jar \org.eclipse.equinox.registry org.eclipse.equinox.registry v jar v jar org.eclipse.osgi_3.4.3.r34x_ \org.eclipse.osgi_3.4.3.r34x_ v jar v jar protobuf.jar \protobuf.jar pub_common.jar \pub_common.jar

206

207 SAP BusinessObjects XIR 4.0 (SP7 Patch 1) Location JAR File Name Path ras21core.jar \ras21core.jar ras21proc.jar \ras21proc.jar ras21sdk.jar \ras21sdk.jar rebean.common.jar \rebean.common.jar rebean.wi.adapter.jar \rebean.wi.adapter.jar rebean.wi.jar \rebean.wi.jar rebean.wi.model.jar \rebean.wi.model.jar \rebean.wi.server.commands.ja rebean.wi.server.commands.jar r rebean.wi.server.jar \rebean.wi.server.jar \rebean.wi.server.requests.ja rebean.wi.server.requests.jar r rom.jar \rom.jar sdk.core.jar \sdk.core.jar sdk.core.server.common.jar \sdk.core.server.common.jar sdk.core.server.corba.jar \sdk.core.server.corba.jar sdk.core.server.jar \sdk.core.server.jar sdk.core.session.cms.jar \sdk.core.session.cms.jar sdk.core.session.jar \sdk.core.session.jar SL_plugins.jar \SL_plugins.jar stax-api jar \stax-api jar TraceLog.jar \TraceLog.jar webi_proxies.jar \webi_proxies.jar wsdl4j jar \wsdl4j jar wstx-asl jar \wstx-asl jar xalan.jar \xalan.jar xercesimpl.jar \xercesimpl.jar

208 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name Path xml-apis.jar \xml-apis.jar XmlSchema jar \XmlSchema jar \external\axis2\1.4\geronimo- \external\axis2\1. geronimo-stax-api_1.0_spec- stax jar api_1.0_spec jar warfiles\webapps\dswsbobje warfiles\webapps\dswsbobje\web- \WEB- INF\lib\dswsdsws-webishared-provider.jar INF\lib webishared-provider.jar wdeploy\ant\lib ant-launcher.jar wdeploy\ant\lib\ant-launcher.jar web services\en\dsws_ consumer\data\dswsjavaapi dsws-reportengine.jar web services\en\dsws_ consumer\data\dswsjavaapi\dswsreportengine.jar SAP BusinessObjects XIR 4.1 The following table details the JAR file requirements for SAP BusinessObjects XIR

209 SAP BusinessObjects XIR 4.1 Location JAR File Name Path wdeploy\ant\lib ant-launcher.jar wdeploy\ant\lib\ant-launcher.jar aspectjrt.jar \aspectjrt.jar bcm.jar \bcm.jar biplugins.jar \biplugins.jar boconfig.jar \boconfig.jar cdz_cluster_mgmt_types_idl.ja \cdz_cluster_mgmt_types_idl.j r ar cdzidl.jar \cdzidl.jar ceaspect.jar \ceaspect.jar cecore.jar \cecore.jar celib.jar \celib.jar ceplugins_core.jar \ceplugins_core.jar ceplugins_cr.jar \ceplugins_cr.jar cereports.jar \cereports.jar cesession.jar \cesession.jar corbaidl.jar \corbaidl.jar cryptojfips.jar \cryptojfips.jar CrystalReportsSDK.jar \CrystalReportsSDK.jar CTPlugin_idl.jar \CTPlugin_idl.jar cvom.jar \cvom.jar dsl_engine.jar \dsl_engine.jar dsl_sdk_commands.jar \dsl_sdk_commands.jar dsl_sdk_requests.jar \dsl_sdk_requests.jar dsl_sdk_server.jar \dsl_sdk_server.jar dsl_sdk_services.jar \dsl_sdk_services.jar dsws-biplatform.jar \dsws-biplatform.jar

210 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name Path webservices\en\dsws_ consumer\data\dswsja vaapi warfiles\webapps\dswsbobj e\web-inf\lib \external\axis2\1.4 dsws-common-util.jar dsws-common.jar dsws-reportengine.jar dsws-session.jar ebus405.jar GenericContainer_idl.ja r GenericContainer_proxy. jar guice-1.0.jar ie_proxies.jar IEPlugin_idl.jar inproc_container.jar \external\axis2\ jaxen jar \dsws-common-util.jar \dsws-common.jar web services\en\dsws_ consumer\data\dswsjavaapi \dsws-reportengine.jar \dsws-session.jar dsws-webisharedprovider.jar geronimo-staxapi_1.0_spec jar warfiles\webapps\dswsbobje\web- INF\lib\dsws-webishared-provider.jar \ebus405.jar \GenericContainer_idl.jar \GenericContainer_proxy.jar \external\axis2\1.4\geroni mo-stax-api_1.0_spec jar \guice-1.0.jar \ie_proxies.jar \IEPlugin_idl.jar \inproc_container.jar jtools.jar logging.jar org.eclipse.emf.common_ v jar org.eclipse.emf.ecore_ \jtools.jar \logging.jar \org.eclipse.emf.common_ v jar

211 SAP BusinessObjects XIR 4.1 Location JAR File Name Path v jar v jar \org.eclipse.equinox.registry org.eclipse.equinox.registry v jar v jar org.eclipse.osgi_3.4.3.r34x_ \org.eclipse.osgi_3.4.3.r34x_ v jar v jar protobuf.jar \protobuf.jar pub_common.jar \pub_common.jar ras21core.jar \ras21core.jar ras21proc.jar \ras21proc.jar ras21sdk.jar \ras21sdk.jar rebean.common.jar \rebean.common.jar rebean.wi.adapter.jar \rebean.wi.adapter.jar rebean.wi.jar \rebean.wi.jar rebean.wi.model.jar \rebean.wi.model.jar \rebean.wi.server.commands.ja rebean.wi.server.commands.jar r rebean.wi.server.jar \rebean.wi.server.jar \rebean.wi.server.requests.ja rebean.wi.server.requests.jar r rom.jar \rom.jar sdk.core.jar \sdk.core.jar sdk.core.server.common.jar \sdk.core.server.common.jar sdk.core.server.corba.jar \sdk.core.server.corba.jar sdk.core.server.jar \sdk.core.server.jar sdk.core.session.cms.jar \sdk.core.session.cms.jar sdk.core.session.jar \sdk.core.session.jar SL_plugins.jar \SL_plugins.jar TraceLog.jar \TraceLog.jar

212 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name Path webi_proxies.jar \webi_proxies.jar \external\axis2\1. \external\axis2\1.6.2\wsdl4j- 6.2 wsdl4j jar \external\axis2\ wstx-asl jar jar \external\axis2\1.6.2\wstx- asl jar xalan.jar \xalan.jar xercesimpl.jar \xercesimpl.jar xml-apis.jar \xml-apis.jar \external\axis2\ XmlSchema jar SAP BusinessObjects XIR 4.1 (SP1) The following table details the JAR file requirements for SAP BusinessObjects XIR 4.1 (SP1). \external\axis2\1.6.2\xmlsche ma jar

213 SAP BusinessObjects XIR 4.1 (SP1) Location JAR File Name Path wdeploy\ant\lib ant-launcher.jar wdeploy\ant\lib\ant-launcher.jar aspectjrt.jar \aspectjrt.jar bcm.jar \bcm.jar biplugins.jar \biplugins.jar boconfig.jar \boconfig.jar cdz_cluster_mgmt_types_idl.ja \cdz_cluster_mgmt_types_idl.j r ar cdzidl.jar \cdzidl.jar ceaspect.jar \ceaspect.jar cecore.jar \cecore.jar celib.jar \celib.jar ceplugins_core.jar \ceplugins_core.jar ceplugins_cr.jar \ceplugins_cr.jar cereports.jar \cereports.jar cesession.jar \cesession.jar corbaidl.jar \corbaidl.jar cryptojfips.jar \cryptojfips.jar CrystalReportsSDK.jar \CrystalReportsSDK.jar CTPlugin_idl.jar \CTPlugin_idl.jar cvom.jar \cvom.jar dsl_engine.jar \dsl_engine.jar dsl_sdk_commands.jar \dsl_sdk_commands.jar dsl_sdk_requests.jar \dsl_sdk_requests.jar dsl_sdk_server.jar \dsl_sdk_server.jar dsl_sdk_services.jar \dsl_sdk_services.jar dsws-biplatform.jar \dsws-biplatform.jar

214 Appendix G: SAP BusinessObjects JAR File Requirements web services\en\dsws_ Location JAR File Name Path consumer\data\dswsja vaapi warfiles\webapps\dswsbobj e\web-inf\lib \external\axis2\1.4 dsws-common-util.jar dsws-common.jar dsws-reportengine.jar dsws-session.jar dsws-webishared-provider.jar ebus405.jar GenericContainer_idl.ja r GenericContainer_proxy. jar guice-1.0.jar ie_proxies.jar IEPlugin_idl.jar inproc_container.jar \dsws-common-util.jar \dsws-common.jar web services\en\dsws_ geronimo-staxapi_1.0_spec jar consumer\data\dswsjavaapi\dswsreportengine.jar \dsws-session.jar warfiles\webapps\dswsbobje\web- INF\lib\dsws-webishared-provider.jar \ebus405.jar \GenericContainer_idl.jar \GenericContainer_proxy.jar \external\axis2\1.6.2\geroni mo-stax-api_1.0_spec jar \guice-1.0.jar \ie_proxies.jar \IEPlugin_idl.jar \inproc_container.jar

215 SAP BusinessObjects XIR 4.1 (SP1) Location JAR File Name Path v jar v jar \org.eclipse.equinox.registry org.eclipse.equinox.registry v jar v jar org.eclipse.osgi_3.4.3.r34x_ \org.eclipse.osgi_3.4.3.r34x_ v jar v jar protobuf.jar \protobuf.jar pub_common.jar \pub_common.jar ras21core.jar \ras21core.jar ras21proc.jar \ras21proc.jar ras21sdk.jar \ras21sdk.jar rebean.common.jar \rebean.common.jar rebean.wi.adapter.jar \rebean.wi.adapter.jar rebean.wi.jar \rebean.wi.jar rebean.wi.model.jar \rebean.wi.model.jar \rebean.wi.server.commands.ja rebean.wi.server.commands.jar r rebean.wi.server.jar \rebean.wi.server.jar \rebean.wi.server.requests.ja rebean.wi.server.requests.jar r rom.jar \rom.jar sdk.core.jar \sdk.core.jar sdk.core.server.common.jar \sdk.core.server.common.jar sdk.core.server.corba.jar \sdk.core.server.corba.jar sdk.core.server.jar \sdk.core.server.jar sdk.core.session.cms.jar \sdk.core.session.cms.jar sdk.core.session.jar \sdk.core.session.jar SL_plugins.jar \SL_plugins.jar TraceLog.jar \TraceLog.jar

216 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name Path webi_proxies.jar \webi_proxies.jar \external\axis2\1. \external\axis2\1.6.2\wsdl4j- 6.2 wsdl4j jar \external\axis2\ wstx-asl jar jar \external\axis2\1.6.2\wstx- asl jar xalan.jar \xalan.jar xercesimpl.jar \xercesimpl.jar xml-apis.jar \xml-apis.jar \external\axis2\ XmlSchema jar \external\axis2\1.6.2\xmlsche ma jar SAP BusinessObjects XIR 4.1 (SP2), (SP3), (SP4), (SP5), (SP6) The following table details the JAR file requirements for SAP BusinessObjects XIR 4.1 (SP)

217 SAP BusinessObjects XIR 4.1 (SP2), (SP3), (SP4), (SP5), (SP6) Location JAR File Name Path wdeploy\ant\lib ant-launcher.jar wdeploy\ant\lib\ant-launcher.jar aspectjrt.jar \aspectjrt.jar bcm.jar \bcm.jar biplugins.jar \biplugins.jar boconfig.jar \boconfig.jar cdz_cluster_mgmt_types_idl.ja \cdz_cluster_mgmt_types_idl.j r ar cdzidl.jar \cdzidl.jar ceaspect.jar \ceaspect.jar cecore.jar \cecore.jar celib.jar \celib.jar ceplugins_core.jar \ceplugins_core.jar ceplugins_cr.jar \ceplugins_cr.jar cereports.jar \cereports.jar cesession.jar \cesession.jar corbaidl.jar \corbaidl.jar cryptojfips.jar \cryptojfips.jar CrystalReportsSDK.jar \CrystalReportsSDK.jar CTPlugin_idl.jar \CTPlugin_idl.jar cvom.jar \cvom.jar dsl_engine.jar \dsl_engine.jar dsl_sdk_commands.jar \dsl_sdk_commands.jar dsl_sdk_requests.jar \dsl_sdk_requests.jar dsl_sdk_server.jar \dsl_sdk_server.jar dsl_sdk_services.jar \dsl_sdk_services.jar dsws-biplatform.jar \dsws-biplatform.jar

218 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name Path webservices\en\dsws_ consumer\data\dswsja vaapi warfiles\webapps\dswsbobj e\web-inf\lib \external\axis2\1.4 dsws-common-util.jar dsws-common.jar dsws-reportengine.jar dsws-session.jar ebus405.jar GenericContainer_idl.ja r GenericContainer_proxy. jar guice-1.0.jar ie_proxies.jar IEPlugin_idl.jar inproc_container.jar \external\axis 2\1.6.2 jaxen jar \external\axis 2\1.6.2\jaxen- jtools.jar logging.jar \dsws-common-util.jar \dsws-common.jar web services\en\dsws_ consumer\data\dswsjavaapi \dsws-reportengine.jar \dsws-session.jar dsws-webisharedprovider.jar geronimo-staxapi_1.0_spec jar warfiles\webapps\dswsbobje\web- INF\lib\dsws-webishared-provider.jar \ebus405.jar \GenericContainer_idl.jar \GenericContainer_proxy.jar \external\axis2\1.6.2\geroni mo-stax-api_1.0_spec jar \guice-1.0.jar \ie_proxies.jar \IEPlugin_idl.jar \inproc_container.jar \external\axis 2\1.6.2\jaxen1.1.1.jar \jtools.jar \logging.jar

219 SAP BusinessObjects XIR 4.1 (SP2), (SP3), (SP4), (SP5), (SP6) Location JAR File Name Path v jar v jar v jar \org.eclipse.equinox.registry org.eclipse.equinox.registry v jar v jar org.eclipse.osgi_3.4.3.r34x_ \org.eclipse.osgi_3.4.3.r34x_ v jar v jar protobuf.jar \protobuf.jar pub_common.jar \pub_common.jar ras21core.jar \ras21core.jar ras21proc.jar \ras21proc.jar ras21sdk.jar \ras21sdk.jar rebean.common.jar \rebean.common.jar rebean.wi.adapter.jar \rebean.wi.adapter.jar rebean.wi.jar \rebean.wi.jar rebean.wi.model.jar \rebean.wi.model.jar \rebean.wi.server.commands.ja rebean.wi.server.commands.jar r rebean.wi.server.jar \rebean.wi.server.jar \rebean.wi.server.requests.ja rebean.wi.server.requests.jar r rom.jar \rom.jar sdk.core.jar \sdk.core.jar sdk.core.server.common.jar \sdk.core.server.common.jar sdk.core.server.corba.jar \sdk.core.server.corba.jar sdk.core.server.jar \sdk.core.server.jar sdk.core.session.cms.jar \sdk.core.session.cms.jar sdk.core.session.jar \sdk.core.session.jar SL_plugins.jar \SL_plugins.jar TraceLog.jar \TraceLog.jar

220 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name Path webi_proxies.jar \webi_proxies.jar \external\axis2\1. \external\axis2\1.6.2\wsdl4j- 6.2 wsdl4j jar \external\axis2\ wstx-asl jar jar \external\axis2\1.6.2\wstx- asl jar xalan.jar \xalan.jar xercesimpl.jar \xercesimpl.jar xml-apis.jar \xml-apis.jar \external\axis2\ XmlSchema jar \external\axis2\1.6.2\xmlsche ma jar - 173

221 SAP BusinessObjects XIR 4.1 (SP10) The following table details the JAR file requirements for SAP BusinessObjects XIR 4.1 (SP10). Location JAR File Name Path wdeploy\ant\lib ant-launcher.jar wdeploy\ant\lib\ant-launcher.jar aspectjrt.jar \aspectjrt.jar bcm.jar \bcm.jar biplugins.jar \biplugins.jar boconfig.jar \boconfig.jar cdz_cluster_mgmt_types_idl.ja \cdz_cluster_mgmt_types_idl.j r ar cdzidl.jar \cdzidl.jar ceaspect.jar \ceaspect.jar cecore.jar \cecore.jar celib.jar \celib.jar ceplugins_core.jar \ceplugins_core.jar ceplugins_cr.jar \ceplugins_cr.jar cereports.jar \cereports.jar cesession.jar \cesession.jar corbaidl.jar \corbaidl.jar cryptojfips.jar \cryptojfips.jar CrystalReportsSDK.jar \CrystalReportsSDK.jar CTPlugin_idl.jar \CTPlugin_idl.jar cvom.jar \cvom.jar dsl_engine.jar \dsl_engine.jar dsl_sdk_commands.jar \dsl_sdk_commands.jar dsl_sdk_requests.jar \dsl_sdk_requests.jar dsl_sdk_server.jar \dsl_sdk_server.jar dsl_sdk_services.jar \dsl_sdk_services.jar

222 dsws-biplatform.jar \dsws-biplatform.jar dsws-common-util.jar \dsws-common-util-jar dsws-common.jar \dsws-common-util-jar web services\en\dsws_consumer\ data\dswsjavaapi dsws-reportengine.jar \dsl_sdk_services.jar dsws-session.jar \dsws-session.jar warfiles\webapps\dswsbobje warfiles\webapps\dswsbobje\web- \WEB-INF\lib dsws-webishared-provider.jar INF\lib\dsws-webishared-provider.jar ebus405.jar \ebus405.jar GenericContainer_idl.jar \GenericContainer_idl.jar GenericContainer_proxy.jar \GenericContainer_proxy.jar \external\axis2\1. geronimo-stax-api_1.0_spec- \external\axis2\1.6.2\ jar geronimo-stax-api_1.0_spec jar guice-1.0.jar \guice-1.0.jar ie_proxies.jar \ie_proxies.jar IEPlugin_idl.jar \IEPlugin_idl.jar inproc_container.jar \inproc_container.jar \external\axis2\ jaxen jar \external\axis2\1.6.2\jaxen jar jtools.jar \jtools.jar logging.jar \logging.jar org.eclipse.emf.common_ \org.eclipse.emf.common_2.4.0 v jar.v jar org.eclipse.emf.ecore_2.4.2.v \org.eclipse.emf.ecore_ jar v jar org.eclipse.emf.ecore.xmi_2.4 \org.eclipse.emf.ecore.xmi_2..1.v jar 4.1.v jar org.eclipse.equinox.common_3. \org.eclipse.equinox.common_3 4.0.v jar.4.0.v jar org.eclipse.equinox.registry_ \org.eclipse.equinox.registry v jar org.eclipse.osgi_3.4.3.r34x_v jar _3.4.0.v jar \org.eclipse.osgi_3.4.3.r34x_ v jar protobuf.jar \protobuf.jar pub_common.jar \pub_common.jar ras21core.jar \ras21core.jar

223 ras21proc.jar \ras21proc.jar ras21sdk.jar \ras21sdk.jar rebean.common.jar \rebean.common.jar rebean.wi.adapter.jar \rebean.wi.adapter.jar rebean.wi.jar \rebean.wi.jar rebean.wi.model.jar \rebean.wi.model.jar \rebean.wi.server.commands.ja rebean.wi.server.commands.jar r rebean.wi.server.jar \rebean.wi.server.jar \rebean.wi.server.requests.ja rebean.wi.server.requests.jar r rom.jar \rom.jar sdk.core.jar \sdk.core.jar sdk.core.server.common.jar \sdk.core.server.common.jar sdk.core.server.corba.jar \sdk.core.server.corba.jar sdk.core.server.jar \sdk.core.server.jar sdk.core.session.cms.jar \sdk.core.session.cms.jar sdk.core.session.jar \sdk.core.session.jar SL_plugins.jar \SL_plugins.jar TraceLog.jar \TraceLog.jar webi_proxies.jar \webi_proxies.jar \external\axis2\ wsdl4j jar \external\axis2\1.6.2\wsdl4j jar \external\axis2\ wstx-asl jar \external\axis2\1.6.2\wstxasl jar xalan.jar \xalan.jar xercesimpl.jar \xercesimpl.jar xml-apis.jar \xml-apis.jar \external\axis2\ XmlSchema jar \external\axis2\1.6.2\xmlsche ma jar

224 SAP BusinessObjects XIR 4.2 (SP2), (SP3) SAP BusinessObjects XIR 4.1 (SP11) The following table details the JAR file requirements for SAP BusinessObjects XIR 4.1 (SP11). Location JAR File Name Path wdeploy\ant\lib ant-launcher.jar wdeploy\ant\lib\ant-launcher.jar aspectjrt.jar \aspectjrt.jar bcm.jar \bcm.jar biplugins.jar \biplugins.jar boconfig.jar \boconfig.jar cdz_cluster_mgmt_types_idl.ja \cdz_cluster_mgmt_types_idl.j r ar cdzidl.jar \cdzidl.jar ceaspect.jar \ceaspect.jar cecore.jar \cecore.jar celib.jar \celib.jar ceplugins_core.jar \ceplugins_core.jar ceplugins_cr.jar \ceplugins_cr.jar cereports.jar \cereports.jar cesession.jar \cesession.jar corbaidl.jar \corbaidl.jar cryptojfips.jar \cryptojfips.jar CrystalReportsSDK.jar \CrystalReportsSDK.jar CTPlugin_idl.jar \CTPlugin_idl.jar cvom.jar \cvom.jar dsl_engine.jar \dsl_engine.jar dsl_sdk_commands.jar \dsl_sdk_commands.jar

225 dsl_sdk_requests.jar \dsl_sdk_requests.jar dsl_sdk_server.jar \dsl_sdk_server.jar dsl_sdk_services.jar \dsl_sdk_services.jar dsws-biplatform.jar \dsws-biplatform.jar dsws-common-util.jar \dsws-common-util-jar dsws-common.jar \dsws-common-util-jar web services\en\dsws_consumer\ data\dswsjavaapi dsws-reportengine.jar \dsl_sdk_services.jar dsws-session.jar \dsws-session.jar warfiles\webapps\dswsbobje warfiles\webapps\dswsbobje\web- \WEB-INF\lib dsws-webishared-provider.jar INF\lib\dsws-webishared-provider.jar ebus405.jar \ebus405.jar GenericContainer_idl.jar \GenericContainer_idl.jar GenericContainer_proxy.jar \GenericContainer_proxy.jar \external\axis2\1. geronimo-stax-api_1.0_spec- \external\axis2\1.6.2\ jar geronimo-stax-api_1.0_spec jar guice-1.0.jar \guice-1.0.jar ie_proxies.jar \ie_proxies.jar IEPlugin_idl.jar \IEPlugin_idl.jar inproc_container.jar \inproc_container.jar \external\axis2\ jaxen jar \external\axis2\1.6.2\jaxen jar jcmfips.jar \jcmfips.jar jtools.jar \jtools.jar logging.jar \logging.jar org.eclipse.emf.common_ \org.eclipse.emf.common_2.4.0 v jar.v jar org.eclipse.emf.ecore_2.4.2.v \org.eclipse.emf.ecore_ jar v jar org.eclipse.emf.ecore.xmi_2.4 \org.eclipse.emf.ecore.xmi_2..1.v jar 4.1.v jar org.eclipse.equinox.common_3. \org.eclipse.equinox.common_3 4.0.v jar org.eclipse.equinox.registry_ v jar.4.0.v jar \org.eclipse.equinox.registry _3.4.0.v jar org.eclipse.osgi_3.4.3.r34x_v \org.eclipse.osgi_3.4.3.r34x_

226 jar v jar protobuf.jar \protobuf.jar pub_common.jar \pub_common.jar ras21core.jar \ras21core.jar ras21proc.jar \ras21proc.jar ras21sdk.jar \ras21sdk.jar rebean.common.jar \rebean.common.jar rebean.wi.adapter.jar \rebean.wi.adapter.jar rebean.wi.jar \rebean.wi.jar rebean.wi.model.jar \rebean.wi.model.jar \rebean.wi.server.commands.ja rebean.wi.server.commands.jar r rebean.wi.server.jar \rebean.wi.server.jar \rebean.wi.server.requests.ja rebean.wi.server.requests.jar r rom.jar \rom.jar sdk.core.jar \sdk.core.jar sdk.core.server.common.jar \sdk.core.server.common.jar sdk.core.server.corba.jar \sdk.core.server.corba.jar sdk.core.server.jar \sdk.core.server.jar sdk.core.session.cms.jar \sdk.core.session.cms.jar sdk.core.session.jar \sdk.core.session.jar SL_plugins.jar \SL_plugins.jar TraceLog.jar \TraceLog.jar webi_proxies.jar \webi_proxies.jar \external\axis2\ wsdl4j jar \external\axis2\1.6.2\wsdl4j- \external\axis2\ wstx-asl jar jar \external\axis2\1.6.2\wstxasl jar xalan.jar \xalan.jar xercesimpl.jar \xercesimpl.jar xml-apis.jar \xml-apis.jar \external\axis2\ XmlSchema jar \external\axis2\1.6.2\xmlsche ma jar

227 SAP BusinessObjects XIR 4.2 (SP2),(SP3) The following table details the JAR file requirements for SAP BusinessObjects XIR 4.2 (SP2)

228 Appendix G: SAP BusinessObjects JAR File Requirements Location JAR File Name aspectjrt.jar bcm.jar cdzextidl.jar cdzidl.jar cdz_cluster_mgmt_types_idl.jar ceaspect.jar cecore.jar celib.jar ceplugins_core.jar certjfips.jar cesdk.jar cesession.jar corbaidl.jar cryptojfips.jar CTPlugin_idl.jar customdsidl.jar cvom.jar dsl_engine.jar dsl_engine_lang.en.jar ds_excel_idl.jar ebus405.jar extendedblock_server_idl.jar GenericContainer_idl.jar GenericContainer_proxy.jar gson jar guice-1.0.jar IEPlugin_idl.jar ie_proxies.jar inproc_container.jar json.jar logging.jar org.eclipse.emf.common_2.4.0.v jar org.eclipse.emf.ecore_2.4.2.v jar protobuf.jar rebean.common.jar

229 SAP BusinessObjects XIR 4.1 (SP2), (SP3), (SP4), (SP5), (SP6) Location Name JAR File rebean.wi.adapter.jar rebean.wi.jar rebean.wi.model.jar rebean.wi.server.commands.jar rebean.wi.server.jar rebean.wi.server.requests.jar rom.jar sdk.core.jar sdk.core.server.common.jar sdk.core.server.corba.jar sdk.core.server.jar sdk.core.session.cms.jar sdk.core.session.jar ssljfips.jar TraceLog.jar webi_proxies

230 SAP BusinessObjects XIR 4.1 (SP2), (SP3), (SP4), (SP5), (SP6) SAP BusinessObjects XIR 4.2 (SP4) The following table details the JAR file requirements for SAP BusinessObjects XIR 4.2 (SP4). Location JAR File aspectjrt.jar bcm.jar cdzextidl.jar cdzidl.jar cdz_cluster_mgmt_types_idl.jar ceaspect.jar cecore.jar celib.jar ceplugins_core.jar certjfips.jar cesdk.jar cereports.jar cesession.jar corbaidl.jar cryptojfips.jar CrystalReportsSDK.jar CTPlugin_idl.jar customdsidl.jar

231 cvom.jar dsl_engine.jar dsl_engine_lang.en.jar ds_excel_idl.jar ebus405.jar extendedblock_server_idl.jar GenericContainer_idl.jar GenericContainer_proxy.jar gson jar guice-1.0.jar IEPlugin_idl.jar ie_proxies.jar inproc_container.jar jcmfips.jar json.jar logging.jar org.eclipse.emf.common_2.4.0.v jar org.eclipse.emf.ecore_2.4.2.v jar protobuf.jar rebean.common.jar rebean.wi.adapter.jar rebean.wi.jar rebean.wi.model.jar rebean.wi.server.commands.jar rebean.wi.server.jar rebean.wi.server.requests.jar rom.jar sdk.core.jar sdk.core.server.common.jar sdk.core.server.corba.jar sdk.core.server.jar sdk.core.session.cms.jar sdk.core.session.jar SL_plugins.jar ssljfips.jar TraceLog.jar

232 SAP BusinessObjects XIR 4.2 (SP5) aspectjrt.jar bcm.jar cdzextidl.jar cdzidl.jar cdz_cluster_mgmt_types_idl.jar ceaspect.jar cecore.jar celib.jar ceplugins_core.jar certjfips.jar cesdk.jar cereports.jar cesession.jar corbaidl.jar cryptojfips.jar CrystalReportsSDK.jar CTPlugin_idl.jar customdsidl.jar cvom.jar dsl_engine.jar dsl_engine_lang.en.jar webi_proxies.jar Location JAR File

233 ds_excel_idl.jar ebus405.jar extendedblock_server_idl.jar GenericContainer_idl.jar GenericContainer_proxy.jar gson jar guice-1.0.jar IEPlugin_idl.jar ie_proxies.jar inproc_container.jar jcmfips.jar json.jar logging.jar org.eclipse.emf.common_2.4.0.v jar org.eclipse.emf.ecore_2.4.2.v jar protobuf.jar rebean.common.jar rebean.wi.adapter.jar rebean.wi.jar rebean.wi.model.jar rebean.wi.server.commands.jar rebean.wi.server.jar rebean.wi.server.requests.jar rom.jar sdk.core.jar sdk.core.server.common.jar sdk.core.server.corba.jar sdk.core.server.jar sdk.core.session.cms.jar sdk.core.session.jar SL_plugins.jar ssljfips.jar TraceLog.jar webi_proxies.jar

234

235