Skip Headers
Oracle® Communications Network Integrity Installation Guide
Release 7.2.2

Part Number E36031-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

9 Upgrading Network Integrity

This chapter explains how to upgrade your existing system to the latest release of Oracle Communications Network Integrity.

This chapter explains how to recover your system after an upgrade failure. See "About Rolling Back Network Integrity" for more information.

In this chapter, the release you are upgrading from is called the old release. The release you are upgrading to is called the new release.

About Upgrading Network Integrity

Upgrading to a new release of Network Integrity consists of the following tasks:

Supported Upgrade Paths

This release of Network Integrity supports the following direct upgrade paths:

  • From release 7.1.0.x to release 7.2.2.

Planning Your Upgrade

Depending on the components affected by the upgrade, your upgrade team may include the following:

Identify who might be affected by the upgrade. For example:

You might need to make changes to your system after the upgrade is complete to accommodate new or modified features or functionality. For example, if the new release provides new security functionality, additional system configuration steps may be required. See "Upgrade Impacts" for more information.

The best way to estimate the duration of an upgrade is to perform the upgrade procedure on a test system with a copy of the production data. See "Testing the Upgrade in a Test Environment" for more information.

It is not necessary to shut down Network Integrity or the Network Integrity WebLogic Server domain before an upgrade. However, you must ensure that Network Integrity is not running any operations, such as scans or blackouts.

Oracle recommends scheduling your upgrade during non-peak hours to minimize the disruption to your operations.

Testing the Upgrade in a Test Environment

Oracle recommends running the upgrade procedure on a test system with a copy of your production data before upgrading your production system. Test the upgrade by doing the following:

Upgrade Impacts

This section explains any important system changes introduced by an upgrade.

New features and new functionality are described in Network Integrity Release Notes.

Upgrade Impacts From 7.1.0.x to 7.2.2

Upgrading to Network Integrity 7.2.2 applies the following changes:

Schema Changes

This version of Network Integrity requires an updated database schema. The Installer upgrades the schema automatically. Migrate the database data to conform with the new schema. See "Upgrading Network Integrity (7.1.0.x to 7.2.2)" for more information. As a precaution against a failed upgrade, backup your Oracle Database Schema for Network Integrity before starting the upgrade. See Network Integrity System Administrator's Guide for more information.

Database and Client Changes

This version of Network Integrity requires an updated version of the database and client. See "Software Requirements" for more information about system requirements. As a precaution against a failed upgrade, backup your Oracle Database data for Network Integrity before starting the upgrade. See Network Integrity System Administrator's Guide for more information.

WebLogic Server Changes

This version of Network Integrity requires an updated version of WebLogic Server. See "Software Requirements" for more information about system requirements. As a precaution against a failed upgrade, backup your WebLogic Server domain for Network Integrity before starting the upgrade. See your WebLogic Server documentation for more information.

Application Component Changes

The Installer updates all the Network Integrity components.

Design Studio Changes

This version of Network Integrity requires an updated version of Oracle Communications Design Studio. See "Network Integrity System Requirements" for version information. Design Studio can be set up before or after you upgrade Network Integrity. See the Design Studio installation documentation for more information. Do not remove your old version of Design Studio until after you have finished upgrading Network Integrity.

Cartridge Changes

You must undeploy cartridges that you do not want migrated to the new release before beginning the upgrade. See "Pre-Upgrade Tasks (7.1.0.x to 7.2.2)" for more information.

After the upgrade is complete, cartridges must be migrated to the new release of Network Integrity using the Design Studio Cartridge Migration Tool. It is possible that migrated cartridges contain minor compilation errors that prevent them from building and deploying. If a cartridge fails to build, open it in Design Studio and correct any compilation errors. See "Post-Upgrade Tasks (7.1.0.x to 7.2.2)" for more information.

Localization Changes

The Installer updates the localization pack to be compatible with the new release of Network Integrity, however any new fields and labels introduced in the new release are not localized. Edit the localization pack for the new fields and labels. See "Post-Upgrade Tasks (7.1.0.x to 7.2.2)" for more information.

Upgrading from 7.1.0.x to 7.2.2

This section details the upgrade procedure to upgrade Network Integrity from version 7.1.0.x to version 7.2.2.

Pre-Upgrade Tasks (7.1.0.x to 7.2.2)

Complete all of the following pre-upgrade tasks before upgrading Network Integrity:

  1. Ensure that SQL*Plus Instant Client is installed on the Administration Server from where you launch the Installer.

  2. Back up the Network Integrity database schema. See Network Integrity System Administrator's Guide for more information.

  3. Back up the Network Integrity WebLogic Server domain. See your WebLogic Server documentation for more information.

  4. Create an Enterprise Scheduling Service (ESS) schema using the Repository Creation Utility (RCU). See "Creating the Database (MetaData) Schema for Network Integrity" for more information.

  5. Export the Network Integrity 7.1.0.x database schema from the 11.2.0.2 database to the new 11.2.0.3 database. Perform the following:

    1. Export the Network Integrity 7.1.0.x schema, the guidelines are the same as for performing an Oracle Database export.

    2. Create blank MDS and ESS schemas, on the Network Integrity 7.2.2 database, using Fusion Middle Ware PS5 RCU.

    3. Import the Network Integrity 7.1.0.x schema (from step a) into the new schema (from step b) using the Oracle import utility (impdp). The following custom parameters need to be passed to the impdp utility:

      EXCLUDE=TABLE:\"LIKE \'MDS_%\'\", INDEX:\"LIKE \'MDS_%\'\" PACKAGE:\"LIKE \'MDS_%\'\" TYPE:\"LIKE \'MDS_%\'\" SEQUENCE:\"LIKE \'MDS_%\'\" PACKAGE:\"LIKE \'ESSI_%\'\" PACKAGE:\"LIKE \'ESS_%\'\" PROCEDURE:\"LIKE \'ESSI_%\'\" TRIGGER USER

    See the Oracle Database documentation for more information on the import/export utilities.

  6. Upgrade WebLogic Server from 10.3.2 to 10.3.6 and ADF from 11.1.1.2 to 11.1.1.6 following the steps documented in the knowledge article How to upgrade a WLS domain extended with ADF libraries [ID 1408663.1].

    After WebLogic Server has been upgraded to 10.3.6, apply any required patches. Refer to "Installing Patches".

  7. Apply the ESS template to the WebLogic domain. See "Installing Oracle Enterprise Scheduling Service" for more information.

  8. Extend the WebLogic domain to assign the ESS features, by performing the following:

    1. Execute the following command:

      WL_Home/wlserver_10.3/common/bin/config.sh

    2. Select the Extend an existing WebLogic domain option and click Next.

      The Select a WebLogic DomainDirectory screen appears.

    3. Select the Network Integrity domain which needs to be extended with the ESS features and click Next.

      The Select Extension Source screen appears.

    4. Select the Extend my domain automatically to support the following added products: option and then select Oracle Enterprise Scheduler Service and Oracle WSM Policy Manager and click Next.

      A Conflict Detected pop-up window will appear.

    5. Select the Replace existing component option and click OK for all Conflict Detected popup windows.

      The Configure JDBC Data Sources screen appears.

    6. Edit the host name and service name, to point to the new database (11.2.0.3), for each data source and click Next.

      The Test JDBS Data Sources screen appears.

    7. Click Select All and then Test Connections to test the modified Data Sources configuration. After the testing has completed click Next.

      The Configure JDBC Component Schema screen appears.

    8. Provide the ESS schema details, created previously in step 4, then select ESS Schema and click Next.

    9. Provide the MDS schema details, created when the databse was installed, then select MDS Schema and click Next.

    10. Provide the MDS schema details then select OWSM MDS Schema and click Next.

      The Test JDBC Component Schema screen appears.

    11. Click Select All and then Test Connections to test the modified Component Schemas configuration. After the testing has completed successfully, click Next.

      The Select Optional Configuration screen appears.

    12. Select the Deployments and Services option and click Next.

      The Target Deployments to Clusters or Servers screen appears.

    13. From the Target pane, select the target servers (administration server and managed servers) and from the AdminServer pane, under Deployments, select the wsm-pm, ESSAPP applications and the oracle.ess.client and oracle.ess libraries.

    14. From the AdminServer pane, under Service, select EssDS, EssXADS, EssInternalDS, and mds-ESS_MDS_DS. Select mds-commsRepository for the AdminServer and select mds-owsm for the managed servers. Click Next.

      The Configuration Summary screen appears.

    15. Click Extend to begin extending the domain.

  9. If this is a clustered server upgrade, perform the following (otherwise proceed to the step 10):

    1. Start the AdminServer and cluster member servers.

    2. Go to:

    3. http://ServerName:Port/console
      

      where ServerName is the name of the Administration Server system and Port is the Administration Server port number.

    4. Enter the WebLogic server administration user name and password.

    5. In the Change Center of the Administration Console, click Lock & Edit.

    6. In the Domain Structure tree, expand Services and click Data Sources.

    7. In the Summary of Data Sources screen, select JobDispatcherPersistentDS and click the Transactions tab, then deselect the Supports Global Transactions option. Click Save.

      Repeat this step for NIPersistentDS and POMSPersistentDS.

    8. In the Change Center of the Administration Console, click Activate Changes.

    9. In the Change Center of the Administration Console, click Lock & Edit.

    10. In the Domain Structure tree, expand Services and click Persistent Stores.

    11. In the Summary of Persistent Stores screen, select JDPersistentJDBCStore-0 and change the target from the managed server to the same managed server's migratable target (For example, if the target is ms2 then change the target to ms2(migratable). Click Save (ignore any warning messages).

      Repeat this step for JDPersistentJDBCStore-*, NIPersistentJDBCStore-*, and POMSPersistentJDBCStore-*.

    12. In the Change Center of the Administration Console, click Lock & Edit.

    13. In the Domain Structure tree, expand Services, expand Messaging, select JMS Servers>JDJMSServer-0 and change the target from the managed server to the same managed server's migratable target. Click Save.

      Repeat this step for JDJMSServer-*, NIJMSServer-*, and POMSJMSServer-*.

    14. In the Summary of Persistent Stores screen, select JDPersistentJDBCStore-0 and change the target from the managed server to the same managed server's migratable target (For example, if the target is ms2 then change the target to ms2(migratable). Click Save (ignore error messages).

      Repeat this step for JDPersistentJDBCStore-*, NIPersistentJDBCStore-*, and POMSPersistentJDBCStore-*.

    15. In the Change Center of the Administration Console, click Activate Changes.

    16. Proceed to step 10, to deploy the ESSAPP.

      Note:

      Errors shouldn't recur when restarting the servers after ESSAPP deployment.
  10. Deploy the ESSAPP by performing the following:

    1. Start the WebLogic server.

    2. Deploy the ESSAPP application, using the WebLogic console's Update option.

      Note:

      If Weblogic console contains any errors, these errors can be ignored.
    3. Restart the WebLogic server.

      Note:

      If the Weblogic server console contains the following exceptions, it can be ignored:javax.faces.application.ViewExpiredException: viewId:/as/deployment/deploymentHome - ADF_FACES-30108:The view state of the page has expired because of inactivity. Reload the page.
  11. Ensure that all the deployed applications are active, otherwise you will need to manually update each application and then make each application active.

  12. Undeploy all cartridges that you do not want migrated to the new version of Network Integrity. See "Managing Network Integrity Cartridges" for more information.

    For example, you should undeploy cartridges that you are no longer licensed to use or cartridges that provide functionality you no longer want to use.

    It is not possible to undeploy a non-migrated cartridge after upgrading Network Integrity. Failure to undeploy cartridges that cannot or are not migrated causes Network Integrity to not function. See "Problem: Inability To Run Scans or Resolve Discrepancies After Upgrading" for more information.

Upgrading Network Integrity (7.1.0.x to 7.2.2)

To upgrade Network Integrity:

  1. Create a temporary directory (dir).

  2. Download the software for your operating system from the Oracle software delivery Web site:

    https://edelivery.oracle.com

    and save it to dir:

  3. Extract the contents of the software pack to dir.

    The extracted software pack has the following structure:

    integrity/Disk1/install/

  4. (Optional: for IBM AIX systems only) Stop and restart the WebLogic Server domain for Network Integrity.

  5. Run the following command:

    /dir/integrity/Disk1/install/runInstaller -jreloc jre_Path
    

    Where jre_Path is the JRE location.

    The Installer Welcome screen appears.

  6. Click Next.

  7. In the Select Installation Type screen, select Custom and click Next.

    The Specify Home Details screen appears.

  8. Do all of the following:

    1. In the Name field, enter, browse to, or confirm the name of the folder that contains the installation files for the old version of Network Integrity.

    2. In the Path field, enter, browse to, or confirm the directory where the folder specified in the Name field is located.

    3. Click Next.

    The Installer scans the specified directory and folder. The Installer displays a pop-up message if it detects a pre-existing installation of Network Integrity.

  9. (Optional) Confirm that you want to override your pre-existing installation.

    The Installer retrieves information about your old Network Integrity installation, such as connection details and user names.

    The Available Product Components screen appears displaying installation information about the installed Network Integrity components.

    The Installer automatically detects the Network Integrity components that can be upgraded.

  10. Review the list of components to be upgraded and click Next.

    The WebLogic Administration Server Connection Information screen appears displaying the current connection information.

  11. Verify the WebLogic Administration Server connection information, enter the WebLogic Server password, and click Next.

    The WebLogic Server / Cluster Selection screen appears.

    Note:

    The Installer does not proceed from the WebLogic Administration Server Connection Information screen if the fields contain errors.
  12. Select the same target WebLogic server or cluster of servers belonging to the WebLogic Server domain to upgrade and click Next.

    If you are upgrading a cluster of servers, the Cluster Member Server Selection screen appears, where you can select a cluster member for Network Integrity adapters to install or upgrade.

    The Database Type Selection screen appears.

  13. Select the same database type that is used by your old Network Integrity installation:

    • If your old installation is connected to a standalone database, select Standard Oracle 11g Enterprise Database and click Next.

      The Database Connection Information screen appears.

      Do the following:

      1. Verify that the retrieved field values are correct and click Next.

      2. In the Password field, enter the database server password for the user specified in the User Name field.

      3. Click Next.

    • If your old installation is connected to an Oracle Real Application Cluster (RAC) database, select Oracle 11g Real Application Cluster Database and click Next.

      The RAC DB Nodes Connection Information screen appears.

      Do the following:

      1. Verify that the retrieved field values are correct and click Next.

      2. In the Password field, enter the database server password for the user specified in the User Name field.

      3. Click Next.

      The Network Integrity Schema User Information screen appears.

      Note:

      The Installer does not proceed from either the Database Connection Information or RAC DB Nodes Connection Information screen if the fields on these screens contain errors.
  14. Do the following:

    1. Verify that the retrieved value in the Schema User Name field is correct.

    2. In the Schema User Password field, enter the schema user password for the user specified in the Schema User Name field.

    3. Click Next.

    The Summary screen appears.

  15. Review the Summary screen and click Install.

    The Summary screen lists the products and components that are being upgraded. The Already Installed list includes products and components that are already up to date and are not being upgraded.

  16. Click the Install button.

    The Install screen appears, showing the status of the upgrade installation. The Install screen also explains where the upgrade log files are saved (NI_Home/oraInventory/logs/installActionDate_Time.log).

    When the Installer completes the upgrade, the End of Installation screen appears displaying the success of the upgrade. This screen also provides the URLs for accessing the new release of Network Integrity. Make a note of the URLs.

  17. Click Installed Products and verify that the installed version for Network Integrity is 7.2.2.0.0.

  18. Logon to the Network Integrity database instance and run the following data migration scripts:

    Caution:

    You must use the same user name and password that you provided when you set up the database schema using the Repository Creation Utility (RCU). See "Creating the Database (MetaData) Schema for Network Integrity" for more information.
    • NI_Home/integrity/upgrade/migration/7.2.2.0.0_NetworkIntegrity_data_migration.sql

    • NI_Home/integrity/upgrade/migration/post_upgrade_data_changes.sql

  19. In the Installer, click Exit.

Post-Upgrade Tasks (7.1.0.x to 7.2.2)

Complete all of the following post-upgrade tasks after upgrading Network Integrity, if necessary:

  1. Execute any database migration and post upgrade data changes sql scripts.

    Note:

    The sql scripts must be executed as the MDS user and prior to re-deploying any cartridges.
  2. Execute the following script, using the Network Integrity 7.2.2 ESS schema:

    . update request_history set submitter = '&niuser' where submitter = '&weblogic_admin_user';

    commit;

  3. Verify that the upgrade was completed successfully. See "Verifying the Network Integrity Installation" for more information.

  4. If you configured an Inventory System in release 7.1.0.x and specified a password, you need to re-enter the password. Click on Manage Import System, click on Edit, enter the password and click Save and Close.

  5. Migrate your cartridges to the new version of Network Integrity. See "Migrating Cartridges" for more information.

  6. Re-deploy your cartridges. See "About Managing Network Integrity Cartridges with the Cartridge Deployer Tool" for more information.

  7. Update and re-deploy your localization pack. See Network Integrity Developer's Guide for more information.

    Note:

    Your localization pack is compatible with this version of Network Integrity, however new fields and labels must be localized.
  8. Copy any custom scripts from the Network Integrity 7.1.0.x CartridgeDeployer/ directory to the new Network Integrity 7.2.2 CartridgeDeployerClients/ directory, then delete the 7.1.0.x CartridgeDeployer/ directory.

  9. Edit the Cisco UIM import scans / MIB II UIM import scans to specify the correct parameter group and filter criteria. See Network Integrity UIM Integration Cartridge Guide and Network Integrity MIB-II UIM Integration Cartridge Guide for more information.

Migrating Cartridges

If you developed or extended cartridges for the old version of Network Integrity, you must migrate them to the new version of Network Integrity to continue to use them.

It is not possible to migrate scan instances or scan data. Scan instances have to be manually re-created in Design Studio. Scan data is re-created when you run a scan.

Production cartridges (cartridges with binaries supplied by Oracle) are already compatible with the new version of Network Integrity. Deploy production cartridges into the latest installation of Network Integrity.

Migrate your old custom cartridges to be compatible with the new version of Network Integrity using the Design Studio Cartridge Migration Tool. See Oracle Communications Design Studio Platform Online Help for more information.

The procedure for migrating cartridges assumes you have two Design Studio environments: one for the old version of Network Integrity, and one for the new version of Network Integrity.

Please make sure the imported project is not read-only. Everything inside the imported project should be writable. The cartridge migration will fail if the project is read-only.

The Network Integrity cartridge migration tool will migrate 7.0.1 and 7.1.0.x Network Integrity projects. It also migrates Data Dictionary Project (7.0.1 or 7.1.0.x) with Specifications. The specifications will be created in a new Integrity project after the migration. The new integrity specification project will have the name as "<Imported_Project>_Specifications". If the imported Network Integrity project or Data Dictionary project does not contain any specifications, the migration tool will not create this new specification project.

In the 7.0.1 and 7.1.0.x releases, specifications are defined in a Data Dictionary Project. After the migration, the specifications will be created inside the new Integrity specification project. The Data Dictionary project will still be migrated into 7.2.2. However, it will no longer contain the specifications as in 7.0.1 or 7.1.0.x. Please do not remove this data dictionary project after migration. This data dictionary project still contains important information related to the original specifications. If another Network Integrity project is dependent on this data dictionary project, without this data dictionary project in the workspace, the migration of that Network Integrity project will fail.

It is important to make sure that all the dependent projects exist in the workspace before importing a Network Integrity project. The user should always import the dependent project first. The migration tool will automatically set the dependencies when migrating Network Integrity projects, if the dependent projects exist in the workspace. If multiple projects are imported into Design Studio at the same time, please move the dependent project to the top of the order in the cartridge upgrade dialog, so that the dependent project will be migrated first.

Sometimes there will be compiling errors after cartridge migration is completed. This is due to the changed API in the 7.2.2 release. For example, the pre-722 API will return Set as return type and now it returns List as return type. The user will need to manually modify the implementation Java code to fix the compiling errors.

The productized cartridge, MIB_II_Model, in 7.0.1 and 7.1.0.x, is using an unconventional method to model the device interface configuration for IpAddress. If a pre-7.2.2 Network Integrity project is dependent on the MIB_II_Model for IpAddress device interface configuration entity, the migration will fail. Because the 7.2.2 productized MIB_II_SNMP_Cartridge (replacing both MIB_II_Model and MIB_II_SNMP_Cartridge cartridges in pre-7.2.2 releases) is using a new method to model device interface configuration, the user will need to manually modify the cartridge to use the new device interface configuration entity defined inside the productized 7.2.2 MIB_II_SNMP_Cartridge, after importing.

To migrate a custom cartridge (a cartridge with binaries not supplied by Oracle):

  1. Using the old Design Studio environment for Network Integrity, do the following:

    1. Select the Design Studio perspective.

    2. Select the Cartridge view.

    3. Select the cartridge project and, from the Project menu, unseselect Build Automatically.

    4. From the Project menu, select Clean.

    5. Select the Navigation view.

    6. Right-click the cartridge project folder and select Close Project.

  2. Using the new installation of Design Studio for Network Integrity, do the following:

    1. Select the Design Studio perspective.

    2. Select the Cartridge view.

    3. Right-click anywhere in the Cartridge view and select Import.

      The Import Project dialog box appears.

    4. Verify that the imported project is not "read-only."

      Note:

      Everything inside the imported project should be writable. The cartridge migration will fail if the project is read-only.
    5. Locate the cartridge project and import it.

    6. Double-click the cartridge project folder.

      The cartridge properties appear.

    7. Verify that 7.2.2 appears in the Target Version field.

      Note:

      If the Target Version field is not editable, it may mean that the cartridge is sealed, read-only, or under source control.
    8. Using Windows Explorer, navigate to the cartridge directory.

    9. Perform all necessary pre-build steps particular to your cartridge.

    10. From the Project menu, enable Build Automatically.

    11. From the Project menu, select Clean.

      The cartridge project is automatically built. The binary file is produced and written to the cartridgeBin directory.

About Rolling Back Network Integrity

If the Installer fails to successfully upgrade Network Integrity, you must manually restore the WebLogic server domain, the database schema, and the database domain. See Network Integrity System Administrator's Guide for more information about restoring the database. See your WebLogic Server documentation for more information about restoring the WebLogic Server domain.