Remote Access to a Midas experiment: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Pagelinks}} | |||
As Midas supports remote [[Frontend Operation|frontend(s)]], the method to connect the frontend to the backend is through a daemon '''[[mserver]]''' providing the necessary interface at the backend computer for accepting the frontend connection. This client requesting connection to a particular Midas experiment, will have to provide arguments such as: | |||
As Midas | |||
* The backend node name to which it wants to connect | * The backend node name to which it wants to connect | ||
* The name of the Midas experiment to connect | * The name of the Midas experiment to connect | ||
* The port through which it wants to connect (optional) | * The port through which it wants to connect (optional) | ||
Undesired nodes can be prevented from connecting to the backend by using the -a argument of the Midas server ('''[[mserver|mserver]]'''). This can provide mserver with a list of clients nodes allowed to connect to any experiment on this backend node. | |||
[[Category:Experiment]] [[Category:Frontend]] | |||
Latest revision as of 13:03, 8 July 2015
As Midas supports remote frontend(s), the method to connect the frontend to the backend is through a daemon mserver providing the necessary interface at the backend computer for accepting the frontend connection. This client requesting connection to a particular Midas experiment, will have to provide arguments such as:
- The backend node name to which it wants to connect
- The name of the Midas experiment to connect
- The port through which it wants to connect (optional)
Undesired nodes can be prevented from connecting to the backend by using the -a argument of the Midas server (mserver). This can provide mserver with a list of clients nodes allowed to connect to any experiment on this backend node.