How to Pull Data Topology from a Micro Focus NA Server using a Java Client

Ensure that there is connectivity to the NA server on the RMI port. The default port is 1099.

(This step is for NA 10.10, 10.11, 10.20, 10.21, and 10.30) To support NA 10.10, 10.11, 10.20, 10.21, and 10.30, do the following:

1. Create a new folder naxxxx (for example, na1010) under the <DataFlowProbe_Home>\runtime\probeManager\discoveryResources directory.

   Note xxxx is the NA version number.

2. Copy the following two JAR files from the <DataFlowProbe_Home>\runtime\probeManager\discoveryResources\na directory to the <DataFlowProbe_Home>\runtime\probeManager\discoveryResources\naxxxx directory :

   • ddm-na-client.jar
   • fst.jar

3. Copy the following JAR files to the <DataFlowProbe_Home>\runtime\probeManager\discoveryResources\naxxxx directory:

   • bcprov-jdk150on.jar, cryptojce.jar, cryptojcommon.jar, and jcmFIPS.jar in the <NA_Installation>/jre/lib/ext directory.
   • truecontrol-client.jar in the <NA_Installation>/client directory.
   • json.jar in the <NA_Installation>/server/ext/jboss/server/default/lib directory.

4. Result

   The <DataFlowProbe_Home>\runtime\probeManager\discoveryResources\naxxxx directory includes the following files:

   • bcprov-jdk15on.jar
   • cryptojce.jar
   • cryptojcommon.jar
   • ddm-na-client.jar
   • fst.jar
   • jcmFIPS.jar
   • json.jar
   • truecontrol-client.jar

(This step is for NA 10.40 and 10.50) To support NA 10.40 and 10.50, do the following:

1. Copy bc-fips.jar and bcpkix-fips.jar from <NA_Installation>\jre\lib\ext to <DataFlowProbe_Home>\ runtime\probeManager\discoveryResources\NAxxxx.
2. Copy truecontrol-client.jar from <NA_Installation>\client to<DataFlowProbe_Home>\ runtime\probeManager\discoveryResources\NAxxxx.

3. Copy ddm-na-client.jar and json.jar from <DataFlowProbe_Home>\runtime\probeManager\discoveryResources\na to <DataFlowProbe_Home>\ runtime\probeManager\discoveryResources\NAxxxx.

Create a new integration point in the Integration Studio based on the Pull Topology from Network Automation adapter as follows:

1. In UCMDB, go to Data Flow Management > Integration Studio.

2. Click the New Integration Point button. The New Integration Point dialog box opens.

3. Enter a name and description for the adapter.

4. Check the Is Integration Activated check box.
5. In the Adapter field, click the Select Adapter button. The Select Adapter dialog box opens.

6. Go to HP Software Products / Micro Focus Products > Network Automation, select Pull Topology from Network Automation, and click OK.

7. In the Adapter Properties section, define the following properties:

   Note Most of the properties listed below are assigned default values that are displayed after selecting Pull Topology from Network Automation in the previous step.

   Parameter	Description
   Credentials ID	Click the Select Credentials ID button and in the Choose Credentials dialog box, select the HP Network Automation Java Protocol to be used for connection.
   discoverDeviceGroup	This parameter indicates whether to discover Device Group CIs. The default value is true.
   NAVersion10.40	This parameter is only for NA 10.40. Set its value to true if you create the integration for NA 10.40.
   Query Topology Per Device	This parameter affects how information about devices is queried. If false, topology entities are retrieved in single queries. If true, separate query is issued to retrieve data per device. The default value is false.
   Remote JVM Arguments	The JVM parameters that should be passed to the remote process. For NA 10.40 integration, if the NA server runs on the Linux operation system, you need to add the following: -Djava.security.egd=file:/dev/urandom
   Remote JVM Class Path	The class path of the external JVM process. When integrating with NA 10.10, 10.11, 10.20, 10.21, or 10.30, replace the value of the remoteJVMClasspath with the following: ../runtime/probeManager/discoveryResources/naxxxx/*;%minimal_classpath% When integrating with NA 10.40 or 10.50, do the following: Remove all the default value. Add the following: ../runtime/probeManager/discoveryResources/NAxxxx/*; Open the file <DataFlowProbe_Home>\conf\DataFlowProbeOverride.properties, copy the value of the basic_discovery_minimal_classpath parameter to a temporary location, and remove the following: ../lib/bcprov-jdk15.jar; ../lib/lwcm.jar;../lib/lwcrypto.jar;../lib/lwssoImpl.jar;../lib/lwssoUtils.jar; Note If the DataFlowProbeOverride.properties file does not exist in your environment, use the DataFlowProbe.properties file instead. Add the rest of the value of basic_discovery_minimal_classpath that you copied to this paramter Remote JVM Class Path.
   Report Device Configuration	This parameter specifies whether the latest configuration of devices should be reported as configuration_document CIs. The default value is false.
   Run In Separate Process	This parameter enables the job to run in an external JVM process, separate from the main probe process. The default value is true and this value should not be changed.
   Data Flow Probe	This parameter defines the Probe to be used for integration. Select DataFlowProbe to explicitly choose the probe, or Auto-Select if you want the probe to be automatically selected according to where the destination IP is assigned.
   Trigger CI instance	This parameter defines the IP Address of the target NA server.

8. Click OK in the New Integration Point dialog box.

Run the full synchronization of the Network Automation by Java job with the integration point that you just created. This job performs the following internal actions:

1. Establishes a connection to the target NA server.

2. Performs a query to retrieve IDs of all devices in the system.

3. Retrieves all devices in chunks. The default chunk size is 500 devices.

4. Retrieves all ports on all devices. Depending on the value of parameter Query Topology Per Device, the ports are retrieved per device or from all devices at once.

5. Retrieves all device modules. Depending on the value of parameter Query Topology Per Device, the device modules are retrieved per device or from all devices at once.

6. Retrieves all VLANs.

7. Retrieves connections between devices. Depending on the value of parameter Query Topology Per Device, the connections are retrieved per device or from all devices at once.

8. Retrieves configuration of each device as textual data (if Report Device Configuration=true).

9. Analyzes topology. Port channels are identified with related child ports, port aliases are identified along with the parent port.

10. Reports the topology. The job forms result vectors with information about devices and their connections, while trying to not exceed 10000 objects in one vector. Vectors are sent to the UCMDB server.