The purpose of this ERP system design architecture is to centrally manage and deploy servers in a distributed manner, mainly used for the development of centralized ERP systems. As a result, the current technical architecture will adopt the Web Application Server + Web Service Application Server + DB server security architecture. The Web Service Application Server + DB server will be deployed on the slave end, the coupling relationship between Web application server and Web Service Application Server and data traffic will be the most important part of the system.
This system will adopt a more recommended SOA approach. From the technical perspective, I think it can be used in practice, I don't want to spend too much time discussing the principles and implementation of SOA. Next, I will analyze how to use the ticket mode to inject the website-based server creation object in the following RMB:
- ERP. utils. Exception (Custom Handler)
- ERP. utils. Logging (processing logs)
- ERP. utils. configuration (implementing SOA functions)
- ERP. utils. XML (define SOA object)
- ERP. utils. Biz (defines the interface provided by SOA vendors)
- ERP. utils. Data)
- ERP. utils. Common (the most common sharing interface in the bottommost Region)
- ERP. utils. Web (all pages requiring services must be accepted)
- ERP. usercontrols. operationmode)
- ERP. usercontrols. menu (custom permission limits unlimited orders)
ERP. XXX. Web... models of various systems
ERP. XXX. WebService ...... WebService applied by various systems
Processing Process:
Web --- request service --- "WebService --- publish service --- <your business website> --- return service result ---" Web
Related to ERP. utils. Biz will be released in Series II for multi-region attention.