This topic provides the following information about upgrading your ITSM or HRCM OnDemand solution:
BMC's OnDemand solutions usually have up to two releases per year. Typically, one release is a major release while any others are considered minor releases. A major release could impact end users due to changes such as user interface improvements. A minor release could involve an update to functionality that is localized to a section or module and typically has limited end-user impact. Two examples of a minor release are an update to mobility to include more device types and a release of BMC Remedy Single Sign-On to permit Security Assertion Markup Language (SAML) authentication. Patches and small service packs might not be considered full releases of the subscription, because they are localized in nature.
You will be notified approximately 30 days before a new release becomes available. The overall goal for the upgrade process is to ensure that your environments are upgraded to the new release before the next version becomes available. BMC recommends staying within one release of the current generally available version at all times.
Upgrades to the MyIT and Smart IT solutions are proactively managed by BMC SaaS Operations per a set release schedule. If you are on a shared instance of these services, upgrades are performed per data center location for multiple customers at the same time. You will be notified of the schedule for upgrades to these applications at least three weeks in advance. For customers on a shared instance, MyIT and Smart IT upgrades are done in two phases, Phase 1 being a cluster upgrade and Phase 2 being the tenant upgrade (development, QA and production), specific to your environment.
Customers in the BMC FedRAMP data center are not eligible for a major version upgrade until that version has been authorized by FedRAMP stakeholders.
Requesting an upgrade
Upgrades to your OnDemand solutions are performed by BMC's SaaS Operations team and are included as part of your subscription fees.
To request an upgrade, either submit a request through the BMC OnDemand Service Desk using the 'Request an ITSM Upgrade' option, or work through your Business Relationship Manager (BRM) to coordinate a start date that is convenient for you. Detailed upgrade documentation is available from your BRM upon request. A review of this documentation will help you understand what is required from your end and help you make a decision on project scheduling.
The upgrade process
The table below describes both the actions that BMC performs during an upgrade and the actions that you must perform during the upgrade, for each phase in the upgrade process. The timing of each phase is approximate and may vary depending on the complexity of your solution and the availability of your internal staff.
Cutover is a process that enables you to move from an old environment to a new environment.
A sanity test is a brief run-through of the functionality to ensure that it works roughly as expected.
Planning (1 week)
Upgrading (1 week)
Reconciliation (2 weeks)
Acceptance testing (2 weeks)
Production readiness (1 week)
Cutover (12 hours)
During the Reconciliation phase of the upgrade, BMC's SaaS Operations team analyses the customer's valid customizations (those designed with overlays) against the current release out-of-the-box version and the new release out-of-the-box version. BMC reconciles any changes required on the customer's supported overlay forms/objects to any new change in the new version. Any customization that cannot be reconciled with the new features or any situation where the customization is replaced by new features with better results will be communicated to the customer. BMC may require further collaboration with the customer in this situation.
Customizations applied to any form/object in Base Development mode are considered invalid as out-of-the-box forms/objects (type = unmodified) are then touched without creating an overlay. If an overlay is not created, there could be a scenario where a new version installer clears the customization, resulting in errors post upgrade.
Any overlay or custom forms/objects created in the CMDB will be considered invalid because the CMDB may only be extended using the Class Manager Console.
You will have the opportunity during user acceptance testing to test your customizations. Customizations requiring updates may require the involvement of your in-house development staff, BMC Global Services, or a trusted partner.