How to Upgrade Your Applications From 9.X to 10 PPT...Title How to Upgrade Your Applications From...

Copyright © 2017 MicroStrategy Incorporated. All Rights Reserved .

How to Upgrade Your Applications From 9.X to 10Jacek PapuckiSupport Specialist, Premium EMEA


• Top upgrade challenges

• Typical upgrade workflow – The six phases

• Documents, Flash and 10.x

• Integrity Manager, Command Manager

• Performance, Cubes

• Web Customizations upgrade

• MicroStrategy upgrade tips

• Differences between “Feature” and “Platform” release

Agenda


What defines a successful upgrade?

•Equal or better performance

•Meaningful introduction of new features

•User guidance

•Sufficient Tests

•Seamless migration


Top Upgrade ChallengesUpgrade in a big picture

Underestimating the real effort and duration


Top Upgrade Challenges

5

• Underestimating the scope and breadth of the upgrade

SCOPE

• Experience with new version, potential typical upgrade issues and environment

EXPERIENCE

• Knowing best practices and understanding when “the plan” is complete

KNOWLEDGE

• Regression testing cycles and best practices

TESTING

• Knowing how to manage Customization (SDK) updates

CUSTOMIZATIONS


Big Picture

• New Server OS• New Hardware• New Warehouse and/or Metadata Platform• Authentication Mode Change• Application Security Changes

• Business schedules• BI Project releases• Holiday Freeze• IT Freeze • Allowable downtime• Code Freeze and Promotions• Time committed for testing• Tools – Integrity Manager/Config Wizard• Failover Plan, Backups

6

Common Planning Issue: Underestimating the Real Effort and Duration

Environment Considerations: Schedules/SLAs


Typical Upgrade WorkflowThe six phases 6 phases of success and sandbox


Standard Upgrade Phases

8

Typical upgrade workflow

Review Plan Dry Run Upgrade Test Release

Upgrade Monitoring

6 phases…

…all necessary for success.


Phase 1: System Review

Mobilization• Software and License Keys• Identify Key Resources• Review Big Picture impacts• Assign Responsibilities

Gather Key Inputs• BI Project Inventory• BI Architecture• Current MSTR Deployment

Details• Certified and Supported

configurations

Recommendations• Ancillary software upgrades

needed• Hardware purchases to support

upgrade• Major delays to Plan

Review Plan Upgrade Test Release


Phase 2: Upgrade Planning

Determine Upgrade Approach• Simple or Incremental• Customizations• Change Management

Determine Upgrade Approach**• Upgrade Execution

Plan - Milestones• Testing Plan• System Availability

Plan

Resource Model• Roles and

Responsibilities• Technical Support• Customer Resources• 3rd-party Application

Support

Pre-Requisites• Procure hardware /

virtual environments• Stand-up

Test/Upgrade Environment

• Network Connectivity and System Access



Small to medium MicroStrategy infrastructure Typical Upgrade Plan

WeeksbeforeProductionUpgrade-9 -8 -7 -6 -5 -4 -3 -2 -1 UpgradeWeek 1 2

Reviewenvironments,PlanSetupSandbox

TestsonSandboxDevelopandapplychanges

RefreshSandboxTestsonSandbox

UpgradepreparationActualUpgrade

Monitoring


Phase 3: Dry Run Upgrade

Upgrade Server Components• Intelligence Servers• Mobile Server**• Web Servers• App Servers• Configuration Wizard

Upgrade Repositories & Customizations• Metadata• Enterprise Manager• History and Stats• Web and Mobile Customizations• Log all upgrade times

Upgrade User Tools• Integrity Manager• Desktop Developer• Command Manager

**NOTE: Mobile client upgrade has special considerations depending on Enterprise or App Store client



Phase 4 : Test and Fix

Test Preparation• Align resources and responsibilities• Confirm availability of key

resources (Business and Technical)• Issue resolution process/policy

Test Execution• User Testing• Regression and Data Integrity• Customizations• 3rd party integrations

Verification• Review Test results• Apply environment

upgrades as needed• “Go/No Go” decision for

Production release



Non-Prod Upgrades• Execute step-by-step upgrade plan• Server Components• Repositories• Ancillary applications (Mobile,

Narrowcast)

Prod Upgrade• Execute step-by-step upgrade plan• Server Components• Repositories• Ancillary applications (Mobile,

Narrowcast)• Release Test Users (critical)• Go / No-Go Decision

Release and Monitor• Open System for Users• Monitor (including DSS Errors)• Use Sandbox to test any

anomalies• Review upgrade project

Phases 5 and 6: Upgrade Release and Monitor



• Disconnected from live system

• Copy of your Production MD

• Verify System Settings/Drivers

• Compare Current PROD to 10.x

• Most time spent in this stage

• Intensive User Testing

• Timeline creation for final upgrades

• Source for creating documentation

• Creation and test of automated scripts

• Integrity Manager tests

• Relieves stress

Why a Sandbox?

Test new version with no interference!


Documents, Flash and 10.xUpgrading existing Flash documents

Replacing Flash Widgets

Copyright © 2017 MicroStrategy Incorporated. All Rights Reserved .17

Flash

HTML5 is replacing Flash starting with MicroStrategy 10

HTML5

Documents, Flash and 10.x

• Flash is owned by Adobe and has fewer upgrades

• Adobe Flash Player must be installed

• Flash can run slowly on some platforms

• Flash is not supported on iOS

• HTML5 is controlled by a standards committee - World Wide Web Consortium (W3C) and can be developed by several developers.

• Flash Mode, Interactive Mode, and Express Mode have been depreciated in v10.x. Presentation Mode and Editable Mode are used to run the document

• Export to Flash has been depreciated in v10.x – unless an existing Flash document prior to v10.x has been run


Upgrading existing Flash documentsDocuments, Flash and 10.x

• 9.X Flash Documents will still open in 10.x but users will see the mouse over “deprecated”

• Flash and Interactive Run modes will still be the default “unless” saved as Presentation or Editable


• Dashboard visualizations are built with HTML5 and provide a more modern look and feel than graphs available in documents

• Documents provide more breadth of visualizations and more powerful design capabilities

Flash Widgets are still available in v10.x under the Insert menu. However MicroStrategy strongly encourages users to use HTML5 based alternatives

Replacing Flash Widgets


Integrity Manager, Command Manager

Example of a Data mismatch

Command Manager


• IM is designed to greatly expedite the time it takes to compare two different versions of the same project

• Ideal when test users are not available or time limited

• Great for Document testing/PDF compare

• Run Integrity Manager from your 10.x system

Integrity Manager


Results summary XML will look like this and identify issues. Formatting issue:Integrity Manager


Example of a Data mismatch Integrity Manager


Integrity ManagerReal world insight

• IM files can be large so save them locally to compare

• PDF and data comparisons are very CPU intensive especially when run on a workstation

• Remember to set Desktop User permissions on Source and Target

• Be cognizant of firewall rules

• Saving static versions of the report/document saves time

• Use the Default Prompt answer for hierarchy/element prompts

• MSTR Version 9.4.x and later: The Data Engine in 10.x has changed, which in some cases can generate differences in your existing data. Running integrity manager will identify if you have any affected documents. You can resolve the issue for affected documents by recreating them. - clarification


Configure Enterprise Manager data loads

Use to make bulk changes

Use to make bulk changes

Command Manager

• Enterprise Manager 10.2 is not dependent on Operations Manager and Health Center and can be controlled through MicroStrategy Command Manager

• TN273206: Best practices for configuration of MicroStrategy Enterprise Manager 10.x

• Perform various administrative and application development tasks by using text commands that can be saved as scripts. Add, delete, or update enterprise-level MicroStrategy data associated with large numbers of users and user groups


Upgrading your 9.x Cubes to PRIME

PRIME - Parallel Relational In-Memory Engine

Automatic Partition Attribute for MTDI Cubes


PRIME - Parallel Relational In-Memory Engine

Flexible schema and partitioned data

Linear scalability to 1,000s of CPUs Tightly-coupled

interactive exploration

PARALLEL RELATIONAL ENGINE

3x to 10x faster7x to 20x more users

IN-MEMORY


• Advanced options

• Multi-table Data Import

• Parallel loading

• Improved Dataset Join Behavior

PRIME Cubes


Automatic Partition Attribute for MTDI Cubes

• The automatic partition feature allows the Analytical Engine to select the partition attribute for the user• The Analytical Engine will choose the partition attribute that is a best fit for the loaded data

No Partition

Manually picked partition attribute

(which in this case is not ideal)

Automatically Selected Partition Attribute

% Improvement when selectingthe right partition attribute

1. Aggregation (Lowest Level) 285.88 274.41 83.53 29.22%2. Average Aggregation 205.09 820.94 60.76 29.63%3. Count on Attribute 199.57 815.7 59.65 29.89%4. Partition parent 50% 135.88 706.977 38.96 28.67%5. Partition parent 90% 251.23 1288.93 71.01 28.26%6. Metric Qualification (No Aggregation) 17.89 17.38 4.83 27.00%7. Non Aggregation Metric 218.94 1025.52 62.97 28.76%

An example of the benefits of using the automatic partition attribute feature:

Notes:The test runs against a 30 GB Cube with 180 Million Rows (TPCH Benchmark Cube).


iServer hardware:16-vCPU hardware

• RH Enterprise 6.3• 2 x Intel Xeon X5560 @ 2.8GHz• 144GB RAM• 248 SPECint_rate 2006

MSTR 10 vs. 9.4.1 – In Memory Analytics (Linux)

In Memory Analytics which involves typical reports.Designed specifically to replicate the cube query characteristics typical among MicroStrategy’s enterprise BI customers based on customer feedback through tech support.

The Kilocycles represent the query load (1 Kilocycle = 1000 user executions per hour)

0

1

2

3

4

5

60 5 10 15 20 25 30 35 40

Aver

age

Res

pons

e Ti

me

(sec

)

Power Rating (KiloCycles)

MSTR10 cube 8-partition MSTR10 cube non-partition

941 OLAP cube

Analytic complexity• Cube returns data 50 million rows and 45 columns• 57 view reports returned data:

• Range: 1 to 2,901,706 rows• Average: 56,257 rows

Data size:• Cube (8.25GB)


Web Customizations Upgrade Plug-in Architecture andthings to consider


Plug-in Architecture

Framework for plugging in customizations as modular piece of software into MicroStrategy web

Advantages• More extensible and customizable Web• Offers transparency in customization code• Facilitates portability of customization• Minimize impact on upgrades


Pre-requisites Upgrade Tools

Things to consider

Upgrading environment with customization needs a few basic things

• 10.x environment with similar objects as 9.x• Common integration points as 9.x (LDAP/SSO, BPM engine, etc.)• Web applications hosted on a common web environment• Effective regression test plan

• Eclipse with relevant JRE• MicroStrategy 10.x customization editor• WinMerge (for windows) or FileMerge (for Mac)


1. Obtain/Install vanilla copy of MicroStrategy 10.x web

2. Connect to MicroStrategy 10.x I-Server

3. Ensure OOTB reports/dashboard interaction is ok

4. Copy existing 9.x customizations under the plugin folder

5. Recompile Java code from source in plugins

6. Adjust customizations/plugins based on 10.x features

7. Test. Test. Test.

Things to considerCommon Upgrade Steps


Differences between “Feature” and “Platform” release

Agile releases

Which suits you best?


Agile Releases

36

A release every 3 months

Agile Releases ensures instant access to new features and functionality

• Improved means to incorporate feedback from customers

• Time-boxed schedules for features to be released frequently

• Ensures predictability in releases

• Instant access to latest features


Platform release

Which will suits you best?

Feature release

37


Platform release

Which suits you best?

Feature release

Platform versus Feature Release

• Widely adopted for most of our customers

• Do not anticipate adding new features to a Platform Release

• We will continue to issues patches and hotfixes for three years after the designation

• Expect Platform Releases to be made generally available about every 18 months

• Intend to make Feature Releases available about every 3 months

• Include new features and functionalities from the prior release

• Intended for customers that are willing to upgrade more frequently to receive our latest features and functionally

• Deliver enhancements to existing features, and defect corrections

• Incorporate all applicable defect corrections made in prior releases, hotfixes, and patches

• Feature release will be supported for 6 months after release


MicroStrategy Upgrade Tips Time Saving Tips


• Use Configuration Wizard!

• In LINUX increase “vm.max_map_count=5242880” (5.24MB)(see Install and Config Guide p.50)

• Use Silent Installation Script. “Options.txt” Slight change per environment

10 Upgrade Time Saving Tips


• Don’t forget to upgrade your drivers to 64-bit

• Can’t set the Server Definition without doing this first



• Use Command Manager to script any changes that have to be added to the new environment

• It is not necessary to perform the “Lean Objects Migration” if you do not have time

• Check “Update the Remaining Projects”

• 2 new upgrades for Cubes



Questions or Comments?Contact: [email protected]


Thank You

How to Upgrade Your Applications From 9.X to 10 PPT...Title How to Upgrade Your Applications From...

Documents

Transcript of How to Upgrade Your Applications From 9.X to 10 PPT...Title How to Upgrade Your Applications From...