RTP Server - Setup & Testing

This article applies to the ROES Transport Protocol Server (RTP Server)

To begin using RTP for order transmissions from the ROES Client, you must first set up the RTP Server.

Install and Configure the RTPServer

1. Choose a customer, local, outbound port that isn't normally blocked by most customers network systems.  This assures the ROES Client will be able to use the port when sending the order. The ports called out on ROES-U are a sample of those most often used. ('8081', '2129', '84', '8181' & '51515')

2. Create a port forwarding rule on the labs router.  The rule will forward a ports traffic from the external IP address to the internal IP address of the computer you chose to run the RTP Server.  There are many types of routers and you will need to either know how to do this or have someone with IT knowledge configure the router for you.  Google your brand of router and port forwarding how-to.

3. Select the computer that will run the RTPServer.  This can be the same computer that is running the ROES Server but can be any computer that has network connectivity back to the ROES Server.

4. Install and launch the RTP Server using this link. (http://www.roeslaunch.com/ROES/RTPServer/index.html?)

5. Enter the port(s) you have chosen.

6. Enter the path to the folder being watched by the ROES Server.  This is usually labeled as the 'Incoming' or 'Search' folder.

7. Set the Max Connections and the Max copy threads both to 20.  This can be increased depending on the internet bandwidth available at your lab and the number of customers you expect to be connecting at one time.

8. Start the RTP Server and watch for the spinner/pinwheel movement to confirm it is running.



Next, you need to let the ROES Client know where to send the order



Setup the ROES Client to Send to the RTP Server

1. Download the Example Templates file (https://www.roes.co/Training/RTP/RTPServerFiles/RTP.zip).

2. Open it with the Template Tool Utility and locate a Configuration element/icon 'FTP config' inside or outside of one of the catalogs.

3. Use the example templates file as a guide for adding the 'rtpuri' attribute to your templates file.  This will be in the Configuration element of your ROES Client(s) template file(s), enter your external IP address and port.  ** rtpuri="" -- (Labs PublicIP):(Port)

**Note**. You can also find your public/external ip address using this link (https://www.whatismyip.com/)

4. Save the changes to your templates file and upload

5. Launch your ROES Client, create a test order and send it, watching the upload for a success message.

6. Watch the RTP Server for a connection and a .ro file transmission to the Incoming directory.



Finally, "Why didn't it work?"


What if I don't see anything happening?  Or the order isn't in the 'Incoming' folder?

1. Is the RTP Server turned on?  Look at the pinwheel/spinner at the bottom of the RTP Server...is it turning?

2. If it is, is the folder path correct and you have permissions to write to it?

3. If it is, re-examine the routers port forward rule for correct configuration.

4. Verify the templates file was updated with the external IP address and the port values. Look in the 'rtpuri' attribute of the templates file found in the .roescache of the computer you used to send the test order.

5. Verify the correct IP address was used in the router. Verify the RTP Server computers IP address using the command 'ipconfig /all' from a commands window.

6. Verify the external IP address by Googling "What is my IP" on the RTP Server computer and selecting one of the returned sites.

7. Did the order go to my old FTP Server?  If so, the ROES Client isn't updated properly in the templates file or the Client wasn't relaunched to get the new information.



Notes: You may want to leave your FTP Server running for several weeks to catch orders from customers that haven't relaunched the ROES Client since you made the change to RTP Server. 


Article Details

Article ID: