Skip to content
+90 850 885 27 43 info@argeict.com

Logo Netsis

Server and cloud infrastructure for Logo Netsis 3 Enterprise

In a manufacturing company on Netsis 3 Enterprise, the database works hardest during MRP and production planning runs and month-end consolidation. The factory and branches keep working on the same server while those jobs run. We therefore plan capacity and connectivity for those runs, not for an average day.

Product architecture

Netsis 3 Enterprise architecture on ARGE Cloud

In the diagram, the Netsis application server, the SQL Server database, and the terminal server run in your dedicated VPC. The factory connects from its own firewall over an encrypted link, and e-document traffic goes out only to the provider's addresses.

ARGE ICT infrastructure diagram (Netsis 3 Enterprise). Head office and branches connect from their own firewall to the Istanbul data center over an IPsec tunnel or MPLS/SD-WAN; remote staff use SSL VPN, ZTNA, or ARGE ZTNA. Traffic passes from the data center router through the ARGE ICT Backbone HA Cluster to an HA firewall. Inside the dedicated VPC it passes the VPC firewall and the WAF and is spread across the application servers by a load balancer; the application server (Netsis 3 Enterprise), the database, and the terminal server run in this VPC; application and database tiers can be built as HA clusters on request. A service zone beside the VPC runs monitoring, SIEM and SOAR, antivirus/XDR/EDR, and DLP. It runs on Dell and Supermicro servers with Xeon Platinum and enterprise NVMe, hosts linked by a 25–200G NVIDIA Mellanox network. Backups are kept in an isolated backup zone and can optionally be replicated to a second data center (DR site). The factory connects to the data center over an encrypted link from its own firewall. For e-Invoice, e-Archive, and e-Ledger the firewall allows outbound traffic only to the provider's addresses.ARCHITECTURE · NETSIS 3 ENTERPRISENetsis 3 Enterprise architecture on ARGE Cloude-DönüşümMPLS · SD-WANInternetCustomer: head office and branchesyour own firewallData center · Istanbuldata stays in TürkiyeARGE physical environmentARGE ICT network and racksYour dedicated VPCfirewall · WAF · serversVPC monitoring and security serviceMonitoring · SIEM and SOAR · AV/XDR/EDR · DLPBackup infrastructureisolated backup zoneDR site · second data centeridentical to the primary environmentHead officeBranchesCustomer firewallIPsec tunnel endpointCustomer firewallyour company's gatewayIPsec tunnelfrom head office and branches, encryptedIPsec tunnelencrypted private linkRemote staffSSL VPN · ZTNA · ARGE ZTNARemote staffsecure access from home or fieldDC routersdata center network · HA pairDC routersterminates external linksARGE ICT Backbone HA ClusterHA link from DC network to ARGE networkARGE ICT Backbone HA Clusterredundant core backboneFirewall (HA)ARGE perimeter · HA pairFirewall (HA)only allowed traffic passesVPC firewallrules for you onlyVPC firewallentry to the VPCWAFweb application firewallWAFinspects web requestsTerminal serverRDS · desktop clientsTerminal serverremote access to the programApplication serverNetsis 3 Enterprise · Windows ServerHA cluster: optionalApplication serverNetsis 3 Enterpriseredundant cluster on requestDatabase serverMicrosoft SQL Server · version to be confirmedDatabase HA cluster: optionalDatabase serveryour data lives hereredundant cluster on requestInfrastructure monitoringserver, disk, network, backupInfrastructure monitoringon one dashboardSIEM and SOARlog collection and correlationSIEM and SOARalerts handled in defined stepsAntivirus · XDR · EDRendpoint protection on serversAntivirus · XDR · EDRmalware and suspicious behavior stoppedDLPdata loss preventionDLPdata egress monitoredVirtualization hostsDell and Supermicro serversXeon Platinum · enterprise NVMeVirtualization hostsenterprise-class serversfast processors and storage25G / 50G / 100G / 200G host networkNVIDIA Mellanox Ethernet cards25G / 50G / 100G / 200G host network25–200G links between serversBackup copiesseparate logical zoneseparate from productionBackup copiesyour copies are kept hereDR firewallsame rulesDR application serveractive · serving usersDR application serverstandby · takes over in a disasterDR databasesynchronized both waysDR databaseup-to-date copy, read-onlyGlobal Load Balancerhealth-checked routingGlobal Load Balancersends users to the site that is upFactoryproduction · MRP and planningFactoryproduction on the same systemFactory firewallIPsec · second link advisedFactory firewallfactory over an encrypted linkE-invoicing providere-Invoice, e-Archive, e-LedgerE-invoicing providercontrolled outbound linkSSL VPN · ZTNAARGE ZTNAlogs and metricsBackup lineAlso to DR (active-active)traffic shared across both sitesFailover pathused only in a disasterTwo-way replicationContinuous replicationone way, primary to DR123456IPsec tunnelMPLS / SD-WANSSL VPN · ZTNAInternet to WAFDC and ARGE networkHA pairingApplication ↔ data25–200G host networkLogs and metricsBackup lineGlobal Load BalancerFailover pathDR replication1Step (below the diagram)Listed outboundIllustrative · HA and DR are added with the buttons on the page
IPsec tunnelMPLS / SD-WANSSL VPN · ZTNAInternet to WAFDC and ARGE networkHA pairingApplication ↔ data25–200G host networkLogs and metricsBackup lineGlobal Load BalancerFailover pathDR replicationListed outboundIllustrative · HA and DR are added with the buttons on the page
Hover over or tap a component to see its name and role; choose “Show all” to see every label at once. Zoom with Ctrl/⌘ + scroll, a two-finger pinch or a double click. Use the buttons above to add HA and DR options; click a step to bring its layer forward.
The diagram shows the path we build (Netsis 3 Enterprise), from your sites to the data center and from the dedicated VPC to the isolated backup zone. Application and database HA clusters and the DR site (passive, or active with a Global Load Balancer) are added with the buttons above the diagram. It is illustrative; ports, database, and integration details are confirmed with the vendor before installation.

How to read the diagram

  1. 1
    Your sites and staff connect over encrypted links

    Head office and branches come in from their own firewall over an IPsec tunnel, or over an MPLS or SD-WAN circuit. Staff outside the office use SSL VPN, ZTNA, or ARGE ZTNA. Where an application is internet-facing, its traffic passes through the WAF.

  2. 2
    Traffic is filtered at the data center edge

    The connection goes from the data center router to the ARGE ICT Backbone HA Cluster and then to the firewall. All three are HA pairs side by side; if one fails, the other takes over.

  3. 3
    Your dedicated VPC: firewall and WAF

    Traffic entering the VPC passes your own firewall and then the WAF, and a load balancer spreads it across the application servers. The application, terminal, and database servers run in this VPC. On request we build the application and database tiers as HA clusters.

  4. 4
    Monitoring and security service beside the VPC

    Server, disk, network, and backup status show on the monitoring dashboard. Logs are collected in SIEM and SOAR, and alerts are handled in defined steps. Antivirus and XDR/EDR run on the servers, and DLP monitors unauthorized transfers of sensitive data. The scope is set in the contract.

  5. 5
    Enterprise hardware, fast internal network

    The environment runs on Dell and Supermicro servers with Xeon Platinum processors and enterprise NVMe drives. Hosts are interconnected at 25G, 50G, 100G, or 200G with NVIDIA Mellanox cards.

  6. 6
    Backup in an isolated zone, DR site optional

    Backups are kept in an isolated backup zone, separate from the production environment. On request we build an identical environment in a second data center: in passive mode it takes over in a disaster, in active mode a Global Load Balancer spreads traffic across both sites.

What is Netsis 3 Enterprise?

Logo Netsis 3 Enterprise is an enterprise resource planning (ERP) product from Logo Yazılım, installed on the company's own server, and it is the top package of the Netsis family. In Logo's new product structure, the Netsis group goes by the name N-Series under Logo Edge. Its web-based version is Logo Netsis Wings Enterprise; the interface is available in Turkish and English as standard.

According to Logo's product page, on the production side the MRP module handles forecasting, master production scheduling (MPS), and material requirements planning. The Advanced Production Planning module schedules jobs by operation and machine, and the Quality Control module draws statistical control charts. Machine Maintenance is offered as an add-on module.

On the finance and distribution side there is a branch, business-unit, and holding hierarchy, consolidation, bank loans, foreign trade, and request and quotation management. The Dynamic Warehouse module tracks stock by warehouse cell. e-Document processing runs through Logo e-Solutions.

Companies that use Netsis 3 Enterprise

Logo lists distribution and wholesale, automotive, aerospace, chemicals, food and beverage, and construction as the sectors for the product. From an infrastructure point of view, manufacturers whose factory and branches work from separate sites are the most relevant group.

In these companies the ERP is not used from a single building. Finance and purchasing at head office, production and quality at the factory, and a distribution warehouse in another city all write to the same database. Month-end consolidation and MRP runs put a heavy load on the server for short periods.

Take a manufacturer with head office in one city and a factory in another. A buyer waits for the MRP result while the planner at the factory opens work orders. Two teams writing to the same database at once means capacity planning has to count concurrent sessions as well.

Desktop client, database, and integration interfaces

Netsis 3 Enterprise is a Windows application with a desktop client and a client-server design. Logo does not state the database engine on its product page. For Netsis Wings, which shares the same foundation, Oracle and Microsoft SQL Server are supported. Setups on ARGE Cloud use Microsoft SQL Server, and the version is confirmed before setup.

Four tools accompany the application. NetOpenX is a development interface for pushing records into Netsis and reading data out without bypassing its business logic. According to Logo, Netsis Rest API runs as a Windows service and therefore needs no IIS installation. Dynamic Coding and NDI (Netsis Data Inspector) count among the customization tools.

On the identity side, the Central Identity Control System supports single sign-on with Active Directory. Permissions can be defined at column, form, and row level. These permissions are defined inside the application, while single sign-on involves the domain design on the server side.

MRP and MPS runs and consolidation put the most load on the database. How users run the client from a factory or a branch is a separate infrastructure decision.

Because the desktop client runs on Windows, it is possible to run it on a terminal server (RDS) at remote sites instead of on each user's own computer. That keeps the query traffic between the client and the database inside the data center; only the screen image crosses the link.

Netsis 3 Enterprise setup on ARGE Cloud

The SQL Server database and the terminal servers run in your dedicated VPC on ARGE Cloud. ARGE Cloud is our own infrastructure in a data center in Istanbul, and a highly available (HA) firewall is placed in front of the VPC. In sizing we look at the number of companies, how often MRP runs, and the scope of consolidation. The number and memory of the terminal servers are planned around the number of sessions open at the same time.

Because MRP run times depend on memory and disk latency, the database runs on Dell and Supermicro servers with Xeon Platinum processors, enterprise NVMe drives, and 25–200G NVIDIA Mellanox networking. Where a stop in planning also stops the factory, an optional SQL HA cluster can be added. A disaster recovery (DR) site in a second data center is optional as well; we confirm Netsis's cluster and DR behavior with Logo before setup.

Factories and branches connect to the VPC over IPsec, MPLS, or SD-WAN and run the Netsis client on a terminal server. If the factory link drops, users cannot enter records until the connection returns, so we recommend a second link for the factory. The link is part of monitoring. Users outside the office connect over SSL VPN, zero trust network access (ZTNA), or ARGE ZTNA.

If the Rest API has to be published to the internet, its traffic passes through a web application firewall (WAF). The e-document path is defined on the firewall for the required addresses only. We monitor servers, disks, memory, the SQL Server service, links, and backup results, with hours and response scope set in the contract. Security information and event management (SIEM), security orchestration, automation, and response (SOAR), antivirus, and XDR/EDR run in the service zone next to the VPC.

SQL Server backups go to the isolated backup zone. We write down the restore order together with you and run a restore test, and the test frequency is stated in the contract. We describe the backup design separately under backup and disaster recovery.

MRP parameters, customizations made with Dynamic Coding, and e-document definitions stay with your Logo partner. Licensing, application setup, version upgrades, and functional support also remain with your partner or Logo; we build and operate the infrastructure.

What we confirm with Logo before setup

  • Microsoft SQL Server versions supported for the release you use
  • Windows Server and terminal server requirements
  • Server-side requirements of Netsis Rest API and NetOpenX
  • Active Directory requirements for the Central Identity Control System
  • Infrastructure impact of a move to Logo Edge N-Series, if you plan one

Technologies: Windows Server · Microsoft SQL Server · Remote Desktop Services (RDS) · Active Directory · IPsec · ARGE ZTNA · ARGE Cloud

Frequently asked questions

Does Netsis Rest API need IIS on the server?

No. According to Logo, the Rest API runs as a Windows service and does not need IIS. If the service is published externally, it is placed behind a WAF.

What happens to production records if the factory loses its connection?

While the server is on ARGE Cloud, factory users connect to the terminal server over the link. New records cannot be entered while the link is down, and work resumes when the connection returns. A second link is the measure we recommend to shorten that window.

Which database does Netsis 3 Enterprise run on?

Logo's product page does not name an engine. For Netsis Wings, which uses the same foundation, Oracle and Microsoft SQL Server are supported; we build on Microsoft SQL Server and confirm the version before setup.

Can single sign-on with Active Directory be set up?

Yes. According to Logo, the Central Identity Control System supports this. We build the domain design and the terminal server sessions, and the setting inside the product is handled by your Logo partner.

For Logo Netsis 3 Enterprise, licensing, implementation, and functional support are obtained from the vendor or your partner. Logo Yazılım makes the software and owns its name and trademark; ARGE ICT is not an official partner or reseller of the vendor, and it provides and operates the infrastructure underneath the software.

Sizing call for Logo Netsis infrastructure

Share your Netsis product, user count, and database size; we respond to your request within one business day.

Request a sizing call