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

Nebim V3 and Winner

Head office server and cloud infrastructure for Nebim V3 ERP

The head office side of Nebim V3 is not a single server. Around the ERP database run Windows services for scheduled jobs, an integration layer that connects to external systems, and a transfer layer that exchanges data with stores. When one service stops, the ERP screen stays open, but payments are not posted or exchange rates are not updated. We build the head office infrastructure with each of these layers in view.

Product architecture

Nebim V3 ERP architecture on ARGE Cloud

In the diagram, the ERP database, the application, and the integration services run in your dedicated VPC. Stores connect to head office from their own firewall, and e-document traffic goes out only to the provider's addresses.

ARGE ICT infrastructure diagram (Nebim V3 ERP). 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 (Nebim V3 ERP), the database, and the integration services 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). Stores connect to head office from their own firewall over IPsec, MPLS, or SD-WAN. For e-Invoice, e-Archive, and e-Ledger the firewall allows outbound traffic only to the provider's addresses.ARCHITECTURE · NEBIM V3 ERPNebim V3 ERP architecture on ARGE Cloude-BelgeMPLS · 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 requestsIntegration servicese-Documents, payments, loyaltyIntegration servicesservice status monitoredApplication serverNebim V3 ERP · Windows servicesHA cluster: optionalApplication serverNebim V3 ERPredundant cluster on requestDatabase serverengine and version to be confirmed with vendorDatabase 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 upStoresprice, promotion, and sales transferStoresevery store linked to head officePOS terminalsales and paymentStore firewallIPsec · MPLS · SD-WAN · second link advisedStore firewallstore over an encrypted linke-Document providere-Invoice, e-Archive, e-Ledgere-Document 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 (Nebim V3 ERP), 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 Nebim V3 ERP?

Nebim V3 ERP is Nebim's ERP and store-management software for retail, wholesale, and manufacturing companies. The modules run on one platform and one database. In its brochure, Nebim refers to experience going back to 1966.

The main features are variant management (color, size, drop), season and collection management, allocation, and automatic transfer rules. The product supports e-Invoice, e-Archive, e-Ledger, and e-Reconciliation. Wholesale, retail, dealer, consignment, and export channels run on the same platform. A data warehouse and dashboards are part of the product too.

The product comes in four editions: Starter, Standard, Advanced, and Enterprise. Store and user limits vary by edition, and Enterprise has no limit; current limits are available from Nebim. Standard adds production and the data warehouse, and Advanced adds allocation, inter-store transfer planning, business intelligence, and merchandise planning.

Nebim also offers a cloud service under the name Nebim ERA. The infrastructure for the store side is described separately under Nebim V3 POS and store.

Companies that use Nebim V3

Nebim lists apparel, footwear, home textiles, carpets, furniture, tableware, optics, cosmetics, and accessories as the product's sectors. The product is aimed at companies with a store chain and a dealer network.

The load concentrates at season openings and during promotion periods, and the infrastructure is sized around those periods. As the number of stores and dealers grows, the work of the transfer layer grows too.

Take a season opening, when head office defines the new price list and promotion. That information travels to the stores through the transfer layer. Posting payments and updating exchange rates depend on the Windows services, so the servers that run these services are also part of the head office infrastructure.

Database, Windows services, and the transfer layer

The ERP database and application are at the center of the architecture, with Windows services, an integration layer, and a transfer layer around them. The layers do different jobs but write to the shared database, so the server plan counts them together. Nebim does not state the database engine and version in the documents it publishes, so this is confirmed before setup.

According to Nebim's 23.10 release notes, the Windows services fetch exchange rates, run the accounting integration, talk to the online bank integrator, and run allocation and transfer plan rules. Bulk SMS and email sending are also among these services. Not every installation uses all of them; the ones in use are determined during setup.

According to the same release notes, Nebim has gathered these services in an installation package called Nebim V3 Service. Parameters and schedules are set from a single interface, and a service can be triggered manually for testing. Before an upgrade, Nebim's version upgrade guide is followed.

External connections are made in two ways. Nebim V3 Integrator offers REST API services for e-commerce sites and other applications. Nebim V3 Data Send/Receive carries product, price list, customer, sales invoice, and inventory data between V3 databases at set intervals. Dealers, affiliated companies, and store databases connect to head office this way.

Enterprise installations also have a planning layer. According to Nebim's Enterprise brochure, the CPM Merchandise Planning and Budgeting applications are built on IBM Cognos TM1 and use an in-memory database. Users connect through a web or Excel interface.

Nebim V3 head office setup on ARGE Cloud

The servers for the ERP database, the application, and the services run in your dedicated VPC on ARGE Cloud. The VPC is protected by a highly available (HA) firewall, and ARGE Cloud is our own infrastructure in a data center in Istanbul. In this setup, customer and loyalty data stays in Türkiye. Server size is set by the number of stores and users, the load of the services, and the season peak.

For season openings and promotions, we build the database servers on Dell and Supermicro hardware with Xeon Platinum processors, enterprise NVMe drives, and host-to-host NVIDIA Mellanox networking at 25–200G.

Stores connect over IPsec, MPLS, or SD-WAN links, and we recommend a second link for critical stores. Head office users connect over SSL VPN, zero trust network access (ZTNA), or ARGE ZTNA. The endpoints Integrator exposes externally are placed behind a web application firewall (WAF).

The running status of the Windows services can be added to server monitoring, and which services are monitored is settled with your Nebim partner during setup. We also monitor servers, disks, memory, the database service, links, and backup results. 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. The contract sets monitoring hours and response scope.

The database and service configurations are backed up to the isolated backup zone; restore tests are run, and their frequency is set in the contract. Backup design details are under backup and disaster recovery. An application HA cluster and a database HA cluster are optional, as is a disaster recovery (DR) site in a second data center. We confirm the product's cluster and DR behavior with Nebim.

Promotion definitions, allocation rules, and service parameters stay with your Nebim partner. Licensing and version upgrades also remain with your partner or Nebim; we build and operate the infrastructure.

What we confirm with Nebim before setup

  • Database engine, version, and operating system requirements for the V3 release you use
  • Which Windows service runs on which server, and whether you have moved to the Nebim V3 Service package
  • Endpoints that Integrator and other integration services must expose externally
  • Infrastructure steps in the version upgrade guide

Technologies: Windows Server · Nebim V3 Service · Nebim V3 Integrator · IPsec · SSL VPN · ARGE ZTNA · WAF · ARGE Cloud

Frequently asked questions

Which database does Nebim V3 run on?

The sources Nebim publishes do not give the engine or version. We get this from Nebim or your partner for the V3 release you use before setup, and the server plan is finalized accordingly.

We use Nebim Winner; what can be done on the infrastructure side?

You need to ask Nebim for Winner's current support status. Moving to V3 is the job of your Nebim partner. Until then we arrange the backup and access of the Winner server, and we prepare the V3 head office environment before the move.

How is it noticed when one of the Windows services stops?

The running status of the services can be added to server monitoring. Which services are monitored and who receives the alert are settled during setup and stated in the contract.

How does our e-commerce site connect to Nebim V3?

Through the REST API services of Nebim V3 Integrator. Endpoints exposed externally are placed behind the WAF, and only the required sources are allowed. The addresses of connected systems are recorded during setup.

ARGE ICT provides and operates the infrastructure that Nebim V3 ERP runs on. Nebim Neyir Bilgisayar Sanayii ve Hizmetleri A.Ş. 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.

Sizing call for Nebim infrastructure

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

Request a sizing call