Oracle® Communications
Network Integrity

Installation Guide

Release 7.3.2

E66031-01

May 2016

Oracle Communications Network Integrity Installation Guide, Release 7.3.2

E66031-01

Copyright © 2010, 2016, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Related Documents

- Documentation Accessibility

- Document Revision History

1 Network Integrity Installation Overview

- Directory Placeholders Used in This Guide

- Overview of the Installation Procedure

- About the Installer

- Installation Options

- Ensuring a Successful Installation

2 Network Integrity System Requirements

- Software Requirements

- Supported Operating Systems

- Required Software

- Supported Software

- Hardware Requirements

- Information Requirements

- WebLogic Connection Information

- Database Connection Information

- Database Connection Information for Real Application Cluster Database

- Schema User Name Information

- Hardware Sizing Considerations

3 Installing and Configuring the Oracle Database

- Oracle Database Installation

- Oracle Database Configuration

- Creating a Tablespace for Network Integrity

- Setting the Database Time Zone

- Creating the Database (MetaData) Schema for Network Integrity

- Installing and Configuring Database Real Application Clusters

- Tuning the Database

4 Installing and Configuring Oracle WebLogic Server

- About Java Requirements

- Installing IBM Java

- Installing JDK

- Downloading and Installing WebLogic Server

- Installing Patches

- Installing Application Development Runtime

- Installing Patches

- Creating/Extending a WebLogic Server Domain for a Single Managed Server Installation

- Setting Memory Requirements for Network Integrity

- Creating a WebLogic Server Domain for a Server Cluster Installation

- Installation Scenario

- Server Cluster Example

- Network Integrity Server Cluster Prerequisites

- Overview of Steps for Setting Up Network Integrity on a Server Cluster

- Installing WebLogic Server and Network Integrity in a Clustered Environment

- Creating a Domain

- Starting the WebLogic Server

- Starting the Cluster Member Servers

- Configuring the WebLogic Server StuckThreadMaxTime Value

- Configuring Automatic Service Migration (ASM) on the WebLogic Server

- Verifying WebLogic Administration Server Migration

5 Installing and Configuring Additional Software

- Overview of Additional Installation Tasks

- Installing and Configuring Oracle Internet Directory

- Configuring the Authentication Provider

- Configuring Custom Authentication Providers

- Installing and Configuring BI Publisher

6 Installing Network Integrity

- Types of Installation

- Installing Network Integrity by Using Interactive Install

- Installing Network Integrity in Silent Mode

- About the Response File

- Populating the Response File

- Starting Silent Mode Installation

7 Network Integrity Post-Installation Tasks

- Overview of Network Integrity Post-Installation Tasks

- About the Trusted Certificate for Network Integrity

- Managing Network Integrity Cartridges

- Deploying Network Integrity Cartridges

- Deploying Cartridges with the Network Integrity Cartridge Deployer Tool

- Undeploying Cartridges with the Network Integrity Cartridge Deployer Tool

- Deploying and Undeploying Cartridges on a Remote Server

- Deploying Cartridges into Cluster Environments That Use Proxy Server

- Viewing Cartridges with the Network Integrity Cartridge Deployer Tool

- Managing Cartridges With Custom Scripts

- Developing a Custom Java Application

- Developing Custom ANT Tasks

- Running Cartridge Operations From a Command-Line

- Configuring Network Integrity for Inventory Management

- Installing Network Integrity Report Templates

- Starting the AgeOut Process

- Enabling HTTP Tunneling

- Setting Up Oracle Internet Directory

8 Verifying the Network Integrity Installation

- Checking the State of all Installed Components

- Logging In to Network Integrity

9 Upgrading Network Integrity

- About Upgrading Network Integrity

- Supported Upgrade Paths

- Planning Your Upgrade

- Testing the Upgrade in a Test Environment

- Upgrade Impacts

- Upgrade Impacts From 7.2.4.x to 7.3.2

- Fusion Middleware Changes

- Java Development Kit changes

- WebLogic Server Changes

- Database Software Changes

- Database Schema Changes

- Application Component Changes

- Design Studio Changes

- Cartridge Changes

- Upgrading Network Integrity

- Pre-Upgrade Tasks (7.2.4.x to 7.3.2)

- Upgrading Network Integrity (7.2.4.x to 7.3.2)

- Post-Upgrade Tasks (7.2.4.x to 7.3.2)

- Migrating Cartridges

- Upgrading Network Integrity (7.3.0 to 7.3.2)

- Post-Upgrade Tasks (7.3.0 to 7.3.2)

- Migrating Cartridges

- About Rolling Back Network Integrity

10 Setting Up Network Integrity for Single Sign-On Authentication

- Installing Required Software

- Configuring Network Integrity to Enable SSO Authentication

- Installing and Deploying Network Integrity Specifying the External LDAP Provider

- Configuring the Frontend URL in Administration Console

- Creating and Configuring Authentication Providers for OAM SSO

- Configuring web.xml for the OAM Identity Asserter

- Configuring the mod_wl_ohs Plug-In for Oracle HTTP Server

- Protecting Resources For SSO Authentication

- Excluding Resources From SSO Authentication

11 Installing Patches

- About Patching Network Integrity

- Planning Your Patch Installation

- Installing a Patch

12 Uninstalling Network Integrity

- About Uninstalling Network Integrity

- Uninstalling Network Integrity or Network Integrity Components

- Uninstalling Network Integrity Using the Silent Mode

13 Troubleshooting the Network Integrity Installation

- Common Problems and Their Solutions

- Problem: Installer Fails to Update Application KEYSTORE Table

- Solution

- Problem: Installer Fails to Update Application INFORMATION Table

- Solution

- Problem: Inability To Run Scans or Resolve Discrepancies After Upgrading

- Solution

- Problem: Unable to Load Performance Pack

- Solution

- Problem: Application Server Takes a Long Time to Start

- Solution

- Reporting Problems

Preface

This guide provides instructions for installing Oracle Communications Network Integrity.

Audience

This document is for system administrators, database administrators, and developers who install and configure Network Integrity. The person installing the software should be familiar with the following topics:

- Operating system commands

- Database configuration

- Oracle WebLogic Server

- Network management

Before reading this guide, you should have familiarity with Network Integrity. See Network Integrity Concepts.

Network Integrity requires Oracle Database and Oracle WebLogic Server. See the documentation for these products for installation and configuration instructions.

Related Documents

Network Integrity Installation Guide is one book in the following set of resources that comprise the Network Integrity documentation suite. The resources include:

- Network Integrity Concepts: Provides an outline of Network Integrity high-level concepts and architecture.

- Network Integrity System Administrator's Guide: Describes, and provides procedures for, the tasks, such as managing and monitoring the Network Integrity system, that a Network Integrity system administrator performs.

- Network Integrity Security Guide: Provides information about all Network Integrity security features, and information about how to install and set up Network Integrity in the most secure deployment configuration possible.

- Network Integrity Developer's Guide: Explains how to customize and extend many aspects of Network Integrity, including the schema, user interface, rule sets, web services, life-cycle management, topology, security, and localization.

- Oracle Communications Information Model Reference: Describes entities and patterns in the Oracle Communications Information Model. The Information Model entities and patterns that are available within Network Integrity, and the application-specific capabilities applied to entities within Network Integrity, are described in Network Integrity Developer's Guide. Oracle Communications Information Model Reference is a password-protected document on the Oracle software delivery website.

- Network Integrity Release Notes: Provides information like new features and known issues for Network Integrity.

- Online Help: Provides instructions for tasks you perform in Network Integrity.

- Cartridge Guides: Describe the content of product technology packs and configuration guidelines and implementation considerations.

- Network Integrity Cisco Router and Switch SNMP Cartridge Guide

- Network Integrity Cisco Router and Switch UIM Integration Cartridge Guide

- Network Integrity CLI Cartridge Guide

- Network Integrity CORBA Cartridge Guide

- Network Integrity File Transfer and Parsing Guide

- Network Integrity Incremental TMF814 Discovery Cartridge Guide

- Network Integrity MIB-II SNMP Cartridge Guide

- Network Integrity MIB-II UIM Integration Cartridge Guide

- Network Integrity MSS Integration Cartridge Guide

- Network Integrity Optical Circuit Assimilation Cartridge Guide

- Network Integrity Optical TMF814 CORBA Cartridge Guide

- Network Integrity Optical UIM Integration Cartridge Guide

- Network Integrity TL1 Cartridge Guide

- Network Integrity UIM Integration Cartridge Guide

- Oracle Communications Design Studio Platform Online Help: Provides step-by-step instructions for tasks you perform in Design Studio. This help provides a separate section for Network Integrity-related tasks called Modeling Network Integrity.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Document Revision History

The following table lists the revision history for this guide:

Version

Date

Description

E66031-01

May 2016

Initial release.

1 Network Integrity Installation Overview

This chapter provides an overview of the installation process of Oracle Communications Network Integrity.

Directory Placeholders Used in This Guide

Table 1-1 lists the placeholders that are used in this guide:

Table 1-1 Network Integrity Directory Placeholders

Placeholder

Description

NI_Home

The directory in which the Network Integrity software is installed.

MW_Home

The directory in which the Oracle Fusion Middleware products, files, and folders are installed, such as WebLogic Server. Also contains the utils directory.

WL_Home

The directory in which WebLogic Server is installed. WL_Home is located in MW_Home.

Domain_Home

The directory containing the configuration for the domain into which Network Integrity is installed. The default location is MW_Home/user_projects/domains/domain_name, where domain_name is the name of the WebLogic Server domain for Network Integrity.

Overview of the Installation Procedure

The following is an outline of the installation procedure for Network Integrity:

1. Plan your installation, including:

- Determine the scale of your implementation; for example, is it a small test system, or a large production system. To determine the scale, you may need to assess the scale of the network or data set to be discovered or reconciled.

- Assess how many physical systems you need, and which software components to install on which systems.

- Plan the system topology; for example, determining whether you want a single managed server deployment or a clustered deployment.

2. Review the system requirements, as described in "Network Integrity System Requirements".

3. Install and configure the Oracle Database, as described in "Installing and Configuring the Oracle Database".

4. Install and configure the Oracle WebLogic server, as described in "Installing and Configuring Oracle WebLogic Server".

5. Install and configure additional software, as described in "Installing and Configuring Additional Software".

6. Install Network Integrity, as described in "Installing Network Integrity".

7. Perform post-installation configuration tasks, as described in "Network Integrity Post-Installation Tasks".

8. Verify the installation, as described in "Verifying the Network Integrity Installation".

About the Installer

You install Network Integrity using the Oracle Universal Installer. The Installer installs the core application and configures connections with the components, according to the connection details you provide during installation. See the Oracle Universal Installer documentation for more information about the Installer.

Installation Options

You can install Network Integrity in GUI mode (using the Installer) or in silent mode.

- GUI mode: Use the Installer when you want to interact with the graphical installation screens during the installation process.

- Silent mode: Use silent mode when you are repeatedly installing Network Integrity using the same configuration. Silent mode does not use the GUI and runs in the background.

Ensuring a Successful Installation

Network Integrity installations should be performed only by qualified personnel. You must be familiar with the following before you begin the installation:

- UNIX operating system

- Oracle WebLogic Server administration

- Oracle Database administration

- Installing Java-related packages

Oracle recommends that the installation and configuration of the Oracle database be performed by an experienced database administrator.

Follow these guidelines:

- As you install each component verify that the component installed successfully before continuing the installation process.

- Pay close attention to the system requirements. Before you begin installing the application, ensure your system has the required base software. In addition, ensure that you know all of the required configuration values, such as host names and port numbers.

- Make a note of any new configuration values as you create them. You are required to enter configuration values later in the procedure.

2 Network Integrity System Requirements

This chapter describes the hardware, operating system, software, server, and database requirements for installing Oracle Communications Network Integrity.

Software Requirements

Network Integrity consists of a base application that is installed on an Oracle WebLogic server domain. It connects with an Oracle database to store all relevant information, and can connect to a report publishing tool if you require reports to be published. You must install and connect all required software with Network Integrity for optimal performance.

Supported Operating Systems

Table 2-1 lists operating systems that support the Network Integrity server. Use the My Oracle Support Certifications tab to access the latest software platform support information. See knowledge article 1491004.1 or the My Oracle Support Help on the My Oracle Support Web site for additional information:

https://support.oracle.com

Table 2-1 Supported Server-Side Operating Systems

Product

Version

Oracle Linux on x86 (64-bit)

Linux 5 update 8 or higher (such as Linux 5.8, 5.9, or 5.10)

Linux 6 update 2 or higher (such as Linux 6.2, 6.3, or 6.4)

Oracle recommends the latest available update.

Red Hat Enterprise Linux on x86 (64-bit)

Linux 5 update 8 or higher (such as Linux 5.8, 5.9, or 5.10)

Linux 6 update 2 or higher (such as Linux 6.2, 6.3, or 6.4)

Oracle recommends the latest available update.

Oracle Solaris on SPARC (64-bit)

10, 11

Oracle VM on x86

3.0.2

IBM AIX on POWER Hardware (64-bit)

6.1 Technology Level (TL) 6 SP2

HP-UX Itanium

11i v3 (11.31)

Note:
When installing Network Integrity in a multihost shared-disk cluster environment, you must have full permissions on the NI_Home, MW_Home, WL_Home, and Domain_Home directories.
where:

- NI_Home is the directory in which the Network Integrity software is installed.

- MW_Home is the directory in which the Oracle Fusion Middleware products, files, and folders are installed.

- WL_Home is the directory in which WebLogic Server is installed. WL_Home is located in MW_Home.

- Domain_Home is the directory containing the configuration for the domain into which Network Integrity is installed.

Required Software

Table 2-2 lists software required on the server for installing and running Network Integrity.

Table 2-2 Required Server-Side Software

Product

Version

Oracle WebLogic Server Enterprise Edition (included with the Oracle Fusion Middleware WebLogic Server and Coherence distribution in the Oracle Fusion Middleware 12c software)

12c (12.1.3.0.0)

Oracle WebLogic Server Patch

20838345

Oracle Fusion Middleware Application Development Runtime, including Enterprise Manager and Repository Creation Utility (included with the Oracle Fusion Middleware Infrastructure distribution in the Oracle Fusion Middleware 12c software)

12c (12.1.3.0.0)

Oracle Application Development Runtime Patches

18843495 (for release 12.1.3.0.0), 19393515, 18609420, and 20479164.

After applying patch 20479164, you must clear your Web browser's cache and restart the application server.

Oracle Fusion Middleware Repository Creation Utility (RCU) for Linux

12c (12.1.3)

Sun Hotspot (JDK) for Linux or Solaris

Linux: Java 7 with latest critical patch update

Solaris: Java 7 with latest critical patch update

IBM Java SE Runtime Environment for IBM AIX

Java 7 with latest critical patch update

Java SE Runtime Environment for HP-UX

Java 7 with latest critical patch update

Oracle Database Enterprise Edition

12c Release 1 (12.1.0.2.0)

Includes support for multitenant container database (CDB) and pluggable database (PDB)

Oracle Database Patch

20831110

The Network Integrity Installer checks for all required software and displays errors if it detects any missing or unavailable components, or if there are any connectivity related issues.

Table 2-3 lists software required to access the Network Integrity UI.

Table 2-3 Required Client-Side Software

Product

Version

Operating System

Microsoft Windows 7

Java Runtime Environment (JRE)

Java 7 and 8 with latest critical patch update

Web Browser

Microsoft Internet Explorer (IE) 9, 10, or 11

Mozilla Firefox 31.x

Oracle Communications Design Studio

7.3.2

Oracle Fusion Middleware JDeveloper Studio Generic

12c (12.1.3.0.0)

Design Studio is required for developing cartridges that extend Network Integrity. Install Design Studio on a computer with network access to the Network Integrity server.

Supported Software

Table 2-4 lists additional software that is supported by Network Integrity.

Table 2-4 Supported Software

Product

Version

Oracle Business Intelligence (BI) Publisher

11g R1 PS7 (11.1.1.9)

BI Publisher is required to use the reporting templates included with Network Integrity.

Oracle Communications Unified Inventory Management (UIM)

7.3.3

Oracle Communications MetaSolv Solution (MSS)

6.2.1

Oracle Internet Directory

11.1.1.7 or higher

Supported software is installed and licensed separately from Network Integrity.

Hardware Requirements

The number and configuration of the systems that you employ for your Network Integrity installation depends on the scale and the kind of deployment you have planned according to your network(s).

Note:
The sizing estimates contained in this section are based on the assumptions of proper application configuration and tuning, in a manner consistent with leading practices of Oracle Communications consulting and performance engineering. This information is provided for informational purposes only and is not intended to be, nor shall it be construed as a commitment to deliver Oracle programs or services. This document shall not form the basis for any type of binding representation by Oracle and shall not be construed as containing express or implied warranties of any kind. You understand that information contained in this document will not be a part of any agreement for Oracle programs and services. Business parameters and operating environments vary substantially from customer to customer and as such not all factors, which may impact sizing, have been accounted for in this documentation.

Table 2-5 provides the minimal hardware requirement for Network Integrity installed on a single managed server in a WebLogic domain.

Table 2-5 Network Integrity Minimum Hardware Requirements

Component

Requirement

Hard disk

4 GB for all required software.

1.5 GB for Network Integrity.

1 GB to 3 GB for supported software.

Processor

Oracle recommends using twin cores, each running at 1.5 GHz CPU.

Note: A minimum of 1.5 GB free space should be available in the Oracle WebLogic server domain home.

Memory

If Network Integrity is installed on a different server from the database: a minimum of 4 GB physical memory and 4 GB swap.

If Network Integrity is installed on the same server as the database: a minimum of 6 GB physical memory and 6 GB swap.

Temporary disc space

150 MB

The Network Integrity Installer uses a temporary directory to extract all installation files.

These files are deleted after installation.

Information Requirements

During Network Integrity installation, you must enter configuration values such as host names and port numbers. This section describes the information that you must provide during the installation process. You define some of these configuration values when you install and configure the Oracle database and WebLogic Server.

If you have already installed other Oracle Communications products, the installer reads the values from the existing Oracle Communications products and uses them as default values. If no existing Oracle Communications products are installed, the installer proposes default values.

WebLogic Connection Information

Table 2-6 lists WebLogic Server and domain connection details that you are required to provide during installation.

Table 2-6 Application Server Connection Information

Information Type

Description

Host name

The host name for the particular WebLogic server instance to define it uniquely for the specific purpose of installing, and working with, Network Integrity.

Port number

This is the number assigned to this specific service. Port numbers are usually pre-defined and you can accept the provided default value.

User name

Your WebLogic Server user name. You define this name when you install Oracle WebLogic Server.

Password

Your password to connect to the WebLogic server as the user for which you provided the user name. You define this password along with the user name during the Oracle WebLogic Server installation.

Database Connection Information

Table 2-7 lists database connection details that you are required to provide during installation.

Table 2-7 Database Connection Information

Information Type

Description

Host name

Host name or IP address of the Oracle Database server for Network Integrity.

Port number

This is the number assigned to this specific service. Port numbers are usually pre-defined and you can accept the provided default value.

User name

Your database user name. You define the user name when you install the database.

Password

Your password to connect to the database as the user for which you provided the user name. You define this password along with the user name during database installation.

Service name

This is the name of the database service or instance to remotely connect to the database. For example, oracle.com.

Database Connection Information for Real Application Cluster Database

Table 2-8 lists database connection details for an Oracle Real Application Cluster (RAC) database that you are required to provide during installation.

Table 2-8 Database Connection Information for Oracle RAC Database

Information Type

Description

Oracle RAC database connection string

The information string that is used to connect to the Oracle RAC database. For example, HOST NAME1:PORT1:SERVICE NAME1, HOST NAME2:PORT2:SERVICE NAME2.

User name

A database user name with SYS privileges. You define the user name when you install the database.

Password

Your password to connect to the database as the user for which you provided the user name. You define this password along with the user name during database installation.

Schema User Name Information

Table 2-9 lists schema user details that you are required to provide during installation.

Table 2-9 Schema user Information

Information Type

Description

Schema user name

Your schema user name that you use to access the Network Integrity schema.

Schema user password

The password to access the Network Integrity schema for the schema user you defined.

Hardware Sizing Considerations

Use Table 2-10 as a general guideline when planning the hardware for your Network Integrity system.

Note:
The information in this section is meant as a guideline only. The values in this section are approximate. Accurate sizing for a production system requires a detailed analysis of the proposed business requirements.

Note:
For information on hardware sizing requirements for HP-UX Itanium, contact Oracle Support.

Note:
The Network Integrity installer supports Internet Protocol version 6 (IPv6) addresses. You can install and deploy Network Integrity on servers that support IPv6 addresses.

Table 2-10 Network Integrity Hardware Planning Guideline

System Size and Range

Solaris

Linux

IBM AIX

Oracle Database Server

Small

- Up to 35,000 reconciled devices

- Up to 100,000 assimilated circuits

Sun server:

- 2 x Ultra SPARC64-VII quad core CPUs at 2.4GHz or 1 x SPARC T4 8 core CPUs at 2.95GHz

- 8 GB RAM

- 2x 146 GB disk space

Sun server:

- 1 x Intel E5620 quad core CPU at 2.4GHz

- 8 GB RAM

- 2x 146 GB disk space

IBM server:

- 1 x POWER6 quad core CPUs at 5.0GHz

- 8 GB RAM

- 2x 146 GB disk space

Solaris or Linux server:

- 8 threads at 2.9GHz

- 8 GB RAM

- 500 GB disk space

Network Integrity tablespace- 200GB

Medium

- Between 30,000 and 70,000 reconciled devices

- Between 80,000 and 220,000 assimilated circuits

Sun server:

- 2 x Ultra SPARC64-VII quad core CPUs at 2.4GHz or 2 x SPARC T4 8 core CPUs at 2.95GHz

- 20 GB RAM

- 2x 146 GB disk space

Sun server:

- 1 x Intel E5-2690 8 core CPU at 2.9GHz

- 20 GB RAM

- 2x 146 GB disk space

IBM server:

- 2 x POWER6 quad core CPUs at 5.0GHz

- 20 GB RAM

- 2x 146 GB disk space

Solaris or Linux server:

- 16 threads at 2.9GHz

- 16 GB RAM

- 800 GB disk space

Network Integrity tablespace- 200GB

Large

- Between 50,000 and 75,000 reconciled devices

- Between 200,000 and 420,000 assimilated circuits

Sun server:

- 2 x Ultra SPARC64-VII quad core CPUs at 2.4GHz or 2 x SPARC T4 8 core CPUs at 2.95GHz

- 32 GB RAM

- 2x 146 GB disk space

Sun server:

- 1 x Intel E5-2690 8 core CPU at 2.9GHz

- 32 GB RAM

- 2x 146 GB disk space

IBM server:

- 2 x POWER6 quad core CPUs at 5.0GHz

- 32 GB RAM

- 2x 146 GB disk space

Solaris or Linux server:

- 16 threads at 2.9GHz

- 16 GB RAM

- 1 TB disk space

Network Integrity tablespace - 250GB

Note: Increase thread to 32 and increase RAM to 32 GB for circuit assimilation in excess of 200,000 circuits.

Extra-large (multi-node cluster)

- Between 70,000 and 110,000 reconciled devices

- More than 400,000 assimilated circuits

2x Sun server:

- 2 x Ultra SPARC64-VII quad core CPUs at 2.4GHz or 2 x SPARC T4 8 core CPUs at 2.95GHz

- 32 GB RAM

- 2x 146 GB disk space

2x Sun server:

- 1 x Intel E5-2690 8 core CPU at 2.9GHz

- 32 GB RAM

- 2x 146 GB disk space

2x IBM server:

- 2 x POWER6 quad core CPUs at 5.0GHz

- 32 GB RAM

- 2x 146 GB disk space

Solaris or Linux server:

- 16 threads at 2.9GHz

- 32 GB RAM

- 1.8 TB disk space

Network Integrity tablespace - 450GB

Note: Increase thread to 32 for circuit assimilation in excess of 200,000 circuits. Contact your sales representative for a custom sizing recommendation for circuit assimilation in excess of 400,000 circuits.

3 Installing and Configuring the Oracle Database

This chapter describes the process of installing the Oracle database and configuring the Oracle Database for Oracle Communications Network Integrity.

Oracle Database Installation

Network Integrity must be installed in an Oracle Database tablespace. See Table 2-2, "Required Server-Side Software" for database requirements.

For information on installing Oracle Database, see the Oracle Database installation documentation.

Note:
Configure the Oracle Database with the XDB component.

Oracle Database Configuration

The Oracle database must be configured for Network Integrity. Specifically, this section covers the following:

- Creating a Tablespace for Network Integrity

- Setting the Database Time Zone

- Creating the Database (MetaData) Schema for Network Integrity

- Installing and Configuring Database Real Application Clusters

- Tuning the Database

Creating a Tablespace for Network Integrity

Create a Network Integrity specific tablespace according to the Oracle Database documentation. See Table 2-10, "Network Integrity Hardware Planning Guideline" for tablespace sizing guidelines.

Setting the Database Time Zone

Oracle Database must have the correct time zone setting, because Network Integrity uses the datatype TIMESTAMP WITH LOCAL TIME ZONE in its database schema.

See Oracle Database Globalization Support Guide for information and instructions on setting the time zone.

Note:
After Network Integrity has been installed, the database time zone cannot be changed. Ensure the time zone is correctly set before installing Network Integrity.

Creating the Database (MetaData) Schema for Network Integrity

The MetaData schema is an Oracle Fusion Middleware component that is required by Network Integrity. You create the schema using the Repository Creation Utility (RCU).

Note:
A new schema must be created for all new Network Integrity installations. Upgrade installations will use the schema created during the installation of that Network Integrity instance.
The Repository Creation Utility can run on the Linux (32 bit) and Microsoft Windows platforms. A Linux or Windows system can be used to remotely access and configure the database.

To create the schema for Network Integrity using RCU:

1. Export the environment variables by running one of the following commands:

export JAVA_HOME= $JDK_HOME

or

export ORACLE_HOME=$mw_home

2. Run the following command:

. /MW_Home/oracle_common/bin/rcu

The Welcome screen of the Repository Creation Utility appears.

3. Click Next.
The Create Repository screen appears.

4. Select Create Repository and click Next.
The Database Connection Details screen appears.

5. Do the following:

1. From the Database Type list, select Oracle Database.

2. In the Host Name field, enter the database system host name or IP address.

3. In the Port field, enter the port number for the system hosting the database.

4. In the Service Name field, enter the service name.

5. In the Username field, enter the user name for the database user.

Note:
This user account must have the following privileges: CATALOG, CONNECT, Create User, Create Session, Grant Any Privilege, Grant Any Role, Select Any Table, Select any Dictionary.

Caution:
You must use the same user name and password when providing database user information during Network Integrity installation.

6. In the Password field, enter the password for the database user.

7. From the Role list, select SYSDBA.

8. Click Next.
The Checking Global Prerequisites screen appears, displaying the progress of establishing the connection with the specified database.

9. Click OK.

The Select Components screen appears.

6. On the Select Components screen, do the following:

1. Select Create new Prefix and enter the prefix value.

The prefix is any appropriate name for your schema. RCU adds a suffix to this name.

2. Expand Oracle AS Repository Components.

3. Expand AS Common Schemas and select Metadata Services, Audit Services, Audit Services Append, Audit Services Viewer, and Oracle Platform Security Services.

Note:
The Service Table (prefix_STB) schema is a default selection and you cannot change this selection.
where:

prefix is the prefix that you define in step 6a.

4. Click Next.
The Checking Component Prerequisites screen appears, displaying the progress of the component prerequisites check before the schemas are created.

5. Click OK.

The Schema Passwords screen appears.

7. Select Use same passwords for all schemas.

8. In the Password field, enter the password for the schema.

9. In the Confirm Password field, enter the password for the schema again and click Next.
The Map Tablespaces screen appears.

10. Review the entries on the Map Tablespaces screen and click Next.
The Summary screen appears.

11. Review and verify the information you have provided and click Create.
The Completion Summary screen appears, displaying details of the newly created repository.

12. Click Close.

Installing and Configuring Database Real Application Clusters

Oracle recommends Oracle Real Application Clusters (RAC) for high availability and scalability if your network data requires multiple databases for storage purposes. Refer to the Oracle Real Application Clusters documentation on the Oracle Help Center.

Tuning the Database

Table 3-1 and Table 3-2 provide the recommended database parameters for tuning your database for the Network Integrity installation. These are the minimum requirements for Network Integrity.

Table 3-1 Database Creation Parameters

Parameter

Recommended Value

SGA+PGA

At least 4 GB in total.

Oracle recommends that you use as much memory as you have available in the system, and also use Automatic Memory Management.

Processes

2000

Connection mode

Dedicated server

Redo log file size

1024 MB

Table 3-2 Database Initialization Parameters

Parameter

Recommended Value

db_file_multiblock_read_count

16

distributed_lock_timeout

7200

dml_locks

9700

job_queue_processes

10

log_buffer

31457280

open_cursors

5000

parallel_max_servers

640

plsql_code_type

NATIVE

4 Installing and Configuring Oracle WebLogic Server

Oracle Communications Network Integrity is installed and run on an instance of the WebLogic Administration Server. This chapter describes procedures relating to installing the WebLogic Administration Server and other required applications, and also configuring the WebLogic Server domain where you install Network Integrity.

Note:
Ensure that the Administration Server is running in the WebLogic Server domain before you install Network Integrity.

Installation and configuration tasks include:

- Installing IBM Java

- Installing JDK

- Downloading and Installing WebLogic Server

- Installing Application Development Runtime

- Creating/Extending a WebLogic Server Domain for a Single Managed Server Installation

- Creating a WebLogic Server Domain for a Server Cluster Installation

- Configuring Automatic Service Migration (ASM) on the WebLogic Server

About Java Requirements

Oracle WebLogic Server is a Java application and needs a Java environment in which to run. See "Required Software" for information about Java version requirements.

Installing IBM Java

Download the Java SDK from the IBM Web site.

For information on installing IBM Java, refer to IBM Java Installation documentation.

Installing JDK

Download JDK for the required platform from the Oracle Technology Network Web site:

http://www.oracle.com/technology

For information on installing JDK, see the JDK installation documentation.

Downloading and Installing WebLogic Server

Oracle WebLogic Server is available as a component of the Oracle Fusion Middleware software.

Download Oracle WebLogic Server from the Network Integrity software on the Oracle software delivery website:

https://edelivery.oracle.com/

For information about installing Oracle WebLogic Server, see the Oracle WebLogic Server documentation.

Installing Patches

After you install Oracle WebLogic Server, you must install any applicable patches.

See "Required Software" for information about patches for Oracle WebLogic Server.

Download the required patches from the My Oracle Support Web site:

https://support.oracle.com

Apply the patches using the OPatch tool.

For information about downloading and applying patches, see Knowledge Article 1302053.1 - Master Note: How to Locate and Download Patches for WebLogic Server Using My Oracle Support and Knowledge Article 1075833.1 - Master Note on WebLogic Server (WLS) Patches, Upgrade Installers, and Full Installers.

Installing Application Development Runtime

Download Oracle Application Development Runtime from the Network Integrity software on the Oracle software delivery website:

https://edelivery.oracle.com/

For installing Oracle Application Development Runtime, see the Oracle Fusion Middleware documentation on the Oracle Help Center.

Note:
The Oracle Fusion Middleware Application Developer Installer installs both Oracle Application Development Runtime and Oracle Enterprise Manager.
Install Application Developer with the same credentials used to install WebLogic Server.

For more information on the Application Development Framework, see Oracle Fusion Middleware Understanding Oracle Application Development Framework.

Installing Patches

After you install Oracle Application Development Runtime, you must install any applicable patches.

See "Required Software" for information about patches for Oracle Application Development Runtime.

Download the required patches from the My Oracle Support Web site:

https://support.oracle.com

Apply the patches using the OPatch tool.

Creating/Extending a WebLogic Server Domain for a Single Managed Server Installation

You extend the WebLogic Server domain when upgrading Network Integrity.

Before creating or extending a WebLogic Server domain, you must have finished installing Oracle Application Development Runtime. See "Installing Application Development Runtime" for more information.

To create or extend a WebLogic Server domain for a single managed server:

1. Go to MW_Home/wlserver/common/bin and run the WebLogic domain configuration script:

./config.sh

The Configuration Type screen of the Fusion Middleware Configuration Wizard appears.

2. Select the Create a new domain option and in the Domain Location field, enter the full path for the domain or click Browse to navigate to the directory in which your domains are located, and then click Next.
The Templates screen appears.

3. Select the Create Domain Using Product Templates option and from the provided list, select the following products:

- Basic WebLogic Server Domain (This product is selected by default and you cannot deselect it.)

- Oracle Enterprise Manager - 12.1.3.0 [em]

- Oracle JRF - 12.1.3.0 [oracle_common]

- WebLogic Coherence Cluster Extension - 12.1.3.0 [wlserver]

4. Click Next.
The Application Location screen appears.

The Domain name and Domain location fields are populated by default.

5. In the Application location field, enter the path and directory for the application files. For example, enter the value:

MW_Home/user_projects/applications/application_name

6. Click Next.
The Administrator Account screen appears.

7. In the Name field, enter the administrator user name.

8. In the Password field, enter the administrator user password. The password must be a minimum of 8 alphanumeric characters, and must contain at least one number or special character.
In the Confirm Password field, reenter your password.

9. Click Next.
The Domain Mode and JDK screen appears.

10. In the Domain Mode section, select the Production option.
In the JDK section, select the required JDK.

11. Click Next.
The Database Configuration Type screen appears.

12. Select the RCU Data option and enter the connection information that you specified for the Service Table (STB) schema component in the Repository Creation Utility (RCU):

1. In the Vendor field, select the vendor name for the component schema.

2. In the DBMS/Service field, enter the database management system or service name for the component schema.

3. In the Driver field, select the driver used by the component schema.

4. In the Host Name field, enter the host name/IP address for the component schema.

5. In the Port field, enter the port number used by the schema component.

6. In the Schema Owner field, enter the owner name for the schema component.

Note:
The default schema owner name is prefix_STB, where prefix is the prefix that you defined in RCU for the Service Table schema.

7. In the Schema Password field, enter the password for the schema component.

8. Click Get RCU Configuration, which retrieves the schema information.

9. After the schema information is retrieved successfully, click Next.
The JDBC Component Schema screen appears.

13. Verify the values in the fields and click Next.
The Test Component Schema screen appears, which enables you to test the configurations for the schemas.

14. Select the check boxes beside the schemas you want to test and click Test Selected Connections.

15. Verify that all the JDBC component connections pass the validation test and click Next.
The Advanced Configuration screen appears.

16. Select the services to install in the WebLogic Server domain:

- Administration Server

- Managed Servers, Clusters and Coherence

- Deployments and Services

Note:
Oracle recommends that production environments for Network Integrity use a minimum of an Administration Server and one or more Managed Servers or Clusters. Lab environments can be installed on an Administration Server only, if desired.
If you select only Administration Server, the Domain Creation wizard does not display some dialog boxes pertaining to managed servers or clusters.

17. Click Next.
The Administration Server screen appears.

18. Do the following:

1. In the Server Name field, enter the Administration Server name.
This single server serves as the Network Integrity domain Administration Server.

2. In the Listen Address field, select a DNS or an IP address.

Note:
Use listener addresses that are equal to a resolvable DNS host or IP address. Do not use localhost or 127.0.0.1. Those addresses interfere with clustered servers.

3. In the Listen Port field, accept the default.

4. Select the Enable SSL check box if you want to enable SSL.
It is not a requirement to either enable or disable SSL.

5. In the SSL Listen Port field, enter a port that is not used by another domain.
This field is enabled only if you selected the Enable SSL check box.

6. In the Server Groups list, accept the provided default value.

7. Click Next.
The Managed Servers screen appears.

19. Do the following:

1. In the Server Name field, enter the name for the managed server, if required.

2. In the Listen Address field, enter the host, or IP address of the system where the managed server is running.

Note:
Use listener addresses that are equal to a resolvable DNS host or IP address. Do not use localhost or 127.0.0.1. Those addresses interfere with clustered servers.

3. In the Listen Port field, enter the number of the port where the managed server listens for incoming messages.

4. Select the Enable SSL check box if you want to enable SSL.
It is not a requirement to either enable or disable SSL.

5. In the SSL Listen Port field, enter a port that is not used by another domain.
This field is enabled only if you selected the Enable SSL check box.

6. (Optional) Create additional managed servers as required on your Network Integrity deployment by clicking Add, and then configure the settings for the new managed servers.

7. Click Next.
The Clusters screen appears.

20. Click Next until the Deployments Targeting screen appears.

21. Under Targets, select the Administration Server; under Deployments, select the deployments; and then click the right arrow, which moves the applications to the Administration Server for deployment.

22. Repeat step 21 to target applications for deployment on the Network Integrity target server.

23. Click Next.
The Services Targeting screen appears.

24. Under Services, select the services; under Targets, select the Administration Server, and then click the right arrow, which moves the services to the Administration Server.

25. Repeat step 24 to target services to the Network Integrity target server.

26. Click Next.
The Configuration Summary screen appears.

27. Review the summary to verify the contents of your domain and click Create to create the domain.
The Configuration Progress screen appears, which displays the progress of the domain creation process.

After the domain is created successfully, the Configuration Success screen appears.

28. Click Finish.
See Oracle Fusion Middleware documentation for more information.

29. To set memory requirements, see "Setting Memory Requirements for Network Integrity".

30. Continue with the procedures in "Starting the WebLogic Server".
You can now log in to the Administration console and start the Administration Server manually.

Setting Memory Requirements for Network Integrity

You must set appropriate memory requirement values in the WebLogic server to be able to install multiple cartridges after Network Integrity installation. Not allotting enough memory space for the WebLogic domain can cause errors during cartridge deployment.

The following example shows the entries in the setDomainEnv.sh file for setting the memory requirement values for Network Integrity:

1. In the WebLogic domain bin folder, open the setDomainEnv.sh file.

2. Set the memory arguments for your JVM as follows:

WLS_MEM_ARGS_64BIT="-Xms20g -Xmx20g"

3. Set Perm size as:

MEM_PERM_SIZE_64BIT="-XX:PermSize=1024m"
MEM_MAX_PERM_SIZE_64BIT="-XX:MaxPermSize=1024m"

Note:
Although these values can be adjusted based on system memory availability, when using high-end systems, the above configuration is recommended for running Network Integrity.

Creating a WebLogic Server Domain for a Server Cluster Installation

A server cluster arrangement is used for load balancing, scalability, and failover. A clustered server installation (also called an Administration Server with cluster-managed servers installation) is one in which one or more WebLogic server instances are managed by a separate Administration Server. In this arrangement, clustering the Managed Servers in WebLogic allows the servers to work as one unit, rather than as several independent processing units. This is the configuration Oracle recommends because it provides protection if a server fails.

When working with a cluster, install the Cartridge Management Web Services (CMWS) and Network Integrity adapters on the system where the Administration server is running.

Caution:
Ensure that you run the Network Integrity Installer from the Administration server.

Installation Scenario

This installation scenario includes two clustered Managed Servers (networkintegrity01 and networkintegrity02) that are separate from the Administration Server, an Administration server, and a hardware load balancer, used for load balancing. Managed Servers are instances of WebLogic used to host enterprise applications, in this case, Network Integrity.

Note:
For more information on configuring the load balancer, see Network Integrity System Administrator's Guide.

This example uses a shared disk storage environment.

The advantages of using shared disk storage are: easier Network Integrity installation, maintenance, and cartridge deployment.

Using shared disk storage allows the Administration Server and all of the managed servers in the cluster to use the same instance of WebLogic. The systems on which the servers reside must have access to the shared storage.

Network Integrity does not support session replication; however, Network Integrity does support server failover.

Server Cluster Example

Refer to the values in Table 4-1 and Table 4-2 to set up the cluster arrangement.

Table 4-1 Server Cluster Example Values

Value

Example

Domain_Home

WL_Home/user_projects/domains/networkintegritycluster

Domain login

weblogic

Domain password

networkintegritycluster1

Cluster DNS

NetworkIntegrityClusterDNS

(It includes the networkintegrity01 and networkintegrity02 listening IP addresses.)

Table 4-2 Servers in a Sample Cluster

Value

Administration Server

Cluster-managed Server #1

Cluster-managed Server #2

WebLogic server

networkintegrityAdmin

networkintegrity01

networkintegrity02

Listening port

IP_Address:8063

IP_Address:8065

IP_Address:8066

Machine

NETINT1

NETINT2

NETINT3

Figure 4-1 shows the servers in a sample server cluster.

Figure 4-1 Servers in a Sample Cluster

Network Integrity Server Cluster Prerequisites

The prerequisites for setting up a Network Integrity server cluster are:

- Oracle WebLogic administration experience.

- A hardware load balancer is required. Refer to the server load balancer configuration for details.

- A DNS entry containing all of the cluster-managed servers' listening addresses serves as the Network Integrity cluster address.

- A system that hosts multiple cluster-managed servers must be multi-homed.

- All cluster-managed servers must reside in the same subnet for multicast traffic.

- Multicast is used for WebLogic cluster heart beats and JNDI updates.

- Ensure that multicasts do not collide in the same domain and other domains.

Overview of Steps for Setting Up Network Integrity on a Server Cluster

Note:
The figures shown in this section are for reference only. The actual server names that you use may be different from those shown in the figures.

For the considered scenario, installing Network Integrity on an Oracle WebLogic Server cluster arrangement involves:

- Installing Oracle WebLogic Server and Network Integrity software on the shared disk storage.

- Deleting all JMS resources.

- Creating server instances for each WebLogic server in your system, and creating your cluster.

- Deploying the Network Integrity data source and the Network Integrity transaction data source on the cluster.

- Modifying the startup script on the shared disk storage.

- Manually modifying the config.xml file.

- Starting up the Administration Server and all cluster-managed servers.

- Logging in to Network Integrity through the server load balancer.

Installing WebLogic Server and Network Integrity in a Clustered Environment

Before creating a WebLogic Server domain, you must have finished installing Oracle Application Development Runtime. See "Installing Application Development Runtime" for more information.

Install WebLogic on the shared disk storage.

After you install WebLogic:

- Create a domain

- Start the WebLogic server

- Install Network Integrity

Creating a Domain

To create a domain:

1. Go to MW_Home/wlserver/common/bin and run the WebLogic domain configuration script:

./config.sh

The Configuration Type screen of the Fusion Middleware Configuration Wizard appears.

2. Select the Create a new domain option and in the Domain Location field, enter the full path for the domain or click Browse to navigate to the directory in which your domains are located, and then click Next.
The Templates screen appears.

3. Select the Create Domain Using Product Templates option and from the provided list, select the following products:

- Basic WebLogic Server Domain (This product is selected by default and you cannot deselect it.)

- Oracle Enterprise Manager - 12.1.3.0 [em]

- Oracle JRF - 12.1.3.0 [oracle_common]

- WebLogic Coherence Cluster Extension - 12.1.3.0 [wlserver]

4. Click Next.
The Application Location screen appears.

The Domain name and Domain location fields are populated by default.

5. In the Application location field, enter the path and directory for the application files. For example, enter the value:

MW_Home/user_projects/applications/application_name

6. Click Next.
The Administrator Account screen appears.

7. In the Name field, enter the administrator user name.

8. In the Password field, enter the administrator user password. The password must be a minimum of 8 alphanumeric characters, and must contain at least one number or special character.
In the Confirm Password field, reenter your password.

9. Click Next.
The Domain Mode and JDK screen appears.

10. In the Domain Mode section, select the Production option.
In the JDK section, select the required JDK.

11. Click Next.
The Database Configuration Type screen appears.

12. Select the RCU Data option and enter the connection information that you specified for the Service Table (STB) schema component in the Repository Creation Utility (RCU):

1. In the Vendor field, select the vendor name for the component schema.

2. In the DBMS/Service field, enter the database management system or service name for the component schema.

3. In the Driver field, select the driver used by the component schema.

4. In the Host Name field, enter the host name/IP address for the component schema.

5. In the Port field, enter the port number used by the schema component.

6. In the Schema Owner field, enter the owner name for the schema component.

Note:
The default schema owner name is prefix_STB, where prefix is the prefix that you defined in RCU for the Service Table schema.

7. In the Schema Password field, enter the password for the schema component.

8. Click Get RCU Configuration, which retrieves the schema information.

9. After the schema information is retrieved successfully, click Next.
The JDBC Component Schema screen appears.

13. Verify the values in the fields and click Next.
The Test Component Schema screen appears, which enables you to test the configurations for the schemas.

14. Select the check boxes beside the schemas you want to test and click Test Selected Connections.

15. Verify that all the JDBC component connections pass the validation test and click Next.
The Advanced Configuration screen appears.

16. Select the services to install in the WebLogic Server domain:

- Administration Server

- Managed Servers, Clusters and Coherence

- Deployments and Services

Note:
Oracle recommends that production environments for Network Integrity use a minimum of an Administration Server and one or more Managed Servers or Clusters. Lab environments can be installed on an Administration Server only, if desired.
If you select only Administration Server, the Domain Creation wizard does not display some dialog boxes pertaining to managed servers or clusters.

17. Click Next.
The Administration Server screen appears.

18. Do the following:

1. In the Server Name field, enter the Administration Server name.
This single server serves as the Network Integrity domain Administration Server.

2. In the Listen Address field, select a DNS or an IP address.

Note:
Use listener addresses that are equal to a resolvable DNS host or IP address. Do not use localhost or 127.0.0.1. Those addresses interfere with clustered servers.

3. In the Listen Port field, accept the default.

4. Select the Enable SSL check box if you want to enable SSL.
It is not a requirement to either enable or disable SSL.

5. In the SSL Listen Port field, enter a port that is not used by another domain.
This field is enabled only if you selected the Enable SSL check box.

6. In the Server Groups list, accept the provided default value.

7. Click Next.
The Managed Servers screen appears.

19. Do the following:

1. In the Server Name field, enter the name for the managed server, if required.

2. In the Listen Address field, enter the host, or IP address of the system where the managed server is running.

Note:
Use listener addresses that are equal to a resolvable DNS host or IP address. Do not use localhost or 127.0.0.1. Those addresses interfere with clustered servers.

3. In the Listen Port field, enter the number of the port where the managed server listens for incoming messages.

4. Select the Enable SSL check box if you want to enable SSL.
It is not a requirement to either enable or disable SSL.

5. In the SSL Listen Port field, enter a port that is not used by another domain.
This field is enabled only if you selected the Enable SSL check box.

6. (Optional) Create additional managed servers as required on your Network Integrity deployment by clicking Add, and then configure the settings for the new managed servers.

7. Click Next.
The Clusters screen appears.

20. Do the following:

1. Click Add to start configuring the cluster.

2. In the Cluster Name field, enter the name for the cluster.

3. In the Cluster Address field, provide the cluster address information.
The cluster address contains each managed server along with the managed server's port separated by a comma. Separate the managed server and the port number by a colon.

4. Click Next.
The Assign Servers to Clusters screen appears.

21. Assign the servers to the cluster by moving the managed servers in the left pane to the required cluster in the right pane.

22. Click Next.
The HTTP Proxy Applications screen appears.

23. (Optional) Select Create HTTP Proxy for any proxy servers in the list.

Note:
If you configure an HTTP proxy server to act as a frontend host for the cluster, ensure that you configure the Frontend URL in the Administration Console after the WebLogic domain is created successfully. See "Configuring the Frontend URL in Administration Console" for more information.

24. Click Next.
The Coherence Clusters screen appears, displaying the Coherence cluster that is automatically added to the domain.

This screen appears only if you included Coherence in the WebLogic Server installation.

25. Do the following:

1. In the Name field, accept the default cluster name or type a new name for the Coherence cluster.

2. In the Coherence Listen Port field, enter the port number to use as the Coherence cluster listen port.

26. Click Next.
The Machines screen appears.

Use this screen to change the configuration information for the systems. A computer is the logical expression of the system that hosts one or more WebLogic Server instances. The Administration Server and the Node Manager application use the system definition to start remote servers.

27. (Optional) Add the systems by doing one of the following:

- Select the Machine tab, and do the following:

1. Click Add to create the first system.

2. In the Name field, enter a name for the system.

3. In the Node Manager Listen Address field, enter the host, or IP address of the node manager.

4. In the Node Manager Listen Port, enter the port number for the node manager.

5. Create further systems as required on your Network Integrity deployment.

6. Click Next.
The Assign Servers to Machines screen appears.

- Select the UNIX Machine tab, and do the following:

1. Click Add to create the first UNIX system.

2. If required, select the Enable Post Bind GID check box. The default state is unselected.

3. In the Post Bind GID field, enter a value or select the default.

4. If required, select the Enable Post Bind UID check box. The default state is unselected.

5. In the Post Bind UID field, enter a value or select the default.

6. In the Node Manager Listen Address field, enter the host, or IP address of the node manager.

7. In the Node Manager Listen Port field, enter the port number of the node manager.

8. (Optional) Create further systems or UNIX systems as required on your Network Integrity deployment.

9. Click Next.
The Assign Servers to Machines screen appears.

28. Assign the servers to the machines by moving the servers in the left pane to the required machine in the right pane.

29. Click Next.
The Deployments Targeting screen appears.

30. Under Targets, select the Administration Server; under Deployments, select the applications; and then click the right arrow, which moves the applications to the Administration Server for deployment.

31. Repeat step 30 to target applications for deployment on the cluster.

32. Click Next.
The Services Targeting screen appears.

33. Under Targets, select the Administration Server, under Services, select the services; and then click the right arrow, which moves the services to the Administration Server.

34. Repeat step 33 to target services (libraries) to the cluster.

35. Click Next.
The Configuration Summary screen appears.

36. Review the summary to verify the contents of your domain and click Create to create the domain.
The Configuration Progress screen appears, which displays the progress of the domain creation process.

After the domain is created successfully, the Configuration Success screen appears.

37. Click Finish.
See Oracle Fusion Middleware documentation for more information.

38. To set memory requirements, see "Setting Memory Requirements for Network Integrity".

39. Continue with the procedures in "Starting the WebLogic Server".
You can now log in to the Administration console and start the Administration Server manually.

Note:
Create domains for remote system in the same manner, in the respective systems.

Starting the WebLogic Server

To start the WebLogic server:

1. Open a command window.

2. Go to the Domain_Home/bin and enter the command:

./startWebLogic.sh

The script starts the WebLogic server.

3. Verify that the server started by logging in to the WebLogic server administration console or by checking the log files.
To access the WebLogic server administration console:

1. Go to:

http://Host_Name:Port/console

where Host_Name is the name of the Administration Server name or IP address and Port is the Administration Server port number.

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

3. In the Domain Structure tree, expand Environment, and click Servers.
The Summary of Servers screen appears.

4. View the State of the server and see RUNNING.
If the State is not RUNNING, you may need to wait a short period and refresh the page.

4. Look at the bottom of the Administration Server command window.
The command window should contain the following lines:

Server state changed to RUNNINGServer started in RUNNING mode

Starting the Cluster Member Servers

Note:
If you have configured the node manager, you can start the Network Integrity cluster member servers using the WebLogic Administration Console.

Note:
If the managed servers are started simultaneously, the javax.naming.NameNotFoundException error message is displayed for JMS queues created under JDJMSModule module. To prevent this error message from being displayed, do not start the managed servers simultaneously.

To start the cluster member servers:

1. Log in to the first cluster server system.

2. Go to the DOMAIN_Home/bin directory.

3. Start the cluster server using the following command executed from the system where the managed server is defined:

./startManagedWebLogic.sh cluster_managed_server_name admin_server_URL

4. Start the second server by using the following command executed from the system where the managed server is defined:

./startManagedWebLogic.sh cluster_managed_server_name admin_server_URL

5. To view the log file for each of the managed servers to verify that the server is in RUNNING mode, in a command window, enter:

tail -f Managed_Server_1.log
tail -f Managed_Server_2.log

6. Look at the end of the managed server log files.
The log files should contain the following lines:

Server state changed to RUNNING
Server started in RUNNING mode

If you encounter errors (returned to the terminal, and contained in WebLogic Server domain and server logs) about the Stuck Thread Max Time: value being exceeded during these processes, see "Configuring the WebLogic Server StuckThreadMaxTime Value".

7. Log in to the WebLogic console to check all of the cluster server states.

8. Go to:

http://Host_Name:Port/console

where Host_Name is the name of the Administration Server name or IP address and Port is the Administration Server port number.

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

10. Select Servers and verify that the State of all servers is RUNNING. If you encounter

Note:
To configure the Node Manager, see the Oracle WebLogic documentation on the Oracle Help Center:
http://docs.oracle.com

Configuring the WebLogic Server StuckThreadMaxTime Value

During the installation of Oracle WebLogic Server and Network Integrity in a clustered environment, if the execute thread takes more time than the Stuck Thread Max Time declared in WebLogic, a Stuck Thread Max Time error is displayed.

Stuck Thread Max Time is a property in WebLogic for performance tuning. It is defined as ”the number of seconds that a thread must be continually working before this server considers the thread stuck”. The minimum value is 0 seconds; the default is 600 seconds.

Consider setting Stuck Thread Max Time from its default 600 seconds to a larger value such as 3600 seconds.

Use the WebLogic Console to change this value:

1. Log in to the WebLogic Administration console.

2. In the Home page, select Environment.

3. Select Servers, and then click Admin Server.

4. Select Configuration, and then click Tuning.

5. Increase the value of Stuck Thread Max Time to 3600.

6. Restart your domain. Your changes take effect only after a restart.

Configuring Automatic Service Migration (ASM) on the WebLogic Server

WebLogic server's Automatic Service Migration (ASM) framework monitors the health of JMS services and automatically migrates failing services to healthy and available servers. You configure WebLogic server for automatic service migration for failover and high availability.

For information on configuring Automatic Service Migration (ASM) on the WebLogic server, see Roadmap for Configuring Automatic Migration of JMS-related Services.

Caution:
Not configuring ASM on your WebLogic server results in the Network Integrity installer giving the following warning when launched:
Migration policy for the target is manual. Recommended value is automatic migration. Refer to the JMS recommendations section of the documentation.

If you choose not to configure ASM, ignore the warning and continue with the installation.

To configure auto migration for JMS service in a WebLogic cluster:

1. Configured Managed Servers and the Node Manager.

2. Configure the Migration Leasing Basis as follows:

1. Select the cluster where you are planning Auto JMS Service migration and select the Migration tab.

2. Add all systems to Candidate Machines For Migratable Servers.

3. Select the Migration Basis as Consensus.

4. Save the changes and activate.

3. Configure migratable targets as follows:

1. Select the migratable target and select the Migration tab.

2. Select Auto-Migrate Exactly-Once Services as Service Migration Policy.

3. Add all Constrained Candidate Servers available.

4. Repeat these steps for each migratable target associated with member servers in the cluster.

4. Continue with installing Network Integrity.

5. Once Network Integrity is installed, you can verify whether the environment is ready for JMS Service Auto Migration by following these steps:

1. Select servers and navigate to the Migration tab.

2. All member servers are selected in the JMS Service Candidate Servers list.

3. Repeat these steps for all member servers in the cluster.

Verifying WebLogic Administration Server Migration

To ensure that the WebLogic Administration server has migrated:

1. Log on to the Oracle WebLogic Server Administration Console.
The Administration Console Home screen appears.

2. Under Environment select Migratable Targets.
The Summary of Migratable Targets screen appears.

3. Select the Control tab to display it.

4. If the WebLogic Administration server has migrated, then, in the Migratable Targets table, the name in the Current Hosting Server column equals the corresponding name in the Name column.

5. In case the servers names showing in the two columns are different, do the following:

1. Select the check box corresponding to the name, and click Migrate.
The Migrate Migratable Targets screen appears.

2. From the New hosting server list, select the name of the hosting server and click OK.
The server is migrated.

5 Installing and Configuring Additional Software

This chapter describes the process of installing and configuring additional software to enhance Oracle Communications Network Integrity.

Overview of Additional Installation Tasks

Install and configure the following additional software:

- Oracle Internet Directory

- Oracle BI Publisher

Installing and Configuring Oracle Internet Directory

The WebLogic Server includes an embedded LDAP store that acts as the default security provider data store for the Default Authentication, Authorization, Credential Mapping, and Role Mapping providers. You manage the embedded LDAP store using the WebLogic console. The Oracle Universal Installer uses this embedded LDAP server by default as the security provider. During installation, you can change the setting to use third party security providers with the Oracle WebLogic server.

See the WebLogic Server documentation for information on the embedded LDAP server.

You also have the option to use an external LDAP store, or security provider, if your requirements are greater and you need more security options than are provided by the embedded LDAP server.

Oracle recommends Oracle Internet Directory as the LDAP store external to the WebLogic server.

You require the following information to install the Oracle Internet Directory:

- A static IP address
You require a static IP address to install the Oracle Identity Management suite.

- Oracle Database

- WebLogic Server

- Application Development Runtime

- Identity Management

- Fusion Middleware

For information on installing Oracle Internet Directory, see For information on installing and configuring Oracle Internet Directory, see Oracle Fusion Middleware Installation Guide for Oracle Identity Management.

Configuring the Authentication Provider

To enable the WebLogic Server to work with an external LDAP store, or Oracle Internet Directory:

1. Log in to the Administration console.

2. Under Your Application's Security Settings, click Security Realms.
The Summary of Security Realms screen appears.

3. Select the realm YourRealmName, for which you must set the Oracle Internet Directory as the external LDAP store.
The Settings For YourRealmName screen appears.

4. Click the Providers tab, and in the Providers tab, click the Authentication tab.

5. Click New.
The Create a New Authentication Provider screen appears.

6. In the Name field, enter the name of the authenticator, AuthenticatorName.

7. From the Type list, select OracleInternetDirectoryAuthenticator.

8. Click OK.
The Settings For YourRealmName screen appears, showing the newly created Authentication Provider, AuthenticatorName, in the Authentication tab.

9. Click the AuthenticatorName.
The Settings for AuthenticatorName screen appears.

10. In the Control Flag list, select SUFFICIENT.

11. Click Save.

12. Click the Provider Specific tab.

13. Under the Connection section, in the following fields, enter the relevant values:

- Host

- Port

- Principal

- Credentials

- Confirm Credentials

14. Under the Users section, in the following fields, enter the relevant values:

- User Base DN
Ensure that you provide the following value:

cn=Users,dc=idc,dc=oracle,dc=com

- All User Filter

- User From Name Filter

- User Search Scope

- User Name Attribute

- User Object Class

15. Under the Groups section, in the following fields, enter the relevant values:

- Group Base DN
Ensure that you provide the following value:

cn=Groups,dc=idc,dc=oracle,dc=com

- All Groups Filter

- Group From Name Filter

- Group Search Scope

- Group Membership Searching

- Max Group Membership Search Level

16. Click Save.

17. Restart the WebLogic server.

18. Log in to the Administration console.

19. Navigate to the Settings For YourRealmName screen, and click Reorder.
The Reorder Authentication Providers screen appears.

20. Use the Up and Down arrows to reorder the listed Authentication Providers, and click OK.

Configuring Custom Authentication Providers

You can configure custom authentication providers for your external security provider. In which case, you are required to manually create users and groups before starting Network Integrity installation.

Create the following groups in the new authentication provider store:

- JDGroup

- NetworkIntegrityRole (this is a member of the JDGroup)

Create a user named NIUSER in the new authentication provider store as a member of NetworkIntegrityRole and JDGroup. Ensure that you create the groups and users in the default security realm.

Installing and Configuring BI Publisher

Installing publishing tools is optional. The requirement is based entirely on your individual requirements.

You use Oracle Business Intelligence Publisher (BI Publisher) to host and publish Network Integrity scan-related and other reports.

Download BI Publisher 11g from the Oracle Technology Network Web site:

http://www.oracle.com/technology

For information on installing and configuring, see BI Publisher documentation.

6 Installing Network Integrity

This chapter describes how to install Oracle Communications Network Integrity. Before installing Network Integrity, read these chapters:

- Network Integrity Installation Overview

- Network Integrity System Requirements

- Installing and Configuring the Oracle Database

- Installing and Configuring Oracle WebLogic Server

- Installing and Configuring Additional Software

Types of Installation

There are two types of Network Integrity installation:

- Complete installation. See "Installing Network Integrity by Using Interactive Install".

- Installation in silent mode. See "Installing Network Integrity in Silent Mode".

Caution:
If the installation fails for some reason, you must create a new WebLogic domain and a new database user before you begin installation again.
See "Installing and Configuring the Oracle Database" and "Installing and Configuring Oracle WebLogic Server" for more information.

Caution:
The Network Integrity Installer must be launched from the same system as the one hosting the Administration server of your domain.

Installing Network Integrity by Using Interactive Install

To run the Network Integrity installer, the Java Runtime Environment (JRE) must already be installed. See "Required Software" for more information about the required Java version.

To install Network Integrity:

1. Create a directory (dir).

2. Download the software for your operating system from the Oracle software delivery website:
https://edelivery.oracle.com

and save it to dir:

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

4. Run the Oracle Universal Installer using the following command:

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

where jre_Path contains the jre folder inside the Java Development Kit (JDK) installation directory.

The Installer Welcome screen appears.

5. Click Next.

6. One of the following screens is displayed:

- If Network Integrity is the first Oracle product that you are installing on the system, the Specify Inventory directory and credentials screen appears. Enter the full path of the inventory directory, select the Operating System group name, and then click Next.
The Select Installation Type screen appears. Continue with step 7.

Note:
The inventory directory manages all Oracle products installed on your system.

- If you have installed any Oracle products on the system prior to installing Network Integrity, the Select Installation Type screen appears. Continue with step 7.

7. Select the type of Network Integrity installation you require, and click Next.

- If you select Complete, the Specify Home Details screen appears.
Skip the next step.

- If you select Custom, the Available Product Components screen appears.
Continue with the next step.

8. In the Available Product Components screen, select the components you want to install, and click Next.

9. In the Specify Home Details screen, do the following:

1. In the Name field, enter a name to identify your installation as an Oracle Product in OUI.

2. In the Path field, enter the path to the folder where you want to install Network Integrity.

Note:
You can also select the name for the installation from the list of names the Installer provides or browse to the location.

3. Click Next.

The WebLogic Administration Server Connection Information screen appears.

10. Do the following:

1. In the Host Name field, enter the IP address or the host name of the Administration Server.

2. In the Port Number field, enter the Administration Server port number.

3. In the User Name field, enter user name with which you connected to the Administration Server.

Note:
This user should belong to the WebLogic Administrator's group.

4. In the Password field, enter the password for the user name that you provided in the User Name field.

5. Select or unselect the Use SSL check box based on your business need.

6. In the Keystore field, enter the keystore location if the Use SSL check box is selected.

7. Click Next.
The WebLogic Server/Cluster Selection screen appears.

11. Select the option for the server, or cluster, where you want to deploy Network Integrity, and click Next.

- If you select Administration server, or a managed server, the  Database Type Selection screen appears.
Skip to step 13.

Note:
If you select a managed server, ensure that the managed server and the node manager are running.

- If you select a cluster server, the Cluster Member Server Selection screen appears.
Continue with the next step.

12. In the Cluster Member Server Selection screen, select a cluster member for Network Integrity adapters installation, and click Next.
The Database Type Selection screen appears.

13. In the Database Type Selection screen, do one of the following.

- Select the Standard Oracle 12c Enterprise Database option.
The Database Connection Information screen appears.

Do the following:

1. In the Host Name field, enter the IP address or the host name of the system where the database server is installed.

2. In the Port Number field, enter the port number with which the installer connects to the database server.

3. In the User Name field, enter the user name for the database server.

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).
The user must have the following privileges: CATALOG, CONNECT, Create User, Create Session, Grant Any Privilege, Grant Any Role, Select Any Table, Select any Dictionary.

See "Creating the Database (MetaData) Schema for Network Integrity" for more information.

4. In the Password field, enter the password for the user name that you provided in the User Name field.

5. In the Service name field, enter the service name that uniquely identifies your database on the system.

6. Click Next.
The Network Integrity Schema User Information screen appears.

- Select the Oracle 12c Real Application Cluster Database option.
The RAC DB Nodes Connection Information screen appears.

Do the following:

1. In the RAC Database Connection String field, enter the connection details to connect to the Oracle RAC database.
For example:

HOST NAME1:PORT1:SERVICE NAME1;HOST NAME2:PORT2:SERVICE NAME2

2. In the User Name field, enter the user name for the Oracle RAC database server.

3. In the Password field, enter the password for the user name that you provided in the User Name field.

4. Click Next.
The Network Integrity Schema User Information screen appears.

14. In the Network Integrity Schema User Information screen, do the following:

Note:
Ensure that the schema owner has an associated MetaData Services (MDS) schema.

Caution:
You must use the same user name and password that you created during the MetaData schema creation. See "Creating the Database (MetaData) Schema for Network Integrity" for more information.

1. In the Schema User Name field, enter the name for the MDS schema user.

2. In the Schema User Password field, enter the password for the MDS schema user to access the schema.

3. Click Next.
The Security Provider Selection screen appears.

15. Select the type of security provider you want to use by performing one of the following steps:

- Select the Default WebLogic Security Provider (Embedded_LDAP) option, and click Next.
The Network Integrity User Information screen appears.

- If you select External Security Provider, the External Security Provider Connection Information screen appears.
Do the following:

1. In the LDAP Server Host Name field, enter the host name for the external LDAP server.

2. In the LDAP Server Port Number field, enter the port number for the external LDAP server.

3. In the LDAP Server User Name field, enter the user name for the external LDAP server.

4. In the LDAP Server Password field, enter the password for the external LDAP server.

5. In the User Base DN field, enter the user base DN.

6. In the Group Base DN field, enter the group base DN.

7. Click Next.
The NI Administrator user creation (Optional) screen appears.

- If you select Other Security Provider, and click Next, the Reporting Tool Connection (Optional) screen appears.
Skip to step 20.

16. In the NI Administrator user creation (Optional) screen, do the following:

1. In the User Name field, enter the user name for the Network Integrity user.
This user accesses and uses Network Integrity.

2. In the Password field, define a password for the Network Integrity user.

Note:
The Network Integrity user password can be a maximum of 12 characters long, and should contain at least one digit, one capital letter, and one non alpha-numeric value; For example, Weblogic@123.
Also, the user name must not be part of the password.

In the Confirm Password field, enter the password again to confirm it.

3. Click Next.
The NI User ni-internal secure credentials screen appears.

17. Do the following:

1. 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.

2. Click Next.
The Disable Unsecured Listen Port screen appears.

18. Select whether or not to disable the unsecured listen port by doing one of the following:

- Select Yes if you are configuring Network Integrity to communicate and listen over SSL-enabled ports.

- Select No if you are not configuring Network Integrity to communicate and listen over SSL-enabled ports.

19. Click Next.
The Reporting Tool Connection (Optional) screen appears.

20. Enter the names of, and links to, the reporting tool(s) you have configured, and click Next.

Note:
This is an optional screen. If you do not have any reporting tools configured, click Next to continue with the installation.

The Launch Cartridge Deployer (Optional) screen appears.

21. Select whether to launch the Cartridge Deployer and click Next.

Note:
This is an optional screen that only appears for systems installed on the Linux or Solaris operating systems. Clicking Next takes you to the next screen if you do not want to make this choice now.
Selecting Yes launches the Cartridge Deployer Tool after the successful installation of Network Integrity.

The Summary screen appears.

22. Review the selections you have made in the preceding screens, and click Install.
The Install screen appears.

23. You can view the installation progress.

Note:
During the installation progress, two popup messages will appear.
The first popup message asks for the confirmation to stop the WebLogic Servers, click OK.

The second popup message gives the order in which the servers should be restarted manually. Start the servers, in order listed in the popup message, and click OK, only after all the servers are started.

On successful installation of Network Integrity, the End of Installation screen appears.

Note:
Record the URLs that are displayed in the End of Installation screen, to access Network Integrity.

24. Follow any on-screen instructions to complete the installation.
You can now access the Network Integrity application.

25. Click Exit to close the Installation Wizard.

26. For a Cluster Server installation, do the following:

1. Edit the startWebLogic.sh file under Domain_Home/bin/ directory.
${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME}

-Dweblogic.wsee.useRequestHost=true

-Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS}

${PROXY_SETTINGS} ${SERVER_CLASS}

${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME}

-Dweblogic.wsee.useRequestHost=true

-Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS}

${PROXY_SETTINGS} ${SERVER_CLASS} >"${WLS_REDIRECT_LOG}" 2>&1

2. Stop the AdminServer and restart, using the following command:
./startWebLogic.sh

3. Stop the managed servers and restart, using the following command:
./startManagedWebLogic.sh cluster_managed_server_name admin_server_URL

For information on verifying the successful installation of Network Integrity, see "Verifying the Network Integrity Installation".

Installing Network Integrity in Silent Mode

Use silent install mode when you are installing Network Integrity using the same configuration repeatedly. Silent install mode does not use the GUI and it runs in the background.

About the Response File

The Network Integrity installer uses a response file, which contains a pre-defined set of values, such as server connection details. The response file comes in a template form, to install Network Integrity in silent mode.

The following two response file templates come as part of the Network Integrity installation package:

- oracle.communications.ni.Complete.rsp
Use this file template if you are doing a complete installation.

- oracle.communications.ni.Custom.rsp
Use this file template if you are doing a custom installation.

The response file templates contain all the fields that the installer requires values for to connect to various servers during the silent, unattended installation.

When you untar the Network Integrity package, the response file templates are saved in the Response folder at the following location:

integrity/Disk1/stage/Response

Populate the response file with the required server and connection values for the installer to use during installation, before you begin the silent installation. The provided response file is a template with pre-defined places where you fill in the required values of the required type. Shown here is sample section of a response file:

#Name       : DATABASE_TYPE
#Datatype   : String
#Description:
#Example: DATABASE_TYPE =
#---------------------------------------------------------------
DATABASE_TYPE="Non Clustered-DB"
#---------------------------------------------------------------
#Name       : MANAGED_SERVER_NAME
#Datatype   : String
#Description:
#Example: MANAGED_SERVER_NAME =
#---------------------------------------------------------------
MANAGED_SERVER_NAME="Managed_Server_1"

In this section of the response file sample, you would provide values for the following:

DATABASE_TYPE=
MANAGED_SERVER_NAME=

Similarly, provide values for all variables described in the response file.

Populating the Response File

You can populate the response file in the following ways:

- Recording the response file contents during a GUI installation
To record the response file contents during a GUI installation:

1. Use the following command to launch the Network Integrity installer and also record all input values you provide during the installation:

./runInstaller -record -destinationFile Path -silent -jreloc jre_Path

where jre_Path contains the jre folder inside the JDK installation directory.

- Manually populating the response file
To populate the response file manually:

1. Go to the following location:
integrity/Disk1/stage/Response

2. Open the appropriate RSP template and make a copy for your current requirement.

3. Enter the required input values in the provided locations.

Starting Silent Mode Installation

Before you begin installing Network Integrity in silent mode, ensure that you have provided all required input values in the response file template.

To install Network Integrity in silent mode:

1. Use the following command, where path is the response file location, to start the installation:

./runInstaller -responseFile Path -silent -jreloc jre_Path

where jre_Path contains the jre folder inside the JDK installation directory.

The installation runs silently in the background.

Note:
The installer shuts down all of the servers, including the Administration Server and the Managed Servers, after a silent installation. Start all of the servers manually after the installation is complete. See "Starting the Cluster Member Servers".

2. Open the following file once the installation is complete, to get the URL to access Network Integrity:
NI_Home/install/readme.txt

For example: /opt/integrity/Oraclecommunications/install/readme.txt

3. Copy the URL and paste it in the browser window's address field and press Enter to access Network Integrity.
You can now access the Network Integrity application.

For information on verifying the successful installation of Network Integrity, see "Verifying the Network Integrity Installation".

7 Network Integrity Post-Installation Tasks

This chapter provides instructions for Oracle Communications Network Integrity post-installation tasks.

Overview of Network Integrity Post-Installation Tasks

Post-installation tasks for Network Integrity include:

- Managing Network Integrity Cartridges

- Configuring Network Integrity for Inventory Management

- Installing Network Integrity Report Templates

- Starting the AgeOut Process

- Enabling HTTP Tunneling

- Setting Up Oracle Internet Directory

About the Trusted Certificate for Network Integrity

Note:
Network Integrity uses a demo CA certificate provided by the Oracle WebLogic Server. As a result, when you connect to the Network Integrity UI for the first time, the browser displays a warning page with a message indicating that the security certificate presented is not issued by a trusted certificate authority.
This is expected behavior. Accept this untrusted certificate to continue to connect to Network Integrity UI.

The demo CA certificate provided by the Oracle WebLogic Server, automatically configures the SSL settings in your browser. Configure the SSL, according to your individual requirements, if you are using some other certificate.

For information about configuring SSL for Network Integrity, see Network Integrity System Administrator's Guide.

Managing Network Integrity Cartridges

Managing Network Integrity cartridges includes deploying and undeploying cartridges, viewing deployed and available cartridges, and migrating older cartridges to the latest version of Network Integrity.

Deploying Network Integrity Cartridges

You can deploy cartridges into Network Integrity in the following ways:

- From Design Studio. You can deploy cartridges interactively from Design Studio to test environments. Design Studio enables you to manage cartridges in the test environment consistently, manage common test environment connection parameters across the design team, and compare cartridge version and build numbers in the development environment with those of the cartridges deployed in the test environment. See the Design Studio Help for more information.

- By using the Design Studio Cartridge Management Tool (CMT). The CMT enables you to automate cartridge deployment. You can use the CMT to deploy cartridges into both test and production environments. You can also use it to deploy cartridges into cluster environments. See the Design Studio Developer's Guide for more information about the CMT.

- By using the Network Integrity Cartridge Deployer Tool (CDT). The Network Integrity CDT is a GUI-based tool that enables you to deploy to Network Integrity run-time environments. The Oracle Universal Installer installs the CDT as part of the Network Integrity installation process. You can use the CDT to deploy cartridges into both test and production environments. You can also use it to deploy cartridges into cluster environments. See "Deploying Cartridges with the Network Integrity Cartridge Deployer Tool" for more information.

- By writing your own custom scripts. See "Managing Cartridges With Custom Scripts" for more information.

Deploying Cartridges with the Network Integrity Cartridge Deployer Tool

The Cartridge Deployer Tool is available as a component of the core Network Integrity application. The Oracle Universal Installer installs the Cartridge Deployer Tool as part of the installation process in the same folder as the Network Integrity application.

The WebLogic Server Administration Console must not be locked for editing for the Cartridge Deployer Tool to successfully manage cartridges. See your WebLogic Server documentation for more information.

Note:
Before deploying or undeploying cartridges, ensure that:

- You are logged out of the WebLogic Server Administration Console.

- No one else is deploying or undeploying cartridges on the same server.

- Network Integrity is not running a scan that uses the cartridge.

To deploy cartridges with the Network Integrity Cartridge Deployer Tool:

1. Go to the NI_Home/CartridgeDeployerClients/CartridgeDeployer folder.

2. Run the Cartridge Deployer Tool executable with the following command:

./runCartridgeDeployer.sh

The Cartridge Deployer Welcome screen appears.

3. Select the Deploy Cartridge option and click Next.
The Select Cartridge Type screen appears.

In this screen, you select the cartridge type that is same as the application for which you are deploying the cartridges.

4. Select Network Integrity from the Cartridge Type list and click Next.

Note:
If you are using a cartridge type other than Network Integrity, then ensure that the cartridge type that you select in this list matches the Cartridge Type attribute in the manifest.xml of the cartridge.

The Cartridge Location screen appears.

5. Click Browse to search for and select the required cartridges for the Cartridge Deployer Tool to deploy.
You can select multiple cartridges from a single directory by holding down the Ctrl key.

Ensure that a cartridge is already deployed, or selected for deployment, if the cartridges you are selecting for deployment are dependent on it.

Note:
The customized file browser shows only predefined cartridge extensions. Network Integrity supports cartridges with IAR and JAR extensions.

6. After selecting the required cartridges, click Next.
The Configure Deployment Queue screen appears.

7. View the details of the selected cartridges, confirm your selection, and click Next.

Note:
To add Deploy property or Model property, under Details for that cartridge, right-click Properties and select the respective options for related menus.

The WebLogic Connection Information screen appears.

8. Do the following:

1. In the Host name or IP address field, enter the host name or IP address of the WebLogic Administration Server.

2. In the Port number field, enter the port number of the WebLogic Administration Server.

3. Select whether or not to enable SSL by selecting or unselecting the Use SSL check box.

Note:
You must enter the Admin Server SSL Port if the Use SSL check box is selected.

4. In the Keystore field, enter the keystore location if the Use SSL check box is selected.

5. In the CMWS User field, enter the user name of the CMWS user.

Note:
Use your WebLogic administrator user name and password here, and in the next step.
The cartridge management web service (CMWS) user is a WebLogic server user belonging to the administrators group.

6. In the Password field, enter the password for the CMWS user.

Note:
Use your WebLogic administrator user name and password here.

7. Click Next.

The Select WebLogic Target screen appears.

9. In the list, select the Managed Server where CMWS is deployed and click Next.
The following message is displayed, if SSL is not configured properly:

SSL Handshaking failed. You can proceed without SSL by unchecking SSL options on the bottom of this screen.

Note:
The SLL handshake fails when the Cartridge Deployer Tool connects to the CMWS using HTTPS.

10. Click OK in the message, and deselect Use SSL (if enabled) while connecting to Cartridge Management WebService at the bottom of the screen.

Note:
For information on installing a cartridge with Use SSL enabled, see Network Integrity System Administrator's Guide.

11. Click Next.
The Review Deployment screen appears.

12. Review and confirm your selections, and click Deploy.
The Cartridge Deployment screen appears.

Note:
The Cartridge Deployer Tool rejects cartridges whose higher versions already exist. You can view rejected cartridges in the Cartridges rejected for this deployment session list.

Logs returned by the adapter are displayed after each cartridge deployment operation irrespective of its success.

Note:
If the system or server goes down during cartridge deployment, the cartridge is recovered after the system is up again, or during the next cartridge deployment session, with the cartridge deployment request showing as ”failed”.

13. Click Exit to close the Cartridge Deployment Tool.

Note:
You must log back into the Network Integrity application (if it is already opened) after cartridge deployment.

Undeploying Cartridges with the Network Integrity Cartridge Deployer Tool

You can use the Cartridge Deployer Tool to undeploy the cartridges.

Note:
When a cartridge is undeployed, all Network Integrity scans that use scan actions associated with the undeployed cartridge are deleted.

To undeploy a cartridge:

1. Go to the NI_Home/CartridgeDeployerClients/CartridgeDeployer folder.

2. Run the Cartridge Deployer Tool executable by running the following command:

./runCartridgeDeployer.sh

The Cartridge Deployer Welcome screen appears.

3. Select Undeploy Cartridge and click Next.
The Select Cartridge Type screen appears.

4. From the Cartridge Type list, select NetworkIntegrity and click Next.
The WebLogic Connection Information screen appears.

5. Do the following:

1. In the Host name or IP address field, enter the host name or IP address of the WebLogic Administration Server.

2. In the Port number field, enter the port number of the WebLogic Administration Server.

3. In the CMWS User field, enter the user name of the CMWS user.

Note:
Use your WebLogic administrator user name and password here, and in the next step.
The CMWS user is a WebLogic server user belonging to the administrators group.

4. In the Password field, enter the password for the CMWS user.

Note:
Use your WebLogic administrator user name and password here.

5. Click Next.

The Select WebLogic Target screen appears.

6. Select the WebLogic targets where the cartridges you want to undeploy are installed, and click Next.

Note:
In some cases, WebLogic targets may be different from where Network Integrity is installed.
The Cartridge Deployer Tool lists all WebLogic targets available in the domain where Network Integrity Cartridge Management Components are installed. Select a target from the list.

The following message appears:

SSL Handshaking failed. You can proceed without SSL by unchecking SSL options on the bottom of this screen.

Note:
The SLL handshake fails when the Cartridge Deployer Tool connects to the CMWS using HTTPS.

7. Click OK in the message, and deselect Use SSL (if enabled) while connecting to Cartridge Management WebService at the bottom of the screen.

Note:
For information on installing a cartridge with Use SSL enabled, see Network Integrity System Administrator's Guide.

8. Click Next.
The Select Cartridges for Undeployment screen appears.

You can view all of the cartridges that you had selected earlier, deployed in Network Integrity.

9. Click on the cartridge name to select it, then right-click on that cartridge name and select Select for Undeployment.

Note:
The cartridge name must be selected before right-clicking.

10. Click Next.

Note:
Network Integrity does not use undeployment properties.

The Review Undeployment screen appears.

11. Review your selection(s) and click Next.
The Cartridge Undeployment screen appears.

You can view the undeployment progress in this screen. Logs returned by the adapter are displayed after each cartridge operation irrespective of its success.

For more information about managing cartridges and deploying cartridges using Design Studio, see the Design Studio Help.

Caution:
If the server or system goes down during cartridge undeployment, the cartridge is recovered after the system is up again, or during the next cartridge undeployment session, with the cartridge deployment request showing as ”deploy”.
Ensure that you deploy the recovered cartridge first and then undeploy it.

Deploying and Undeploying Cartridges on a Remote Server

Note:
Oracle recommends that you deploy cartridges, or any Network Integrity adapters on the same server where Network Integrity is deployed.

To deploy cartridges from a remote managed server:

1. Copy the file NetworkIntegrity.ear from the administration server to the remote managed server before starting the cartridge deployment/undeployment.

Note:
NetworkIntegrity.ear is on the same system where the Administration server is running.

2. In the remote server, deploy, or undeploy, cartridges using steps provided in the sections "Deploying Cartridges with the Network Integrity Cartridge Deployer Tool" and "Undeploying Cartridges with the Network Integrity Cartridge Deployer Tool".

3. Copy the NetworkIntegrity.ear file from remote managed server back to the administration server.

4. Update the NetworkIntegrity.ear file.
The cartridges are deployed on, or undeployed from, the remote managed server.

Deploying Cartridges into Cluster Environments That Use Proxy Server

To deploy cartridges into a cluster environment that uses a proxy server as a frontend host:

1. Shut down all the managed servers except the managed server on which the cartridge_management_ws application is deployed. If you do not know the managed server on which the cartridge_management_ws application is deployed, continue with step 2; otherwise, proceed to step 3.

2. (Optional) Locate the cartridge_management_ws application and the corresponding server on which it is deployed by doing the following:

1. Log in to the WebLogic Server Administration Console.

2. On the Home page, under Domain Structure, click the Deployments link.
The Summary of Deployments page appears.

3. Under the Name column, locate the cartridge_management_ws application; under the Targets column, locate the server on which this application is deployed.

3. Deploy the required cartridges.

4. After you have deployed the cartridges, start the Administration Server and all the other managed servers.

Note:
Repeat this procedure for every cartridge deployment life cycle.

Viewing Cartridges with the Network Integrity Cartridge Deployer Tool

To view deployed cartridges:

1. Go to the NI_Home/CartridgeDeployerClients/CartridgeDeployer folder.

2. Run the Cartridge Deployer Tool executable by running the following command:

./runCartridgeDeployer.sh

The Cartridge Deployer Welcome screen appears.

3. Select the View Cartridges option, and click Next.
The Select Cartridge Type screen appears.

4. Select Network Integrity in the Cartridge Type list, and click Next.
The WebLogic Connection Information screen appears.

5. Do the following:

1. In the Host name or IP address field, enter the host name or IP address of the WebLogic Administration Server.

2. In the Port number field, enter the port number of the WebLogic Administration Server.

3. In the CMWS User field, enter the user name of the CMWS user.

Note:
Use your WebLogic administrator user name and password here, and in the next step.
The CMWS user is a WebLogic server user belonging to the administrators group.

4. In the Password field, enter the password for the CMWS user.

Note:
Use your WebLogic administrator user name and password here.

5. Click Next.

The Select WebLogic Target screen appears.

6. Select the WebLogic targets where the CMWS is installed and click Next.

Note:
In some cases, the WebLogic targets may be different from where Network Integrity is installed.

The following message is displayed:

SSL Handshaking failed. You can proceed without SSL by unchecking SSL options on the bottom of this screen.

Note:
The SLL handshake fails when the Cartridge Deployer Tool connects to the CMWS using HTTPS.

7. Click OK in the message, and deselect the Use SSL (if enabled) while connecting to Cartridge Management WebService check box at the bottom of the screen.

Note:
For information about installing a cartridge with Use SSL enabled, see Network Integrity System Administrator's Guide.

8. Click Next.
The Deployed Cartridges screen appears.

You can view the deployed cartridges.

For more information about managing cartridges, see Modeling Network Integrity, which is part of Design Studio online Help.

For information about deploying cartridges using Design Studio, see the Design Studio online Help.

Managing Cartridges With Custom Scripts

Scripted cartridge management allows you to develop custom scripts that deploy, undeploy, list deployed cartridges, and list available cartridges. Scripts can be run manually, or from a command prompt, and can be used to execute cartridge operations to secure and non-secure network systems.

To manage cartridges using Java, you must develop a custom Java application. Or, to manage cartridges using ANT tasks, you must develop a custom XML script.

Note:
You can automate cartridge deployment using the Design Studio Cartridge Management Tool (CMT). You can use the CMT to deploy cartridges into both test and production environments. See the Design Studio Developer's Guide for more information about the CMT.

Developing a Custom Java Application

Refer to NI_Home/CartridgeDeployerClients/tools/Sample.java for an example custom Java application, containing example syntax and sample Java classes.

To develop a custom Java application with which to manage cartridges:

1. Open Oracle Communications Design Studio or any Java Integrated Development Environment (IDE) in the Java perspective.

2. Create a Java project and a /lib directory in the project.

3. Import all the JAR files from the NI_Home/CartridgeDeployerClients/lib/ directory to the /lib directory in the project.

4. Download cartridge-management-client-tools.jar from the NI_Home/CartridgeDeployerClients/tools directory to the /lib directory in the project.

5. Inside /lib directory, create a Java file to develop the Java classes that are required to implement cartridge management operations by doing all of the following:

1. Import the following files:

- oracle.communications.platform.cartridgemanagement.client.domain.Cartridge

- oracle.communications.platform.cartridgemanagement.client.domain.CartridgeOperationResponse

- oracle.communications.platform.cartridgemanagement.client.core.CartridgeManager

2. To deploy cartridges, create an oracle.communications.platform.cartridgemanagement.client.domain.Cartridge object with the following class attributes:

- name

- version

- buildId

- type

- deploy properties

3. Call the deployCartridge() operation on the cartridge manager object with the following arguments:

- webServiceUrl

- keystore_location

- cmwsUserName

- password

- cartridge_object

- pollwait

- pollcount

4. To undeploy cartridges, create an oracle.communications.platform.cartridgemanagement.client.domain.Cartridge object with the following class attributes:

- name

- version

- type

- undeploy properties

5. Call the unDeployCartridge() operation on the cartridge manager object with the following arguments:

- webServiceUrl

- keystore_location

- cmwsUserName

- password

- cartridge_object

- pollwait

- pollcount

6. To list cartridges of a specific type, call the getInstalledCartridges() operation on the cartridge manager object with the following arguments:

- webServiceUrl

- keystore_location

- cmwsUserName

- password

- cartridgeType

7. To list existing cartridges of a specific type, create an oracle.communications.platform.cartridgemanagement.client.domain.Cartridge object with the following class attributes:

- name

- version

- type

8. Call the cartridgeExist() operation on the cartridge manager object with the following arguments:

- webServiceUrl

- keystore_location

- cmwsUserName

- password

- cartridge_object

- comparisonOperator

9. To get the environment, call the getEnvironmentVersion() operation on the cartridge manager object with the following arguments:

- webServiceUrl

- keystore_location

- cmwsUserName

- password

- cartridgeType

Developing Custom ANT Tasks

Refer to NI_Home/CartridgeDeployerClients/tools/sample-build.xml for an example custom ANT script, containing example syntax and sample operations. Refer to NI_Home/CartridgeDeployerClients/tools/sample-build.properties for an example custom Java application, containing example syntax and sample operations.

To develop custom ANT tasks with which to manage cartridges:

1. Open Design Studio or any Java Integrated Development Environment (IDE) in the XML perspective.

2. Create a Java project and a /lib directory in the project.

3. Import all the JAR files from the NI_Home/CartridgeDeployerClients/lib/ directory to the /lib directory in the project.

4. Download cartridge-management-client-tools.jar from the NI_Home/CartridgeDeployerClients/tools directory to the /lib directory in the project.

5. Inside the lib/ directory, create an XML file with the following cartridge management operations:

<taskdef name="deploy" classname="oracle.communications.sce.cartridgemanagement.ws.tools.DeployCartridge" classpathref="class.path"/>

<taskdef name="undeploy" classname="oracle.communications.sce.cartridgemanagement.ws.tools.UndeployCartridge" classpathref="class.path"/>

<taskdef name="list" classname="oracle.communications.sce.cartridgemanagement.ws.tools.ListCartridge" classpathref="class.path"/>

<taskdef name="exist" classname="oracle.communications.sce.cartridgemanagement.ws.tools.CartridgeExist" classpathref="class.path"/>

<taskdef name="environment" classname="oracle.communications.sce.cartridgemanagement.ws.tools.GetEnvironment Version" classpathref="class.path"/>

6. Add the valid attributes for each ANT task:

- For the deploy task:

<target name="deploy">
<echo message="Deploying cartridge..."/>
<deploy host="${host}" port="${port}" username="${username}" password="${password}" adminServerKeyStore="${adminServerKeyStore}" sslKeyStore="${sslKeyStore}" fileLocation="${fileLocation}" cartridgeType="${cartridgeType}" target="${target}" property="deployresponse"/>
<echo message="Message from cartridge deploy task : ${deployresponse}"/>
</target>

- For the list task:

<target name="list">
<echo message="Listing cartridge..."/>
<list host="${host}" port="${port}" username="${username}" password="${password}" adminServerKeyStore="${adminServerKeyStore}" sslKeyStore="${sslKeyStore}" target="${target}" cartridgeType="${cartridgeType}" property="listval"/>
<echo message="Message from cartridge list task : ${listval}"/>
</target>

- For the undeploy task:

<target name="undeploy">
<echo message="Undeploying cartridge ${cartridgeName}
${cartridgeVersion}..."/>
<undeploy host="${host}" port="${port}" username="${username}" password="${password}" adminServerKeyStore="${adminServerKeyStore}" sslKeyStore="${sslKeyStore}" target="${target}" cartridgeName="${cartridgeName}" cartridgeVersion="${cartridgeVersion}" cartridgeType="${cartridgeType}" property="undeployresponse"/>
<echo message="Message from cartridge undeploy task : ${undeployresponse}"/>
</target>

- For the exist task:

<target name="exist">
<echo message="Checking existance of cartridge ${cartridgeName} ${cartridgeVersion}..."/>
<exist host="${host}" port="${port}" username="${username}" password="${password}" adminServerKeyStore="${adminServerKeyStore}" sslKeyStore="${sslKeyStore}" target="${target}" cartridgeName="${cartridgeName}" cartridgeVersion="${cartridgeVersion}" cartridgeType="${cartridgeType}" property="existval"/>
<echo message="Message from cartridge exist task : ${existval}"/>
</target>

- For the environment task:

<target name="env">
<echo message="Fetching environment version..."/>
<environment host="${host}" port="${port}" username="${username}" password="${password}" adminServerKeyStore="${adminServerKeyStore}" adminServerKeyStore="${adminServerKeyStore}" sslKeyStore="${sslKeyStore}" target="${target}" cartridgeType="${cartridgeType}" property="envval"/>
<echo message="Message from env task : ${envval}"/>
</target>

7. Inside the lib/ directory, create an XML properties file to automate the ANT tasks:

ant -lib ..lib/ -f sample-build.xml deploy
ant -lib ..lib/ -f sample-build.xml list
ant -lib ..lib/ -f sample-build.xml undeploy
ant -lib ..lib/ -f sample-build.xml exist
ant -lib ..lib/ -f sample-build.xml env

Where lib/ refers to the location where the dependent libraries are stored.

Running Cartridge Operations From a Command-Line

To use a command-line interface to run cartridge operations:

1. Open a system console command-line or connect to the Network Integrity server using a remote client.

2. Set the Java path, as it is explained in your Java documentation.

3. Enter commands at the command-line.

From the command-line interface, you can:

- Deploy one or more cartridges.

- Undeploy one or more cartridges.

- List all deployed cartridges.

- List all available, undeployed cartridges.

- Show the help message.

Table 7-1 lists all the arguments used at the command-line for managing cartridge operations.

Table 7-1 Valid Arguments for Command-Line Cartridge Management

Valid Argument

Description

-host

The admin host name where the cartridge manager web service (CMWS) is deployed.

-port

A valid port number to the admin server.

-user

A CMWS user.

-password

The CMWS password for the specified user. If -password is omitted from the command, you are prompted to enter the password at the command prompt.

-keystore

A valid keystore location for SSL connection.

-adminkeystore

A valid keystore location for the admin server if the SSL connection is used.

-type

The cartridge type. When deploying multiple cartridges, -type must be set to NetworkIntegrity.

-operation

The cartridge operation to be performed. Possible values are: deploy, undeploy, list, and exist.

-location

A path to a single cartridge, or a comma separated list of paths to multiple cartridges.

-target

The target server, where CMWS is deployed.

-name

A single cartridge name, or a comma-delimited list of cartridge names for multiple cartridges. Only the undeploy operation can accept multiple names.

-version

A single five-digit cartridge version, or a comma-delimited list of cartridge versions for multiple cartridges. Only the undeploy operation can accept multiple versions.

-help

Display the help message.

Table 7-2 lists the commands for managing cartridge operations, with their mandatory and valid arguments.

Table 7-2 Valid Arguments for Each Cartridge Command

Command

Description

deploy

Mandatory Arguments: -host, -port, -username, -password, -target, -keystore (if command is run on an SSL-enabled network system)

Valid Arguments: -type, -location, -target

undeploy

Mandatory Arguments: -host, -port, -username, -password, -target, -keystore (if command is being run on an SSL-enabled network system)

Valid Arguments: -type, -target, -name, -version

list

Mandatory Arguments: -host, -port, -username, -password, -target, -keystore (if command is being run on an SSL-enabled network system)

Valid Arguments: -type, -target

exist

Mandatory Arguments: -host, -port, -username, -password, -target, -keystore (if command is being run on an SSL-enabled network system)

Valid Arguments: -type, -name, -version, -target

To display instruction messages, enter a command similar to the example below:

java -jar cartridge-management-client-tools.jar -help

To deploy a cartridge, enter a command similar to the example below:

java -Djava.util.logging.config.file=logger.conf -jar cartridge-management-client-tools.jar -operation deploy -host admin_host -port admin_port -user cmws_user -password cmws_password -target target_name_where_cmws_deployed -location cartridge_path -type cartridge_type -property model.modelname=modelvalue,deploy.deployname1=deployvalue1,deploy.deployname2=deployvalue2

To list deployed cartridges, enter a command similar to the example below:

java -Djava.util.logging.config.file=logger.conf -jar cartridge-management-client-tools.jar -operation list -host admin_host -port admin_port -user cmws_user -password cmws_password -type cartridge_type -target target_name_where_cmws_deployed

To undeploy a cartridge, enter a command similar to the example below:

java -Djava.util.logging.config.file=logger.conf -jar cartridge-management-client-tools.jar -operation undeploy -host admin_host -port admin_port -user cmws_user -password cmws_password -type cartridge_type -target target_name_where_cmws_deployed -name cartridge_name -version cartridge_version

To check if a cartridge exists, enter a command similar to the example below:

java -Djava.util.logging.config.file=logger.conf -jar cartridge-management-client-tools.jar -operation exist -host admin_host -port admin_port -user cmws_user -password cmws_password -type cartridge_type -target target_name_where_cmws_deployed -name name_of_cartridge -version version_of_cartridge

To fetch environment properties, enter a command similar to the example below:

java -Djava.util.logging.config.file=logger.conf -jar cartridge-management-client-tools.jar -operation env -host admin_host -port admin_port -user cmws_user -password cmws_password -type cartridge_type -target target_name_where_cmws_deployed

Configuring Network Integrity for Inventory Management

After installing Network Integrity, you can use it to discover devices on your network. To compare the discovered device data with an existing inventory model, and to detect and resolve discrepancies between the two, you must configure or extend Network Integrity to communicate with your inventory management system. You may also need to configure or extend your inventory system.

You can license and download components to simplify the task of configuring and extending Network Integrity to communicate with Unified Inventory Management (UIM).

For information on Network Integrity cartridges or UIM technology packs that enable communication between Network Integrity and UIM, see the UIM Integration Cartridge documentation.

Installing Network Integrity Report Templates

Network Integrity comes with pre-defined report templates that you can use. A folder, integrityreports, is created during installation, in the folder where Network Integrity is deployed. The integrityreports folder contains the following report templates:

- Scan_History_Report

- Discrepancy_Corrective_Action_Report

- Device_Discrepancy_Detection_Summary_Report

- Device_Discrepancy_Detection_Detailed_Report

- Device_Discovery_Summary_Report

Note:
The integrityreports folder should be on the system where BI Publisher is installed. If BI Publisher is installed on a system separate from the system where Network Integrity is deployed, move the integrityreports folder to the location where BI Publisher is installed and provide the correct connection information as shown in "Installing Network Integrity Report Templates".

To deploy the report templates to BI Publisher:

1. Open the BI Publisher application and click the Admin tab.

2. In the Admin tab, under Data Sources, click JDBC Connection.
The Data Sources screen appears with the JDBC tab open.

3. In the Add Data Source table, under the heading Data Source Name, click demo.
The Update Data Source: demo screen appears.

4. Provide the following details:

- The Connection String
The format is:

jdbc:oracle:thin:@Host name: Port:SID

For example, a sample connection string may look like:

jdbc:oracle:thin:@myhost:1521:orcl

- User name

- Password

- Database Driver Class
The default is:

oracle.jdbc.driver.OracleDriver

5. Click Test Connection.

6. When a message confirming that the connection is successfully established appears, click Apply to save the connection details.

7. Go to the BI Publisher Home page.

8. Click the My Folders link.
The My Folders pane appears.

9. Click the Create a new folder link.
Enter the folder name, and click Create.

10. Click the folder name of the folder you created.
The folder screen appears.

11. Click the Upload a report link.

12. Click Browse adjacent to the Report to Upload field, and browse for a file with the XDO extension.

13. Click Upload.
The report templates are saved in the folder you created.

14. In the Reports tab, click Edit, and click the Layouts link.
The Create Layouts panel appears.

15. In the Manage Template Files section, click Browse adjacent to the Upload Template field.

16. Browse for and select all available RTF files and click Upload.

17. Click Save.

18. Repeat steps 12 - 17 to upload all unzipped folders in the same manner.

19. Click View to view reports.

Starting the AgeOut Process

The AgeOut process in Network Integrity cleans up the database by deleting old scan results. Although running the AgeOut process is an optional component, doing so improves Network Integrity performance and is recommended.

See Network Integrity System Administrator's Guide for information about starting the AgeOut Process.

Enabling HTTP Tunneling

In order for Network Integrity to transfer large amounts of data between the server and client, the WebLogic server must be configured for http tunneling. This will help the server to make a dedicated connection with the client, for the given timeout and within this time, the data can be transferred without giving any errors.

Note:
HTTP tunneling should be enabled on the server where Network Integrity is deployed. If Network Integrity is deployed in a single managed server installation, then the parameters need to be changed on the WebLogic administration server. If Network Integrity is deployed in a clustered server installation, then the parameters need to be changed on the WebLogic administration server and all the managed servers.

To enable http tunneling, perform the following:

1. Log in to the Administration console using the administrator user name and password.

2. Click Lock and edit.

3. Click Servers in the left panel.

4. Select the server name and click Protocols.

5. In the Enable tunneling field, select the check box.

6. In the Tunneling client ping field, enter 80 seconds.

7. In the Tunneling client timeout field, enter 900 seconds.

8. Click Activate Changes.

9. Repeat the same procedure for any managed servers.

Setting Up Oracle Internet Directory

If you choose to use Oracle Internet Directory as your lightweight directory access protocol (LDAP) provider, you must set it up to run with Network Integrity.

1. Navigate to Domain_Home/config/fmwconfig.

2. Edit the file jps-config.xml.

3. Find the following serviceInstance parameter:

<serviceInstance name="idstore.ldap" provider="idstore.ldap.provider">

4. Add the following bold entries to the file:

<serviceInstance name="idstore.ldap" provider="idstore.ldap.provider">
<description>LDAP Identity Store Service Instance</description>
<property name="idstore.config.provider" value="oracle.security.jps.wls.internal.idstore.WlsLdapIdStoreConfigProvider"/>
<property name="CONNECTION_POOL_CLASS" value="oracle.security.idm.providers.stdldap.JNDIPool"/>
<property name="virtualize" value="true"/>
<serviceInstanceRef ref="NetworkIntegrityAuthenticationProvider"/>
</serviceInstance>
<serviceInstance name="NetworkIntegrityAuthenticationProvider" provider="idstore.ldap.provider">
<property name="idstore.type" value="ACTIVE_DIRECTORY" />
</serviceInstance>

5. Save and close the file.

8 Verifying the Network Integrity Installation

This chapter describes how to verify that Oracle Communications Network Integrity is installed correctly.

Checking the State of all Installed Components

You can verify that Network Integrity is installed by checking the state of all installed components.

To check the state of all installed components:

1. Log in to the WebLogic Administration Server.

2. Ensure that all of the managed servers are running.

3. In the left panel, in the Domain Structure section, click Deployments.
The Summary of Deployments page appears.

4. If Network Integrity is installed successfully, the following deployments appear in the Active state:

- JobDispatcher

- NetworkIntegrity

- NICMWSAdapter

- snmpAdapter

- FileTransferJCA

- cartridge_management_ws

Logging In to Network Integrity

You can verify that Network Integrity is installed by logging in to Network Integrity.

To log in to Network Integrity:

1. Open a browser window. Refer to Table 2-2, "Required Server-Side Software" for supported web browsers.

2. Enter the URL as provided by the Installer after the installation.

3. Click Go, or press the Enter key.
The Network Integrity login page appears.

4. Do the following:

1. In the User Name field, enter the Network Integrity user name.

2. In the Password field, enter the password for the Network Integrity user name.

The Network Integrity home page appears, verifying that Network Integrity is installed successfully.

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.

About Upgrading Network Integrity

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.

Supported Upgrade Paths

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.

Planning Your Upgrade

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.

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:

- 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.

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.2.4.x to 7.3.2

Upgrading to this version of Network Integrity requires the following system changes:

- Fusion Middleware Changes

- Java Development Kit changes

- WebLogic Server Changes

- Database Software Changes

- Database Schema Changes

- Application Component Changes

- Design Studio Changes

- Cartridge Changes

Fusion Middleware 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.

Java Development Kit changes

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.

WebLogic Server Changes

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.

Database Software Changes

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.

Database Schema Changes

The new version of Network Integrity requires an updated database schema.

Application Component Changes

The Oracle Universal 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 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.

Cartridge Changes

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.

Upgrading 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:

- Pre-Upgrade Tasks (7.2.4.x to 7.3.2)

- Upgrading Network Integrity (7.2.4.x to 7.3.2)

- Post-Upgrade Tasks (7.2.4.x to 7.3.2)

- From release 7.3.0 to release 7.3.2 by doing the following tasks:

- Upgrading Network Integrity (7.3.0 to 7.3.2)

- Post-Upgrade Tasks (7.3.0 to 7.3.2)

Pre-Upgrade Tasks (7.2.4.x to 7.3.2)

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:

1. Back up the Network Integrity and MDS databases. See Network Integrity System Administrator's Guide for more information.

2. 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.

3. 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.

4. Create the data source for the OPSS user by doing the following:

1. Log in to the WebLogic server Administration Console using the Administrator credentials.

2. Click Lock & Edit.

3. In the Domain Structure tree, expand Services, and then click Data Sources.
The Summary of Data Sources page appears.

4. Click New and select Generic Data Source.
The JDBC Data Sources Properties page appears.

5. In the Name and JNDI Name fields, enter the required information; from the Database Type list, select an option, and then click Next.

6. 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.

7. Click Next.
The Transaction Options Page appears.

8. Deselect the Supports Global Transactions check box and click Next.
The Connection Properties page appears.

9. 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.

10. Review the connection parameters and click Test Configuration.

11. If the test is successful, click Next.
The Select Targets page appears.

12. 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.

13. Verify that the newly created data source is listed under the Data Sources table.

14. In the Change Center of the Administration Console, click Activate Changes, which activates these changes.
See the Oracle WebLogic Server documentation for more information.

5. To reassociate the OPSS security store to a DB-based security store, do the following:

1. 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.

2. Click Change Store Type.
The Configure Security Stores page appears.

3. From the Store Type list, select Oracle Database.

4. 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.

5. Enter the required information about the OPSS data source in the fields under the Data Source Properties and Root Node Details areas.

6. 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.

6. 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.

7. 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.

8. 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.

9. (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.

10. Stop the Network Integrity Domain Servers.

11. 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.

12. 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"/>

13. Upgrade the MDS and OPSS schemas by doing the following:

1. 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.

2. Launch the Fusion Middleware Upgrade Assistant.
The Welcome screen appears.

3. Click Next.

4. Select Schemas and click Next.
The Available Components screen appears.

5. Select the Oracle Metadata Services and Oracle Platform Security Services check boxes, and click Next.
The Domain Directory screen appears.

6. In the Directory field, enter the WebLogic domain directory for the domain to be upgraded and click Next.
The Prerequisites screen appears.

7. 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.

8. From the Database Type list, select the database type.

9. 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.

10. In the DBA User Name field, enter the database administrator user name.

11. In the DBA Password field, enter the password.

12. Click Connect.
If the provided details are valid, the Schema User Name and Schema Password fields become enabled.

13. From the Schema User Name list, select the OPSS schema.

14. In the Schema Password field, enter the database password, and click Next.
The MDS Schema screen appears.

15. From the Database Type list, select the database type.

16. 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.

17. In the DBA User Name field, enter the database administrator user name.

18. In the DBA Password field, enter the password.

19. Click Connect.
If the provided details are valid, the Schema User Name and Schema Password fields become enabled.

20. From the Schema User Name list, select the MDS schema.

21. In the Schema Password field, enter the database password, and click Next.
The Examine screen appears.

22. Click Next.
The Upgrade Summary screen appears.

23. 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.

24. After the upgrade completes, click Next.
The Upgrade Success screen appears.

25. Verify that the upgrade was successful and click Close.
See Oracle Fusion Middleware documentation for more information.

14. 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.

15. 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

1. 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.

2. Click Next.
The Domain Mode and JDK screen appears.

The domain mode cannot be changed during reconfiguration. It is inherited from the original domain.

3. Select the JDK option and browse to the folder (JAVA_HOME) where JDK is installed and click Next.
The Database Configuration Type screen appears.

4. 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.

5. Click Next.

6. Navigate through the different screens by clicking Next on each screen and specify your settings as necessary.

7. On the Node Manager screen, under the Node Manager Type area, select Manual Node Manager Setup and click Next.
The Advanced Configuration screen appears.

8. 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.

9. Navigate through the different screens by clicking Next on each screen and specify your settings as necessary.

10. 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.

11. Click Next.
The Services Targeting screen appears.

12. 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.

13. Click Next until the Configuration Summary screen appears.

14. 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.

15. Click Finish.
See Oracle Fusion Middleware documentation for more information.

16. Upgrade the WebLogic domain configurations by doing the following:

1. 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.

2. Launch the Fusion Middleware Upgrade Assistant.
The Welcome screen appears.

3. Click Next.

4. Select WebLogic Component Configurations, in the Domain Directory field, enter the WebLogic domain directory you want to upgrade, and then click Next.

5. Navigate through the different screens by clicking Next on each screen and specify your settings as necessary.

6. On the Upgrade Success screen, verify that the upgrade was successful and click Close.
See Oracle Fusion Middleware documentation for more information.

17. Remove the ess-mbeans.xml file from the Domain_Home/config/fmwconfig/mbeans folder.

18. 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.

19. 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.

20. Start the Network Integrity Administration Server. If this is a clustered server environment, start the cluster member servers.

21. Ensure that all the deployed applications are active, otherwise you will need to manually update each application and then make each application active.

22. 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.2.4.x to 7.3.2)

To upgrade Network Integrity:

1. Create a directory (dir).

2. Download the software for your operating system from the Oracle software delivery website:
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. (IBM AIX only) Stop and restart the WebLogic Server domain for Network Integrity.

5. 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.

6. Click Next.
The Select Installation Type screen appears.

7. Select Complete and click Next.
The Available Product Components screen appears.

8. Select Network Integrity and click Next.
The Specify Home Details screen appears.

9. 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.

10. (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.

11. Review the list of components to be upgraded and click Next.
The WebLogic Administration Server Connection Information screen appears displaying the current connection information.

12. 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.

13. 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.

14. 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:

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 Clusters (RAC) database, select Oracle 12c 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.

15. 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 NI User ni-internal secure credentials screen appears.

16. Do the following:

1. In the User Password field, define a password for the Network Integrity internal user.

2. In the Confirm The User Password field, enter the password again to confirm it.

3. Click Next.
The Summary screen appears.

17. 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.

18. 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.

19. Click Installed Products and verify that the installed version for Network Integrity is correct.

20. 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

21. In the Installer, click Exit.

Post-Upgrade Tasks (7.2.4.x to 7.3.2)

After upgrading Network Integrity, do the following, if necessary:

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

2. If you configured an Inventory System in the old version of Network Integrity and specified a password, you need to re-enter the password.

1. In the new version of Network Integrity, click Manage Import System.

2. Click Edit.

3. Enter the password and click Save and Close.

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

4. Re-deploy your cartridges. See "Deploying Network Integrity Cartridges" for more information.

5. In Network Integrity, edit all scans that use the Import Optical from UIM and Import Logical Optical from UIM scan action:

1. On the Manage Scans page, search for scans that use the Import Optical from UIM scan action.

2. In the search result, select each scan and do the following:

- Click the Edit icon.

- Click Save and Close.

3. On the Manage Scans page, search for scans that use the Import Logical Optical from UIM scan action.

4. 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.

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 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):

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

1. Select the Design Studio perspective.

2. Select the Studio Projects 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 Studio Projects view.

3. Right-click anywhere in the Studio Projects view and select Import.
The Import Project dialog box appears.

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

5. Locate the cartridge project and import it.

6. Double-click the cartridge project folder.
The cartridge properties appear.

7. 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.

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

9. From the Project menu, enable Build Automatically.

10. From the Project menu, select Clean.
The cartridge project is automatically built. The binary file is produced and written to the cartridgeBin directory.

Upgrading Network Integrity (7.3.0 to 7.3.2)

To upgrade Network Integrity:

1. Create a 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. (IBM AIX only) Stop and restart the WebLogic Server domain for Network Integrity.

5. 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.

6. Click Next.
The Select Installation Type screen appears.

7. Select Complete and click Next.
The Available Product Components screen appears.

8. Select Network Integrity and click Next.
The Specify Home Details screen appears.

9. 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.

10. (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.

11. Review the list of components to be upgraded and click Next.
The WebLogic Administration Server Connection Information screen appears displaying the current connection information.

12. 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.

13. 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.

14. 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:

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 Clusters (RAC) database, select Oracle 12c 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.

15. 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 NI User ni-internal secure credentials screen appears.

16. Do the following:

1. In the User Password field, define a password for the Network Integrity internal user.

2. In the Confirm The User Password field, enter the password again to confirm it.

3. Click Next.
The Summary screen appears.

17. 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.

18. 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.

19. Click Installed Products and verify that the installed version for Network Integrity is correct.

20. 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

21. In the Installer, click Exit.

Post-Upgrade Tasks (7.3.0 to 7.3.2)

After upgrading Network Integrity, do the following, if necessary:

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

2. If you configured an Inventory System in the old version of Network Integrity and specified a password, you need to re-enter the password.

1. In the new version of Network Integrity, click Manage Import System.

2. Click Edit.

3. Enter the password and click Save and Close.

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

4. Re-deploy your cartridges. See "Deploying Network Integrity Cartridges" for more information.

5. In Network Integrity, edit all scans that use the Import Optical from UIM and Import Logical Optical from UIM scan action:

1. On the Manage Scans page, search for scans that use the Import Optical from UIM scan action.

2. In the search result, select each scan and do the following:

- Click the Edit icon.

- Click Save and Close.

3. On the Manage Scans page, search for scans that use the Import Logical Optical from UIM scan action.

4. 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.

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 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):

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

1. Select the Design Studio perspective.

2. Select the Studio Projects 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 Studio Projects view.

3. Right-click anywhere in the Studio Projects view and select Import.
The Import Project dialog box appears.

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

5. Locate the cartridge project and import it.

6. Double-click the cartridge project folder.
The cartridge properties appear.

7. 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.

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

9. From the Project menu, enable Build Automatically.

10. 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.

10 Setting Up Network Integrity for Single Sign-On Authentication

This chapter provides instructions for setting up Oracle Communications Network Integrity for single sign-on (SSO) authentication.

Network Integrity implements the single sign-on (SSO) authentication solution using Oracle Access Manager, which enables you to seamlessly access multiple applications without being prompted to authenticate for each application separately. The main advantage of SSO is that you are authenticated only once, which is when you log in to the first application; you are not required to authenticate again when you subsequently access different applications with the same (or lower) authentication level (as the first application) within the same web browser session.

Network Integrity also supports the single logout (SLO) feature. If you access multiple applications using SSO within the same web browser session, and then if you log out of any one of the applications, you are logged out of all the applications.

This solution supports SSO authentication between Network Integrity and Oracle Communications Unified Inventory Management (UIM) applications.

For more information, see Oracle Fusion Middleware Administrator's Guide for Oracle Access Management.

Setting up Network Integrity for SSO authentication includes the following tasks:

- Installing Required Software

- Configuring Network Integrity to Enable SSO Authentication

Installing Required Software

Install and configure the following software that Network Integrity requires for implementing SSO authentication:

- External Lightweight Directory Access Protocol (LDAP) Server. Oracle recommends Oracle Internet Directory (OID) as the LDAP store external to the WebLogic server.

- Oracle Access Manager (OAM), included with Oracle Identity and Access Management 11g Release 2 (11.1.2.3.0)

- Oracle WebLogic Server 11g (10.3.6)

- Oracle HTTP Server (OHS) 12c (12.1.3)

- Oracle HTTP Server 11g WebGate for OAM

- Oracle WebLogic Server 12c (12.1.3)

To install the required software, do the following:

1. Install WebLogic Server 11g (10.3.6) and create the Oracle Middleware Home directory (MW_Home). This is the directory in which the Oracle Fusion Middleware products are installed.
For more information, see Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server 11g.

2. Install Oracle Access Manager (OAM) in the same Oracle Middleware Home directory that you created when you installed Oracle WebLogic Server 11g.
For more information, see Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management.

3. Install and configure Oracle HTTP Server, which is a Web server that acts as the front end to the Oracle WebLogic Server.
For more information, Oracle Fusion Middleware Installing and Configuring Oracle HTTP Server.

4. Install and configure Oracle HTTP Server WebGate for OAM.
A WebGate is a web-server plug-in for Oracle Access Manager (OAM) that intercepts HTTP requests and forwards them to the Access Server for authentication and authorization. For more information, see Oracle Fusion Middleware Installing WebGates for Oracle Access Manager.

5. Install an external LDAP server. For example, Oracle Internet Directory (OID). Oracle recommends Oracle Internet Directory as the LDAP store external to the WebLogic Server. See the following for more information.

- Installing and Configuring Oracle Internet Directory

- Setting Up Oracle Internet Directory

For information on installing and configuring Oracle Internet Directory, see Oracle Fusion Middleware Installation Guide for Oracle Identity Management.

6. Configure the external LDAP as the user identity store in OAM.
For more information, see Oracle Fusion Middleware Administrator's Guide for Oracle Access Management.

7. Register the Oracle HTTP Server WebGate instance with OAM by using the Oracle Access Manager Administration Console.
For more information, see the chapter on ”Registering Partners (Agents and Applications) by Using the Console” in Oracle Fusion Middleware Administrator's Guide for Oracle Access Manager with Oracle Security Token Service.

8. Install Oracle WebLogic Server 12c. See "Installing and Configuring Oracle WebLogic Server" for more information.

9. Continue with the steps in "Configuring Network Integrity to Enable SSO Authentication".

Configuring Network Integrity to Enable SSO Authentication

Configuring Network Integrity to enable SSO authentication involves the following tasks:

- Installing and Deploying Network Integrity Specifying the External LDAP Provider

- Configuring the Frontend URL in Administration Console

- Creating and Configuring Authentication Providers for OAM SSO

- Configuring web.xml for the OAM Identity Asserter

- Configuring the mod_wl_ohs Plug-In for Oracle HTTP Server

- Protecting Resources For SSO Authentication

- Excluding Resources From SSO Authentication

Installing and Deploying Network Integrity Specifying the External LDAP Provider

To install and deploy Network Integrity specifying the external LDAP security provider:

1. Configure authentication providers for your external security provider. See "Configuring Custom Authentication Providers" for more information.
Oracle recommends Oracle Internet Directory as the LDAP store external to the WebLogic server. See "Installing and Configuring Oracle Internet Directory" for more information.

2. Install and deploy Network Integrity specifying the external LDAP provider.
When installing Network Integrity, in the Security Provider Selection screen, select the External Security Provider option, and then enter the required information in the External Security Provider Connection Information screen. Follow the instructions provided in "Installing Network Integrity by Using Interactive Install".

Configuring the Frontend URL in Administration Console

Set the front-end host and port so that all requests to access the applications (Network Integrity) deployed in the WebLogic administration server go through the Oracle HTTP server:

To configure the Frontend URL:

1. Log in to the Oracle WebLogic Server administration console.

2. In the Domain Structure tree, expand Environment, and do one of the following:

- Select Clusters (if the server instances to which you want to proxy requests from Oracle HTTP Server are in a cluster)

- Select Servers.
The Summary of Servers page appears.

3. Select the server or cluster to which you want to proxy requests from Oracle HTTP Server.

4. Click the Configuration tab.

5. On the General tab, in the Advanced section, select the WebLogic Plug-In Enabled check box.

6. If you selected Servers in step 2, repeat steps 3 through 5 for the other servers to which you want to proxy requests from Oracle HTTP Servers.

7. Click Save.

8. Restart the WebLogic server.

9. Log in to the Oracle WebLogic Server administration console.

10. In the Domain Structure tree, expand Environment, and click Servers.
The Summary of Servers screen appears.

11. Click the server where Network Integrity is deployed.
The settings screen for the server appears.

12. Click the Protocols tab.

13. On the HTTP tab, do the following:

14. In the Frontend Host field, enter the name of the Oracle HTTP Server host machine.
WebLogic Server uses this value instead of the one in the host header. All HTTP URLs are redirected to this HTTP host.

15. In the Frontend HTTP Port field, enter the Oracle HTTP Server port number.
All HTTP URLs are redirected to this HTTP port.

16. In the Frontend HTTPS Port field, enter the Oracle HTTP Server SSL port number.
All HTTPS URLs are redirected to this HTTPS port.

17. Click Save.

18. In the Change Center of the Administration Console, click Activate Changes, which activates these changes.

Creating and Configuring Authentication Providers for OAM SSO

You must create a new OAMIdentityAsserter provider for OAM SSO in WebLogic Server Administration Console.

To create the OAMIdentityAsserter provider:

1. Log in to the WebLogic Server Administration Console.

2. Under Your Application's Security Settings, click Security Realms.
The Summary of Security Realms screen appears.

3. Select the realm YourRealmName, for which you need to configure the OAM identity asserter.
The Settings For YourRealmName screen appears.

4. Click the Providers tab, and then click the Authentication tab.

5. Click New.
The Create a New Authentication Provider screen appears.

6. In the Name field, enter a name for the new provider; for example, OAM ID Asserter.

7. From the Type list, select OAMIdentityAsserter.

8. Click OK.
The Settings For YourRealmName screen appears, showing the newly created authentication name in the Authentication tab.

9. Click the link for AuthenticatorName (For example, OAM ID Asserter).
The Settings for AuthenticatorName screen appears.

10. On the Common tab, from the Control Flag list, select REQUIRED.

11. Under Active Types, use the directional arrow buttons to move OAM_REMOTE_USER from the Available column to the Chosen column.
Ensure that OAMAuthnCookie and OAM_IDENTITY_ASSERTION are present in the Chosen column.

12. Click Save.

13. Click the Providers tab, and then click the Authentication tab.

14. Click the link for DefaultAuthenticator and ensure that the default authenticator's control flag is set to SUFFICIENT.

15. Click the link for OID/OUD Authenticator (for example, OracleInternetDirectoryAuthenticator) and ensure that the OID/OUD authenticator's control flag is set to SUFFICIENT.
See "Configuring the Authentication Provider" for more information.

16. On the Authentication tab, click Reorder.
The Reorder Authentication Providers screen appears

17. Use the up and down arrows to reorder the listed authentication providers as follows:

- OAMIdentityAsserter (REQUIRED)

- OracleInternetDirectoryAuthenticator (SUFFICIENT)

- DefaultAuthenticator (SUFFICIENT)

18. Click OK.

Configuring web.xml for the OAM Identity Asserter

You configure the web.xml file for the OAM Identity Asserter by updating the deployment plan. You use deployment plans to change an application's WebLogic Server configuration for a specific environment without modifying existing deployment descriptors.

To update the web.xml file:

1. For using Oracle Access Manager Identity Asserter, you must specify the authentication method as CLIENT-CERT in the web.xml file for the appropriate realm by editing the deployment plan. The web.xml file is located at NI_Home/app/NetworkIntegrity.ear/NetworkIntegrityApp_NetworkIntegrityUI_webapp1.war/WEB-INF/, where NI_Home is the directory in which the Network Integrity software is installed.

- Depending on your deployment configuration, do one of the following:

- If Network Integrity is installed in a single server environment, navigate to and open the NI_Home/app/plan/Plan.xml file.

- If Network Integrity is installed in a clustered server environment, navigate to and open the NI_Home/app/plan/ClusterPlan.xml file.

- Update the variable-definition and variable-assignment elements; specifically, add CLIENT-CERT as follows:

<variable-definition>
<variable>
<name>ClientCertAuthMethod</name>
<value>CLIENT-CERT</value>
</variable>
<variable>
<name>RealmName</name>
<value>myrealm</value>
</variable>
</variable-definition>
<module-override>
<module-name>NetworkIntegrityApp_NetworkIntegrityUI_webapp1.war</module-name>
<module-type>war</module-type> <module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
<variable-assignment>
<name>ClientCertAuthMethod</name>
<xpath>/web-app/login-config/auth-method</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>RealmName</name>
<xpath>/web-app/login-config/realm-name</xpath>
<operation>add</operation>
</variable-assignment>
</module-descriptor>
</module-override>

- Save and close the Plan.xml/ClusterPlan.xml file.

2. Update the deployment plan for the currently-deployed Network Integrity application:

1. Log in to the WebLogic Server Administration Console.

2. In the Domain Structure tree, expand Environment, and click Deployments.
The Summary of Deployments screen appears.

3. Select the check box beside NetworkIntegrity.

4. Click Update.
The Update Application Assistant page appears.

5. Select Update this application in place with new deployment plan changes and click Next.

6. (Optional) Click Change Path beside the Deployment Plan Path field and browse to the location of the Plan.xml/ClusterPlan.xml file.
The Summary page appears.

7. Click Finish.

8. In the Change Center of the Administration Console, click Activate Changes, which activates these changes.

Configuring the mod_wl_ohs Plug-In for Oracle HTTP Server

You can configure mod_wl_ohs plug-in by specifying directives in the mod_wl_ohs.conf file to enable the Oracle HTTP Server instances to forward requests to the applications deployed on the Oracle WebLogic server or clusters.

For more information, see Oracle Fusion Middleware Using Web Server Plug-Ins with Oracle WebLogic Server.

To configure the mod_wls_ohs plug-in:

1. Open the mod_wl_ohs.conf file from the following location:
Domain_Home/config/fmwconfig/components/OHS/ohs1/

where:

Domain_Home is the directory containing the configuration for the domain into which Oracle HTTP Server is installed.

2. Add directives within the <IfModule weblogic_module> element in the configuration file as follows:

- To forward requests to the Network Integrity application running on a single Oracle WebLogic Server instance, specify /NetworkIntegrity within the <location> element as follows:

<IfModule weblogic_module>
<Location /NetworkIntegrity>
SetHandler weblogic-handler
WebLogicHost host
WebLogicPort port
</Location>
</IfModule>

where:

- host is the name of the WebLogic Administration server machine

- port is the port of the server on which Network Integrity is installed

- To forward requests to the Network Integrity application running on a cluster of Oracle WebLogic Server instances, specify /NetworkIntegrity within a new <location> element as follows:

<IfModule weblogic_module>
<Location /NetworkIntegrity>
SetHandler weblogic-handler
WebLogicCluster host1:port1,host2:port2
</Location>
</IfModule>

where:

- host1 and host 2 are host names of the managed servers

- port1 and port2 are ports of the managed servers

- To forward requests to the Network Integrity Web services running on a single Oracle WebLogic Server instance, specify /NetworkIntegrityApp-NetworkIntegrityControlWebService-context-root within the <location> element as follows:

<IfModule weblogic_module>
<Location /NetworkIntegrityApp-NetworkIntegrityControlWebService-context-root>
SetHandler weblogic-handler
WebLogicHost host
WebLogicPort port
</Location>
</IfModule>

where:

- host is the name of the WebLogic Administration server machine

- port is the port of the server on which Network Integrity is installed

- To forward requests to the Network Integrity Web services running on a cluster of Oracle WebLogic Server instances, specify /NetworkIntegrityApp-NetworkIntegrityControlWebService-context-root within a new <location> element as follows:

<IfModule weblogic_module>
<Location /NetworkIntegrityApp-NetworkIntegrityControlWebService-context-root>
SetHandler weblogic-handler
WebLogicCluster host1:port1,host2:port2
</Location>
</IfModule>

where:

- host1 and host 2 are host names of the managed servers

- port1 and port2 are ports of the managed servers

- To forward requests to the Network Integrity application running on a single Oracle WebLogic Server instance to support integration with UIM, specify /NI_Uim within the <location> element as follows:

<IfModule weblogic_module>
<Location /NI_Uim>
SetHandler weblogic-handler
WebLogicHost host
WebLogicPort port
</Location>
</IfModule>

where:

- host is the name of the WebLogic Administration server machine

- port is the port of the server on which Network Integrity is installed

- To forward requests to the Network Integrity application running on a cluster of Oracle WebLogic Server instances to support integration with UIM, specify /NI_Uim within a new <location> element as follows:

<IfModule weblogic_module>
<Location /NI_Uim>
SetHandler weblogic-handler
WebLogicCluster host1:port1,host2:port2
</Location>
</IfModule>

where:

- host1 and host 2 are host names of the managed servers

- port1 and port2 are ports of the managed servers

- To forward requests to the Network Integrity application running on a single Oracle WebLogic Server instance into which you want to deploy cartridges, specify /cartridge within the <location> element as follows:

<IfModule weblogic_module>
<Location /cartridge>
SetHandler weblogic-handler
WebLogicHost host
WebLogicPort port
</Location>
</IfModule>

where:

- host is the name of the WebLogic Administration server machine

- port is the port of the server on which Network Integrity is installed

- To forward requests to the Network Integrity application running on a cluster of Oracle WebLogic Server instances into which you want to deploy cartridges, specify /cartridge within a new <location> element as follows:

<IfModule weblogic_module>
<Location /cartridge>
SetHandler weblogic-handler
WebLogicHost host
WebLogicPort ms_port
</Location>
</IfModule>

where:

- host is the machine where the managed server is running

- ms_port is the port of the managed server running on the host specified in the host variable above

For example, if a managed server networkintegrity01 with listen port 8065 is running on the machine NETINT1, you must specify the following:

<IfModule weblogic_module>
<Location /cartridge>
SetHandler weblogic-handler
WebLogicHost NETINT1
WebLogicPort 8065
</Location>
</IfModule>

Protecting Resources For SSO Authentication

You must protect resources (for example, the Network Integrity application) in Oracle Access Manager for SSO authentication. For more information, see Fusion Middleware Administrator's Guide for Oracle Access Management.

To protect resources for SSO authentication:

1. Open the Oracle Access Management Console.

2. On the Policy Configuration tab, expand the Application Domains node.

3. Expand the node for the application domain.

4. Within the application domain, expand the Resources node.

5. Click the Resources tab, and then click the New Resource button in the upper-right corner of the Search page.
The Resource Definition page appears.

6. Do the following to configure the Network Integrity application as a protected resource for SSO authentication:

- From the Type list, select HTTP.

- In the Resource URL field, enter /NetworkIntegrity/.../*.

- From the Protection Level list, select Protected.

7. Click Apply.

Excluding Resources From SSO Authentication

You can exclude HTTP resources that do not require SSO authentication. For example, when accessing a Web Services Description Language (WSDL) document for Web services. The excluded resources are public and do not require an OAM Server check for authentication.

When allowing access to excluded resources, WebGate does not contact the OAM Server. Excluded resources cannot be added to any user-defined policy in the console. For more information, see Fusion Middleware Administrator's Guide for Oracle Access Management.

To exclude resources from SSO authentication:

1. Open the Oracle Access Management Console.

2. On the Policy Configuration tab, expand the Application Domains node.

3. Expand the node for the application domain.

4. Within the application domain, expand the Resources node.

5. Click the Resources tab, and then click the New Resource button in the upper-right corner of the Search page.
The Resource Definition page appears.

6. Do the following to exclude Network Integrity Web services from SSO authentication:

- From the Type list, select HTTP.

- In the Resource URL field, enter the following to exclude Network Integrity Web services from SSO authentication:
/NetworkIntegrityApp-NetworkIntegrityControlWebService-context-root/.../*

- From the Protection Level list, select Excluded.

7. Click Apply.

8. Click the New Resource button.
The Resource Definition page appears.

9. Do the following to exclude the Network Integrity cartridge deployment process from SSO authentication:

- From the Type list, select HTTP.

- In the Resource URL field, enter /cartridge/.../*.

- From the Protection Level list, select Excluded.

10. Click Apply.

11. Click the New Resource button.
The Resource Definition page appears.

12. Do the following to exclude the Network Integrity and UIM integration process from SSO authentication:

- From the Type list, select HTTP.

- In the Resource URL field, enter /NI_Uim/.../*.

- From the Protection Level list, select Excluded.

13. Click Apply.

11 Installing Patches

This chapter describes how to install patches on Oracle Communications Network Integrity.

See the patch ReadMe file, included in the patch download, for information about the contents of a patch.

About Patching Network Integrity

Network Integrity patches are posted on the My Oracle Support Web site:

https://support.oracle.com

Most Network Integrity patches are installed using the Oracle Universal Installer. If the Installer fails to install the patch, you must restore your database schema and domain, and your WebLogic Server domain.

The patch ReadMe file specifies whether to use the Installer to install a patch or whether to follow other installation instructions.

Important:
Always read the patch ReadMe file in its entirety before installing a patch.

Install all patches for a release of Network Integrity to benefit from the contents of each patch. For example, if Network Integrity 7.2.2 has three available patches, install each patch. The patch with the latest date does not contain the content from the previous two patches.

Some patches contain fixes and functionality that may not be of any interest to you or may apply to features that you have not installed or purchased. Read the patch ReadMe file to determine if you must install the patch.

Some patches are password protected. To request the password to download a protected patch, open a Service Request on the My Oracle Support Web site.

Planning Your Patch Installation

Before installing a patch, verify your version of Network Integrity and ensure the patch is not already installed.

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

Ensure that Network Integrity is not running any operations, such as scans or blackouts.

As a precaution against a failed patch installation, Oracle recommends that you back up your database schema for Network Integrity, database domain for Network integrity, and your WebLogic Server domain for Network Integrity. See Network Integrity System Administrator's Guide for more information about backing up the database. See your WebLogic Server documentation for more information about backing up your WebLogic Server domain. See "About Rolling Back Network Integrity" for more information about restoring Network Integrity after a failed patch installation.

Oracle recommends installing a patch on a test system with a copy of your production data before installing the patch on your production system. Test the patch by logging into Network Integrity and verifying the version number of installed components

Installing a Patch

To install a patch on Network Integrity:

1. Create a directory (dir).

2. Download the patch for your operating system from the My Oracle Support Web site:
https://support.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:

NI-version/Disk1/install/

4. (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 contains the jre folder inside the Java Development Kit (JDK) installation directory.

The Installer Welcome screen appears.

6. Click Next.
The Specify Home Details screen appears.

7. Do the following:

1. In the Name field, enter, browse to, or confirm the name of the folder that contains the installation files for 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 and retrieves information about your Network Integrity installation, such as connection details and user names.

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

8. 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 any field contains errors.

9. Select the same target WebLogic server or cluster of servers belonging to the WebLogic Server domain and click Next.
If you are installing a patch on a cluster of servers, the Cluster Member Server Selection screen appears, where you can select a cluster member for Network Integrity adapters to patch.

The Database Type Selection screen appears.

10. 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:

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.

- If your old installation is connected to an Oracle Real Application Cluster (RAC) database, select Oracle 12c 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 screen or the RAC DB Nodes Connection Information screen if any field on these screens contains errors.

11. 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.

12. Review the Summary screen and click Install.
The Install screen appears, showing the status of the installation.

Installation log files for Linux and Solaris are saved to NI_Home/oraInventory/logs/installActionDate_Time.log.

Installation log files for IBM AIX are saved to export/home/oracle/oraInventory/logs/installActionDate_Time.log.

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

13. Click Installed Products and verify that the patch is listed.

14. Click Exit.

12 Uninstalling Network Integrity

This chapter describes how to uninstall Oracle Communications Network Integrity.

About Uninstalling Network Integrity

You use the Oracle Universal Installer to uninstall Network Integrity. You can also uninstall other components of the Network Integrity product using the Oracle Universal Installer.

Uninstalling Network Integrity or Network Integrity Components

To uninstall Network Integrity, or a component belonging to the Network Integrity product:

1. Go to the location of the install folder into which you have untarred the original Network Integrity installation file. The folder structure should look something like the folder structure shown here:
integrity/Disk1/install

2. In the install folder, run the OUI executable file runInstaller by using the following command syntax:
./runInstaller

The Oracle Universal Installer installation wizard starts.

The Welcome screen appears.

3. Click Deinstall Products.
The Inventory screen appears.

4. Select the item(s) you want to uninstall.

5. Click Remove.

Note:
Selecting Show Empty Homes displays any previously created Oracle product homes. Select displayed homes, or folders, to remove them.

The User Input screen appears.

6. In the WebLogic User Password field, enter your WebLogic user password, and click OK.
The Confirmation screen appears.

7. View and confirm your selection, and click Next.
You can see the remove progress as the selected components are uninstalled.

The installer removes Network Integrity files and directories, except the logs. If required, delete the log files manually. The logs can be found at the following location:

CentralInventorylocation/logs/

Note:
Some files and directories will not be removed from the Network Integrity home directory during uninstallation. Verify that these remaining files and directories do not contain any customized information that may be necessary for upgrades, and if required, remove the files manually.
The Network Integrity schema, Network Integrity user, Cartridge Deployer Client and CMWS user will not be removed during uninstallation. The database schema and application users can be used by other applications, so they should not be deleted.

8. Remove the MDS schema user. Refer to Oracle Fusion Middleware Repository Creation Utility User's Guide for details on removing/dropping the schema.

Uninstalling Network Integrity Using the Silent Mode

Use the following command to uninstall Network Integrity:

./runInstaller -responseFile path -silent -deinstall

Where path is the location of the response file that was created during silent mode installation of Network Integrity.

After a successful uninstall, you get a message indicating that Network Integrity has been uninstalled successfully.

13 Troubleshooting the Network Integrity Installation

This chapter describes how to troubleshoot the Oracle Communications Network Integrity installation. For more information on troubleshooting Network Integrity, see Network Integrity System Administrator's Guide. To verify that the installation was successful, see "Verifying the Network Integrity Installation".

Common Problems and Their Solutions

This section describes the following installation problems, and how to resolve them:

- Problem: Installer Fails to Update Application KEYSTORE Table

- Problem: Installer Fails to Update Application INFORMATION Table

- Problem: Inability To Run Scans or Resolve Discrepancies After Upgrading

- Problem: Unable to Load Performance Pack

- Problem: Application Server Takes a Long Time to Start

Problem: Installer Fails to Update Application KEYSTORE Table

If the installer fails to update the application KEYSTORE table, the installer is interrupted and the following error message appears:

Unable to update application key store 'AppKeyStore', please check log files for more details. Refer to Network Integrity documentation for executing this step manually.

Solution

Click the Continue button to complete the installation. Manually update the application KEYSTORE table when the installation is complete.

To manually update the application KEYSTORE table:

1. Navigate to NI_Home/POMSClient.

2. Execute the following command:

jre_Path/bin/java -javaagent:lib/eclipselink.jar -cp POMSClient.jar oui.j2ee.poms.client.UpdateAppKeyStore DB_HostName DB_Port DB_ServiceName NI_Schema_UserName NI_Schema_Password default aes 128

where:

- jre_Path contains the jre folder inside the Java Development Kit (JDK) installation directory

- DB_HostName is the database host name

- DB_Port is the database port number

- DB_ServiceName is the database service name or system ID

- NI_Schema_UserName is a valid Network Integrity database user name for the schema

- NI_Schema_Password is the password for the Network Integrity schema user name

3. Connect to the application KEYSTORE table and verify the following:

- That the COMPONENT column has a value of default.

- That the ENCRYPTALGORITHM column has a value of aes.

- That the KEYLENGTH column has a value of 128.

4. Restart Network Integrity for the changes to take effect, as explained in Network Integrity System Administrator's Guide.

Problem: Installer Fails to Update Application INFORMATION Table

If the installer fails to update the application INFORMATION table, the installer is interrupted and the following error message appears:

Unable to update application details 'ApplicationInfo', please check log files for more details. Refer to Network Integrity documentation for executing this step manually.

Solution

Click the Continue button to complete the installation. Manually update the application INFORMATION table when the installation is complete.

To manually update the application INFORMATION table:

1. Navigate to NI_Home/POMSClient.

2. Execute the following command:

jre_Path/bin/java -javaagent:lib/eclipselink.jar -cp POMSClient.jar oui.j2ee.poms.client.UpdateAppInfoTable DB_HostName DB_Port DB_ServiceName NI_Schema_UserName NI_Schema_Password "Network Integrity" NI_Version SUCCESS

where:

- jre_Path contains the jre folder inside the JDK installation directory

- DB_HostName is the database host name

- DB_Port is the database port number

- DB_ServiceName is the database service name or system ID

- NI_Schema_UserName is a valid Network Integrity database user name for the schema

- NI_Schema_Password is the password for the Network Integrity schema user name

- NI_Version is the version of Network Integrity being installed

3. Connect to the application INFORMATION table and verify the following:

- That the NAME column has a value of Network Integrity.

- That the VERSION column has the correct version of Network Integrity.

- That the STATUS column has a value of SUCCESS.

Problem: Inability To Run Scans or Resolve Discrepancies After Upgrading

After upgrading Network Integrity, you may be unable to run scans or resolve discrepancies using cartridges if you have unmigrated cartridges still deployed to your system.

To confirm that you are experiencing this issue, verify the following:

- Network Integrity displays the following error messages when you try to run a scan:

Unable to start scan, as cartridge is in the process of getting deployed or undeployed.

- Network Integrity displays the following error messages when you try to resolve discrepancies:

All Plugins are not ready. Cartridge deploy or undeploy is in progress.

- The DisPlugin database table has the value 0 set for the pluginready attribute for some cartridges.

Solution

Resolve this issue by doing the following:

- Migrate all deployed, unmigrated cartridges that you are licensed and permitted to migrate.

- Run the Troubleshoot_delete_unused_plugins_post_upgrade.sql script to delete the remaining unmigrated cartridges from your system:

1. In Network Integrity, delete all scan configurations related to unmigrated cartridges.

2. From the command prompt, go to the NI_Home/integrity/upgrade/migration directory.

3. Enter the following command, to execute the script as the Network Integrity MDS DB schema user, using sqlplus:

Troubleshoot_delete_unused_plugins_post_upgrade.sql

4. Follow the command-line prompts.
The script deletes all cartridges from the system that have a pluginready value of 0 in the DisPlugin database table.

5. Restart Network Integrity.

6. Run a test scan to confirm that the issue is resolved.

Problem: Unable to Load Performance Pack

This procedure is only applicable if you are running WebLogic Server 10.3.6 on a Solaris platform with a 64-bit JVM.

There is a known issue that is encountered when starting the WebLogic server. Specifically, the 64-bit native libraries are not loaded correctly. To confirm that you have this issue, search the standard output log for the following error:

Unable to load performance pack

Solution

If you have this issue, do the following:

1. Back up and edit the Domain_Home/bin/setDomainEnv.sh file.

2. Add the following lines to the end of the file:

LD_LIBRARY_PATH_64=${BEA_HOME}/wlserver_10.3/server/native/solaris/sparc64
export LD_LIBRARY_PATH_64

3. Save and close the file.

Problem: Application Server Takes a Long Time to Start

If the Network Integrity environment has McAfee AntiVirus software installed, the Application server takes a long time to start.

Solution

Add the NI_Home, MW_Home, and WL_Home/server/lib/Java_Home directories to the McAfee exclusion list so that these directories are excluded from being scanned.

where:

- NI_Home is the directory in which the Network Integrity software is installed.

- MW_Home is the directory in which the Oracle Fusion Middleware products, files, and folders are installed.

- WL_Home is the directory in which WebLogic Server is installed. WL_Home is located in MW_Home.

- Java_Home is the JDK installation directory.

Reporting Problems

Before calling Oracle Global Support, read the description of preparing to call Global Support in the Troubleshooting chapter in Network Integrity System Administrator's Guide.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2016, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Alpha and Beta Draft Documentation Notice

If this document is in private preproduction status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.