Unsupported content

 

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.

Upgrading

The upgrade methods are similar to the methods for installing a new product. You run the installation program from a graphical user interface (GUI) or from a command line. This section provides an overview of the upgrade process and the procedures for performing platform upgrades with the GUI and command-line options.

Note

This version of BMC Atrium Orchestrator does not support the use of custom realms. 

Important

Before upgrading to 7.7.x, ensure that you install BMC Atrium Single Sign-On first. For information about installing BMC Atrium Single Sign-On, see Installing.

When you upgrade from 7.6.02.06 or 7.6.03 to 7.7, the Access Manager component is replaced by BMC Atrium Single Sign-On. In BMC Atrium Orchestrator Platform 7.7 and SP1, you were required to manually create the user roles and permissions existing in Access Manager in BMC Atrium Single Sign-On. In BMC Atrium Orchestrator 7.7 Service Pack 2, a migration utility/tool is provided, which exports all authentication data from Access Manager and then allows you to import the data in Grid Manager. 

You must run the migration tool before you start with the upgrade. For more information, see Migrating authentication and authorization data from Access Manager

Supported upgrade paths

The following table describes the supported upgrade paths from all earlier versions to the latest platform version.

Your current versionSupported upgrade versionNotes
7.6.02.067.7To upgrade to BMC Atrium Orchestrator Platform 7.7 from any earlier versions, ensure that you first upgrade to platform 7.6.02 Service Pack 6 and then upgrade to platform 7.7.
7.6.02.067.7.01 
7.6.02.067.7.02 
7.6.037.7.02 
7.7

7.7.01

 
7.77.7.02 
7.7.017.7.02 

Upgrading to 7.7 (video)

The following video shows how to upgrade from 7.6.03 to 7.7.02. 

Error rendering macro 'hide-if'

Failed to render Visibility macro due to: Unsupported Current Space parameter: currentspace . Please check if you have inputted a valid spacekey or used one of the allowed keywords.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Dhananjay Sengar

    Hi Team,

    While installing Atrium Single Sign On is it compulsory that Access Manager, Repository and CDP services should be up and running?

     

    I tried installing Atrium SSO while the services were shut down and installation was failed saying "waiting for the tomcat to start" in the install logs. In second attempt I tried installing Atrium SSO while AM, REPO and CDP services were up and running (as there was no clear instructions on service status of these components in the video) and I was able install SSO successfully.

     

    I am not able to co-relate this scenario. Please suggest.

     

    Thanks,

    Dhananjay

    Dec 03, 2015 02:18
    1. Dorothy Poole

       Thank you for your comment. I am making inquiries with the team and will respond when I have more information.

      Dec 03, 2015 06:44
    1. Dorothy Poole

      According to a team member, these are the following requirements for the upgrade scenarios:

      The team member said that it is unclear why your first attempt to install Atrium SSO had problems and the only way to determine the cause is to examine the logs. If you continue to have problems, please contact BMC Support and have the log files available. For more information about the log files that support might need, see Sending troubleshooting logs to BMC Software.

       

       

      Dec 03, 2015 09:22
  2. Dhananjay Sengar

    Hi Dorothy,
    Thanks for the response.

    --Migration utility worked for me successfully when the services were down. Initially when I used migration utility with services up, it failed stating am folder is locked and migration cannot be done (This is not the exact error message but I have written here what it meant and worked for me.

    --For the second point, it did not work for me in 2nd attempt when I installed atrium sso 9.0 keeping AO services up and running. For every failed scenario the only error I see is "Waiting for the tomcat to start".

    Thanks,
    Dhananjay

    Dec 06, 2015 02:44
    1. Dorothy Poole

      Thanks again for your comments. One thing I notice is that you mention installing Atrium SSO 9.0. We recommend earlier versions of SSO with BAO 7.7. For example, if you look at the 7.7.02 Service Pack 2 release page, you'll see that it is compatible with SSO 8.1.00.03 (7.7.02: Service Pack 2).  

      I sent your new comments to a team member and I will let you know if I get any further information about this. However, Support may be able to look at the logs and determine the exact cause.

      Dec 07, 2015 06:42
    1. Dorothy Poole

      I spoke with the team member and he suggested that you should file Support ticket to determine what caused the problem in the second scenario involving the SSO installation. They will be able to help with it. 

      Dec 07, 2015 08:08