Installing the Data Fabric Client (Non-FIPS)

This section describes how to prepare the client machine for the installation process in a non-FIPS environment.

In a FIPS or mixed FIPS/non-FIPs environment, special procedures are required to configure clients. If your environment is FIPS or mixed FIPS/non-FIPS, see Installing the Data Fabric Client (FIPS).

CAUTION Do not attempt to install Ecosystem Pack (EEP) service components on client machines. Client machines do not have the service-management framework required to host the service components.

Before you install the data-fabric client, perform the following steps:

  • Verify that the operating system on the machine where you plan to install the client is supported. For a list of operating systems that are compatible with the data-fabric clients, see Client Support Matrix.
  • Verify that the machine where you plan to install the client is not a cluster node. The data-fabric client is intended for use on a computer that has no other data-fabric server software installed.
  • Ensure that the hostname of the machine is set to a fully qualified DNS name. This is critical as else will fail to generate SSL keys.
  • Obtain connectivity information and cluster setup requirements. When you use to configure the client, you will need to know the following details:
    • The cluster name. You will need the cluster name when you specify the -N parameter.
    • The IP addresses and ports of the CLDB nodes on the cluster. You will need this information when you specify the CLDB nodes with the -C parameter.
    • If one or more nodes in the cluster run the ResourceManager, you may need to specify the hostname or IP address for each ResourceManager nodes using the -RM parameter. If the cluster is configured to use zero-configuration failover, do not specify the ResourceManager nodes. If the cluster is not configured to use zero-configuration failover, specify each ResourceManager node.
    • Determine if the cluster is secure. If the cluster is secure, you will need to specify the -secure parameter when you run
    • If a node in the cluster runs the HistoryServer, note the hostname for the HistoryServer. You must specify each HistoryServer node using the -HS parameter.
  • Add the hostname mapping. In the /etc/hosts file of the client machine, add a mapping between the CLDB nodes in the cluster and the IP addresses of those nodes. For example, add the IP address and CLDB node name centos22 on the Mac OSX where you installed the client:       localhost broadcasthost
    ::1             localhost
    fe80::1%lo0     localhost     centos22
  • Configure repositories for the client. The client nodes also need to have the data-fabric repositories configured in order to pull the client packages. See Data Fabric Repositories and Packages.

To install the client, obtain the data-fabric packages for your operating system at and complete the installation steps described in one of the subsequent topics.