|
Step 1 - Host Participants and Directories |
  
|
|
Step 1 - Host Participants and Directories |
|
Once global options have been configured, create a new file collaboration job by clicking on the Create New button in toolbar of the PeerLink Hub, or by selecting the New menu item from the File menu. A drop down list of all installed Peerlet types will be displayed. Selecting the File Collaboration option will prompt you for a unique name for the job, then open the File Collaboration Configuration dialog..
The first page of configuration will be for Host Participants of the file collaboration job. On this page, you will select and configure which hosts will be participating in this job.
Participant configuration steps are as follows:
| 1. | A list of all available hosts will appear in the Available table on the top of the page. Available hosts are any host with a PeerLink Agent installed that has successfully connected to the configured PeerLink Broker. The name that will be displayed is the computer name of the server that the PeerLink Agent is running on. If a particular host is not displayed in the list then try restarting the PeerLink Agent Windows Service on that host, and if it successfully connects to the PeerLink Broker, then the list will be updated with the computer name of that host. |
NOTE: Computer Description is defined through Windows on a per-computer basis.
| 2. | Select two or more hosts from the Available table and click on the Add button to add the hosts to the Selected table. |
| 3. | For each selected host you will need to type in the path to the Root Folder, and then press enter. The Root Folder for all hosts can be identical, or they can have different absolute path names based on your needs. |
| 4. | Optionally, if you would like to exclude real time events from certain users, this can be done by selecting the desired host in the Selected table and clicking Edit Detector Settings. This is helpful if you are trying to prevent events generated from backup and/or archival tools from triggering activity. Usernames should be separated by commas. |
| 5. | If you are properly licensed to and wish to include a NetApp storage device within a file collaboration job, additional configuration is required for each selected host that is to interface with a NetApp storage device via the NetApp fPolicy API. For more information, please review the NetApp Configuration section. |
NOTE: From this point on, no other configuration items are mandatory. You can leave the rest of the configuration settings as their default values and move onto to Step 10 - Save Settings. If you wish to continue configuring the job, please continue to Step 2 - General Settings.