To help you understand the Job Hopping plan better, let us evaluate the problem, and understand how Job Hopping Plan addresses it.
What happens in the absence of a Job Hopping Plan?
For illustrative purposes, let us assume you need to collect data from assets located in four network zones A, B, C and D. Each network zone allows only one way connectivity to the other zone, as shown in the following network map:
The connectivity between the above mentioned network zones is A > B > C > D. Zone A is not directly connected to zone C and D. Zone A contains the installation of the CCS core components, such as the CCS Application Server, CCS Console and a CCS Manager with Load Balancer role. Zones B, C and D each contain a CCS Manager that is collecting data from assets located in the respective zones. As there is only a one way connectivity between the zones, the CCS Manager load balancer Server located in zone A cannot collect data directly from assets located in zones C and D.
How does this work if you configure a Job Hopping Plan?
In this scenario, you can collect data from zones C and D by configuring an appropriate job hopping plan. The job hopping plan collects data by forwarding the request to an immediately accessible zone, as shown in the following illustration:
For example, a request for collecting data from assets in zone D, will be forwarded from zone A to zone B, then from zone B to zone C, and finally from zone C to zone D.
Collected data from an asset in zone D is sent back in the reverse sequence of the request.
Therefore, if you want to collect data from zone D, you must create a job hopping plan which forwards the data collection request through each CCS Manager located in the respective zones.
In this scenario the job hopping plan that is required is as follows:
Zone A CCS Manager Load Balancer > Zone B CCS Manager Data Collector > Zone C CCS Manager Data Collector > Zone D CCS Manager Data Collector.