Upgrade Guide. Version: 9.2.1m. Document Number: m

Transcription

1 Upgrade Guide Version: 9.2.1m Document Number: m

2 Sixteenth Edition, version 9.2.1m To ensure that you are using the documentation that corresponds to the software you are licensed to use, compare this version number with the software version shown in About MicroStrategy... in the Help menu of your software. Document number: m Copyright 2011 by MicroStrategy Incorporated. All rights reserved. If you have not executed a written or electronic agreement with MicroStrategy or any authorized MicroStrategy distributor, the following terms apply: This software and documentation are the proprietary and confidential information of MicroStrategy Incorporated and may not be provided to any other person. Copyright by MicroStrategy Incorporated. All rights reserved. THIS SOFTWARE AND DOCUMENTATION ARE PROVIDED AS IS AND WITHOUT EXPRESS OR LIMITED WARRANTY OF ANY KIND BY EITHER MICROSTRATEGY INCORPORATED OR ANYONE WHO HAS BEEN INVOLVED IN THE CREATION, PRODUCTION, OR DISTRIBUTION OF THE SOFTWARE OR DOCUMENTATION, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, GOOD TITLE AND NONINFRINGMENT, QUALITY OR ACCURACY. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE AND DOCUMENTATION IS WITH YOU. SHOULD THE SOFTWARE OR DOCUMENTATION PROVE DEFECTIVE, YOU (AND NOT MICROSTRATEGY, INC. OR ANYONE ELSE WHO HAS BEEN INVOLVED WITH THE CREATION, PRODUCTION, OR DISTRIBUTION OF THE SOFTWARE OR DOCUMENTATION) ASSUME THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR, OR CORRECTION. SOME STATES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. In no event will MicroStrategy, Inc. or any other person involved with the creation, production, or distribution of the Software be liable to you on account of any claim for damage, including any lost profits, lost savings, or other special, incidental, consequential, or exemplary damages, including but not limited to any damages assessed against or paid by you to any third party, arising from the use, inability to use, quality, or performance of such Software and Documentation, even if MicroStrategy, Inc. or any such other person or entity has been advised of the possibility of such damages, or for the claim by any other party. In addition, MicroStrategy, Inc. or any other person involved in the creation, production, or distribution of the Software shall not be liable for any claim by you or any other party for damages arising from the use, inability to use, quality, or performance of such Software and Documentation, based upon principles of contract warranty, negligence, strict liability for the negligence of indemnity or contribution, the failure of any remedy to achieve its essential purpose, or otherwise. The entire liability of MicroStrategy, Inc. and your exclusive remedy shall not exceed, at the option of MicroStrategy, Inc., either a full refund of the price paid, or replacement of the Software. No oral or written information given out expands the liability of MicroStrategy, Inc. beyond that specified in the above limitation of liability. Some states do not allow the limitation or exclusion of liability for incidental or consequential damages, so the above limitation may not apply to you. The information contained in this manual (the Documentation) and the Software are copyrighted and all rights are reserved by MicroStrategy, Inc. MicroStrategy, Inc. reserves the right to make periodic modifications to the Software or the Documentation without obligation to notify any person or entity of such revision. Copying, duplicating, selling, or otherwise distributing any part of the Software or Documentation without prior written consent of an authorized representative of MicroStrategy, Inc. are prohibited. U.S. Government Restricted Rights. It is acknowledged that the Software and Documentation were developed at private expense, that no part is public domain, and that the Software and Documentation are Commercial Computer Software provided with RESTRICTED RIGHTS under Federal Acquisition Regulations and agency supplements to them. Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFAR et. seq. or subparagraphs (c)(1) and (2) of the Commercial Computer Software Restricted Rights at FAR , as applicable. Contractor is MicroStrategy, Inc., 1850 Towers Crescent Plaza, Tysons Corner, VA Rights are reserved under copyright laws of the United States with respect to unpublished portions of the Software. The following are either trademarks or registered trademarks of MicroStrategy Incorporated in the United States and certain other countries: MicroStrategy, MicroStrategy 6, MicroStrategy 7, MicroStrategy 7i, MicroStrategy 7i Evaluation Edition, MicroStrategy 7i Olap Services, MicroStrategy 8, MicroStrategy 9, MicroStrategy Distribution Services, MicroStrategy MultiSource Option, MicroStrategy Command Manager, MicroStrategy Enterprise Manager, MicroStrategy Object Manager, MicroStrategy Reporting Suite, MicroStrategy Power User, MicroStrategy Analyst, MicroStrategy Consumer, MicroStrategy Delivery, MicroStrategy BI Author, MicroStrategy BI Modeler, MicroStrategy Evaluation Edition, MicroStrategy Administrator, MicroStrategy Agent, MicroStrategy Architect, MicroStrategy BI Developer Kit, MicroStrategy Broadcast Server, MicroStrategy Broadcaster, MicroStrategy Broadcaster Server, MicroStrategy Business Intelligence Platform, MicroStrategy Consulting, MicroStrategy CRM Applications, MicroStrategy Customer Analyzer, MicroStrategy Desktop, MicroStrategy Desktop Analyst, MicroStrategy Desktop Designer, MicroStrategy ecrm 7, MicroStrategy Education, MicroStrategy etrainer, MicroStrategy Executive, MicroStrategy Infocenter, MicroStrategy Intelligence Server, MicroStrategy Intelligence Server Universal Edition, MicroStrategy MDX Adapter, MicroStrategy Narrowcast Server, MicroStrategy Objects, MicroStrategy OLAP Provider, MicroStrategy SDK, MicroStrategy Support, MicroStrategy Telecaster, MicroStrategy Transactor, MicroStrategy Web, MicroStrategy Web Business Analyzer, MicroStrategy World, Application Development and Sophisticated Analysis, Best In Business Intelligence, Centralized Application Management, Information Like Water, Intelligence Through Every Phone, Intelligence To Every Decision Maker, Intelligent E-Business, Personalized Intelligence Portal, Query Tone, Rapid Application Development, MicroStrategy Intelligent Cubes, The Foundation For Intelligent E-Business, The Integrated Business Intelligence Platform Built For The Enterprise, The Platform For Intelligent E-Business, The Scalable Business Intelligence Platform Built For The Internet, Industrial-Strength Business Intelligence, Office Intelligence, MicroStrategy Office, MicroStrategy Report Services, MicroStrategy Web MMT, MicroStrategy Web Services, Pixel Perfect, Pixel-Perfect, MicroStrategy Mobile, MicroStrategy Integrity Manager and MicroStrategy Data Mining Services are all registered trademarks or trademarks of MicroStrategy Incorporated. All other company and product names may be trademarks of the respective companies with which they are associated. Specifications subject to change without notice. MicroStrategy is not responsible for errors or omissions. MicroStrategy makes no warranties or commitments concerning the availability of future products or versions that may be planned or under development. Patent Information This product is patented. One or more of the following patents may apply to the product sold herein: U.S. Patent Nos. 6,154,766, 6,173,310, 6,260,050, 6,263,051, 6,269,393, 6,279,033, 6,567,796, 6,587,547, 6,606,596, 6,658,093, 6,658,432, 6,662,195, 6,671,715, 6,691,100, 6,694,316, 6,697,808, 6,704,723, 6,741,980, 6,765,997, 6,768,788, 6,772,137, 6,788,768, 6,798,867, 6,801,910, 6,820,073, 6,829,334, 6,836,537, 6,850,603, 6,859,798, 6,873,693, 6,885,734, 6,940,953, 6,964,012, 6,977,992, 6,996,568, 6,996,569, 7,003,512, 7,010,518, 7,016,480, 7,020,251, 7,039,165, 7,082,422, 7,113,993, 7,127,403, 7,174,349, 7,181,417, 7,194,457, 7,197,461, 7,228,303, 7,260,577, 7,266,181, 7,272,212, 7,302,639, 7,324,942, 7,330,847, 7,340,040, 7,356,758, 7,356,840, 7,415,438, 7,428,302, 7,430,562, 7,440,898, 7,486,780, 7,509,671, 7,516,181, 7,559,048, 7,574,376, 7,617,201, 7,725,811, 7,801,967, 7,836,178, 7,861,161, 7,861,253, 7,881,443, 7,925,616, 7,945,584, 7,970,782, and 8,005,870. Other patent applications are pending. Various MicroStrategy products contain the copyrighted technology of third parties. This product may contain one or more of the following copyrighted technologies: Graph Generation Engine Copyright Three D Graphics, Inc. All rights reserved. Actuate Formula One. Copyright Actuate Corporation. All rights reserved. XML parser Copyright Microsoft Corporation. All rights reserved. Xalan XSLT processor. Copyright The Apache Software Foundation. All rights reserved. Xerces XML parser. Copyright The Apache Software Foundation. All rights reserved. FOP XSL formatting objects. Copyright The Apache Software Foundation. All rights reserved. Portions of Intelligence Server memory management Copyright Compuware Corporation. All rights reserved. ASIHTTPRequest library. Copyright , All-Seeing Interactive. All rights reserved.

3 This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. ( International Components for Unicode Copyright Compaq Computer Corporation Copyright Hewlett-Packard Company Copyright IBM Corporation Copyright Hummingbird Communications Ltd. Copyright Silicon Graphics, Inc. Copyright Sun Microsystems, Inc. Copyright The Open Group All rights reserved. Real Player and RealJukebox are included under license from Real Networks, Inc. Copyright All rights reserved.

4

5 CONTENTS Description of Guide... ix About this book...x Additional formats...x How to find business scenarios and examples...xi What s new in this guide...xi Prerequisites...xii Who should use this guide...xii Resources... xiii Documentation... xiii Education...xxi Consulting...xxi International support...xxi Technical Support... xxii Feedback... xxvii 1. Impact of the Upgrade and Upgrade Checklist Introduction... 1 Impact of the upgrade... 2 New features and workflow changes... 3 The upgrade process checklist... 5 Upgrade best practices... 7 Reference materials Preparing for the Upgrade Introduction... 9 Reviewing upgrade prerequisites Database and driver requirements MicroStrategy, Inc. v

6 Contents Upgrade Guide System sizing guidelines Privileges and access Checking for supported data types Backing up the metadata Metadata compatibility Upgrading in a clustered environment Upgrading Web customizations Where to find best practices and upgrade considerations Upgrading MicroStrategy on Windows, UNIX, or Linux Introduction Upgrading MicroStrategy on Windows Uninstall the previous version of MicroStrategy Install and configure the latest version of MicroStrategy Intelligence Server and Desktop on a test server Update the production metadata Perform basic stability testing Install and configure the latest version of Intelligence Server in the production environment Install remaining MicroStrategy products in the production environment Run tests representing day-to-day usage Upgrading your Enterprise Manager environment Upgrading MicroStrategy on UNIX and Linux Installing MicroStrategy Universal products on UNIX and Linux Updating the metadata on a UNIX or Linux machine Completing the upgrade Using a response file with Configuration Wizard Creating a response file Loading a response file Response configuration parameters and options After the Upgrade Introduction Using License Manager to verify licensing Using Service Manager to check Intelligence Server Testing product functionality Intelligence Server and Desktop MicroStrategy Web MicroStrategy administrative tools vi 2011 MicroStrategy, Inc.

7 Upgrade Guide Contents Checking and assigning privileges Merging pre-existing translations into a single project Completing the upgrade process Accessing MicroStrategy documentation Migrating Intelligence Server from Windows to UNIX or Linux Troubleshooting the upgrade Index MicroStrategy, Inc. vii

8 Contents Upgrade Guide viii 2011 MicroStrategy, Inc.

9 BOOK OVERVIEW AND ADDITIONAL RESOURCES Description of Guide This guide contains information and procedures for migrating to MicroStrategy 9.2.1m. The information covers the upgrade process: preparing a MicroStrategy system for an upgrade, upgrading your MicroStrategy system in different environments, and performing important post-upgrade tasks. Before upgrading, review Chapter 1, Impact of the Upgrade and Upgrade Checklist for important information related to the specific version upgrade you intend to perform. Specifically, this guide provides the following information: Chapter 1, Impact of the Upgrade and Upgrade Checklist provides a checklist of the major steps involved in upgrading a MicroStrategy system, upgrade tips, compatibility and interoperability information, and the impact of specific version upgrades. Chapter 2, Preparing for the Upgrade lists the prerequisites of upgrading to the latest version of MicroStrategy and how to prepare your MicroStrategy system and projects for the upgrade MicroStrategy, Inc. ix

10 Book Overview and Additional Resources Upgrade Guide Chapter 3, Upgrading MicroStrategy on Windows, UNIX, or Linux walks you through the process of upgrading a MicroStrategy system in a Windows, UNIX, or Linux environment. Chapter 4, After the Upgrade provides information about the post-upgrade tasks you must perform once the upgrade process is complete. About this book This book is divided into chapters that begin with a brief overview of the chapter s content. The following sections provide the location of examples, list prerequisites for using this book, and describe the user roles the information in this book was designed for. Dates in the MicroStrategy Tutorial project are updated to reflect the current year. The sample documents and images in this guide, as well as the procedures, were created with dates that may no longer be available in the Tutorial project. Replace them with the first year of data in your Tutorial project. Additional formats This book is also available as an electronic publication in the Apple ibookstore, and can be read on an iphone or ipad with the ibooks app installed. To download this book, search for the book s title in the ibookstore search bar, or scan the QR code below using your device's camera. x About this book 2011 MicroStrategy, Inc.

11 Upgrade Guide Book Overview and Additional Resources How to find business scenarios and examples Within this guide, many of the concepts discussed are accompanied by business scenarios or other descriptive examples. For examples of reporting functionality, see the MicroStrategy Tutorial, which is MicroStrategy s sample warehouse, metadata, and project. Information about the MicroStrategy Tutorial may be found in the MicroStrategy Basic Reporting Guide. Detailed examples of advanced reporting functionality can be found in the MicroStrategy Advanced Reporting Guide. Business scenarios can be found in the Analytics Modules, which include a set of precreated sample reports, each from a different business area. Sample reports present data for analysis in such business areas as financial reporting, human resources, and customer analysis. What s new in this guide MicroStrategy 9.2.1m Any updates to this guide were minor and not directly related to MicroStrategy 9.2.1m. For a list of new features in MicroStrategy 9.2.1m, see the MicroStrategy Readme. MicroStrategy 9.2.1a Interoperability of MicroStrategy Mobile clients and servers on different versions of MicroStrategy has been clarified (see Impact of the upgrade, page 2). MicroStrategy The Configuration Wizard is now required to update your project metadata to the latest version (see Updating project metadata, page 12) MicroStrategy, Inc. About this book xi

12 Book Overview and Additional Resources Upgrade Guide MicroStrategy 9.2 Use the Configuration Wizard to automatically upgrade your existing database-based History List (see Upgrade the History List database, page 26; for response file parameters, see Upgrading History List repositories, page 55). Preview the SQL used to update the metadata from Configuration Wizard (see Update the production metadata, page 20). Prerequisites Before using this book, you should be familiar with the following: The installation and configuration information provided in the MicroStrategy Installation and Configuration Guide. If you do not review the MicroStrategy hardware and software requirements before upgrading, you may experience problems with the upgrade. The MicroStrategy Readmes for the current version of MicroStrategy. The MicroStrategy product suite and architecture, specifically ODBC connectivity and metadata. The basic structure of the MicroStrategy system from which you are upgrading. Who should use this guide This document is designed for system administrators and managers who intend to perform one or more of the following upgrades: MicroStrategy 8.0.x to MicroStrategy 9.2.1m MicroStrategy 8.1.x to MicroStrategy 9.2.1m MicroStrategy 9.0.x to MicroStrategy 9.2.1m MicroStrategy 9.2 to MicroStrategy 9.2.1m MicroStrategy to MicroStrategy 9.2.1m MicroStrategy 9.2.1a to MicroStrategy 9.2.1m xii About this book 2011 MicroStrategy, Inc.

13 Upgrade Guide Book Overview and Additional Resources Resources Documentation MicroStrategy provides both manuals and online help; these two information sources provide different types of information, as described below: Manuals: In general, MicroStrategy manuals provide: Introductory information and concepts Examples and images Checklists and high-level procedures to get started The steps to access the manuals are described in Accessing manuals and other documentation sources, page xix. Most of these manuals are also available printed in a bound, soft cover format. To purchase printed manuals, contact your MicroStrategy account executive or [email protected]. Help: In general, MicroStrategy help provides: Detailed steps to perform procedures Due Descriptions of each option on every software screen to translation time, manuals in languages other than English may contain information that is one or more releases behind. You can see the version number on the title page of each manual. For the most up-to-date translations, refer to the MicroStrategy Knowledge Base. MicroStrategy overview and evaluation Introduction to MicroStrategy: Evaluation Guide Instructions for installing, configuring, and using the MicroStrategy Evaluation Edition of the software. This guide also includes a detailed, step-by-step evaluation process of MicroStrategy features, where you perform reporting with the MicroStrategy Tutorial project and its sample business data MicroStrategy, Inc. Resources xiii

14 Book Overview and Additional Resources Upgrade Guide MicroStrategy Evaluation Edition Quick Start Guide Overview of the installation and evaluation process, and additional resources. Evaluate MicroStrategy for Linux Guide: In a Windows or Linux Environment with the MicroStrategy Evaluation Edition Virtual Appliance Evaluate MicroStrategy for Linux, in a Microsoft Windows or Linux environment, with the MicroStrategy Evaluation Edition Virtual Appliance. This guide provides all details to download, activate, and evaluate MicroStrategy software running in a Linux environment. MicroStrategy Reporting Suite: Quick Start Guide Evaluate MicroStrategy as a departmental solution. Provides detailed information to download, install, configure, and use the MicroStrategy Reporting Suite. MicroStrategy Mobile Suite: Quick Start Guide Evaluate MicroStrategy Mobile as a departmental solution. Provides detailed information to download, install, configure, and use the MicroStrategy Mobile Suite. Manuals for query, reporting, and analysis MicroStrategy Installation and Configuration Guide Information to install and configure MicroStrategy products on Windows, UNIX, Linux, and HP platforms, as well as basic maintenance guidelines. MicroStrategy Upgrade Guide Instructions to upgrade existing MicroStrategy products. MicroStrategy Project Design Guide Information to create and modify MicroStrategy projects, and understand facts, attributes, hierarchies, transformations, advanced schemas, and project optimization. MicroStrategy Basic Reporting Guide Instructions to get started with MicroStrategy Desktop and MicroStrategy Web, and how to analyze data in a report. Includes the basics for creating reports, metrics, filters, and prompts. xiv Resources 2011 MicroStrategy, Inc.

15 Upgrade Guide Book Overview and Additional Resources MicroStrategy Advanced Reporting Guide: Enhancing Your Business Intelligence Application Instructions for advanced topics in the MicroStrategy system, building on information in the Basic Reporting Guide. Topics include reports, Freeform SQL reports, Query Builder reports, filters, metrics, Data Mining Services, custom groups, consolidations, and prompts. MicroStrategy Report Services Document Analysis Guide: Analyzing Data with Report Services Documents Instructions for a business analyst to execute and analyze a document in MicroStrategy Desktop and MicroStrategy Web, building on basic concepts about projects and reports presented in the MicroStrategy Basic Reporting Guide. MicroStrategy Report Services Document Creation Guide: Creating Boardroom Quality Documents Instructions to design and create Report Services documents, building on information in the MicroStrategy Report Services Document Analysis Guide. MicroStrategy OLAP Services Guide Information on MicroStrategy OLAP Services, which is an extension of MicroStrategy Intelligence Server. OLAP Services features include Intelligent Cubes, derived metrics, derived elements, dynamic aggregation, view filters, and dynamic sourcing. MicroStrategy Office User Guide Instructions for using MicroStrategy Office to work with MicroStrategy reports and documents in Microsoft Excel, PowerPoint, Word, and Outlook, to analyze, format, and distribute business data. MicroStrategy Mobile Analysis Guide: Analyzing Data with MicroStrategy Mobile Information and instructions for using MicroStrategy Mobile to view and analyze data, and perform other business tasks with MicroStrategy reports and documents on a mobile device. MicroStrategy Mobile Design and Administration Guide: A Platform for Mobile Intelligence Information and instructions to install and configure MicroStrategy Mobile, as well as instructions for a designer working in MicroStrategy Desktop or MicroStrategy Web to create effective reports and documents for use with MicroStrategy Mobile MicroStrategy, Inc. Resources xv

16 Book Overview and Additional Resources Upgrade Guide MicroStrategy System Administration Guide: Tuning, Monitoring, and Troubleshooting your MicroStrategy Business Intelligence System Concepts and high-level steps to implement, deploy, maintain, tune, and troubleshoot a MicroStrategy business intelligence system. MicroStrategy Supplemental Reference for System Administration: VLDB Properties, Internationalization, User Privileges, and other Supplemental Information for Administrators Information and instructions for MicroStrategy administrative tasks such as configuring VLDB properties and defining data and metadata internationalization, and reference material for other administrative tasks. MicroStrategy Functions Reference Function syntax and formula components; instructions to use functions in metrics, filters, attribute forms; examples of functions in business scenarios. MicroStrategy MDX Cube Reporting Guide Information to integrate MicroStrategy with MDX cube sources. You can integrate data from MDX cube sources into your MicroStrategy projects and applications. Manuals for Analytics Modules Analytics Modules Installation and Porting Guide Customer Analysis Module Reference Sales Force Analysis Module Reference Financial Reporting Analysis Module Reference Sales and Distribution Analysis Module Reference Human Resources Analysis Module Reference Manuals for Narrowcast Services products MicroStrategy Narrowcast Server Getting Started Guide Instructions to work with the tutorial to learn Narrowcast Server interfaces and features. xvi Resources 2011 MicroStrategy, Inc.

17 Upgrade Guide Book Overview and Additional Resources MicroStrategy Narrowcast Server Installation and Configuration Guide Information to install and configure Narrowcast Server. MicroStrategy Narrowcast Server Application Designer Guide Fundamentals of designing Narrowcast Server applications. MicroStrategy Narrowcast Server System Administrator Guide Concepts and high-level steps to implement, maintain, tune, and troubleshoot Narrowcast Server. MicroStrategy Narrowcast Server Upgrade Guide Instructions to upgrade an existing Narrowcast Server. Software Development Kits MicroStrategy Developer Library (MSDL) Information to understand the MicroStrategy SDK, including details about architecture, object models, customization scenarios, code samples, and so on. MicroStrategy Web SDK The Web SDK is available in the MicroStrategy Developer Library, which is sold as part of the MicroStrategy SDK. Narrowcast Server SDK Guide Instructions to customize Narrowcast Server functionality, integrate Narrowcast Server with other systems, and embed Narrowcast Server functionality within other applications. Documents the Narrowcast Server Delivery Engine and Subscription Portal APIs, and the Narrowcast Server SPI. Documentation for MicroStrategy Portlets Enterprise Portal Integration Help Information to help you implement and deploy MicroStrategy BI within your enterprise portal, including instructions for installing and configuring out-of-the-box MicroStrategy Portlets for several major enterprise portal servers MicroStrategy, Inc. Resources xvii

18 Book Overview and Additional Resources Upgrade Guide This resource can be accessed using the MicroStrategy Product Manuals page, as described in Accessing manuals and other documentation sources, page xix. Documentation for MicroStrategy GIS Connectors GIS Integration Help Information to help you integrate MicroStrategy with Geospatial Information Systems (GIS), including specific examples for integrating with various third-party mapping services. This resource can be accessed using the MicroStrategy Product Manuals page, as described in Accessing manuals and other documentation sources, page xix. Help Each MicroStrategy product includes an integrated help system to complement the various interfaces of the product as well as the tasks that can be accomplished using the product. Some of the MicroStrategy help systems require a web browser to be viewed. For supported web browsers, see the MicroStrategy Readme. MicroStrategy provides several ways to access help: Help button: Use the Help button or? (question mark) icon on most software windows to see help for that window. Help menu: From the Help menu or link at the top of any screen, select MicroStrategy Help to see the table of contents, the Search field, and the index for the help system. F1 key: Press F1 to see context-sensitive help that describes each option in the software window you are currently viewing. For MicroStrategy Web, MicroStrategy Web Administrator, and MicroStrategy Mobile Server, pressing the F1 key opens the context-sensitive help for the web browser you are using to access these MicroStrategy interfaces. Use the Help menu or? (question mark) icon to access help for these MicroStrategy interfaces. xviii Resources 2011 MicroStrategy, Inc.

19 Upgrade Guide Book Overview and Additional Resources Accessing manuals and other documentation sources The manuals are available from your MicroStrategy disk or the machine where MicroStrategy was installed. Adobe Acrobat Reader is required to view these manuals. If you do not have Acrobat Reader installed on your computer, you can download it from The best place for all users to begin is with the MicroStrategy Basic Reporting Guide. To access the installed manuals and other documentation sources, see the following procedures: To access installed manuals and other documentation sources on Windows, page xix To access installed manuals and other documentation sources on UNIX and Linux, page xix To access installed manuals and other documentation sources on Windows 1 From the Windows Start menu, choose Programs (or All Programs), MicroStrategy, then Product Manuals. A page opens in your browser showing a list of available manuals in PDF format and other documentation sources. 2 Click the link for the desired manual or other documentation source. 3 If you click the link for the Narrowcast Services SDK Guide, a File Download dialog box opens. This documentation resource must be downloaded. Select Open this file from its current location, and click OK. If bookmarks are not visible on the left side of an Acrobat (PDF) manual, from the View menu click Bookmarks and Page. This step varies slightly depending on your version of Adobe Acrobat Reader. To access installed manuals and other documentation sources on UNIX and Linux 1 Within your UNIX or Linux machine, navigate to the directory where you installed MicroStrategy. The default location is /opt/microstrategy, 2011 MicroStrategy, Inc. Resources xix

20 Book Overview and Additional Resources Upgrade Guide or $HOME/MicroStrategy/install if you do not have write access to /opt/microstrategy. 2 From the MicroStrategy installation directory, open the Documentation folder. 3 Open the Product_Manuals.htm file in a web browser. A page opens in your browser showing a list of available manuals in PDF format and other documentation sources. 4 Click the link for the desired manual or other documentation source. 5 If you click the link for the Narrowcast Services SDK Guide, a File Download dialog box opens. This documentation resource must be downloaded. Select Open this file from its current location, and click OK. If bookmarks are not visible on the left side of an Acrobat (PDF) manual, from the View menu click Bookmarks and Page. This step varies slightly depending on your version of Adobe Acrobat Reader. Documentation standards MicroStrategy online help and PDF manuals (available both online and in printed format) use standards to help you identify certain types of content. The following table lists these standards. These standards may differ depending on the language of this manual; some languages have rules that supersede the table below. Type bold italic Indicates Button names, check boxes, options, lists, and menus that are the focus of actions or part of a list of such GUI elements and their definitions Example: Click Select Warehouse. New terms defined within the text and in the glossary Names of other product manuals and documentation resources When part of a command syntax, indicates variable information to be replaced by the user Example: The aggregation level is the level of calculation for the metric. Example: Type copy c:\filename d:\foldername\filename xx Resources 2011 MicroStrategy, Inc.

21 Upgrade Guide Book Overview and Additional Resources Type Courier font Indicates Calculations Code samples Registry keys Path and file names URLs Messages displayed in the screen Text to be entered by the user Example: Sum(revenue)/number of months. Example: Type cmdmgr -f scriptfile.scp and press Enter. + A keyboard command that calls for the use of more than one key (for example, SHIFT+F1). A note icon indicates helpful information for specific situations. A warning icon alerts you to important information such as potential security risks; these should be read before continuing. Education MicroStrategy Education Services provides a comprehensive curriculum and highly skilled education consultants. Many customers and partners from over 800 different organizations have benefited from MicroStrategy instruction. For a detailed description of education offerings and course curriculums, visit Consulting MicroStrategy Consulting Services provides proven methods for delivering leading-edge technology solutions. Offerings include complex security architecture designs, performance and tuning, project and testing strategies and recommendations, strategic planning, and more. For a detailed description of consulting offerings, visit International support MicroStrategy supports several locales. Support for a locale typically includes native database and operating system support, support for date formats, 2011 MicroStrategy, Inc. Resources xxi

22 Book Overview and Additional Resources Upgrade Guide numeric formats, currency symbols, and availability of translated interfaces and certain documentation. MicroStrategy is certified in homogeneous configurations (where all the components lie in the same locale) in the following languages English (US), French, German, Italian, Japanese, Korean, Portuguese (Brazilian), Spanish, Chinese (Simplified), Chinese (Traditional), Danish, and Swedish. A translated user interface is available in each of the above languages. For information on specific languages supported by individual MicroStrategy system components, see the MicroStrategy readme. MicroStrategy also provides limited support for heterogeneous configurations (where some of the components may lie in different locales). Please contact MicroStrategy Technical Support for more details. Technical Support If you have questions about a specific MicroStrategy product, you should: 1 Consult the product guides, Help, and readme files. Locations to access each are described above. 2 Consult the MicroStrategy Knowledge Base online at A technical administrator in your organization may be able to help you resolve your issues immediately. 3 If the resources listed in the steps above do not provide a solution, contact MicroStrategy Technical Support directly. To ensure the most productive relationship with MicroStrategy Technical Support, review the Policies and Procedures document in your language, posted at Refer to the terms of your purchase agreement to determine the type of support available to you. MicroStrategy Technical Support can be contacted by your company s Support Liaison. A Support Liaison is a person whom your company has designated as a point-of-contact with MicroStrategy s support personnel. All customer inquiries and case communications must come through these named individuals. Your company may designate two employees to serve as their Support Liaisons, and can request to change their Support Liaisons two times per year with prior written notice to MicroStrategy Technical Support. xxii Resources 2011 MicroStrategy, Inc.

23 Upgrade Guide Book Overview and Additional Resources It is recommended that you designate Support Liaisons who have MicroStrategy Administrator privileges. This can eliminate security conflicts and improve case resolution time. When troubleshooting and researching issues, MicroStrategy Technical Support personnel may make recommendations that require administrative privileges within MicroStrategy, or that assume that the designated Support Liaison has a security level that permits them to fully manipulate the MicroStrategy projects and has access to potentially sensitive project data such as security filter definitions. Ensure issues are resolved quickly Before logging a case with MicroStrategy Technical Support, the Support Liaison may follow the steps below to ensure that issues are resolved quickly: 1 Verify that the issue is with MicroStrategy software and not a third party software. 2 Verify that the system is using a currently supported version of MicroStrategy software by checking the Product Support Expiration Schedule at 3 Attempt to reproduce the issue and determine whether it occurs consistently. 4 Minimize the complexity of the system or project object definition to isolate the cause. 5 Determine whether the issue occurs on a local machine or on multiple machines in the customer environment. 6 Discuss the issue with other users by posting a question about the issue on the MicroStrategy Customer Forum at The following table shows where, when, and how to contact MicroStrategy Technical Support. If your Support Liaison is unable to reach MicroStrategy Technical Support by phone during the hours of operation, they can leave a voic message, send or fax, or log a case using the Online Support 2011 MicroStrategy, Inc. Resources xxiii

24 Book Overview and Additional Resources Upgrade Guide Interface. The individual Technical Support Centers are closed on certain public holidays. North America EMEA: Europe The Middle East Africa Asia Pacific Latin America Web: Fax: (703) Phone: (703) Hours: 9:00 A.M. 7:00 P.M. Eastern Time, Monday Friday except holidays Web: Fax: +44 (0) The European Technical Support Centre is closed on national public holidays in each country. Phone: Belgium: France: Germany: Ireland: Italy: Poland: Scandinavia & Finland: Spain: The Netherlands: UK: +44 (0) International distributors: +44 (0) Hours: United Kingdom: 9:00 A.M. 6:00 P.M. GMT, Monday-Friday except holidays EMEA (except UK): 9:00 A.M. 6:00 P.M. CET, Monday-Friday except holidays [email protected] Web: Phone: Australia: Korea: Fax: Japan: Fax: Singapore: Fax: Asia Pacific (except Australia, Japan, Korea, and Singapore): Fax: Hours: Japan and Korea: 9:00 A.M. 6:00 P.M. JST (Tokyo), Monday-Friday except holidays Asia Pacific (except Japan and Korea): 7 A.M.-6 P.M. (Singapore) Monday-Friday except holidays [email protected] Web: Phone: LATAM (except Brazil and Argentina): Fax: Argentina: MSTR Fax: Brazil: Fax: Hours: Latin America (except Brazil): 9:00 A.M. 7:00 P.M. (Buenos Aires), Monday-Friday except holidays Brazil: 9 A.M. - 6 P.M. (São Paulo), Monday Friday except holidays xxiv Resources 2011 MicroStrategy, Inc.

25 Upgrade Guide Book Overview and Additional Resources Support Liaisons should contact the Technical Support Center from which they obtained their MicroStrategy software licenses or the Technical Support Center to which they have been designated. Required information when calling When contacting MicroStrategy Technical Support, please provide the following information: Personal information: Name (first and last) Company and customer site (if different from company) Contact information (phone and fax numbers, addresses) Case details: Configuration information, including MicroStrategy software product(s) and versions Full description of the case including symptoms, error messages(s), and steps taken to troubleshoot the case thus far Business/system impact If this is the Support Liaison s first call, they should also be prepared to provide the following: Street address Phone number Fax number address To help the Technical Support representative resolve the problem promptly and effectively, be prepared to provide the following additional information: Case number: Please keep a record of the number assigned to each case logged with MicroStrategy Technical Support, and be ready to provide it when inquiring about an existing case Software version and product registration numbers of the MicroStrategy software products you are using 2011 MicroStrategy, Inc. Resources xxv

26 Book Overview and Additional Resources Upgrade Guide Case description: What causes the condition to occur? Does the condition occur sporadically or each time a certain action is performed? Does the condition occur on all machines or just on one? When did the condition first occur? What events took place immediately prior to the first occurrence of the condition (for example, a major database load, a database move, or a software upgrade)? If there was an error message, what was its exact wording? What steps have you taken to isolate and resolve the issue? What were the results? System configuration (the information needed depends on the nature of the problem; not all items listed below may be necessary): Computer hardware specifications (processor speed, RAM, disk space, and so on) Network protocol used ODBC driver manufacturer and version Database gateway software version (For MicroStrategy Web-related problems) browser manufacturer and version (For MicroStrategy Web-related problems) Web server manufacturer and version If the issue requires additional investigation or testing, the Support Liaison and the MicroStrategy Technical Support representative should agree on certain action items to be performed. The Support Liaison should perform any agreed-upon actions before contacting MicroStrategy Technical Support again regarding the issue. If the Technical Support representative is responsible for an action item, the Support Liaison may call MicroStrategy Technical Support at any time to inquire about the status of the issue. xxvi Resources 2011 MicroStrategy, Inc.

27 Upgrade Guide Book Overview and Additional Resources Feedback Please send any comments or suggestions about user documentation for MicroStrategy products to: Send suggestions for product enhancements to: When you provide feedback to us, please include the name and version of the products you are currently using. Your feedback is important to us as we prepare for future releases MicroStrategy, Inc. Feedback xxvii

28 Book Overview and Additional Resources Upgrade Guide xxviii Feedback 2011 MicroStrategy, Inc.

29 1 1.IMPACT OF THE UPGRADE AND UPGRADE CHECKLIST Introduction This chapter provides a checklist for the upgrade process and provides a list of possible impacts of the upgrade, as well as best practices for upgrading to guide you as you upgrade MicroStrategy. It is strongly recommended that you carefully review and follow the upgrade procedure outlined in this chapter. This chapter has the following sections: Impact of the upgrade, page 2 The upgrade process checklist, page 5 Upgrade best practices, page 7 Reference materials, page MicroStrategy, Inc. 1

30 1 Impact of the Upgrade and Upgrade Checklist Upgrade Guide Impact of the upgrade MicroStrategy 9.2.1m features new products and architectural extensions to the MicroStrategy Business Intelligence Platform. Therefore, the upgrade may affect your users standard workflow. The list below details the immediate impact of the upgrade. For new features that may affect a user s workflow, see New features and workflow changes, page 3. MicroStrategy 9.2.1m is not interoperable with pre releases. That is, clients (such as MicroStrategy Web or Desktop) and servers (such as Intelligence Server or MicroStrategy Web Server) should be upgraded to MicroStrategy 9.2.1m. However, MicroStrategy 9.2.1m is interoperable with MicroStrategy 9.0.1, MicroStrategy 9.0.1m, MicroStrategy 9.0.2, MicroStrategy 9.2, MicroStrategy 9.2.1, and MicroStrategy 9.2.1a. In addition, you must upgrade both Intelligence Server and MicroStrategy Web to version 9.2.1m to ensure the successful execution of Report Services documents in Flash Mode. MicroStrategy Mobile clients from version 9.2.1a and later are interoperable with MicroStrategy Mobile Server version and later. However, full feature support is unavailable in any scenario where the client and server are on different versions. To ensure full feature support, upgrade both MicroStrategy Mobile client and server systems to the latest version. All pre-9.0 MicroStrategy products must be uninstalled prior to upgrading to MicroStrategy 9.2.1m. However, you can upgrade directly from 9.0.x or 9.2.x to 9.2.1m without uninstalling the previous version of MicroStrategy. For more information about the upgrade process, see The upgrade process checklist, page 5. After updating your MicroStrategy system, you have a grace period of 30 calendar days to activate your installation. If you do not complete the activation before the grace period expires, your MicroStrategy product stops functioning until you activate it. For more information about MicroStrategy activation, see the MicroStrategy Installation and Configuration Guide and installation online help. For information about License Manager, see the License Manager Help (from within License Manager, press F1). Due to performance improvements and enhancements, MicroStrategy version 9 may require more memory than version 8 for comparable functionality. In particular, if your MicroStrategy 8.x system is running on Windows and is approaching the 3 GB Windows memory limit, you 2 Impact of the upgrade 2011 MicroStrategy, Inc.

31 Upgrade Guide Impact of the Upgrade and Upgrade Checklist 1 may need to upgrade your Intelligence Server machines. For more information on MicroStrategy memory recommendations, see the system requirements in the MicroStrategy readme and the Tuning chapter in the System Administration Guide. When the project metadata is upgraded, all preferences stored in the metadata are migrated to the new version as well. In particular, the user preferences for Desktop and MicroStrategy Web are migrated. Images from the MicroStrategy Photo Uploader widget for MicroStrategy Mobile are stored in the /SavedImages directory in the MicroStrategy Web or Web Universal installation. This directory may be overwritten when you upgrade MicroStrategy Web or Web Universal. Make sure you back up this directory before upgrading MicroStrategy Web or Web Universal. New features and workflow changes For a complete list of new products, new features, and updates in MicroStrategy 9.2.1m, see the MicroStrategy Tech Note New Features in MicroStrategy 9.2.1m. If you are not upgrading from version 9.2.1m, you may wish to consult the New Features MicroStrategy Tech Note for all intervening releases as well. The default options for VLDB settings may change between releases. You can determine what VLDB default settings have changed by creating a VLDB settings report for your database type before the upgrade, and comparing it to a VLDB settings report created after the upgrade. For instructions on how to create a default VLDB settings report, see the section on Default VLDB settings for specific data sources in the Supplemental Reference for System Administration. Some of the new features of MicroStrategy 9.2.1m that may affect your users workflow include: MicroStrategy Mobile for Android now applies new configurations when the MicroStrategy app is restarted, without having to reset the device. As an alternative to using BlackBerry Enterprise Server (BES) to configure mobile devices, you can now create Mobile configurations for BlackBerry devices through the Mobile Server Administrator page, generate URLs for the configurations, and those URLs to BlackBerry users to configure their mobile devices. For detailed instructions on using Mobile Server Administrator to create configurations for MicroStrategy Mobile for BlackBerry, see the 2011 MicroStrategy, Inc. Impact of the upgrade 3

32 1 Impact of the Upgrade and Upgrade Checklist Upgrade Guide MicroStrategy Mobile Design and Administration Guide, or see the Mobile Server Administrator Help. Some of the new features of MicroStrategy 9.2.1a that may affect your users workflow include: Android devices are now supported for use with MicroStrategy Mobile. When creating a new analysis using Visual Insight, users are now presented with a choice of visualizations. To change the type of a visualization (for example, to change a Heat Map to a Grid), users now click Change Visualization in the analysis toolbar and select a visualization from the dialog box. Some of the new features of MicroStrategy that may affect your users workflow include: Project metadata must be updated using Configuration Wizard. Updating the project metadata through Desktop is no longer supported. Modifying a Heat Map widget now requires the Web Edit Grid/Graph privilege in the Web Professional privilege group. In the New Grid dialog box for creating a report or Intelligent Cube, the ODBC Sources tab has been renamed to the Freeform Sources tab. On this tab, the following options have changed: Use Query Builder Editor has been renamed to Create Query Builder Report. Use Freeform SQL Editor has been split into Create Freeform SQL Report and Create Freeform XQuery Report. The function parameter IsInputSignificant is now called UseLookupForAttributes. This parameter is primarily used with the Count function. Some of the new features of MicroStrategy 9.2 that may affect your users workflow include: If you are using a response file to upgrade your projects through the Configuration Wizard, and you are upgrading multiple projects, the list of projects should be separated by backslashes \ instead of commas. If you are using projects in multiple languages, be aware that the hierarchy for language fallback has changed. The project default language now takes priority over the Intelligence Server machine s language. For 4 Impact of the upgrade 2011 MicroStrategy, Inc.

33 Upgrade Guide Impact of the Upgrade and Upgrade Checklist 1 details, see the Internationalization chapter in the Supplemental Reference for System Administration. The Use Translation Editor privilege no longer allows users to make changes to an object s name or description unless they have Write access to the object. The new Use Translation Editor Bypass privilege (found in the Desktop Designer privilege group) allows users to make changes to any object s name or description through the Translation Editor. This behavior was previously allowed with the Use Translation Editor privilege. In MicroStrategy Web, the user interface for importing data from a spreadsheet or Intelligent Cube has been updated for improved usability. For detailed information on this new interface, see the MicroStrategy Web Help. In MicroStrategy Web, in the Properties And Formatting dialog box, the option formerly called Enable horizontal swipe to change panels option for panel stacks is now called Allow current panel to be changed without selector, and is located in the General options. The MicroStrategy Web Services Administration Guide is deprecated beginning with MicroStrategy 9.2. Information formerly contained in this book can be found in the MicroStrategy Office Users Guide. The upgrade process checklist The upgrade process described in the rest of this guide involves the following high-level steps. To help ensure a successful upgrade, follow these steps in the order they are presented in this guide. 1 Prepare MicroStrategy system and projects for upgrade Preparing a MicroStrategy system for an upgrade involves reviewing information specific to your version upgrade, pre-upgrade information and prerequisites, checking for supported warehouse data types, backing up the production metadata, understanding how to successfully migrate your customizations, and uninstalling existing MicroStrategy applications. This is covered in this chapter and Chapter 2, Preparing for the Upgrade MicroStrategy, Inc. The upgrade process checklist 5

34 1 Impact of the Upgrade and Upgrade Checklist Upgrade Guide 2 Install and configure Intelligence Server and Desktop 9.2.1m on a test server In this step, you install and configure MicroStrategy Intelligence Server 9.2.1m and MicroStrategy Desktop 9.2.1m on a test server and then establish a connection to your production metadata. This is covered in Install and configure the latest version of MicroStrategy Intelligence Server and Desktop on a test server, page 19 in Chapter 3, Upgrading MicroStrategy on Windows, UNIX, or Linux. 3 Update the production metadata In this step, you update the metadata version of your production projects using the test server environment. This is covered in Update the production metadata, page 20 in Chapter 3, Upgrading MicroStrategy on Windows, UNIX, or Linux. 4 Perform basic stability testing In this step, you perform basic testing to ensure the stability and efficiency of Intelligence Server and your updated projects. This is covered in Perform basic stability testing, page 27 in Chapter 3, Upgrading MicroStrategy on Windows, UNIX, or Linux. 5 Install and configure Intelligence Server in the production environment Once you are satisfied with the status of the latest version of Intelligence Server, and have updated the projects in your test environment, you install Intelligence Server in the production environment. This is covered in Install and configure the latest version of Intelligence Server in the production environment, page 28 in Chapter 3, Upgrading MicroStrategy on Windows, UNIX, or Linux. 6 Install remaining MicroStrategy products in the production environment With the latest version of Intelligence Server installed in your production environment, you now install and configure the remaining MicroStrategy products in your production environment. This is covered in Install remaining MicroStrategy products in the production environment, page 28 in Chapter 3, Upgrading MicroStrategy on Windows, UNIX, or Linux. 6 The upgrade process checklist 2011 MicroStrategy, Inc.

35 Upgrade Guide Impact of the Upgrade and Upgrade Checklist 1 7 Run tests simulating day-to-day system usage Before implementing your newly updated and configured MicroStrategy system, you perform system tests that simulate the kind of day-to-day usage you require. These tests can involve running reports and documents, checking report caches, and monitoring the status of Intelligence Server. This is covered in Run tests representing day-to-day usage, page 33 in Chapter 3, Upgrading MicroStrategy on Windows, UNIX, or Linux. 8 Perform post-upgrade tasks After upgrading to the latest version of MicroStrategy, you perform several post-upgrade tasks such as checking system licensing and functionality, managing user privileges, and optimizing your MicroStrategy system. This is covered in Chapter 4, After the Upgrade. Upgrade best practices Review the following recommendations to help ensure the success and stability of your MicroStrategy system and projects after upgrading to the latest version of MicroStrategy. Follow the upgrade order and recommendations outlined in this guide. Always upgrade Intelligence Server prior to upgrading client applications such as MicroStrategy Desktop and MicroStrategy Web. Do not downgrade MicroStrategy products or components on a machine to previous versions if you have already installed the most recent version of another MicroStrategy product on that machine. Do not install MicroStrategy 9.2.1m products on a machine on which older versions of MicroStrategy products reside. If you upgrade a MicroStrategy product on a machine you must upgrade all MicroStrategy products to the same version. Avoid installing MicroStrategy products using services such as Windows Terminal Services, which create a virtual session on the host machine. Always install MicroStrategy directly on the server machine s physical interface, or by using a remote connection tool (such as Microsoft Netmeeting or Virtual Private Network) that takes full control of the server machine s interface MicroStrategy, Inc. Upgrade best practices 7

36 1 Impact of the Upgrade and Upgrade Checklist Upgrade Guide Reference materials Some detailed information about installing and configuring MicroStrategy products is beyond the scope of this guide and can be found in the MicroStrategy Installation and Configuration Guide. The MicroStrategy Installation and Configuration Guide provides detailed procedures on installing and configuring your MicroStrategy system. It also includes important information about installing, deploying, and configuring MicroStrategy Universal products. Refer to the MicroStrategy Installation and Configuration Guide if you require additional information about installing and configuring your MicroStrategy system. In addition, the MicroStrategy Readme contains information about the new products, new features, and bug fixes available in MicroStrategy 9.2.1m. 8 Reference materials 2011 MicroStrategy, Inc.

37 2 2.PREPARING FOR THE UPGRADE Introduction Taking the time to prepare your MicroStrategy system for an upgrade to the latest version of MicroStrategy helps ensure both the success of the upgrade and the safe migration of your MicroStrategy projects. This chapter provides information about important upgrade prerequisites and the necessary steps you must take before upgrading your MicroStrategy system. Reviewing upgrade prerequisites, page 10 Checking for supported data types, page 11 Backing up the metadata, page 11 Upgrading in a clustered environment, page 13 Upgrading Web customizations, page 13 Depending on the type of upgrade you are performing, upgrading to MicroStrategy 9.2.1m can have a significant effect on your current Web customizations. The MicroStrategy SDK is a valuable resource that provides information about customizations and how to upgrade these customizations in your MicroStrategy environment. If you do 2011 MicroStrategy, Inc. 9

38 2 Preparing for the Upgrade Upgrade Guide not currently own a MicroStrategy SDK license, contact your Account Executive. Reviewing upgrade prerequisites Before upgrading your MicroStrategy system, review the MicroStrategy Readme so that you are aware of any changes from previous release. You should also review the system prerequisites outlined in the Planning Your Installation chapter of the MicroStrategy Installation and Configuration Guide. If you do not review the MicroStrategy hardware and software requirements before upgrading, you may experience problems with the upgrade. Database and driver requirements Refer to Certified and Supported Configurations in the MicroStrategy General Information Readme for updated information about specific database and driver combinations certified by MicroStrategy. System sizing guidelines There are several factors to consider when you initially set up your MicroStrategy system. These factors include the number of users that will access the system, report complexity, and whether or not you should employ caches. You should periodically re-evaluate your system and update it based on actual system performance and use. In particular, before updating your metadata (see Update the production metadata, page 20), MicroStrategy recommends that you have an amount of free disk space equal to at least twice the on-disk size of the metadata database. A complete discussion of system sizing guidelines is beyond the scope of this guide. Refer to the Planning Your Installation chapter of the MicroStrategy Installation and Configuration Guide for the latest details about sizing your system. 10 Reviewing upgrade prerequisites 2011 MicroStrategy, Inc.

39 Upgrade Guide Preparing for the Upgrade 2 Privileges and access Before upgrading, ensure you have the following: If you are installing on a Windows system, you must have a login account with administrative privileges for the domain or target machine. MicroStrategy Intelligence Server installation files. You can access the installation files from a disk or from a network location. Write permissions in the installation directory; otherwise the installation/upgrade process fails. If you have purchased a CPU-based MicroStrategy license and are installing on UNIX or Linux, you need root access permissions for installation. A license key from MicroStrategy for the version of the MicroStrategy software that you are installing. Checking for supported data types MicroStrategy 9.2.1m supports a wide variety of data types for each supported warehouse database. However, some pre-9.2.1m projects may contain data types not supported in MicroStrategy 9.2.1m. If a project containing columns with unsupported data types is upgraded, the data types for those columns are assigned as reserved, and proper data types are not assigned in temporary tables. This affects report execution. Before proceeding with the upgrade, you must ensure that all data types assigned in the pre-9.2.1m project are supported in MicroStrategy 9.2.1m. See the MicroStrategy Project Design Guide for a listing of the supported data types for each database type and additional information about changing to supported data types. Backing up the metadata Although the MicroStrategy installation process itself does not affect your project s metadata, MicroStrategy recommends that you back up your metadata before any significant installation or upgrade. In most major 2011 MicroStrategy, Inc. Checking for supported data types 11

40 2 Preparing for the Upgrade Upgrade Guide MicroStrategy upgrades, a metadata update is required for all the pre-existing projects in your metadata. Once you update your metadata project, you cannot revert that metadata to a previous version. Therefore, MicroStrategy strongly recommends that you perform a full database backup of your original metadata prior to the upgrade. Note the following: MicroStrategy strongly recommends that you also tape backup, image, or ghost the production server before upgrading. If you are upgrading your Distribution Services installation, you may need to change the database character set. Since any change in the database character set also affects the other contents of the database, backing up the database is recommended before changing the character set during the upgrade process. If you want to keep an old MicroStrategy Tutorial metadata repository and warehouse from a previous MicroStrategy version, rename the Microsoft Access files or move them to another location; otherwise, they are overwritten during the installation process. The Access files are installed by default in the MicroStrategy\Tutorial Reporting folder. Metadata compatibility The following applies to upgrading and downgrading metadata and provides information about which metadata versions are supported in MicroStrategy Desktop 9.2.1m. Updating project metadata Beginning with version 9.2.1, MicroStrategy requires that you use the Configuration Wizard to update a metadata project created in a pre version of MicroStrategy to the latest version. Be aware of the following: If you are upgrading a MicroStrategy 8.x metadata that is stored in a DB2 UDB for z/os database, refer to MicroStrategy Tech Note TN For assistance with updating MicroStrategy metadata projects from versions prior to MicroStrategy version 8.1.0, contact MicroStrategy Technical Support. 12 Backing up the metadata 2011 MicroStrategy, Inc.

41 Upgrade Guide Preparing for the Upgrade 2 MicroStrategy requires that you update projects through an Intelligence Server connection (3-tier). Upgrading your project using a direct ODBC connection (2-tier connection) is not supported. If you do not upgrade the metadata to the latest version, certain features will not work as expected. For example, if MicroStrategy Web 9.2.1m connects to a pre-9.2.1m metadata through a 9.2.1m server, Change Journaling, Distribution Services, and some Report Services enhancements may not be available. Downgrading metadata projects Downgrading a MicroStrategy metadata or project to any previous product version is not supported. Once you update the project metadata to the latest version, you cannot downgrade to earlier product versions. Therefore, backing up the metadata is an essential step in the upgrade process as it allows you to revert to a backup version of the metadata to obtain pre-update versions of the projects it contains. Upgrading in a clustered environment If you are using clustered Intelligence Servers, then to retain stability in your Intelligence Server cluster while upgrading, shut down Intelligence Server on all nodes in the cluster before proceeding with the upgrade. Every node in the MicroStrategy cluster must run the same version of MicroStrategy for the cluster to work properly. For more information about clustering Intelligence Servers, see the Clustering chapter in the System Administration Guide. Upgrading Web customizations The Customization Upgrade Wizard allows to upgrade customizations from a previous version of MicroStrategy Web to 9.2.1m. The Customization Upgrade Wizard upgrades your customizations to plug-ins that work with the plug-in architecture (the Plug-in_Architecture.htm file in the default MSDL directory) MicroStrategy, Inc. Upgrading in a clustered environment 13

42 2 Preparing for the Upgrade Upgrade Guide Where to find best practices and upgrade considerations Before using the Web Customization Upgrade Utility to initiate an upgrade to the latest version of MicroStrategy, you must prepare your new application to be upgraded. The MSDL includes information which can be helpful when upgrading your MicroStrategy Web customizations. The MSDL is provided with the MicroStrategy SDK. To purchase MicroStrategy SDK, contact your account executive for more information. To open the MicroStrategy Developer Library In Windows: From the Start menu, select Programs, then MicroStrategy, then SDK, and then Developer Library. In UNIX or Linux: Navigate to SDK/docs and open DeveloperLibrary.htm. Information on MicroStrategy Web customizations is within the Web SDK section of the MSDL. After reviewing this content, you are ready to upgrade your MicroStrategy Web customizations with the Web Customization Upgrade Utility. Refer to the MSDL for more information on using this utility. 14 Upgrading Web customizations 2011 MicroStrategy, Inc.

43 3 3.UPGRADING MICROSTRATEGY ON WINDOWS, UNIX, OR LINUX Introduction This chapter provides information about the steps you must take to successfully upgrade your MicroStrategy system in a Windows, UNIX, and Linux environment. Follow the prerequisite and pre-upgrade information in Chapter 1, Impact of the Upgrade and Upgrade Checklist and Chapter 2, Preparing for the Upgrade before proceeding in this chapter. This chapter has the following sections: Upgrading MicroStrategy on Windows, page 16 This section is broken up into the upgrade steps listed below. To help ensure a successful upgrade, follow these steps in order. Uninstall the previous version of MicroStrategy, page 16 Install and configure the latest version of MicroStrategy Intelligence Server and Desktop on a test server, page 19 Update the production metadata, page MicroStrategy, Inc. 15

44 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide Perform basic stability testing, page 27 Install and configure the latest version of Intelligence Server in the production environment, page 28 Install remaining MicroStrategy products in the production environment, page 28 Run tests representing day-to-day usage, page 33 Upgrading your Enterprise Manager environment, page 34 This step is only necessary if you have a pre-9.2.1m Enterprise Manager environment you intend to upgrade. Upgrading MicroStrategy on UNIX and Linux, page 43 Upgrading MicroStrategy on Windows This section provides installation and project update procedures to upgrade MicroStrategy in a Windows environment. Be aware of the following: While the installation process does not affect your project s metadata, MicroStrategy strongly recommends that you perform a full database backup of your production metadata in case you later need to restore a copy of your original metadata. Before upgrading to the latest version of MicroStrategy, see Backing up the metadata, page 11. If you use clustered Intelligence Servers in MicroStrategy, see Upgrading in a clustered environment, page 13 before proceeding with the upgrade. Uninstall the previous version of MicroStrategy MicroStrategy 9.2.1m is not interoperable with pre releases. That is, clients (such as MicroStrategy Web or Desktop) and servers (such as Intelligence Server or MicroStrategy Web Server) should be upgraded to MicroStrategy 9.2.1m. However, MicroStrategy 9.2.1m is interoperable with MicroStrategy 9.0.1, MicroStrategy 9.0.1m, MicroStrategy 9.0.2, MicroStrategy 9.2, MicroStrategy 9.2.1, and MicroStrategy 9.2.1a. In addition, you must upgrade both Intelligence Server and MicroStrategy Web 16 Upgrading MicroStrategy on Windows 2011 MicroStrategy, Inc.

45 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 to version 9.2.1m to ensure the successful execution of Report Services documents in Flash Mode. MicroStrategy Mobile clients from version 9.2.1a and later are interoperable with MicroStrategy Mobile Server version and later. However, full feature support is unavailable in any scenario where the client and server are on different versions. To ensure full feature support, upgrade both MicroStrategy Mobile client and server systems to the latest version. When you begin your upgrade by running the MicroStrategy Installation Wizard (included on the MicroStrategy installation disk, and also available on the MicroStrategy download site), the following dialog box opens: There are two different ways to uninstall the previous MicroStrategy components from your machine. Selecting Yes generates a batch file that is used to remove the files. Selecting No allows you to remove existing files using Add/Remove Programs. To uninstall previous MicroStrategy components using the batch file 1 Start the MicroStrategy Installation Wizard. For details about the MicroStrategy Installation Wizard, see the MicroStrategy Installation and Configuration Guide MicroStrategy, Inc. Upgrading MicroStrategy on Windows 17

46 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide 2 Select Yes in the Question dialog box. The following is displayed in the MicroStrategy Installation Wizard: 3 Note the folder location given. Click OK. The MicroStrategy Installation Wizard closes. 4 Browse to MSTR_UnInst.bat, in the location specified, and double-click it. 5 Follow the steps displayed to uninstall the previous version of MicroStrategy. 6 When the uninstallation is complete, reboot your machine before continuing with the upgrade process. To uninstall previous MicroStrategy components using Add/Remove Programs The third-party products discussed below are manufactured by vendors independent of MicroStrategy, and the information provided is subject to change. Refer to the appropriate third-party vendor documentation for updated information about Microsoft Windows. 1 Start the MicroStrategy Installation Wizard. For details about the MicroStrategy Installation Wizard, see the MicroStrategy Installation and Configuration Guide. 18 Upgrading MicroStrategy on Windows 2011 MicroStrategy, Inc.

47 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 2 Select No in the Question dialog box. The following is displayed in the MicroStrategy Installation Wizard: 3 Click OK. The MicroStrategy Installation Wizard closes. 4 From your Start menu, point to Settings, and select Control Panel. The Control Panel opens. 5 Select Add or Remove Programs. The Add or Remove Programs window opens. 6 Select MicroStrategy and click Remove. 7 Follow the on-screen instructions to remove the MicroStrategy components from your computer. Install and configure the latest version of MicroStrategy Intelligence Server and Desktop on a test server Once you review the prerequisite and pre-upgrade information in Chapter 2, Preparing for the Upgrade and back up your production metadata projects, install and configure the latest version of Intelligence Server and Desktop on a test server. Once the products are installed on a test server, establish a metadata connection to the production metadata. The following sections expand upon these steps. Install and configure Intelligence Server and Desktop Follow the detailed procedures in the Installing MicroStrategy on Windows chapter of the MicroStrategy Installation and Configuration Guide to learn how to install and configure MicroStrategy Intelligence Server and MicroStrategy Desktop MicroStrategy, Inc. Upgrading MicroStrategy on Windows 19

48 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide As part of the configuration process, you configure the Intelligence Server, establish a server definition, and create a project source. See the next section for more details. When you install products using the MicroStrategy Installation Wizard, a Server Activation screen prompts you to activate your installation. For more information about software activation, see the Managing Your Licenses chapter System Administration Guide. Establish a connection to the production metadata After the installation, establish a metadata connection between Desktop and the production metadata, which you previously backed up. Follow the configuration instructions in the MicroStrategy Installation and Configuration Guide. Once you have installed and configured MicroStrategy Intelligence Server and MicroStrategy Desktop, return to this guide for instructions and information on the next steps in the upgrade procedure. For information about viewing the Configuration Wizard log file in the event of an error, see Troubleshooting the upgrade, page 70. Update the production metadata After installing the latest versions of MicroStrategy Intelligence Server and Desktop on a test server, update the metadata version of your production projects by performing the procedure that follows. This procedure creates and updates metadata tables to support new features available in MicroStrategy 9.2.1m. Updating the metadata helps ensure compatibility between your pre-existing reports and documents and the MicroStrategy clients. You can also take advantage of new configuration settings exposed through the client applications, functionality, and objects available only with the updated version of metadata. MicroStrategy does not support connecting 9.2.1m components to a pre-9.2.1m metadata. 20 Upgrading MicroStrategy on Windows 2011 MicroStrategy, Inc.

49 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 The specific changes that are made to the metadata during the update process depend on several factors, such as: The version of MicroStrategy that you are updating from The type of database that you use to store the metadata You can see what kind of changes are made to the metadata database by viewing the metadata update SQL script for your database. The metadata update scripts are stored in the MicroStrategy Common Files folder. By default this folder is located in C:\Program Files\Common Files\MicroStrategy. The scripts are named in the form mdrdbms.sql where RDBMS indicates the type of database. For example, the script to update an Oracle database is mdorcl.sql. MicroStrategy does not recommend or support making any changes to these scripts unless specifically directed to do so by MicroStrategy support technicians. Altering these update scripts may void your warranty. The metadata upgrade scripts contain the SQL necessary to create a new metadata, or to update the metadata from any supported version. Comments within the scripts indicate where the script should begin executing for each version, as follows: If you are updating from a pre-9.0 metadata, the update begins executing the script at the line If you are updating from a metadata, the update begins executing the script at the line If you are updating from a or 9.0.1m metadata, the update begins executing the script at the line If you are updating from a metadata, the update begins executing the script at the line For example, if you are updating to 9.2.1m from 9.0.0, the update begins executing the script at the line and executes the rest of the script, including the section following the line During the metadata update process, the Configuration Wizard generates additional SQL for tasks such as managing indexes and primary keys. To view this SQL during the update process, on the Summary Page of the Configuration Wizard, in the Summary pane, click SQL Preview. In addition, once you have completed the update process, the generated SQL is saved in the MicroStrategy common files directory. The file name is OriginalScript_generated.sql, where OriginalScript is the 2011 MicroStrategy, Inc. Upgrading MicroStrategy on Windows 21

50 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide name of the original SQL update script. For example, if you are updating an Oracle database, the original SQL update script is mdorcl.sql and the generated SQL file is mdorcl_generated.sql. Prerequisites for updating a MicroStrategy metadata Before attempting to update your MicroStrategy metadata to the latest version, make sure you meet the following prerequisites: The metadata update process can only be executed by a MicroStrategy user who is either a member of the System Administrators user group, or is the out-of-the-box Administrator user. Having all administrative privileges is not sufficient: the user must be a member of the System Administrators user group. The project s metadata version from which you update must be older than, or the same as, the version of the product (for example, Desktop and Intelligence Server) that is performing the metadata update. An older version of the product is not able to perform an update on a newer version of metadata. The language settings of the client, project, and Intelligence Server must all be the same. The metadata configuration must be valid, meaning that at least the root folder for the configuration section exists. The projects to be updated must be valid, meaning that at least the root project folder, schema object, system dimension, and the system function package definition exist. The projects to be updated must not be locked. To unlock a project s metadata, in Desktop, from the Administration menu, point to Locking and select Unlock Project. Database-specific prerequisites The following prerequisites are specific to the RDBMS that your project metadata is stored in. If you are using Oracle for your metadata database, make sure that the Maximum Open Cursors parameter for the database is set to at least If you are using DB2 for your metadata database, make sure that the Dynamic Sections property for the database is set to Upgrading MicroStrategy on Windows 2011 MicroStrategy, Inc.

51 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 If you are upgrading a MicroStrategy 8.x metadata that is stored in a DB2 UDB for z/os database, refer to MicroStrategy Tech Note TN If you are using a Microsoft Access database to store your metadata and you are upgrading from a pre-9.0 version of MicroStrategy, additional steps are required before you update your metadata. For details, refer to MicroStrategy Tech Note TN Metadata update process You can update various parts of the metadata for multiple projects at once using the Configuration Wizard. This method also allows you to make updates to configuration objects. Only projects that are loaded on Intelligence Server can be upgraded. To upgrade an unloaded project, first load the project on Intelligence Server, then perform the upgrade, then unload the project. By updating the metadata through the Configuration Wizard, you can update either the system objects, the privileges, or both. By making updates to the metadata for multiple individual projects at once, you can select different projects and choose whether to update the system objects, schedules, MDX source related objects, or any combination of these. For more details about these updates, see the procedure below. Note the following: As an alternative to stepping through each page of the Configuration Wizard for each project source that needs to be updated, you can create a response file with the update information, and use that response file with the Configuration Wizard to automatically update your metadata. For more information about using a response file to update the metadata, see Using a response file with Configuration Wizard, page 48. For information about viewing the Configuration Wizard log file in the event of an error, see Troubleshooting the upgrade, page 70. The MDUpdateUtil.exe command line utility that was formerly used to update the metadata is now deprecated. To update the metadata from the command line, you can use a response file with Configuration Wizard MicroStrategy, Inc. Upgrading MicroStrategy on Windows 23

52 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide To make metadata updates using the Configuration Wizard If you attempt to update a project through the Configuration Wizard and the update fails, the project is locked. You must unlock the project before you attempt to upgrade the project again. To unlock a project, in Desktop, from the Administration menu, point to Locking, and select Unlock Project. 1 From the Start menu, point to Program Files, then MicroStrategy, then select Configuration Wizard. The Configuration Wizard opens. 2 Select the Upgrade existing environment to MicroStrategy 9 option, and then select the Intelligence Server components option. Then click Next. 3 On the MicroStrategy Authentication page, type the username and password of a MicroStrategy system administrator. Then click Next. 4 On the Select Components page, select the check boxes for each Intelligence Server you want to upgrade. 5 Under each selected Intelligence Server, select the system components you want to upgrade: Upgrade metadata repository: The metadata repository contains the definitions of your MicroStrategy applications and supporting objects. An upgrade of your metadata is required to provide support for all new and updated features in the most recent version of MicroStrategy. Be aware of the following: If this upgrade has already been completed, this option is named Re-execute metadata repository upgrade. This update overwrites any changes you may have made to the out of the box MicroStrategy user groups and security roles. Upgrade administration privileges: In MicroStrategy 9.0, several new privileges were added, so certain user tasks that previously required one privilege may require several. Updating the privileges ensures that users with administrative privileges have access to the same functionality that they had in previous versions of MicroStrategy. By default, privileges are upgraded based on the version of your MicroStrategy metadata. However, if you previously upgraded 24 Upgrading MicroStrategy on Windows 2011 MicroStrategy, Inc.

53 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 your MicroStrategy metadata and did not upgrade privileges along with the metadata upgrade, you must identify the MicroStrategy version you most recently upgraded your privileges for. To do this, to the right of Update privileges, click Advanced. A Configuration Wizard dialog box opens. The version of your MicroStrategy metadata is selected by default. From the drop-down list, select the version of MicroStrategy that privileges were most recently upgraded for. Migrate History List messages from a flat file into a database: Beginning with MicroStrategy 9.0 you can store the History List repository in a database, instead of using a file-based method. This allows administrators to centrally monitor all History List messages across the system. If you select this check box, additional configuration options for this migration are provided later in these upgrade and migration steps. If you are already using a database-based History List, then for information about upgrading the History List database, see Upgrade the History List database, page Select each project you want to update. Only projects that are currently loaded on Intelligence Server can be updated. Project updates can include any or all of the following options: Execute project logical upgrade: Updates the project to the most recent version of MicroStrategy. This option also updates the report and document definitions to improve the performance and reduce the memory usage and storage requirements of reports and documents that were created with a previous version of MicroStrategy. Be aware of the following: If this update has already been completed, this option is named Re-execute project logical upgrade. This upgrade is required to execute any additional project upgrade options. Updated Report Services documents cannot be run in previous versions of MicroStrategy. Depending upon the number of reports and documents in the project, this update may take a significant amount of time. Update Schedules: Makes previous subscriptions viewable in MicroStrategy 9.2.1m MicroStrategy, Inc. Upgrading MicroStrategy on Windows 25

54 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide Update MDX Source Objects: Updates the MDX data source objects (MDX Cubes) that were created in earlier versions of MicroStrategy to take advantage of improved performance. Depending upon the number of MDX source objects in the project, this update may take a significant amount of time. By 7 Click Next. default, if you update multiple projects and the update fails for one project, the update process continues for other projects. This allows you to complete all possible updates and then review any errors. To abort the update process for other projects when one project fails, clear the Update the remaining projects, even when one project update fails check box. 8 On the Metadata Connection page, type the DSN, database login, and database password to access the MicroStrategy metadata. Then click Next. If you are using a DB2 Z/OS database on a UNIX/Linux system, you must also type the table space name and database name for the metadata repository. 9 If you selected the Migrate History List messages from a flat file into a database option, then on the History List Target Database page, specify the login information and database options for the History List database. Then click Next. 10 On the Summary page, review your upgrade choices and click Update to update the metadata. Upgrade the History List database Beginning with MicroStrategy 9.0, you can store the History List repository in a database, instead of using a file-based method. If you are currently using a database-based History List, when upgrading to MicroStrategy 9.2.1m you must upgrade the History List database tables. MicroStrategy recommends using the Configuration Wizard to upgrade the History List repository. To upgrade the History List repository 1 From the Start menu, point to Program Files, then MicroStrategy, then select Configuration Wizard. The Configuration Wizard opens. 26 Upgrading MicroStrategy on Windows 2011 MicroStrategy, Inc.

55 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 2 Select Upgrade History List Repositories and click Next. The Upgrade History List Tables page opens. 3 On the Upgrade History List Tables page, select the DSN for the History List database, and specify the login information. 4 To upgrade existing History List messages to the current format, select the Copy History List content check box. If you clear this check box, History List messages are not upgraded, and only the new tables required to support History List messages are created. 5 If you select to upgrade your History List messages, you can also select the Compress data check box to compress all existing History List messages. This compression can improve the performance of using History List messages. However, the compression of your History List messages can require significant system resources. To avoid the overhead of compressing your existing History List messages, clear the Compress data check box. Existing History List messages are not modified, but any newly created History List messages are created with the new compressed format. 6 Click Next. The Summary page opens. 7 On the Summary page, review the available information, and click Finish. The History List repository is upgraded. Perform basic stability testing The test server environment that you created in the preceding steps allows you to closely monitor the interaction between Intelligence Server and your recently updated production metadata. With Intelligence Server and Desktop upgraded to the latest version and connected to the updated production metadata, perform some basic testing to ensure the stability and efficiency of Intelligence Server. During the test, ensure you are satisfied with the status and efficiency of the Intelligence Server. If you require assistance, refer to the MicroStrategy Readme or contact MicroStrategy Technical Support MicroStrategy, Inc. Upgrading MicroStrategy on Windows 27

56 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide Install and configure the latest version of Intelligence Server in the production environment Once you are completely satisfied with the status of Intelligence Server and the updated projects, install the latest version of Intelligence Server on the production servers. Install remaining MicroStrategy products in the production environment Now that the production Intelligence Servers are installed, begin upgrading any remaining MicroStrategy products to the latest version. Follow the installation procedures provided in the MicroStrategy Installation and Configuration Guide to install these remaining products. Recommended upgrade order for upgrading separate machines It is recommended you follow a specific product upgrade sequence when upgrading MicroStrategy products across several machines. Following this upgrade sequence helps ensure that MicroStrategy products installed on separate machines are interoperable, that is, they are able to work together when installed on separate machines. The recommended upgrade sequence is as follows: 1 Metadata, Intelligence Server, Web Server, and Mobile Server. If you followed the preceding instructions, your production environment now contains an updated version of the project metadata and Intelligence Servers. Continue the recommended upgrade order by installing MicroStrategy Web Servers and Mobile Servers. Before installing MicroStrategy Web, note your current Web customizations and review the information in Upgrading Web customizations, page 13 to learn how to successfully migrate these customizations. 28 Upgrading MicroStrategy on Windows 2011 MicroStrategy, Inc.

57 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 2 Office, and migrate Web delivery subscriptions from Narrowcast Server to Distribution Services. MicroStrategy Office users may be prompted to upgrade their version of MicroStrategy Office if a newer version exists on the Web Services machine. For more information, see Upgrading MicroStrategy Office automatically through MicroStrategy Web Services, page Desktop, Mobile clients, and administrator products such as Enterprise Manager, Command Manager, and Object Manager. Note the following: Before you upgrade your Enterprise Manager environment, see Upgrading your Enterprise Manager environment, page 34 for important upgrade considerations and procedures. Before you upgrade the MicroStrategy Mobile for BlackBerry client on mobile devices, see Upgrading MicroStrategy Mobile for BlackBerry, page 30 for important upgrade considerations and procedures. Preserving MicroStrategy Mobile configurations when upgrading MicroStrategy Mobile Server Beginning with MicroStrategy 9.0.1m, MicroStrategy Web and Mobile use separate web server applications to deliver MicroStrategy reports and documents. The web server application for MicroStrategy Mobile is called MicroStrategy Mobile Server. The name of the application file for Mobile Server is microstrategymobile.war. Upgrading Mobile Server is similar to upgrading MicroStrategy Web. However, if you have created any mobile device configurations, those configurations are deleted during the upgrade unless you manually back them up before the upgrade and restore them after the upgrade. To back up your configuration files, make a copy of the directory <MicroStrategyMobileServer>/WEB-INF/xml/mobile/ and all its contents, where <MicroStrategyMobileServer> is the installation location of MicroStrategy Mobile Server. By default, this location is C:\Program Files\MicroStrategy\Mobile Server ASPx or \Mobile Server JSP. Then, after you have upgraded Mobile Server, copy 2011 MicroStrategy, Inc. Upgrading MicroStrategy on Windows 29

58 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide the contents of the backed-up directory to the same corresponding location in the new Mobile Server deployment. Upgrading MicroStrategy Office automatically through MicroStrategy Web Services If you are a MicroStrategy Office user, you may be prompted to upgrade MicroStrategy Office after you log into a MicroStrategy project using the MicroStrategy Office toolbar or menu in Microsoft Excel, PowerPoint, or Word. When you use MicroStrategy Office to log in to a project, your version of MicroStrategy Office is checked to see if it is as recent as the version on the Web Services machine. If the Web Services machine contains a more recent version of MicroStrategy Office, you are asked if you want to upgrade your version of MicroStrategy Office. If you choose to upgrade, MicroStrategy Office launches the MicroStrategy Office installation program on your machine. Follow the steps in the installation wizard to install the latest version of MicroStrategy Office. Be aware of the following: If you have Excel workbooks that contain Flash reports generated using Office 8.1.0, an exception may occur the first time the workbook is refreshed and saved. However, once you save the workbook and close Excel, the workbook can be refreshed without exceptions or problems. If the MicroStrategy Office client is connected to a 9.2.1m Intelligence Server that is connected to a non-upgraded metadata, new features such as Change Journaling and Distribution Services may be unavailable. Upgrading MicroStrategy Mobile for BlackBerry There are two ways to upgrade the MicroStrategy Mobile for BlackBerry application. The software can either be installed from a website on each device individually, or it can be installed on all of the devices simultaneously if you have administrator access to your company s BlackBerry Enterprise Server. The procedure below describes the basic steps to use files posted from a website to upgrade the MicroStrategy Mobile client. For a more detailed procedure, refer to the section Installing the client from a website in the 30 Upgrading MicroStrategy on Windows 2011 MicroStrategy, Inc.

59 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 Administering MicroStrategy Mobile chapter of the MicroStrategy Mobile Design and Administration Guide. High-level steps to upgrade the BlackBerry application from a website 1 Change any software configuration from the BlackBerry Enterprise Server assigned to the device to none. 2 Change the existing IT policy on the device to default. 3 Access the web page that contains the new client files. 4 Confirm that the version of MicroStrategy Mobile that is on the website is the most recent version of the software. 5 Download the files to the device. If you have administrator access to your company s BlackBerry Enterprise Server, you can use it to update MicroStrategy Mobile on all mobile devices it connects to. Distributing the client to users by means of the BlackBerry Enterprise Server takes between three and four hours. Because the BlackBerry Enterprise Server network drive can only contain a single version of each application at a time, the old versions of MicroStrategy Mobile must be deleted and replaced with the new ones. The procedure below provides high-level steps for this upgrade process. For detailed instructions on how to deploy an application using the BlackBerry Enterprise Server, see the documentation provided with the BlackBerry Enterprise Server. High-level steps to upgrade MicroStrategy Mobile for BlackBerry on multiple devices simultaneously 1 Overwrite the previous.alx and.cod files in the MicroStrategy Mobile folder with the new files. 2 Open a command window and enter, C:\ Program Files\Research In Motion\Apploader 3 In the command line, type loader.exe /reindex, and press Enter. This updates the specification.pkg and PkgDBCache.xml files MicroStrategy, Inc. Upgrading MicroStrategy on Windows 31

60 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide Migrate Web delivery subscriptions from Narrowcast Server to Distribution Services Beginning with version 9.0, MicroStrategy Distribution Services replaced MicroStrategy Narrowcast Server as the application that delivers Web delivery subscriptions. When you migrate all information related to Web delivery subscriptions from your existing MicroStrategy Narrowcast Server to Distribution Services, you can select to migrate Narrowcast Server users and their addresses. These users are copied as contacts who will receive the subscriptions in Distribution Services. During the upgrade process, only user addresses are migrated; subscriptions and schedules will not be migrated. MicroStrategy recommends that you back up the database containing your Object Repository and Subscription Book Repository before migrating subscriptions. Do not back up the repositories using the Copy Repository tool in Narrowcast Server. Copy Repository assigns a new System ID to the resulting repositories, which breaks the link between Narrowcast Server and your existing MicroStrategy project. Making a database backup retains this link. You can migrate existing Narrowcast Server subscriptions to Distribution Services using the Configuration Wizard. As an alternative to stepping through each page of the Configuration Wizard, you can create a response file with the update information, and use that response file with the Configuration Wizard to automatically migrate your Narrowcast Server subscriptions. For more information about using a response file to migrate your subscriptions, see Using a response file with Configuration Wizard, page 48. To migrate Narrowcast Server subscriptions using the Configuration Wizard 1 From the Start menu, point to Program Files, then MicroStrategy, then select Configuration Wizard. The Configuration Wizard opens. 2 Select the Upgrade existing environment to MicroStrategy 9 option, and then select the Narrowcast Server Web Delivery Subscriptions option. Then click Next. 32 Upgrading MicroStrategy on Windows 2011 MicroStrategy, Inc.

61 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 3 Step through the wizard, providing all information required. For details about the information required on each page, click Help. 4 When you reach the Summary page, review your upgrade choices, and click Migrate to migrate your subscriptions. You can also migrate your subscriptions from within Desktop, with the Migrate Subscriptions for Web Deliveries wizard. To access the Migrate Subscriptions for Web Deliveries wizard, in Desktop, from the Tools menu, select Migrate Narrowcast Server Subscriptions for Web Deliveries. For detailed information about using the Migrate Subscriptions for Web Deliveries wizard, see the MicroStrategy Desktop Help. Run tests representing day-to-day usage It is essential that you fully test your new MicroStrategy system to see how it withstands the kind of typical day-to-day system usage your user community requires. This simulation allows you to test reports, documents, report caches, the stability of the Intelligence Server, and other functionalities that contribute to the efficiency of your MicroStrategy system. If the newly upgraded project is currently connected in 2-tier mode, switch to 3-tier mode. To do so, right-click the appropriate project source and select Modify Project Source. Select Server from the Connection mode drop-down menu, type the name of your Intelligence Server in the Server name field, and click OK. Using a previous version of Desktop with an upgraded version of Intelligence Server: If you did not upgrade MicroStrategy Desktop and are using an earlier version of Desktop to connect to Intelligence Server 9.2.1m, a warning message appears when you try to log in via 3-tier mode. The warning message informs you that you are trying to connect an older client (the older version of Desktop) to a newer server (Intelligence Server 9.2.1m). This warning message is governed by the Warn on connect when server version is newer than client version setting in the Desktop Preferences. If you plan to update MicroStrategy Desktop clients in the near future, keep this setting enabled. If you do not plan to upgrade Desktop, you can disable this setting so you are not prompted by the message in the future. However, keep in mind that using the same versions of clients and servers within the MicroStrategy platform results in more efficient and reliable system performance. While you can, in some 2011 MicroStrategy, Inc. Upgrading MicroStrategy on Windows 33

62 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide cases, connect an older client to a newer Intelligence Server, you cannot benefit from the enhancements a newer client offers. If you have specific questions about updating the clients and servers within your system, contact MicroStrategy Technical Support. During the test, make sure you are satisfied with the status and efficiency of your MicroStrategy system. If you require assistance, refer to the MicroStrategy Readme or contact MicroStrategy Technical Support. Upgrading your Enterprise Manager environment A MicroStrategy Enterprise Manager environment includes the statistics tables, the Enterprise Manager warehouse, the Enterprise Manager console, and the Enterprise Manager project metadata. Each part of this environment needs to be upgraded. For a list of the changes that were made to the statistics tables and the Enterprise Manager warehouse for version 9.0, see MicroStrategy Tech Note TN The statistics tables, warehouse, and console can be upgraded at the same time, using one of the approaches below: Complete Upgrade: All of the Intelligence Servers that are monitored by Enterprise Manager, as well as the Enterprise Manager statistics tables, warehouse, and console, are upgraded at the same time. For high-level steps to perform a complete upgrade to Enterprise Manager, see Complete upgrade of Enterprise Manager warehouse and statistics, page 36. Phased Upgrade: The Intelligence Servers are upgraded in phases, and both 8.x and 9.x Intelligence Servers must be maintained. MicroStrategy Intelligence Server 9.x can log statistics to statistics tables in 8.x and 9.x formats; Intelligence Server 8.x can only log statistics to statistics tables in 8.x formats. In this situation, the statistics tables, Enterprise Manager warehouse, and Enterprise Manager console should only be upgraded after all of the Intelligence Servers are upgraded. For high-level steps to perform a phased upgrade to Enterprise Manager, see Phased upgrade of Enterprise Manager warehouse and statistics, page Upgrading MicroStrategy on Windows 2011 MicroStrategy, Inc.

63 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 Updating the Enterprise Manager project metadata is a separate process. The project should be updated once you have upgraded the statistics and the data warehouse. For detailed steps to update the metadata, see Updating the Enterprise Manager project, page 39. When you install a newer version of MicroStrategy Enterprise Manager over your previous version, a dialog box notifies you that the Enterprise Manager project will be overwritten. The message only refers to the files EM_WH.mdb, EM_Proj_MD.mdb, and the *.sql files; the MicroStrategy Enterprise Manager warehouse and metadata databases are not affected by the upgrade. If you have made any changes to these files, make sure you have backed them up before you install the new version of Enterprise Manager. Upgrading the statistics tables MicroStrategy recommends using the Configuration Wizard to upgrade the Intelligence Server statistics tables. Manually upgrading the Intelligence Server statistics tables is a two-step process: DDL upgrade: This step is required when upgrading to MicroStrategy 9.2.1m. It involves adding the new statistics tables and new columns, and creating indexes to the statistics tables. This upgrade can be performed through the Configuration Wizard by selecting the Upgrade Statistics Repository option, or through the Enterprise Manager console when you first open the console after upgrading it to 9.2.1m. DML upgrade: This step is optional, but recommended because it enables reporting against statistics data that was collected before the upgrade. It involves running data manipulation scripts against the statistics tables, which populates the new columns with data that was collected in the 8.x format. If the DML upgrade is not performed, Enterprise Manager version 9.2.1m may not able to report on statistics collected under a previous version of Enterprise Manager. For detailed information about the statistics DML upgrade, including the scripts to run against your database, see MicroStrategy Tech Note TN MicroStrategy, Inc. Upgrading MicroStrategy on Windows 35

64 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide Upgrading the data warehouse Upgrading the Enterprise Manager data warehouse is a two-step process: DDL upgrade: This step is required when upgrading to MicroStrategy 9.2.1m. It involves adding the new data warehouse tables and new columns, so that the warehouse can load data from the upgraded statistics tables. This upgrade is performed using the Enterprise Manager console when you first open the console after upgrading it to 9.2.1m. DML upgrade: This step is optional, but recommended if you perform the DML upgrade to the statistics tables. It enables reporting against statistics data that was collected before the upgrade. It involves running data manipulation scripts against the statistics database, which populates the new columns with data that was collected in the 8.x format. If the DML upgrade is not performed, Enterprise Manager version 9.2.1m may not able to report on statistics collected under a previous version of Enterprise Manager. For detailed information about the warehouse DML upgrade, including the scripts to run against your database, see MicroStrategy Tech Note TN Complete upgrade of Enterprise Manager warehouse and statistics In a complete upgrade, you upgrade all Intelligence Servers, all projects, and Enterprise Manager to the latest version simultaneously. This is the simplest method of upgrading your MicroStrategy environment. High-level steps for a complete upgrade of Enterprise Manager 1 Close all user connections, to ensure that there is no session activity on the Intelligence Servers being monitored by Enterprise Manager. 2 Run an Enterprise Manager data load. Make sure the Close orphan sessions option is selected. This data load ensures that the statistics tables are completely up to date, and that all open Intelligence Server sessions are closed. If you do not run a data load before upgrading Enterprise Manager and the projects on the Intelligence Servers, you may lose access to some statistics data. 36 Upgrading MicroStrategy on Windows 2011 MicroStrategy, Inc.

65 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 3 Upgrade all the Intelligence Servers that are being monitored by Enterprise Manager to the latest version. 4 Update all projects on those Intelligence Servers to the latest version. 5 Shut down all Intelligence Servers that are being monitored by Enterprise Manager. 6 Upgrade the Enterprise Manager console to the latest version. 7 Back up the statistics database and the Enterprise Manager warehouse database. 8 Upgrade the statistics repository through Configuration Wizard. 9 Open the Enterprise Manager console. You are prompted to upgrade the Enterprise Manager Warehouse tables. Click Yes. 10 (Optional) Execute the appropriate DML script against the data warehouse. For download sites and instructions on using the script, see Upgrading the data warehouse, page Restart all the Intelligence Servers. 12 Run an Enterprise Manager data load. This data load populates the new Enterprise Manager warehouse tables. Phased upgrade of Enterprise Manager warehouse and statistics A phased upgrade refers to an environment containing several Intelligence Servers, some running version 8.x and some running version 9.2.1m. This occurs when users need to upgrade their MicroStrategy system in phases. For example, you may want to ensure that if there are any problems with the upgrade process, your system is still functional. In a phased environment, Enterprise Manager should not be upgraded to the latest version until after all monitored Intelligence Servers have been upgraded to the latest version. In addition, the projects on the upgraded Intelligence Servers should not be upgraded to the latest version until after Enterprise Manager has been upgraded to the latest version. Enterprise Manager version 8.x cannot load statistics logged by version 9.2.1m projects MicroStrategy, Inc. Upgrading MicroStrategy on Windows 37

66 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide High-level steps for a phased upgrade of Enterprise Manager This procedure assumes that you have two Intelligence Servers, S1 and S2. 1 Upgrade S1 to the latest version of MicroStrategy. Do not update the projects associated with this Intelligence Server. If the projects are updated, Enterprise Manager will no longer be able to load statistics for them. 2 Upgrade S2 to the latest version of MicroStrategy. Do not update the projects associated with this Intelligence Server. If the projects are updated, Enterprise Manager will no longer be able to load statistics for them. 3 Close all user connections, to ensure that there is no session activity on the Intelligence Servers being monitored by Enterprise Manager. 4 Run an Enterprise Manager data load. Make sure the Close orphan sessions option is selected. This data load ensures that the statistics tables are completely up to date, and that all open Intelligence Server sessions are closed. If you do not run a data load before upgrading Enterprise Manager and the projects on these Intelligence Servers, you may lose access to some statistics data. 5 Shut down all the Intelligence Servers that are being monitored by Enterprise Manager. 6 Upgrade the Enterprise Manager console to the latest version. 7 Back up the statistics database and the Enterprise Manager warehouse database. 8 Upgrade the statistics repository through Configuration Wizard. 9 Open the Enterprise Manager console. You are prompted to upgrade the Enterprise Manager Warehouse tables. Click Yes. 10 (Optional) Execute the appropriate DML script against the data warehouse. For download sites and instructions on using the script, see Upgrading the data warehouse, page Upgrading MicroStrategy on Windows 2011 MicroStrategy, Inc.

67 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 11 Restart both Intelligence Servers. 12 Update all projects on both Intelligence Servers to the latest version. For instructions on updating the Enterprise Manager project, see Updating the Enterprise Manager project, page Run an Enterprise Manager data load. This data load populates the new Enterprise Manager warehouse tables. Updating the Enterprise Manager project After you have upgraded your statistics database and Enterprise Manager data warehouse, and performed a data load, you must update the Enterprise Manager project metadata. This gives you access to the new reports and metrics included in Enterprise Manager 9.2.1m. There are three ways to update the Enterprise Manager metadata: If you have not made any modifications to the Enterprise Manager project, such as creating new reports or altering existing report definitions, you can replace the previous version of the Enterprise Manager project with the new version of the project in Enterprise Manager 9.2.1m. For more information and instructions, see Upgrading and replacing the Enterprise Manager project, page 40. If you want to keep using your customized Enterprise Manager reports or other objects, and do not require the enhanced reporting capabilities available in version 9.2.1m, you can simply update your Enterprise Manager project in the same way as all your other projects. For more information and instructions, see Updating an existing Enterprise Manager project, page 40. If you want to take advantage of the new reporting capabilities in MicroStrategy 9.2.1m, and want to keep using your custom Enterprise Manager objects, you can update your existing project, and then import the new reports and metrics from the version 9.2.1m project. For more information and instructions, see Including the new features in your custom Enterprise Manager environment, page 41. For more detailed information about the Enterprise Manager metadata upgrade process, see MicroStrategy Tech Note TN MicroStrategy, Inc. Upgrading MicroStrategy on Windows 39

68 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide Upgrading and replacing the Enterprise Manager project To replace your existing Enterprise Manager project with the version 9.2.1m project, install the new Enterprise Manager metadata in your metadata database, using the Enterprise Manager console and the Project Mover Wizard. If you do not perform the DML upgrade to the statistics tables and the data warehouse, Enterprise Manager cannot report on statistics collected prior to upgrading to version 9.2.1m. For more information about the DML upgrade, see Upgrading the statistics tables, page 35 and Upgrading the data warehouse, page 36. To upgrade and replace the Enterprise Manager project 1 From the Start menu, point to Programs, then MicroStrategy, then Administrator, then choose Enterprise Manager Console. The Enterprise Manager Console opens. 2 Select Initialize. 3 Read the Initialize Overview page. Be sure you know the Data Source Name for the Enterprise Manager metadata database before you continue. Click Next. 4 Read the Initialize Project page and click Transfer to import the project files. The Project Mover Wizard opens. 5 Step through the Project Mover Wizard, entering the information for your system where prompted. On the Select Your Source Files page, make sure you clear the Warehouse Source check box, so that the Enterprise Manager data warehouse is not transferred. 6 On the Summary page, review the information about the project transfer, and click Transfer when you are ready. The process can take several minutes. When the transfer process is complete, the Project Mover Wizard closes and you are returned to the Enterprise Manager Console. Updating an existing Enterprise Manager project If you want to keep your existing Enterprise Manager project, and do not need access to the new functionality available in version 9.2.1m, you can 40 Upgrading MicroStrategy on Windows 2011 MicroStrategy, Inc.

69 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 update your existing metadata in the same way as you update the other projects on your server. Follow the procedure below to update your existing Enterprise Manager project. For detailed information about the update process, see Metadata update process, page 23. To update your existing Enterprise Manager project 1 In Desktop, log in to the Enterprise Manager project. You must use a login that has administrative privileges. A dialog box with update options is displayed. 2 Select the Update Report Services document definitions and Update report definitions check boxes. 3 Click Yes to proceed with the project updates. 4 Restart the Intelligence Server. Including the new features in your custom Enterprise Manager environment You may have created custom objects in Enterprise Manager that you want to keep, and also want to take advantages of the new reporting features in Enterprise Manager version 9.2.1m. You can do this by updating your existing Enterprise Manager project, and then using Object Manager to migrate the new and updated objects from the version 9.2.1m Enterprise Manager project into your current project. The upgrade process requires Project Duplication and Object Manager. For background information about these tools, see the Managing Your Projects chapter of the MicroStrategy System Administration Guide. If you do not perform the DML upgrade to the statistics tables and the data warehouse, Enterprise Manager version 9.2.1m is not able to use the new reporting features on statistics collected prior to upgrading to version 9.2.1m. For more information about the DML upgrade, see Upgrading the statistics tables, page 35 and Upgrading the data warehouse, page MicroStrategy, Inc. Upgrading MicroStrategy on Windows 41

70 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide To update your custom Enterprise Manager environment with the new features 1 Update your existing Enterprise Manager project, by following the steps in Updating an existing Enterprise Manager project, page Use the Project Duplication Wizard to make a backup of your Enterprise Manager project. For detailed information about using Project Duplication, see the Managing Your Projects chapter of the MicroStrategy System Administration Guide. 3 Use Object Manager s project comparison feature to identify which objects are different between the version 9.2.1m project and your project. For detailed information about using Object Manager, see the Managing Your Projects chapter of the MicroStrategy System Administration Guide. The version 9.2.1m project is located in the Access database EM_PROJ_MD.mdb, in the Enterprise Manager directory. By default, this directory is C:\Program Files\MicroStrategy\Enterprise Manager. MicroStrategy recommends that, rather than making changes to an Enterprise Manager object such as a report or metric, you make a copy of the object and modify the copy. This prevents your changes from being overwritten during an upgrade. 4 Use Object Manager to migrate the new objects from the version 9.2.1m project to your project. Specify the EM_PROJ_MD.mdb file as the source project, and your Enterprise Manager project as the destination project. For detailed information about using Object Manager, see the Managing Your Projects chapter of the MicroStrategy System Administration Guide. 42 Upgrading MicroStrategy on Windows 2011 MicroStrategy, Inc.

71 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 Upgrading MicroStrategy on UNIX and Linux This section provides installation and project update procedures to upgrade MicroStrategy Universal products to the latest version in a UNIX or Linux environment. Be aware of the following: While the installation process does not affect your project s metadata, it is strongly recommended you perform a full database backup of your production metadata in case you later need to restore a copy of your original metadata. Before upgrading to the latest version of MicroStrategy, see Backing up the metadata, page 11. If you use clustered Intelligence Servers in MicroStrategy, see Upgrading in a clustered environment, page 13 before proceeding with the upgrade. MicroStrategy 9.2.1m is not interoperable with pre releases. That is, clients (such as MicroStrategy Web or Desktop) and servers (such as Intelligence Server or MicroStrategy Web Server) should be upgraded to MicroStrategy 9.2.1m. However, MicroStrategy 9.2.1m is interoperable with MicroStrategy 9.0.1, MicroStrategy 9.0.1m, MicroStrategy 9.0.2, MicroStrategy 9.2, MicroStrategy 9.2.1, and MicroStrategy 9.2.1a. In addition, you must upgrade both Intelligence Server and MicroStrategy Web to version 9.2.1m to ensure the successful execution of Report Services documents in Flash Mode. MicroStrategy Mobile clients from version 9.2.1a and later are interoperable with MicroStrategy Mobile Server version and later. However, full feature support is unavailable in any scenario where the client and server are on different versions. To ensure full feature support, upgrade both MicroStrategy Mobile client and server systems to the latest version. In addition, all pre-9.0 MicroStrategy products must be uninstalled prior to upgrading to MicroStrategy 9.2.1m. You can upgrade directly from 9.0.x or 9.2.x to 9.2.1m without uninstalling the previous version of MicroStrategy. For information about uninstalling previous versions of MicroStrategy, see Uninstall the previous version of MicroStrategy, page MicroStrategy, Inc. Upgrading MicroStrategy on UNIX and Linux 43

72 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide Installing MicroStrategy Universal products on UNIX and Linux To install MicroStrategy on a UNIX or Linux machine, follow the detailed procedures in the Installing MicroStrategy on UNIX and Linux chapter of the MicroStrategy Installation and Configuration Guide. During the installation, the MicroStrategy Installation Wizard prompts you to define the location in which the following MicroStrategy folders are installed: Home directory Do The default location is /var/opt/microstrategy or $HOME/MicroStrategy if you do not have write access to /var/opt/microstrategy not install the MicroStrategy configuration files directly to your UNIX or Linux home directory ($HOME). To ensure that the required MicroStrategy permissions can be defined for the MicroStrategy configuration files, you must install these files within a separate directory. For example, the default path of $HOME/MicroStrategy uses the MicroStrategy directory within $HOME to ensure permissions on these files are defined correctly. Install directory Log directory MicroStrategy Web Universal installation directory You are prompted for this information only when the MicroStrategy Web Universal option is selected in the Select Components page. MicroStrategy SDK installation directory You are prompted for this information only when the MicroStrategy SDK option is selected in the Select Components page. You can verify your installation after installing MicroStrategy. To learn how to verify the installation of MicroStrategy, see the Installation procedures on UNIX and Linux chapter of the MicroStrategy Installation and Configuration Guide. 44 Upgrading MicroStrategy on UNIX and Linux 2011 MicroStrategy, Inc.

73 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 Migrating Intelligence Server from Windows to UNIX or Linux If you are installing MicroStrategy Intelligence Server Universal on UNIX or Linux, and you previously had Intelligence Server installed on a Windows platform, it is strongly recommended you modify certain system tuning settings. These memory and cache settings govern and optimize the performance of Intelligence Server Universal and MicroStrategy projects in your 64-bit UNIX or Linux environment. You can configure these memory, cache, and other settings from your newly installed MicroStrategy Desktop. For information on modifying these settings to optimize the performance of your MicroStrategy system in UNIX or Linux, see Migrating Intelligence Server from Windows to UNIX or Linux, page 68. Supporting fonts for documents, exported reports, and graphs When Intelligence Server Universal is running on a UNIX or Linux platform, all fonts are converted to the Courier New font for: Reports exported to PDF format Report Services documents Graphs contained in HTML documents Graphs displayed in MicroStrategy Web This occurs because the fonts required by the PDF component are missing from UNIX and Linux machines running Intelligence Server Universal. The missing fonts may include Microsoft True Type fonts. MicroStrategy does not distribute or license Microsoft fonts, and therefore cannot package Microsoft fonts with Intelligence Server Universal. To resolve this issue, you must install the font files in the PDFGeneratorFiles folder within the MicroStrategy installation path on the UNIX or Linux machine, as described below MicroStrategy, Inc. Upgrading MicroStrategy on UNIX and Linux 45

74 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide To copy fonts to your UNIX or Linux machine 1 Log in to your UNIX or Linux machine that hosts Intelligence Server Universal. 2 Install the Microsoft True Type fonts. Refer to the following resources for information on licensing requirements for and installing Microsoft True Type fonts: RedistributionFAQ.mspx msfonts_main.html 3 Copy the font files into the <INSTALL_PATH>/PDFGeneratorFiles directory, where <INSTALL_PATH> is the directory you specified as the MicroStrategy install directory during installation. 4 Restart the Intelligence Server to update the list of available fonts. Updating the metadata on a UNIX or Linux machine Whenever an Intelligence Server is upgraded, the metadata should also be updated to match the version of the Intelligence Server. You should update all projects in the metadata at the same time to ensure that new MicroStrategy products are not running against old metadata. To update the metadata using the Configuration Wizard on UNIX or Linux, access the Configuration Wizard by following the steps below, and then follow the procedures in Update the production metadata, page 20. Alternately, you can use a response file to update the metadata without having to step through the Configuration Wizard. For more information on using a response file to automatically update the metadata, see Using a response file with Configuration Wizard, page Upgrading MicroStrategy on UNIX and Linux 2011 MicroStrategy, Inc.

75 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 To access the MicroStrategy Configuration Wizard in UNIX/Linux 1 Open the Configuration Wizard from either a console window or a command line. To open the Configuration Wizard in a console window a b From a UNIX/Linux console window, browse to <HOME_PATH>, where <HOME_PATH> is the directory that you specified as the home directory during installation. Browse to the folder bin and type./mstrcfgwiz, and then press ENTER. The Configuration Wizard opens. To open the Configuration Wizard in command line mode a b From a UNIX/Linux console window, browse to <HOME_PATH>, where <HOME_PATH> is the directory that you specified as the home directory during installation. Browse to the folder bin and type./mstrcfgwiz-editor, then press ENTER. In command line mode, the command line prompts guide you through the available configuration options. For information on using the Configuration Wizard in command line mode, see the Installation and Configuration Guide. Completing the upgrade After installing and configuring the MicroStrategy Universal products in your production environment, continue the upgrade procedure outlined in the rest of this guide. To make your upgraded MicroStrategy Web application available, re-deploy the new WAR file on an application server of your choice. For information about deploying MicroStrategy Web Universal on different application servers, refer to the MicroStrategy Installation and Configuration Guide. For information about installing and deploying MicroStrategy Web Universal on other operating systems or with other Web and application servers, see the MicroStrategy Installation and Configuration Guide MicroStrategy, Inc. Upgrading MicroStrategy on UNIX and Linux 47

76 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide Using a response file with Configuration Wizard As an alternative to stepping through each page of the Configuration Wizard, you can create a response file with the upgrade information, and use that response file with the Configuration Wizard to automatically upgrade your MicroStrategy systems. MicroStrategy recommends that you create the response file through the GUI mode of the Configuration Wizard. This section provides the following information on using a response file: Creating a response file, page 48 Loading a response file, page 49 Response configuration parameters and options, page 51: Upgrading Intelligence Server components and projects, page 51 Upgrading Statistics repositories, page 55 Migrating Narrowcast Web delivery subscriptions to MicroStrategy Distribution Services, page 56 Creating a response file MicroStrategy recommends that you create a response file through the GUI mode of the Configuration Wizard. You step through the Configuration Wizard and make your selections. Then, at the end of the Configuration Wizard, do not click Finish. Instead, click Save. You are prompted to save your selections in a response file. For detailed instructions on how to use the Configuration Wizard, see Metadata update process, page 23. You can also create or modify a response file with a text editor. For information on all the parameters in the response file, see Response configuration parameters and options, page 51. MicroStrategy supplies a blank response file template, Response.ini, in the Common Files folder of your MicroStrategy installation. By default, this folder is C:\Program Files\Common Files\MicroStrategy. 48 Using a response file with Configuration Wizard 2011 MicroStrategy, Inc.

77 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 Loading a response file You can execute a response file in any of the following ways: From within the Configuration Wizard. See To use a response file with the Configuration Wizard, page 49. From the Windows command line. See To use a response file through the Windows command line, page 49. This enables users to run the file without using any graphical user interfaces. In UNIX or Linux. See To use a response file through the Configuration Wizard in UNIX or Linux, page 50. To use a response file with the Configuration Wizard 1 From the Windows Start menu, point to Programs, then MicroStrategy, and then select Configuration Wizard. The Configuration Wizard opens. 2 Click Load. The Open dialog box displays. 3 Browse to the path where the response file is saved and click Open. The Summary page opens. 4 An overview of all of the configuration tasks performed by the response file is displayed. Review the configuration tasks and click Finish to perform the configuration. To use a response file through the Windows command line 1 Type the following command in the Windows command line: macfgwiz.exe -r Path\response.ini Where Path\ is the fully qualified path to the response file. For example, a common location of a response file is: C:\Program Files\Common Files\ MicroStrategy\RESPONSE.INI If an error message is displayed, check the path and name you supplied for the response file and make any required changes MicroStrategy, Inc. Using a response file with Configuration Wizard 49

78 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide To use a response file through the Configuration Wizard in UNIX or Linux 1 From a UNIX or Linux console window, browse to <HOME_PATH> where <HOME_PATH> is the directory you specified as the Home Directory during installation. 2 Browse to the folder bin. 3 Type mstrcfgwiz-editor, and then press ENTER. The Configuration Wizard opens with the Welcome page displayed. 4 Press ENTER. 5 Type 1 to select to use a response file, and then press ENTER. 6 Type the full qualified path to the response.ini file and then press ENTER. For example: /home/username/microstrategy/response.ini If an error message is displayed, check the path and name you supplied for the response file and make any required changes. To use a response file through the UNIX/Linux command line 1 From a UNIX or Linux console window, browse to <HOME_PATH> where <HOME_PATH> is the directory you specified as the Home Directory during installation. 2 Browse to the folder bin. 3 Type the following command in the command line, and then press ENTER. mstrcfgwiz-editor -response /Path/response.ini Where Path is the fully qualified path to the response file. For example, a common location of a response file is: /home/username/microstrategy/response.ini If an error message is displayed, check the path and name you supplied for the response file and make any required changes. 50 Using a response file with Configuration Wizard 2011 MicroStrategy, Inc.

79 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 Response configuration parameters and options MicroStrategy recommends that you always create the response file through the GUI mode of the Configuration Wizard. However, you can also modify a response file with a text editor to make minor changes such as entering different user login and password information. The file must be saved with ANSI encoding. The following tables list the response file parameters for the tasks you can perform with Configuration Wizard: Upgrading Intelligence Server components and projects, page 51 Upgrading Statistics repositories, page 55 Upgrading History List repositories, page 55 Migrating Narrowcast Web delivery subscriptions to MicroStrategy Distribution Services, page 56 Upgrading Intelligence Server components and projects The response file parameters within the [UpgradeServer] section upgrade Intelligence Server components and projects. The table below lists the available parameters and the functionality of available options for each parameter. Options [UpgradeServer] UpgradeServer= UpgradeMD= Description In this section you can upgrade Intelligence Server components and the projects for an Intelligence Server. Defines whether to upgrade Intelligence Server components and projects, as determined by the following values: 1: Upgrade Intelligence Server components and projects 0: Does not upgrade Intelligence Server components and projects Defines whether to upgrade the metadata, as determined by the following values: 1: Upgrades the metadata repository, which contains the definitions of your MicroStrategy applications and supporting objects. An upgrade of your metadata is required to provide support for all new and updated features in the most recent version of MicroStrategy. 0: Does not upgrade the metadata MicroStrategy, Inc. Using a response file with Configuration Wizard 51

80 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide Options Upgrade Privileges= MigrateHL= UpgradeProjects= ServerUser= ServerPwd= MDPwd= PrivilegesSource Version= HLPath= HLDSNName= HLUserName= Description Defines whether to upgrade administrative privileges, as determined by the following values: 1: Upgrades the privileges used to define the features and capabilities available for each MicroStrategy user. This upgrade is required to reflect any changes in privileges for the most recent version of MicroStrategy. After the upgrade is finished, you can manually modify the privileges for your users and user groups to ensure that all users have access to the required MicroStrategy features. To ensure that the updated user privileges are in compliance with your license agreement, you can use License Manager to audit and view user product privileges. 0: Does not upgrade administrative privileges. Defines whether to migrate History List from a flat file to a database, as determined by the following values: 1: Migrate your previous file-based History List repository to a database-based History List repository. In pre-9.0 versions of MicroStrategy, all History List files could only be stored using a file-based method. In addition to the file-based method, it is also possible to store the History List repository in the database. This allows administrators to centrally monitor all History List messages across the system. 0: Does not migrate History Lists to a database. You should use this option if you did not previously use History List messages or you plan to continue to use a flat file to support and store History Lists. Defines whether to upgrade projects, as determined by the following values: 1: Upgrades the projects defined in ProjectLogicalUpgrade. 0: Does not upgrade projects. Provide the user name for the MicroStrategy user to connect to the Intelligence Server to upgrade. Provide the password for the MicroStrategy user to connect to the Intelligence Server to upgrade. Provide the password for the metadata to upgrade. If you have previously upgraded the metadata but not upgraded the privileges, provide the version of the metadata that you most recently upgraded your privileges to, from the following list of options: 8.x m If performing a History List migration, defines the directory location of the History List flat file to migrate to a database. If performing a History List migration, defines the DSN of the database to migrate the History List tables to. If performing a History List migration, defines the user name to connect to the database for the History List migration. 52 Using a response file with Configuration Wizard 2011 MicroStrategy, Inc.

81 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 Options HLUserPwd= HLPrefix= HLDropTables= HLDeleteFiles= HLUseUTF8= HLUseUnixUTF8= ProjectLogical Upgrade= Description If performing a History List migration, defines the password to connect to the database for the History List migration. If performing a History List migration, defines the table prefix for History List tables. Defines whether to drop existing tables in the database used for the History List migration, as determined by the following values: 1: Deletes existing tables in the database before migrating the History List tables. 0: Appends the migrated History List tables to the database without deleting existing tables. Defines whether to delete the file based History List after the migration is complete, as determined by the following values: 1: Deletes the file-based History List repository once the migration to a database-based History List repository is complete. This option should only be used if the file-based History List repository is no longer needed, and you can ensure the migration process can be completed successfully. 0: Does not delete the file-based History List repository once the migration to a database-based History List repository is complete. Defines whether UTF-8 encoding should be used for the History List migration on Windows, as determined by the following values: 1: Uses UTF-8 encoding for Windows drivers. This option should be used if your database and History List messages use UTF-8 encoding, and the Intelligence Server is installed on Windows. 0: Does not use UTF-8 encoding. Defines whether UTF-8 encoding should be used for the History List migration on UNIX/Linux, as determined by the following values: 1: Uses UTF-8 encoding for UNIX/Linux drivers. This option should be used if your database and History List messages use UTF-8 encoding, and the Intelligence Server is installed on UNIX or Linux. 0: Does not use UTF-8 encoding. Define the projects to update their schedules that send reports and documents to caches, History Lists, and MicroStrategy Mobile as subscriptions. These subscriptions are part of the integrated subscription and delivery features in Intelligence Server 9.0 and later versions. They provide the same ability to send reports and documents to caches, History Lists, and MicroStrategy Mobile as the schedules in MicroStrategy pre-9.0. This option also upgrades the reports and Report Services documents in the projects, which improves performance, reduces storage space requirements, and ensures that graphs display correctly in MicroStrategy Web and Desktop 9.2.1m. To upgrade multiple projects, you must enclose the name of each project in curly braces { } and separate the names with a backslash \. For example: {Project1}\{Project2}\...\{ProjectN} 2011 MicroStrategy, Inc. Using a response file with Configuration Wizard 53

82 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide Options ScheduleUpdate= MDXUpdate= SysObjID Unification= ProjectUpgrade Continue Executing= EncryptPassword= DB2ZoSDBName= DB2ZoSTableSpace Name= Description Define the projects to upgrade their schedules to the most recent version of MicroStrategy. To upgrade multiple projects schedules, you must enclose the name of each project in curly braces { } and separate the names with a backslash \. For example: {Project1}\{Project2}\...\{ProjectN} Define the projects to update their MDX source objects (MDX cubes) that were created in earlier versions of MicroStrategy to take advantage of increased performance and other updates. Note: You can integrate MDX sources such as SAP BW, Microsoft Analysis Services, and Hyperion Essbase into your MicroStrategy environment. For information on integrating MDX sources into MicroStrategy, see the MDX Cube Reporting Guide. To upgrade multiple projects MDX source objects, you must enclose the name of each project in curly braces { } and separate the names with a backslash \. For example: {Project1}\{Project2}\...\{ProjectN} Define the projects for which to update system objects so as to successfully move objects between unrelated projects using MicroStrategy Object Manager. This is required for projects from pre versions of MicroStrategy. To upgrade multiple projects system objects, you must enclose the name of each project in curly braces { } and separate the names with a backslash \. For example: {Project1}\{Project2}\...\{ProjectN} Define whether to update the rest of the specified projects if one project update generates an error: 1: Continue the update process even if an error is found in one project. 0: Halt the update process for all projects if an error is found in one project. Defines whether the password is encrypted in the response file, as determined by the following values: 0: The password is not encrypted in the response file, which enables you to modify the password in the response file later using a text editor. You can then distribute the response file to multiple users with various login and password credentials. However, be aware that this can compromise your database security if you do not remove the password from the response file before distributing it. 1: Encrypts the password in the response file, which ensures that your password is secure. This is the default behavior. Defines the database name to update metadatas stored in DB2 z/os. This option should only be used when connecting to a DB2 z/os database. Defines the table name to be used in the database when upgrading the metadata. This option should only be used when connecting to a DB2 z/os database. 54 Using a response file with Configuration Wizard 2011 MicroStrategy, Inc.

83 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 Upgrading Statistics repositories The response file parameters within the [UpgradeStats] section upgrade a statistics repository. The table below lists the available parameters and the functionality of available options for each parameter. Options [UpgradeStats] UpgradeStats= EncryptPassword= StatsDSN= StatsUser= StatsPwd= StatsPrefix= Description In this section you can upgrade statistics repositories to the most recent version of MicroStrategy. You can have more than one [UpgradeStats] section. Additional statistics upgrade sections can be included as [UpgradeStats1], [UpgradeStats2], and so on. Defines whether to upgrade a statistics repository, as determined by the following values: 1: Upgrade the statistics repository 0: Does not upgrade the statistics repository Defines whether the password is encrypted in the response file, as determined by the following values: 0: The password is not encrypted in the response file, which enables you to modify the password in the response file later using a text editor. You can then distribute the response file to multiple users with various login and password credentials. However, be aware that this can compromise your database security if you do not remove the password from the response file before distributing it. 1: Encrypts the password in the response file, which ensures that your password is secure. This is the default behavior. If performing a statistics repository upgrade, defines the DSN of the database that stores the statistics repository. If performing a statistics repository upgrade, defines the user name to connect to the database for the statistics repository. If performing a statistics repository upgrade, defines the password to connect to the database for the statistics repository. If performing a statistics repository upgrade, defines the database prefix for the statistics repository. Upgrading History List repositories The response file parameters within the [UpgradeHistoryList] section upgrade a database-based History List repository. The table below lists the 2011 MicroStrategy, Inc. Using a response file with Configuration Wizard 55

84 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide available parameters and the functionality of available options for each parameter. Options [UpgradeHistory List] UpgradeHistory List= EncryptPassword= HLDSN= HLUser= HLPwd= HLPrefix= Description In this section you can upgrade History List repositories to the most recent version of MicroStrategy. You can have more than one [UpgradeHistoryList] section. Additional History List upgrade sections can be included as [UpgradeHistoryList1], [UpgradeHistoryList2], and so on. Defines whether to upgrade a History List repository, as determined by the following values: 1: Upgrade the History List repository 0: Does not upgrade the History List repository Defines whether the password is encrypted in the response file, as determined by the following values: 0: The password is not encrypted in the response file, which enables you to modify the password in the response file later using a text editor. You can then distribute the response file to multiple users with various login and password credentials. However, be aware that this can compromise your database security if you do not remove the password from the response file before distributing it. 1: Encrypts the password in the response file, which ensures that your password is secure. This is the default behavior. If performing a History List repository upgrade, defines the DSN of the database that stores the History List repository. If performing a History List repository upgrade, defines the user name to connect to the database for the History List repository. If performing a History List repository upgrade, defines the password to connect to the database for the History List repository. If performing a History List repository upgrade, defines the database prefix for the History List repository. Migrating Narrowcast Web delivery subscriptions to MicroStrategy Distribution Services The response file parameters within the [UpgradeServer] section migrate MicroStrategy Web delivery subscriptions from a Narrowcast Server environment to Distribution Services. MicroStrategy Web delivery subscriptions include , file, and print subscriptions created from MicroStrategy Web. Migrating these subscriptions from Narrowcast Server to Distribution Services allows the subscriptions to be centralized within Intelligence Server rather than a separate Narrowcast Server. The table 56 Using a response file with Configuration Wizard 2011 MicroStrategy, Inc.

85 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 below lists the available parameters and the functionality of available options for each parameter. Options [MigrateNCS] MigrateNCS= DSNNameSBR= UserNameSBR= UserPwdSBR= SysPrefixSBR= DSNNameOR= UserNameOR= UserPwdOR= SysPrefixOR= PSNName= DSSUser= DSSPwd= TargetProjects= Description In this section you can migrate MicroStrategy Web delivery subscriptions from a Narrowcast Server environment to Distribution Services. You can have more than one [MigrateNCS] section. Additional MicroStrategy Web delivery subscription migration sections can be included as [MigrateNCS1], [MigrateNCS2], and so on. Defines whether to migrate MicroStrategy Web delivery subscriptions from a Narrowcast Server environment to Distribution Services, as determined by the following values: 1: Migrates MicroStrategy Web delivery subscriptions from a Narrowcast Server environment to Distribution Services 0: Does not migrate MicroStrategy Web delivery subscriptions from a Narrowcast Server environment to Distribution Services Defines the DSN of the database that stores the Narrowcast Subscription Book Repository. Defines the user name to connect to the database for the Narrowcast Subscription Book Repository. Defines the password to connect to the database for the Narrowcast Subscription Book Repository. Defines the prefix used for the tables of the Narrowcast Subscription Book Repository. Defines the DSN of the database that stores the Narrowcast Object Repository. Defines the user name to connect to the database for the Narrowcast Object Repository. Defines the password to connect to the database for the Narrowcast Object Repository. Defines the prefix used for the tables of the Narrowcast Object Repository. Defines the project source that the Web delivery subscriptions are migrated to. Defines the user name to connect to the project source. Defines the user password to connect to the project source. Defines the projects, for a given project source, to migrate their Narrowcast subscriptions to MicroStrategy Web delivery subscriptions. You can select multiple projects, separating projects by the \ character. For example, TargetProjects=Project1\Project MicroStrategy, Inc. Using a response file with Configuration Wizard 57

86 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide Options MigrateWeb DeliveryUsers= Assign Privileges= MigrateNCSUsers= Description Defines whether to migrate all users of Web deliveries to Distribution Services, as determined by the following values: 1: Migrates all users of Web deliveries to Distribution Services. Addresses of the MicroStrategy users who subscribed to Web deliveries are assigned to the corresponding MicroStrategy users. No new MicroStrategy users are created. 0: Does not migrate all users of Web deliveries to Distribution Services. If you choose to migrate all users of Web deliveries to Distribution Services, this option defines whether to grant the Use Distribution Services privilege for all Web delivery users that are migrated to Distribution Services, as determined by the following values: 1: Grants the Use Distribution Services privilege for all Web delivery users that are migrated to Distribution Services. Ensure that granting these privileges is in compliance with your product license for Distribution Services. 0: Does not grant the Use Distribution Services privilege for all Web delivery users that are migrated to Distribution Services. Defines whether to migrate Narrowcast Server users and their addresses as contacts in Distribution Services, as determined by the following values: 1: Migrates Narrowcast Server users and their addresses as contacts in Distribution Services. A contact is created for each Narrowcast Server user. The Narrowcast Server user s addresses are copied as addresses of the contact. A contact is a list of subscription recipient addresses. These recipients do not have the permissions to log in to MicroStrategy Web or Desktop. Contacts enable these recipients to receive subscriptions. 0: Does not migrate Narrowcast Server users and their addresses as contacts in Distribution Services 58 Using a response file with Configuration Wizard 2011 MicroStrategy, Inc.

87 Upgrade Guide Upgrading MicroStrategy on Windows, UNIX, or Linux 3 Options MigrateTransmitt ersaction= MigrateDevicesAc tion= MigrateSchedules Action= MigrateSubscript ionsaction= MigrateUsersActi on= Description These parameters specify the conflict resolution rules when migrating Narrowcast objects to Distribution Services. Conflicts occur when objects are present in both the Narrowcast Server system you are migrating from and the Intelligence Server metadata you are migrating to. Defining conflict resolution rules determines how these conflicts are resolved during the migration. You can use the following parameters to define how to resolve any conflicts during the migration: MigrateTransmittersAction for Transmitters fmigratedevicesaction for Devices MigrateSchedulesAction for Schedules MigrateSubscriptionsAction for Subscriptions MigrateUsersAction for Users For each object type listed above, you can define conflict resolution rules based on matching IDs. For transmitters, devices, and schedules you can also define conflict resolution rules based or matching definitions. These options are described in the table below. Note: In the table below, source refers to your Narrowcast Server and destination refers to the new metadata tables. Match by ID or Definition Match by IDs Objects are matched by their ID only. Match by Definition Objects are matched by their definitions. This enables objects that have the same definition, but different IDs to be defined as a match. These conflict resolution options are available for transmitters, devices, and schedules. Conflict Resolution Match by IDs, keep existing If objects with matching IDs are found, the object in the destination location is kept. The object in the source is not migrated to the destination. Match by IDs, replace If objects with matching IDs are found, the object from the source replaces the matching object in the destination. Match by Definition, merge If objects with matching definitions are found, all dependent objects of the matching object in the source are migrated to the destination. The migrated dependent objects are defined as dependents of the matching object in the destination. Match by Definition, create new If objects with matching definitions are found, the matching object in the source is migrated to the destination as a new object. A separate object for the matching object in the destination is also kept. This results in two objects with matching definitions in the destination, which you can modify after the migration is complete. Option Value MicroStrategy, Inc. Using a response file with Configuration Wizard 59

88 3 Upgrading MicroStrategy on Windows, UNIX, or Linux Upgrade Guide Options EncryptPassword= Description Defines whether the password is encrypted in the response file, as determined by the following values: 0: The password is not encrypted in the response file, which enables you to modify the password in the response file later using a text editor. You can then distribute the response file to multiple users with various login and password credentials. However, be aware that this can compromise your database security if you do not remove the password from the response file before distributing it. 1: Encrypts the password in the response file, which ensures that your password is secure. This is the default behavior. 60 Using a response file with Configuration Wizard 2011 MicroStrategy, Inc.

89 4 4.AFTER THE UPGRADE Introduction After installing and configuring MicroStrategy, perform the post-upgrade procedures outlined in this chapter to fully prepare and optimize your upgraded MicroStrategy system for the production environment. This chapter includes the following sections: Using License Manager to verify licensing, page 62 Using Service Manager to check Intelligence Server, page 62 Testing product functionality, page 62 Checking and assigning privileges, page 66 Merging pre-existing translations into a single project, page 67 Completing the upgrade process, page 68 Migrating Intelligence Server from Windows to UNIX or Linux, page 68 Troubleshooting the upgrade, page MicroStrategy, Inc. 61

90 4 After the Upgrade Upgrade Guide Using License Manager to verify licensing After upgrading to the latest version of MicroStrategy, verify your product licenses to ensure you are in compliance with your licensing agreements with MicroStrategy. You can use License Manager to perform a compliance check of your MicroStrategy system. For information about using License Manager to perform a compliance check of your MicroStrategy system, see the Managing your Licenses chapter of the MicroStrategy System Administration Guide. Using Service Manager to check Intelligence Server MicroStrategy Service Manager is a management tool installed with MicroStrategy Intelligence Server that enables you to start and stop Intelligence Server and choose a startup option. You can also use it to check to see if the Intelligence Server is running. For information about configuring the startup options for Intelligence Server, refer to the Tuning chapter of the System Administration Guide. For steps to use MicroStrategy Service Manager, see the Introduction to MicroStrategy System Administration chapter of the MicroStrategy System Administration Guide. Testing product functionality The following sections outline specific features and settings to check before using your upgraded MicroStrategy system in a production environment. Intelligence Server and Desktop After performing the upgrade, verify the following settings and features to ensure that Desktop is configured to your specific needs. 62 Using License Manager to verify licensing 2011 MicroStrategy, Inc.

91 Upgrade Guide After the Upgrade 4 Folder locations Verify the location of the Cache, Working Set, and HTML Document folders to ensure they are stored in appropriate folders and machines. If you are using a clustered Intelligence Server environment, ensure that the folders storing caches are in fact shared folders. You can modify the Cache and HTML document folder settings in the Project Configuration Editor in Desktop. The settings for the History List and Working Set folders are located in the Intelligence Server Configuration dialog box. If you are storing your History List in a file instead of in a database, verify the location of the History List folders as well. For more information about storing the History List in a file, see the Caching chapter in the MicroStrategy System Administration Guide. Testing your reports in an upgraded environment After upgrading your system you may want to ensure that the changes involved do not alter any of your report results. MicroStrategy Integrity Manager can execute any or all reports from a project, note whether or not they execute, and allow you to view their results. Integrity Manager can also execute reports from two different projects and compare their results. Integrity Manager informs you as to what data, SQL, and graph reports are different between the two projects. For more information about Integrity Manager, see the Integrity Manager Chapter in the MicroStrategy System Administration Guide. The default SQL Global Optimization value was increased in MicroStrategy 9.0. SQL Global Optimization determines the level by which SQL queries in reports are optimized by combining certain SQL passes and eliminating unnecessary temporary tables. Because of this change, MicroStrategy Integrity Manager may return Not Matched results for some reports and documents after the metadata update. The reports and documents return the same results after the upgrade, but the SQL that is generated is different. If you need to preserve the SQL generated by reports after you upgrade from a pre-9.0 version of MicroStrategy, you can change the SQL Global Optimization VLDB property from the 9.0 default value (4) to the pre-9.0 default value (1). For more information about changing VLDB properties, and about SQL Global Optimization, see the SQL Generation and Data Processing: VLDB Properties chapter in the Supplemental Reference for System Administration MicroStrategy, Inc. Testing product functionality 63

92 4 After the Upgrade Upgrade Guide New features and settings Verify the following settings and make appropriate changes, if necessary: VLDB settings Project preferences in the Project Configuration Editor Intelligence Server settings in the Intelligence Server Configuration Editor Connection properties Authentication modes For help with any product-related issues, contact MicroStrategy Technical Support. MicroStrategy Web Once you have installed the latest version of MicroStrategy Web, you need to establish connectivity with MicroStrategy Intelligence Server. You establish connectivity by performing the following steps. To establish a connection between the Intelligence Server and MicroStrategy Web 1 From the Start menu, select Programs, then MicroStrategy, and then Web Administrator. 2 In the Add a server manually box, enter the appropriate MicroStrategy Intelligence Server name and click Add. 3 Click Save to save the connection properties and click Connect to allow Web to connect to your Intelligence Server. Once a connection between MicroStrategy Web and the Intelligence Server is established, you can log in to MicroStrategy Web and execute reports and documents. 64 Testing product functionality 2011 MicroStrategy, Inc.

93 Upgrade Guide After the Upgrade 4 To open and log in to MicroStrategy Web 1 From the Web Administrator page, click the Return to MicroStrategy Web Home link at the top of the page. The MicroStrategy Web project selection screen opens. From here, you are able to log in to your MicroStrategy projects. 2 To log in to a project, click the icon or the title of the project. 3 At the login screen, type the user name and password you use to access your project and click Login. The MicroStrategy Web home page is displayed. Make sure to check your Web customizations and refer to Upgrading Web customizations, page 13 for information on recovering your previous customizations. MicroStrategy administrative tools After upgrading Command Manager, Enterprise Manager, and Object Manager, perform the following system checks to ensure these products are working properly: Verify that the Use Command Manager and Use Object Manager privileges are properly enforced. Only users with these privileges should be able to use the appropriate MicroStrategy tools. Use Object Manager and the Project Merge Wizard to duplicate and merge projects and verify that these tasks are successfully completed. If you changed any default settings in the previous versions of these products, verify that your customized settings exist in the upgraded products. If you were using the default MicroStrategy settings, review the default settings in the upgraded products for any changes and ensure that they are still valid in your environment. Run the data load process and verify that the load completes successfully. Make sure you can use Enterprise Manager 9.2.1m to retrieve statistics from the pre-9.2.1m version of Enterprise Manager. If you encounter any product-related issues, contact MicroStrategy Technical Support MicroStrategy, Inc. Testing product functionality 65

94 4 After the Upgrade Upgrade Guide Checking and assigning privileges It is essential you take the time to assign and make changes to the many user permissions that affect your MicroStrategy system. Review the following for a list of privileges you should manually assign to users after upgrading MicroStrategy. Ensure that Desktop users are granted the Use Desktop privilege, in the Desktop Analyst privilege group. If a user does not have this privilege, an error message appears when the user attempts to connect to a specific project. Ensure that Create New Folder privilege, in the Common Privileges privilege group, is granted to any users that need to create folders in Desktop or in MicroStrategy Web. Verify the access control lists for folders such as the Public Objects and Schema Objects and make appropriate changes if necessary. Certain new features may require you to assign additional privileges to users. Refer to the appropriate product documentation to learn about the specific feature, and the MicroStrategy System Administration Guide for details about any associated privileges. MicroStrategy 9.0 introduced several new privileges, and some user tasks that previously required only one privilege may now require more than one. You can determine which users have been affected by the changes in privileges in the latest version of MicroStrategy by using the Find and Replace Privileges dialog box, as described in the procedure below. To access the Find and Replace Privileges dialog box 1 In Desktop, log in to a project source as an administrator. 66 Checking and assigning privileges 2011 MicroStrategy, Inc.

95 Upgrade Guide After the Upgrade 4 2 From the Administration menu, point to User Management, and select Find and Replace Privileges. The Find and Replace Privileges dialog box opens, as shown below: For instructions on how to use the Find and Replace Privileges dialog box, refer to the Desktop Help. (From within Desktop, press F1, or select Help from the menu.) Merging pre-existing translations into a single project Beginning in MicroStrategy 9.0, support for a multi-lingual environment has been greatly expanded. Translations can be applied to objects stored in the metadata and information stored in the data warehouse. For a full description of internationalization in MicroStrategy, see the Creating a Multi-Lingual Environment chapter of the Supplemental Reference for System Administration MicroStrategy, Inc. Merging pre-existing translations into a single project 67

96 4 After the Upgrade Upgrade Guide Prior to version 9.0, each project could only support a single language. If you implemented a multi-lingual environment, you maintained a duplicate project for each language that you wanted to be available for a project. Beginning with MicroStrategy 9.0, it is possible to have a single project that supports multiple languages. If you implemented a multi-lingual environment prior to version 9.0, and you want to take full advantage of the improved internationalization functionality introduced in MicroStrategy 9.0, you must merge your pre-existing translated projects into a single project. This process is detailed in the Creating a Multi-Lingual Environment chapter of the Supplemental Reference for System Administration. Completing the upgrade process Once the upgrade process is complete, you should tune and optimize your MicroStrategy system for performance and stability reasons. For information about administering, maintaining, and optimizing your MicroStrategy system and projects, see the Tuning chapter of the MicroStrategy System Administration Guide. Accessing MicroStrategy documentation The MicroStrategy documentation suite provides a wide range of product information related to various aspects of your MicroStrategy system. To access MicroStrategy documentation, from the Start menu, select Programs, then MicroStrategy, and then Product Manuals. Migrating Intelligence Server from Windows to UNIX or Linux If you are installing MicroStrategy Intelligence Server Universal on UNIX or Linux, and you previously had Intelligence Server installed on a Windows platform, it is strongly recommended that you modify several Intelligence Server and project settings in your newly installed Desktop. Adjusting these settings allows Intelligence Server Universal and the rest of the MicroStrategy platform to better utilize your 64-bit UNIX or Linux operating 68 Completing the upgrade process 2011 MicroStrategy, Inc.

97 Upgrade Guide After the Upgrade 4 system s resources. The adjustments also allow your system to better mirror the performance you achieved with your Windows configuration. Your MicroStrategy projects are therefore optimized for Intelligence Server on UNIX or Linux. Repeat the steps in the procedure below for every project connected to an Intelligence Server on UNIX or Linux. For details about the settings discussed in the procedure below, refer to the Desktop Help. To modify settings that govern Intelligence Server Universal and project performance 1 In Desktop, right-click a project connected to an Intelligence Server Universal on UNIX or Linux, and select Project Configuration. The Project Configuration dialog box is displayed. 2 Expand the Caching category, then the Result Caches subcategory, and select Storage. Under Memory Storage, do the following: Under Data Sets, adjust the Maximum RAM usage (MBytes) setting so that it is at least double the size you used when Intelligence Server was installed on Windows. Under Formatted Documents, adjust the Maximum RAM usage (MBytes) setting so that it is at least double the size you used when Intelligence Server was installed on Windows. 3 Expand the Auxiliary Caches subcategory and select Objects. Under Server, adjust the Maximum RAM Usage (MBytes) setting so that it is at least double the size that you used when Intelligence Server was installed on Windows. 4 Expand the Elements subcategory. Under Server, adjust the Maximum RAM usage (MBytes) setting so that it is at least double the size that you used when Intelligence Server was installed on Windows. 5 Click OK to close the Project Configuration dialog box. 6 Repeat the steps above for every project connected to an Intelligence Server on UNIX or Linux MicroStrategy, Inc. Migrating Intelligence Server from Windows to UNIX or Linux 69

98 4 After the Upgrade Upgrade Guide 7 From the Administration menu, select Server, and then Configure MicroStrategy Intelligence Server. The Intelligence Server Configuration dialog box is displayed. 8 Expand the Governing category and select the Working Set subcategory. Adjust the Maximum RAM for Working Set cache setting so that it is at least double the size that you used when Intelligence Server was installed on Windows. 9 Expand the File Generation subcategory under Governing. Adjust only the following settings so that they are at least double the size that you used when Intelligence Server was installed on Windows. Maximum memory consumption for XML (MB) Maximum memory consumption for PDF files (MB) Maximum memory consumption for Excel files (MB) As with every production system, additional monitoring and analysis is necessary for fine-tuning and optimizing your system. For information about administering, maintaining, and optimizing your MicroStrategy system and projects, see the Tuning chapter of the MicroStrategy System Administration Guide. Troubleshooting the upgrade When you use the Configuration Wizard to add tables to the metadata or update your projects, each SQL statement that is executed is logged to the Configuration Wizard log file, MACfgWiz.xml. This log file is located in the Log subfolder of the main MicroStrategy directory. You can analyze the log file using the Apache Chainsaw log viewer, which can be downloaded from The MicroStrategy Readme contains troubleshooting scenarios aimed to assist you during or after an upgrade to the latest version of MicroStrategy. If you encounter an issue not covered in the Readme, contact MicroStrategy Technical Support for additional assistance. 70 Troubleshooting the upgrade 2011 MicroStrategy, Inc.

99 INDEX Numerics 3-tier mode, upgrading metadata in 13 A activation 2 B backing up metadata 11 best practices for upgrading 7 C clustered environment upgrade 13 Configuration Wizard response file 48 configuring MicroStrategy Intelligence Server 19 D data type, supported 11 DB2 22 downgrading a metadata project 13 E Enterprise Manager environment upgrade 34 data warehouse 36 project 39 statistics tables 35 warehouse and statistics 36, 37 H History List database update 26 I installation prerequisites hardware requirements for UNIX and Linux 10 hardware requirements for Windows 10 software requirements for UNIX and Linux 10 software requirements for Windows MicroStrategy, Inc. 71

100 Index Upgrade Guide installing activation 2 MicroStrategy 16 MicroStrategy Desktop 19 MicroStrategy Intelligence Server 19 MicroStrategy products in production environment 28 MicroStrategy Universal products on UNIX and Linux 44 international support xxi L license activation 2 License Manager, using to verify licensing 62 Linux memory settings 45, 68 migrating Intelligence Server from Windows to 68 performance 45, 68 M memory setting, UNIX or Linux 45, 68 metadata backing up 11 downgrading 13 update process 23 updating 12 updating for Intelligence Server Universal 46 version 22 metadata project, downgrading 13 metadata update 23 prerequisites 22 Microsoft Access 22 MicroStrategy Intelligence Server configuring 19 installing 19 installing in production environment 28 testing 27 using Service Manager to check 62 MicroStrategy Mobile for BlackBerry upgrade 30 MicroStrategy Narrowcast Server upgrade 29 MicroStrategy Office upgrade through Web Services 30 MicroStrategy Report Services document execution setup 46 MicroStrategy Universal products installation on UNIX and Linux 44 MicroStrategy, installing 16 migrating Intelligence Server from Windows to UNIX/Linux 68 Mobile configuration 29 Mobile Server 29 N new features 3 O ODBC connectivity 13 optimizing a MicroStrategy system 68 Oracle 22 P post-upgrade procedures MicroStrategy Command Manager 65 MicroStrategy Desktop 62 MicroStrategy Enterprise Manager 65 MicroStrategy Intelligence Server 62 MicroStrategy Object Manager 65 MicroStrategy Web MicroStrategy, Inc.

101 Upgrade Guide Index prerequisites metadata database 22 metadata update 22 pre-upgrade procedures clustered environment 13 metadata backup 11 supported data types 11 upgrade prerequisites 10 Web customization upgrade 13 product upgrade order for separate machines 28 production environment installing MicroStrategy Intelligence Server 28 installing MicroStrategy products 28 project backing up 11 downgrading 13 optimizing 68 updating 12 R response file 48 Configuration Wizard (UNIX) 50 Configuration Wizard (Windows) 49 S Service Manager, checking MicroStrategy Intelligence Server 62 setup for document execution for Report Services documents 46 SQL 70 support international xxi support. See technical support. supported data type check 11 T technical support xxii testing MicroStrategy Desktop 33 MicroStrategy Intelligence Server 27, 33 product functionality 62 troubleshooting 70 tuning performance 45, 68 performance settings in UNIX or Linux 68 U uninstalling previous version of MicroStrategy 16 UNIX memory settings 45, 68 migrating Intelligence Server from Windows to 68 performance 45, 68 updating metadata project 12 upgrade prerequisites database and driver requirements 10 privileges 11 supported data type check 11 system sizing guidelines 10 upgrade process checklist 5 upgrading basic stability testing 27 best practices 7 checklist 5 clustered environment 13 Enterprise Manager environment 34 installing and configuring a test server 19 installing in production environment MicroStrategy, Inc. 73

102 Index Upgrade Guide MicroStrategy Mobile for BlackBerry 30 MicroStrategy Narrowcast Server 29 MicroStrategy Office 30 MicroStrategy Office through MicroStrategy Web Services 30 MicroStrategy on UNIX and Linux 16 MicroStrategy on Windows 16 order for upgrading machines 28 testing 33, 62 uninstalling previous version of MicroStrategy 16 updating the production metadata 20 Web customizations 13 upgrading metadata using 3-tier connection 13 using ODBC connection 13 with Intelligence Server on UNIX or Linux 13 V verifying licensing using License Manager 62 W Web customization upgrade 13 workflow changes MicroStrategy, Inc.