Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 10

changes.mady.by.user Victor Garcia-Beltran

Saved on

compared with

New Version 11

changes.mady.by.user Victor Garcia-Beltran

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • One JobScheduler Master is running.
  • N different servers, where K JobScheduler Universal Agent instances have to be installed on each server. 
  • The ports where the JobScheduler Universal Agents will be running are the NOT the same ones  the same ones, by what is meant within the ports taken for the same server, in case more than one instance will be installed on the same Agent Server.
  • The users, which the JobScheduler Universal Agents is running under are NOT named  named the same.
  • There has been no previous JobScheduler Universal Agents installations on the N servers.

...

Let be the following scenario:

  • One JobScheduler Master is running.
  • N different  different servers, where where K JobScheduler  JobScheduler Universal Agent instances have to be installed on each server. 
  • The ports where the JobScheduler Universal Agents will be running are the NOT the same ones the same ones, by what is meant within the ports taken for the same server, in case more than one instance will be installed on the same Agent Server.
  • The users, which the JobScheduler Universal Agents is running under are NOT named  named the same.
  • It is NOT a  a fresh installation, but it is an update of the JobScheduler Universal Agents that have been already installed on the servers.

...