This persistent connection operates even when separated by a Firewall. The advantage of this method is that it is possible to use the Studio Integration on several nodes at once. For example, to debug an entire cluster of machines behind a load-balancer using only a single debugger connection to Platform's Studio Server component.
The technology is based on two functional elements:
The Studio that includes an internal Web server that listens on the local host on a specific Auto Detection port.
Platform auto-evaluates Studio’s Auto Detection port, by evaluating Studio’s settings. These are the Tunnel Settings defined in Platform.
To establish a communication tunnel between Platform and Studio:
Go to: Platform | Preferences.
Communication Tunnel Method
In the Platform Settings section, enable Auto detect the Studio Settings by clicking On.
This informs Platform of the method of connection to Studio. The relevant options/fields for configuring Tunneling are as described below:
Auto Detection Port - Indicates that Studio will listen to the local host on the signified Auto Detection port - Default=20080. Leave empty to automatically identify the IP from the browser.
Test - Verifies if Studio is listening to this port. This test should only be run when Studio is running.
Method of passing the Studio Server parameters - Defines the means for passing communication parameters from the Platform to Studio. Choose COOKIE or GET method.
|
|
|
|
|
Configure communication as follows:
|
|
Note: The default method is Cookie, and it is recommended that you use the default. Platform supports a Get method as well that can be used if experiencing problems with Cookies. Platform establishes a communication tunnel with Studio based on the default detection port. Note: Tunneling to Debug and Profile code with the Studio is only possible if Studio is open and running and Studio’s Tunneling settings are properly configured in Platform and Studio. |
|
|
|
|
|
|
Related Links: |
|
|
|
