
π΅ 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
-
User uploads document
-
Web Server receives request
-
Application Server processes
-
Document stored in Disk Group
-
Metadata saved in Database
-
Workflow triggered
-
Document moves through lifecycle
π΅ Simple Text Diagram (for your forum)