Make installations, migrations and upgrades digestible with Patterns Books
Everybody running business analytics environments face it: the horror of necessary upgrades or migrations. It happens when you vendors provide new versions of your BA platforms. Luckily I would say; software environments change, data source types evolve and users require new or adjusted functionality that vendors apply in their software.
Nevertheless these upgrades and migrations often cause headaches upfront with your IT Management: downtimes of the platforms that users don’t agree upon, risky migration projects, unforeseen outcome and a lack of a guided approach are the core reason for them to take an aspirin. Try to plan and budget that, and you know why the feel this way.
Deploying an Enterprise Analytics platform in most cases is a bit more than just installing the software on a single machine. Think about additional activities like:
Performance tuning an load balancing
Manage enterprise scalability and redundancy by installing the platforms over multiple machines or multi-tenant
Manage and apply your governance: integrate your installation or migration into existing security infrastructures
Configuration: configure your company’s existing software like application-, web- or database servers
In case of migrations and upgrades: adapt a plan and workflow for your existing analytics applications, reports, cubes, views or storyboards. Which ones will be migrated, which ones are redundant given new functionalities or which ones require re-development
Reverse proxy set – up and firewalls
Communication plans to developers and users
Stress testing and performance checks of the new environment
…. many, many more ..
Luckily some of the leading analytics software vendors help their customers managing the process of enterprise scaled installations, migrations or upgrades. They provide end-to-end instructions, workflows and check-lists that may vary for different operating systems, application server vendors, and database vendors. This is done in scenarios which we call patterns.
SAP is class leading when it comes to providing highly detailed patterns to their customers. Their so-called Pattern-Books are workflow oriented step-by-step guides that literally take you by the end guiding either an installation, upgrade, update or migration. I have seen several leading enterprises using these Pattern-Books and they all talk positive primarily mentioning:
Predictable and reliable time, effort and cost estimations
Less risk to unsuccessful migrations and upgrades
Expectation management towards users and management is way better using the books
What is the difference between upgrade, update and migration?
So do you know honestly what the difference between an update, upgrade, and migration is? Ah, of course you know :-) Let me summarize for you one.
Below you will find an explanation of commonly used phrases related to installing CodeTwo products.
Version of the program
The version of the program consists of 3 numbers separated by dots, e.g. CodeTwo Exchange Rules 2007 2.2.7. The version number is always provided on product download pages Fig.1.
An upgrade is when you reinstall the application using a newer version that has a higher first figure e.g. an upgrade from 1.2.3 to 2.0.0. Upgrades are typically payable and it is safe to assume you should not install a version with higher first figure without confirming your eligibility to such action with our Support team.
If you were asked by CodeTwo Customer Support to reinstall the software with the newest available installer from our website and were not instructed specifically to do an upgrade, please make sure you are using the installer with the same first figure as the version you have purchased your license for, i.e. please perform an update, see below.
An update is when you reinstall the application using a newer version that has the same first figure e.g. an update from 1.2.3 to 1.3.0. Updates are free of charge for all customers – a valid support contract is not necessary.
You should update your installation on regular basis to make sure you always have a version of the software with all new features included and all known bugs removed.
A migration is when you stop using an application in order to move to another product on preferential terms e.g. you drop CodeTwo Exchange Rules 2007 in order to migrate to CodeTwo Exchange Rules PRO. A migration is always payable but priced less than repurchasing.