|
Default Parameters for ShareFileBWTest
This test tracks the average bandwidth consumed on the target Citrix Content Collaboration account. Using this test, administrators can figure out bandwidth consumption patterns and identify sudden surges, if any. This test also helps administrators plan their bandwidth utilization and purchase additional bandwidth, as and when required.
This page depicts the default parameters that need to be configured for the ShareFileBWTest.
Provide the email ID of the Citrix Content Collaboration user with ‘Admin’ access to Citrix Content Collaboration in the EMAIL ID text box. The credentials of this user are necessary for connecting to the Citrix Content Collaboration REST API, running API commands, and pulling out metrics.
These parameters are applicable only if the eG agent needs to communicate with the Citrix Content Collaboration portal via a Proxy server.
In this case, provide the IP/host name and port number of the Proxy server that the eG agent should use in the PROXY HOST and PROXY PORT parameters, respectively.
If the Proxy server requires authentication, then specify the credentials of a valid Proxy user against the PROXY USER NAME and PROXY PASSWORD text boxes. Confirm that password by retyping it in the CONFIRM PASSWORD text box. If the Proxy server does not require authentication, then specify none against the PROXY USER NAME, PROXY PASSWORD, and CONFIRM PASSWORD text boxes.
On the other hand, if the eG agent is not behind a Proxy server, then you need not disturb the default setting of any of the Proxy-related parameters. By default, these parameters are set to none.
When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.
|