![]() |
|||||||||||||||||||||||||||||||||
|
Global Historical Data Solutions |
|||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||
| TickWrite
7 Software With TickWrite 7 users can customize their data output files by specifying:
Network Connectivity and TCP Ports for TickWrite 7 TickWrite 7 is a networked-enabled application that depends on certain network access being available in order to function properly. Network connectivity is required for both receiving updates from Tick Data, as well as normal TickWrite operation: Normal TickWrite 7 Operation: Because of the TickWrite 7 scheduler and other features, TickWrite 7 utilizes a service process that runs in the background. Therefore, even a standalone instance of TickWrite 7 still makes use of network ports. However, because connections are only made back to the same host, firewalls should almost never be a problem. Additionally, TickWrite 7 has attempted to use higher, non-standard ports to avoid conflicts with existing application. The below information on port usage is intended as a reference only and port numbers only need to be change or configured when it is shown that there is a problem or conflict. Currently, there are two static ports and two dynamic ports used in TickWrite 7 (dynamic ports are dynamically chosen at application startup based on availability on the host system). The static ports are 12092 and 12093 and they must either be available on the system or set to alternate available ports. Contact our Support Desk to learn how to configure TickWrite 7 to utilize different ports. Data Updates from Tick Data: If you subscribe to data updates from Tick Data, an Internet connection from the machine on which TickWrite 7 is installed is required (at least during the times when the updates will be run). The initial update request for updates is sent out over the HTTPS protocol to Tick Data’s update server (updates.tickdata.com). However, HTTP is not an efficient protocol for streaming large data files. Therefore, a very thin and efficient custom protocol known as TickWrite Transfer Protocol (TWTP) was developed for streaming data files down to TickWrite 7. The response to the initial HTTPS request contains a port number to which TickWrite 7 will then connect to receive the data files (via TWTP). This port is opened specifically for installation of TickWrite 7 and will only stay open while the update is occurring. This is similar to how passive FTP operates. While HTTP(S) is generally not a problem for customer firewalls, other protocols and ports can be an issue. Currently, the TWTP port that TickWrite 7 will connect to will be taken from a pool of ports ranging for 11001 – 11100. Customers should ensure that their firewalls will allow then to initiate connections to these ports on the host updates.tickdata.com (in addition to port 80 and 443 for HTTP(S)).
Download TickWrite 7 Demo with Sample Data Related Links Questions? Please contact us. |
|||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||