ROES transport Protocol Server is a Java application created to receive
incoming ROES Orders. Moving to this
new upload vehicle will avoid numerous customer service calls received by the lab. This should greatly improve
the photographer/consumer experience when using ROES and help increase your repeat business.
**The RTP Server uses low level communications for the most secure exchange of order files from the ROES Client to the lab**
Port: - Enter the port number you want the order to come into the lab on. You will create a 'port forwarding' rule in the router, sending traffic from this port to the port and internal ip address of the computer running the RTPServer application. The Port can be set to '81' or something else, such as ,'8081', '2129', '84', '8181' in most cases. If you are trying to set this for orders coming from a corporate environment (where they may have these ports blocked) you can try setting this to '51515'
SSL - Click on this box to enable the use of SSL. Clicking here will take you to a page with more information.
On completed transfer, broadcast ensemble message - This box is enabled from a checkbox on the left side of the options bar near the bottom of the window labeled “Run Ensemble”. Check this box when you want the RTP Server to broadcast the “ORDER_FILE_READY” message. Using this checkbox will also enable the “Ensemble Group:” field which you can either leave blank to broadcast to everyone, or you can enter the name of an ensemble group to limit who will get the message.
Ensemble Group: - field which you can either leave blank to broadcast to everyone, or you can enter the name of an ensemble group to limit who will get the message. This value would match the value in the ROES Server configuration pane.
Run Ensemble - Checking this box will enable the 'Ensemble' feature to send messages directly to ROES Servers when an order has completed transfer. With it selected you can then select the “On completed transfer, broadcast ensemble message” checkbox which will enable the “Ensemble Group:” field which you can either leave blank to broadcast to everyone, or you can enter the name of an ensemble group to limit who will get the message.
The message that gets sent out is “ORDER_FILE_READY” and the data that goes with it is the path to the order file. That path is as it is seen by the RTPServer so you will need to be sure that that path is seen in the same way by servers processing the message (a UNC path under windows or some common mounted path on Macs).
The server listens for the “ORDER_FILE_READY” message and upon receiving it, attempts to claim ownership of the event among the workstations which, if it fails, it does nothing further with it. If it succeeds (which exactly one of the workstations should do) then it will add it to the pending queue. The path to the file should be less than 255 characters.
Used with the 'Run Ensemble', there is a new option in the Options tab of the ROES Server called “Actively scan the incoming directory” which should be selected by default (preserving our old behavior). If you deselect this then the server, when running, will not scan the incoming directory for completed orders. You do not have to turn this off to use the new RTPServer but you can.
Max Connections: - Set this to the maximum number of customers you want to allow to connect to the RTP Server at one time. This will depend on the amount of internet bandwidth you have for the speed at which your customer can upload. The bandwidth will be divided between the number of customers connected to the RTP Server.
Max copy threads: - Set this to the maximum number of threads you want the RTP Server to spawn at one time. This is usually a one-to-one match to the "Max Connections" value so each connection will get its own thread.
Documentation version 4.3,2017/01.