UPGRADING IMIS NEWLIN

Transcription

1 UPGRADING IMIS NEWLIN

2 AGENDA UPGRADING IMIS, THE TECHNICAL PERSPECTIVE Want to be on the latest greatest release of imis but not sure where to start? This technical session will cover what you need to know from both a software and hardware perspective - including what hosting might offer for your organisation. We wrap up with things you need to know before you take the plunge.

3 AGENDA WHAT WE LL COVER Before you begin Choosing a version Server architecture Web & app vs web/app Hosting options imis Ecosystem Migration considerations Overall upgrade approach Third party software Custom integrations Best practice Top tips References Questions

4 INTEGR8TIV YOUR IMIS & BUSINESS SYSTEMS PARTNER Integr8tiv assists imis customers to get more from their business systems Authorized imis Solution Provider with unparalleled imis experience imis Certified Professionals and Certified imis Extension Developers Founded in 2012, now with 5 full time imis dedicated consultants Located in Melbourne, servicing customers in Asia Pacific and world wide

5 INTEGR8TIV YOUR IMIS & BUSINESS SYSTEMS PARTNER Services include: Award winning RiSE websites imis Dashboards and reporting invoice and receipt automation & other process automation imis upgrades imis training and support Staff site and customer portal development iqa, Crystal and SSRS reporting Business Intelligence reporting Financial Integration, inc MYOB and Xero System Health and usage reviews IT strategy and road maps Passbook member cards Marketing automation and marketing Systems integration 3rd party CMS and imis integration LMS integration Everything imis

6 INTRODUCTION First installed 10.6 back in 2003 Upgrades all the way through to current versions Introduction of web, IQA s, Business Objects, API s, web services Increase in hardware & complexity (300) Decrease in hardware & complexity ( ) Less downtime due to website integration & process automation Greater functionality and flexibility Migration to the cloud Currently average 1 upgrade every 1 2 months

7 ALWAYS START WITH AN AWESOME QUOTE WHO SAID THAT? Every upgrade will contain hurdles, the question is how many and how high Wise grasshopper

8 BEFORE YOU BEGIN Read the imis documentation imis.htm Know current and plan future your architecture Consider hosting options Audit related software and suppliers Plan and document your upgrade approach, create test plans

9 VERSIONING WHAT IS THE DIFFERENCE BETWEEN GA, EA & INTERIM RELEASES? GA General Availability EA Early Adopter GA is the main release for the year, generally 1 per year Fully tested with hotfixes available throughout the year EA is the preview of GA, available for customers to test Users provide feedback and changes are made before GA version Interim updates happen throughout the year Allow new features or fixes to be deployed prior to annual GA Don t go through same regression testing as GA, but are stable and supported and can be upgraded No hotfixes issued, so to fix bugs an upgrade is required

10 CHOOSING A VERSION IMIS 20.2.XX Latest interim version is Latest Generally Available version Q Other interims include and ASI recommends current interim update (e.g ) and lots of testing What version is right for you? known issue with public user credentials page Work around is to change to casual/full, modify, change back to public Installing multiple versions on one server Consider carefully and test on a non live server

11 HOSTING OPTIONS Internal Physical vs Virtual ASI Cloud Shared Dedicated virtual server Other cloud Amazon Web Services (AWS) Microsoft Azure Google Cloud Platform (GCP)

12 SERVER ARCHITECTURE 3 separate servers to consider: Database Server Application Server Web Server Most common architecture approach is: 1 database server 1 combined web & app server Ability to install a separate stand alone web server was removed and recently re-added to the product (version /9) Multiple web & app servers requires publishing considerations

13 IMIS ECOSYSTEM

14 MIGRATION CONSIDERATIONS Manually migrate the following: Custom reports Custom RiSE files (docs, images, themes, master pages) Other imis related files (e.g. GL Int folders/files) Non imis related files Third party applications Task Centre tasks Informz db access Non imis related applications (e.g. GL, reporting, MS Office etc.) Existing db backup files Non imis databases User configuration RDP

15 ASI UPGRADE - DOCUMENTED APPROACH Before you begin Upgrade Post Upgrade Tasks Upgrade existing websites imis.htm

16 BEFORE YOU BEGIN Review system requirements Review install and upgrade changes Install additional required components Prepare the application server Prepare databases for an upgrade (optional) Refresh metadata (optional) Delete Database Engine Tuning Advisor Index Prepare to upgrade your websites _begin_your_upgrade.htm

17 UPGRADE Download the imis product image Have all users log out of imis Uninstall imis Temporarily disable tools and settings Run the imis setup.exe Upgrade additional instances of imis MIS.htm

18 POST UPGRADE CHECKS Upgrade the On Behalf Of role Upgrade content items Upgrade website master pages Upgrade system alerts Redirect to the virtual directory URL Test access to installed components

19 UPGRADE EXISTING WEBSITES Review website upgrade strategy Update sites that have page errors Upgrade older sites existing_websites.htm

20 COLLATION SEQUENCE SQL Collation Sequence: SQL_Latin1_General_CP1_CI (sort order ID 52), which is the default for the EmptyDB and DemoDB provided with imis. If your SQL Server default is different, reinstall SQL Server with the correct collation before installing imis. imis will now let you upgrade with a different collation sequence Difficult to change this later Get it right at the start

21 PRE UPGRADE CHECKS Ensure that your server environment is ready for the upgrade: Confirm minimum system requirements Server(s) have all standard and additional components installed and configured Complete a test upgrade run on the same server environment and architecture Clean data Close all batches before running the upgrade Ensure there are no duplicate registrations for the same events, if so close events Run pre-upgrade steps from imis site: pgrade.htm#preparing_databases_for_an_upgrade Make sure that all users are logged out from imis and server, close all connections Take a database backup Check there is no QAS path stored in the system parameters table, if so remove it as it wipes out the server path variables which will cause system issues Ensure no user is logged on to your server, if necessary logged them off Now ready to upgrade but don't forget to run the process with 'run as admin' option

22 OVERALL UPGRADE APPROACH Download software from ASI website Client support - Releases OR Request interim release from ASI Read release notes New functionality Known issues ASI regarding known issues Prepare servers Run pre upgrade steps Run test upgrade Prepare database DB Maintenance Tool installed with imis

23 DB MAINTENANCE TOOL Login as system admin Allows you to complete a bunch of adminy type functions Prepare imis database Purge unused contacts & users Sync net contacts

24 OVERALL UPGRADE APPROACH Publish sites & content Configure IIS Bindings App Pool config SSL server signed is fine for testing migrate or reinstall? Test imis client / staff site / public sites Report & fix issues Define issue reporting process Plan live upgrade Run live upgrade Post deployment support

25 POST UPGRADE STEPS Run DB Prepare, Purge unused contacts & users, Sync contacts in the DB Maintenance Tool Restart web & app server Ensure imis Desktop URL is correct imis Desktop & Staff Site should now work Do the following in RiSE to ensure website are operating correctly: clean up publishing server publish a page with the re-generate option to ensure that publishing is working clean Lucene index (delete) publish parent content folder with re-generate option ensure that all RiSE websites are correctly configured (imis website URL, IIS)

26 WHERE S THE CLIENT GONE? By default the new Advanced Account Console is shown Switch back to the standard client by changing the URL:

27 WHERE S MY IQA S? IQA options on the desktop client are no longer visible by default Can be easily accessed on the staff site Can also be easily added back in to the imis desktop after the upgrade SMR ASI me

28 MANAGING YOUR WEBSITE DURING AN UPGRADE imis integrated websites will be offline for a period of time Put up a maintenance mode web page Provide contact details Ideally a time when site is back up Do during a Third party Single Sign On sites may also be down if they are relying login page Think about SEO and 301 redirects if changing web sites

29 MANAGING CUSTOMISATIONS & MODIFICATIONS SQL Stored Procs Triggers Other objects Scheduled Jobs Custom integrations Reads Writes RiSE Content pages Documents Themes Master pages Shortcuts IQA Embedded C# no longer supported Reports

30 KATI S TOP 3 UPGRADE TIPS KATI RETI, SENIOR CONSULTANT INTEGR8TIV Kati s Top 3 Upgrade Tips 1. Try to avoid test upgrade run on your live server environment. Although imis 20.2 allows mixed server installations on the same server architecture it is often hard to separate test upgrade related issues that may / may not impacted the live environment. 2. After successful upgrade run don't forget to run the DB Prepare process in DB Maintenance tool. This will re-create the necessary backend SQL users and without that you may receive logon errors in imis Desktop 3. Update your publishing server details. Ensure you have the correct code and path, remove any redundant old publishing server details BEFORE you republish the parent folder in RiSE.

31 BEST PRACTICE TIPS & TRICKS Separate out upgrade vs enhancements Try to phase the tasks as much as possible (avoid the big bang approach) Run the upgrade at least once in a test environment which is as close to live replica environment as possible Backup everything (db, Net folder, other files, server image, TC tasks, SQL jobs) Test everything Have a rollback plan There s a point where this becomes impossible Check collation sequence upgrade won t fail but some functionality will 2 step required on pre (use SQL 2008 box to get to first, then upgrade on SQL 2012 or 2014) Recommend running upgrades on a separate server for now

32 UPGRADE STRATEGY Have one Plan to upgrade every 1 2 years depending on the benefit to your business Understand what is coming and determine if there is a business case for your organisation Try and stick to it Skipping upgrades to save on money can sometimes be a false economy Keep up do date on latest software, get access to what you are paying for Consider external support If your staff only do this once every 2+ years consider outsourcing the project to those who do it every month This allows your internal staff to focus on day to day operations, rather than rare/one off tasks Distributes knowledge of your imis ecosystem to third party to mitigate risk

33 FUTURE OF IMIS UPGRADES? Multiple versions on the same server Continuous delivery & less downtime Continuous Delivery (CD) is an approach in which teams keep producing valuable software in short cycles and ensure that the software can be reliably released at any time. It is used in software development to automate and improve the process of software delivery. Dev Ops approach by ASI DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support. Less user and third party involvement Clearer and more defined release scheduled

34 REFERENCES ASI documentation (Q4 2015) MIS.htm NiUG Member Community Shared

35 QUESTIONS & CONTACT DETAILS Newlin Jolme

36 WITH THANKS TO OUR SPONSORS NIUG DISCOVERY CONFERENCE