This page gives a complete high-level flow right from preparing your environment for installation to the actual installation procedure. It also includes any optional configuration that you might need. Note that once you have installed the optional products, you must ensure that you perform the following steps before you go live:
- Perform a sanity check of your upgraded environment
- Revert the upgraded VMs to the captured snapshot
- Verify that the customizations are present and fix any issues
- Complete user acceptance tests
This topic includes the installation flows for the following deployments:
In-Place Upgrade Compact Deployment
| | |
|---|
Preparing for the upgrade |
Also, go through the following topic and perform the following steps: - Before you begin
- Start with a clean upgrade environment by deleting DSO Pending, Invalid Workflow.
- Make sure that you have access to all VMs and databases.
- Collect all the productregistry.xml and installedconfiguration.xml files from your previous installation.
- Make sure that you have access to all the necessary client tools – BMC Remedy Development Studio, BMC Remedy Migrator and licenses, BMC Atrium Orchestrator Development Studio, and Best Practice Conversion Utility (BPCU) Tool and overlay hash files.
- Get customizations and related documents; get AO content details.
- Export/backup customizations as applicable.
- Make sure that you understand VM snapshot process and its limitations.
- Make sure that you understand the database backup and restore process.
- Collect all application administrator and end-user credentials and ports.
- Collect the list of parameters that you changed for performance tuning.
| |
| | |
Upgrading the CLM stack in the following order | | |
| | |
| | |
Back to top
In-Place Upgrade Small Deployment
| | |
|---|
Preparing for the upgrade |
Also, go through the following topic and perform the following steps: - Before you begin
- Start with a clean upgrade environment by deleting DSO Pending, Invalid Workflow.
- Make sure that you have access to all VMs and databases.
- Collect all the productregistry.xml and installedconfiguration.xml files from your previous installation.
- Make sure that you have access to all the necessary client tools – BMC Remedy Development Studio, BMC Remedy Migrator and licenses, BMC Atrium Orchestrator Development Studio, and Best Practice Conversion Utility (BPCU) Tool and overlay hash files.
- Get customizations and related documents; get AO content details.
- Export/backup customizations as applicable.
- Make sure that you understand VM snapshot process and its limitations.
- Make sure that you understand the database backup and restore process.
- Collect all application administrator and end-user credentials and ports.
- Collect the list of parameters that you changed for performance tuning.
| |
| | |
Upgrading the CLM stack in the following order | | |
| | |
| | |
Back to top
In-Place Upgrade Medium Deployment
| | |
|---|
Preparing for the upgrade |
Also, go through the following topic and perform the following steps: - Before you begin
- Start with a clean upgrade environment by deleting DSO Pending, Invalid Workflow.
- Make sure that you have access to all VMs and databases.
- Collect all the productregistry.xml and installedconfiguration.xml files from your previous installation.
- Make sure that you have access to all the necessary client tools – BMC Remedy Development Studio, BMC Remedy Migrator and licenses, BMC Atrium Orchestrator Development Studio, and Best Practice Conversion Utility (BPCU) Tool and overlay hash files.
- Get customizations and related documents; get AO content details.
- Export/backup customizations as applicable.
- Make sure that you understand VM snapshot process and its limitations.
- Make sure that you understand the database backup and restore process.
- Collect all application administrator and end-user credentials and ports.
- Collect the list of parameters that you changed for performance tuning.
| |
| | |
Upgrading the CLM stack in the following order | | |
| | |
| | |
Back to top
