XMPro BPM
| Version | Minimum OS Versions | Minimum SQL Versions | Minimum .Net Version | Minimum IE Versions | Minimum iOS Versions | Dates | Status | New and Amended Process + Report Configurations |
| 6.0 | Windows 2008 R2 | SQL 2008 | 4.0 | 8 | 7 | 04-2012 | Archived: 01-2015 | – |
| 6.05 | Windows 2008 R2 | SQL 2008 | 4.0 | 8 | 7 | 08-2013 | Update 5 Released 10-2014
Maintenance: 07-2014 : 02-2016 Archived: 02-2016 |
– |
| 6.1 | Windows 2008 R2 | SQL 2008 | 4.0 | 8 | 7 | 07-2014 | Update 5 Released 03-2016
Maintenance: 09-2015 : 08-2017 Archived: 08-2017 |
Limited |
| 6.5 | Windows 2012 | SQL 2012 | 4.5.2 | 9 | 7 | 08-2015 | Maintenance: 02-2017 : 07-2019
Archived: 07-2019 |
Full Support |
| 6.6 | Windows 2012 | SQL 2012 | 4.5.2 | 9 | 7 | 02-2017 | Maintenance: 07-2019
Update 3 Released 06-2019 |
Full Support |
| 6.7 | Windows 2016 | SQL 2016 SP1 | 4.7.2 | 11, Edge | 7 | 07-2019 | Released |
Subscription Manager
| Version | Minimum OS Versions | Minimum SQL Versions | Minimum .Net Version | Dates | Status |
| 1.0 | Windows 2008 R2 | SQL 2008 | 4.5.2 | 09-2017 | Archived: 12-2018 |
| 2.0 | Windows 2012 | SQL 2014 | 4.5.2 | 06-2018 | Maintenance: 10-2018 : 06-2019
Archived: 06-2019 |
| 2.1 | Windows 2016 | SQL 2014 | 4.5.2 | 10-2018 | Maintenance: 06-2019
Released |
| 2.2 | Windows 2016 | SQL 2016 SP1 | 4.6.1 | 06-2019 | Released |
Data Stream Designer
| Version | Minimum OS Versions | Minimum SQL Versions | Minimum .Net/ .Net Core Version | Dates | Status |
| 2.1 | Windows 2008 R2 | SQL 2008 | 4.5.2 | 09-2017 | Archived: 12-2018 |
| 3.01 | Windows 2012 R2 | SQL 2014 | 2.1 (.Net Core) | 06-2018 | Maintenance: 10-2018
Released |
| 3.02 | Windows 2016 | SQL 2016 SP1 | 2.1 (.Net Core) | 10-2018 | Released |
Approach of new releases and service packs
Releases
Current Subscription Manager Versions: 2.2, 2.1
- Generally 1 per year
Current Data Stream DesignerIs a model-driven approach to connect, transform and action real-time “streaming” data in a visual, drag and drop manner. Versions: 3.02, 3.01
- Generally 1 per year
Current XMPro BPMBusiness process management (BPM) is a discipline in operations management that uses various methods to discover, model, analyze, measure, improve, optimize, and automate business processes. BPM focuses on improving corporate performance by managing business processes. Any combination of methods used to manage a company's business processes is BPM. Processes can be structured and repeatable or unstructured and variable. Versions: 6.7, 6.6
- Generally 1 per year
We currently support released product current -1 where current = latest version released.
The implication of this is that any version prior in maintenance mode will get an end date of new version + 6 months and then move into archived (no more work outside of special cases); and any production version will move into maintenance mode where the below Service Pack and Issues are addressed.
Service Pack (Production and Maintenance)
These are compiled and released depending on circumstances and items contained within them. We try and minimize these. It is advised to only deploy these if you are experiencing the issues highlighted in the release notes.
- Issues resolved
- Minor feature enhancement if warranted by business case
Issues (Production and Maintenance)
We treat these on a case by case basis, approach followed is impact of the issue identified, is there a work around that can be provided until it can be resolved per the above. Is this work around acceptable with no long term impact vs the issue.
Dependencies for Microsoft patches:
XMPro does not have any dependencies on Microsoft patches currently and we don’t envision having any going forward. These patches can be applied as needed in the various environments. The only considerations to work though are any changes to IIS configurations and or any changes to SQL configurations as these will have an impact on the XMPro environments if their impacts are not assessed.
Upgrade and effort
- Upgrading XMPro involves two parts the first being running the various upgrade tools provided depending on the various components deployed. These tools generally run very quickly and it’s not uncommon for a site to be upgraded within an hour or less.
- Release upgrade: This involves upgrading all deployed products.
- Service Pack upgrade: This involves only upgrading the affected products.
How current is the XMPro deployment: If you are upgrading from an XMPro version that is a few versions behind there might be interim versions to upgrade to bring it up to date.
- The second part is post an upgrade there is regression testing of processes already deployed that will need to be done by using your standard UAT procedure; by assessing the impact of the changes in the upgrade (features added, issues corrected) this could mean all processes need testing or specific processes only. This is assessed during the upgrade scheduling effort.
- When upgrading XMPro there are two scenarios open:
- In place upgrade
- Server rebuild/Server move
Both are valid options and which approach to follow is directed by the IT governing policies of the company. There are various factors to consider for each approach, while a server rebuild is a cleaner approach, oftentimes the in place upgrade is faster. It comes down to the considerations to work though on each side, what is to be upgraded, only XMPro or XMPro and the environment?
We try as much as possible to only move off an older technology when Microsoft has closed out their main tier support for the technology. We also try as much as possible to also ensure backwards compatibility with older technology until it starts having a detrimental effect on current features and experiences.