One server must be running the OnBase Client with the following command line switch:
-RIMSERVER
This command line switch is used to process Records Management retention plans and event sets with timed delay periods, where the database server's date/time is used as the point of reference. Without a Records Management server running, events that have timed delay periods can be posted (either manually or automatically using OnBase Workflow), but the events will not be processed.
Retention plans that are configured using time-based transitions instead of events will not transition without the -RIMSERVER switch. When posted in the OnBase Client, immediate events, or events that have no timed delay period associated with them will be processed immediately. When posted in the OnBase Unity Client or Web Client, immediate events will require one OnBase Client machine running the -RIMSERVER switch for events to be processed.
For example, if the -RIMSERVER switch is not applied to a server when a Closed or Cutoff event (or any event with a timed delay period) is posted on an Open managed folder from the Unity Client or Web Client, then the event will not be processed. This means that the documents will not be locked down or made unalterable; users can edit keywords, add documents, delete documents, and perform other actions normally prohibited on Closed or Cutoff folders. Although the effective date on a folder's disposition status will be updated when an event is posted, the folder will not be processed through the configured retention plan without the -RIMSERVER switch. The recommended best practice is that the -RIMSERVER switch be applied to a single OnBase Client server that is running at all times.
Only one instance of the OnBase Client should be running with the -RIMSERVER switch. You can verify that the Client is running as a Records Management server by checking the RIM Server Mode status in the System Status dialog box. If RIM Server Mode is displayed as Yes, the Records Management server is active.