A train of thought of connecting on the line (local ERP and online e-commerce platform docking)

At present, many companies hope that the local ERP can connect with the online e-commerce platform.

But a lot of offline ERP system vendors do not want to modify the code to do the corresponding docking, or feel too much cost.

And for the enterprise itself, there will be a lot of special needs.

Below is a brief account of an importer product enterprise's online and offline integration program.

The offline system uses Shenzhen's store management system, using Vs.net platform development, database using MSQL2005,BS structure (internal management) +CS structure (store pos billing), LAN deployment

The online system uses a local e-commerce platform provider's marketplace system (through which distributors can purchase orders directly, check inventory, and download the latest new products in a timely manner, etc.). Using NetBeans Platform Development (php,c++, various services integration), the database uses MYSQL+REDIS,BS structure +saas, open to the outside.

Internal network, must restrict the access of the outside network, each store uses the VPN device to carry on the networking. Then only internal access is allowed outside, and external direct access to the internal system is not allowed.

Online e-commerce platform, hope that each docking system has a separate interface, through for each interface through, to achieve a variety of interoperability.

The policy is as follows:

1, each line system can not be modified by each of the original program code, but the database is flexible existence, for the internal is shared, in the familiar with the current business premise, through monitoring the operation of the database to grasp the information in real-time interaction. For example: through the MSSQL SqlDependency function to monitor the trigger and so on, monitoring members of the registration, product additions and deletions, order submission, inventory of the stock, inventory and so on.

2, by providing a unified Windows service (you can use WCF to encapsulate specific business processing, provide the appropriate interface for extranet access: Soap,json,rest, etc.) through the HTTP protocol or the TCP protocol for interactive communication.

3, e-commerce platform through the Redis isolated extranet and intranet interaction. The extranet data is parsed through Swool, and the data and tasks are delivered to Redis, and the corresponding business logic is updated to the platform through a process.

4, in the e-commerce platform Interface Management, the implementation of the new third-party interface application and authorization, so as to achieve data interaction.

Problem point:

1, offline business logic abstraction to do in place, avoid causing frequent version updates (members, goods, orders, inventory: Add, modify, delete)

2, access control with Gateway

3, to have a message queue, avoid communication anomalies, resulting in suspended animation.

4, do the log recording work.

A train of thought of connecting on the line (local ERP and online e-commerce platform docking)