Architecture Overview
Overview
The OpCon server consists of the Schedule Activity Monitor (SAM) and supporting services (SAM-SS). Each component handles a specific role in processing schedules, communicating with agents, sending notifications, and routing requests.
Use this section to:
- Install or configure an OpCon server
- Diagnose connectivity or processing issues between components
- Configure service startup, logging, or failover behavior
- Understand component roles before making changes
Components
| Component | Description |
|---|---|
| SMA Service Manager (SMAServMan) | Controls startup, shutdown, and monitoring of all OpCon services. In failover configurations, coordinates the transition from the primary to the secondary machine. |
| Schedule Activity Monitor (SAM) | Core engine that processes schedules, determines when jobs qualify for submission, and processes OpCon events. |
| SMA Network Communications Module (SMANetCom) | Handles all TCP/IP communication between SAM and all agents. Sends job start information to agents and writes agent responses back to the database. |
| SMA Notify Handler | Reads the OpCon database notification queue and routes notifications via email, text message, Windows Event Log, SNMP trap, and other channels. |
| SMA Request Router | Routes requests between the OpCon database and designated request handlers, including schedule maintenance and job output retrieval. |
| SMA Start Time Calculator | Periodically recalculates estimated start times for jobs in the OpCon Daily tables and updates the database. |
| Optional Components | Additional server modules available for specific deployments. |
| Configuration | Server-level configuration file reference. |
| Logging | Log file locations, log levels, and log rotation settings. |