Table of Contents |
---|
For instructions on how to set up this architecture, see JobScheduler Universal Agent - connecting via HTTPS
...
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Explanations
This setup needs requires 2 user accounts on the Agent host:
...
- Communication between JobScheduler Master and Agent is initiated by the Master only and is restricted to the port that is specified for the HTTPS connection.
- Communication between JobScheduler Master instances for remote execution make use of a number of ports in both directions, see How to configure remote execution.
References
Change Management References
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
See also