Skip Headers
Oracle® Communications Network Integrity Installation Guide
Release 7.2.2

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

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

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

About the Trusted Certificate for Network Integrity

Note:

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

This is expected behavior. Accept this untrusted certificate to continue to connect to Network Integrity UI.

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

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

Managing Network Integrity Cartridges

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

You can manage cartridges in the following ways:

About Managing Network Integrity Cartridges with the Cartridge Deployer Tool

You use the Cartridge Deployer Tool to deploy and manage cartridges in Network Integrity.

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

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:

Before deploying or undeploying cartridges, ensure that:
  • You are logged out of the WebLogic Server Administration Console.

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

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

Deploying Cartridges

To deploy the required cartridges:

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

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

    ./runCartridgeDeployer.sh 
    

    The Cartridge Deployer Welcome screen appears.

  3. Select the Deploy Cartridge option and click Next.

    The Select Cartridge Type screen appears.

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

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

    Note:

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

    The Cartridge Location screen appears.

  5. Click Browse to search for and select the required cartridges for the Cartridge Deployer Tool to deploy.

    You can select multiple cartridges from a single directory by holding down the Ctrl key.

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

    Note:

    The customized file browser shows only predefined cartridge extensions. Network Integrity supports cartridges with .iar and .jar extensions.
  6. After selecting the required cartridges, click Next.

    The Configure Deployment Queue screen appears.

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

    Note:

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

    The WebLogic Connection Information screen appears.

  8. Do the following:

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

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

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

      Note:

      You must enter the Admin Server SSL Port if the Use SSL check box is selected.
    4. In the Keystore field, enter the keystore location if the Use SSL check box is selected.

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

      Note:

      Use your WebLogic administrator user name and password here, and in the next step.

      CMWS is Cartridge Management Web Service. CMWS user is a WebLogic server user belonging to the administrators group.

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

      Note:

      Use your WebLogic administrator user name and password here.
    7. Click Next.

    The Select WebLogic Target screen appears.

  9. In the list, select the Managed Server where CMWS is deployed and click Next.

    The following message is displayed, if SSL is not configured properly:

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

    Note:

    The SLL handshake fails when the Cartridge Deployer Tool connects to the CMWS using HTTPS.
  10. Click OK in the message, and deselect Use SSL (if enabled) while connecting to Cartridge Management WebService at the bottom of the screen.

    Note:

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

    The Review Deployment screen appears.

  12. Review and confirm your selections, and click Deploy.

    The Cartridge Deployment screen appears.

    Note:

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

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

    Note:

    If the system or server goes down during cartridge deployment, the cartridge is recovered after the system is up again, or during the next cartridge deployment session, with the cartridge deployment request showing as “failed”.
  13. Click Exit to close the Cartridge Deployment Tool.

Note:

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

Undeploying Cartridges

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

Note:

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

To undeploy a cartridge:

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

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

    ./runCartridgeDeployer.sh 
    

    The Cartridge Deployer Welcome screen appears.

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

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

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

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

      Note:

      Use your WebLogic administrator user name and password here, and in the next step.

      CMWS is Cartridge Management Web Service. CMWS user is a WebLogic server user belonging to the administrators group.

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

      Note:

      Use your WebLogic administrator user name and password here.
    5. Click Next.

    The Select WebLogic Target screen appears.

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

    Note:

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

    The Cartridge Deployer Tool lists all WebLogic targets available in the domain where Network Integrity Cartridge Management Components are installed. Select a target from the list.

    The following message appears:

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

    Note:

    The SLL handshake fails when the Cartridge Deployer Tool connects to the CMWS using HTTPS.
  7. Click OK in the message, and deselect Use SSL (if enabled) while connecting to Cartridge Management WebService at the bottom of the screen.

    Note:

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

    The Select Cartridges for Undeployment screen appears.

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

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

    Note:

    The cartridge name must be selected before right-clicking.
  10. Click Next.

    Note:

    To add an undeployment property, right-click the cartridge and select the required option.

    The Review Undeployment screen appears.

  11. Review your selection(s) and click Next.

    The Cartridge Undeployment screen appears.

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

For more information about managing cartridges, 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 system where the Administration server is running.
  2. In the remote server, deploy, or undeploy, cartridges using steps provided in the sections "Deploying Cartridges" and "Undeploying Cartridges".

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

  4. Update the NetworkIntegrity.ear file.

    The cartridges are deployed on, or undeployed from, the remote managed server.

Viewing Cartridges

To view deployed cartridges:

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

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

    ./runCartridgeDeployer.sh 
    

    The Cartridge Deployer Welcome screen appears.

  3. Select the View 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:

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

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

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

      Note:

      Use your WebLogic administrator user name and password here, and in the next step.

      CMWS is Cartridge Management Web Service. CMWS user is a WebLogic server user belonging to the administrators group.

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

      Note:

      Use your WebLogic administrator user name and password here.
    5. Click Next.

    The Select WebLogic Target screen appears.

  6. Select the WebLogic targets where the 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.
    

    Note:

    The SLL handshake fails when the Cartridge Deployer Tool connects to the CMWS using HTTPS.
  7. Click OK in the message, and deselect the Use SSL (if enabled) while connecting to Cartridge Management WebService check box at the bottom of the screen.

    Note:

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

    The Deployed Cartridges screen appears.

    You can view the deployed cartridges.

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

For information about deploying cartridges using Design Studio, see 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 NI_Home/CartridgeDeployerClients/tools/Sample.java for an example custom Java application, containing example syntax and sample Java classes.

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

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

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

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

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

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

    1. Import the following files:

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

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

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

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

      • name

      • version

      • buildId

      • type

      • deploy properties

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

      • webServiceUrl

      • keystore_location

      • cmwsUserName

      • password

      • cartridge_object

      • pollwait

      • pollcount

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

      • name

      • version

      • type

      • undeploy properties

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

      • webServiceUrl

      • keystore_location

      • cmwsUserName

      • password

      • cartridge_object

      • pollwait

      • pollcount

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

      • webServiceUrl

      • keystore_location

      • cmwsUserName

      • password

      • cartridgeType

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

      • name

      • version

      • type

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

      • webServiceUrl

      • keystore_location

      • cmwsUserName

      • password

      • cartridge_object

      • comparisonOperator

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

      • webServiceUrl

      • keystore_location

      • cmwsUserName

      • password

      • cartridgeType

Developing Custom ANT Tasks

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

To develop custom ANT tasks with which to manage cartridges:

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

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

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

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

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

    <taskdef name="deploy" classname="oracle.communications.sce.cartridgemanagement.ws.tools.DeployCartridge" classpathref="class.path"/>
    
    <taskdef name="undeploy" classname="oracle.communications.sce.cartridgemanagement.ws.tools.UndeployCartridge" classpathref="class.path"/>
    
    <taskdef name="list" classname="oracle.communications.sce.cartridgemanagement.ws.tools.ListCartridge" classpathref="class.path"/>
    
    <taskdef name="exist" classname="oracle.communications.sce.cartridgemanagement.ws.tools.CartridgeExist" classpathref="class.path"/>
    
    <taskdef name="environment" classname="oracle.communications.sce.cartridgemanagement.ws.tools.GetEnvironment Version" classpathref="class.path"/>
    
  6. Add the valid attributes for each ANT task:

    • For the deploy task:

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

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

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

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

      <target name="env">
        <echo message="Fetching environment version..."/>
        <environment host="${host}" port="${port}" username="${username}" password="${password}" adminServerKeyStore="${adminServerKeyStore}" adminServerKeyStore="${adminServerKeyStore}" sslKeyStore="${sslKeyStore}" target="${target}" cartridgeType="${cartridgeType}" property="envval"/>
        <echo message="Message from env task : ${envval}"/>
      </target>
      
  7. Inside the lib/ directory, create an XML properties file to automate the ANT tasks:

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

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

Running Cartridge Operations From a Command-Line

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

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

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

  3. Enter commands at the command-line.

From the command-line interface, you can:

  • Deploy one or more cartridges.

  • Undeploy one or more cartridges.

  • List all deployed cartridges.

  • List all available, undeployed cartridges.

  • Show the help message.

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

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

Valid Argument Description

-host

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

-port

A valid port number to the admin server.

-user

A CMWS user.

-password

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

-keystore

A valid keystore location for SSL connection.

-adminkeystore

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

-type

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

-operation

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

-location

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

-target

The target server, where CMWS is deployed.

-name

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

-version

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

-help

Display the help message.


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

Table 7-2 Valid Arguments for Each Cartridge Command

Command Description

deploy

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

Valid Arguments: -type, -location, -target

undeploy

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

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

list

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

Valid Arguments: -type, -target

exist

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

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


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

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

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

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

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

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

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

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

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

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

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

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

Configuring Network Integrity for Inventory Management

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

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

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

Installing Network Integrity Report Templates

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

Note:

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

To deploy the report templates to BI Publisher:

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

  2. In the Admin tab, under Data Sources, click JDBC Connection.

    The Data Sources screen appears with the JDBC tab open.

  3. In the Add Data Source table, under the heading Data Source Name, click demo.

    The Update Data Source: demo screen appears.

  4. Provide the following details:

    • The Connection String

      The format is:

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

      For example, a sample connection string may look like:

      jdbc:oracle:thin:@myhost:1521:orcl
      
    • User name

    • Password

    • Database Driver Class

      The default is:

      oracle.jdbc.driver.OracleDriver
      
  5. Click Test Connection.

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

  7. Go to the BI Publisher Home page.

  8. Click the My Folders link.

    The My Folders pane appears.

  9. Click the Create a new folder link.

    Enter the folder name, and click Create.

  10. Click the folder name of the folder you created.

    The folder screen appears.

  11. Click the Upload a report link.

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

  13. Click Upload.

    The report templates are saved in the folder you created.

  14. In the Reports tab, click Edit, and click the Layouts link.

    The Create Layouts panel appears.

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

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

  17. Click Save.

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

  19. Click View to view reports.

Starting the AgeOut Process

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

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

Enabling HTTP Tunneling

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

Note:

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

To enable http tunneling, perform the following:

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

  2. Click Lock and edit.

  3. Click Servers in the left panel.

  4. Select the server name and click Protocols.

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

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

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

  8. Click Activate Changes.

  9. Repeat the same procedure for any managed servers.