Upgrading BMC ProactiveNet Server 9.0.xx or 9.5.xx to Infrastructure Management Server on Solaris or Linux

This section explains the procedure to upgrade to Infrastructure Management Server 9.6.00 on Solaris or Linux.

To upgrade to BMC TrueSight Infrastructure Management Server 9.6.00 on Solaris or Linux

1. Archive the old installation files including the user apps, PERL libraries, and any other customizations.

   1. Run the pw system stop command to stop the BMC ProactiveNet Server.
   2. Tar the /usr/pw directory and place the resulting file in a secure location such as on another server, another file partition, or a directory that lies above /usr/pw.

   3. Save the Crontab entries (especially the database archive entry) related to the BMC ProactiveNet Server.

      Note

      For more information about archiving your old installation, check with your Solaris administrator.

   4. Restart the BMC ProactiveNet Server by using the pw system start command.
   5. Save any custom Apache settings.
2. Access the installation program by using one of these methods:
   • DVD — Insert the installation DVD. In the <installLocation>/Linux or <installLocation>/Solaris directory, open the BPPMServer directory.
   • BMC Software EPD website (http://webapps.bmc.com/epd) —  For more information about downloading the Infrastructure Management software, see Downloading-the-installation-files.

3. Apply executable rights to all the installation files by running the following command:

   chmod -R 777 installationDirectoryFolderName 

   installationDirectoryFolderName is the name of the folder that contains all the installation files.

4. Run one of the following commands to set the DISPLAY environment to enable the installation program UI to launch:

   • export DISPLAY=targetHostName:0.0
   • setenv DISPLAY targetHostName:0.0

   targetHostName is the name of the computer on which you want to display the installation program UI.

5. Open the command prompt using the Run as administrator option and run the following command:
   ./install.sh
   NoteBMC recommends that you do not use the setup.bin file to start the installation process, and use a binary mode if you are moving the files from one computer to another.
6. On the Welcome page, click Next.
7. On the license agreement page, select I agree to the terms of the license agreement, and click Next.
   The upgrade routine checks the system to see that it meets the upgrade prerequisites. It also checks for a current installation of Infrastructure Management Server 9.0.xx or 9.5.xx. It displays any errors that it discovers. You can correct them and then return to the upgrade sequence.
8. If your server is a standalone BMC TrueSight Infrastructure Management Server or a Central Server, perform the following step:
   Notes

   • This step is not applicable for a Child Server.
   • If you do not want to upgrade the repository now, you can specify an earlier version of the repository and upgrade only the repository later by using the pw-repository-update command.
   On the Configuring Infrastructure Management Central Monitoring Base Repository page, provide the following details, and click Next:
   • Source Directory — Infrastructure Management Central Monitoring Repository base file, 9.6.00_base-yyyymmdd-hhmmss.zip, where yyyymmdd-hhmmss is the date and time of the repository image. Download repository files from the BMC Electronic Product Distribution (EPD) facility or copy the files from the installation kit.
     
     

     WarningThe directory path must not contain any of the following special characters. The installer does not support them.(, ), !, @, #, $, %, ^, &, *, +, =, ~, `, \, ', <, and > 
   • Destination Directory — Directory to install the Infrastructure Management Central Monitoring Repository
   If you have a 9.0 Central Server without Central Monitoring Administration and you upgrade to a 9.6 Central Server that has Central Monitoring Administration, the Central Server will not contain the 9.0 Central Monitoring Repository contents. The repository will contain only the 9.6 repository contents after the upgrade. Hence, BMC recommends that when upgrading a 9.0 Central Server without Central Monitoring Administration to a 9.6 Central Server with Central Monitoring Administration, specify the 9.0 repository in the Source Directory field. After the upgrade is complete, run the pw-repository-update command with the 9.6 repository as an argument. This will ensure that the repository contains both the 9.0 and 9.6 repository contents.

9. On the Configuring KB Migration Path page, if you have already migrated customized KB definitions to the new standard 9.6.00 KB, select Yes, and browse to the path of the customized KB directory.
   
   The file path should follow this hierarchy structure:
   <topLevelDirectory>/mergedKB/server/etc/cellName, where /server/etc/cellName is the standard subdirectory

   Warning

   If you do have KB or KBs to migrate but have not done so, you can pause the upgrade process and perform the migration steps. See Migrating the configuration of cells.

   During the upgrade, the routine copies the KB under the /mergedKB/server/etc/cellName path and overwrites the KB in the default <installationDirectory>/pw/server/etc/cellName path.

    

10. Click Next.
11. On the Installation Preview page, click Install.
12. On the Installation Summary window, if you want to view the installation logs, select View Logs. If you want to exit the installation wizard, click Done.
    
    

Related topic

Upgrading-Integration-Service