What is Netsis Wings Enterprise?
Logo Netsis Wings Enterprise is Logo's web-based Netsis product, installed on the company's own server. According to Logo, the design is hybrid: the browser and the desktop application can be used at the same time. In Logo's brochure, the Netsis Wings and Wings Enterprise packages are listed separately. Whether the server runs in the company's own building or on ARGE Cloud is a separate decision.
The screens Logo highlights include the Bank Screen, the Dynamic Warehouse Screen, and automatic accept and reject in quality control. Cost accounting, Fixed Assets, and Machine Maintenance are sold separately, and payment can be monthly, yearly, or one-time. Your Logo partner settles which modules a package includes and what is bought separately during the license discussion.
The desktop-client product in the same family is Logo Netsis 3 Enterprise. According to Logo, the two products share the same Netsis foundation, which is why tools such as NetOpenX, the Rest API, and Dynamic Coding are in Wings as well.
Companies that use Netsis Wings
Among Wings users are companies that have moved from Netsis 3 Enterprise to the browser. Warehouse and field teams working on tablets belong to this group as well; according to Logo, Wings runs in HTML5 browsers and on tablet screens and supports a virtual keyboard.
Another group is companies that want to open their own screens to dealers and suppliers. Because these users connect from outside the company network, the way the application is published is planned separately. The sessions of external users also run on the server, so they count toward the session total.
Take a dealer who wants to check an order from a meeting room on a tablet. The accounting team at head office, using the same application through the desktop client, connects to the same database by a different route.
Hybrid architecture with browser and desktop access
According to Logo, Wings needs no extra IIS configuration; the product runs on a physical or cloud server and supports Oracle and Microsoft SQL Server. Because sessions run on the server, the number of sessions during peak hours is the measure of memory and processor demand. These conditions are confirmed again for the release you use before setup.
Browser and desktop users write to the same database. The load of both access paths therefore lands on the database server, and the web layer and the database run in the same VPC.
Browser access needs a published address. Users arrive at that address first, and the web layer and the database run behind it. The domain name and the TLS certificate for the address are planned together before setup.
The tools shared with Netsis 3 Enterprise are also in Wings: NetOpenX, Netsis Rest API, single sign-on with Active Directory, Dynamic Coding, and NDI. The server-side requirements of these tools can vary by release and are confirmed before setup.
Microsoft's free SQL Server Express edition limits database size and memory. Choosing the edition for Wings is therefore part of sizing and is handled together with the license discussion.
Netsis Wings setup on ARGE Cloud
The Wings server and the SQL Server database run in your dedicated VPC on ARGE Cloud. A highly available (HA) firewall is placed in front of the VPC, and ARGE Cloud is our own infrastructure in a data center in Istanbul. Sites such as branches and factories connect over IPsec, MPLS, or SD-WAN. Site links are monitored; if a link drops, users at that site cannot access the application, so we recommend a second link.
Browser users connect over SSL VPN, zero trust network access (ZTNA), or ARGE ZTNA. Users of the desktop application work on a terminal server (RDS). Because the terminal server and the web layer run in the same VPC, both groups of users connect to the database from inside the VPC. Which user group enters by which route is written down during setup.
If external users such as dealers and suppliers need access published to the internet, the traffic passes through a web application firewall (WAF) and is encrypted with TLS. The TLS certificate needs a published address, and we plan how the certificate is installed and renewed. If the certificate is not renewed before it expires, browser access shows a warning or does not open. The expiry date can therefore be added to monitoring; the scope is set in the contract.
We size by measurement: the number of concurrent sessions, peak hours, and the monthly growth of the database. The status of the servers, the SQL Server service, the links, and the backup results falls under monitoring. The service zone next to the VPC holds antivirus and XDR/EDR together with security information and event management (SIEM) and security orchestration, automation, and response (SOAR) systems. Monitoring hours and response scope are stated in the contract.
The database and the application configuration are backed up to the isolated backup zone; restore tests are run, and their frequency is set in the contract. Our backup and disaster recovery page describes how backups are taken. A SQL HA cluster and a disaster recovery (DR) site in a second data center are optional; we confirm Wings's cluster behavior with Logo.
The choice of the Wings package and the license stays with your Logo partner. Where the server runs and which access routes are opened is decided in the discovery meeting. How the SQL Server license is supplied is stated in the quote. Application setup, version upgrades, and functional support also remain with your Logo partner; we build and operate the server, the access layer, and the backup.
What we confirm with Logo before setup
- SQL Server and Oracle versions supported for the Wings release you use
- Recommended memory and processor per browser session
- Conditions for running Wings behind an access layer or reverse proxy
- How desktop and browser use are licensed together
- Requirements for single sign-on with Active Directory
Technologies: Windows Server · Microsoft SQL Server · TLS · Active Directory · SSL VPN · ARGE ZTNA · WAF · ARGE Cloud
Frequently asked questions
How do users connect to Netsis Wings from outside the company?
Users connect through a layer that authenticates them: SSL VPN, ZTNA, or ARGE ZTNA. If access for external users such as dealers and suppliers is published to the internet, the traffic passes through a WAF. We define the access route separately for each user group.
Can we also use Wings as a desktop application?
Yes. According to Logo, the browser and the desktop application are used at the same time, and both write to the same database. We set up a terminal server for the desktop users.
What changes in the infrastructure when moving from Netsis 3 Enterprise to Wings?
The database stays the same. What is added is a published address, a TLS certificate, and extra memory for browser sessions. License and version steps stay with your Logo partner. If desktop users are involved too, the terminal server is planned separately.
Can Netsis Wings run on SQL Server Express?
The Express edition limits database size and memory, and it may be enough to start with in a small setup. As data or users grow, a move to the Standard edition is planned. We decide which edition to start with by measurement.
ARGE ICT provides and operates the infrastructure that Logo Netsis Wings Enterprise runs on. Logo Yazılım is the vendor of this software and the owner of its name and trademark; ARGE ICT is not an official partner or reseller of that company. You get licensing, implementation, and functional support from the vendor or your partner.