QlikView 11 Upgrade & Migrations

Transcription

1 QlikView 11 Upgrade & Migrations QlikView Technical Brief Published: November 2011 qlikview.com

2 Introduction This guide is provided as a reference and best practices for upgrading and migrating an existing QlikView deployment from versions 9 and 10 to version 11. This is not intended as an exhaustive document covering every possible deployment scenario, rather it is provided to QlikView system administrators to provide them an understanding of the best practices associated with a successful upgrade of their QlikView deployments. QlikView 11 Upgrade and Migrations Page 2

3 Contents Introduction 2 Section 1: General Upgrade and Migration Considerations 4 Section 2: Existing QlikView Server 9 6 Considerations 6 QlikView 9 Upgrade Scenarios 12 Upgrade QlikView Server 9 to QlikView Server 10 or Upgrade QlikView Server 9 to QlikView Server & Publisher 10 or Upgrade QlikView Server & Publisher 9 to QlikView Server & Publisher 10 or Section 3: Existing QlikView Server Considerations 17 QlikView 10 Upgrade Scenarios 17 Upgrade QlikView Server 10 to QlikView Server Upgrade QlikView Server 10 to QlikView Server & Publisher Upgrade QlikView Server & Publisher 10 to QlikView Server & Publisher Section 4: Example Multi-Machine Scenarios 21 Section 5: Re-locating QlikView Services 30 QlikView Server 10/11 30 Directory Service Connector 10/11 32 QlikView WebServer 10/11 33 QlikView 11 Upgrade and Migrations Page 3

4 Section 1: General Upgrade and Migration Considerations This section outlines architectural changes that occurred over multiple versions of QlikView Server and should be considered before embarking on any upgrade and migration of QlikView..NET Framework requirements When upgrading from QlikView Server 9 to 10 or 11, you need to make sure that the correct.net Framework is installed to support the components. QlikView Server version.net Framework version required EDX triggers Different versions of QlikView Server handle EDX triggers in different ways. The following table illustrates in which QlikView Server version each methodology is supported. QlikView Server version HTTP POST EDX call QMS API EDX call 9 Supported N/A 10 Supported (legacy) Supported 11 N/A Supported Please refer to the QMS API documentation for the QlikView Management Console and the QlikView SDK for further usage instructions on EDX triggers. QlikView 11 Upgrade and Migrations Page 4

5 Services Different versions of QlikView Server contain different services. The following table illustrates the existence of the various services, by version. QlikView Server 9 QlikView Server 10 QlikView Server 11 QlikView Server Yes Yes Yes QlikView WebServer Yes Yes Yes QlikView Publisher Command Center Service Yes No No QlikView Management Service Yes Yes Yes QlikView Directory Service Connector Yes Yes Yes QlikView Distribution Service Yes Yes Yes QlikView Settings Service No No Yes * * Only if using IIS instead of QlikView WebServer Old Distribution Service files It is considered best practice to remove the old work order and related files from the DistributionService application data folder before starting the new services, or if experiencing issues with Publisher/Distribution Service, after an upgrade or migration. The folder is located under: Windows Server 2003/XP: C:\Documents and Settings\All Users\Application Data\ QlikTech\DistributionService Windows Server 2008/Vista/7: C:\ProgramData\QlikTech\DistributionService Remember that the log files are stored in this location. It is best practice to back them up first. QlikView 11 Upgrade and Migrations Page 5

6 Section 2: Existing QlikView Server 9 This section is written for QlikView administrators who are considering migrating from QlikView version 9 to QlikView version 11. (Because of the similarities involved, it also can be used as a guide to upgrade from version 9 to version 10). For the purposes of this section, both version 10 and version 11 will be referred to collectively as 10/11. Considerations A number of significant architectural changes were introduced with QlikView Server 10, and subsequently QlikView Server 11, that will affect upgrade scenarios from QlikView Server 9. The following pages describe the major considerations that need to be taken when upgrading from version 9 to version 10 and 11. Please refer to the Release Notes for QlikView 10 and 11 respectively for all differences. The procedures to upgrade from QlikView Server 9 to version 10 or to version 11 are the same, and therefore this section will cover the scenarios involved in upgrading from version 9 to version 10 or indeed directly from version 9 to version 11. Clients Ajax Zfc (Zero footprint client) Major changes have been implemented on the QlikView server client side, especially in the Ajax Zfc client, between QlikView Server 9 and 10/11. When upgrading from QlikView Server 9 to 10/11, always ensure that Ajax Zfc clients clear their web browser cache and cookies to avoid unexpected behavior caused by legacy cache on client machines. IE Plug-in clients & Desktop clients Always attempt to align client versions of the IE Plug-in with the QlikView Server version. This client should be backwards compatible in most aspects, but using older clients might hinder users use of new functionality implemented in the newer versions. This is most applicable in cases where clients use the newer QlikView Developer/Desktop and new functions in the applications that QlikView Server is then presenting to the server clients. The IE Plug-in or Developer/Desktop should not be considered forward compatible against a QlikView Server. Server URLs If using hardcoded URLs to documents or other resources on a QlikView Server 9, it s important to verify that they work in newer versions. Architectural changes may have changed the format of these URLs or paths and you may need to change them to have them work properly in the newer release. QlikView 11 Upgrade and Migrations Page 6

7 Settings, Program files and Application data When QlikView Server 9 is uninstalled, or if QlikView Server 10 or 11 is installed in place of a QlikView Server 9, the installation package will only remove the program binaries and the Windows services (Program files). Settings, configuration files, data files (such as.qvw files) and repositories are not uninstalled (Application data). This makes for the possibility to do straightforward in-place upgrades from QlikView Server 9 to 10 or 11. Program files for QlikView Server (9, 10 or 11) are by default located under C:\Program Files\QlikView (for x64 QlikView on x64 OS and x86 QlikView on x86 OS) or C:\Program Files (x86)\qlikview (for x86 on x64 OS). Application data for QlikView Server (9, 10 or 11) are by default located under the following folders: Windows Server 2003/XP: C:\Documents and Settings\All Users\ Application Data\QlikTech Windows Server 2008/Vista/7: C:\ProgramData\QlikTech Relocated application data folders The folder structure for the application data for QlikView Server has changed in 10/11. Folders for the QlikView services application data are now changed according to the below table. Note: [AppDataFolder] translates to the corresponding folder from the bullets above. QlikView Server 9 QlikView Server 10/11 [AppDataFolder]\Qvs [AppDataFolder]\QvWebServer [AppDataFolder]\ QlikviewManagementService [AppDataFolder]\Publisher\Qlikview Distribution Service [AppDataFolder]\Publisher\CommandCenter [AppDataFolder]\DirectoryServiceConnector [AppDataFolder]\QlikViewServer [AppDataFolder]\WebServer [AppDataFolder]\ManagementService [AppDataFolder]\DistributionService N/A Unchanged This means that after an upgrade, it is recommended to remove old QlikView Server 9 legacy folders from an upgraded machine, if you have backups of the data in them. The exception is the Directory Service Connector folder that remains as the same name in 10/11. QlikView 11 Upgrade and Migrations Page 7

8 QlikView Server settings In QlikView Server 9, the QlikView Server core service has its settings stored in the Windows registry, under the key: HKEY_LOCAL_MACHINE\Software\QlikTech\QlikViewServer\Settings 7. In QlikView Server 10/11 the settings are stored in a Settings.ini file in any of the following folders: Windows Server 2003/XP: C:\Documents and Settings\All Users\Application Data\QlikTech\QlikViewServer Windows Server 2008/Vista/7: C:\ProgramData\QlikTech\QlikViewServer When starting the QlikView Server 10/11 service, it will look for the version 9 settings key in the registry and if it is found, migrate the settings to its Settings.ini file. This means that in migration scenarios where QlikView Server is moved to a new server(s), if settings in the QlikView Server service should persist, the Settings 7 registry key needs to be located in the old server and populated on the new server to be applied to a QlikView Server 10/11. QvWebServer settings Settings for the QlikView WebServer 9 service are stored in the config.xml file in under C:\ProgramData\QlikTech\QvWebServer. If a QlikView WebServer 10 /11 service finds this file in this folder when it starts, it will migrate the settings to the new configuration file for the service. This means that in migration scenarios where services are moved, if settings in the QvWebServer should persist, the config.xml file needs to be found and copied to the version 9 legacy folder on the new server to be applied to a QlikView WebServer 10/11. IIS virtual folder settings If Microsoft Internet Information Services (IIS) is used as web server for the QlikView Accesspoint, these settings needs to be considered as well. The QlikView Server 10/11 installation package will not remove QlikView Server 9 virtual directories or application pools from IIS. If upgrading, please make sure to remove all the version 9 legacy directories and application pools before the upgrade and migrate any eventual 3 rd part legacy files in IIS. QlikView 11 Upgrade and Migrations Page 8

9 The table below gives an overview of the virtual folders in IIS for the different versions of QlikView Server. QlikView Server 9 QlikView Server 10 QlikView Server 11 QlikView C:\Program Files\ QlikView\Web C:\Program Files\ QlikView\Web C:\Program Files\ QlikView\Web QvAjaxZfc * C:\Program Files\QlikView\ Server\QvClients\ QvAjaxZfc C:\Program Files\ QlikView\Server\ QlikViewClients\ QlikViewAjax C:\Program Files\ QlikView\Server\ QlikViewClients\ QlikViewAjax QlikView Desktop N/A C:\Program Files\ QlikView\Server\ QlikViewClients\ QlikViewDesktop N/A QvAnalyzer C:\Program Files\QlikView\ Server\QvClients\ QvAnalyzer N/A N/A QvClients C:\Program Files\ QlikView\Server\ QvClients C:\Program Files\ QlikView\Server\ QlikViewClients N/A QvJava C:\Program Files\ QlikView\Server\ QvClients\QvJava N/A N/A QvPlugin C:\Program Files\ QlikView\Server\ QvClients\QvPlugin C:\Program Files\ QlikView\Server\ QlikViewClients\ QlikViewPlugin C:\Program Files\ QlikView\Server\ QlikViewClients\ QlikViewPlugin QvPrint C:\ProgramData\ QlikTech\Qvs\ QvPrint N/A N/A * In QlikView Server 9, this folder is named QvAJAXZfc. Note the upper case difference. QlikView 11 Upgrade and Migrations Page 9

10 Additional settings Some configuration settings that are outside of UI might be set in configuration files that are stored under the Program Files folders. If any such settings are configured, make sure to back up the configuration files and re-apply the specific settings later. Do not replace these configuration files on a newer system with files from an old one. Instead, consider manually re-applying the settings to the new configuration files. This will help avoid situations where a specific setting has been moved or changed in the new version. Service removed: QlikView Publisher Command Center Service Since QlikView Server 10, and subsequently 11, one service has been merged into another: QlikView Publisher Command Center Service is now part of the QlikView Management Service. One consequence of this change is you may now only run one Management Service per licensed environment in 10/11, whereas in 9, you could run multiple Management Services provided they pointed to the same Command Center service. This has several implications in upgrade and migrations scenarios: 1. The ownership of the QVPR database (QlikView Publisher Repository) changes to the QlikView Management Service. This means that the QVPR database is moved from the application data folder for Publisher Command Center to the application data folder for QlikView Management Service in 10/ The Program files and Application data folders for QlikView Publisher Command Center will no longer exist. 3. The service QlikView Publisher Command Center will no longer exist. QVPR databases Migration of the QVPR database is only relevant if a QlikView Publisher license is activated in the environment. If using QlikView Publisher, one must be sure to migrate the QVPR database between QlikView Publisher Command Center 9 and QlikView Management Service 10/11. This is done automatically if doing an in-place upgrade to 10/11, but must be performed manually in migration scenarios. QlikView Management Service 10/11 will try and locate any version 9 QVPR, as well as some other files needed, in the old version 9 folder structure and migrate them to version 10/11 format. This will be done the first time the QlikView Management Service 10/11 is started. If it does not find a version 9 QVPR, it will create a new QVPR database in version 10/11 format. Details on these procedures are in the QlikView Publisher upgrade scenarios later in this documentation. QlikView 11 Upgrade and Migrations Page 10

11 For environments that do not have a Publisher license, it is necessary to migrate the reload tasks via the QVS Resource settings in the Management Console in order to get them into the QVPR, as they were stored in an xml file in 9, but 10/11 store them in the QVPR. Source Documents folder location In QlikView Publisher 9, the Source Documents folder was located under the following folder: Windows Server 2003/XP: C:\Documents and Settings\All Users\Application Data\QlikTech\Publisher\Sourcedocuments Windows Server 2008/Vista/7: C:\ProgramData\QlikTech\Publisher\ Sourcedocuments In QlikView Publisher 10/11, this has changed to: Windows Server 2003/XP: C:\Documents and Settings\All Users\Application Data\QlikTech\SourceDocuments Windows Server 2008/Vista/7: C:\ProgramData\QlikTech\SourceDocuments Be aware of the fact that these folder settings are stored in the QVPR database and will be unchanged when migrating a Publisher 9 to 10/11. You will have to manually re-map these folders if you want to have Source Documents in the 10 default folders, or make sure that the 9 legacy folder is manually created on the new system in migration scenarios. Management Console requirements After QlikView Server 9, Internet Explorer 6 is no longer supported in the QlikView Management Console or the QlikView Enterprise Management Console. Consider upgrading on machines that have administrative access or use another supported web browser. More information on browser support is defined in QlikView Server Reference manual or Release notes for each release. Service added: QlikView Settings Service An additional and optional service has been introduced the QlikView Settings Service. This service has the purpose to work as the administrative service for web server settings if the IIS is used to handle the QlikView Accesspoint. It will only be installed if IIS support is selected (or if the service itself is explicitly installed) and will use the same configuration files as the QlikView WebServer. Note: Read more about the QlikView Settings Service in the QlikView Server 11 Reference manual QlikView 11 Upgrade and Migrations Page 11

12 QlikView 9 Upgrade Scenarios Upgrade QlikView Server 9 to QlikView Server 10 or 11 Installed: QlikView Server 9 Upgrade to: QlikView Server 10 or QlikView Server 11 OS: Windows Server 2008 R2 x64 Scenario This scenario performs an in-place upgrade on a single host QlikView Server 9 installation to QlikView Server 10 or 11. This is a single-machine configuration with all QlikView services residing on the same server. We will make sure that all server settings stay the same and that we keep the configured reload schedules on documents. This QlikView Server has no Publisher license applied and will not have one after the upgrade. Procedure overview 1. Upgrade QlikView Server 2. Migrate reload schedules from 9 to 10/11 Step 1: Upgrade QlikView Server 1. In the Windows Services management console, stop all QlikView Server 9 services. 2. Optional: Uninstall QlikView Server 9, either from the Control Panel in Windows or by running the QlikView Server 9 installation package and selecting the Remove option. 3. Run the installation package for QlikView Server 10/ On the Profile(s) step of the installation, select the Full install(ation) option. 5. On the Logon Information step of the installation, provide the credentials for the service account to be used for the QlikView services. This account will be automatically added to the group QlikView Administrators. Note that it will not be added to the machine local group Administrators, which is a requirement. 6. When the installation has finished, a reboot of the machine is recommended. 7. To verify services availability, open the QlikView Enterprise Management Console (QlikView Management Console in 11) from Windows Start menu > QlikView. Navigate to Status > Services. There should be three services that have Status of Running: a. DSC (QlikView Directory Service Connector) b. QVS (QlikView Server) c. QVWS (QlikView Web Server) 8. If you are running QlikView Server 11, you will also see a fourth service: a. QMS (QlikView Management Service) QlikView 11 Upgrade and Migrations Page 12

13 Step 2: Migrate reload schedules from 9 to 10/11 1. We are now going to migrate the reload schedules for documents. Since we are not using Publisher, this is a separate step that does not involve moving the QVPR database. Go to the tab System > Setup > QlikView Servers > QVS@[machine] > General. 2. Under the Migrate Schedules header, press Migrate. 3. Verify by navigating to Documents > User Documents > QVS@[machine] and look at the icon on the document(s) that had reloads scheduled in QlikView Server 9 a schedule will be signified by a small timer watch on the document icon. Verify by clicking the Reload tab and checking the Reload Schedule settings. 4. The service settings for the QlikView Server service will have been migrated from the registry (9) to the new Settings.ini file (10/11). Upgrade QlikView Server 9 to QlikView Server & Publisher 10 or 11 Installed: QlikView Server 9 Upgrade to: QlikView Server & Publisher 10 or 11 OS: Windows Server 2008 R2 x64 Scenario This scenario performs an in-place upgrade on a single host QlikView Server 9 installation to QlikView Server 10 or 11 and at the same time upgrade to Publisher. This is a singlemachine configuration with all QlikView services residing on the same server. All server settings stay the same and the configured reload schedules on documents remain the same. This scenario requires the QlikView Power Tool Reload Schedule Migration Tool. The tool can be found in the QlikView Power Tool package that is available for download on the QlikView Community site here. Procedure overview 1. Upgrade QlikView Server 2. Migrate reload schedules from 9 to 10/11 3. Migrate reload schedules to QlikView Publisher tasks Step 1: Upgrade QlikView Server Perform the instructions under Step 1: Upgrade QlikView Server in the procedure for Upgrade QlikView Server 9 to QlikView Server 10/11. Step 2: Migrate reload schedules from 9 to 10a Perform the instructions under Step 2: Migrate reload schedules from 9 to 10/11 in the procedure for Upgrade QlikView Server 9 to QlikView Server 10/11. QlikView 11 Upgrade and Migrations Page 13

14 Step 3: Activate Publisher & migrate reload schedules to QlikView Publisher tasks 1. On the machine, run the Reload Schedule Migration Tool. 2. In the tool, use the button under Step 1 to browse to and select the QVPR folder for your QlikView Server installation. It is located under any of the following folders: Windows Server 2003/XP: C:\Documents and Settings\All Users\Application Data\QlikTech\ManagementService\QVPR Windows Server 2008/Vista/7: C:\ProgramData\QlikTech\ ManagementService\QVPR 3. The checkbox at Step 1 will automatically be checked. 4. In Step 2, change or add Source Document Folders to reflect the new system. Check the checkbox at Step In Step 3a, return to the QlikView Enterprise Management Console (QlikView Management Console in 11) and navigate to System > Licenses > QlikView Publisher, and enter your licensing information for Publisher. Press Apply License. Return to the tool and check the checkbox at Step 3a. 6. In Step 3b, open the Windows Services management console, stop the QlikView Management Service. Return to the tool and check the checkbox at Step 3b. 7. In Step 3c, return to the machine and manually copy the affected documents from the User Documents folders to the Source Documents folders according to the mapping from Step 2. Check the checkbox at Step 3c. 8. The tool is now ready to migrate the tasks. Press Recreate Tasks Now. The checkbox at Step 4 will be checked automatically. 9. In Step 5, open the Windows Services management console, start the QlikView Management Service. Return to the tool and check the checkbox at Step 5. You will get a message saying that the migration was completed. 10. Verify by returning to the Enterprise Management Console (Management Console in 11); Documents > Source Documents and find your reload tasks on the moved documents. Note: If you find your tasks under the <Orphaned> node, please make sure that you have the correct Source Documents folder mapped in Distribution Service QlikView 11 Upgrade and Migrations Page 14

15 Upgrade QlikView Server & Publisher 9 to QlikView Server & Publisher 10 or 11 Installed: QlikView Server & Publisher 9 Upgrade to: QlikView Server & Publisher 10 or 11 OS: Windows Server 2008 R2 x64 Scenario This scenario performs an in-place upgrade on a single host QlikView Server 9 installation to QlikView Server 10 or 11 and at the same time migrates all tasks in Publisher. This is a single-machine configuration with all QlikView services residing on the same server. All server settings stay the same and all tasks and triggers in Publisher are kept as-is. When performing an in-place upgrade of a QlikView Server & Publisher 9 to 10 or 11, the Publisher tasks will be automatically migrated. This means that the QVPR database will be migrated to the 10 or 11 format. Procedure overview 1. Upgrade QlikView Server 2. Verify Publisher task migration Step 1: Upgrade QlikView Server Perform the instructions under Step 1: Upgrade QlikView Server in the procedure for Upgrade QlikView Server 9 to QlikView Server 10/11. Step 2: Verify Publisher task migration When a QlikView Server 10/11 Management Service started the first time, it will try and locate any version 9 QVPR database still on the server in version 9 legacy folders, depending on OS: Windows Server 2003/XP: C:\Documents and Settings\All Users\Application Data\QlikTech\Publisher\CommandCenter Windows Server 2008/Vista/7: C:\ProgramData\QlikTech\Publisher\ CommandCenter It will search for two components: 1. A folder named QVPR 2. An.ini file named qvpr_<machine>.ini (where <machine> is the hostname of the current machine where the Management Service is installed) QlikView 11 Upgrade and Migrations Page 15

16 If these two components are found, the QlikView Server 10/11 Management Service will automatically upgrade the QVPR database to the 10/11 format and move it to its new location. 1. On the machine, browse to the C:\ProgramData\QlikTech\Publisher\CommandCenter folder. Verify that the qvpr_<machine>.ini file has changed name to qvpr_<machine>. migrated.ini. This signals that the migration has taken place. 2. Browse to the C:\ProgramData\QlikTech\ManagementService\QVPR folder. This is the new QVPR location for version 10/11. Open the file About.xml in a text editor. This file contains the versions that the QVPR has gone through via upgrades. Verify that the XML file has been upgraded properly by looking at the last VersionRow node, where the installation date and QlikView Publisher version will be stated. 3. Open the QlikView Server Enterprise Management Console via Windows Start > QlikView. 4. To verify services availability, open the QlikView Enterprise Management Console (QlikView Management Console in 11) from Windows Start menu > QlikView. Navigate to Status > Services. There should be four services that has Status set to Running: a. DSC (QlikView Directory Service Connector) b. QDS (QlikView Distribution Service) c. QVS (QlikView Server) d. QVWS (QlikView Web Server) 5. If you are running QlikView Server 11, you will also see a fifth service: a. QMS (QlikView Management Service) 6. Navigate to Documents > Source Documents and verify your tasks. QlikView 11 Upgrade and Migrations Page 16

17 Section 3: Existing QlikView Server 10 This section is written for QlikView administrators who are considering migrating from QlikView version 10 to QlikView version 11. Considerations There are no major architectural changes between QlikView Server 10 and 11 that will affect upgrade scenarios notably. Please refer to the Release Notes for QlikView 11 for differences between versions. QlikView 10 Upgrade Scenarios Upgrade QlikView Server 10 to QlikView Server 11 Installed: QlikView Server 10 Upgrade to: QlikView Server 11 OS: Windows Server 2008 R2 x64 Scenario This scenario performs an in-place upgrade on a single host QlikView Server 10 installation to QlikView Server 11. This is a single-machine configuration with all QlikView services residing on the same server. All server settings stay the same and the configured reload schedules on documents remain the same. This QlikView Server has no Publisher license applied and will not have one after the upgrade. Procedure overview 1. Upgrade QlikView Server 2. Migrate reload schedules from 10 to 11 Step 1: Upgrade QlikView Server 1. In the Windows Services management console, stop all QlikView Server 10 services. 2. Optional: Uninstall QlikView Server 10, either from the Control Panel in Windows or by running the QlikView Server 10 installation package and selecting the Remove option. 3. Run the installation package for QlikView Server 11. Note: If you have not uninstalled an earlier version of QlikView Server, select the option Uninstall earlier version during installation. 4. On the Profile step of the installation, select the Full installation, Single Machine option. Note: In this scenario, we will use the option with QlikView WebServer. 5. On the Logon Information step of the installation, provide the credentials for the service account to be used for the QlikView services. This account will be automatically added to the group QlikView Administrators. Note: that it will not be added to the machine local group Administrators, which is a requirement. QlikView 11 Upgrade and Migrations Page 17

18 6. When the installation has finished, a reboot of the machine is recommended. 7. To verify services availability, open the QlikView Management Console from Windows Start menu > QlikView. Navigate to Status > Services. There should be four services that has Status set to Running: a. DSC (QlikView Directory Service Connector) b. QMS (QlikView Management Service) c. QVS (QlikView Server) d. QVWS (QlikView Web Server) 8. Verify that the tasks have been migrated by open the QlikView Management Console and navigate to Documents > User Documents. Documents that have tasks will have a different icon with a small timer on them. Note: The reload schedules between 10 and 11 does not need to be migrated, since reload tasks in 10 is stored in the QVPR database. They are kept in the upgrade process and do not need a separate step. Upgrade QlikView Server 10 to QlikView Server & Publisher 11 Installed: QlikView Server 10 Upgrade to: QlikView Server & Publisher 11 OS: Windows Server 2008 R2 x64 Scenario This scenario performs an in-place upgrade on a single host QlikView Server 10 installation to QlikView Server 11 and at the same time upgrade to Publisher. This is a single-machine configuration with all QlikView services residing on the same server. All server settings stay the same and that we keep the configured reload schedules on documents. This scenario requires the QlikView Power Tool Reload Schedule Migration Tool. The tool can be found in the QlikView Power Tool package that is available for download on the QlikView Community site here. Procedure overview 1. Upgrade QlikView Server 2. Activate Publisher & migrate reload schedules to QlikView Publisher tasks Step 1: Upgrade QlikView Server 1. Perform the instructions under Step 1: Upgrade QlikView Server in the procedure for Upgrade QlikView Server 10 to QlikView Server 11. QlikView 11 Upgrade and Migrations Page 18

19 Step 2: Activate Publisher & migrate reload schedules to QlikView Publisher tasks 1. On the machine, run the Reload Schedule Migration Tool. 2. In the tool, use the button under Step 1 to browse to and select the QVPR folder for your QlikView Server installation. It is located under: a. Windows Server 2003/XP: C:\Documents and Settings\All Users\Application Data\QlikTech\ManagementService\QVPR b. Windows Server 2008/Vista/7: C:\ProgramData\QlikTech\ ManagementService\QVPR 3. Check the checkbox at Step In Step 2, change or add Source Document Folders to reflect the new system. Check the checkbox at Step In Step 3a, return to the Enterprise Management Console (Management Console in 11) and navigate to System > Licenses > QlikView Publisher, and enter your licensing information for Publisher. Press Apply License. Return to the tool and check the checkbox at Step 3a. 6. In Step 3b, open the Windows Services management console, stop the QlikView Management Service. Return to the tool and check the checkbox at Step 3b. 7. In Step 3c, return to the machine and manually copy the affected documents from the User Documents folders to the Source Documents folders according to the mapping from Step 2. Check the checkbox at Step 3c. 8. The tool is now ready to migrate the tasks. Check the checkbox at Step 4 and press Recreate Tasks Now. You will get a message saying that the tasks were migrated successfully. 9. In Step 5, open the Windows Services management console, start the QlikView Management Service. Return to the tool and check the checkbox at Step Verify by returning to the QlikView Enterprise Management Console; Documents > Source Documents and find your reload tasks on the moved documents. QlikView 11 Upgrade and Migrations Page 19

20 Upgrade QlikView Server & Publisher 10 to QlikView Server & Publisher 11 Installed: QlikView Server & Publisher 10 Upgrade to: QlikView Server & Publisher 11 OS: Windows Server 2008 R2 x64 Scenario This scenario performs an in-place upgrade on a single host QlikView Server 10 installation to QlikView Server 11 and at the same time migrate all tasks in Publisher. This is a singlemachine configuration with all QlikView services residing on the same server. All server settings stay the same and all tasks and triggers in Publisher are kept as-is. When performing an in-place upgrade of a QlikView Server & Publisher 10 to 11, the Publisher tasks will be automatically migrated. This means that the QVPR database will be migrated to the 11 format. Procedure overview 1. Upgrade QlikView Server 2. Verify Publisher task migration Step 1: Upgrade QlikView Server 1. Perform the instructions under Step 1: Upgrade QlikView Server in the procedure for Upgrade QlikView Server 10 to QlikView Server 11. Step 2: Verify Publisher task migration When a QlikView Server 11 Management Service started the first time, it will try and locate any version 9 QVPR database still on the server in version 9 legacy folders. It will search for two components in the C:\ProgramData\QlikTech\Publisher\CommandCenter folder: A folder named QVPR An.ini file named qvpr_<machine>.ini (where <machine> is the hostname of the current machine where the Management Service is installed) QlikView 11 Upgrade and Migrations Page 20

21 If these two components are found, the QlikView Server 10/11 Management Service will automatically upgrade the QVPR database to the 10/11 format and move it to its new location. 1. On the machine, browse to the C:\ProgramData\QlikTech\Publisher\CommandCenter folder. Verify that the qvpr_<machine>.ini file has changed name to qvpr_<machine>. migrated.ini. This signals that the migration has taken place. 2. Browse to the C:\ProgramData\QlikTech\ManagementService\QVPR folder. This is the new QVPR location for version 10/11. Open the file About.xml in a text editor. This file contains the versions that the QVPR has gone through via upgrades. Verify that the XML file has been upgraded properly by looking at the last VersionRow node, where the installation date and QlikView Publisher version will be stated. 3. Open the QlikView Server Enterprise Management Console via Windows Start > QlikView. 4. Navigate to Status > Services and verify that four tasks are running. 5. Navigate to Documents > Source Documents and verify your tasks. Section 4: Example Multi-Machine Scenarios This section is written for QlikView administrators who are migrating an existing deployment where multiple machines are being used to host the various QlikView services of a deployment or where a multi-machine deployment scenario is being considered for the first time. (Note: This is not intended as a discussion on clustering QlikView Servers). Best practices for migrating QlikView services are provided in Section 5: Relocating QlikView Services. Considerations One service at a time A good rule when upgrading or migrating multiple machines is to plan for one service at a time. Consider the different services as different roles that all needs to be upgraded in turns to complete the upgrade or migration. QlikView 11 Upgrade and Migrations Page 21

22 Multi-machine upgrade QlikView Server & Publisher 10 to 11 The multi-machine scenario Consider a scenario where we have an environment with QlikView Server 10 installed and all services are distributed over servers like below: Machine1 Machine2 Machine3 Directory Svc. Connector10 Distribution Service 10 QlikView Server 10 QlikView WebServer 10 Management Service QlikTech, Inc. Server Service(s) Machine1 QlikView Server 10, Directory Service Connector 10 Machine2 QlikView WebServer 10 Machine3 QlikView Distribution Service 10, QlikView Management Service 10 This should be the configuration after upgrade: Machine1 Machine2 Machine3 Directory Svc. Connector 11 Distribution Service 11 QlikView Server 11 QlikView WebServer 11 Management Service QlikTech, Inc. Server Service(s) Machine1 QlikView Server 11, Directory Service Connector 11 Machine2 QlikView WebServer 11 Machine3 QlikView Distribution Service 11, QlikView Management Service 11 QlikView 11 Upgrade and Migrations Page 22

23 Scenario This upgrade scenario is pretty straightforward and consists of only three procedures each one upgrading the services at one machine at a time. Note: There aren t that big a difference between this scenario where we upgrade from 10 to 11 and a scenario where we upgrade from 9 to 10/11 in place upgrades is helped by the automatic migration of existing configuration files from earlier version to new ones when services start up. Procedure overview 1. Perform an in-place upgrade of QlikView Server and Directory Service Connector on Machine1 2. Perform an in-place upgrade of QlikView WebServer on Machine2 3. Perform an in-place upgrade of QlikView Distribution Service and QlikView Management Service on Machine3 Step 1: Upgrade Machine1 1. On Machine1, stop all services. 2. Run the QlikView Server 11 installation package. The installation will detect the previous QlikView Server. Select the option Uninstall earlier version. 3. In the Profiles step of the installation, make sure to select the option Custom installation, select profiles and install only the following Profile: a. QlikView Server Note: The Directory Service Connector is included in this profile. Do not select Full Installation, since this will install all services. 4. Reboot Machine1. The service will start automatically after restart. Step 2: Upgrade Machine2 1. On Machine2, stop all services. 2. Run the QlikView Server 11 installation package. The installation will detect the previous QlikView Server. Select the option Uninstall earlier version. 3. In the Profiles step of the installation, make sure to select the option Custom installation, select profiles and install only the following Profile: a. Webserver 4. Reboot Machine2. The service will start automatically after restart. QlikView 11 Upgrade and Migrations Page 23

24 Step 3: Upgrade Machine3 1. On Machine3, stop all services. 2. Run the QlikView Server 11 installation package. The installation will detect the previous QlikView Server. Select the option Uninstall earlier version. 3. In the Profiles step of the installation, make sure to select the option Custom installation, select profiles and install only the following Profiles: a. Reload/Distribution Engine b. Management Console 5. Reboot Machine3. The service will start automatically after restart. Machine migration QlikView Server & Publisher 9 to 10 The scale-out scenario Consider a scenario where we have all QlikView services on one single machine, but have decided to scale out our environment during the upgrade by distributing the services across several machines. We will upgrade from QlikView Server 9 to 10/11 in the process and we are already using Publisher in 9. This is the configuration before upgrade and migration: Machine1 QlikView Server 9 Distribution Service 9 Directory Svc. Connector 9 Management Service 9 Command Center Svc. 9 QlikView WebServer QlikTech, Inc. Server Machine1 Service(s) QlikView Server 9, Directory Service Connector 9, QlikView WebServer 9, QlikView Distribution Service 9, QlikView Management Service 9 QlikView 11 Upgrade and Migrations Page 24

25 This should be the configuration after upgrade and migration. Machine1 Machine2 Machine3 Directory Svc. Connector 10 Distribution Service 10 QlikView Server 10 QlikView WebServer 10 Management Service QlikTech, Inc. Server Service(s) Machine1 QlikView Server 10, Directory Service Connector 10 Machine2 *new!* WebServer 10 Machine3 *new!* Distribution Service 10, Management Service 10 In this scenario, we will not strive for full uptime during the upgrade. We will instead shut down all QlikView services and complete the upgrade and migration before making the environment operational again. Scenario We need to consider that we are moving the WebServer, Distribution Service and Management Service from the original machine to the other two new machines. We will therefore have to uninstall these services permanently from Machine1. Also, the Command Center service will disappear as a whole, since it does no longer exist in QlikView Server 10/11. QlikView Server and Directory Service Connector will not be migrated, but only upgraded and will stay on Machine1. Since we have the QlikView Publisher Command Center 9, and subsequently the QVPR database, on Machine1, we need to move that database to Machine3 where the Management Service 10 will reside. Remember that ownership of the QVPR changed from Command Center in 9 to Management Service in 10/11. Machine2 will host the QvWebServer and/or IIS, and will be a regular install of those components. QlikView 11 Upgrade and Migrations Page 25

26 We also need to consider where to place the Source Documents folder in this new environment. Since we are moving the Distribution Service to Machine3, the Source Documents naturally follow that service. And since we are not using any clustering on QlikView services, we will not utilize a shared storage unless we specifically need to do so for infrastructural reasons. We will use a domain service account that has administrative privileges on all three machines that will run the services. Procedure overview 1. Perform an in-place upgrade of QlikView Server on Machine1 a. Remove QlikView Server 9 b. Install QlikView Server and QlikView Directory Service Connector 10/11 2. Move QlikView Distribution Service and QlikView Management Service to Machine3 a. Install QlikView Distribution Service and QlikView Management Service 10/11 b. Import and migrate Publisher database (QVPR), Publisher license and Source Documents c. Re-configure QDS, QVS and DSC in the Enterprise Management Console (Management Console in 11) 3. Move QlikView WebServer to Machine2 a. Install QlikView WebServer components and/or IIS components b. Re-configure QVWS in the Enterprise Management Console (Management Console in 11) Step 1: Machine1 We will start with the in-place upgrade of QlikView Server and Directory Service Connector on Machine1. From here we will also back up some configuration files before starting the upgrade and migration to the other machines. 1. Stop all QlikView Server services. 2. We will now create a backup of settings and databases for migration to the other machines in this configuration. a. Before starting the uninstallation, make a backup copy of the whole following folder: i. Windows Server 2003/XP: C:\Documents and Settings\All Users\ Application Data\QlikTech ii. Windows Server 2008/Vista/7: C:\ProgramData\QlikTech QlikView 11 Upgrade and Migrations Page 26

27 Note: Uninstalling QlikView Server will not remove data from the Application Data folders, but better safe than sorry. b. Backup all your User Documents and Source Documents, if they are outside of the Application Data folders that you backed up in the above step. Try and keep the folder structure to ease the migration later. c. Open the Windows Registry Editor via Windows Start > Run.. > regedit and export a copy of the whole key: HKEY_LOCAL_MACHINE\SOFTWARE\QlikTech\QlikViewServer\Settings 7. This is the settings for the QlikView Server service. 3. Uninstall QlikView Server 9 all services. 4. Install QlikView Server 10, but make sure to install only the following services: a. QlikView Server b. Directory Service Connector 5. Reboot the machine. At service startup, QlikView Server will migrate its settings from the version 9 legacy location in registry and copy them to its new Settings.ini configuration file, since this is an in-place upgrade of QlikView Server. The Directory Service Connector does not migrate any settings, since they are confined in the QVPR. Step 2: Machine3 Next, we install the Distribution Service and the Management Service on Machine3, and then migrate settings for Publisher to this machine. Once the Management Service is up and running, we will also start verifying the upgrade of the QlikView Server and Directory Service Connector services by updating their references from the Enterprise Management Console. 1. Install QlikView Server 10, but make sure to install only the following services: a. Distribution Service b. Management Service 2. Copy the following items from the following folder on Machine1 and place them in a folder with the exact same path on Machine3: a. Windows Server 2003/XP: C:\Documents and Settings\All Users\Application Data\QlikTech\Publisher\CommandCenter b. Windows Server 2008/Vista/7: C:\ProgramData\QlikTech\Publisher\ CommandCenter 3. This is to have the Management Service 10/11 recognize the version 9 database and migrate it to 10/11, as well as bringing the license information for Publisher to the new machine. The files/folders are: a. The folder QVPR and all its content b. The file qvpr_machine1.ini c. The folder Publisher LEF d. The file reginfo.txt QlikView 11 Upgrade and Migrations Page 27

28 4. Rename the new qvpr_machine1.ini file to qvpr_machine3.ini. 5. Reboot the machine. 6. Now, move all Source Documents and its folder structure from Machine1 to Machine3. You will find the newly created Source Documents folder under any of the following folders (if it is not created on Machine3, create it manually): a. Windows Server 2003/XP: C:\Documents and Settings\All Users\Application Data\QlikTech b. Windows Server 2008/Vista/7: C:\ProgramData\QlikTech 7. When the QlikView Management Service 10 starts for the first time, it will find the QVPR database in the version 9 legacy folder structure and migrate it. Verify that the QVPR was migrated by making sure the qvpr_machine3.ini file has been renamed to qvpr_machine3. migrated.ini. Also look in the About.xml file in the QVPR folder to see the new version of the database. 8. We will now re-configure the Distribution Service for this new machine. Open the Enterprise Management Console. a. Under System > Setup > Distribution Services, change the Url value to reflect the new machine name to where the QDS resides. i. QlikView Server 10: ii. QlikView Server 11: b. Then click Apply and manually restart the QlikView Distribution Service from the Windows Services Console on Machine3. c. Under System > Setup > Distribution Services > QDS@Machine3 > General, make sure to change the Source Folders list to reflect the Source Document Folders on the new machine. Click Apply. 9. We will now verify the QlikView Server service for this configuration. a. Under System > Setup > QlikView Servers, verify that the Url value reflects the correct machine name; qvp://machine1, where the QVS resides. This will be unchanged since we did not move the upgraded QlikView Server 10 service. 10. We will now verify the Distribution Service for this configuration. a.under System > Setup > Directory Service Connectors, verify that the Url value reflects the correct machine name to where the DSC resides. This will be unchanged since we did not move the upgraded Directory Service Connector 10 service. i. QlikView Server 10: ii. QlikView Server 11: b. Then click Apply. 11. Verify under Status > Tasks > QDS@Machine3 to find your tasks on the Source Documents. Note: If you can only find your tasks under the <Orphans> folder under Documents > Source Documents, it s because the Source Folders in Distribution Service is not correctly mapped make sure they are correct on this new machine. QlikView 11 Upgrade and Migrations Page 28

29 Step 3: Machine2 In this final step, we will install the web server components on Machine2 and make sure that we can access its settings from the Enterprise Management Console and the Management Service, and also update the mappings to the QlikView Server(s) that Accesspoint will use. 1.If using IIS: a. Verify that there are no legacy web sites or virtual directories left in IIS from previous QlikView Server installations. Make sure you have at least one web site running that will act as the QlikView web site. 2. Install QlikView Server 10, but make sure to install only the following services: a. WebServer Note: If you are using IIS, make sure to select IIS during the install. If using the Config option in the installer, make sure that you install the QlikView Server Client files as well. 3. Reboot the machine. 4. We will now re-configure the web server for this new machine. a. Under System > Setup > QlikView Web Servers, change the Url value to reflect the correct machine name to where the QvWebServer/IIS resides. i. If using QvWebServer: 1. QlikView Server 10: 2. QlikView Server 11: ii. If using IIS: 1. b. Then click Apply. Note: If QMS cannot access the Web Server for some reason, make sure to verify that the aspx page as well as the the directory QvAjaxZfc has its security settings set to Windows Authentication only. c. Verify that the web server responds properly by navigating to System > Setup > QlikView Web Servers > > Summary. d. Under System > Setup > QlikView Web Servers > > AccessPoint, select the QVS that the Accesspoint will work against under Server Connections. Note that the Load Balancing setting only applies if you are using a QVS cluster. Click Apply. 5. Verify by opening a web browser and browsing to the Accesspoint via Your environment should now be fully upgraded to QlikView Server 10/11. QlikView 11 Upgrade and Migrations Page 29

30 Section 5: Re-locating QlikView Services This section is written for QlikView administrators who are relocating an existing deployment from a machine(s) to a new machine(s) in version 10 or 11 and is included to assist in understanding multi-machine deployment migrations, covered in Section 4 of this document. This section covers the best practices for relocating 4 QlikView server-side services: QlikView Server service, Directory Service Connector service, WebServer service and Distribution Service service. QlikView Server 10/11 Installed: QlikView Server 10/11 OS: Windows Server 2008 R2 x64 Scenario This is a multi-machine configuration with all QlikView Server 10/11 services currently residing on the same server; Machine1. We are going to move the QlikView Server service from Machine1 to Machine2 and migrate its settings to the new machine. Procedure overview 1. Install QlikView Server on Machine2 2. Migrate settings 3. Re-configure environment 4. Uninstall on Machine1 Step 1: Install QlikView Server service on Machine2 1. Stop the QlikView Server service on Machine1 from the Windows Services console. 2. Run the installation package for QlikView Server 10/11 on Machine2. Make sure to install only the following service: a. QlikView Server Note: Use the Config option during the installation procedure to select only QlikView Server. If you select the QlikView Server role/profile, and not using the Config option, it will install both QlikView Server and Directory Service Connector automatically. 3. Reboot Machine2. The service will start automatically after restart. QlikView 11 Upgrade and Migrations Page 30