This section explains the procedure to upgrade to BMC ProactiveNet Server 9.6.00 on Solaris or Linux.
Notes
To upgrade to BMC ProactiveNet Server 9.6.00 on Solaris or Linux
pw system stop
command to stop the BMC ProactiveNet Server.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.
pw system start
command.Access the installation program by using one of these methods:
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.
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.
Open the command prompt using the Run as administrator option and run the following command:./install.sh
Note
If your server is a standalone BMC ProactiveNet Server or a BMC ProactiveNet Central Server, perform the following step:
Notes
On the Configuring BMC ProactiveNet Central Monitoring Base Repository page, provide the following details, and click Next:
Source Directory — BMC ProactiveNet 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.
Warning
The directory path must not contain any of the following special characters. The installer does not support them.
(, ), !, @, #, $, %, ^, &, *, +, =, ~, `, \, ', <, and >
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.
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 BMC ProactiveNet 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.
Note
After you successfully upgrade the BMC ProactiveNet Server, you can find the following two folders at <installationDirectory>/BMC Software: