Network Integrity Installation On Linux

Oracle Communications Network Integrity
Installation Guide Release 7.0.1

E20436-01
March 2011
Oracle Communications Network Integrity Installation Guide, Release 7.0.1 E20436-01 Copyright 2010, 2011, 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 software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software 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 which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. This software and documentation may provide access to or information on 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. 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.
Contents
Preface ................................................................................................................................................................ vii
Audience...................................................................................................................................................... Related Documents .................................................................................................................................... vii vii
1 Network Integrity Installation Overview

Overview of Network Integrity Installed Components ................................................................... Overview of the Network Integrity Installation Procedure............................................................. About the Network Integrity Installer ................................................................................................. Common Installer Services ............................................................................................................... Network Integrity Installation Options............................................................................................... Ensuring a Successful Network Integrity Installation...................................................................... About Upgrading Network Integrity ................................................................................................... 1-1 1-1 1-2 1-3 1-3 1-3 1-4
2 Network Integrity System Requirements

Software Requirements........................................................................................................................... Supported Operating Systems ......................................................................................................... Additional Software Requirements ................................................................................................. Hardware Requirements......................................................................................................................... Information Requirements..................................................................................................................... WebLogic Connection Information ................................................................................................. Database Connection Information................................................................................................... Database Connection Information For Real Application Cluster Database....................... Schema User Name Information...................................................................................................... 2-1 2-1 2-1 2-2 2-3 2-3 2-4 2-4 2-5
3 Network Integrity Pre-Installation Tasks

Overview of Pre-Installation Tasks ...................................................................................................... Installing and Configuring the Oracle Database ............................................................................... Setting the Database Time Zone ...................................................................................................... Creating the Database (MetaData) Schema for Network Integrity ............................................ Installing and Configuring Oracle Database Real Application Clusters ................................... Tuning the Database .......................................................................................................................... Installing the SQL*Plus Instant Client ........................................................................................... Installing and Configuring Oracle WebLogic Server........................................................................ About Java Requirements ................................................................................................................. Installing IBM Java...................................................................................................................... 3-1 3-1 3-2 3-2 3-4 3-4 3-4 3-5 3-5 3-5
iii
Installing Oracle JRockit Real Time.......................................................................................... 3-5 Installing the Sun JDK ................................................................................................................ 3-5 Switching Between the Oracle JRockit Real Time JDK and the Sun JDK ........................... 3-6 Downloading and Installing Oracle WebLogic Server 10.3.2...................................................... 3-6 Installing Oracle Application Development Runtime 11g........................................................... 3-7 Creating an Oracle WebLogic Server Domain for a Standalone Installation ............................ 3-7 Setting Memory Requirements for Network Integrity....................................................... 3-10 Configuring Automatic Service Migration (ASM) on the WebLogic Server.......................... 3-11 Verifying WebLogic Administration Server Migration ..................................................... 3-12 Setting Up Network Integrity on a Server Cluster..................................................................... 3-12 Installation Scenario ................................................................................................................ 3-13 Server Cluster Example........................................................................................................... 3-13 Network Integrity Server Cluster Prerequisites .................................................................. 3-14 Overview of Steps for Setting Up Network Integrity on a Server Cluster ...................... 3-15 Installing Oracle WebLogic Server and Network Integrity in a Clustered Environment........ 3-15 Creating a Domain................................................................................................................... 3-15 Starting the Oracle WebLogic Server .................................................................................... 3-19 Starting the Cluster Member Servers .................................................................................... 3-20 Configuring the WebLogic Server StuckThreadMaxTime Value .................................... 3-21 Installing and Configuring Additional Third-Party Software..................................................... 3-21 Installing and Configuring Oracle Internet Directory ............................................................... 3-21 Configuring The Authentication Provider........................................................................... 3-22 Configuring Custom Authentication Providers ......................................................................... 3-24 Installing and Configuring Oracle BI Publisher 10g .................................................................. 3-24
4 Installing Network Integrity

Types of Installation ................................................................................................................................ Installing Network Integrity in the GUI Mode.................................................................................. Installing Network Integrity in Silent Mode...................................................................................... About the Response File.................................................................................................................... Populating the Response File .................................................................................................... Starting Silent Mode Installation ..................................................................................................... 4-1 4-1 4-6 4-6 4-7 4-8
5 Network Integrity Post-Installation Tasks

Overview of Network Integrity Post-Installation Tasks .................................................................. 5-1 About the Trusted Certificate for Network Integrity ................................................................... 5-1 Managing Network Integrity Cartridges............................................................................................. 5-1 Managing Network Integrity Cartridges with the Cartridge Deployer Tool ........................... 5-2 Deploying Cartridges ................................................................................................................. 5-2 Undeploying Cartridges ............................................................................................................ 5-4 Deploying/Undeploying Cartridges on/from a Remote Server......................................... 5-6 Viewing Cartridges..................................................................................................................... 5-6 Managing Cartridges With Custom Scripts ................................................................................... 5-8 Developing a Custom Java Application .................................................................................. 5-8 Developing Custom ANT Tasks ............................................................................................ 5-10 Running Cartridge Operations From a Command Line .................................................... 5-11
iv
Migrating Cartridges ...................................................................................................................... Migrating Network Integrity Production Cartridges......................................................... Migrating Network Integrity Sample and Custom Cartridges......................................... Enabling Cache Coordination in Remote Servers ........................................................................ Configuring Network Integrity for Inventory Management........................................................ Installing Network Integrity Report Templates.............................................................................. Starting the AgeOut Process ............................................................................................................... Starting the AgeOut Process Using Oracle Enterprise Manager ............................................. Starting the AgeOut Process Using JConsole..............................................................................
5-13 5-14 5-14 5-15 5-17 5-17 5-18 5-19 5-19
6 Verifying the Network Integrity Installation

Checking the State of all Installed Components ............................................................................... 6-1 Logging In to Network Integrity ........................................................................................................... 6-1
7 Uninstalling Network Integrity

About Uninstalling Network Integrity ................................................................................................ 7-1 Uninstalling Network Integrity or Network Integrity Components ............................................. 7-1 Uninstalling Network Integrity Using the Silent Mode .................................................................. 7-2
vi
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 Oracle Communications 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
Oracle Communications Network Integrity Installation Guide is one book in the following set of resources that make up the Network Integrity documentation suite. The resources include:
Oracle Communications Network Integrity Installation Guide: Describes the requirements for installing Network Integrity, pre-installation tasks, installation procedures, and post-installation tasks. Oracle Communications Network Integrity System Administrators Guide: Describes, and provides procedures for, the tasks, such as managing and monitoring the Network Integrity system, that a Network Integrity system administrator performs. Concepts: Provides an outline of Network Integrity high-level concepts and architecture. Developers 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.
vii
Online Help: Provides step-by-step instructions for tasks you perform in Network Integrity. Design Studio 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. Cartridge Guides: Describe the content of product technology packs as well as configuration guidelines and implementation considerations. Oracle Communications Network Integrity - UIM Sample Technology Pack for Cisco Devices Guide Oracle Communications Network Integrity - MIB-II SNMP Cartridge Guide Oracle Communications Network Integrity - MIB-II UIM Integration Cartridge Guide Oracle Communications Network Integrity - Cisco Router and Switch SNMP Cartridge Guide Oracle Communications Network Integrity - Cisco Router and Switch UIM Integration Cartridge Guide Oracle Communications Network Integrity - UIM Sample Web Service Guide Oracle Communications Network Integrity - UIM MIB-II Logical Device Sample Technology Pack Guide Oracle Communications Network Integrity - Optical TMF814 CORBA Cartridge Guide Oracle Communications Network Integrity - CORBA Cartridge Guide Oracle Communications Network Integrity - File Transfer and Parsing Guide
Oracle Communications Information Model Reference: Describes entities and patterns in the Oracle Communications Information Model (the Information Model). The Information Model entities and patterns that are available within Network Integrity, and the application-specific capabilities applied to CIM entities within Network Integrity, are described in an appendix to the Oracle Communications Network Integrity Developer's Guide. Note that the Oracle Communications Information Model Reference is a password protected document on the Oracle E-Delivery Web site. Network Integrity Release Notes: Provides information like new features and known issues for Network Integrity.
viii
1
1
Network Integrity Installation Overview

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

During the installation process, you install and configure the following components:

Oracle Database server Oracle WebLogic Server Network Integrity application Optional software Oracle Internet Directory, 3rd party LDAP, if required Oracle Business Intelligence Publisher, for report creation Oracle Communications Unified Inventory Management 7 (UIM)
Network Integrity Cartridges
Overview of the Network Integrity Installation Procedure

The following is an outline of the installation procedure for Network Integrity:
1.
Plan your installation. Planning your installation involves: Determining the scale of your implementation; for example, is it a small test system, or a large production system. For this, it might be a good idea to assess the scale of the network or dataset to be discovered or reconciled. Assessing how many physical machines you need, and which software components to install on which machines. Planning the system topology; for example, determining whether you want a standalone deployment or a clustered deployment.

2.
Review system requirements. System requirements include: System software requirements, such as operating system (OS) versions and OS patch requirements. Hardware requirements, such as disk space. Information requirements, such as IP addresses and host names.
3.
Perform the following pre-installation tasks:
1-1
About the Network Integrity Installer
Setting up the database Installing and configuring an Oracle database
Note:
If you have a database server installed already, obtain a tablespace for Network Integrity on that database server. Installing Oracle SQL *Plus Creating a Database (Metadata) schema Installing and configuring Oracle Database Real Application Clusters
Installing and configuring Oracle WebLogic Server (WebLogic): Installing JDK, or JRockit, or both Installing and configuring WebLogic Installing ADF 11g Run-time Creating a WebLogic domain
Managing Security: Selecting the WebLogic default embedded LDAP server Installing Oracle Internet Directory 11g OID is optional and requires a separate license.
Note:
Preparing for reports Installing Oracle Business Intelligence Publisher 10g (BI Publisher) BI Publisher is optional and requires a separate license.
Note:
4.
Install Network Integrity You are required to provide the following connection information during installation:

WebLogic Server details Database, or RAC database, server details Network Integrity schema user details Security provider details
5. 6. 7.
Deploy Network Integrity cartridges Perform post-installation configuration tasks Verify the installation
About the Network Integrity Installer

You install Network Integrity using the Network Integrity Installer (the Installer). The GUI-based Installer installs the core application and also configures connections with the components, as per the connection details you provide during installation.
1-2 Network Integrity Installation Guide
Ensuring a Successful Network Integrity Installation
Common Installer Services

The Network Integrity Installer provides the following common services:
Help Each screen in the Installer contains context sensitive help accessible by clicking the Help button.
Logging The Installer logs can be found at CentralInventorylocation/logs/. You use the following log files to monitor installation and post-installation events: installActionTimeStamp.log oraInstallTimeStamp.log oraInstallTimeStamp.log dbScriptsgTimeStamp.log silentInstallTimeStamp.log (for Silent mode installation)
Inventory updates This and all subsequent installations are updated in the Oracle Inventory. This is useful for updating the application at a later time. Oracle inventory updates include the following: Component Name Version Build Number Release Install location, time stamp Oracle Home Name Location Mapping
Localization The current version of Network Integrity only supports English - US.
Network Integrity Installation Options

You can install Network Integrity in the GUI mode (using the Installer) or in silent install mode.
GUI mode: Use the GUI mode when you want to interact with the Installer GUI during installation. Silent install mode: Use the 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.
Ensuring a Successful Network Integrity Installation

Network Integrity installation 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
1-3
About Upgrading Network Integrity
Oracle Database 11gR2 administration
Additionally, you should have experience installing Java-related packages. It is recommended that the installation and configuration of the Oracle database be performed by an experienced database administrator. Follow these guidelines:
As you install each component; for example, the Oracle database and WebLogic Server, 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 will be required to enter configuration values later in the procedure.
About Upgrading Network Integrity

It is not possible to upgrade to Network Integrity 7.0.1 from any previous version. A clean installation is required.
2
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 is comprised 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 21 lists operating systems that support Network Integrity.
Table 21 Product
Network Integrity Operating Systems Requirements Version 5 UL3+ 5 UL3+ 10 Update 4+ 6.1 on POWER Hardware (Technology Level 5 SP2)
Oracle Enterprise Linux, x86 (32bit) or x86-64 (64bit) Red Hat Enterprise Linux, x86 (32bit) or x86-64 (64bit) Oracle Solaris for SPARC (64bit) IBM AIX (64bit)
Additional Software Requirements

Table 22 lists software required for running Network Integrity.
Table 22 Product Oracle WebLogic Server 11g Enterprise Edition Oracle Fusion Middleware 11g Application Development Runtime JRockit Real Time 4.0 for Java version 6 for Linux x86 or x86-64 or Solaris SPARC (64bit) Network Integrity Software Requirements Version 10.3.2 11.1.1.2 1.6 (1.6.0_17-b04+) Disk Space 604 MB 697 MB 101 MB
Network Integrity System Requirements 2-1
Hardware Requirements
Table 22 (Cont.) Network Integrity Software Requirements Product Sun Hotspot (JDK) for Linux x86 or x86-64 or Solaris SPARC (64bit) Version Linux x86: 1.6.0_20 Linux x86-64: 1.6.0_18 Solaris SPARC: 1.6.0_18 IBM Java SE Runtime Environment for IBM AIX (64bit) Oracle Database 11g R2 Enterprise Edition (for single, or Real Application Clusters (RAC) installation) Instant Client (SQL*Plus) Oracle Communications Unified Inventory Management (UIM) Business Intelligence (BI) Publisher 1.6.0 build 2.4 11g R2 155 MB 1.2 GB Disk Space 158 MB
11.2 7.1.1 7.1.2 10.1.3 (10.1.3.4.1+)
1 MB
770 MB
Oracle Internet Directory 11g Oracle Fusion Middleware Repository Creation Utility 11g for Linux x86 Oracle Communications Design Studio Internet Browser
11.1.1.2.0 11.1.1.2.0 3.1.2 or later Microsoft Internet Explorer 7, 8 Mozilla Firefox 3.5, 3.6
60 MB 320 MB
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.
Note:
For details on how to download the required software component, see the section of the guide for each component. Oracle Enterprise Manager 11g Fusion Middleware Control, which is used for WebLogic Server and application management, is available as part of Fusion Middleware 11g Application Development Runtime. BI Publisher 10g is required for use of reporting templates included with Network Integrity.
Hardware Requirements
The number and configuration of the machines 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). Table 23 provides the minimal hardware requirement for Network Integrity installed on a single managed server in a WebLogic domain.
Table 23 Network Integrity Minimum Hardware Requirements Requirement 1.5 GB free
Component Hard disk
Information Requirements
Table 23 (Cont.) Network Integrity Minimum Hardware Requirements Component Processor Requirement 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 A minimum of 4 GB physical memory and 4 GB swap. If you plan to have the database installed on the same server as Network Integrity, the minimum memory requirements increase to 6 GB physical memory and 6 GB swap. Color bit depth display and size Temporary disc space For Graphical User Interface (GUI) mode installation, 8-bit color depth (256 colors) is required. 150 MB The Network Integrity Installer uses a temporary directory to extract all installation files, the compressed Java Run-time Environment (JRE) bundled with the Network Integrity installer, and an uncompressed copy of the JRE. These files are deleted after installation.
During Network Integrity installation, you are required to enter configuration values such as host names and port numbers. This section describes the information that you will be required to provide during the installation process. You define some of these configuration values when you install and configure the Oracle database and WebLogic. If you have already installed the 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 uses the default values shown in this table.
Note: It is advisable that you print the table(s) and enter your values for future reference.
You will be required to enter these values during the installation process.
WebLogic Connection Information

Table 24 lists WebLogic server connection details that you are required to provide during installation.
Table 24 Application Server Connection Information Description You provide the host name for this particular WebLogic server instance to define it uniquely for the specific purpose of installing, and working with, Network Integrity. Default Value current_ hostname Sample Value localhost
Information Type Host Name
Table 24 (Cont.) Application Server Connection Information Information Type Port Number Description This is the number assigned to this specific service. Port numbers are usually pre-defined and you can accept the provided default value. Your WebLogic Server user name. You define this name when you install Oracle WebLogic Server. 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. The Oracle WebLogic Home directory where all software binaries for Oracle WebLogic Server are installed. Default Value 7001 Sample Value 7001
User Name
weblogic
Provide an appropriate user name Provide an appropriate password
Password
This option has no default value.
WebLogic Home
/opt/oracle/Middlew are/wlserver_10.3
Database Connection Information

Table 25 lists database connection details that you are required to provide during installation.
Table 25 Database Connection Information Description Host name of the server where you install Network Integrity. Default Value This option has no default value. 1521 Sample Value localhost
Information Type Hostname
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. 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. This is the name of the database service or instance to remotely connect to the database.
1521
sys
Provide an appropriate user name Provide an appropriate password
Password
Service Name
orcl
orcl.oracle.com
Database Connection Information For Real Application Cluster Database

Table 26 lists database connection details for a Real Application Cluster (RAC) database that you are required to provide during installation.
Table 26
Database Connection Information for RAC database Description The information string that is used to connect to the RAC database. Default Value This option has no default value. Sample Value HOST NAME1:PORT1:SERVI CE NAME1, HOST NAME2:PORT2:SERVI CE NAME2 A user with the same privileges/roles as SYS. Provide an appropriate password.
Information Type RAC Database Connection String User name
Your database user name. You define the user name when you install the database. 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.
sys
Password
Schema User Name Information

Table 27 lists schema user details that you are required to provide during installation.
Table 27 Schema user Information Description Your schema user name that you will use to access the Network Integrity schema. The password to access the Network Integrity schema for the schema user you defined. Default Value This option has no default value. This option has no default value. Sample Value Provide an appropriate user name. Provide an appropriate password.
Information Type Schema User Name Schema User Password
3
3
Network Integrity Pre-Installation Tasks

This chapter describes the tasks that you perform before installing Oracle Communications Network Integrity.
Overview of Pre-Installation Tasks

Pre-installation tasks for Network Integrity are divided into the following four groups:
Setting up the Database Installing and configuring the Oracle database Installing Oracle SQL *Plus Creating Network Integrity Metadata schema user
Installing and configuring an Oracle WebLogic Server Installing the Sun JDK, or Oracle JRockit Installing and configuring an Oracle WebLogic Server Installing the ADF 11g Run-time Creating an Oracle WebLogic Server domain
Managing security Using the default embedded LDAP server (Optional) Installing Oracle Internet Directory 11g
(Optional) Preparing for reports Installing Oracle Business Intelligence Publisher (BI Publisher) 11g
Installing and Configuring the Oracle Database

The Network Integrity Installer checks for a database to connect to during the installation process. Ensure that a database is up and running before you start installing Network Integrity. If you already have a database up and running, create a tablespace for Network Integrity. See chapter Network Integrity System Requirements for Database requirements.
Note:
Oracle recommends Oracle Database 11g R2 for maximum performance output with Network Integrity.
Network Integrity Pre-Installation Tasks 3-1
Download and install Oracle Database 11g R2 for this version of Network Integrity. Download Oracle Database 11g R2 from the Oracle E-Delivery Web site, located at: https://edelivery.oracle.com For information on installing Oracle database, see the Oracle Database installation documentation.
Caution: The XDB component of the Oracle Database must be installed for a successful Network Integrity installation.
For information on XDB and how to install it, refer the Oracle Database documentation on the Oracle Technology Network located at: http://www.oracle.com/technology
Setting the Database Time Zone

The Oracle Database must have the correct time zone setting, as 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: Once 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 a Fusion Middleware component that is required by Network Integrity. You create the schema using the Repository Creation Utility (RCU). Download Oracle Fusion Middleware Repository Creation Utility 11g (11.1.1.2.0) for Linux x86 or Oracle Fusion Middleware Repository Creation Utility 11g (11.1.1.2.0) for Microsoft Windows from the Network Integrity media pack available at the following location: http://edelivery.oracle.com/ For information on creating the MetaData schema, see the Repository Creation Utility User's Guide.
Note:
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. 2.
Extract the RCU package. Execute the following command:

rcuHome/bin/rcu
The Welcome screen of the Repository Creation Utility Installation wizard appears.
3.
Click Next.
The Create Repository screen appears.

4.
Select Create and click Next. The Database Connection Details screen appears.
5.
Do the following:
a. b. c. d. e.
In the Database Type list, select Oracle Database. In the Host Name field, enter the IP address of the machine hosting the database. In the Port field, enter the port number for the machine hosting the database. In the Service Name field, enter the service name. In the Username field, enter the user name for the database user.
Note:
This user must have DBA, or SYSDBA, privileges.
Caution: Ensure that you use these same user credentials, that is, user name and password, while providing Network Integrity schema user information during Network Integrity installation.
f. g. h.
In the Password field, enter the password for the database user. In the Role list, select SYSDBA. Click Next. The Select Components screen appears.
6.
Select Create a new Prefix, and enter the prefix value in the corresponding box. The prefix is any appropriate name for your schema. RCU adds a suffix to this name.
7. 8.
When specifying components, choose Oracle AS Repository Components; then, expand AS Common Schemas and select Metadata Services. Click Next. The Schema Passwords screen appears.
9.
Select Use same password for all schemas.
10. In the Password field, enter the password for the schema. 11. In the Confirm Password field, enter the password for the schema again and click
Next. The Map Tablespaces screen appears.

12. Select the required tablspace and click Next.
The Summary screen appears.

13. Review and verify the information you have provided and click Create.
Upon successful completion, the Completion Summary screen shows details of the newly created repository.
Installing and Configuring Oracle Database Real Application Clusters

Oracle recommends Oracle Real Application Clusters for high availability and scalability if your network data requires multiple databases for storage purposes. Refer to the Oracle Real Application Clusters documentation at the following location: http://www.oracle.com/technology
Tuning the Database

The following tables provide recommended database parameters for tuning your database for the Network Integrity installation. These are the minimum requirements for Network Integrity.
Table 31 Parameter SGA+PGA Database Creation Parameters Recommended Value At least 4GB in total. It is recommended that you use as much memory as you have available in the system, and also use Automatic Memory Management. Processes Connection mode Redo log file size 2000 Dedicated server 1024 MB minimum
Table 32 Parameter
Database Initialization Parameters Recommended Value 16 7200 9700 10 31457280 5000 640 NATIVE
db_file_multiblock_read_ count distributed_lock_timeout dml_locks job_queue_processes log_buffer open_cursors parallel_max_servers plsql_code_type
Installing the SQL*Plus Instant Client

Download SQL *Plus Instant Client from the Oracle Technology Network. For information on installing and configuring SQL *Plus Instant Client, see the SQL *Plus Instant Client installation documentation. If you are installing Network Integrity on the IBM AIX operating system, it is necessary to set the LIBPATH environment variable on AIX to the installation location of the SQL *Plus Instant Client.
Installing and Configuring Oracle WebLogic Server
Caution: Install Oracle SQL *Plus in the Administration server from where you will launch the Network Integrity Installer. Both SQL *Plus and the installer should be on the same path.
The SQL*Plus Instant Client package should never be installed in an ORACLE_Home.

Network Integrity is installed and run WebLogic Administration Server. This section describes procedures relating to installing the WebLogic Administration Server and other required applications, and also configuring the WebLogic Server domain where you will install Network Integrity.
Note:
Ensure that the Administration Server is up and running in the WebLogic Server domain before you install Network Integrity.
About Java Requirements

Note:
Oracle recommends Sun JDK for development mode, and WebLogic JRockit for production mode.
WebLogic server is a Java application and needs a Java environment in which to run. You can use any of the popular, available Java environments for your WebLogic server. When WebLogic server is installed on IBM AIX, Oracle recommends installing IBM Java. When WebLogic server is installed on Linux or Solaris, Oracle recommends that you use either the Sun JDK, or the Oracle JRockit JDK. The JRockit JDK includes the Oracle JRockit Java Virtual Machine (JVM). You can switch between the two JDKs, if you have both installed on your system.
Installing IBM Java

Download the Java6_64.sdk.tar Java SDK from the IBM Web site. For information on installing IBM Java, refer to IBM Java Installation documentation.
Installing Oracle JRockit Real Time

Download Oracle JRockit Real Time from the Oracle Technology Network. For information on installing Oracle JRockit Real Time, see the Oracle JRockit Real Time installation documentation.
Installing the Sun JDK

Use a 64-bit Java Development Kit (JDK) on a 64-bit operating system (OS) and a 32-bit JDK on a 32-bit OS for a successful Network Integrity installation. Download the Sun JDK for the required platform from the Oracle Technology Network. For information on installing Sun JDK, see the Sun JDK installation documentation.
Switching Between the Oracle JRockit Real Time JDK and the Sun JDK
You can switch between the Oracle JRockit D and the Sun JDK for the existing domain, if you have both installed, at any time. To switch from the Sun JDK to JRockit:
1. 2. 3.
Log in to the Administration console. Stop the Administration Server and all running managed servers. Go to the following location: DOMAIN_Home/bin
4. 5.
Open the file setDomainEnv.sh for editing. Modify the value for BEA_JAVA_Home to point to where JRockit is installed, as follows:
BEA_JAVA_Home="/opt/oracle/jrrt-4.0.0-1.6.0" JAVA_Home="/opt/oracle/jrrt-4.0.0-1.6.0"
Shown here is a sample:

BEA_JAVA_Home="/opt/oracle/jrrt-4.0.0-1.6.0" export BEA_JAVA_Home SUN_JAVA_Home="/opt/oracle/jdk1.6.0_18" SUN_JAVA_Home="" export SUN_JAVA_Home if [ "JAVA_Vendor" = "Oracle" ; then JAVA_Home="BEA_JAVA_Home" export JAVA_Home else if [ "JAVA_Vendor" = "Sun" ; then JAVA_Home="SUN_JAVA_Home" export JAVA_Home else JAVA_Vendor="Sun" export JAVA_Vendor JAVA_Home="/opt/oracle/jrrt-4.0.0-1.6.0" export JAVA_Home 6.
After the setDomainEnv.sh file has been modified, start the Administration Server and all of the managed servers.
Downloading and Installing Oracle WebLogic Server 10.3.2

Oracle WebLogic Server is available as a component of the Oracle Fusion Middleware 11g media pack. Fusion Middleware 11g PS1 is the latest release and includes WebLogic Server 10.3.2, and JDeveloper 11.1.1.2 among other software.
Note:
The critical security patch SU: 9324911 for Oracle WebLogic Server 10.3.2 must be applied post-installation. Refer the Critical Patch Updates and Security Alerts page at the Oracle Technology Network Web site.
Download Oracle WebLogic Server 10.3.2 from the Oracle E-Delivery site, located at:
http://edelivery.oracle.com/ For information about installating Oracle WebLogic Server 10.3.2, see the Oracle WebLogic documentation on the Oracle Technology Network.
Installing Oracle Application Development Runtime 11g

Download Oracle Application Development Runtime 11g from the Oracle E-Delivery site. For installing Oracle Application Development Runtime 11g, see the Oracle WebLogic Server 10.3.2 documentation on the Oracle Technology Network.
Note: The Oracle Fusion Middleware 11g Application Developer Installer installs both Oracle Application Development Runtime and Oracle Enterprise Manager.
For more information on the Application Development Framework, see Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.
Creating an Oracle WebLogic Server Domain for a Standalone Installation

Create a WebLogic domain with at least one managed server configured along with the Administration server. To create a standalone WebLogic Server domain:
1.
Go to the following path:

WL_Home/common/bin
2.
Enter the following command:

./config.sh
The Welcome screen of the Fusion Middleware Configuration Wizard appears.

3.
Select the Create a New WebLogic domain option and click Next. The Select Domain Source screen appears.
4.
Select the Generate a domain configured automatically to support the following products: option, and from the provided list, select the following products:

Oracle Enterprise Manager - 11.1.1.0 [oracle_common] Oracle JRF - 11.1.1.0 [oracle_common]
5.
Click Next. The Specify Domain Name and Location screen appears.
6. 7.
In the Domain name field, enter a domain name. In the Domain location field, enter the path and directory where the domain files will be created. For example, enter the value:
WL_Home/user_projects/domains/base_domains
8.
Click Next. The Configure Administrator User Name and Password screen appears.
9.
In the User name field, enter the administrator user name.

10. In the User 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, re-enter your password.
11. (Optional) In the Description field, enter information about the administrator. For
example: This user is the default administrator (or whatever text fits your business practices).
12. In the WebLogic Domain Startup Mode section, select the Production Mode
option. In the Available JDKs section, select the required JDK. Oracle recommends the Sun JDK for development mode, and JRockit for production mode:

Sun JDK 1.6.0._18 Sun JDK 1.6.0._20 JRockit4.0.0-1.6.0
13. Click Other JDK to browse to the location of another JDK. Ensure that this JDK is
supported. See the chapter Network Integrity System Requirements for details.
14. Click Next.
The Select Optional Configuration page appears.

15. Select the following:

Administration Server Managed Servers, Clusters and Machines Deployments and Services
16. Click Next.
The Configure the Administration Server screen appears.

17. Do the following: a.
In the Name field, enter the Administration Server name. This single server serves as the Network Integrity domain Administration Server.
b.
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.
c. d. e.
In the Listen Port field, accept the default. In the SSL Listen Port field, enter a port that is not used by another domain. Select SSL enabled if you are enabling SSL. It is not a requirement to either enable or disable SSL.
f.
Click Next. The Configure Managed Servers screen appears.
18. Do the following:
a. b. c.
Click Add to create a managed server. In the Name field, enter a name for the managed server. In the Listen address field, enter the host, or IP address of the machine where the managed server is running.
Note:
d. e. f. g. h.
In the Listen port field, enter the number of the port where the managed server will listen for incoming messages. 8061 In the SSL listen port field, enter the appropriate value only if SSL is selected. Select SSL enabled as required. (Optional) Create further managed servers as required on your Network Integrity deployment. Click Next The Configure Clusters screen appears.
19. Click Next, as you are performing a standalone installation, that is, you are not
using clustering in this installation. The Configure Machines screen appears Use this screen to change the configuration information for machines. A machine 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 machine definition to start remote servers.
20. Add the machines by carrying out one of the following options:
Select the Machine tab, and do the following:

a. b. c. d. e. f.
Click Add to create the first machine. In the Name field, enter a name for the machine. In the Node manager listen address field, enter the host, or IP address of the node manager. In the Node manager listen port, enter the port number for the node manager. Create further machines as required on your Network Integrity deployment. Click Next. The Target Deployments to Clusters or Servers screen appears.
Select the Unix Machine tab, and do the following:

a. b. c. d.
Click Add to create the first UNIX machine. If required, select Post bind GID enabled. The default state is unselected. In the Post bind GID field, enter a value or select the default. In the Post bind UID field, enter a value or select the default.
e. f. g. h.
In the Node manager listen address field, enter the host, or IP address of the node manager. In the Node manager listen port field, enter the port number of the node manager. (Optional) Create further machines or UNIX machines as required on your Network Integrity deployment. Click Next. The Target Deployments to Clusters or Servers screen appears.
21. Select servers in the left pane, and click Select All to select all of the applications
and libraries listed in the right pane to target them to the selected clusters or servers.
22. Click Next.
The Target Services to Clusters or Servers screen appears.

23. Select servers in the left pane, and click Select All to select all of the services listed
in the right pane to target them to the selected clusters or servers.

24. Click Next.
The Configuration Summary screen appears.

25. Review the summary to verify the contents of your domain.
Click Previous to return to prior screens to modify their content.

26. Click Create to create the domain. 27. To finish the domain creation process, click Done, after the domain is created
successfully.
28. To set memory requirements, see "Setting Memory Requirements for Network
Integrity".
29. Continue with the procedures in "Starting the Oracle WebLogic Server"
For more information on Oracle WebLogic Server Domains, see the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite 11g Release 1 (11.1.1). 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 example shows the entries in the setDomainEnv.sh file for setting the memory requirement values for Network Integrity:
1. 2.
In the WebLogic domain bin folder, open the setDomainEnv.sh file. Set the memory arguments for your JVM as follows:
For a 64 bit OS:

WLS_MEM_ARGS_64BIT="-Xms20g -Xmx20g"
For a 32 bit OS:

WLS_MEM_ARGS_32BIT="-Xms3g -Xmx3g"
3.
Set Perm size as:
For a 64 bit OS:

MEM_PERM_SIZE_64BIT="-XX:PermSize=1024m" MEM_MAX_PERM_SIZE_64BIT="-XX:MaxPermSize=1024m"
For a 32 bit OS:

MEM_PERM_SIZE_32BIT="-XX:PermSize=1024m" MEM_MAX_PERM_SIZE_32BIT="-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.
Configuring Automatic Service Migration (ASM) on the WebLogic Server

WebLogic servers 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. Please 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. 2.
Configured Managed Servers and the Node Manager. Configure the Migration Leasing Basis as follows:
a. b. c. d.
Select the cluster where you are planning Auto JMS Service migration and select the Migration tab. Add all machines to Candidate Machines For Migratable Servers. Select the Migration Basis as Consensus. Save the changes and activate.
3.
Configure migratable targets as follows:

a. b.
Select the migratable target and select the Migration tab Select Auto-Migrate Exactly-Once Services as Service Migration Policy.
c. d. 4. 5.
Add all Constrained Candidate Servers available. Repeat these steps for each migratable target associated with member servers in the cluster.
Continue with installing Network Integrity. Once Network Integrity is installed, you can verify whether the environment is ready for JMS Service Auto Migration by following these steps:
a. b. c.
Select servers and navigate to the Migration tab All member servers are selected in the JMS Service Candidate Servers list 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. 4.
Select the Control tab to display it. If the WebLogic Administration server has migrated, then, in the Migratable Targets table, the ServerName in the Current Hosting Server column is the same as the corresponding ServerName in the Name column. In case the servers names showing in the two columns are different, do the following:
a.
5.
Select the checkbox corresponding to the ServerName, and click Migrate. The Migrate Migratable Targets screen appears.
b.
From the New hosting server list, select the name of the hosting server and click OK. The server is migrated.
Setting Up Network Integrity on a Server Cluster

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 together as one unit, rather than as several independent processing units. This is the configuration Oracle recommends because it provides protection in the event that a server fails. When working with a cluster, install the Cartridge Management Web Services (CMWS) and Network Integrity adapters on the machine 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 the Oracle Communications Network Integrity System Administrators 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 machines 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 the values in Table 33 and Figure 31, "Servers in a Sample Cluster" to set up the cluster arrangement.
Table 33 Server Cluster Example Values Values WL_Home DOMAIN_Home directory Domain login Domain password Cluster DNS
Home/
WL_Home/user_projects/domains/networkintegritycluster
weblogic networkintegritycluster NetworkIntegrityClusterDNS (It includes the networkintegrity01 and networkintegrity02 listening IP addresses.)
Table 34
Servers in a Sample Cluster Administration Server Cluster-managed Server #1 networkintegrity01 XX.XX.XX.XX:8065 NETINT2 Cluster-managed Server #2 networkintegrity02 XX.XX.XX.XX:8066 NETINT3
WebLogic server Listening port Machine
networkintegrityAdmin XX.XX.XX.XX:8063 NETINT1
Figure 31, "Servers in a Sample Cluster" also shows the servers in a sample server cluster.
Figure 31 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 machine that hosts multiple cluster-managed servers must be multi-homed. All cluster-managed servers must reside in the same subnet for multicast traffic. See below. Multicast is used for the following: 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 will 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 11g 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 Oracle WebLogic Server and Network Integrity in a Clustered Environment

Install WebLogic on the shared disk storage by following the procedures in "Installing and Configuring Oracle WebLogic Server", except the procedure to create a domain. After you install WebLogic:

Create a domain Start the WebLogic server Install Network Integrity
Creating a Domain
To create a domain:
1.
Go to WL_Home/weblogic10.3/common/bin and run the WebLogic domain configuration script. Enter:

./config.sh
The Welcome screen appears.

2.
Select Create a new WebLogic domain and click Next. The Select Domain Source screen appears.
3.
Select the Generate a domain configured automatically to support the following products: option, and from the provided list, select the following products:
Oracle Enterprise Manager - 11.1.1.0 [oracle_common]
Note:
Selecting this option will select the following two options automatically.
Oracle JRF - 11.1.1.0 [oracle_common]
The Specify Domain Name and Location screen appears.

4.
Do the following:
a. b.
In the Domain name field, enter an appropriate domain name as per your requirements or standards. In the Domain location field, enter the path and directory where the domain files will be created. For example:
WL_Home/user_projects/domains/base_domains
c. d.
In the Application location field, enter the path where the application will be saved. Click Next. The Configure Administrator User Name and Password screen appears.
5.
Do the following:
a. b.
In the User name field, enter the administrator user name. In the User 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, re-enter your password. (Optional) In the Description field, enter information about the administrator. For example: This user is the default administrator.
c. d.
e.
Click Next. The Configure Server Start Mode and JDK screen appears.
6.
In the WebLogic Domain Startup Mode section, select one of the following:

Development Mode, or Production Mode
7.
In the Available JDKs section, select the required JDK. Oracle recommends the Sun JDK for development mode, and JRockit for production mode:

Sun JDK 1.6.0._18 Sun JDK 1.6.0._20 JRockit4.0.0-1.6.0
8.
Click Other JDK to browse to the location of another JDK and click Next.
Note:
Ensure that this JDK is supported. See the chapter Network Integrity System Requirements.
The Select Optional Configuration screen appears.

9.
Select the following:
Administration Server Managed Servers, Clusters and Machines Deployments and Services
10. Click Next.
The Configure the Administration Server screen appears.

11. Do the following: a. b.
In the Name field, enter your Administration Server name. In the Listen Address field, select a DNS or an IP address.
Note:
c. d. e.
In the Listen Port field, accept the default. In the SSL Listen Port field, enter a port that is not used by another domain. Select SSL enabled if you are enabling SSL It is not a requirement to either enable or disable SSL.
f.
Click Next. The Configure Managed Servers screen appears.
12. Do the following: a. b. c.
Click Add to add a managed server to the cluster. In the Name field, enter a name for the managed server. In the Listen address field, enter the host, or IP address of the machine where the managed server is running.
Note:
d. e. f. g. h.
In the Listen port field, enter the number of the port where the managed server will listen for incoming messages. In the SSL listen port field, enter the appropriate value only if SSL is selected. Select SSL enabled as required. (Optional) Click Add to add more managed servers as required on your Network Integrity deployment. Click Next The Configure Clusters screen appears.
13. Do the following: a. b.
Click Add to start configuring the cluster. In the Name field, enter the name for the cluster.
c. d. e. f.
In the Cluster messaging mode field, provide information about the messaging type to use in the cluster. In the Multicast address field, provide the multicast address that the cluster members use to communicate with each other. In the Multicast port field, provide the multicast port (between 1 and 65535) that the cluster members use to communicate with each other. In the Cluster address field, provide the cluster address information. The cluster address contains each managed server along with the managed servers port separated by a comma. Separate the managed server and the port number by a colon.
g.
Click Next. The Assign Servers to Clusters screen appears.
14. Assign the servers to the cluster by moving the managed servers in the left pane to
the required cluster in the right pane.

15. Click Next.
The Configure Machines screen appears. Use this screen to change the configuration information for the machines. A machine 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 machine definition to start remote servers.
16. (Optional) Add the machines by carrying out one of the following options:
Select the Machine tab, and do the following:

a. b. c. d. e. f.
Click Add to create the first machine. In the Name field, enter a name for the machine. In the Node manager listen address field, enter the host, or IP address of the node manager. In the Node manager listen port, enter the port number for the node manager. Create further machines as required on your Network Integrity deployment. Click Next. The Target Deployments to Clusters or Servers screen appears.
Select the Unix Machine tab, and do the following:

a. b. c. d. e. f.
Click Add to create the first UNIX machine. If required, select Post bind GID enabled. The default state is unselected. In the Post bind GID field, enter a value or select the default. In the Post bind UID field, enter a value or select the default. In the Node manager listen address field, enter the host, or IP address of the node manager. In the Node manager listen port field, enter the port number of the node manager.
g. h.
(Optional) Create further machines or UNIX machines as required on your Network Integrity deployment. Click Next. The Target Deployments to Clusters or Servers screen appears.
17. Select clusters or servers in the left pane, and click Select All to select all of the
applications in the right pane to target them to the selected clusters or servers.
18. Click Next.
The Target Services to Clusters or Servers screen appears.

19. Select clusters or servers in the left pane, and click Select All to select all of the
services in the right pane to target them to the selected clusters or servers.
20. Click Next.
The Configuration Summary screen appears.

21. Review the summary to verify the contents of your domain. Click Previous to
return to prior screens to modify their content.

22. Click Create to create the domain. 23. After the domain is created successfully, click Done. 24. Continue with the procedures in "Starting the Oracle WebLogic Server".
For more information on configuring managed cluster servers, see Configuring Managed Cluster Servers. You can now log in to the Administration console and start the Administration Server manually.
Note:
Create domains for remote machine in the same manner, in the respective machines.
Starting the Oracle WebLogic Server

To start the WebLogic server:
1. 2.
Open a command window. Go to the DOMAIN_Home 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:
a.
Go to:
http://ServerName:Port/console
where ServerName is the name of the Administration Server machine and Port is the Administration Server port number.
b. c.
Enter the WebLogic server administration user name and password. In the Domain Structure tree, expand Environment, and click Servers.
The Summary of Servers screen appears.

d.
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 RUNNING Server 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.
To start the cluster member servers:

1. 2. 3.
Log in to the first cluster server machine. Go to the DOMAIN_Home/BIN directory. Start the cluster server using the following command executed from the machine where the managed server is defined:
./startManagedWebLogic.sh cluster_server_name admin_server_URL
4.
Start the second server by using the following command executed from the machine where the managed server is defined:
./startManagedWebLogic.sh cluster_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 networkintegrity01.log tail -f networkintegrity02.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. 8.
Log in to the WebLogic console to check all of the cluster server states. Go to:
http://ServerName:Port/console
where ServerName is the name of the Administration Server machine and Port is the Administration Server port number.
Installing and Configuring Additional Third-Party Software
9.
Enter the WebLogic server administration user name and password. encounter
10. Select Servers and verify that the State of all servers is RUNNING. If you
Note:
To configure the Node Manager, see the Oracle WebLogic documentation on the Oracle Technology Network located at: http://www.oracle.com/technology
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 configurable 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. 2. 3. 4. 5. 6.
Log in to the WebLogic Administration console. In the Home page, select Environment. Select Servers, and then click Admin Server. Select Configuration, and then click Tuning. Increase the value of Stuck Thread Max Time: to 3600. Restart your domain. Your changes will take effect only after a restart.

Install the following third party software to enhance Network Integrity performance, post installation:

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 Oracle Fusion Middleware Securing Oracle WebLogic Server 11g Release 1 (10.3.1) 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.
Note:
The use of Oracle Internet Directory requires a separate license from Network Integrity; please contact your Oracle representative for information on acquiring a license.
You require the following information to install the Oracle Internet Directory:
A static IP address You require a static IP address in order to install the IDM 11g suite.
Oracle Database 11g WebLogic server 10.3.2 Application Development Runtime Identity Management 11g Fusion Middleware Patchset1
For information on installing Oracle Internet Directory, see Installing and Configuring Oracle Internet Directory at the Oracle Technology Network.
Configuring The Authentication Provider

To enable the WebLogic Server to work with an external LDAP store, or Oracle Internet Directory:
1. 2.
Log in to the Administration console. Under Your Applications Security Settings, click Security Realms. The Summary of Security Realms screen appears.
3.
Select the realm YourRealmName, for which you need to set the Oracle Internet Directory as the external LDAP store. The Settings For YourRealmName screen appears.
4. 5.
Click the Providers tab, and in the Providers tab, click the Authentication tab. Click New. The Create a New Authentication Provider screen appears.
6. 7. 8.
In the Name field, enter the name of the authenticator, AuthenticatorName. From the Type list, select OracleInternetDirectoryAuthenticator. 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.
You now need to reorder the authentication providers.

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 the following users in the new authentication provider store:

JDUser (this is a member of the JDGroup), and NIUSER (this is a member of NetworkIntegrityRole and JDGroup)
Note:
Ensure that you create the groups and users in the default security realm.
Installing and Configuring Oracle BI Publisher 10g

Note:
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.
Note:
The use of Oracle BI Publisher requires a separate license from Network Integrity; please contact your Oracle representative for information on acquiring a license.
Download BI Publisher 10g from the Oracle Technology Network. For information on installing and configuring, see BI Publisher documentation.
4
4
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 Network Integrity Pre-Installation Tasks
Types of Installation
There are two types of Network Integrity installation:

Complete installation. See "Installing Network Integrity in the GUI Mode". Installation in silent mode. See "Installing Network Integrity in Silent Mode".
Caution: In the event that the installation fails for some reason, you are required to create a new WebLogic domain and a new database user before you begin installation again.
See "Network Integrity Pre-Installation Tasks".
Caution: The Network Integrity Installer must be launched from the same machine as the one hosting the Administration server of your domain.
Installing Network Integrity in the GUI Mode

To install Network Integrity in the GUI mode, using the Installer:
1. 2.
Create a temporary directory (temp_dir). Download the software pack for your operating system from the Oracle E-Delivery Web site at https://edelivery.oracle.com and save it to temp_ dir:

Oracle Communications Network Integrity 7.0.1 for Linux (including Red Hat) Oracle Communications Network Integrity 7.0.1 for Solaris Oracle Communications Network Integrity 7.0.1 for IBM AIX
3.
Unzip the software pack in a folder of your choice using the following command:
Installing Network Integrity 4-1
#unzip software_pack.zip
The file unzips into the following: # unzip software_pack.zip Archive: software_pack.zip Inflating: NetworkIntegrity-7.0.1.0.0-Operating_System.zip
4.
Unzip the file NetworkIntegrity-7.0.1.0.0-Operating_System.zip The following folder structure is created: ni/Disk1/install/
5.
Run the Oracle Universal Installer (OUI) executable file runInstaller using the following command:
>./runInstaller
The Welcome screen of the OUI installation wizard appears.

6.
Click Next. The Select Installation Type screen appears.

Note:
The OUI creates an Inventory directory if it does not detect any installed Oracle products on the system. The Inventory directory manages all Oracle products installed on your system.
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. 9.
In the Available Product Components screen, select the components you wish to install, and click Next. In the Specify Home Details screen, do the following:
a. b.
In the Name field, enter an appropriate name for the folder that will contain all of the installation files. In the Path field, enter the path to the folder where you wish to install Network Integrity.
Note:
You can also select the name for the installation from the list of names the Oracle Universal Installer provides. You can also browse for the path where Network Integrity will be installed from the provided list using the explorer GUI.
c.
Click Next.
The WebLogic Administration Server Connection Information screen appears.

10. Do the following:
a. b. c.
In the Host Name field, enter the IP address or the host name of the host machine. In the Port Number field, enter the Administration server port number. In the User Name field, enter user name with which you connected to the Administration Server.
Note:
This user should belong to the WebLogic Administrators
group.
d. e.
In the Password field, enter the password for the user name that you provided in the User Name field. In the WebLogic Home field, enter the path to the Weblogic.jar file that is used for deployment-related functionality.
Caution:
Ensure that WebLogic Home points to WL_ Home/server/lib/weblogic.jar.
f.
Click Next. The WebLogic Server/Cluster Selection screen appears.
11. Select the option for the server, or cluster, where you wish to deploy Network
Integrity, and click Next.
If you select Administration server, or a standalone managed server, the Database Type Selection screen appears. Skip the next step.
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 11g Enterprise Database option. The Database Connection Information screen appears. Do the following:
a. b. c.
In the Host Name field, enter the IP address or the host name of the machine where the database server is installed. In the Port Number field, enter the port number with which the installer will connect to the database server. In the User Name field, enter the user name for the database server.
d. e. f.
In the Password field, enter the password for the user name that you provided in the User Name field. In the Service name field, enter the service name that uniquely identifies your database on the system. Click Next. The Network Integrity Schema User Information screen appears.
Select the Oracle 11g Real Application Cluster Database option. The RAC DB Nodes Connection Information screen appears. Do the following:
a.
In the RAC Database Connection String field, enter the connection details to connect to the RAC database. For example: HOST NAME1:PORT1:SERVICE NAME1, HOST NAME2:PORT2:SERVICE NAME2
b. c. d.
In the User Name field, enter the user name for the RAC database server. In the Password field, enter the password for the user name that you provided in the User Name field. 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 schema.
Caution: Ensure that you use the same user name and password here that you had used during the MetaData schema creation.
a. b. c.
In the Schema User Name field, enter a name for the schema user. In the Schema User Password field, enter the password for the schema user to access the schema. 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:
a. b. c. d. e. f. g.
In the LDAP Server Host Name field, enter the host name for the external LDAP server. In the LDAP Server Port Number field, enter the port number for the external LDAP server. In the LDAP Server User Name field, enter the user name for the external LDAP server. In the LDAP Server Password field, enter the password for the external LDAP server. In the User Base DN field, enter the user base DN. In the Group Base DN field, enter the group base DN. Click Next. The Network Integrity User Information (Optional) screen appears.
If you select Other Security Provider, and click Next, the Reporting Tool Connection (Optional) screen appears. Skip the next step.
16. In the Network Integrity User Information (Optional) screen, do the following: a.
In the Network Integrity User name field, enter the user name for the Network Integrity user. This user accesses and uses Network Integrity.
b.
In the Network Integrity Password field, define a password for the Network Integrity user.
Note:
The Network Integrity user password can be a maximum of 12 letters long, and should contain at least one numeric value, 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.
c.
Click Next. The Reporting Tool Connection (Optional) screen appears.
17. In the Reporting Tool Connection (Optional) screen, 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.

18. Select whether or not you wish to launch Cartridge Deployer, and click Next.
Installing Network Integrity in Silent Mode
Note:
This is an optional screen that only appears for systems installed on the Linux or Solaris operating systems. Clicking Next will take you to the next screen if you do not wish to make this choice now.
Selecting Yes will launch the Cartridge Deployer Tool after the successful installation of Network Integrity. The Summary screen appears.
19. Review the selections you have made in the preceding screens, and click Install.
The Install screen appears.

20. You can view the installation progress.
On successful installation of Network Integrity, the End of Installation screen appears.

Note:
Note down the provided URLs. You use these URLs to access Network Integrity.
21. At the end of a successful installation, the installer shuts down all target servers
and displays the following warning message: Target servers ServerName will be shut down now. Please select OK to continue. Click OK. The following warning message is displayed: All target servers were shut down. Please start the servers in this order Server1Name, Server2Name, ... other member servers of cluster ClusterName manually to access the application.
22. Make a note of the order in which the servers are mentioned in the displayed
warning message and click OK.

23. Start all servers manually in the order mentioned in the previous warning
message. You can now access the Network Integrity application. For information on verifying the successful installation of Network Integrity, see "Verifying the Network Integrity Installation".

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: ni/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
Here path is the response file location.
Manually populating the response file To populate the response file manually:
1.
Go to the following location: ni/Disk1/stage/Response
2. 3.
Open the appropriate .rsp template and make a copy for your current requirement. 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
The installation will run 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: InstallLocation/install/readme.txt For example: /opt/ni/Oraclecommunications/install/readme.txt
3.
Copy the URL and paste it in the browser windows 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".
5
5
Network Integrity Post-Installation Tasks

This chapter provides instructions for Oracle Communications Network Integrity post-installation tasks. You must install Network Integrity before following these procedures. See "Installing Network Integrity".
Overview of Network Integrity Post-Installation Tasks

Post-installation tasks for Network Integrity include:

Managing Network Integrity Cartridges Enabling Cache Coordination in Remote Servers Configuring Network Integrity for Inventory Management Installing Network Integrity Report Templates Starting the AgeOut Process
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, as per your individual requirements, if you are using some other certificate. For information about configuring SSL for Network Integrity, see Network Integrity System Administrators 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. You can manage cartridges in the following ways:
Network Integrity Post-Installation Tasks 5-1
Using the Cartridge Deployer Tool Writing a custom application
Managing Network Integrity Cartridges with the Cartridge Deployer Tool

You use the Cartridge Deployer Tool to deploy and manage cartridges in Network Integrity. 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.
Note:
Ensure that you are logged out of the Administration Server before you start deploying cartridges.
Caution: Before you start deploying or undeploying cartridges using the Cartridge Deployer Tool, ensure that the WebLogic administration console is not locked for editing.
Deploying Cartridges
To deploy the required cartridges:
1. 2.
From the folder where Network Integrity is installed, go to the CartridgeDeployer folder. Run the Cartridge Deployer Tool executable by running 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. The current release of Network Integrity only 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. To add Deploy property or Model property, under Details for that cartridge, right-click Properties and select the respective options for related menus.
Note:
The WebLogic Connection Information screen appears.

8.
Do the following:
a. b. c.
In the Host name or IP address field, enter the host name or IP address of the WebLogic Administration Server. In the Port number field, enter the port number of the WebLogic Administration Server. 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. CMWS is Cartridge Management Web Service. CMWS user is a WebLogic server user belonging to the administrators group.
d.
In the Password field, enter the password for the CMWS user.
Note:
Use your WebLogic administrator user name and password
here.
e.
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 the Use SSL... option selected, see the Oracle Communications System Administrators Guide.
11. Click Next.
The Review Deployment screen appears.

12. Review and confirm your selections, and click Next.
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.
13. Click Start Deployment.
You can view the deployment progress. Logs returned by the adapter are displayed at the end of 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.
Undeploying Cartridges
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 cartrdige are deleted.
To undeploy a cartridge:
1.
In the NetworkIntegrity_Home, access the following folder: /CartridgeDeployer
2.
Run the Cartridge Deployer Tool executable by running the following command:

3.
Select the UnDeploy Cartridge 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:
a. b. c.
Note:
d.
Note:
here.
e.
Click Next.

6.
Select the WebLogic targets where the cartridges you wish 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.
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 the Use SSL... option selected, see the Oracle Communications System Administrators 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.
Select the cartridges to undeploy, and click Next.

Note:
To add an undeployment property, right-click the cartridge and select the required option.
The Review Undeployment screen appears.

10. 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 at the end of each cartridge operation irrespective of its success. For more information about managing cartridges, see Modeling Network Integrity, which is part of the Oracle Communications Design Studio online Help. For information about deploying cartridges using Design Studio, see Modeling Network Integrity, which is part of the Studio online 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/Undeploying Cartridges on/from 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 machine where the Administration server is running.
2. 3. 4.
In the remote server, deploy, or undeploy, cartridges using steps provided in the sections "Deploying Cartridges" and "Undeploying Cartridges". Copy the NetworkIntegrity.ear file from remote managed server back to the administration server. Update the NetworkIntegrity.ear file. The cartridges are deployed on, or undeployed from, the remote managed server.
Viewing Cartridges
To view deployed cartridges:
1.
In the NetworkIntegrity_Home, access the following folder: /CartridgeDeployer
2.
Run the Cartridge Deployer Tool executable by running the following command:

3.
Select the View Deployed 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:
a. b. c.
Note:
d.
Note:
here.
e.
Click Next.

6.
Select the WebLogic targets where the Cartridge Management Web Service 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.
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 the Use SSL... option selected, see Network Integrity System Administrators 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 Modeling Network Integrity, which is part of 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.
Developing a Custom Java Application

Refer to CartridgeDeployer/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. 2. 3.
Open Oracle Communications Design Studio in the Java perspective. Import all the JAR files from the NI_Home/CartridgeDeployer/lib/ directory, where NI_Home is the location where Network Integrity is installed. Inside the CMWSClient.jar/ directory, create a Java file to develop the Java classes that are required to implement cartridge management operations by doing all of the following:
a.
To deploy cartridges, create an oracle.communications.platform.cartridgemanagement.client.cbo.Cartridge object with the following class attributes: name version buildId type deploy properties
b.
Call the deployCartridge() operation on the cartridge manager objects with the following arguments: webServiceUrl

c.
keystore_location cmwUserName password cartridge_object pollwait pollcount
To undeploy cartridges, create an oracle.communications.platform.cartridgemanagement.client.cbo.Cartridge object with the following class attributes: name version type undeploy properties
d.
Call the unDeployCartridge() operation on the cartridge manager objects with the following arguments: webServiceUrl keystore_location cmwUserName password cartridge_object pollwait pollcount
e.
To list available cartridges of a specific type, call the getInstalledCartridges() operation on the cartridge manager object with the following arguments: webServiceUrl keystore_location cmwUserName password type
f.
To list installed cartridges of a specific type, create an oracle.communications.platform.cartridgemanagement.client.cbo.Cartridge object with the following class attributes: name version type
g.
Call the cartridgeExist() operation on the cartridge manager objects with the following arguments: webServiceUrl keystore_location
cmwUserName password cartridge_object comparisonOperator
Developing Custom ANT Tasks

Refer to CartridgeDeployer/tools/sample-build.xml for an example custom ANT script, containing example syntax and sample operations. Refer to CartridgeDeployer/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. 2. 3. 4.
Open Design Studio in the XML perspective. Import all the JAR files from the NI_Home/CartridgeDeployer/lib/ directory, where NI_Home is the location where Network Integrity is installed. Import NI_Home/CartridgeDeployer/tools/cartridge-management-tools.jar. Inside the cartridge-management-tools.jar/ directory, create an XML file that implements cartridge management operations:
<taskdef name="deploy" classname="oracle.communications.sce.cartridgemanagement.ws.tools.DeployCartrid ge" classpathref="class.path"/> <taskdef name="undeploy" classname="oracle.communications.sce.cartridgemanagement.ws.tools.UndeployCartr idge" 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.CartridgeExis t" classpathref="class.path"/>
5.
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}" sslKeyStore="${sslKeyStore}" fileLocation="${fileLocation}" target="${target}" property="deployresponse"/> <echo message="Message from cartridge deploy task : ${deployresponse}"/> </target>
For the undeploy task:

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

<target name="list"> <echo message="Listing cartridge..."/> <list host="${host}" port="${port}" username="${username}" password="${password}" sslKeyStore="${sslKeyStore}" cartridgeType="${cartridgeType}" target="${target}" property="listval"/> <echo message="Message from cartridge list task : ${listval}"/> </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}" sslKeyStore="${sslKeyStore}" cartridgeName="${cartridgeName}" cartridgeVersion="${cartridgeVersion}" cartridgeType="${cartridgeType}" target="${target}" property="existval"/> <echo message="Message from cartridge exist task : ${existval}"/> </target>
6.
Inside the cartridge-management-tools.jar/ directory, create an XML properties file to automate the ANT tasks:
ant ant ant ant -lib -lib -lib -lib ../lib ../lib ../lib ../lib -f -f -f -f sample-build.xml sample-build.xml sample-build.xml sample-build.xml deploy undeploy list exist
Where /lib refers to where the dependent JAR files are stored.
Running Cartridge Operations From a Command Line

To use a command line interface to run cartridge operations:
1. 2. 3.
Open a system console command line or connect to the Network Integrity server using a remote client. Set the Java path, as it is explained in your JDK documentation. 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 51 lists all the arguments used at the command line for managing cartridge operations.
Table 51
Valid Arguments for Command Line Cartridge Management Description The admin host name where the cartridge manager Web service (CMWS) is deployed. A valid port number to the admin server. A valid endpoint URL to the CMWS. A CMWS user. 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. A valid keystore location for SSL connection. The cartridge type. When deploying multiple cartridges, -type must be set to NetworkIntegrity. The cartridge operation to be performed. Possible values are: deploy, undeploy, list, and exist. A path to a single cartridge, or a comma separated list of paths to multiple cartridges. The target server. A single cartridge name, or a comma-separated list of cartridge names for multiple cartridges. Only the undeploy operation can accept multiple names. A single cartridge version, or a comma-separated list of cartridge versions for multiple cartridges. Only the undeploy operation can accept multiple versions. Display the help message.
Valid Argument -host -port -url -user -password
-keystore -type -operation -location -target -name
-version
-help
Table 52 lists the commands for managing cartridge operations, with their mandatory and valid arguments.
Table 52 Command deploy Valid Arguments for Each Cartridge Command Description 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 deploy a single cartridge, enter a command similar to the example below:

* java -Djava.util.logging.config.file=logger.conf -jar cartridge-management-tools.jar -operation deploy -host admin_host -port admin_port -user cmws_user -password cmws_password -type cartridge_type -target target_name_ where_cmws_deployed -location cartridge_path
To deploy multiple cartridges, enter a command similar to the example below:

* java -Djava.util.logging.config.file=logger.conf -jar cartridge-management-tools.jar -operation deploy -host admin_host -port admin_port -user cmws_user -password cmws_password -type NetworkIntegrity -target target_ name_where_cmws_deployed -location cartridge_1_path, cartridge_2_path, cartridge_ n_path
To undeploy a single cartridge, enter a command similar to the example below:

* java -Djava.util.logging.config.file=logger.conf -jar cartridge-management-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 undeploy multiple cartridges, enter a command similar to the example below:

* java -Djava.util.logging.config.file=logger.conf -jar cartridge-management-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_1_name, cartridge_2_name, cartridge_n_ name -version cartridge_1_version, cartridge_2_version, cartridge_n_version
To list deployed cartridges, enter a command similar to the example below:

* java -Djava.util.logging.config.file=logger.conf -jar cartridge-management-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 list available, undeployed cartridges, enter a command similar to the example below:
* java -Djava.util.logging.config.file=logger.conf -jar cartridge-management-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 display the help message, enter a command similar to the example below:
* java -jar cartridge-management-tools.jar -help
Migrating Cartridges
If you developed or extended cartridges for a previous version of Network Integrity, you will want to migrate them to the current version of Network Integrity so that you can continue to use them. The supported migration path is from version 7.0.0 to 7.0.1.
Note:
It is not possible to migrate scan instances or scan data. Scan instances have to be manually recreated in Design Studio. Scan data is recreated when you run a scan.
Follow the correct procedure for each of your cartridges:

Migrating Network Integrity Production Cartridges Migrating Network Integrity Sample and Custom Cartridges
Migrating Network Integrity Production Cartridges

Production cartridges (cartridges with binaries supplied by Oracle) are already compatible with the latest version of Network Integrity. Deploy the cartridge into the latest installation of Network Integrity. See "Managing Network Integrity Cartridges with the Cartridge Deployer Tool" for more information.
Migrating Network Integrity Sample and Custom Cartridges

Sample and custom cartridges (cartridges with binaries not supplied by Oracle) must be migrated to the latest version of Network Integrity. This section assumes that you have two Design Studio environments: one for Network Integrity 7.0.0 and another for 7.0.1.
Note: Ensure that Design Studio for Network Integrity 7.0.1 is up to date with the correct plug-ins. See Oracle Communications Design Studio Installation Guide for more information.
To migrate the cartridge:

1.
Using the old installation of Design Studio for Network Integrity, do the following:
a. b. c. d. e. f. g.
Select the Design Studio perspective. Select the Cartridge view. Select the cartridge project and, from the Project menu, deseselect Build Automatically. From the Project menu, select Clean. Select the Navigation view. Delete all files and folders from the integrityLib directory. Right-click the cartridge project folder and select Close Project.
2.
Using the new installation of Design Studio for Network Integrity, do the following:
a. b. c.
Select the Design Studio perspective. Select the Cartridge view. Right-click anywhere in the Cartridge view and select Import. The Import Project dialog box appears.
d.
Locate the cartridge project and import it.

Note:
Design Studio will automatically populate the integrityLib directory in the cartridge project with new files.
e.
Double-click the cartridge project folder. The cartridge properties appear.
Enabling Cache Coordination in Remote Servers
f.
Enter the text 7.0.1 in the Target Version field.

Note:
If the Target Version field is not editable, it may mean that the cartridge is sealed, read-only, or under source control.
g. h.
Using Windows Explorer, navigate to the cartridge directory. Open the .classpath file and delete all entries that contain the text kind="lib" path="generated. Design Studio will generate new entries in the file when the project is built.
Note:
If the .classpath file is read-only, it may mean that it is under source control.
i. j. k.
Perform all necessary pre-build steps particular to your cartridge. From the Project menu, enable Build Automatically. From the Project menu, select Clean. The cartridge project is automatically built. The binary file is produced and written to the cartridgeBin directory.
l.
Deploy the cartridge to your Network Integrity system. See "Managing Network Integrity Cartridges with the Cartridge Deployer Tool" for more information.

Note:
You are not required to follow the procedure to place the cache coordination property file on remote servers, described in this section, if you are using a shared file system.
When your Network Integrity system runs on multiple machines, across networks, you must configure each remote server so that it holds only valid data in its respective cache to ensure that the data is not duplicated in any of the other remote servers cache. Failing to do so could lead to errors each time the database updates its records, synchronizing data across servers. During installation, the Network Integrity Installer creates two files as a set of property key value pair, enabling cache coordination within the servers. The application itself utilizes one of these files. The other file is utilized by the Job Dispatcher, a component within the application, for the same purpose. The two files are located in two different directories; commsplatform and ni. Since the Network Integrity Installer is run from the same machine that runs the Administration server, these directories are created in the DOMAIN_Home/ of the Administration server only. For any remote servers, you must manually copy and place these directories in the DOMAIN_Home/ of the respective servers, to enable cache coordination between these remote servers/nodes. To copy and place the two directories to a remote managed server:
1. 2.
Go to the Domain home location of the machine where Network Integrity is running and copy the directories. Paste the directories in the remote managed server using the following command:
scp -r commsplatform ni USER_NAME@IP:FULL_DOMAIN_LOCATION
In this command:

USER_NAME is the admin user name used to log into the machine. IP is the IP address of that machine. FULL_DOMAIN_LOCATION is the location where the Network Integrity domain is created.
3. 4.
Enter the admin password for that machine when prompted. Update the jobdispatcher.ear file as follows:
a. b. c. d. e.
Log in to the Administration console using the administrator user name and password. Click Lock and edit. Click Deployments in the left panel. In the Deployments table, select jobdispatcher. Click Update. The Update Application Assistant screen appears.
f.
Select Redeploy this application using the following deployment files, ensure that the source and Deployment plan paths are correct, and click Finish. Click Activate Changes.
g. 5.
Repeat the same procedure for the networkintegrity.ear file.
After you have copied the two directories, update the Network Integrity and Job Dispatcher deployments. To update the Network Integrity and Job Dispatcher deployments:
1.
Log on to the Oracle WebLogic Administration Server Console. The Home screen of the Administration Console appears.
2.
Select Deployments. The Summary of Deployments screen appears. The Control tab is displayed by default.
3.
In the Deployments table, select the checkbox corresponding to NetworkIntegrity and click Update. The Update Application Assistant screen appears.
4. 5. 6. 7.
Select Update this application in place with new deployment plan changes. (A deployment plan must be specified for this option). Click Next. Review you selection(s). Click Finish.
Installing Network Integrity Report Templates
Network Integrity is updated.

8. 9.
In the same manner, update Job Dispatcher in the Deployments table. Start Network Integrity.
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 need to 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 cartridge or technology pack 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. 2.
Open the BI Publisher application and click the Admin tab. 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:

Starting the AgeOut Process
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. 6. 7. 8.
Click Test Connection. When a message confirming that the connection is successfully established appears, click Apply to save the connection details. Go to the BI Publisher Home page. 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.

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. You can start the AgeOut process using the following tools:
Enterprise Manager
Java Monitoring & Management Console (JConsole)

Note:
To use Oracle Enterprise Manager or JConsole to start the AgeOut process, you required your WebLogic credentials.
Starting the AgeOut Process Using Oracle Enterprise Manager

To start the AgeOut process using Oracle Enterprise Manager:
1.
Log in to Oracle Enterprise Manager using your WebLogic credentials, at the following URL: http://Admin_Server_IP:Admin_Port/em
2. 3. 4.
Click WebLogic Domain. In the tree view, click Server_Name or Cluster_Name/Server_Name. Right-click System Mbean Browser. The MBean browser opens.
5. 6. 7. 8. 9.
Click the Application Defined Mbeans node. Click oracle.communications.integrity, and then click Server: Server_Name. Click oracle.communications.integrity.ResourceProviderMXBean, and then click NIConfigurationService. Click operations, and then click startAgeOutProcess. Enter values for startDate and recurrenceRule. For example: startDate=2011-02-28 16:45:50 GMT; recurrenceRule=FREQ=DAILY;BYHOUR=16;BYMINUTE=45;BYSECOND=50;
10. Click Invoke.
Starting the AgeOut Process Using JConsole

For more information about using JConsole in Network Integrity, see Network Integrity System Administrators Guide. To start the AgeOut process using JConsole:
1. 2. 3. 4. 5.
Start JConsole using the steps for starting the JConsole in Network Integrity System Administrators Guide, and using your WebLogic credentials. In the tree view, click oracle.communications.integrity, and then click NIConfigurationService. Click Operations, and then click startAgeOutProcess. Click oracle.communications.integrity.ResourceProviderMXBean. Enter values for startDate and recurrenceRule. For example: startDate=2011-02-28 16:45:50 GMT; recurrenceRule=FREQ=DAILY;BYHOUR=16;BYMINUTE=45;BYSECOND=50;
6.
Click StartAgeOutProcess.
6
6
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. 2.
Log in to the WebLogic Administration Server. In the left panel, in the Domain Structure section, click Deployments. The Summary of Deployments page appears.
3. 4.
Ensure that all of the managed servers are running. If Network Integrity is installed successfully, the following deployments appear in the Active state:

ESSAPP JobDispatcher NetworkIntegrity NICMWSAdapter SNMPAdapter 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. 2. 3.
Open a browser window. Enter the URL as provided by the Installer at the end of the installation. Click Go, or press the Enter key. The Network Integrity login page appears.
4.
Do the following:
a.
Enter the user name, in the User Name field.
Verifying the Network Integrity Installation
6-1
Logging In to Network Integrity
b.
Enter the password in the Password field.
The Network Integrity home page appears, verifying that Network Integrity is installed successfully.
7
7
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: ni/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. 5.
Select the item(s) you want to uninstall. 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 User Input screen appears again.
Uninstalling Network Integrity 7-1
Uninstalling Network Integrity Using the Silent Mode
7.
In the Network Integrity Database schema user password field, enter your Network Integrity Database schema user password, and click OK. The User Input screen appears again.
8.
In the Embedded LDAP NI user password field, enter your Embedded LDAP NI user password, and click OK. The Confirmation screen appears.
9.
View and confirm your selection, and click Next. You can see the remove progress as the selected components are uninstalled.
The installer removes all of the files except the logs. If required, delete the log files manually. The logs can be found at the following location: CentralInventorylocation/logs/
Uninstalling Network Integrity Using the Silent Mode

To uninstall Network Integrity using the silent mode:
1.
Use the following command to uninstall Network Integrity:

./runInstaller -responseFile Path -silent -deinstall
Here path is the location of the response file that was created during silent mode installation of Network Integrity.
2.
After a successful uninstall, you will get a message indicating that Network Integrity has been uninstalled successfully.

Network Integrity Installation On Linux

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Network Integrity Installation On Linux

Uploaded by

Copyright:

Available Formats

Oracle Communications Network Integrity

Installation Guide Release 7.0.1

1 Network Integrity Installation Overview

2 Network Integrity System Requirements

3 Network Integrity Pre-Installation Tasks

4 Installing Network Integrity

5 Network Integrity Post-Installation Tasks

5-13 5-14 5-14 5-15 5-17 5-17 5-18 5-19 5-19

6 Verifying the Network Integrity Installation

7 Uninstalling Network Integrity

Network Integrity Installation Overview

Overview of Network Integrity Installed Components

Network Integrity Cartridges

Overview of the Network Integrity Installation Procedure

Perform the following pre-installation tasks:

Network Integrity Installation Overview

About the Network Integrity Installer

Setting up the database Installing and configuring an Oracle database

About the Network Integrity Installer

1-2 Network Integrity Installation Guide

Ensuring a Successful Network Integrity Installation

Common Installer Services

Network Integrity Installation Options

Ensuring a Successful Network Integrity Installation

UNIX operating system Oracle WebLogic Server administration

Network Integrity Installation Overview

About Upgrading Network Integrity

Oracle Database 11gR2 administration

About Upgrading Network Integrity

1-4 Network Integrity Installation Guide

Network Integrity System Requirements

Supported Operating Systems

Additional Software Requirements

Network Integrity System Requirements 2-1

11.2 7.1.1 7.1.2 10.1.3 (10.1.3.4.1+)

Component Hard disk

2-2 Network Integrity Installation Guide

WebLogic Connection Information

Information Type Host Name

Network Integrity System Requirements 2-3

Provide an appropriate user name Provide an appropriate password

This option has no default value.

This option has no default value.

Database Connection Information

Information Type Hostname

Provide an appropriate user name Provide an appropriate password

This option has no default value.

Database Connection Information For Real Application Cluster Database

2-4 Network Integrity Installation Guide

Information Type RAC Database Connection String User name

This option has no default value.

Schema User Name Information

Information Type Schema User Name Schema User Password

Network Integrity System Requirements 2-5

2-6 Network Integrity Installation Guide

Network Integrity Pre-Installation Tasks

Overview of Pre-Installation Tasks

Installing and Configuring the Oracle Database

Network Integrity Pre-Installation Tasks 3-1

Installing and Configuring the Oracle Database

Setting the Database Time Zone

Creating the Database (MetaData) Schema for Network Integrity

To create the schema for Network Integrity using RCU: