Upgrading using console mode

Upgrading Predictive Insights using console mode.

Before you begin

  1. Create a directory for the upgrade software, for example:
    mkdir ~/PredictiveInsights_1.3.6
  2. Download and extract the Predictive Insights package from the media to the new directory.
  3. On each server that runs the Analytics component, log in as the analytics user, for example, scadmin, and stop the Analytics instance. 
    $PI_HOME/bin/stop.sh
  4. Stop any instance of the Mediation Tool that is running.
  5. If the previous version of Predictive Insights was configured to use LDAP authentication, you must replace the LDAP authentication with the authentication method that was in place when you installed the previous version.

    For example, if you used the ncoadmin user from an ObjectServer user repository to install version 1.3.4 and later replaced the ObjectServer user repository with an LDAP user repository, then you must switch to authenticating against an ObjectServer user repository before you start the upgrade.

    To switch from LDAP to ObjectServer authentication, complete the following steps:

    1. Make a backup copy of the following configuration files:
      • <installdir>/UI/wlp/usr/servers/piserver/ldapRegistry.xml
      • <installdir>/UI/wlp/usr/servers/piserver/server.xml
      • <installdir>/UI/wlp/usr/servers/piserver/taspConfig.xml
      where <installdir> is /opt/IBM/scanalytics by default.
    2. To remove the LDAP integration and configure the UI server to use the ObjectServer user repository, restore the <installdir>/UI/wlp/usr/servers/piserver/server.xml that you backed up in step 5 of the Configuring the LDAP User Registry procedure.
    3. To configure the WebGUI to point to the ObjectServer, enter the following commands:
      cd <WEBGUI_HOME>/configtool/linux.gtk.x86_64
./ncwConfigUI -WASUserID smadmin -WASPassword smadmin
      where <WEBGUI_HOME> is /opt/IBM/netcool/omnibus_webgui by default

About this task

You must upgrade each Predictive Insights component on the server on which the component is installed. Therefore, if Predictive Insights components are installed on multiple servers, you must run the upgrade on each server.

Procedure

  1. As the user that was used to install the component or components you are upgrading, change to the predictiveInsightsInstaller1.3.6 directory within the directory in which you extracted the upgrade software.
  2. To start the installer, enter the following command: 
    ./install.sh -c
  3. Enter 2 to Update - Find and install updates and fixes to installed software packages.
  4. Enter 1 to select the Predictive Insights package. All of the Predictive Insights components present on the server are selected for upgrade.
  5. Enter N to continue.
    The installer prepares and validates the set of updates.
  6. Enter A to accept the license agreement.
  7. Enter N to continue.
  8. Enter the requested parameters for each component.
  9. Enter N to continue.
  10. Enter U to update.
  11. Enter F to finish.
  12. Enter X to exit.
  13. If the previous version of Predictive Insights was configured to use LDAP authentication, complete the following steps to set up LDAP authentication for version 1.3.6.
    1. Copy the files that you backed up in step 5 of the Before you begin section to their original location.
    2. To grant users in the LDAP directory access to Predictive Insights User Interface, do the following:
      1. Change to the <Liberty_Install_Home>/UI/bin directory. The default path for <Liberty_Install_Home> is /opt/IBM/scanalytics.
      2. Enter the following command
        ./addAccess.sh <user | group> <LDAP user or group name>
        For example, to grant access to an LDAP group called operators, enter the following command:
        ./addAccess.sh group operators
    Note: After the upgrade completes, you must clear the web browser cache before you log in to your visualization tool.

What to do next

On the Analytics server, the upgrade procedure does not remove older JAR files when it installs later versions of the files. To resolve these file conflicts, complete the following steps:
  1. Enter the following commands to remove the older version of the JAR files:
    rm -f $PI_HOME/lib/commons-lang3-3.1.jar      
rm -f $PI_HOME/lib/commons-math3-3.0.jar      
rm -f $PI_HOME/lib/org.eclipse.emf.common_2.8.0.v20130125-0546.jar      
rm -f $PI_HOME/lib/org.eclipse.emf.common.ui_2.7.0.v20130125-0826.jar      
rm -f $PI_HOME/lib/org.eclipse.emf.ecore_2.8.3.v20130125-0546.jar      
rm -f $PI_HOME/lib/org.eclipse.emf.ecore.xmi_2.8.1.v20130125-0546.jar
  2. To compile each topic, enter the following commands: 
    cd $PI_HOME/spl/instances/Analytics<topic> 
./compile.sh

    Where <topic> is the name of the topic.