The following practices apply to all medical records servers:
- Before setting up the medical records servers as Windows services, run them interactively in the OnBase Client (not as Windows services) for a few cycles. Monitor the servers to ensure they are working correctly (e.g., completing processes, creating and releasing locks). The OnBase Client's Medical Records Server window allows you to monitor whether individual processes are being started and finished.
-
Set up the medical records servers as Windows services.
-
The Analysis Server, Closure Server, and (if applicable) Polling Service should run on the same process. These are the only medical record servers that should run on the same process.
-
Configure each remaining medical records server as its own service. None of these services should be configured to run on the same process as another service (such as the OnBase Scheduler or the Workflow Timer Service).
-
- Each service should have its own Windows user account and OnBase user account.
- Run only one service per medical records server. For example, do not run two Analysis Servers at the same time. Doing so can lead to burning conflicts and prevent successful database upgrades.
- For troubleshooting, use verbose logging. For more information about verbose logging, see the System Administration module reference guide.
- Restart services sparingly. When you restart a service, clear the processing lock in the OnBase Client. Contact your solution provider for assistance.
- Do not restart the OnBase Application Server that medical records servers or clients are connecting to. If you must restart the Application Server, do so when all users are logged out and services are stopped. Restart services after the Application Server is restarted.