Rules Engine Visual Rules Solution Development Basic Course [Serial 19]--Introduction to Rules Collaborative Management

Introduction to Rule Collaborative Management


1. Introduction

        When a team develops a project, it is often a division of labor, so issues such as rule package sharing, version control, permission control, and collaborative management are often involved in the development process. Rule collaborative management is a management system used to manage rule packages, control rule versions, maintain rule permissions, coordinate rule updates, and realize rule sharing. The collaborative management of rules not only greatly increases the efficiency of team development, but also enables timely update and modification of rule packages to achieve faster and better response to changes in business rules, and finally achieve the controllability, flexibility, and maintainability of rules. .

2. Login management system

        Before the login rules are managed collaboratively, two services must be enabled in the windows service: Apache Tomcat Server and mysql rules. Click "Start" - "Run". The operation is shown in the following figure:




        After clicking "Run", enter "services.msc" in the pop-up window, as shown below:




        After clicking "OK", you can see all the services under Windows, and enable "Apache Tomcat Server", as shown in the following figure:




        Then you can see in the service list that mysql rules have been started, so there is no need to start it here. As shown below:




        After the two services are started, open a browser and enter http://localhost:8880/ in the address bar . Once confirmed, a login page will appear. It should be noted here that the browser is preferably IE8 or above, as shown in the following figure:




        After entering the user name: admin and password: 123456, you are logged in to the rules collaborative management. The main interface of the rules collaborative management is shown in the following figure:




3. Rules collaborative management consists

        of four main parts: rule management, authority management, information maintenance, and system management.
        The rule management consists of 8 modules: rule setting, rule modification, application review, rule review, publishing rules, rule execution, execution results, and rule viewing. Authority management consists of 3 modules: user management, rule authority, and role management. There are only 2 modules for information maintenance: personal information and password modification. System management consists of 3 modules: resource management, menu management, log management.
        The rules collaboratively manage all functional module information, as shown in the following figure:




Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=326684759&siteId=291194637