Table of Contents Introduction to the SAP Roambi migration process SystemRequirements Preparing to upgrade SAP Roambi ES

Transcription

1

2 Table of Contents Introduction to the SAP Roambi migration process 6 SystemRequirements 6 Mobile Devices Server Requirements Hardware Operating Systems Java Application Servers Databases Other Collaterals Browsers Backend Requirements Portals Relational Database Access Reporting Layers Access OLAP Servers Authentication Servers Preparing to upgrade SAP Roambi ES 7 Migrating to SAP Roambi ES5.0 from ES4.+ 7 Migrating from MySQL to SQL Server 9 Troubleshooting 10 -

3 Introduction to the SAP Roambi migration process This guide provides instructions to upgrading the Roambi server to SAP Roambi ES5.0 from a previous release. Depending on which version of Roambi ES you are starting with, your upgrade instructions will vary: 1. Back up the Roambi ES database and Roambi installation files (see Preparing to upgrade Roambi ES). 2. Depending on which version of Roambi ES you have previously installed, follow the appropriate instructions to upgrade to the current version of Roambi ES: Migrating to Roambi ES5.0 from ES Troubleshoot the upgrade, if necessary. Note: If you are migrating from ES4.x to a newer version, make sure to replace your existing license key with the license key for the new release as instructed in Migrating to Roambi ES5.0 from ES4.+. SystemRequirements For the latest information on system requirements and technical prerequisites, refer the PAM here

4 Preparing to upgrade Roambi ES Preparing to upgrade SAP Roambi ES Before upgrading Roambi ES to a newer release, back up the Roambi database and configuration files in case you need them later. To prepare to upgrade to a new release of Roambi ES: 1. Stop the Tomcat application server, using either the Tomcat control panel or catalina.sh stop command. 2. If you are currently running Roambi ES 4.x, back up the MySQL database for Roambi: $ mysqldump --routines --add-drop-database --user=root -p -- databases roambi > C:\roambi.sql 3. If you need to restore the Roambi database at any point after creating the backup, type the following command: $ mysql -u root -p roambi < C:\roambi.sql 4. Create a backup copy of the Roambi installation folder: [TomcatDirectory]/webapps/[RoambiDirectory] 5. Move the backup copy somewhere outside of the Tomcat path. 6. Delete the Roambi installation folder that you just backed up: [TomcatDirectory]/webapps/[RoambiDirectory] 7. Delete the Roambi.war file from the previous release that is in the /webapps folder. 8. Follow the instructions in the appropriate next section to upgrade to the new Roambi release. Migrating to SAP Roambi ES5.0 from ES4.+ If your organization is migrating to Roambi ES5.0 from ES4.+, only the Roambi administrator will need to perform migration tasks; this migration does not affect end users. End users will automatically have access to the new Roambi features after the migration is complete. Note: If you are migrating from ES4.x to a newer version, make sure to replace your existing license key with the license key for the new release. If you do not replace your license key, you will not be able to successfully migrate to the latest version of Roambi ES. To migrate to Roambi ES5.0 from ES4.+: 1. Install the Roambi server as described in the Installation Guide: a. Use the Roambi Installer to unpack the updated Roambi.war file. b. Rename and copy the Roambi.war file to the appropriate directory for your application server. c. Transfer any changes from your backed up [BackupTomcatDirectory] /webapps/[roambidirectory]/web-inf/web.xml file to the new - 7 -

5 [TomcatDirectory]/webapps/[RoambiDirectory]/WEB- INF/web.xmlfile. d. Transfer any changes from your backed up [BackupTomcatDirectory] /webapps/[roambidirectory]/web- INF/classes/com/mellmo/roambi/data/plugins/ooexcel/ openoffice.properties file to the new [TomcatDirectory]/webapps/ [RoambiDirectory]/WEB- INF/classes/com/mellmo/roambi/data/plugins/ooexcel/ openoffice.propertiesfile. e. Copy all OpenOffice, MySQL connector, and BI tool JAR files that you added to the previous release to the appropriate folders for the new release. f. Stop Tomcat and wait for Tomcat to go idle (using top in Linux or the Task Manager in Windows). g. Restart Tomcat. 2. As described in the Installation Guide instructions, make sure to copy your new license key (the license.es file) to the newly created.roambi folder; your old license key will no longer work for ES When you connect to Roambi via a web browser for the first time, you will be prompted to migrate your Roambi database: 4. Per the instructions, make sure that your MySQL Roambi database is backed up, then click the Migrate DB button to complete the migration. 5. If your organization will be using Roambi Flow, follow the instructions in the Installation Guide to download and install the wkhtmltoimage utility. 6. Migrate your configuration changes: a. Restart Tomcat. b. Transfer any changes from your backed up [BackupTomcatDirectory] /webapps/[roambidirectory]/web-inf/web.xml file to the new [TomcatDirectory]/webapps/[RoambiDirectory]/WEB- INF/web.xmlfile

6 Migrating from MySQL to SQL Server c. Transfer any changes from your backed up [BackupTomcatDirectory] /webapps/[roambidirectory]/web- INF/classes/com/mellmo/roambi/data/plugins/ooexcel/ openoffice.properties file to the new [TomcatDirectory]/webapps/ [RoambiDirectory]/WEB- INF/classes/com/mellmo/roambi/data/plugins/ooexcel/openoffice.propertiesfile. d. Copy all OpenOffice, MySQL connector, and BI tool JAR files that you added to the previous release to the appropriate folders for the new release. e. Stop Tomcat and wait for Tomcat to go idle (using top in Linux or the Task Manager in Windows). f. Restart Tomcat. Migrating from MySQL to SQL Server With the release of Roambi ES5, Roambi now supports using a Microsoft SQL Server database to store and manage administrative data, in addition to the previously supported MySQL database. If you would like to use a SQL Server database for your Roambi data, you will need to migrate your existing MySQL database content to SQL server. To migrate your MySQL database to a SQL Server database: 1. Create a backup copy of your database as described in Preparing to upgrade Roambi ES. 2. Migrate your existing Roambi server to the current Roambi ES5 release. (See Migrating to Roambi ES5.0 from ES4.+.) This process will migrate the existing Roambi MySQL database to the latest MySQL database schema. Migration to an MS SQL Server requires a MySQL 4.+ database schema. 3. Follow the instructions in the Roambi ES5 Installation Guide to configure your Roambi server and your application server to use MS SQL Server. 4. Download the Microsoft SQL Server Migration Assistant (SSMA) for MySQL Version 5.2. You will use this to migrate your MySQL database content to SQL Server as follows: a. Download the SSMA from the Microsoft web site: b. Follow the instructions on the Microsoft web page to install the tool. c. Make sure that Store procedures is not enabled for migration. d. Follow Microsoft's instructions to migrate your data. 5. Navigate to your.roambi folder (in the folder where you installed Roambi ES), and open the config.json file for editing. 6. Create a backup copy of the original content, then replace the original content with the following text: {"roambi-data":"0.2.0","db":"java:comp/env/jdbc/roambidatasource", "setup_complete":true} - 9 -

7 Troubleshooting If you have correctly performed the upgrade steps, but SAP Roambi is not displaying the upgraded version in your browser, clear the cache for both Tomcat and your browser: To clear the cache in Tomcat: 1. Shut down Tomcat. 2. Delete the /Roambi folder located under [TomcatInstallation] /work/catalina/localhost. 3. Delete all files located in the [TomcatInstallation]/temp. 4. Restart Tomcat. Follow the instructions in your browser's online help to delete your browser cache.

8 - 10 -