ROES Server - Moving or Adding a ROES Server
Replicate an Existing ROES Server on a New Computer
Use this article when moving or replicating an existing ROES Server onto a new computer, including backup, preference cleanup, order directories, database rebuild, and test-order verification.
Before Adding a Second ROES Server
If you are adding a ROES Server in your lab, review the database requirements and tips for configuring a second ROES Server before proceeding: ROES-U MultiDatabaseConfig.
1. Back Up the Existing or Primary ROES Server
Use ROESHelp article 33 to back up the existing ROES Server: ROESHelp article 33.
2. Launch and Close ROES Server on the New Computer
If this is a new computer, make sure Java is installed. The database is served up using a Java process.
- Install and launch the ROES Server application on the new computer.
- For PC, the launch page format is:
- For Mac, the launch page format is:
Close the new ROES Server after launching it. This creates the default folders and files on the new computer.
3. Replicate the Existing ROES Server
Move and extract the backup
Take the backup zip file to the new computer and extract the files to a folder.
Edit SARPreferences.xml
Find SARPreferences.xml in the extracted folder and open it in a text editor.
Search for uid. It may look similar to:
Remove the value between the double quotes so it becomes:
Save the file.
Copy files to the new ROES Server folder
Copy the full contents of the extracted folder, including all files and folders, into the .ROESServer folder or similarly named folder on the new computer. Use the path guidance from article 33.
4. Move the Order Directories
If the order directories, such as Finished Orders, Working Files, and Order Images, are being moved, modify the paths in the Order Directories tab to reflect the new location. UNC paths are strongly encouraged. **NOTE: Create a folder named "ROES" and share it with permissions for 'everyone' on the new computer**
5. Rebuild the Database
If the ROES Server is a single instance with no other ROES Server on the network, or if you want to start using a new or multi-connection database, rebuild or build the database. At the bottom of the Options tab, use Scan Working Directory for Orders not in Database. This scans the order.xml files in the Working Files folder and rebuilds the database. The scan may take some time depending on how many orders are in Working Files.
6. Assign the Current Order Number
In the 123 Order Numbers tab, with ROES Server stopped, use Set Next Sequence Number... and set the next order number that should be assigned to the next processed order.
Close ROES Server to Save Changes
Closing ROES Server performs a save operation to preserve the changes made above.
After closing, relaunch ROES Server.
7. Submit a Test Order
Create a test order to the Incoming folder and follow it through production. Verify that the correct order number is assigned, reports are created, emails are sent, and the order processes as expected.
Expected Result
You should now have a new ROES Server that is a replicate or duplicate of the existing ROES Server.
Helpful Links
- ROES-U MultiDatabaseConfig
Source link for database requirements and tips for configuring a second ROES Server. Display text in source: https://www.roes-u.com/MultiDatabaseConfig - ROESHelp article 33
Referenced backup article for the existing ROES Server. - ROES Server PC installer format
Source href used a lab-specific launch.msi URL; source text described the generic path as http://www.roeslaunch.com/ROES/SAServer/labs/<labname>/launch.msi. - ROES Server Mac installer format
Source text included this Mac launch.dmg path without an href.
Escalation Notes
- Before configuring multiple ROES Servers, review the database requirements for multi-workstation or multi-server use.
- Always back up the existing ROES Server before copying or changing files.
- Make sure SARPreferences.xml has the old uid value cleared before copying it into the new server folder.
- Use UNC paths for moved order directories whenever possible.
- Rebuild the database when the new server is a single instance or when starting a new or multi-connection database.
- Always submit and follow a test order after migration to confirm order numbers, reports, emails, and production flow.