Lab Frequently Asked Questions

What are the system requirements to run the ROES Server?
What do I need to do to become a ROES Site?
Our lab doesn’t have an internal FTP server, what can we do?
What can additional launch configurations be used for?

What are the system requirements to run the ROES Server?

The ROES DP2 Server can be run on any DP2 Workstation – if the system can run DP2 it can run ROES. Windows 2000 or higher is recommended however we advise not running the ROES DP2 Server on the DP2 Server itself. A system running the ROES Stand Alone Server should be a minimum 1.8GHz speed processor with at least 1GB RAM and have the latest Java Runtime loaded from Sun, available here. Any Java capable system can be used, so Apple OS X 10.3 or higher, Linux, and all current versions of Windows will support the application. For either server, expect to need a good amount of drive storage for order processing and storage of images. A small lab could get by starting out with 250GB in free space; a larger site will want to invest in drive banks/arrays offering expandability to multiple terabytes as well as fault tolerance.

What do I need to do to become a ROES Site?

Once you have decided to become a ROES Site, we will send you a software license agreement covering the modules you wish to start with. You will need a system to act as an FTP Server to receive order files (hosted sites not recommended) and set up a folder on your web site to host your templates files. All ROES Sites get 2 unlimited use ROES Client launch configurations plus 1 test configuration (for testing new products in your test templates file or add-on modules). In order to configure your branded clients, please provide us with the following:
  1. Your FTP Server address and drop folder designation if not using the root FTP home.
  2. FTP login information – you can set a universal login for all customers to use and issue it by request (prevents unknown persons from sending orders in); create separate login accounts for each customer by request (though you may end up needing to maintain a lot of accounts); or provide us with the universal login and have it coded into the client launch (so customers will not need to know it).
  3. Your state and sales tax rate.
  4. A file containing an icon that you would like to use for the application. This will appear in the Windows task bar and will also be used on the desktop if they create a shortcut. This should be a 128 x 128 pixel GIF or JPG File. If you would like to able to change this image yourself you can just send a URL to where you will keep the image on your lab’s web server.
  5. A file containing your logo, banner, or whatever other image you would like to have displayed across the top of the main client window and index page. This file should also be a GIF, JPG, or PNG and be a maximum of 800 x 125 to preserve a good workspace in the application. .If you would like to able to change this image yourself you can just send a URL to where you will keep the image on your lab’s web server.
  6. Additional information to capture at client startup from customers, such as phone number, address information, ftp login/password, Tax Exempt status/ID, etc. Default fields currently required in the client are Account Number, Name, E-mail address, and State.
  7. Payment types you would like to offer to customers, such as charge to lab account, COD, Pick up and pay at lab, credit cards with data collected to be charged at the lab, or credit cards to be authorized before the order transmits to the lab. Online authorizers currently include Authorize.net, PayFlow Pro, PAYFuse XML, USA E-Pay, GoEMerchant.com, and Paymentech.
  8. After training on our Template Tool application, the URL to where your templates file will be stored on your web site.

Our lab doesn’t have an internal FTP server, what can we do?

Hosting an FTP Site is easier – and less costly – than you might think. As long as you have a static IP address at your lab (check with your ISP), you can create an FTP Server on any Windows Server (NT, 2000, 2003) or 2000/XP Pro PC system. Windows offers the built-in Microsoft Internet Information Services (IIS), which can be added (from your Windows CD) via Add/Remove Programs in Control Panel under Windows Components. However, as IIS is constantly being attacked by hackers looking to find new security holes, there are numerous add-on programs you can use. BulletProof FTP ($35) and CuteFTP are both inexpensive FTP Server host options you can use. If you need to go with a hosted FTP site, there are 2 issues to be aware of: 1) You will need to pull down (via script or manually) the order files to your local network to pull into ROES for processing; 2) There can be occurrences of pulling down a partially uploaded order, causing the file to error out upon processing and likely requiring the customer to re-transmit.

What can additional launch configurations be used for?

While your first client launch build may be suitable for the majority of your pro photographer clients, you can use the 2nd launch to target a particular market segment. Focusing a client branding or product list to studio-corrected work, wedding albums, sports or schools can drive up business. Additional ROES Clients can even be branded for a particular studio or large customer. Please call us for more information.