There are multiple ways to incorporate the Naviate Cloud Manager refresh capability. For example, when first setting up the system and no Jobs are deployed, server refresh should not be a concern and the Server Location Refresh Filter should remain at the default setting of None. Likewise, if all Jobs are deployed to the local machine, then leave it set to Local and it should be fine. Local refresh happens extremely quickly and should present no problems.

However, if Jobs are deployed to one or more Remote servers, then it may be advisable to do a Remote refresh when first starting work to get a picture of where everything is at, then change it to Local or None for the rest of the day’s activities. If no Jobs are scheduled for execution that day, for example, then the Status Display won’t be expected to change and there need not be a wait time for server access.

Therefore, according to the following situations, here are some general recommendations:

Jobs are deployed to Remote servers

  1. Refresh Remote when first starting the system.
  2. Change the setting back to None or Local.
  3. Change it back to Remote only when necessary — for example, when viewing the status of remote scheduled Jobs or invoking Start or Stop and obtaining the most recent data is necessary.

Jobs are deployed only to the Local server

  1. Set the Server Location dropdown to Local.
  2. Refresh whenever necessary.

No Jobs are yet deployed to either Local or Remote server

  1. Set the Server Location dropdown to None.
  2. Refresh whenever necessary.