Skip Headers
Oracle® Communications Network Integrity System Administrator's Guide
Release 7.2.2

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

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

4 Managing Network Integrity and Its Components

This chapter provides information on managing Oracle Communications Network Integrity, and Network Integrity components.

About Managing the Oracle Database Server

To manage the Oracle Database server, see the Oracle Database administrator's guide on the Oracle Technology Network Web site:

http://www.oracle.com/technology

Perform all required administration tasks for the database.

About Managing Network Integrity

This section explains how to perform various Network Integrity management tasks.

Starting Network Integrity Instances

To start a Network Integrity instance:

  1. Ensure that the server hosting Network Integrity is running.

  2. Log in to the WebLogic server Administration console using Administrator credentials.

    The Home screen appears.

  3. Click Configure applications.

    The Summary of Deployments screen appears.

  4. In the Deployments table, select the check box corresponding to the Network Integrity instance.

  5. On the Start drop-down menu, select the appropriate option.

Stopping Network Integrity Instances

To stop a Network Integrity instance:

  1. Ensure that the server hosting Network Integrity is running.

  2. Log in to the WebLogic server Administration console using Administrator credentials.

    The Home screen appears.

  3. Click Configure applications.

    The Summary of Deployments screen appears.

  4. In the Deployments table, select the check box corresponding to the Network Integrity instance.

  5. On the Stop drop-down menu, select the appropriate option.

Starting/Stopping the Reporting Tool

Note:

Before starting or stopping the reporting tool using the WebLogic Administration console, ensure that the server hosting the reporting tool is running.

To start or stop a deployed reporting tool:

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

    The Home screen appears.

  2. Select Deployments under Your Deployed Resources.

    The Summary of Deployments screen appears.

  3. In the Deployments table, select the check box corresponding to the Reporting tool.

  4. Do one of the following:

    • To start the reporting tool, click Start.

    • To stop the reporting tool, click Stop.

  5. Select the required options.

Starting/Stopping the WebLogic Administration Server

To start or stop the WebLogic server on which Network Integrity is installed:

  1. Log in to the Linux system on which Network Integrity is installed.

  2. Open the Console window.

  3. Go to the Domain_Home/bin folder

  4. Do one of the following:

    • To start the WebLogic server

      . startWebLogic.sh
      
    • To stop the WebLogic server

      . stopWebLogic.sh
      

Starting/Stopping a Managed Server

You can use the WebLogic scripting and command line tool to start or stop a Managed WebLogic server.

To start a Managed WebLogic server:

  1. Run the following script:

    MW_Home/user_projects/domains/domain_name/bin/startManagedWebLogic.sh
    managed_server_name admin_url
    

    where:

    • MW_Home is the location where Fusion Middleware products (such as WebLogic Server) are installed.

    • domain_name is the name of the domain.

    • managed_server_name is the name of the managed server being started.

    • admin_url is the URL for the managed server being started.

  2. At the prompt, provide your user name and password.

    The managed server starts.

To stop a Managed WebLogic server:

  1. Run the following script:

    MW_Home/user_projects/domains/domain_name/bin/stopManagedWebLogic.sh
    managed_server_name admin_url user_name password
    

    where:

    • MW_Home is the location where Fusion Middleware products (such as WebLogic Server) are installed.

    • domain_name is the name of the domain.

    • managed_server_name is the name of the managed server being stopped.

    • admin_url is the URL for the managed server being stopped.

  2. At the prompt, provide your user name and password.

    The managed server starts.

Adding Additional Managed Servers to a WebLogic Domain

You add additional managed servers to an existing cluster to increase the capacity and performance of your system.

Note:

If you add new member servers to an existing cluster, the new member servers inherit all applications and services targeted to that cluster.

To add a managed server to a domain:

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

    The Home screen appears.

  2. In the Change Center, click Lock & Edit.

  3. Under Environment, select Servers.

    The Summary of Servers screen appears.

    The Configuration tab is displayed by default.

  4. Click New.

    The Create a New Server screen appears.

  5. Do the following:

    1. In the Server Name field, enter a name for the new server.

    2. In the Server Listen Address field, enter the IP address of the host system.

    3. In the Server Listen Port field, enter the port number from which to access the server.

    4. Select whether this server is a member of an existing cluster.

    5. Click Next.

      The Review Choices page of the Create a New Server screen appears.

    6. Review the information and click Finish.

      The new server appears in the Servers table.

Creating a Cluster

A WebLogic server cluster is a group of multiple WebLogic servers, called member servers, working as one large server, thereby increasing the capacity, performance, and reliability of your system. The member servers can either be on the same, or different systems.

Note:

Each member server in a cluster must run the same version of WebLogic Server.

To create a cluster:

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

    The Home screen appears.

  2. In the Change Center, click Lock & Edit.

  3. Under Environment, select Clusters.

    The Summary of Clusters screen appears.

  4. Click New.

    The Create a New Cluster screen appears.

  5. Do the following:

    1. In the Name field, enter a name for the new cluster.

    2. (Optional) Select the Messaging Mode.

    3. In the Unicast Broadcast channel field, enter the channel that is used to transmit messages within the cluster.

    4. Click OK.

      The newly created cluster in the Clusters table.

      You can now add member servers to this cluster.

Adding Managed Servers to an Existing Cluster

To add a new managed server to an existing clustered environment:

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

    The Home screen appears.

  2. In the Change Center, click Lock & Edit.

  3. Under Environment, click Servers.

    The Summary of Servers page appears.

  4. Click New.

    The Create a New Server page is displayed.

  5. Do the following:

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

    2. In the Server Listen Address field, enter the IP address of the managed server to add to the cluster.

    3. In the Server Listen Port field, enter the port number of for the new managed server.

    4. Select Yes, make this server member of existing cluster.

  6. Click Next, and then click Finish.

  7. Click Save.

  8. Enable SSL for the newly added managed server:

    1. Click Domain, and then select Environments.

    2. Click Server, and then select the new managed server.

      The Settings page for the new managed server is displayed.

    3. Click the Configuration tab, and then click the General tab.

    4. Select SSL Listen Port Enabled and assign a unique port in the SSL Listen Port field.

    5. Click Save, and then click Release Lock.

During Network Integrity installation, the installer creates JMS servers for each member server of the cluster. JMS servers and filestores are among the WebLogic entities that cannot be targeted to a cluster.

Note:

The pattern followed is EntityName-N, where N is greater than 0 but less than the number of member servers in the cluster. For example, for a cluster with two member servers, these entities are named EntityName-0 and EntityName-1. Create JMS servers manually and target them to the newly added managed servers.

To manually create filestores for the added managed server:

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

    The Home screen appears.

  2. In the Change Center, click Lock & Edit.

  3. Click Domain, and then click Services.

  4. Select Persistent Stores New, and then click Create File Stores.

    Note:

    Persistent Stores New is the new persistent store.
  5. Target the new file store to the newly created servers migratable target.

  6. Set the directory attribute to ./.

  7. Create JDJMSServer-M-1 using the new filestore as its persistent store.

    To manually create JMS server for the added managed server:

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

      The Home screen of the Administration Console appears.

    2. Click Lock & Edit.

    3. Click Domain, and then click Services.

    4. Select Messaging, and then click JMSServersNew.

      Note:

      JMSServersNew is the new JMS server.
    5. Change the target of JD sub-deployment to include the newly created JMS server migratable target.

    6. Click Domain, and then select Services.

    7. Click JMS Modules, and then select (JDJMSModule).

    8. Click the SubDeployments tab.

    9. Select the new JMS server as the target.

    10. Click Save, and click Release Lock.

    11. Start the newly created managed server.

Changing the Listen Address to Network Integrity Servers

To change the listen address to Network Integrity servers:

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

    The Home screen appears.

  2. Select Servers under Environment.

    The Summary of Servers screen appears.

  3. Click Lock & Edit in the Change Center in the left pane.

  4. In the Servers table, click the Network Integrity server name. It could be the Administration, or managed server.

    The Settings for ServerName screen appears.

    The General tab is displayed by default.

  5. In the Listen Address field, enter the IP address of the required administration or managed server.

  6. Click Save.

  7. Click Release Lock.

  8. Restart the server.

Configuring the SSL Policy/Certificate

This section describes the configuration of SSL with Oracle WebLogic.

To generate a new private key and self-signed certificate in the WL_Home/server/lib directory:

  1. Go to the lib directory of the Oracle WebLogic Server installation, and use the following keytool command with complete path of the keytool:

    Java_Home/bin/keytool -genkey -alias alias -keypass keypass -keystore keystore.jks -storepass keystorepass
    

    where

    • Java_Home is the JDK installation directory

    • alias is the name

    • keypass is the password

    • keystore.jks is the key store name

    • keystorepass is the key store password

  2. At the What is your first and last name?, enter the application server IP address.

  3. Provide relevant information for the following prompts:

    1. What is the name of your organizational unit?

    2. What is the name of your organization?

    3. What is the name of your City or Locality?

    4. What is the name of your State or Province?

    5. What is the two-letter country code for this unit?

      A summary is displayed showing the information you entered, as shown in the example below:

      Is CN=IPAddressProvided, OU=OrganizationalUnit, O=Organization, L=Locality, ST=State, C=CountryCode correct?

    6. Enter Yes.

      The mykeystore.jks is created.

You must configure the new self-signed certificate in the WebLogic Administration Console.

To configure the new self-signed certificate in the Administration Console:

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

    The Home screen appears.

  2. Select Servers under Environment.

    The Summary of Servers screen appears.

  3. In the Servers table, click AdminServer.

    The Settings for AdminServer screen appears.

    The General tab is displayed by default.

  4. Select SSL Listen Port Enabled.

  5. In the SSL Listen Port field, update the value as appropriate.

  6. Click Save.

  7. Click the Keystores tab.

  8. From the Keystores list, select Custom Identity and Java Standard Trust.

  9. Do the following:

    1. In the Custom Identity Keystore field, enter the full path to your JKS file as follows:

      WL_Home/server/lib/DemoIdentity.jks

    2. In the Custom Identity Keystore Type field, enter jks.

    3. In the Custom Identity Keystore Passphrase field, enter the keystore password.

    4. Leave the Java standard trust key as the default.

    5. Click Save.

  10. Click the SSL tab.

  11. Do the following:

    1. From the Identity and Trust Locations list, select Keystores.

    2. In the Private Key Alias field, enter the alias name.

    3. In the Private Key Passphrase field, enter the private key password.

    4. Click Advanced to expand the Advanced section.

    5. From the Two Way Client Cert Behavior list, select Client Certs Requested But Not Enforced.

    6. Click Save.

  12. Click Activate Changes in the Change Center in the left pane.

For more information on SSL configuration, refer to the Administration Console Help.

Note:

To replace a self-signed certificate with a production-quality certificate, or to import a trusted CA certificate into a keystore, run the following command:
Keytool -import -alias alias -file cert.pem -keypass keypass -keystore keystore.jks -storepass keystorepass

Note:

If you import a trusted CA certificate, no existing entry for alias should be in the keystore.

While accessing the application, the browser asks to install the certificate. Install the certificate in Trusted Root Certification Authorities.

Switching the Database Instances

Network Integrity has the following data sources:

  • CMWSPersistentDS

  • EssDS

  • EssInternalDS

  • EssXADS

  • JobDispatcherDS

  • JobDispatcherPersistentDS

  • mds-commsNIRepository

  • mds-ESS_MDS_DS

  • mds_owsm

  • NIDatasource

  • NIPersistentDS

  • NIPomsPersistentDS

To change connection details for one or more data sources:

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

    The Home screen appears.

  2. Under Services, select JDBC.

    The Summary of Services: JDBC screen appears.

  3. In the Section column, click Data Sources.

    The Summary of JDBC Data Sources screen appears.

  4. Click Lock & Edit.

  5. In the Data Sources table, select a data source.

    The Settings screen appears for the selected data source.

  6. Click the Connection Pool tab.

  7. Do the following:

    1. In the URL field, enter the URL for the database JDBC.

    2. In the Properties field, change database user name.

      For example, user=niuser.

    3. In the Password field, enter the database user password.

    4. In the Confirm Password field, enter the database user password again.

    5. Click Save.

  8. Click Release Configuration.

  9. Restart all Network Integrity managed servers.

Note:

In case of Oracle Real Application Cluster (RAC) DB, you must create Multi datasources for each of the NI datasources mentioned above in the beginning of this section.

Configuring the JTA Transaction Timeout

To configure the JTA transaction timeout:

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

    The Home screen of appears.

  2. Under Services, select JTA.

    The Settings screen appears for the selected data source.

  3. Click the JTA tab.

  4. Click Lock & Edit.

  5. In the Timeout Seconds field, enter the transaction timeout seconds for active transactions.

  6. Click Save.

  7. Click Release Configuration.

  8. Restart all Network Integrity managed servers.

Configuring the Job Dispatcher Parameter - Time Out

A job refers to any of the following tasks:

  • Discovery job

  • Discrepancy job

  • Resolution job

  • Assimilation job

  • Inventory import job

You specify a timeout value for these jobs and configure the Job Dispatcher parameters to maximize performance.

To configure the Job Dispatcher parameters for Time out:

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

    The Home screen appears.

  2. Under Services, select Messaging.

    The Summary of Services: JMS screen appears.

  3. Click Lock & Edit.

  4. In the Section column, select JMS Modules.

    The JMS Modules screen appears.

  5. In the JMS Modules table, click JDJMSModule.

    The Settings for JDJMSModule screen appears.

  6. In the Summary of Resources table, click JobQueue.

    The Settings for JobQueue screen appears.

  7. Click the Overrides tab.

  8. In the Time-to-Live Override field, enter the value in milliseconds.

    This value applies to all job tasks.

  9. Click Save.

  10. Click Release Configuration.

  11. Restart all Network Integrity servers.

Configuring the Time Out Parameter for Work Items

A work item is any single unit of a Network Integrity job.

For example, a work item for a Discovery job consists of scanning a single IP address.

To configure the time out parameter for a work item:

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

    The Home screen appears.

  2. Under Services, select Messaging.

    The Summary of Services: JMS screen appears.

  3. Click Lock & Edit.

  4. In the Section column, select JMS Modules.

    The JMS Modules screen appears.

  5. In the JMS Modules table, click JDJMSModule.

    The Settings for JDJMSModule screen appears.

  6. In the Summary of Resources table, select WorkItemQueue.

    The Settings for WorkItemQueue screen appears.

  7. Click the Overrides tab.

  8. In the Time-to-Live Override field, enter the value in milliseconds.

    This value applies to all work items for all job tasks.

  9. Click Save.

  10. Click Release Configuration.

  11. Restart all Network Integrity servers.

About Node Managers

For information on Node managers, and information on using a Node manager to control the starting and stopping of application managed servers, refer to Node Manager Administrator's Guide:

http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/overview.html

Caution:

For the Node manager properties file the StartScriptEnabled flag is enabled.

Change the nodemanager.properties and ensure that the following property is changed to true (default is false) as shown:

StartScriptEnabled=true

Using JMS File Store

By default, Network Integrity uses JDBC JMS stores. To configure the WebLogic server to use File JMS stores instead of JDBC HMS stores:

  1. From the WebLogic server Administration Console, create the following filestores:

    • CMWSPersistentFILEStore

    • JDPersistentFILEStore

    • NIPOMSPersistentFILEStore

    • NIPersistentFILEStore

    Refer to your WebLogic Server documentation for more information.

  2. Click JMS Servers.

  3. Select each CMWSJMSServer and save the persistent store to CMWSPersistentFILEStore.

  4. Select each JDJMSServer and save the persistent store to JDPersistentFILEStore.

  5. Select each NIPOMSJMSServer and save the persistent store to NIPOMSPersistentFILEStore.

  6. Select each NIJMSServer and save the persistent store to NIPersistentFILEStore.

Note:

In a clustered environment, there are multiple JMS servers of each type, for example: CMWSJMSServer-0, CMWSJMSServer-1, CMWSJMSServer-2, and so on.

Configuring JMS Auto Migration

JMS Auto Migration is configured as a pre-installation step to installing Network Integrity. See Network Integrity Installation Guide for more information.

About the System MBean Configuration Services

You can use the System MBean Configuration Services to perform configuration tasks on Network Integrity.

MBeans are viewed and used using the System MBean Viewer. See "Accessing the System MBean Viewer" for more information.

This section describes the MBeans available in Network Integrity. See "About Network Integrity MBeans" for more information.

This section also explains how to use MBeans to run tasks. See "About Using MBeans to Execute Configuration Tasks on Network Integrity" for more information.

Accessing the System MBean Viewer

The System MBean Viewer is a component of Oracle Enterprise Manager.

To view MBeans in the System MBean Viewer:

  1. Access the Enterprise Manager using the following URL:

    http://AdminServer-IP:AdminServer-PORT/em
    
  2. Log on to the Enterprise Manager using WebLogic user credentials.

  3. In the left pane, select and expand your WebLogic domain.

  4. Right-click the server on which you are working and select System MBean Browser.

    The System MBean Viewer screen appears.

MBeans for Network Integrity are found in the following directory of the System MBean Browser:

Application Defined MBeans/oracle.communications.integrity/Server: Managed_Server_Name

where Managed_Server_Name is the name of the managed server.

About Network Integrity MBeans

This section lists all the Network Integrity MBeans that you can use to perform configuration tasks on Network Integrity:

CMWSConfigurationService MBean

The CMWSConfigurationService MBean is located in the cmws.jmx.AdapterMXBean folder.

Use the CMWSConfigurationService MBean to recover Network Integrity from a failed state.

The CMWSConfigurationService MBean provides the following operation:

  • startRecoveryProcess: Starts the process to recover the Network Integrity application from a failed state.

The CMWSConfigurationService MBean has the following attributes:

  • StopRunningScansWaitTime: Configures the waiting time (in milliseconds) for the server to stop. The default is 240000.

  • RestartAppWaitTime: Configures the waiting time (in milliseconds) for Network Integrity to restart after deployment or undeployment. The default is 1800000.

NIConfigurationService MBean

The NIConfigurationService MBean is located in the ResourceProviderMXBean folder.

Use the NIConfigurationService MBean to start and stop the Age Out process.

The NIConfigurationService MBean provides the following operations:

  • startAgeOutProcess: Starts the age out process.

  • stopAgeOutProcess: Stops the age out process.

The NIConfigurationService MBean has the following attributes:

  • AgeOutScheduleData: Provides the age out process schedule data.

  • AgeoutMinResults: Configures the minimum number of latest scan results that remain after an ageout purge process. The default is 2.

  • AgeoutPurge: Enables or disables the age out process. The default is True.

  • AgeoutWindowTime: Configures the minimum age (in days) of the scan results for deletion by the age out process. The default is 90.

  • jobDispatcherThrottle: Configures the number of work items that can be in the Job Dispatcher queuethrottle value for JobDispatcher. For example, a value of 10 means that a maximum of 10 work item can be in the JobDispatcher queue.

  • LdapHost: Configures the host name or IP address of the LDAP server.

  • LdapPort: Configures the port number for the LDAP server.

  • LdapUserBase: Configures the domain name of the LDAP search base for Network Integrity users.

  • MinBlackPeriod: Configures the minimum blackout period (in minutes).

  • SSLEnable: Enables or disables SSL for the embedded LDAP server.

  • UIRefreshInterval: Configures the Network Integrity UI scan status pane refresh interval time (in seconds). Valid values range from 1 to 30.

NIRegionalLinkService MBean

The NIRegionalLinkService MBean is located in the RegionalLinksMXBean folder.

Use the NIRegionalLinkService MBean to add URLs to the Links pane of the Network Integrity interface.

The NIRegionalLinkService MBean has the following attributes:

  • URLn: Configures a URL on the Links pane (n can be from 1 to 30).

  • URLNamen: Provides a name to the configured URL, as it is to appear in the Links pane (n can be from 1 to 30).

ActionProperties MBean

The ActionProperties MBean is located in the ActionProperty folder.

Use the ActionProperties MBean to configure property values on a managed property group during run time.

The ActionProperties MBean provides the following operations:

  • addProperty: Adds a new property to a managed property group.

  • listProperties: Lists all properties of the specified managed property group.

  • listPropertyGroups: Lists all managed property groups.

  • removeProperty: Removes a property from a managed property group.

  • restorePropertyDefaultValue: Restores the default value to a managed property.

  • setProperty: Sets a value to a specified managed property.

The managed properties available for a particular action are explained in the Cartridge guide for the action.

FileTransferJCA MBean

The FileTransferJCA MBean is located in the FileTransferConfigMXBean folder.

Use FileTransferJCA MBean to manage the properties of the File Transfer JCA.

For information about file transfer functionality, see Network Integrity File Transfer and Parsing Guide.

The FileTransferJCA MBean has the following attribute:

  • LocalStorageDirectory: Configures the full path where the File Transfer JCA temporarily stores local copies of remote files. The directory must exist and be readable and writable by WebLogic Server.

    For example, Middleware_Home/user_projects/domains/domain_name/servers/server_name/FileTransferAdapter, where server_name is the name of the administration or managed server.

Note:

If the File Transfer JCA is deployed to a cluster, the specified directory must be shared and be readable and writable by all servers in the cluster.

About Using MBeans to Execute Configuration Tasks on Network Integrity

This section explains the administration tasks you can perform on Network Integrity using Enterprise Manager to run MBean operations.

Starting and Stopping the Age Out Process

The startAgeOutProcess and stopAgeOutProcess operations on the NIConfigurationService MBean are used to start and stop the AgeOut process.

To start the AgeOut process for Network Integrity:

  1. In the System MBean Browser of Enterprise Manager, select the NIConfigurationService MBean.

  2. On the Operations tab, select startAgeOutProcess.

    The Operation: startAgeOutProcess screen appears.

  3. In the startDate field, enter the start date for the age out process.

  4. In the recurrenceRule field, enter the frequency

  5. Click Invoke.

    The AgeOut process starts.

To stop the AgeOut process for Network Integrity:

  1. In the System MBean Browser of Enterprise Manager, select the NIConfigurationService MBean.

  2. On the Operations tab, select stopAgeOutProcess.

    The Operation: stopAgeOutProcess screen appears.

  3. Click Invoke.

    The AgeOut process stops.

Enabling and Disabling the Ageout Purge Process

The AgeoutPurge attribute on the NIConfigurationService MBean is used to enable and disable the purging of scan results that are older than a specified value.

To configure the AgeoutPurge attribute:

  1. In the System MBean Browser of Enterprise Manager, select the NIConfigurationService MBean.

  2. On the Attributes tab, select AgeoutPurge.

    The Attribute: AgeoutPurge screen appears.

  3. In the Value list, select True to enable the Ageout Purge Process, select False to disable the Ageout Purge Process.

  4. Click Apply.

Configuring the Minimum Number of Remaining Scans After Ageout Purge

The AgeoutMinResults attribute on the NIConfigurationService MBean is used to configure the minimum number of scan results to remain after the Ageout Purge Process is run.

To configure the AgeoutMinResults attribute:

  1. In the System MBean Browser of Enterprise Manager, select the NIConfigurationService MBean.

  2. On the Attributes tab, select AgeoutMinResults.

    The Attribute: AgeoutMinResults screen appears.

  3. In the Value field, enter the minimum number of scan results to remain after the Ageout Purge Process is run.

  4. Click Apply.

Configuring the Expiration Time for Scan Results

The AgeoutWindowTime attribute on the NIConfigurationService MBean is used to configure the minimum number of days after which a scan result gets deleted by the Ageout Purge Process.

To configure the AgeoutWindowTime attribute:

  1. In the System MBean Browser of Enterprise Manager, select the NIConfigurationService MBean.

  2. On the Attributes tab, select AgeoutWindowTime.

    The Attribute: AgeoutWindowTime screen appears.

  3. In the Value field, enter the minimum number of days after which a scan result gets deleted by the Ageout Purge Process.

  4. Click Apply.

Configuring the Throttle Value for Job Dispatcher

The jobDispatcherThrottle attribute on the NIConfigurationService MBean is used to configure the number of work items permitted in the queue for the Job Dispatcher.

To configure the jobDispatcherThrottle attribute:

  1. In the System MBean Browser of Enterprise Manager, select the NIConfigurationService MBean.

  2. On the Attributes tab, select jobDispatcherThrottle.

    The Attribute: jobDispatcherThrottle screen appears.

  3. In the Value field, enter the number of work items permitted in the queue for the Job Dispatcher.

  4. Click Apply.

Enabling/Disabling SSL for the Embedded LDAP Server

The SSLEnable attribute on the NIConfigurationService MBean is used to enable or disable SSL for the embedded LDAP server.

To configure the SSLEnable attribute:

  1. In the System MBean Browser of Enterprise Manager, select the NIConfigurationService MBean.

  2. On the Attributes tab, select SSLEnable.

    The Attribute: SSLEnable screen appears.

  3. From the Value list, select True to enable SSL, select False to disable SSL.

  4. Click Apply.

Configuring the LDAP Host

The LdapHost attribute on the NIConfigurationService MBean is used to configure the host name or IP address of the LDAP server.

To configure the LdapHost attribute:

  1. In the System MBean Browser of Enterprise Manager, select the NIConfigurationService MBean.

  2. On the Attributes tab, select LdapHost.

    The Attribute: LdapHost screen appears.

  3. In the Value field, enter the host name or the IP address of the LDAP server.

  4. Click Apply.

Configuring the LDAP Port

The LdapPort attribute on the NIConfigurationService MBean is used to configure the port number of the LDAP server.

To configure the LdapPort attribute:

  1. In the System MBean Browser of Enterprise Manager, select the NIConfigurationService MBean.

  2. On the Attributes tab, select LdapPort.

    The Attribute: LdapPort screen appears.

  3. In the Value field, enter the port number of the LDAP server.

  4. Click Apply.

Configuring the Scan Results Status Window Refresh Time

The UIRefreshInterval attribute on the NIConfigurationService MBean is used to configure how often the scan status results are refreshed in the Network Integrity interface.

To configure the UIRefreshInterval attribute:

  1. In the System MBean Browser of Enterprise Manager, select the NIConfigurationService MBean.

  2. On the Attributes tab, select UIRefreshInterval.

    The Attribute: UIRefreshInterval screen appears.

  3. In the Value field, enter the number of seconds between scan result refreshes.

  4. Click Apply.

Setting the Minimum Time Limit for a Blackout Period

The MinBlackPeriod attribute on the NIConfigurationService MBean is used to configure the minimum blackout period.

To configure the MinBlackPeriod attribute:

  1. In the System MBean Browser of Enterprise Manager, select the NIConfigurationService MBean.

  2. On the Attributes tab, select MinBlackPeriod.

    The Attribute: MinBlackPeriod screen appears.

  3. In the Value field, enter the number of minutes for the minimum blackout period.

  4. Click Apply.

Configuring Links on the Links Panel

The URL and URLName attributes on the NIRegionalLinksService MBean are used to configure links on the Links panel. You can use the URL and URL attributes to add, change, and remove links from the Links panel.

To add links to the Links panel of the Network Integrity Interface:

  1. In the System MBean Browser of Enterprise Manager, select the NIRegionalLinksService MBean.

  2. On the Attributes tab, select a URL attribute with a blank value.

    The Attribute: URL screen appears, where URL is the URL attribute you selected.

  3. In the Value field, enter the URL you want to add to the Links panel.

  4. Click Apply.

  5. On the Attributes tab, select the URL name attribute that corresponds with the URL attribute.

    The Attribute: URL_Name screen appears, where URL_Name is the URL name attribute you selected.

  6. In the Value field, enter a name for the URL as you want it to appear in the Links panel.

  7. Click Apply.

To configure links on the Links panel of the Network Integrity Interface:

  1. In the System MBean Browser of Enterprise Manager, select the NIRegionalLinksService MBean.

  2. On the Attributes tab, select a URL attribute with a configured value.

    The Attribute: URL screen appears, where URL is the URL attribute you selected.

  3. Do one of the following:

    • To modify the URL, enter a new URL in the Value field.

    • To delete the URL, make the Value field empty.

  4. Click Apply.

    A confirmation message appears.

  5. Click Return.

  6. On the Attributes tab, select the URL Name attribute that corresponds with the URL attribute.

    The Attribute: URL_Name screen appears, where URL_Name is the URL Name attribute you selected.

  7. Do one of the following:

    • To modify the URL name, enter a new URL name in the Value field, as you want it to appear in the Links panel of the Network Integrity interface.

    • To delete the URL name, make the Value field empty.

  8. Click Apply.

    A confirmation message appears.

Configuring the Server Load Balancer

Multiserver deployments consist of clusters, managed servers, and standalone servers in single, or multiple WebLogic Server domains. A server farm like this achieves high availability and scalability through server load balancing by appearing as a single server to client systems.

There are two types of client requests that are managed when you employ load balancing: HTTP and JMS.

This section briefly discusses these server requests and how the respective loads can be balanced.

Load Balancing HTTP Sessions Using Server Load Balancer

Server load balancer (SLB) provides a virtual server acting as the single point of entry for a group of real servers and distributes requests across the real servers depending on the load balancing algorithm and the availability of the servers.

Note:

Oracle recommends the hardware-based load balancer for reliability and scalability. Hardware SLB contains application-specific integrated circuits (ASICs) that enable high-speed forwarding of network traffic, without operating system overhead.

Server Load Balancer Requirements

For information on server load balance requirements while working with the WebLogic server, see the following Fusion Middleware document:

http://download.oracle.com/docs/cd/E12839_01/web.1111/e13709/load_balancing.htm#CLUST175

Note:

The SLB examples provided at this link refer the F5 BIG-IP Application Switches LTM, Cisco ACE, and Brocade ServerIron.

Note:

Oracle recommends the SSL acceleration module to process SSL transactions efficiently. Furthermore, it eliminates cost installing SSL certificates on all WebLogic servers.

Server Load Balancer Configurations

Network Integrity uses TCP-levels load balancing.

Keep the following considerations in mind for virtual server and real server configurations:

  • Use the following URL to identify the Network Integrity managed servers in a cluster and configure the hardware load balancer to balance the loads on UI and Web service Network Integrity requests:

    https://IP:Port/NetworkIntegrity/index.html
    

    Where IP is the IP address of the Network Integrity server, and Port is the port number where the Network Integrity server is running.

    Note:

    Oracle recommends BIG IP LTM 3600 as a hardware load balancer.
  • Working with sticky sessions, which basically means that a user's requests are sent to the same server where the sessions was first initiated. The server must be enabled for HTTP/HTTPS requests until it is not available.

During HTTP request processing, such as dynamic Web service discovery, the response may contain a real server listening address which may not be accessible from client systems. In such scenarios, consider the following:

  • Use an SLB-specific feature to replace the listening address and port of a real server with the listening addresses and port of a virtual server. Because the HTTP response content is modified, you must reconfigure the HTTP content-length header. Verify with your SLB vendor if this feature is supported.

  • Configure the HTTP front end host and the HTTP/HTTPS front end port for the WebLogic server or cluster. This approach is recommended if SLB does not support HTTP response modification. When configured, any attempt to access real servers directly is directed back to the virtual server.

Network Configurations

In a production environment, Network Integrity may be deployed with other Oracle Communications products, such as Unified Inventory Management (UIM). Network Integrity sends Web service requests to the UIM application server for inventory import. If UIM is deployed on a cluster, the Web service requests must go through the UIM virtual server. Therefore, the Network Integrity application server must be multi-homed.

Provided here are some examples of network deployment.

  • Management network: This network is used for system administration and software installation. This is the default WebLogic server listening address.

  • Client network: This network is used for client systems to send requests to the Network Integrity or UIM cluster.

  • Application server network: This network is used for when the server load balancer is required to distribute client requests to clusters. It is advisable that you create a network channel for each application server.

  • Database server network: Use this network when the application servers are required to send SQL requests to the database through JDBC.

  • Storage network: If SAN is deployed, WebLogic server domains, JMS file stores, and database files could be placed on SAN. For performance, JMS file stores should be separated from WebLogic domains.

Note:

You do not necessarily need multiple networks to configure an SLB. If required, you can combine a management network, application server network, and database network.

Note:

Use link aggregation to increase bandwidth.

Load Balancing in a Clustered Environment

For load balancing in a clustered environment, use the Apache proxy server with the Oracle WebLogic server.

See the Apache Web site to download and install the Apache server:

http://httpd.apache.org/download.cgi

Download the Apache plug-in for the WebLogic server from the Oracle Technology Network (OTN) Web site:

http://www.oracle.com/technetwork/middleware/ias/downloads/wls-plugins-096117.html

Note:

You must accept the OTN License Agreement to download this software.

For more information on how the plug-in works in WebLogic, see the following Oracle Web site:

http://download.oracle.com/docs/cd/E13222_01/wls/docs100/plugins/apache.html

To configure the server load balancer:

  1. Extract mod_wl_22.so for the particular operating system where Apache is running from the WebLogic plug-in you downloaded earlier.

  2. Save the extracted files in the Modules folder of the Apache server. For example:

    C:\Program Files\Apache Software Foundation\Apache2.2\modules

  3. Open \Apache2.2\modules\httpd.conf.

  4. Modify the file by making the following entries:

    IfModule mod_weblogic.c
    
    WebLogicCluster 10.147.240.145:7755,10.147.240.137:7744,10.147.240.145:7055,10.147.240.137:7044
    MatchExpression /NetworkIntegrity/*
    MatchExpression /NetworkIntegrityApp-NetworkIntegrityControlWebService-context-root/*
    Debug ON
    DebugConfigInfo ON
    WLLogFile /opt/oracle/weblogic.log
    </IfModule>
     
    <IfModule mod_weblogic.c>
    WebLogicHost 10.147.240.145
    WebLogicPort 7777
    MatchExpression /xmlpserver/*
    </IfModule>
    

    where WebLogicCluster is the IP address or port number of the WebLogic Server cluster, and MatchExpression has the context root of the Web Application.

    Note:

    In Network Integrity, reports are deployed on a non-clustered Managed Server. Therefore, it is recommended that you use a WebLogicHost instead of a WebLogicCluster in the <ifmodule> in the above example.
  5. Restart the HTTP server.

    You can now access the application from the proxy server.

You can connect to the following services at the provided URLs:

  • Webservices wsdl:

  • http://localhost:82/NetworkIntegrityApp-NetworkIntegrityControlWebService-context-root/NetworkIntegrityControlServicePortType?wsdl
    
  • UI:

  • http://localhost:82/NetworkIntegrity/faces/IntegrityUIShell
    
  • Reports:

  • http://localhost:82/xmlpserver/
    

Load Balancing JMS Messages

For applications that are not running within a WebLogic server instance, load balancing JMS messages is achieved by specifying the PROVIDER_URL when creating JNDI initialContext object to connect to a server or cluster.

For applications running within a WebLogic server instance, creating initialContext without providing PROVIDER_URL implicitly returns the JNDI context for the local server or cluster.

When you use the JMS Store-and-Forward (SAF) feature to provide highly-available JMS message production, by connecting a local server and reliably forwarded messages to a remote JMS destination, SAF remote context defines the URL of the remote server instance or cluster where the JMS destination is exported from. It also contains the security credentials to be authenticated and authorized in the remote cluster or server(s).

To import remote destinations from a remote cluster or servers, you must supply one of the following for the PROVIDER_URL or SAF remote context:

  • A comma-delimited list of DNS server names

  • A comma-delimited list of IP addresses

  • Remote cluster's cluster address defined in DNS (recommended for production environment)

The following examples are of a URL used when a remote SAF context defines a remote cluster from which it imports distributed destination members:

  • <URL> t3://192.180.0.10:7012,192.168.0.11:7012,192.168.0.12:7012</URL>

  • <URL> t3://192.180.0.10:7012,192.168.0.11:7012,192.168.0.12:7012</URL>

where, UIMCluster is the cluster address for the UIM application cluster consisting of servers with IP addresses 192.168.0.10, 192.168.0.11, and 192.168.0.12.

Note:

Server load balancer has no part in load balancing JMS messages and may be used only for initial host name resolution.

For more information on configuring the F5 BIG-IP LTM for WebLogic Server, refer to the following F5 document:

http://www.f5.com/pdf/deployment-guides/f5-weblogic10-dg.pdf

For information on Oracle Fusion Middleware Configuring and Managing Store-and-Forward for Oracle WebLogic Server, see the documentation at the following Oracle Web site:

http://download.oracle.com/docs/cd/E12839_01/web.1111/e13742/toc.htm