Hunter policy

A Hunter policy contains the connection details that are used by a Hunter Request node when you connect to the Hunter application.

Use a Hunter Request node to connect to Hunter and issue requests to create, retrieve, update, or delete the annotation object. The Hunter policy controls, at run time, access to the Hunter application.

The Hunter policy is created when you configure a connection between a Hunter Request node and Hunter by using the Connector Discovery wizard. During the process of discovery, account credentials are stored in the vault and connection details are stored in a Hunter policy. The policy is created with a type of Hunter, and the name of the policy is returned to the node and specified in the Connection tab, in the format {policyProjectName}:policyName.

You can also create, update, or delete a Hunter policy by using the Manage Discovery Connector Policies and Credentials wizard, which you can access by right-clicking the policy project in the IBM® App Connect Enterprise Toolkit and then clicking New > Discovery Connector policies and credentials.

You must deploy this policy before message flows that use the policy are started. If you redeploy a Hunter policy, all message flows that are using the policy will be stopped and restarted.

For more information about using Hunter, see Using Hunter with IBM App Connect Enterprise.

Table 1. Properties of the Hunter policy
Property Property name in .policyxml file Description of properties
Hunter Application Type applicationType This property is reserved for future use and must be set to the value online.
Hunter Application Version applicationVersion This property is reserved for future use and must be set to the value v1.
Hunter Authentication method authenticationMethod This property specifies the type of authentication that is used for the connection between IBM App Connect Enterprise and Hunter. This value is reserved for future use and must be set to BASIC_API_KEY.
Server URL apiUrl Specify the URL for the API server that makes runtime calls.
Allow self-signed certificates isTlsEnabled

Set to true if you want to be able to accept self-signed certificates that are trusted and used only in a nonproduction environment. The default is false.

Override server URL endpointUrl Required if you want to connect to an endpoint in a private network by using the private network client, or if you want to override the server URL. Specify an override value for the host and port for the connector in the format <http or https>://<host_name>:<port>. If you are not using the private network client or do not require an override, leave this field blank.
Credential Name credentialName The name of your Hunter account. For example, hunterpolicy_Hunter1