To automatically retrieve content from a Jive repository, create a new fetch task by following these steps. The connector runs each fetch task automatically, based on the schedule that is defined in the configuration file.
To create a new Fetch Task
In the [FetchTasks]
section of the configuration file, specify the number of fetch tasks using the Number
parameter. If you are configuring the first fetch task, type Number=1
. If one or more fetch tasks have already been configured, increase the value of the Number
parameter by one (1). Below the Number
parameter, specify the names of the fetch tasks, starting from zero (0). For example:
[FetchTasks] Number=1 0=MyTask
Below the [FetchTasks]
section, create a new TaskName section. The name of the section must match the name of the new fetch task. For example:
[FetchTasks] Number=1 0=MyTask [MyTask]
In the new section, set the following parameters:
Community
|
The name of the Jive community from which you want to retrieve data. |
Username
|
(Optional, depending on how the repository is configured) The user name to use to access the Jive community. |
Password
|
(Optional, depending on how the repository is configured) The password to use to access the Jive community. Micro Focus recommends that you encrypt the password before entering it in the configuration file. For information about how to do this, see Encrypt Passwords. |
(Optional) If the connector machine is behind a proxy server, you might need to specify the details of the proxy server so that the connector can access the internet. Use the following parameters:
ProxyHost
|
The host name or IP address of the proxy server that the connector must use to access the Jive community. |
ProxyPort
|
The port of the proxy server that the connector must use to access the Jive community. |
SSLConfig
|
The name of a section in the Jive Connector configuration file that specifies the SSL settings to use for communicating with the proxy server. If you do not set this parameter, the connector does not use SSL when communicating with the proxy server. |
|