RTP Server - Setup & Testing
Set Up RTP Server for ROES Order Transmission
This article applies to the ROES Transport Protocol Server (RTP Server) and explains how to set up RTP for order transmissions from the ROES Client.
Install and Configure the RTP Server
Choose a customer-accessible outbound port that is not commonly blocked by customer network systems. This helps ensure the ROES Client can use the port when sending orders. Example ports often used are 8081, 2129, 84, 8181, and 51515.
Create a port forwarding rule on the lab’s router. The rule should forward traffic from the external IP address and selected port to the internal IP address of the computer that will run RTP Server. Router setup varies by manufacturer, so this may require someone with IT knowledge.
Select the computer that will run RTP Server. It can be the same computer running ROES Server or any computer that has network connectivity back to the ROES Server.
Install and launch RTP Server using this link: RTP Server Download / Launch Page
If this image does not display, open it directly: RTP_Setup.png
Enter the port or ports you selected.
Enter the path to the folder watched by ROES Server. This is usually labeled the Incoming or Search folder.
Set Max Connections and Max copy threads both to 20. These values can be increased depending on the internet bandwidth available at the lab and the number of expected simultaneous customer connections.
Start RTP Server and watch for spinner or pinwheel movement to confirm it is running.
Next, you need to let the ROES Client know where to send the order.
Set Up the ROES Client to Send to RTP Server
Download the example templates file: RTP.zip
Open the example file with Template Tool and locate a Configuration element/icon (FTP config) either inside or outside one of the catalogs.
Use the example templates file as a guide for adding the rtpuri attribute to your template file. This is added in the Configuration element of your ROES Client template file.
Enter your public external IP address and port number.
You can also find your public external IP address using: WhatIsMyIP.com
If this image does not display, open it directly: RTP_Templates.png
Save the changes to the template file and upload it.
Launch the ROES Client, create a test order, and send it while watching for a successful upload message.
Watch RTP Server for a connection and a .ro file transmission into the Incoming directory.
If this image does not display, open it directly: RTP_RecieveOrder.png
Finally, “Why didn’t it work?”
Troubleshooting: No Activity or No Order in Incoming Folder
- Is RTP Server turned on? Look at the pinwheel or spinner at the bottom of the RTP Server window. Is it turning?
- If it is running, is the watched folder path correct and do you have permission to write to that location?
- Re-examine the router port forwarding rule for correct configuration.
- Verify the template file was updated with the correct external IP address and port values. Check the rtpuri attribute in the template file found in the .roescache of the computer used to send the test order.
- Verify the correct internal IP address was used in the router configuration. Check the RTP Server computer’s IP address using ipconfig /all from a command window.
- Verify the external IP address by searching “What is my IP” from the RTP Server computer and checking one of the returned sites.
- If the order went to the old FTP Server, the ROES Client was not updated properly in the template file, or the client was not relaunched to get the new configuration.
Notes
You may want to leave your FTP Server running for several weeks to catch orders from customers who have not relaunched the ROES Client since the change to RTP Server was made.