==================================== Upgrading to Rollbase 2.1 From 2.0.x ==================================== Welcome to Rollbase 2.1! This document will help you with installation procedures so that you can successfully upgrade your Rollbase instance without trouble. This guide will explain the Rollbase 2.1 installation procedures in three different scenarios depending on the database configuration. The scenarios include: - Part A. An existing 2.0.x installation with an embedded Progress OpenEdge Database - Part B. An existing 2.0.x installation with a non-embedded Progress OpenEdge 11.3.1 Database - Part C. An existing 2.0.x installation using another database. You only need to follow installation instructions for the scenario that matches your particular setup. ---------------------------------------------------------------- Part A. An Existing 2.0.x installation with an embedded Progress OpenEdge Database ---------------------------------------------------------------- Rollbase 2.1 cannot be installed until the previous version you are running has been uninstalled and cleanup has been performed. To install Rollbase 2.1, please follow the directions below: 1. Note the location of in the existing 2.0.x installation. You can confirm its location by looking for the following sub-folders: apps, config, db, dbmgmt, docs, install, res, search, sql, storage etc. 2. Create a backup of the 2.0.x config folder and copy it to a location outside of the 2.0.x installation 3. Shut down Tomcat. 4. From run stopdb.bat/sh to stop the database. 5. Uninstall Rollbase 2.0.0.x. The uninstaller will remove Rollbase files and the database installation but it will leave and its files, /search, and /storage intact. 6. If you used the Tomcat that came with the installer, delete the \apache-tomcat-7.0.42 folder. If you installed Rollbase 2.0.0.x and used an existing Tomcat instance, delete the following folders from the webapps/ folder: master, router, prod1, search, storage, rest, webapi, rss, workflow 7. Install Rollbase 2.1. Make sure you specify the existing and locations for the new installation. Choose Progress Database and fill in the details to match your existing database. Refer to your config/databases.xml file that you backed up earlier for the necessary values. This is important for generating the correct databases.xml file for your 2.1 installation.The installer will not overwrite the existing database. 8. For Email Configuration, refer to the values from your old installation within the config/shared.properties file. - The relevant key information in this step is the email address of the first admin user - For the email server, you can use gmail by default: Host Name = smtp.gmail.com Port Number = 465 Check the box for using SSL Username and Password are also required 9. Finish the installation. 10. The installation will start up the embedded database at the end of the installation process. 11. The database schema will need to be updated. Depending on the version of 2.0.0.x you had installed previously, you may need to run one or more of the following update scripts to ensure the schema matches that of 2.1.0 respectively (either a or b). a. If you are updating from a version earlier than 2.0.0.3,you will first run the script update_2_0_0_3.sql and then run the script update_2_1_0.sql. b. If updating from 2.0.0.3 or later you will run the script update_2_1_0.sql. The update scripts contain SQL statements for all supported databases. You need to update them as follows: a. Uncomment the statements for OpenEdge where required. These lines begin with "-- OpenEdge". To uncommnent them, remove the "--". d. Comment out the equivalent statements for other databases, in other words, add "--" to each line you want to comment out. e. Make sure the last line is uncommented and looks like this: COMMIT WORK; 12. Execute the scripts you updated using the OpenEdge proenv utility as follows: a. From a command prompt, start the OpenEdge proenv utility, replacing with the location of your installation directory: >cd \db\bin >proenv b. In the proenv utility set the JREHOME environment variable: proenv> set JREHOME=%DLC%\jre c. In the proenv utility, run SQLExplorer to execute the required update scripts in the correct order [from step #11]. For example to run the update_2_1_0.sq script (on one line): proenv>sqlexp -user -password -url jdbc:datadirect:openedge://localhost:;databaseName=   -infile \sql\update_2_1_0.sql Make sure that the port and database name parameters, and use the same values as specified in your 2.0.0.x installation (these files can be found in the backed up version of config/database.xml). Make sure the database is running before using the update scripts. 12. After the scripts run, the database is updated and ready to be used with Rollbase 2.1. 13. Start Tomcat to connect to the database. ---------------------------------------------------------- Part B. An Existing 2.0.x installation with a non-embedded OpenEdge 11.3.1 Database ---------------------------------------------------------- Follow these steps to upgrade to 2.1.0: 1. Make a backup of the config folder. You can find the config folder here; \config folder after 2.1.0 installation. You will be replacing the /CONFIG directory with the 2.0.0.x directory name 5. Start the database.The database schema has to be updated to match 2.1.0 Depending on the version of 2.0.0.x you had installed previously, you may need to run one or more of the following update scripts to ensure the schema matches that of 2.1.0 respectively (either a or b) a. If you are updating from a version earlier than 2.0.0.3,you will first run the script update_2_0_0_3.sql and then run the script update_2_1_0.sql.” >2.0.0.3: update_2_1_0.sql b. If updating from 2.0.0.3 or later you will run the script update_2_1_0.sql” 6. Review the update scripts. The scripts have SQL statements for all supported databases. Uncomment the statements for OpenEdge where required, following this hint -- OpenEdge Comment out the equivalent statements for other databases. 7. Make sure the last line is uncommented and looks like this: COMMIT WORK; 8. Using SQLExplorer, you will need to run one of the scripts listed above in section 7 (a or b) proenv>sqlexp -user -password -url jdbc:datadirect: openedge://localhost:;databaseName=    -infile \sql\update_2_1_0.sql 9. The database is updated and ready to be used with Rollbase 2.1 10. Start Tomcat to connect to the database. ------------------------------------------------------------- Part C. An existing 2.0.x installation using another database ------------------------------------------------------------- 1. Make a backup of the config folder. You can find the config folder here; \config folder after 2.1.0 installation 3. Start the database 4. The database schema has to be updated to match 2.1.0. Depending on the version of 2.0.0.x you had installed previously, you may need to run one or more of the following update scripts to ensure the schema matches that of 2.1.0 respectively (either a or b). a. If you are updating from a version earlier than 2.0.0.3,you will first run the script update_2_0_0_3.sql and then run the script update_2_1_0.sql.” >2.0.0.3: update_2_1_0.sql b. If updating from 2.0.0.3 or later you will run the script update_2_1_0.sql”Review the update scripts. The scripts have SQL statements for all supported databases. 5. Uncomment the statements for OpenEdge where required, following this hint -- OpenEdge Comment out the equivalent statements for other databases. --------------------------------------------------------------------- Part D. Configuring the integrated OpenEdge Database to Support UTF-8 Character Sets --------------------------------------------------------------------- If you choose the ‘Progress Database’ option while Rollbase 2.1 is installing, the installer will create an OpenEdge 11.3.1 database for you. This instance of the database uses a iso-8859-1 database template. If you wish to create applications which use languages not supported by iso-8859-1, you can use an installer script to re-create the database so that it supports UTF-8. 1. Locate your and folders. The default values in Windows are C:\Progress\Rollbase and C:\Progress\WRK respectively. 2. Shut down Tomcat and run  the stopdb.sh or stopdb.bat in the oe_rollbase_db folder inside 3. Backup the  oe_rollbase_db folder if required and delete it. Edit the   cdb.bat or cdb.sh file in  /db/install folder to make the following changes. 4. If using Windows, change the following line in cdb.bat call "%DLC%"\bin\procopy %DLC%\empty4 %DB_NAME% to this: call "%DLC%"\bin\procopy %DLC%\prolang\utf\empty4 %DB_NAME% In Linux, change the following line in cdb.sh EMPTY_DB_NAME=empty8 to EMPTY_DB_NAME prolang/utf/empty8 5. Run cdb.bat or cdb.sh to recreate the UFT8 database at /oe_rollbase_db If you are running Rollbase 2.1 against an external instance of  OpenEdge 11.3.1, you probably used   /sql/create_oedb.sh or \sql\create_oedb.bat to create the database.The scripts create a database that uses a iso-8859-1 database template. If you wish to create applications which use languages not supported by iso-8859-1, you can change the template in the script to create a UTF8 database. Edit the   create_oedb.bat or create_oedb.sh file in  /sql folder to make the following changes. If using Windows, change the following line in cdb.bat call "%DLC%"\bin\procopy %DLC%\empty4 %DB_NAME% to call "%DLC%"\bin\procopy %DLC%\prolang\utf\empty4 %DB_NAME% In Linux, change the following line in cdb.sh EMPTY_DB_NAME=empty8 to EMPTY_DB_NAME prolang/utf/empty8 2. Run create_oedb.bat or create_oedb.sh  with appropriate parameters to create a UFT8 database Rollbase 2.1 Installation Guidelines