This chapter provides instructions for Oracle Communications Network Integrity post-installation tasks.
Post-installation tasks for Network Integrity include:
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 includes deploying and undeploying cartridges, viewing deployed and available cartridges, and migrating older cartridges to the latest version of Network Integrity.
You can deploy cartridges into Network Integrity in the following ways:
From Design Studio. You can deploy cartridges interactively from Design Studio to test environments. Design Studio enables you to manage cartridges in the test environment consistently, manage common test environment connection parameters across the design team, and compare cartridge version and build numbers in the development environment with those of the cartridges deployed in the test environment. See the Design Studio Help for more information.
By using the Design Studio Cartridge Management Tool (CMT). The CMT enables you to automate cartridge deployment. You can use the CMT to deploy cartridges into both test and production environments. You can also use it to deploy cartridges into cluster environments. See the Design Studio Developer's Guide for more information about the CMT.
By using the Network Integrity Cartridge Deployer Tool (CDT). The Network Integrity CDT is a GUI-based tool that enables you to deploy to Network Integrity run-time environments. The Oracle Universal Installer installs the CDT as part of the Network Integrity installation process. You can use the CDT to deploy cartridges into both test and production environments. You can also use it to deploy cartridges into cluster environments. See "Deploying Cartridges with the Network Integrity Cartridge Deployer Tool" for more information.
By writing your own custom scripts. See "Managing Cartridges With Custom Scripts" for more information.
The Cartridge Deployer Tool is available as a component of the core Network Integrity application. The Oracle Universal Installer installs the Cartridge Deployer Tool as part of the installation process in the same folder as the Network Integrity application.
The WebLogic Server Administration Console must not be locked for editing for the Cartridge Deployer Tool to successfully manage cartridges. See your WebLogic Server documentation for more information.
Note:
Before deploying or undeploying cartridges, ensure that:You are logged out of the WebLogic Server Administration Console.
No one else is deploying or undeploying cartridges on the same server.
Network Integrity is not running a scan that uses the cartridge.
To deploy cartridges with the Network Integrity Cartridge Deployer Tool:
Go to the NI_Home/CartridgeDeployerClients/CartridgeDeployer folder.
Run the Cartridge Deployer Tool executable with the following command:
./runCartridgeDeployer.sh
The Cartridge Deployer Welcome screen appears.
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.
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.
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.After selecting the required cartridges, click Next.
The Configure Deployment Queue screen appears.
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.
Do the following:
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.
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.In the Keystore field, enter the keystore location if the Use SSL check box is selected.
In the CMWS User field, enter the user name of the CMWS user.
Note:
Use your WebLogic administrator user name and password here, and in the next step.The cartridge management web service (CMWS) user is a WebLogic server user belonging to the administrators group.
In the Password field, enter the password for the CMWS user.
Note:
Use your WebLogic administrator user name and password here.Click Next.
The Select WebLogic Target screen appears.
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.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.Click Next.
The Review Deployment screen appears.
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”.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.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:
Go to the NI_Home/CartridgeDeployerClients/CartridgeDeployer folder.
Run the Cartridge Deployer Tool executable by running the following command:
./runCartridgeDeployer.sh
The Cartridge Deployer Welcome screen appears.
Select Undeploy Cartridge and click Next.
The Select Cartridge Type screen appears.
From the Cartridge Type list, select NetworkIntegrity and click Next.
The WebLogic Connection Information screen appears.
Do the following:
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.The CMWS user is a WebLogic server user belonging to the administrators group.
In the Password field, enter the password for the CMWS user.
Note:
Use your WebLogic administrator user name and password here.Click Next.
The Select WebLogic Target screen appears.
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.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.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.
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.Click Next.
Note:
Network Integrity does not use undeployment properties.The Review Undeployment screen appears.
Review your selection(s) and click Next.
The Cartridge Undeployment screen appears.
You can view the undeployment progress in this screen. Logs returned by the adapter are displayed after each cartridge operation irrespective of its success.
For more information about managing cartridges and deploying cartridges using Design Studio, see the Design Studio Help.
Caution:
If the server or system goes down during cartridge undeployment, the cartridge is recovered after the system is up again, or during the next cartridge undeployment session, with the cartridge deployment request showing as ”deploy”.Ensure that you deploy the recovered cartridge first and then undeploy it.
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:
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.In the remote server, deploy, or undeploy, cartridges using steps provided in the sections "Deploying Cartridges with the Network Integrity Cartridge Deployer Tool" and "Undeploying Cartridges with the Network Integrity Cartridge Deployer Tool".
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.
To deploy cartridges into a cluster environment that uses a proxy server as a frontend host:
Shut down all the managed servers except the managed server on which the cartridge_management_ws application is deployed. If you do not know the managed server on which the cartridge_management_ws application is deployed, continue with step 2; otherwise, proceed to step 3.
(Optional) Locate the cartridge_management_ws application and the corresponding server on which it is deployed by doing the following:
Log in to the WebLogic Server Administration Console.
On the Home page, under Domain Structure, click the Deployments link.
The Summary of Deployments page appears.
Under the Name column, locate the cartridge_management_ws application; under the Targets column, locate the server on which this application is deployed.
Deploy the required cartridges.
After you have deployed the cartridges, start the Administration Server and all the other managed servers.
Note:
Repeat this procedure for every cartridge deployment life cycle.To view deployed cartridges:
Go to the NI_Home/CartridgeDeployerClients/CartridgeDeployer folder.
Run the Cartridge Deployer Tool executable by running the following command:
./runCartridgeDeployer.sh
The Cartridge Deployer Welcome screen appears.
Select the View Cartridges option, and click Next.
The Select Cartridge Type screen appears.
Select Network Integrity in the Cartridge Type list, and click Next.
The WebLogic Connection Information screen appears.
Do the following:
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.The CMWS user is a WebLogic server user belonging to the administrators group.
In the Password field, enter the password for the CMWS user.
Note:
Use your WebLogic administrator user name and password here.Click Next.
The Select WebLogic Target screen appears.
Select the WebLogic targets where the CMWS is installed and click Next.
Note:
In some cases, the WebLogic targets may be different from where Network Integrity is installed.The following message is displayed:
SSL Handshaking failed. You can proceed without SSL by unchecking SSL options on the bottom of this screen.
Note:
The SLL handshake fails when the Cartridge Deployer Tool connects to the CMWS using HTTPS.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.Click Next.
The Deployed Cartridges screen appears.
You can view the deployed cartridges.
For more information about managing cartridges, see Modeling Network Integrity, which is part of Design Studio online Help.
For information about deploying cartridges using Design Studio, see the Design Studio online Help.
Scripted cartridge management allows you to develop custom scripts that deploy, undeploy, list deployed cartridges, and list available cartridges. Scripts can be run manually, or from a command prompt, and can be used to execute cartridge operations to secure and non-secure network systems.
To manage cartridges using Java, you must develop a custom Java application. Or, to manage cartridges using ANT tasks, you must develop a custom XML script.
Note:
You can automate cartridge deployment using the Design Studio Cartridge Management Tool (CMT). You can use the CMT to deploy cartridges into both test and production environments. See the Design Studio Developer's Guide for more information about the CMT.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:
Open Oracle Communications Design Studio or any Java Integrated Development Environment (IDE) in the Java perspective.
Create a Java project and a /lib directory in the project.
Import all the JAR files from the NI_Home/CartridgeDeployerClients/lib/ directory to the /lib directory in the project.
Download cartridge-management-client-tools.jar from the NI_Home/CartridgeDeployerClients/tools directory to the /lib directory in the project.
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:
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
To deploy cartridges, create an oracle.communications.platform.cartridgemanagement.client.domain.Cartridge object with the following class attributes:
name
version
buildId
type
deploy properties
Call the deployCartridge() operation on the cartridge manager object with the following arguments:
webServiceUrl
keystore_location
cmwsUserName
password
cartridge_object
pollwait
pollcount
To undeploy cartridges, create an oracle.communications.platform.cartridgemanagement.client.domain.Cartridge object with the following class attributes:
name
version
type
undeploy properties
Call the unDeployCartridge() operation on the cartridge manager object with the following arguments:
webServiceUrl
keystore_location
cmwsUserName
password
cartridge_object
pollwait
pollcount
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
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
Call the cartridgeExist() operation on the cartridge manager object with the following arguments:
webServiceUrl
keystore_location
cmwsUserName
password
cartridge_object
comparisonOperator
To get the environment, call the getEnvironmentVersion() operation on the cartridge manager object with the following arguments:
webServiceUrl
keystore_location
cmwsUserName
password
cartridgeType
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:
Open Design Studio or any Java Integrated Development Environment (IDE) in the XML perspective.
Create a Java project and a /lib directory in the project.
Import all the JAR files from the NI_Home/CartridgeDeployerClients/lib/ directory to the /lib directory in the project.
Download cartridge-management-client-tools.jar from the NI_Home/CartridgeDeployerClients/tools directory to the /lib directory in the project.
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"/>
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>
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.
To use a command-line interface to run cartridge operations:
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 Java 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 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 |
|
-operation |
The cartridge operation to be performed. Possible values are: |
|
-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
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.
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:
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.
In the Add Data Source table, under the heading Data Source Name, click demo.
The Update Data Source: demo screen appears.
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
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.
Click the Create a new folder link.
Enter the folder name, and click Create.
Click the folder name of the folder you created.
The folder screen appears.
Click the Upload a report link.
Click Browse adjacent to the Report to Upload field, and browse for a file with the XDO extension.
Click Upload.
The report templates are saved in the folder you created.
In the Reports tab, click Edit, and click the Layouts link.
The Create Layouts panel appears.
In the Manage Template Files section, click Browse adjacent to the Upload Template field.
Browse for and select all available RTF files and click Upload.
Click Save.
Repeat steps 12 - 17 to upload all unzipped folders in the same manner.
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.
See Network Integrity System Administrator's Guide for information about starting the AgeOut Process.
In order for Network Integrity to transfer large amounts of data between the server and client, the WebLogic server must be configured for http tunneling. This will help the server to make a dedicated connection with the client, for the given timeout and within this time, the data can be transferred without giving any errors.
Note:
HTTP tunneling should be enabled on the server where Network Integrity is deployed. If Network Integrity is deployed in a single managed server installation, then the parameters need to be changed on the WebLogic administration server. If Network Integrity is deployed in a clustered server installation, then the parameters need to be changed on the WebLogic administration server and all the managed servers.To enable http tunneling, perform the following:
Log in to the Administration console using the administrator user name and password.
Click Lock and edit.
Click Servers in the left panel.
Select the server name and click Protocols.
In the Enable tunneling field, select the check box.
In the Tunneling client ping field, enter 80 seconds.
In the Tunneling client timeout field, enter 900 seconds.
Click Activate Changes.
Repeat the same procedure for any managed servers.
If you choose to use Oracle Internet Directory as your lightweight directory access protocol (LDAP) provider, you must set it up to run with Network Integrity.
Navigate to Domain_Home/config/fmwconfig.
Edit the file jps-config.xml.
Find the following serviceInstance parameter:
<serviceInstance name="idstore.ldap" provider="idstore.ldap.provider">
Add the following bold entries to the file:
<serviceInstance name="idstore.ldap" provider="idstore.ldap.provider">
<description>LDAP Identity Store Service Instance</description>
<property name="idstore.config.provider" value="oracle.security.jps.wls.internal.idstore.WlsLdapIdStoreConfigProvider"/>
<property name="CONNECTION_POOL_CLASS" value="oracle.security.idm.providers.stdldap.JNDIPool"/>
<property name="virtualize" value="true"/>
<serviceInstanceRef ref="NetworkIntegrityAuthenticationProvider"/>
</serviceInstance>
<serviceInstance name="NetworkIntegrityAuthenticationProvider" provider="idstore.ldap.provider">
<property name="idstore.type" value="ACTIVE_DIRECTORY" />
</serviceInstance>
Save and close the file.