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.
Upgrading to a new release of Network Integrity consists of the following tasks:
Planning the upgrade. See "Planning Your Upgrade" for more information.
Reviewing the upgrade impacts. See "Upgrade Impacts" for more information.
Performing the pre-upgrade tasks.
Upgrading Network Integrity.
Performing the post-upgrade tasks.
See "Upgrading Network Integrity" for more information.
Before upgrading a production environment, you should first test the upgrade in a test environment. See "Testing the Upgrade in a Test Environment" 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.
This release of Network Integrity supports the following direct upgrade paths:
From release 7.2.4.x to release 7.3.2
From release 7.3.0 to release 7.3.2
See "Upgrading Network Integrity" for more information.
Depending on the components affected by the upgrade, your upgrade team may include the following:
A database administrator, to manage the database upgrade and tune the database.
A system integrator, to handle new and existing customizations.
A system administrator, to manage the Oracle WebLogic Server and Network Integrity software upgrade.
A UNIX administrator, to manage accounts, network setup, and IP configurations.
Identify who might be affected by the upgrade. For example:
You might need to give your system administrators and Network Integrity users notice of any system downtime.
Tell your system administrators in advance about any changes to the system architecture (for example, Oracle database, client, or WebLogic Server upgrades).
Train your administrators, users, cartridge developers, or system integrators on new functionality introduced by the upgrade that has an impact on their role.
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.
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:
Successfully completing all the pre-upgrade, upgrade, and post-upgrade tasks.
Comparing the default behavior between the old and the new releases.
Recreating any custom configurations and extensions.
Confirming that all new behavior and functionality works.
Ensuring that the database tables are properly installed.
Ensuring that the database data is correct.
Starting the WebLogic Server domain.
Ensuring that users and user permissions are correct.
Ensuring that productized and custom cartridges build and deploy properly.
Logging into Network Integrity and verifying the version number of installed components.
This section explains any important system changes introduced by an upgrade.
New features and new functionality are described in Network Integrity Release Notes.
Upgrading to this version of Network Integrity requires the following system changes:
If upgrading from:
7.2.4.x: You must upgrade your version of Application Development Runtime and apply applicable patches, and install Repository Creation Utility.
7.3.0: You do not need to upgrade your version of Application Development Runtime, but you do need to apply applicable patches.
See "Software Requirements" for more information.
The new version of Network Integrity requires an updated version of the Java Development Kit (JDK) on the Network Integrity application server. See "Software Requirements" for more information.
During the upgrade, you will need to update the Network Integrity domain to point to the new JDK.
If upgrading from:
7.2.4.x: You must upgrade your version of WebLogic Server and apply applicable patches.
7.3.0: You do not need to upgrade your version of WebLogic Server, but you do need to apply applicable patches.
See "Software Requirements" for more information.
If upgrading from:
7.2.4.x: You may need to upgrade your version of Oracle Database software and apply applicable patches, depending on the version you are currently using in 7.2.4.x.
7.3.0: You do not need to upgrade your version of the Oracle Database, but you do need to apply applicable patches.
See "Software Requirements" for more information.
If you upgrade to the new version of the Oracle Database software, you must also update your database client software.
The new version of Network Integrity requires an updated database schema.
The Oracle Universal Installer updates all the Network Integrity components.
This version of Network Integrity requires an updated version of Oracle Communications Design Studio. See "Network Integrity System Requirements" for more information.
Design Studio can be set up before or after you upgrade Network Integrity. See the Design Studio installation documentation for more information. Rather than upgrading Design Studio, install the new version and keep the old version until after you have finished upgrading Network Integrity.
You must undeploy cartridges that you do not want to migrate to the new release before beginning the upgrade.
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.
Also, the Optical UIM Integration cartridge is enhanced with new scan parameter groups. You must update any Import Optical from UIM and Import Logical Optical scans in Network Integrity.
This section details the upgrade procedures to upgrade Network Integrity:
From release 7.2.4.x to release 7.3.2 by doing the following tasks:
From release 7.3.0 to release 7.3.2 by doing the following tasks:
This section details the pre-upgrade tasks you must perform to upgrade Network Integrity from 7.2.4.x to 7.3.2.
Complete all of the following pre-upgrade tasks before upgrading Network Integrity:
Back up the Network Integrity and MDS databases. See Network Integrity System Administrator's Guide for more information.
Back up the Network Integrity WebLogic Server domain. See your WebLogic Server documentation for more information.
Note:
If you are upgrading from 7.2.4.x to 7.3.2 in AIX environment, you must configure the 7.2.4.x WebLogic domain to point to the JDK version that you use to install NI 7.3.2.Create an Oracle Platform Security Services (OPSS) schema using Fusion Middleware Repository Creation Utility RCU PS6 (11.1.1.7.0). See "Creating the Database (MetaData) Schema for Network Integrity" for more information.
When creating the OPSS schema using RCU PS6, ensure that you do the following:
On the Select Components screen, select Select an Existing Prefix, and then from the list, select the prefix that you used to create the MDS schema during the 7.2.4.x installation.
See Oracle Fusion Middleware Repository Creation Utility User's Guide for more information.
Create the data source for the OPSS user by doing the following:
Log in to the WebLogic server Administration Console using the Administrator credentials.
Click Lock & Edit.
In the Domain Structure tree, expand Services, and then click Data Sources.
The Summary of Data Sources page appears.
Click New and select Generic Data Source.
The JDBC Data Sources Properties page appears.
In the Name and JNDI Name fields, enter the required information; from the Database Type list, select an option, and then click Next.
From the Database Driver list, select Oracle's Driver (Thin) for Instance connections; Versions 9.0.1 and later.
Note:
When creating a data source for Oracle Real Application Clusters (RAC) database, you can specify details about the single instance of the RAC database.Click Next.
The Transaction Options Page appears.
Deselect the Supports Global Transactions check box and click Next.
The Connection Properties page appears.
In the Database Name, Host Name, Port, Database User Name, Password, and Confirm Password fields, enter the database details of the OPSS schema you created in step 3, and then click Next.
The Test Database Connection page appears.
Review the connection parameters and click Test Configuration.
If the test is successful, click Next.
The Select Targets page appears.
Select the servers or clusters on which you want to deploy the data source and click Finish.
The Summary of JDBC Data Sources page appears.
Verify that the newly created data source is listed under the Data Sources table.
In the Change Center of the Administration Console, click Activate Changes, which activates these changes.
See the Oracle WebLogic Server documentation for more information.
To reassociate the OPSS security store to a DB-based security store, do the following:
Log in to Fusion Middleware Control Enterprise Manager and navigate to Domain, then Security, and then Security Provider Configuration (if connected to Oracle WebLogic Server).
The Security Provider Configuration page appears. The table under the Security Stores area shows the characteristics of the current provider configured in the domain.
Click Change Store Type.
The Configure Security Stores page appears.
From the Store Type list, select Oracle Database.
In the Data Source JNDI Name field under Database Server Details, enter the name of the OPSS data source that you provided when creating the data source.
Enter the required information about the OPSS data source in the fields under the Data Source Properties and Root Node Details areas.
Click OK.
A confirmation message appears that informs you that the security stores configuration is successfully completed.
See Oracle Fusion Middleware documentation for more information.
Run the following command:
For Unix and Solaris:
. ./WL11g_Home/server/bin/setWLSEnv.sh
For AIX:
. ./WL11g_Home/common/bin/wlst.sh
WL11g_Home is the directory in which Oracle WebLogic Server 11g is installed.
This command displays the classpath value.
Run the following command:
export CLASSPATH=ni_installer_extract_location/integrity/Disk1/essrmvl.jar:$CLASSPATH
where:
ni_installer_extract_location is the directory where you extract the contents of the Network Integrity installer package.
Do one of the following:
If you have deployed Network Integrity with Oracle Real Application Clusters (RAC) database, run the following command:
java oracle.communications.integrity.sr3upgrade.SR3ESSRemoval username password t3://host:port rac
If you have deployed Network Integrity with single-instance database, run the following command:
java oracle.communications.integrity.sr3upgrade.SR3ESSRemoval username password t3://host:port norac
where:
username is the administrator user name for the administration server.
password is the password for the administration server.
host is the host name or IP address for the administration server.
port is the port number for the administration server.
(Optional) Upgrade the Oracle Database software. See "Database Software Changes" for more information.
See the Oracle Database documentation for information on upgrading the database software to a newer version.
Stop the Network Integrity Domain Servers.
Import the Network Integrity 7.2.4.x database schema from the 11.2.0.4.0 database to the new 12.1.0.2.0 database.
Step 11 is not required if you do an in-place upgrade of the database, that is, if you upgrade Oracle Database 11g R2 with existing 7.2.4.x schema to Oracle Database 12c.
See the Oracle Database documentation for more information on the import/export utilities.
Edit the Domain_Home/init-info/domain-info.xml file from the 7.2.4.x installation and remove the following entries:
Note:
Domain_Home is the directory containing the configuration for the domain into which Network Integrity 7.2.4.x is installed.<extention-template-ref name="Oracle Enterprise Scheduler Service Base" version="11.1.1.0" location="WLPS6_ESS_HOME/oracle_ess/common/templates /applications/oracle.ess.base_11.1.1_template.jar" symbol="oracle.ess_11.1.1.6.0_oracle_ess_ORACLE_HOME"/> <extention-template-ref name="Oracle WSM Policy Manager" version="11.1.1.0" location="WLPS6_ESS_HOME/oracle_ess/oracle_common/common/templates /applications/oracle.wsmpm_template_11.1.1.jar" symbol="oracle.jrf.owsm_11.1.1.7.0_oracle_common_ORACLE_HOME"/> <extention-template-ref name="Oracle Enterprise Scheduler Service Client" version="11.1.1.0" location="WLPS6_ESS_HOME/oracle_ess/common/templates /applications/oracle.ess.client_11.1.1_template.jar" symbol="oracle.ess_11.1.1.6.0_oracle_ess_ORACLE_HOME"/> <extention-template-ref name="Oracle Enterprise Scheduler Service" version="11.1.1.0" location="WLPS6_ESS_HOME/oracle_ess/common/templates /applications/oracle.ess_11.1.1_template.jar" symbol="oracle.ess_11.1.1.6.0_oracle_ess_ORACLE_HOME"/> <extention-template-ref name="Oracle Enterprise Scheduler Service Basic" version="11.1.1.0" location="WLPS6_ESS_HOME/oracle_ess/common/templates /applications/oracle.ess.basic_11.1.1_template.jar" symbol="oracle.ess_11.1.1.6.0_oracle_ess_ORACLE_HOME"/> <install-comp-ref name="oracle.ess" version="11.1.1.6.0" symbol="oracle.ess_11.1.1.6.0_oracle_ess_ORACLE_HOME" product_home="/opt/softwares/ps6/wl6middleware/oracle_ess"/>
Upgrade the MDS and OPSS schemas by doing the following:
Navigate to the MW_Home/oracle_common/upgrade/bin/ua directory, where MW_Home is the directory in which the Oracle Fusion Middleware 12c products, files, and folders are installed.
This directory contains the Fusion Middleware Upgrade Assistant, which you use to upgrade the MDS schema.
Launch the Fusion Middleware Upgrade Assistant.
The Welcome screen appears.
Click Next.
Select Schemas and click Next.
The Available Components screen appears.
Select the Oracle Metadata Services and Oracle Platform Security Services check boxes, and click Next.
The Domain Directory screen appears.
In the Directory field, enter the WebLogic domain directory for the domain to be upgraded and click Next.
The Prerequisites screen appears.
Confirm that the database backup is complete by selecting the All affected data is backed up, Database version is certified by Oracle for Fusion Middleware upgrade, and Certification and system requirements have been met check boxes, and click Next.
The OPSS Schema screen appears.
From the Database Type list, select the database type.
In the Database Connect String field, enter the hostname:portnumber/SID string.
Note:
For a clustered environment, the hostname:portnumber/SID must specify the primary Oracle RAC node.In the DBA User Name field, enter the database administrator user name.
In the DBA Password field, enter the password.
Click Connect.
If the provided details are valid, the Schema User Name and Schema Password fields become enabled.
From the Schema User Name list, select the OPSS schema.
In the Schema Password field, enter the database password, and click Next.
The MDS Schema screen appears.
From the Database Type list, select the database type.
In the Database Connect String field, enter the hostname:portnumber/SID string.
Note:
For a clustered environment, the hostname:portnumber/SID must specify the primary Oracle RAC node.In the DBA User Name field, enter the database administrator user name.
In the DBA Password field, enter the password.
Click Connect.
If the provided details are valid, the Schema User Name and Schema Password fields become enabled.
From the Schema User Name list, select the MDS schema.
In the Schema Password field, enter the database password, and click Next.
The Examine screen appears.
Click Next.
The Upgrade Summary screen appears.
Verify the details of the OPSS schema and MDS schema to be upgraded and click Upgrade.
The Upgrading Components screen appears. You can monitor the progress of the upgrade from this screen.
After the upgrade completes, click Next.
The Upgrade Success screen appears.
Verify that the upgrade was successful and click Close.
See Oracle Fusion Middleware documentation for more information.
Create the Audit Services (IAU, IAU_APPEND) schema and Common Infrastructure Services (STB) schema using the Oracle Fusion Middleware Repository Creation Utility 12c, which you open using the following command:
./MW_Home/oracle_common/bin/rcu
See Oracle Fusion Middleware Repository Creation Utility User's Guide for more information.
Reconfigure the WebLogic domain configurations using the Fusion Middleware Reconfiguration Wizard 12c, which you open using the following command:
./MW_Home/wlserver/common/bin/reconfig.sh
On the Select Domain screen, from the Existing Domain Location list, select the 7.2.4.x domain and click Next.
The Reconfiguration Setup Progress screen appears, displaying the progress of the reconfiguration setup process.
Click Next.
The Domain Mode and JDK screen appears.
The domain mode cannot be changed during reconfiguration. It is inherited from the original domain.
Select the JDK option and browse to the folder (JAVA_HOME) where JDK is installed and click Next.
The Database Configuration Type screen appears.
Select the RCU Data option, complete the required fields, and then click Get RCU Configuration, which retrieves the schema information.
You select the RCU Data option to connect to the database to retrieve schema information for all schemas that are included in the domain.
Click Next.
Navigate through the different screens by clicking Next on each screen and specify your settings as necessary.
On the Node Manager screen, under the Node Manager Type area, select Manual Node Manager Setup and click Next.
The Advanced Configuration screen appears.
Select the categories for which you want to perform advanced configuration and click Next.
For each category you select, the appropriate configuration screen is displayed to allow you to perform advanced configuration.
Navigate through the different screens by clicking Next on each screen and specify your settings as necessary.
On the Deployments Targeting screen, under Deployments, select the oracle.wsm.console.core.view library; under Targets, select the server or cluster, and then click the right arrow, which moves the library to the targeted server or cluster for deployment.
Note:
When targeting applications for deployment on a cluster, ensure that NICMWSAdapter and cartridge_management_ws are selected for only the first managed server of the cluster.Click Next.
The Services Targeting screen appears.
Under Services, select the services; under Targets, select the server or cluster, and then click the right arrow, which moves the services to the targeted server or cluster for deployment.
Note:
When targeting services to a cluster, ensure that CMWSPersistentDS, CMWSPersistentJDBCStore, and CMWSJMSModule are targeted to only the first managed server of the cluster.Click Next until the Configuration Summary screen appears.
Review the detailed configuration settings of the domain and click Reconfig.
The Reconfiguration Progress screen appears, which displays the progress of the reconfiguration process.
After the reconfiguration process completes, the Reconfiguration Success screen appears.
Click Finish.
See Oracle Fusion Middleware documentation for more information.
Upgrade the WebLogic domain configurations by doing the following:
Navigate to the MW_Home/oracle_common/upgrade/bin/ua directory.
This directory contains the Fusion Middleware Upgrade Assistant 12c, which you use to upgrade the WebLogic domain configurations.
Launch the Fusion Middleware Upgrade Assistant.
The Welcome screen appears.
Click Next.
Select WebLogic Component Configurations, in the Domain Directory field, enter the WebLogic domain directory you want to upgrade, and then click Next.
Navigate through the different screens by clicking Next on each screen and specify your settings as necessary.
On the Upgrade Success screen, verify that the upgrade was successful and click Close.
See Oracle Fusion Middleware documentation for more information.
Remove the ess-mbeans.xml file from the Domain_Home/config/fmwconfig/mbeans folder.
After you upgrade the WebLogic domain, do the following before starting the WebLogic Administration server.
If Network Integrity is installed in a WebLogic cluster domain, open the WL_DOMAIN/config/config.xml file and change the JD persistent store and NI persistent store targets to managed server migratables.
See "Installing and Configuring Oracle WebLogic Server" for more information.
If you use an external LDAP when installing Network Integrity 7.2.4.x, you must create a user named ni-internal in the external authentication provider store as a member of NetworkIntegrityRole. Ensure that you create the ni-internal user in the default security realm.
Start the Network Integrity Administration Server. If this is a clustered server environment, start the cluster member servers.
Ensure that all the deployed applications are active, otherwise you will need to manually update each application and then make each application active.
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.
To upgrade Network Integrity:
Create a directory (dir).
Download the software for your operating system from the Oracle software delivery website:
and save it to dir:
Extract the contents of the software pack to dir.
The extracted software pack has the following structure:
integrity/Disk1/install/
(IBM AIX only) Stop and restart the WebLogic Server domain for Network Integrity.
Run the following command:
./dir/integrity/Disk1/install/runInstaller -paramFile ../oraparam.ini -jreloc jre_Path
where jre_Path contains jre folder inside the JDK installation directory.
The Installer Welcome screen appears.
Click Next.
The Select Installation Type screen appears.
Select Complete and click Next.
The Available Product Components screen appears.
Select Network Integrity and click Next.
The Specify Home Details screen appears.
Do all of the following:
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.
In the Path field, enter, browse to, or confirm the directory where the folder specified in the Name field is located.
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.
(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.
Review the list of components to be upgraded and click Next.
The WebLogic Administration Server Connection Information screen appears displaying the current connection information.
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.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.
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 12c Enterprise Database and click Next.
The Database Connection Information screen appears.
Do the following:
Verify that the retrieved field values are correct and click Next.
In the Password field, enter the database server password for the user specified in the User Name field.
Click Next.
If your old installation is connected to an Oracle Real Application Clusters (RAC) database, select Oracle 12c Real Application Cluster Database and click Next.
The RAC DB Nodes Connection Information screen appears.
Do the following:
Verify that the retrieved field values are correct and click Next.
In the Password field, enter the database server password for the user specified in the User Name field.
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.Do the following:
Verify that the retrieved value in the Schema User Name field is correct.
In the Schema User Password field, enter the schema user password for the user specified in the Schema User Name field.
Click Next.
The NI User ni-internal secure credentials screen appears.
Do the following:
In the User Password field, define a password for the Network Integrity internal user.
In the Confirm The User Password field, enter the password again to confirm it.
Click Next.
The Summary screen appears.
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.
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, where NI_Home is the directory in which the Network Integrity software is installed).
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.
Click Installed Products and verify that the installed version for Network Integrity is correct.
Logon to the Network Integrity database instance and run the following data migration scripts:
Note:
You must use the same user name and password that you provided when you set up the database schema using RCU. See "Creating the Database (MetaData) Schema for Network Integrity" for more information.NI_Home/integrity/upgrade/migration/7.3.2.0.0_NetworkIntegrity_data_migration.sql
NI_Home/integrity/upgrade/migration/post_upgrade_data_changes.sql
In the Installer, click Exit.
After upgrading Network Integrity, do the following, if necessary:
Verify that the Network Integrity software upgrade was completed successfully. See "Verifying the Network Integrity Installation" for more information.
If you configured an Inventory System in the old version of Network Integrity and specified a password, you need to re-enter the password.
In the new version of Network Integrity, click Manage Import System.
Click Edit.
Enter the password and click Save and Close.
Migrate your cartridges to the new version of Network Integrity. See "Migrating Cartridges" for more information.
Re-deploy your cartridges. See "Deploying Network Integrity Cartridges" for more information.
In Network Integrity, edit all scans that use the Import Optical from UIM and Import Logical Optical from UIM scan action:
On the Manage Scans page, search for scans that use the Import Optical from UIM scan action.
In the search result, select each scan and do the following:
Click the Edit icon.
Click Save and Close.
On the Manage Scans page, search for scans that use the Import Logical Optical from UIM scan action.
In the search result, select each scan and do the following:
Click the Edit icon.
Click Save and Close.
These scans are updated with the new scan parameter groups from the Optical UIM Integration cartridge.
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 Network Integrity. Scan data is re-created when you run a scan.
Production cartridges (those with binaries supplied by Oracle) are already compatible with and can be deployed to the new version 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 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.
Ensure the imported project is not read-only. The cartridge migration will fail if the project is read-only.
It is important to make sure that all the dependent projects exist in the workspace before importing a Network Integrity project. 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, move the dependent project to the top of the order in the cartridge upgrade dialog, so that the dependent project will be migrated first.
To migrate a custom cartridge (a cartridge with binaries not supplied by Oracle):
Using the old Design Studio environment for Network Integrity, do the following:
Select the Design Studio perspective.
Select the Studio Projects view.
Select the cartridge project and, from the Project menu, unseselect Build Automatically.
From the Project menu, select Clean.
Select the Navigation view.
Right-click the cartridge project folder and select Close Project.
Using the new installation of Design Studio for Network Integrity, do the following:
Select the Design Studio perspective.
Select the Studio Projects view.
Right-click anywhere in the Studio Projects view and select Import.
The Import Project dialog box appears.
Verify that the imported project is not "read-only."
Locate the cartridge project and import it.
Double-click the cartridge project folder.
The cartridge properties appear.
Verify that the Target Version field value matches the Network Integrity version.
Note:
If the Target Version field is not editable, it may mean that the cartridge is sealed, read-only, or under source control.Perform all necessary pre-build steps particular to your cartridge.
From the Project menu, enable Build Automatically.
From the Project menu, select Clean.
The cartridge project is automatically built. The binary file is produced and written to the cartridgeBin directory.
To upgrade Network Integrity:
Create a directory (dir).
Download the software for your operating system from the Oracle software delivery web site:
and save it to dir:
Extract the contents of the software pack to dir.
The extracted software pack has the following structure:
integrity/Disk1/install/
(IBM AIX only) Stop and restart the WebLogic Server domain for Network Integrity.
Run the following command:
./dir/integrity/Disk1/install/runInstaller -paramFile ../oraparam.ini -jreloc jre_Path
where jre_Path contains jre folder inside the JDK installation directory.
The Installer Welcome screen appears.
Click Next.
The Select Installation Type screen appears.
Select Complete and click Next.
The Available Product Components screen appears.
Select Network Integrity and click Next.
The Specify Home Details screen appears.
Do all of the following:
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.
In the Path field, enter, browse to, or confirm the directory where the folder specified in the Name field is located.
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.
(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.
Review the list of components to be upgraded and click Next.
The WebLogic Administration Server Connection Information screen appears displaying the current connection information.
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.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.
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 12c Enterprise Database and click Next.
The Database Connection Information screen appears.
Do the following:
Verify that the retrieved field values are correct and click Next.
In the Password field, enter the database server password for the user specified in the User Name field.
Click Next.
If your old installation is connected to an Oracle Real Application Clusters (RAC) database, select Oracle 12c Real Application Cluster Database and click Next.
The RAC DB Nodes Connection Information screen appears.
Do the following:
Verify that the retrieved field values are correct and click Next.
In the Password field, enter the database server password for the user specified in the User Name field.
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.Do the following:
Verify that the retrieved value in the Schema User Name field is correct.
In the Schema User Password field, enter the schema user password for the user specified in the Schema User Name field.
Click Next.
The NI User ni-internal secure credentials screen appears.
Do the following:
In the User Password field, define a password for the Network Integrity internal user.
In the Confirm The User Password field, enter the password again to confirm it.
Click Next.
The Summary screen appears.
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.
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.
Click Installed Products and verify that the installed version for Network Integrity is correct.
Logon to the Network Integrity database instance and run the following data migration scripts:
Note:
You must use the same user name and password that you provided when you set up the database schema using RCU. See for more information.NI_Home/integrity/upgrade/migration/7.3.2.0.0_NetworkIntegrity_data_migration.sql
NI_Home/integrity/upgrade/migration/post_upgrade_data_changes.sql
In the Installer, click Exit.
After upgrading Network Integrity, do the following, if necessary:
Verify that the Network Integrity software upgrade was completed successfully. See "Verifying the Network Integrity Installation" for more information.
If you configured an Inventory System in the old version of Network Integrity and specified a password, you need to re-enter the password.
In the new version of Network Integrity, click Manage Import System.
Click Edit.
Enter the password and click Save and Close.
Migrate your cartridges to the new version of Network Integrity. See "Migrating Cartridges" for more information.
Re-deploy your cartridges. See "Deploying Network Integrity Cartridges" for more information.
In Network Integrity, edit all scans that use the Import Optical from UIM and Import Logical Optical from UIM scan action:
On the Manage Scans page, search for scans that use the Import Optical from UIM scan action.
In the search result, select each scan and do the following:
Click the Edit icon.
Click Save and Close.
On the Manage Scans page, search for scans that use the Import Logical Optical from UIM scan action.
In the search result, select each scan and do the following:
Click the Edit icon.
Click Save and Close.
These scans are updated with the new scan parameter groups from the Optical UIM Integration cartridge.
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 Network Integrity. Scan data is re-created when you run a scan.
Production cartridges (those with binaries supplied by Oracle) are already compatible with and can be deployed to the new version 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 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.
Ensure the imported project is not read-only. The cartridge migration will fail if the project is read-only.
It is important to make sure that all the dependent projects exist in the workspace before importing a Network Integrity project. 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, move the dependent project to the top of the order in the cartridge upgrade dialog, so that the dependent project will be migrated first.
To migrate a custom cartridge (a cartridge with binaries not supplied by Oracle):
Using the old Design Studio environment for Network Integrity, do the following:
Select the Design Studio perspective.
Select the Studio Projects view.
Select the cartridge project and, from the Project menu, unseselect Build Automatically.
From the Project menu, select Clean.
Select the Navigation view.
Right-click the cartridge project folder and select Close Project.
Using the new installation of Design Studio for Network Integrity, do the following:
Select the Design Studio perspective.
Select the Studio Projects view.
Right-click anywhere in the Studio Projects view and select Import.
The Import Project dialog box appears.
Verify that the imported project is not "read-only."
Locate the cartridge project and import it.
Double-click the cartridge project folder.
The cartridge properties appear.
Verify that the Target Version field value matches the Network Integrity version.
Note:
If the Target Version field is not editable, it may mean that the cartridge is sealed, read-only, or under source control.Perform all necessary pre-build steps particular to your cartridge.
From the Project menu, enable Build Automatically.
From the Project menu, select Clean.
The cartridge project is automatically built. The binary file is produced and written to the cartridgeBin directory.
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.