Data Flow Probe Installation Guide

HPE Operations Manager i

Software Version: 10.63

 

Install the Data Flow Probe

The Data Flow Probe is a prerequisite for creating connected servers for the APM-OMi integration. For more information on this integration, see the OMi Integrations Guide . For detailed information on installing the Data Flow Probe, see the UCMDB Help.

The following sections provide step-by-step instructions to install, update, start, and manage the Data Flow Probe:

Download the installation files

Download the Data Flow Probe installation .zip file to the system that you want to install or update. The .zip file contains installation files for Linux and Windows:

Linux: Software/Linux/UCMDB_DataFlowProbe_10.33.811.bin

Windows: Software\Windows\UCMDB_DataFlowProbe_10.33.811.exe

Optional. Enable internal secure communication in OMi

If OMi is configured to use HTTP, you have to manually enable OMi's internal secure communication before installing the Data Flow Probe:

  1. Run the following command on your OMi system (in a distributed environment, run the script on the primary gateway server):

    Linux: <OMi_Home>/opr/support/enableOdbInternalSSL.sh

    Windows: <OMi_Home>\opr\support\enableOdbInternalSSL.bat

  2. Restart OMi.

You can then install or update the Data Flow Probe as described below.

Install the Data Flow Probe

Complete the following steps to create a new installation of the Data Flow Probe. If an earlier version of the Data Flow Probe is installed with OMi 10.x, you must uninstall the older version and install version 10.33.811 as described in Update an existing Data Flow Probe installation.

The Data Flow Probe can be installed anywhere. It must be able to establish a connection to the OMi 10.63 gateway server and the APM server.

You can install multiple Data Flow Probes, one on each server; each Data Flow Probe can connect only to exactly one OMi gateway server.

Note: To install the Data Flow Probe on Red Hat Linux 7, you must first create a symbolic link from libsasl2.so.3.0.0 to libsasl2.so.2 before installing the Data Flow Probe. For example:

cd /usr/lib64/

ln -s ./libsasl2.so.3.0.0 ./libsasl2.so.2

  1. Execute the installation file depending on the operating system:

    Linux: Software/Linux/UCMDB_DataFlowProbe_10.33.811.bin

    Windows: Software\Windows\UCMDB_DataFlowProbe_10.33.811.exe

    Note: To execute the Installer, you require a system with GUI.

    A splash screen is shown.

  2. Choose a language from the drop-down menu and click OK to continue.

  3. The installation wizard is shown. For every page, complete the necessary information and click Next to go to the next page. On the last page click Install to install. You can click Cancel at any time to abort the installation.

    • Introduction: Shows the Welcome screen.

    • License Agreement: Shows the License Agreement for using the Data Flow Probe. Click I accept… to agree to the given terms.

    • Setup Type (Windows only): Leave the selection on the default option Full Data Flow Probe Installation.

    • Select Installation Folder: A different installation path from the default one can be chosen by entering the path manually in the text field, or clicking Choose… to open the file explorer. Clicking Restore Default Folder restores the default installation path.

      Note: If you install the Data Flow Probe on an OMi gateway server, make sure to choose an installation path different from the OMi installation path.

    • Probe Configuration (1): To connect the Data Flow Probe to OMi 10.63, choose HP BSM as the option for Application to report to:. In the Application Server address field, enter the FQDN of the OMi 10.63 gateway server. If a load balancer is used, this should be the FQDN of the load balancer.

      In the Data Flow Probe address box, enter the IP address or FQDN of the machine on which the Data Flow Probe is currently installed, or accept the default.

    • Probe Configuration (2): Data Flow Probe identifier is the display name of the Data Flow Probe. This name will later be shown in the OMi 10.63 GUIs to identify it.

      Every Data Flow Probe also falls under a so-called domain. If Use Default UCMDB Domain is selected, the Data Flow Probe is created under the DefaultDomain domain. If it is cleared, a custom domain name can be created in the next step.

      Note: The name of the domain is required later when creating an APM connected server.

    • Probe Domain Config (shown only if Use Default UCMDB Domain is selected in the previous step):

      The Data Flow Probe domain type can be left on the default option Customer. The Data Flow Probe domain name can be changed by using the text box. DefaultDomain is the default value.

    • Probe Working Mode (Windows only): The selection can be left to the default option.
    • Probe Memory Size: The selection can be left to the default option.
    • Account Configuration(1): Create the password for the Data Flow Probe internal PostgreSQL Data Flow Probe account.

      The password must contain upper case, lower case, and numeric characters. Do not use special characters other than the period.

    • Account Configuration(2): Create the password for the Data Flow Probe internal PostgreSQL root account.
    • Account Configuration(3): Create the password for the system administrator (sysadmin) account.
    • Scan File Upload Config: Create the username (can be left to default) and password for uploading scan files.
    • Pre-Installation Summary: Displays the product name (always: HP UCMDB Data Flow Probe), the Installation Folder, and disk space information. Click Install to start the installation.

    • Installing…: Shows the progress of the installation and what is currently being installed. The install log file can be found at:

      <DFP install folder>/UninstallerData/Logs/HP_UCMDB_Data_Flow_Probe_Install_<date and time>.log

  4. Linux only. After the installation, edit the <Data Flow Probe install folder>/conf/DataFlowProbe.properties file.

    Change the appilog.agent.probe.integrationsOnlyProbe parameter to false:

    appilog.agent.probe.integrationsOnlyProbe = false

  5. Only if TLS is enabled in OMi. If your OMi 10.63 installation is configured for TLS, you must manually reimport the corresponding certificates to the Java keystore of the Data Flow Probe.

    Note: To get the OMi gateway server certificate, run the opr-cert-mgmt CLI. For more information, see Export OMi server certificates.

    Import the OMi gateway server certificate into JRE’s trust store:

    <Data Flow Probe install folder>/bin/jre/bin/keytool -import -trustcacerts -file <CA cert>.pem -alias <ca cert alias> -keystore <Data Flow Probe install folder>/bin/jre/lib/security/cacerts

    When prompted for the password, enter the default password: changeit

  6. Only if TLS is enabled in APM. If APM is configured for TLS, you must manually reimport the corresponding certificates to the Java keystore of the Data Flow Probe.

    Import the APM server certificate into JRE’s trust store:

    <Data Flow Probe install folder>/bin/jre/bin/keytool -import -trustcacerts -file <CA cert>.pem -alias <ca cert alias> -keystore <Data Flow Probe install folder>/bin/jre/lib/security/cacerts

    Import the APM server certificate into the HPProbeTrustStore.jks trust store:

    <Data Flow Probe install folder>/bin/jre/bin/keytool -import -v -file <APM>.crt -alias <APM> -keystore <Data Flow Probe install folder>/conf/security/HPProbeTrustStore.jks

  7. Only if TLS is disabled in OMi or APM. If OMi or APM are configured to use HTTP, edit the file <Data Flow Probe install folder>/conf/DataFlowProbe.properties.

    Change appilog.agent.probe.protocol from HTTPS to HTTP and serverPortHttps from 443 to 8443.

  8. Start the Data Flow Probe. For details, see Start the Data Flow Probe.

Update an existing Data Flow Probe installation

Updating an existing Data Flow Probe installation involves uninstalling the old version and installing the new version (10.33.811). The uninstallation deletes all of the customizations you applied to the Data Flow Probe. You must therefore make a backup of the old Data Flow Probe system so that you can reapply your changes after the installation:

  1. Make a backup of the Data Flow Probe system so that you can restore your customizations after the installation of the new version.

  2. Uninstall the old version of the Data Flow Probe. For details, see Uninstall the Data Flow Probe.

  3. Install the Data Flow Probe version 10.33.811. For details, see Install the Data Flow Probe.

  4. Reapply your customizations, for example:

    • Restore any changes you applied to the Data Flow Probe configuration file:

      <Data Flow Probe install folder>/conf/DataFlowProbe.properties

      For example, if APM or OMi is configured to use HTTP, you must change appilog.agent.probe.protocol from HTTPS to HTTP and serverPortHttps from 443 to 8443.

      Note: Do not copy the old DataFlowProbe.properties file from your old installation to the new installation. The old file is not compatible with the new version because the new version introduces new parameters and sets new default values.

    • If APM or OMi are configured for HTTPS, you must manually reimport the corresponding certificates to the Java keystore of the Data Flow Probe:

      1. Import the OMi gateway server certificate into JRE’s trust store:

        Note: To get the OMi gateway server certificate, run the opr-cert-mgmt CLI. For more information, see Export OMi server certificates.

        <Data Flow Probe install folder>/bin/jre/bin/keytool -import -trustcacerts -file <CA cert>.pem -alias <ca cert alias> -keystore <Data Flow Probe install folder>/bin/jre/lib/security/cacerts

      2. Import the APM server certificate into JRE’s trust store:

        <Data Flow Probe install folder>/bin/jre/bin/keytool -import -trustcacerts -file <CA cert>.pem -alias <ca cert alias> -keystore <Data Flow Probe install folder>/bin/jre/lib/security/cacerts

      3. Import the APM server certificate into the HPProbeTrustStore.jks trust store:

        <Data Flow Probe install folder>/bin/jre/bin/keytool -import -v -file <APM>.crt -alias <APM> -keystore <Data Flow Probe install folder>/conf/security/HPProbeTrustStore.jks

  5. If the Data Flow Probe identifier is not changed, the RTSM automatically recognizes the updated Data Flow Probe and starts the synchronization jobs.

    If the Data Flow Probe identifier is changed, you must manually update the probe name, for example:

    • Edit the Data Flow Probe in Administration > RTSM Administration > Data Flow Management > Data Flow Probe Setup and replace the old name with the new name.

    • Edit the APM connected server in Administration > Setup and Maintenance > Connected Servers. In the Synchronization page, select the Data Flow Probe from the drop-down list.

  6. Start the Data Flow Probe. For details, see Start the Data Flow Probe.

Start the Data Flow Probe

You can start the Data Flow Probe by using one of the following methods:

Note: During startup, the Data Flow Probe synchronizes with OMi and takes a few minutes to be fully started.

Manage the Data Flow Probe

Access Data Flow Probe Setup in OMi 10.63 to manage the Data Flow Probe:

Administration > RTSM Administration > Data Flow Management > Data Flow Probe Setup

If the Data Flow Probe is correctly connected, the domain for which it is created is shown under the Domains and Probes root node, for example, DefaultDomain (Default). Under this domain are two more nodes, Credentials and Data Flow Probes. Under Data Flow Probes, the newly created Data Flow Probe with the given Data Flow Probe name should be shown.

If the status of the probe is running, symbolized by the triangle icon on the left of the Data Flow Probe name, the Data Flow Probe is working correctly.

Uninstall the Data Flow Probe

To uninstall the Data Flow Probe use one of the following methods:

Windows: <Data Flow Probe install folder>/UninstallerData/Uninstall_Discovery_Probe.exe

Windows: Use the generated start menu entries.

Linux: <Data Flow Probe install folder>/UninstallerData/Uninstall_Discovery_Probe

Troubleshooting and additional help

Log files

Check the following log files:

Export OMi server certificates

To get the OMi server certificates that you need to import, use the opr-cert-mgmt command-line interface:

<OMi_HOME>\bin\opr-cert-mgmt.[bat|sh] -export <alias> PEM <location>

The CLI exports the certificate with the specified alias to the specified location.

For more information on how to use the opr-cert-mgmt CLI, see the OMi Extensibility Guide.


Legal Notices

Warranty

The only warranties for Seattle SpinCo, Inc and its subsidiaries (“Seattle”) products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Seattle shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Except as specifically indicated, valid license from Seattle required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notice

© Copyright 2015-2017 EntIT Software LLC, a Micro Focus company

Trademark Notices

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

AMD, the AMD Arrow symbol and ATI are trademarks of Advanced Micro Devices, Inc.

Citrix® and XenDesktop® are registered trademarks of Citrix Systems, Inc. and/or one more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries.

Google™ and Google Maps™ are trademarks of Google Inc.

Intel®, Itanium®, Pentium®, and Intel® Xeon® are trademarks of Intel Corporation in the U.S. and other countries.

iPad® and iPhone® are trademarks of Apple Inc.

Java is a registered trademark of Oracle and/or its affiliates.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

Microsoft®, Windows®, Lync®, Windows NT®, Windows® XP, Windows Vista® and Windows Server® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

NVIDIA® is a trademark and/or registered trademark of NVIDIA Corporation in the U.S. and other countries.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates.

Red Hat® is a registered trademark of Red Hat, Inc. in the United States and other countries.

SAP® is the trademark or registered trademark of SAP SE in Germany and in several other countries.

UNIX® is a registered trademark of The Open Group.


Send documentation feedback to HPE