Using static ports in Engine and Driver DDT settings
Article ID: KB0086577
Updated On:
| Products | Versions |
|---|---|
| TIBCO DataSynapse GridServer | - |
| Not Applicable | - |
Description
Resolution:
For DDT communication between Drivers and Engines, you can use fixed ports on both sides.
On the Engine side, the port is set in the Engine Configuration, which you can edit on the Director, in the Engine Configuration page. The default behavior is to use a fixed port (typically 27159, but it can be changed).
On the Driver side, you can change the port in the driver.properties file, using the DSWebserverPort property. The default in driver.properties is 0, which yields an ephemeral port. You can set this to any port number. If you run multiple Drivers on the same machine, you'll need to specify multiple ports in multiple driver.properties files. For SOAP services, you will use the embedded Driver's driver.properties file on the Manager, in webapps/livecluster/WEB-INF/config. Restart the Manager to have the change take effect.
For DDT communication between Drivers and Engines, you can use fixed ports on both sides.
On the Engine side, the port is set in the Engine Configuration, which you can edit on the Director, in the Engine Configuration page. The default behavior is to use a fixed port (typically 27159, but it can be changed).
On the Driver side, you can change the port in the driver.properties file, using the DSWebserverPort property. The default in driver.properties is 0, which yields an ephemeral port. You can set this to any port number. If you run multiple Drivers on the same machine, you'll need to specify multiple ports in multiple driver.properties files. For SOAP services, you will use the embedded Driver's driver.properties file on the Manager, in webapps/livecluster/WEB-INF/config. Restart the Manager to have the change take effect.
Issue/Introduction
Using static ports in Engine and Driver DDT settings
Feedback
Yes
No
Powered by
