Executing the KB Migration Wizard (Solaris or Linux)

This topic explains how to execute the KB migration wizard on a computer where a BMC ProactiveNet Integration Service 9.6.00 is installed (Solaris or Linux).

To execute the KB Migration Wizard

  1. Perform one of the following setup steps:
    1. If the installation media are on a Solaris or Linux computer, from the downloaded installation package, copy the SIEMupgrade subdirectory from the MigrateKB/server folder to the directory path of the Integration Service installation: /opt/pw/server/SIEMupgrade
    2. If the installation media are on a Microsoft Windows computer, ensure that your FTP utility is in binary mode to transfer the file securely.
      1. From the downloaded installation package, tar the SIEMupgrade subdirectory from the MigrateKB\server folder.
      2. Transfer the tar file in binary mode to the following directory path of the Integration Service installation: /opt/pw/server/SIEMupgrade.tar.gz
      3. Untar SIEMupgrade and extract the files to /opt/pw/server/.
  2. 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.

  3. Create a symbolic link from the /usr/pw file system to the /opt/pw file system, where /opt/pw is the installation path of the Integration Service. For example:

    ln -s /usr/pw/ /opt/pw

  4. Update the JAVA_HOME variable in migrate_kb.sh and MECLI.sh script files with the JRE path /usr/pw/jre or with /opt/pw/jre. For example:

    JAVA_HOME=/usr/pw/jre or JAVA_HOME=/opt/pw/jre
  5. Create a temporary download directory or note an existing directory in which you can store the data downloaded from the BMC Event and Impact Management system.
  6. Run the migrate_kb.sh file located in the SIEMupgrade/bin folder.
    ./migrate_kb.sh 
    The KB Upgrade of the Clone Cell window is displayed.

    KB_Migrate3.PNG 
  7. Enter the following information:
    KB Migration Wizard data fields
    Fields
    Description
    Cell whose KB will be migrated
    Cell Name
    Name of the BMC ProactiveNet cell whose KB you intend to migrate

    Enter an exact match of the BMC ProactiveNet cell name.

    Warning    : The upgrade can occur only if the specified cell name matches the actual cell name.
    Select Remote Cell Type
    Cell type determines how certain configuration variables are prefilled for the KB you are migrating. For more information, see Usage options.

    The supported values are as follows:
    • Admin Cell
    • BEM Cell (BMC Event Manager cell)
    • SIM Cell (Service Impact Manager cell)
    • BPPM Cell (BMC ProactiveNet cell)
    Select the cell type that matches the KB you are migrating.
    Remote Cell Hostname
    Name or IP address of the host system where the BMC ProactiveNet remote cell resides
    Operating System
    Operating system of the BMC ProactiveNet Server host where the BMC ProactiveNet cell resides. The supported values are as follows:
    • Windows
    • Solaris
    Logon User Name
    Name of user account with administrator rights on the BMC ProactiveNet Server host where the remote cell resides. Ensure that you provide the user name with the domain name.
    Password
    Password for the specified user name
    Presentation Cell Folder
    File path of the BMC ProactiveNet presentation cell that is to be migrated from the remote BMC ProactiveNet Server system. For example:

    Windows:
    topLevelInstallationDirectory\BMCSoft~1\Proacti~1\pw
    Note    : Use short names (short MS-DOS or 8.3 style) so that the spaces are omitted.

    Solaris:
    /opt/bmc/ProactiveNet/pw
    Temporary Work Directory
    Directory path on the BMC ProactiveNet Integration Service system where the required files are downloaded for the upgrade process
    Clone Cell Details
    Clone Name
    Name of the clone cell to be created on the BMC ProactiveNet Integration Service system

    Accept the prefix CLONE_ as part of the clone cell name. You can assign the clone cell any name.
    Clone Cell Port
    Port number through which the clone cell communicates
  8. Click Execute.
    The KB of the specified remote cell is downloaded, and a clone cell of the BMC ProactiveNet cell on the Integration Service system is created. The mmigrate tool is executed and merges the KB of the remote cell with the KB of the clone cell.
    The output window is displayed.
  9. Review the output window for any errors. If you discover unresolved compilation errors, refer to Resolving conflicts in the mmigrate process. Manually correct the conflicts. Click Previous, and then click Execute to rerun the upgrade.
  10. If the output window displays a success message and shows no errors, click Next.
    The Compile and Restart the Clone Cell window is displayed.
  11. Click Execute.
    The Wizard tries to compile and restart the clone cell (CLONE_name ) on the Integration Service system.
    The output window is displayed.
  12. Review the output window for any errors. To help correct errors, refer the following pages:Correct any errors, and click Previous to rerun the compilation and restart processes.
  13. When the KB of the clone cell compiles and restarts without error, click Finish.
  14. Manually move or copy the KB of the clone cell from the Integration Service system to the specified directory path on the BMC ProactiveNet Server 9.0.xx or 9.5.xx system where you intend to upgrade to BMC ProactiveNet Server 9.6.00. For information about adding clone cell KB directory to unique file path for merged KBs, see Adding the clone cell KB directory to the unique file path for merged KBs.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*