Limited support

 

This version of the product is in limited support. However, the documentation is available for your convenience. You will not be able to leave comments. Click here to view the documentation for the current version.

Upgrade process overview for BMC Digital Workplace Catalog

Review this section for details about the requirements and process for upgrading BMC Digital Workplace Catalog .

Upgrade path supported by version

The following table describes the upgrade path for the supported versions of BMC Digital Workplace Catalog and the application under its previous name, MyIT Service Broker.

ApplicationCurrently installed versionSupported upgrade to versionComments
BMC Digital Workplace Catalog

3.3.00 Patch 1 (version 3.3.00.001) or later

18.02.00

You can upgrade directly from BMC Digital Workplace Catalog 3.3.00 (Patch 1 or later) to version 18.02.00. The upgrade process migrates existing data so you do not need to run a separate data migration step.

If the application is installed in a server group for high availability, you can perform a nondisruptive upgrade by upgrading each individual server in sequence. For more information, see Upgrading BMC Digital Workplace Catalog in a server group.

MyIT Service Broker3.3.003.3.00 Patch 1 (version 3.3.00.001)

You cannot upgrade directly from MyIT Service Broker 3.3.00 to the latest BMC Digital Workplace Catalog 18.02.00 release. You must first upgrade to BMC Digital Workplace Catalog 3.3.00 Patch 1 to upgrade your existing database schema, and then you can upgrade to the latest version.

If you upgrade from 3.3.00 to 3.3.00 Patch 1, you must also perform a manual step to update the platform version in the database to be able to upgrade to version 18.02.00. For more information, see the following knowledge article: KA000141826 Open link .

MyIT Service Broker3.2.00 and related service packs and patches(None)You cannot perform an in-place upgrade directly from versions prior to version 3.3.00 Patch 1. For help transitioning your existing MyIT Service Broker 3.2 installation and migrating data into the latest release, contact BMC Support.

Before you begin


TaskActionReference
1Review the latest deployment use cases to understand whether any changes to your system architecture are required.

Deployment use cases

2Review the release notes for information about what's new, what's changed, and solutions to issues encountered during testing.

Release notes and notices

Known and corrected issues

3Collect the required information about the existing installation that will be used for the upgrade process.Upgrade worksheet for BMC Digital Workplace Catalog
4

If the upgrade is to be performed as a non-root user, ensure that the user account that will be performing the upgrade has the appropriate access to the installation folders and files.

Note: This step would have been completed before the original installation of BMC Digital Workplace Catalog .

See the section Preparing a server for installation as a non-root user in Preparing a Linux server for BMC Digital Workplace Catalog installation

Tasks to upgrade BMC Digital Workplace Catalog

Review the following tasks to understand the process before performing the upgrade.

TaskActionReference
1Download the files required for upgrade.Downloading the BMC Digital Workplace Catalog upgrade files
2Back up the database, file system, and create a snapshot of all servers.Preparing a system for a BMC Digital Workplace Catalog upgrade
3Copy the information from the BMC Digital Workplace Catalog upgrade worksheet into an upgrade options file to upload to the server.Creating a BMC Digital Workplace Catalog upgrade options file
4

Select an upgrade path based on your deployment scenario, either a single BMC Digital Workplace Catalog instance or high-availability server group deployment.

Upgrading a BMC Digital Workplace Catalog server

Upgrading BMC Digital Workplace Catalog in a server group

5Test the upgrade after completion by logging into BMC Digital Workplace Catalog .(Not applicable)

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments