- Getting Started
Get Started with Administering Wyn Enterprise
- System Requirements
- Installing on Windows
- Installing on Linux
- Installing using Docker
- License Wyn Enterprise
- Deploying with HTTPS
- Deploying with Reverse Proxy
- Deploying to Azure App Service (AAS)
- Deploying to Azure Kubernetes Service (AKS)
- Deploying to AKS using Helm Chart
- Deploying to Local Kubernetes
- Deploying to Kubernetes Cluster using Helm Chart
- Deploying as a Virtual Directory or Sub-Application
- Deploying to Amazon ECS
- Deploying to Amazon EKS using Helm Charts
- Deploying in a Distributed Environment
- Migration from ActiveReports Server 12
- Upgrade Wyn Enterprise to Latest Version
- Logging on to the Administrator Portal
- Ports in Firewall
- Configuration Settings
- Account Management
- Security Management
- System Management
- Document Management
- How To and Troubleshooting
- Get Started with Administering Wyn Enterprise
- User Guide
- Developer Guide
Wyn Enterprise: Installing on Linux
This topic describes the installation instructions for installing Wyn Enterprise on Linux.
Wyn Enterprise uses the following ports by default.
Cot Worker: 51983
Reporting Worker: 51982
Scheduler Service: 51981
Dashboard Worker: 51984
Datasource Service: 51988
MemoryDB Service: 51987
AnalysisDB Primary Node: 51996
AnalysisDB Service: 51998
You can reassign the ports in the config (Wyn.conf) file.
Check System Status
sudo systemctl status wyn
Start Wyn Service
sudo systemctl start wyn
Stop Wyn Service
sudo systemctl stop wyn
During the installation of Wyn Enterprise, these services are automatically installed on your system.
WynDatabase: Maintains a PostgreSQL database. This service is unavailable in case you use a custom database for Wyn Enterprise.
WynService: Hosts several processes to maintain Wyn Enterprise websites and other modules.
Publish Wyn Enterprise Portal to Internet
Wyn Enterprise uses the embedded identity in the server by default. Therefore, there is no need to change the configuration to publish Wyn to the internet. The customer just needs to use the reverse proxy to bind the domain if it's needed.
The Wyn Enterprise service listens to all IP addresses of a current server, so you can access the portal on the current server via localhost:42002 (if the server has a graphical shell). Otherwise, you can access the portal on another machine via http://serverip:51980/ in intranet.
On Linux, the Wyn.conf file is located here: