...
- Encrypted Communication - TLS/SSL
- Audit Trail - Complete activity log
- Auto-Logout - Inactivity timeout
- IP Filtering - Connection restrictions
- Password Policy - Complexity requirements
Best Practices
Startup Procedures
- Verify database connectivity before starting
- Check license validity and limits
- Start in maintenance mode for initial testing
- Monitor startup sequence for errors
- Confirm all modules initialize properly
Performance Optimization
- Size memory appropriately for tag count
- Optimize device polling rates
- Use event-driven updates when possible
- Archive historical data regularly
- Monitor and adjust thread pool settings
Maintenance Operations
- Schedule regular backups
- Monitor log file sizes
- Archive old historical data
- Update security certificates
- Test redundancy failover periodically
Troubleshooting
| Symptom | Likely Cause | Solution |
|---|---|---|
| Runtime won't start | Database connection issue | Check connection string and SQL server |
| High CPU usage | Excessive polling or scripts | Review device scan rates and script efficiency |
| Client can't connect | Firewall or port issue | Verify port is open and not blocked |
| Memory growth | Memory leak or retention | Check retentive tag settings and script objects |
| Slow performance | Database or network bottleneck | Analyze performance logs and network traffic |
| Failover not working | Network or configuration issue | Verify heartbeat network and redundancy settings |
| Values not updating | Device communication failure | Check device status and communication logs |
Overview
Content Tools
Tasks