Open topic with navigation

# IndexClients

DEPRECATED:

The `IndexClients` action parameter is deprecated for Coordinator version 11.5.0 and later. HPE recommends that you use authorization roles instead. See Authorization Roles Configuration Parameters.

The `IndexClients` configuration parameter is still available for existing implementations, but it might be incompatible with new functionality. The parameter might be deleted in future.

The IP addresses or host names for machines that are permitted to index data into IDOL Server (using the specified IndexPort). Separate multiple addresses with a comma. There must be no space before or after a comma.

You can use wildcards in the IP addresses. For example, type `187.*.*.*` to permit any machine whose IP address begins with `187` to access the service's status. You can also filter the `IndexClients` parameter using CIDR notation.

NOTE:

If you want to use the Controller and Coordinator servers to run and track index commands, you must configure your Coordinator server as an index client by specifying the host name or IP address of the Coordinator server as the value of the `IndexClients` parameter. For example, if the host name of your Coordinator server is `WIN-IAA62SFQQCV`, edit your Controller configuration file as shown below:

    [IndexProxy]
    Port=41201
    IndexClients=WIN-IAA62SFQQCV

You must implement this change in the configuration file for each of your Controller servers.

Type: | String
Default: | None
Required: | No
Configuration Section: | IndexProxyor Server
Example: | `IndexClients=10.1.1.10,127.0.0.1`
See Also: | IndexPort

© 2015-2017 Hewlett Packard Enterprise Development LP | Send documentation feedback to HPE Close Send documentation feedback To open the configured email client on this computer, open an email window. Otherwise, copy the information below to a web mail client, and send this email to AutonomyTPFeedback@hpe.com. We appreciate your feedback! Product: Topic Title: Help Topic: Feedback:

_HP_HTML5_bannerTitle.htm