imis upgrades: planning & overcoming obstacles...imis 15.2 hardware requirements imis 15.2...
TRANSCRIPT
Monday, November 28, 2016
3:30 PM – 5:00 PM
Ian Evans, President and CEO | E-Tech
Alina Gavrilyuk, E-Tech Cloud for iMIS Team Lead | E-Tech
Michael Wong, E-Tech Cloud for iMIS Technical/Database Administrator | E-Tech
iMIS Upgrades: Planning & Overcoming Obstacles
iMIS Upgrades: Planning & Overcoming Obstacles
Planning your iMIS upgrade? Discover all the requirements you need to be aware of when upgrading. Topics covered include hardware and software requirements, 3rd party integrations and customizations, and testing. Learn tips from fellow iMIS users to ensure your upgrade is seamless.
Ian Evans, President and CEO
As Founder and President of E-Tech, I’m charged with keeping the company moving forward, from business development, financial management, to project management and rolling up my sleeves for the hands-on technical work that goes along with the day to day operations. My vast work experiences brings together a balance of both business and technology: before starting E-Tech, I worked for several years as an IT Manager for a not-for-profit, also worked for ASI for 3 years as Manager of Hosting Operations (ASI Canada), Since then, I have been serving the not-for-profit industry for over 20 years. I have been doing iMIS upgrades and installations for a very long time, and I was involved with the first iMIS installation in Canada.
The iMIS Upgrade Project
The iMIS Upgrade Project is based on the five phases of project management, the life cycle provides a high-level view of the project, these phases are the roadmap to accomplishing it.
• Project Conception and Initiation
• Project Definition and Planning
• Project Launch or Executions
• Project Performance and Control
• Project Close
The iMIS Upgrade Project
Project Concept & Initiation
An idea for a project will be carefully examined to determine whether or not it benefits the organization. During this phase, a decision making team will identify if the project can realistically be completed.
• Define project at a broad level
• What is the business need?
• What other areas of our technology connect with iMIS?
• Does an upgrade benefit the organization?
• Can we realistically complete this project?
• Should we proceed?
iMIS Features
Project Definition & Planning
This phase is key to successful project management and focuses on
developing a roadmap that everyone will follow. This phase typically begins
with setting goals.
A popular method for setting goals is C.L.E.A.R.:
Collaborative – The goal should encourage employees to work together.
Limited – They should be limited in scope and time to keep it manageable.
Emotional – Goals should tap into the passion of employees and be
something they can form an emotional connection to. This can optimize the
quality of work.
Appreciable – Break larger goals into smaller tasks that can be quickly
achieved.
Refinable – As new situations arise, be flexible and refine goals as needed.
Here are some of the documents a PM will create during this phase to
ensure the project will stay on track:
Scope Statement
Work Breakdown Schedule (WBS)
Milestones
Gantt Chart
Communication Plan
Risk Management Plan
Project Definition & Planning
Q4 2015 New Features & Enhancements
http://help.imis.com/q42015/Q4_2015_New_Features_and_Enhancem
ents.htm
New Features
• Redesigned and responsive Staff site to have a
modern look and feel
• iMIS SDK for better integration of external
applications
• Access to purchased website content for
downloadable electronic products
• Offer premiums for donation gifts
• Assign source codes for tracking marketing
efforts
• Join Now extended for Organizations to support
Trade Associations
• Installment payments for flexible donation
options
• New iMIS Documentation responsive Helpsites
Additional Enhancements
• Implementation
• Certification
• Commerce
• Community
• Events
• Fundraising
• Marketing
• Membership
• RiSE
• Settings
Michael Wong, E-Tech Cloud for iMIS Technical/Database Administrator
I have been with the iMIS Cloud team for just over 8 months. l have fast-tracked quickly from handing iMIS support tickets to now handling many of our complex iMIS installations, upgrades and migrations.
iMIS Environment Pre-planning
What to consider for your iMIS?
• Compatibility with other software
• What about older software?
• Future Proof
• Don’t become obsolete
• Growth
• Plan ahead what might be required down the road
iMIS OS / SQL Server Comparisons
Which Operating System?
iMIS 15.1.3 is supported on: iMIS 20.2.26 is supported on:
-Windows Server 2003 R2 SP2 -Windows Server 2008 R2 SP1
-Windows Server 2008 SP2 -Windows Server 2012
-Windows Server 2008 R2 -Windows Server 2012 R2
*Is the operating system compatible with other software?
Which SQL Server? (Is it compatible with your applications?)
iMIS 15.1.3 supports iMIS 20.2.26 supports
-SQL 2005 SP3 -SQL 2008 SP3 and 2008 R2 SP3 (32-bit and 64-bit)
-SQL 2008 SP1 (32-bit and 64-bit) -SQL 2012 SP2
• -SQL 2014 SP1
iMIS 20.2 Hardware Requirements iMIS 20.2 Hardware Requirements
Minimum
Hardware
• 100/1000 Mbps network connection between database server host and
all appservers and iMIS desktop clients
• 2 GHz Intel Pentium 4 or compatible processor (64-bit processors must
support Intel 64 or AMD64 architectures. Some Intel Xeon server
processors prior to 2007 might have issues with running iMIS desktop on
64-bit Windows Vista or Windows 7)
• 2 GB of RAM
• 3.2 GB of disk space for a full/custom install. 1.8 MB for desktop
install/upgrade (InstallShield might under-report disk space needed)
• An additional 2 GB of disk space on the C: drive (for temporary files).
When upgrading, an additional amount of C: drive disk space on the
database server that totals twice the size of your database
• Application Server: additional disk space for publishing and indexing your
contact files for search (for example, 275K contacts=1GB, 2M
contacts=7.56GB)
• Display with 1024x768 (XVGA) minimum resolution
iMIS 20.2 Hardware Requirements
iMIS 20.2 Hardware Requirements
Operating
Systems
• Servers: Windows Server 2008 R2 SP1 and 2012 (32-bit and 64-bit,
Standard/Enterprise/Datacenter editions only)
• iMIS desktop: Windows Vista SP2, Windows 7 SP1, and Windows 8 (32-
bit and 64-bit), installed as and set to run as Administrator, with non-Aero
theme (see note above for 64-bit Intel Xeon server processors)
Databases • Microsoft SQL Server and Express Edition 2012
• Microsoft SQL Server and Express Edition 2008 SP3 and 2008 R2 SP2
(32-bit and 64-bit) (Note: 2008 R2 is not backwards compatible)
Appservers • Microsoft .NET Framework 4.0 (ASP.NET)
• SQL Server 2008/2012 Tools
• Microsoft Internet Information Services (IIS) 7.5 or 8
• Apache Lucene 4.1 Indexing and Search (included with install
http://docs.imis.com/20.0/index.htm#!systemrequirements.htm
iMIS 15.2 Hardware Requirements
iMIS 15.2 Hardware Requirements
Minimum
Hardware
• 10/100 Mbps network connection between database server host and all
appservers and iMIS Desktop clients
• 2 GHz Intel Pentium 4 or compatible processor (64-bit processors must
support Intel 64 or AMD64 architectures; some Intel Xeon server
processors prior to 2007 may have issues running iMIS Desktop on 64-bit
Windows Vista or 7)
• 2 GB of RAM
• 3.2 GB for a full/custom install; 1.8 MB for Desktop install/upgrade
(InstallShield may under-report disk space needed)
• An additional 2 GB of disk space on the C: drive (for temp files); and
when upgrading, an additional amount of C: drive disk space on the
database server that totals twice the size of your database.
• Application Server: additional disk space for publishing and indexing your
contact files for search (e.g., 275K contacts=1GB, 2M contacts=7.56GB)
• Display with 1024x768 (XVGA) minimum resolution
iMIS 15.2 Hardware Requirements iMIS 15.2 Hardware Requirements
Operating
Systems
• Servers: Windows Server 2003 R2 SP2, 2008 SP2, and 2008 R2 SP1
(32-bit and 64-bit, Standard/Enterprise/Datacenter editions only)
• iMIS Desktop: Windows Vista SP2 and 7 SP1 (32-bit and 64-bit), installed
as and set to run as Administrator, with non-Aero theme (see note above
for 64-bit Intel Xeon server processors)
Databases • Microsoft SQL Server and Express Edition 2012
• Microsoft SQL Server and Express Edition 2008 SP3 and 2008 R2 SP2
(32-bit and 64-bit) (Note: 2008 R2 is not backwards compatible)
• Microsoft SQL Server and Express Edition 2005 SP4 (Note: the shipped
Demo DB is not supported on SQL Server 2005)
Appservers • Microsoft .NET Framework 4.0 (ASP.NET)
• Microsoft SQL Server 2005/2008/2012 Tools
• Microsoft Internet Information Services (IIS) 6, 7, or 7.5
• Microsoft Windows Indexing Service (see Preparing all servers and
workstations)
http://docs.imis.com/15.2/index.htm#!systemrequirements.htm
Alina Gavrilyuk, E-Tech Cloud for iMIS Team Lead
I have been with E-Tech since November 2014, during my time with E-Tech, I have been involved with over 100 installations, migrations and upgrades of iMIS all the way from iMIS10 to iMIS15 to iMIS20, for many of our clients. I started out as a database administrator, then was promoted to Team Lead - iMIS Cloud Services during the spring of 2016.
Consider iMIS Version iMIS Production General Availability (GA) release
• Main release for the year
• Hotfixes will be available throughout the year.
iMIS Interim Update releases
• Issued multiple times throughout the year
• Allows ASI to provide new features and fixes to the customers before the GA release
• Pretty stable and supported IMIS version that can be upgraded.
Considerations:
• Do not go through the same regression testing procedure as GA releases
• No Hotfixes. If customer come across a hotfix-worthy problem install the next interim upgrade to get the fix
iMIS Early Adopter (EA) release
• Before GA release
• Gives customer a chance to use new features.
• Provides final feedback from customers to ake any changes that ASI think are required before GA
All releases:
• Supported by ASI tech support
• Upgradable to the future version
Hot Fixes:
• Keep an eye on available new hotfixes or ask your IMIS support. Hotfix is not an iMIS upgrade and could be easily scheduled and applied afterhours. It resolves knowns issues and bugs reported by other companies.
Project Definition and Planning
Budget
• Software costs – SU fees up-to-date, license key, new products, new modules?
• Hardware costs – new servers, more RAM, SQL upgrade?
• Third party integrations?
• If on Public View, a new RiSE site must be ready to go!
• Consider long term budgeting instead of ‘for now’
Timeline Includes
• Server work
• Resolve any licensing issues
• Staff testing time
• Who is responsible for what?
• Where are the stop/break points?
• What’s the roll back plan?
• Who is testing?
Build The Team
Project Execution & Launch: Testing
Project Execution & Launch: Testing
This is the phase where deliverables are developed and
completed. This often feels like the meat of the project
since a lot is happening during this time, like status
reports and meetings, development updates, and
performance reports. A “kick-off” meeting usually marks
the start of the Project Execution phase where the teams involved are informed of their responsibilities.
Setting Up Development Environment
• Good time to Upgrade Hardware and OS
Time & Cost savings
• Upgrade Database
10.6 15.1.3 20.2
Upgrade queries
• Make sure there is no empty ST_IDs in Orders
• Resolve all Duplicate Records (Meetings)
• Refresh the metadata for all views
Check for custom triggers (Name table)
Update iMIS License (if required), OMNIS key
• iMIS Reconfiguration Tool
Allows iMIS to run with database owner sql access
Don’t forget make backups throughout the process!
Setting Up Development Environment • Third Party Products
• TaskCentre
• Quick Books
• CSA
• Communicate
• CSI software
• iMerge, iImporter, iEmail …
• INFORMZ
• Crystal Reports
• Access Reports
• SQL Jobs
• Scheduled Tasks on the application server
• SSL certificate
• Terminal Server or local iMIS installation
E-Tech Hosting Production Environment
End Users:
• iMISDesktop
• CrystalReports
• Third party
software
• User Files
Application server:
• iMIS PROD instance
• iMIS TEST instance
SQL Server:
• IMIS_PROD Database
• IMIS_TEST Database
Step 1: DEVELOPMENT Environment
End Users:
• TEST TEAM
New DEV APP server:
• IMIS DEV Instance
SQL Server:
• IMIS_DEV Database
DEV Site
Troubleshooting Publishing (1)
1. Check pre-requisites and required roles, features and additional components are installed.
System Requirement - http://docs.imis.com/20.2/#!systemrequirements1.htm
Additional Components - http://docs.imis.com/20.2/#!installingadditionalrequiredcomponents1.htm
Roles and Services - http://docs.imis.com/20.2/#!rolesandroleservices.htm
2. Edit web.config file
Next, edit the web.config located under the C:\AsiPlatform\Asi.Scheduler_xxxx folder and make sure the publishing server code matches the one defined in RiSE > Maintenance > Publishing Servers.
3. Verify asi.scheduler application loading
Verify that the asi.scheduler application loads successfully by browsing to the asi.scheduler application in a browser on the server. Typically that would be something like http://localhost/asi.scheduler_xxxx (*note - replace this value with the value of your asi.scheduler name). If that loads successfully, a generic Microsoft ASP.NET help page will appear.
4. Verify the dbo user in the iMIS database is mapped to a valid SQL login.
5. Verify no null rows in name table
Make sure there are no null values in 'name.last_updated' in the name table. If update isn't required then rebuild the search index.
6. Check if you have orphaned SQL Query Notifications for the SQL Service Broker in the iMIS database.
• If you only have 1 publishing server, then you should only have 1 SQLQueryNotification under Service Broke > Queues and under Service Broker > Services in SSMS under the iMIS database. In SSMS, expand the iMIS database > Service Broker > Queues. If you only have one publishing server, then there should be only one SQLQueryNotificationService listed here.
• If that is the case, then delete the SQLQueryNotifications and iMISPublishService Broker in SSMS. Then run the DB Maintenance > "prepare imis database" to recreate the SQL Broker services. Then recycle the AsiSchedulerPool app pool and enable the AsiScheduler application (ie: browse http://localhost/asi.scheduler_xxxx on the iMIS app server).
Troubleshooting Publishing (2)
7. Update name table and rebuild the lucene index
• After updating the name table and rebuilding the lucene index, make sure this query returns a value and that it is being updated:
select ParameterValue, * FROM SystemConfig WHERE ParameterName LIKE 'ContactsPublishing%'
• If there's a large number of records
In cases where there is a large number of contact records (name records), run the following to update the ParameterValue to tomorrow's date to prevent contacts from indexing today:
declare @date as
datetime
set @date = DATEADD(day, +1, GETDATE()) update SystemConfig set ParameterValue=
convert(nvarchar(50), @date, 121) where ParameterName like
'ContactsPublishing%'
8. Check Lucene index for corruption
• Check to see if the Lucene index is corrupted. Check the ..\indexServiceProtected\Search\Lucene folder. If some files are larger than 20MB, the index might be corrupted. Another clue is to get an "Object reference not set to an instance of an object" error when publishing. Rebuild the Lucene search index:
• http://docs.imis.com/20.2/#!deletingcommunitypostsandrebuildingthesearchindex1.htm
Troubleshooting Publishing (3)
9. Check "temp" ParameterValue path in SystemConfig table and iMIS database
• Make sure the "temp" path in the SystemConfig table in the iMIS database is correct:
SELECT * FROM SystemConfig where ParameterName = 'TempDirectory‘
10. Check for orphaned records in the TaskQueue Table
Select count(*) from
TaskQueue
Select count(*) from TaskQueue where TaskQueueId not in (select TaskQueueId
from TaskQueueTriggerDetail)
• If the above returns a significant amount of rows for your db size or rows referencing unused publishing server codes then make a backup of the db and run the following:
delete from TaskQueuePublishDetail
delete from TaskQueue
where TaskQueueId not in (select TaskQueueId from TaskQueueTriggerDetail)
Step 2: TESTING (Client)
Test all components
• iMIS Desktop
• Reporting
• RiSE Sites
Staff site
Member/Event sites
• Integrated websites
• SSO to third party
• Third party software
• Third party data integration
If necessary, run the upgrade on the test database again
Step 2: TESTING
Step 3: 24 Hour Go Live Communication and Support After
• No Weekend Go Lives!
• Take a deep breath and make sure you have a good
backup!
• Stop all:
• Jobs
• Websites
• Outside access to the database
• If you’ve done a test upgrade, the actual upgrade should go relatively smoothly. All that will need to be done is upgrade the database!
• Use your testing plan/checklist to go through the production (live) systems.
• Control the controllable factors. Not everything is an emergency.
• Panicking is counterproductive.
• Communication – pick up the phone!
Project Closure & Debrief
•Punch list of items that weren't completed
•Plan for addressing out of scope items found during upgrade
•Budget recap
•Communication touchpoints
•Finalize any documentation
Resources
Resources
iMIS Consultant / ASI / Authorized iMIS Solutions Provider
iMIS Tutorials & Enhancements iMIS Tutorials:
•Did you know that there is a YouTube channel dedicated to tutorials
about using iMIS?
On youtube.com, search for “iMIS Tutorials” and subscribe to the
playlist so that you will know when new videos are posted. If you would
like to propose a topic that would be helpful in video, email
iMIS Enhancements:
Q4:
http://help.imis.com/q42015/Q4_2015_New_Features_and_Enhancem
ents.htm
20.2:
http://docs.imis.com/20.2/#!202newfeaturesandenhancements.htm
SQL:
•http://www.networkworld.com/article/2453561/microsoft-subnet/the-
difference-between-end-of-mainstream-support-and-end-of-extended-
support.html
•https://www.microsoft.com/en-us/cloud-platform/sql-server-comparison
Q & A
THANK YOU TO OUR SPONSORS
FOUNDING PARTNER
PLATINUM PARTNERS
GOLD PARTNERS
SILVER PARTNERS
