These solutions need separated components for the best response. The database should be separated on a dedicated server before any other OnBase component is configured. Small solutions are valuable enough to make high availability and disaster recovery part of the setup discussion.
|
Database Server |
Specifications |
|---|---|
|
CPU |
2 Cores |
|
Memory |
4 GB |
|
Disk Configuration |
Array 1 - RAID 1+0 - Operating System and transaction log Array 2 - RAID 1+0 - OnBase database Array 3 - RAID 1+0 - tempdb |
|
File Server |
Specifications |
|---|---|
|
CPU |
1 Core |
|
Memory |
2 GB |
|
Disk Configuration |
Array 1 - RAID 1 - Operating System Array 2 - RAID 5 - with adequate storage for Disk Groups |
|
Web, Application, and Processing Server |
Specifications |
|---|---|
|
CPU |
4 Cores |
|
Memory |
4-8 GB |
|
Disk Configuration |
Array 1 - RAID 1 - Operating System Array 2 - RAID 1 - OnBase application files |
The following diagram is a high level representation of a small OnBase solution:
