🔵 Hyland OnBase Architecture (Explanation – Ready to Post)

🔹 1. Client Layer (User Access)

• Unity Client → full-feature desktop client
• Web Client → browser-based access
• Mobile / APIs → integrations

👉 Users interact with OnBase through these interfaces.

🔹 2. Web Server (IIS)

• Handles HTTP/HTTPS requests
• Hosts Web Client
• Acts as entry point

👉 Routes user requests to Application Server.

🔹 3. Application Server (Core Engine)

• Processes business logic
• Handles Unity API / REST API
• Executes Workflow engine
• Manages authentication & sessions

👉 This is the brain of OnBase.

🔹 4. Workflow Engine

• Controls document lifecycle
• Moves documents between queues
• Executes rules, timers, scripts

👉 Example:
Scan → Validation → Approval → Archive

🔹 5. Database Layer (SQL Server / Oracle)

• Stores:
  • Metadata (keywords)
  • User info
  • Workflow data

👉 Important tables:

• ITEMDATA
• KEYITEM
• USERACCOUNT

🔹 6. Disk Groups (Storage Layer)

• Stores actual documents (PDF, images)
• Located on:
  • Local storage
  • NAS / SAN
  • Cloud (optional)

👉 DB stores pointer → Disk Group stores file

🔹 7. Integration Layer

• Unity API (.NET)
• REST API
• Application Enabler

👉 Used for:

• SAP / Salesforce integration
• External apps
• Automation

🔴 End-to-End Flow

1. User uploads document
2. Web Server receives request
3. Application Server processes
4. Document stored in Disk Group
5. Metadata saved in Database
6. Workflow triggered
7. Document moves through lifecycle

🔵 Simple Text Diagram (for your forum)

[ User (Unity/Web) ]
        |
        v
[ Web Server (IIS) ]
        |
        v
[ Application Server ]
        |
   ---------------------
   |        |         |
   v        v         v
[Workflow] [DB]   [Disk Group]
 Engine     |        |
            |        |
        Metadata   Documents