Upgrading BMC Event and Impact Management with multiple SIM presentation cells
This topic describes the procedure to upgrade BMC Event and Impact Management with multiple SIM presentation cells to BMC ProactiveNet 9.6.00.
Before you begin
- Ensure that the BMC Atrium Web Services and other related components are installed. For more details, see Installing BMC Atrium Core.
- If you are migrating an instance of a high availability (HA) Impact Administration Server, ensure that the data is synchronized with the primary server.
- Ensure that the BMC Impact Portal users and user groups are synchronized with the BMC Impact Administration Server.
Upgrading BMC Event and Impact Management with multiple SIM presentation cells to BMC ProactiveNet
- On all the SIM presentation cells, using a text editor, open the mclient.trace file, which is located in the installationDirectory\pw\server\etc folder, and add the following entry:
ALL INFORM no Install BMC ProactiveNet Server 8.6.02 for every SIM presentation cell.
For example, if you have five presentation cells, you must have five BMC ProactiveNet 8.6.02 installations. Ensure that you provide the same cell name as that of the SIM presentation cell when you install BMC ProactiveNet.
For example, if the first SIM cell name is cell1, provide the cell name for the first BMC ProactiveNet installation as cell1.
For more information, see the BMC Support site to access the July 2011 version of the BMC ProactiveNet Upgrade Guide supporting BMC ProactiveNet Performance Management 8.6.02.
- Apply BMC ProactiveNet 8.6.02 SP4 over every BMC ProactiveNet 8.6.02 installation.
- In the computer that has BMC Event and Impact Management cell, open the mcell.dir file, and search for entries with port separator (/), and replace them with colon (:).
For example, change the cell simcell mc bppm123/16923 entry to cell simcell mc bppm123:16923.
The cells created by executing the mcrtcell command result in entries created with port separator (/). It is applicable only for BMC Event and Impact Management 7.4 or above. - In the computer that has BMC ProactiveNet installed, open the pserver.conf file located at the following location:
- For Windows, installationDirectory\server\etc
- For Solaris, installationDirectory/server/etc
- Search for the string, Enterprise=F. If the line is commented, un-comment it, and modify the string as follows:
Enterprise=T
Ensure that you perform this task on every BMC ProactiveNet that you have installed. - On the first server in which you have installed BMC ProactiveNet, launch the upgrade wizard, and migrate BMC Event and Impact Management data, events, and components.
You must execute the steps 1 through 10 documented under the section “Launching the upgrade wizard” in the July 2011 version of the BMC ProactiveNet Upgrade Guide supporting BMC ProactiveNet Performance Management 8.6.02. - On the other servers in which you have installed BMC ProactiveNet, launch the upgrade wizard, and execute the steps 1 through 8 documented under the section “Launching the upgrade wizard” in the July 2011 version of the BMC ProactiveNet Upgrade Guide supporting BMC ProactiveNet Performance Management 8.6.02.
Run the following command to connect with BMC Event and Impact Manager and export the direct feed SIM _Match_Table data:
mquery -n simcell -f BAROC -d -a BMC_SIM_MATCH_TABLE -w "publish_env_id :equals ''" -x data_handle,mc_udid,mc_creation_time,mc_modification_time > <tempDirectoryPath>tempDirectoryPath is the location where you want to export the direct feed data. For example, D:\SimMatchData1.baroc.
Run the following command to delete all the SIM_MATCH_TABLE data from the cell:
mquery -n simcell -d -a BMC_SIM_MATCH_TABLE -s DELETEFrom the first server in which you have installed BMC ProactiveNet, copy the SimMatchData.dat file from the installationDirectory/pw/upgradeBackup/simMatchBackup directory to the same location of the other servers in which you have installed BMC ProactiveNet.
- Execute the step 9 documented under the section “Launching the upgrade wizard” in the July 2011 version of the BMC ProactiveNet Upgrade Guide supporting BMC ProactiveNet Performance Management 8.6.02.
Run the following command to recreate the direct feed SIM_MATCH_TABLE data:
mposter -n <BMCProactiveNetCellName> -d -v <tempDirectoryPath>BMCProactiveNetCellName is the cell name of the corresponding BMC ProactiveNet Server, and the <tempDirectoryPath> is the location where you have exported the direct feed data in this step.
- Complete the step 10 documented under the section “Launching the upgrade wizard” in the July 2011 version of the BMC ProactiveNet Upgrade Guide supporting BMC ProactiveNet Performance Management 8.6.02.
After the upgrade to BMC ProactiveNet 8.6.02 is complete, validate the migrated data. Ensure that all the users, user groups, and user preferences are available. Also, ensure that the events and CIs show up properly in the Operations Console.
BMC ProactiveNet 8.6.02 does not support distributed service models. In BMC Event and Impact Management environment, if you have distributed service model, you cannot view the complete model in BMC ProactiveNet 8.6.02. However, you can view it after you upgrade to BMC ProactiveNet 9.5.00.
- Upgrade every BMC ProactiveNet 8.6.02 installation to BMC ProactiveNet 9.5.00.
For more information, see Upgrading-BMC-ProactiveNet-Server-9-0-xx-or-9-5-xx-to-9-6-00-on-Microsoft-Windows and Upgrading-BMC-ProactiveNet-Server-9-0-xx-or-9-5-xx-to-9-6-00-on-Solaris-or-Linux. - Upgrade every BMC ProactiveNet 9.5.00 installation to BMC ProactiveNet 9.6.00.
For more information, see Upgrading-BMC-ProactiveNet-Server-9-0-xx-or-9-5-xx-to-9-6-00-on-Microsoft-Windows and Upgrading-BMC-ProactiveNet-Server-9-0-xx-or-9-5-xx-to-9-6-00-on-Solaris-or-Linux. - On the BMC ProactiveNet Servers, run the following command, and set the first server as Central Server and the other servers as child servers.
pw configwsroles
For information about the pw configwsroles command, see pw-configwsroles. - Restart all the BMC ProactiveNet Child Servers and then the BMC ProactiveNet Central Server.