Page History

Execute and monitor solutions with different profiles and diagnostic tools.

Tutorials → Runtime| Tutorial | How-to Guide | Reference

Security Checklist

Configure security:

•  Change default passwords
•  Enable user authentication
•  Configure permissions
•  Enable audit trail
•  Setup firewall rules
•  Disable unnecessary services

Production Settings

1. Runtime → Settings
2. Configure:
   • Startup: As Windows Service
   • Auto-start: Enabled
   • Watchdog: Enabled
   • Log level: Warning

Database Configuration

Setup production database:

1. Move from SQLite to SQL Server
2. Configure connection pooling
3. Setup backup schedule
4. Test restore procedure

License Activation

1. Solution Center → License
2. Enter production license
3. Verify tag count
4. Check enabled features

Performance Tuning

Optimize for production:

• Set appropriate scan rates
• Optimize queries
• Configure cache settings
• Disable debug logging

Backup Strategy

Configure backups:

• Solution files: Daily
• Historical data: Continuous
• Configuration: Before changes
• Test restore monthly

Monitoring Setup

Enable monitoring:

• System resources
• Communication status
• License usage
• Disk space

Documentation

Create documentation:

• Network diagram
• Tag list
• User manual
• Disaster recovery plan

Training

Train operators:

• Normal operations
• Alarm response
• Basic troubleshooting
• Emergency procedures

Go-Live

Production startup:

1. Final backup
2. Start Runtime service
3. Verify all communications
4. Monitor for 24 hours
5. Document any issues

Validation Checklist

• ? All devices communicating
• ? Alarms functioning
• ? Historical data logging
• ? Reports generating
• ? User access working
• ? Backup running

Next Steps

• [Troubleshooting] - Common issues
• [Support and Community] - Get help
• [High Availability] - Add redundancy

1. Start Runtime in Development Mode

Quick Test from Designer

1. Open MyFirstSolution in Designer (if not already open)
2. Go to Runtime → Startup
3. Make sure that under "ExecutionProfile" the option Development is checked
4. Click the Run Startup button
5. Observe startup sequence:
   • TServer Startup...
   • Process starting...
   • Connecting to server...
   • Server Started Successfully
   • Starting modules...

Stop Runtime

• Click Stop button in the Designer → Runtime → Startup
• Wait for clean shutdown
• Once the shutdown is complete, the "Run Startup" button will be available again

2. Explore Execution Profiles

View Available Profiles

1. Go to Runtime → Execution Profiles
2. See three default profiles:
   • Development 
   • Validation 
   • Custom

3. Monitor Runtime Status

Start Full Runtime

1. Go to Runtime → Startup
2. Ensure Development profile selected
3. Click Run Startup
4. Watch startup progress

Check Module Status

On the TStartup display, observe which modules are running, paused or stopped.

4. Use Property Watch

Open Property Watch

1. Click Runtime → Runtime Diagnostics
2. Select Property Watch
3. New window opens

Browse Runtime Objects

Navigate the object tree:

1. Expand Tag node
2. Find your tags (Double1, Double2, Double3)
3. Click Double1
4. View properties:
   • Value: Current value
   • Quality: 192 (Good)
   • Timestamp: Last update

Modify a Value

Test runtime write:

1. Select Double1 Value
2. Enter new value: 50
3. Press Enter
4. Observe value changes
5. Note timestamp updates

5. Test Client Connections

Enable Web Client

1. Go to Runtime → Startup
2. Note the HTMNL5 Client URL: http://127.0.0.1:3201/html5
3. Click the play button or copy to browser

Access Web Interface

In your browser:

1. Page loads automatically
2. If prompted for login:
   • Username: Administrator
   • Password: (blank for development)
3. Main display appears

Test Display Updates

1. Return to Property Watch
2. Change Double1 value to 75
3. Watch web display update in real-time
4. Confirms client-server communication

6. Use Trace Window

Open Trace Window

1. Click Runtime → Runtime Diagnostics
2. Select Trace Window
3. Click Settings
4. Check Debug

Any error message should display here (it's expected that at this moment no messages will show up, once there are no errors happening).

In this section...