What you will achieve
A separate practice environment with working Web login and Administrator project upload.
Before you begin
- The installer, license, and installation guide for your release.
- A test machine and an account allowed to install software and manage services.
01 · Map the data flow
- Communicator acquires device data; Server processes and archives it; Webstation presents it.
- Administrator maintains the project and uses Agent for instance deployment. Distinguish source projects from runtime directories.
Expected result
You can trace one measurement from device to Web.
02 · Choose an installation route
- For a first installation, follow the Windows or Linux distribution guide before building extensions.
- Use the React extension line for new projects. Maintain the existing Legacy line at installed sites; keep same-named plugin assemblies separate.
Expected result
OS, distribution version, site URL, and product line are recorded.
03 · Install and inspect services
- Install Server, Communicator, Webstation, Agent, and Administrator using your release guide. Source builds use .NET 8 SDK; packaged runtime requirements may differ.
- Check service status and logs using the operating system service manager.
Expected result
Services remain running without repeated restarts or connection errors.
04 · Open and deploy a practice project
- Open a practice project in Administrator and check its Agent and Server connection settings.
- Confirm the target instance and directories before uploading; restart the affected applications when the deployment requires it.
Expected result
Upload succeeds and the practice views are visible after Web login.
Troubleshooting
Web will not open
Check the Web process and actual listening port, then the reverse proxy and virtual directory. Example ports are not universal defaults.
Project upload fails
Check Agent address, credentials, instance, and target directory. Use the log error to fix connectivity before retrying deployment.