Quick Summary: The ERP Connector automates secure data exchange between your on-premise ERP server and the app. A cloud-based Comms server manages encrypted file transfer between the ERP and the app server, and the same transport channel is used for returning output files such as recommended orders.
How It Works: The 3-Component Architecture
Connecting your ERP system to the app involves three key components:
ERP server: Located on your network, this server runs your ERP system.
Comms server: A secure cloud server that coordinates data flow between your ERP and the app server.
App server: A cloud server that runs your unique instance of the app.
When You Sign Up
Upon installation:
Your instance of the app is created on one of our app servers
The Comms server is configured to allow secure communication between your ERP server and your new Netstock instance
A connector is installed on your ERP server that communicates with the Comms server to send and receive data
Security Considerations
Data Isolation
Each app instance is created for a specific customer and is completely separate from others. There is no way for one customer to access another customer’s data.
Encryption
A secure 2048-bit public/private key combination is generated on your ERP server:
The private key never leaves your ERP server.
The public key is sent to the Comms server via a web service call and stored in your unique instance.
All communication channels are encrypted with the public key and decrypted with the private key. This ensures data cannot be intercepted between:
The ERP server and the Comms server
The Comms server and the app server
The Comms server itself is secured by opening only essential ports and firewall rules.
Firewall Rules
To allow secure communication, the following ports must be open from your ERP server to the Comms server:
Port 80 (TCP)
Port 443 (TCP)
If you are using a WAN, apply these same rules between:
Your LAN and your WAN
Your WAN and the Comms server
A proxy server may also be used if preferred.
Data Flow: Sending Data to the App
Data is extracted from your ERP and sent to the app daily.
On the ERP Server
The connector runs the data extracts against your ERP.
It creates standard CSV files and compresses them using bzip2.
The compressed data is sent to the Comms server via Secure FTP (SFTP) using your private key.
A web service call signals end of transmission.
On the Comms Server
The compressed data is forwarded to the app server via Secure FTP.
On the App Server
Files are unzipped on receipt.
MD5 validation totals in the meta-data file are compared with newly computed MD5 values.
Once validated, the data is imported into your unique app instance.
Data Flow: Sending Data Back to the ERP
Data such as recommended orders or custom reports is sent back to your ERP more frequently.
On the App Server
When a file is created, the Comms server is notified via a web service call.
On the Comms Server
The file is retrieved using Secure FTP.
It is compressed with bzip2, and the file list for ERP delivery is updated.
On the ERP Server
The connector polls the Comms server via a web service call to check for new files.
If new files are available, the ERP server retrieves them using Secure FTP with its private key.
Files are uncompressed, and the Comms server is notified of successful receipt.
Forget about these 👇 😞 😐 😃 Have your say here!