
With Renga, different users can collaborate on a project published on a collaboration server:
To start collaborating:
![]() | To configure a server, launch the Collaboration Server application and follow the instructions. Click Options to specify the installation folder, server connection port, access key and polling interval. Configure a polling interval for detect and disconnect an invalid connection in time. To limit access to the server in the global network, set the Server access key. Prepare the server and client computers for collaboration by opening the port for incoming and outgoing connections in the Windows firewall. |
. You need to restart the application after changing the connection settings.
. The status Is Shared appears in the title bar.When receiving a project published on the server:
. User name must be unique. You need to restart the application after changing the connection settings.
(F5) to synchronize the project with other participants. If this option is enable sync will happen automatically.When collaborating on a project in Renga, you can sync changes:
(F5) command on the Primary Panel. All the changes that were made before sync are retained in a local copy on the user's PC, the changes are not visible for the rest participants of the project. Sync must be done by the user who made the changes, otherwise the changes will be discarded by the server. Sync changes as often as possible.After the project is published, a project journal is maintained on the server in the Renga Collaboration Server\Projects folder. The journal describes all project changes. The journal describes all project changes after publication.
A journal is also maintained on the user's computer in the %LocalAppData%\Renga Software\Renga folder, which displays user actions and changes that occurred during synchronization.
The names of the project journals on the server and on the users ' computers and the name of the project file on the server are the same.
To save the current state of the journal on disk:
menu click Open project journal.We recommend using a spreadsheet editor or business intelligence system to view the logs.
If one person changes one object parameter and a second person changes another object parameter, the changes are automatically merged and both object parameters are changed. If two people have changed the same object parameter at the same time, the Project Journal Status column is marked as a conflict and the parameter value is not changed.
The server should run smoothly. It keeps all data in RAM until all users have finished working on the project in Renga, i.e. the project is closed.
If the server fails while users are connected to collaboration, the server state after recovery is the same as the last save to disk. For this reason, we recommend installing Renga Collaboration Server on the server, monitoring its performance, and closing the project in Renga when the work is done.
When the RengaServer service is stopped and restarted, the data is saved on the drive. To create a backup of a server project on the server: