CN109740841A - A kind of method and system of process resource application - Google Patents
A kind of method and system of process resource application Download PDFInfo
- Publication number
- CN109740841A CN109740841A CN201811433139.XA CN201811433139A CN109740841A CN 109740841 A CN109740841 A CN 109740841A CN 201811433139 A CN201811433139 A CN 201811433139A CN 109740841 A CN109740841 A CN 109740841A
- Authority
- CN
- China
- Prior art keywords
- resource
- service
- layer
- component
- application
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 72
- 230000008569 process Effects 0.000 title claims abstract description 40
- 238000012795 verification Methods 0.000 claims abstract description 18
- 238000012545 processing Methods 0.000 claims description 38
- 230000001960 triggered effect Effects 0.000 claims description 16
- 238000005516 engineering process Methods 0.000 claims description 8
- 238000012423 maintenance Methods 0.000 description 72
- 238000007726 management method Methods 0.000 description 61
- 238000003860 storage Methods 0.000 description 11
- 238000002955 isolation Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000000694 effects Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 5
- 230000018109 developmental process Effects 0.000 description 5
- 238000012550 audit Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013523 data management Methods 0.000 description 3
- 238000013467 fragmentation Methods 0.000 description 3
- 238000006062 fragmentation reaction Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- 230000033772 system development Effects 0.000 description 2
- BQCADISMDOOEFD-UHFFFAOYSA-N Silver Chemical compound [Ag] BQCADISMDOOEFD-UHFFFAOYSA-N 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 229910052709 silver Inorganic materials 0.000 description 1
- 239000004332 silver Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000013068 supply chain management Methods 0.000 description 1
- 238000012549 training Methods 0.000 description 1
- 230000003442 weekly effect Effects 0.000 description 1
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
This application provides a kind of method and systems of process resource application, which comprises the first resource application information that the first user triggers is sent to interface layer by front end page；The interface layer is in the case where the verification of the essential information of first user passes through, the first resource service module that the first resource application information is sent in back-end services layer；First resource service module in the back-end services layer calls one or more infrastructure components in back-end services layer to complete first resource application business according to the first resource application information, and first resource application business completion data are sent in the first resource database of backend resources layer, wherein, there are corresponding relationships with the first resource database for the first service module.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a method and system for processing resource applications.
Background
Information Technology (IT) department usually needs a lot of resource applications during development and accordingly needs to manage these resources. At present, when a research and development staff of a certain department needs to apply for using a server, the research and development staff needs to fill an application form by hand or send an email to a department manager to obtain approval and then send the approval to a system manager for corresponding processing, and the approval process is complex and consumes a lot of time. Moreover, since each department or project group is managed in a distributed manner, the information grasped by each department is fragmented too much due to offline resource information application from the perspective of the entire enterprise, and effective data integration and management cannot be performed on the allocated resources, which is not favorable for further resource allocation optimization and business extension of the enterprise.
Disclosure of Invention
The application provides a method and a system for processing resource application, which can realize online resource application, online resource warehousing and online resource information management.
In a first aspect, a method for processing resource applications is provided, the method comprising the steps of:
the method comprises the steps that a front-end page sends a first resource access request triggered by a first user to an interface layer, wherein the first resource access request comprises basic information of the first user and first resource application information;
the interface layer sends the first resource application information to a first resource service module in a back-end service layer under the condition that the basic information of the first user passes verification, wherein the first resource application information and the first resource service module have a corresponding relation, and the back-end service layer is constructed by using a micro-service technology system different from a front-end page;
and the first resource service module in the back-end service layer calls one or more basic components in the back-end service layer to complete a first resource application service according to the first resource application information, and sends the first resource application service completion data to a first resource database of the back-end resource layer, wherein the first resource module and the first resource database have a corresponding relation.
Optionally, the back-end service layer further includes a service component, where the service component includes a plurality of service modules that independently process different service logics, and the basic component includes a basic data component, a mail service component, a workflow service component, and a file service component.
Optionally, the step of calling, by the first resource service module in the back-end service layer according to the first resource application information, one or more basic components in the back-end service layer to complete the first resource application service includes:
the first service module calls one or more of a workflow service component, a file service component, a mail service component and a basic data component in a back-end service layer according to the first resource application information to execute an approval process of the first resource application;
the first service module confirms a first resource state of a first database of a rear-end resource layer under the condition that the first resource application approval process passes;
and under the condition that the first resource state is callable, calling the first resource from a back-end resource layer, and sending the first resource application service completion data to a first resource database of the back-end resource layer.
Optionally, after the first service module calls the first resource from a backend resource layer, the method further includes:
the first service module calls a mail component in the basic component and sends the first resource information to the first user mailbox; or,
the first service module sends the first resource information to the interface layer;
the interface layer sends the first resource information to the front-end page;
the front-end page presents the first resource information to the first user.
Optionally, the back-end service layer further includes a service management component, where the service management component includes a plurality of management modules, and the plurality of management modules are configured to perform configuration management, registration management, and inter-component call management on the service components and the basic components in the back-end resource layer.
In a second aspect, a system for processing resource applications is provided, where the system includes a front-end page, an interface layer, a back-end service layer, and a back-end resource layer:
the front-end page is used for sending a first resource access request triggered by a user accessing the front-end page to the interface layer;
the interface layer is used for sending the first resource application information to a first resource service module in a back-end service layer under the condition that the basic information of the first user passes verification, wherein the first resource application information and the first resource service module have a corresponding relation, and the back-end service layer is constructed by using a micro-service technology system different from a front-end page;
the back-end service layer is used for calling one or more basic components in the back-end service layer by using a first resource service module according to the first resource application information to complete a first resource application service and sending the first resource application service completion data to a first resource database of the back-end resource layer, wherein the first resource module and the first resource database have a corresponding relation;
the back-end resource layer is used for providing and storing data.
Optionally, the back-end service layer further includes a service component, where the service component includes a plurality of service modules that independently process different service logics, and the basic component includes a basic data component, a mail service component, a workflow service component, and a file service component.
Optionally, the back-end service layer is specifically configured to use the first service module to call one or more of a workflow service component, a file service component, a mail service component, and a basic data component in the back-end service layer according to the first resource application information, and execute an approval process of the first resource application;
the back-end service layer is specifically configured to confirm a first resource state of a first database of the back-end resource layer by using the first service module when the first resource application approval process passes;
the back-end service layer is specifically configured to call the first resource from the back-end resource layer and send the first resource application service completion data to a first resource database of the back-end resource layer when the first resource state is callable.
Optionally, the first service module is further configured to invoke a mail component in the base component after invoking the first resource from the backend resource layer, and send the first resource information to the first user mailbox; or, the first service module is further configured to send the first resource information to the interface layer;
the interface layer is further configured to send the first resource information to the front-end page;
the front-end page is further used for displaying the first resource information to the first user.
Optionally, the back-end service layer further includes a service management component, where the service management component includes a plurality of management modules, and the plurality of management modules are configured to perform configuration management, registration management, and inter-component call management on the plurality of components and modules in the back-end resource layer.
According to the method, a first resource access request triggered by a first user is sent to an interface layer through a front-end page, the interface layer sends first resource application information to a first resource service module in a rear-end service layer under the condition that basic information of the first user passes verification, so that the first resource service module in the rear-end service layer calls one or more basic components in the rear-end service layer to complete a first resource application service according to the first resource application information, and first resource application service completion data are sent to a first resource database of the rear-end resource layer. By the scheme, the resource access request triggered by the user on the front-end page is sent to the service modules corresponding to the resources for processing, each service module uses the basic component to finish the corresponding service, and calls the corresponding resources on the resource layer, so that various resources of an IT department are managed in an integrated mode, data isolation is guaranteed, and the problems of disordered application of offline processes and fragmentation of data management are solved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a schematic flow chart diagram illustrating a method for processing a resource application provided herein;
fig. 2 is a schematic diagram illustrating a correspondence relationship between a service module in a back-end service layer and a database in a resource layer according to the present application;
fig. 3 is a schematic flowchart of a back-end service layer completing a system operation and maintenance resource application service provided by the present application;
FIG. 4 is a flow chart of a workflow component executing system operation and maintenance resource business logic provided by the present application;
fig. 5 is a schematic structural diagram of a system for processing a resource application provided in the present application.
Detailed Description
The present application will be described in further detail below with reference to the accompanying drawings by way of specific embodiments. In the following description, numerous details are set forth in order to provide a better understanding of the present application. However, those skilled in the art will readily recognize that some of the features may be omitted in different instances or may be replaced by other methods. In some instances, certain operations related to the present application have not been shown or described in the specification, in order not to obscure the core portions of the present application with excessive description. It is not necessary for those skilled in the art to describe these related operations in detail, and they can fully understand the related operations according to the description in the specification and the general technical knowledge in the field.
It will be understood that the terms "comprises" and "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is to be understood that the terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only, and is not intended to be limiting of the application. As used in the examples of this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
The method and the system for processing resource application provided by the embodiment of the application can be applied to financial service industry, logistics service industry, property management, large and medium-sized import and export trade companies, government and public institutions, research institutions, education service industry and the like in consumer goods industry, manufacturing industry, telecommunication service industry, silver insurance and the like, and can be specifically used for:
(1) key business process: such as resource information management, resource application management, orders, quote processing, procurement processing, contract review, customer telephone processing, supply chain management, and the like;
(2) administrative management, such as business trip application, overtime application, leave application, vehicle application, various office supplies application, purchase application, daily newspaper and weekly newspaper, etc.;
(3) personnel management class: staff training arrangement, performance appraisal, position change processing, staff archive information management and the like;
(4) finance-related classes: payment request, accounts receivable processing, daily reimbursement processing, business reimbursement, budget and plan application, and the like;
(5) the customer service class: customer information management, customer complaints, request handling, after-sales service management, and the like;
(6) special service classes: ISO series corresponding flow, quality management corresponding flow, product data information management, customs declaration processing of trade companies, goods tracking processing of logistics companies, and the like, and are not particularly limited herein.
Fig. 1 is a schematic flowchart of a method for processing resource applications, as shown in fig. 1, the method for processing resource applications includes the following steps:
s101: and sending a first resource access request triggered by the user accessing the front-end page to the interface layer.
In this embodiment, the first resource access request includes the basic information of the user and first resource application information. The basic information of the user may be verification information such as an account name and a password of the user, and may also be basic information of the user, for example: user name, department of belongingness, job title, etc. The first resource application information may be a software resource application, a software resource management application, a hardware resource management application, a version release information management application, a data authority management application, a Message Queue (MQ) account application, MQ account management, and the like, which is not specifically limited herein.
In this embodiment of the application, a front-end page may show a resource application system interface to a user and interact with the user, and the user may start to perform an application process of a resource by accessing the front-end page, where the front-end page may be a WEB page, an APP page, and the like, and the way for the user to access the front-end page may be through a PC, a mobile device, or other terminals, and is not specifically limited herein. Wherein, the development of the front-end page can be realized by using foreground codes, such as: hypertext Markup Language (HTML), Cascading Style Sheets (CSS), JavaScript, HTML5, Scalable Vector Graphics (SVG), and the like, which are not particularly limited herein.
In this embodiment, the sending of the first resource access request to the interface layer may be performed in a wired or wireless manner. The Wireless mode includes General Packet Radio Service (GPRS), Wireless Local Area Network (WLAN), ZigBee (ZigBee), Bluetooth (Bluetooth), Near Field Communication (NFC), and the like, and the wired mode includes a network cable, a copper wire, RS232, RS458, and the like. It should be understood that the above examples of communication methods are merely for illustration and should not be construed as limiting.
S102: and the interface layer sends the first resource application information to a first resource service module in a back-end service layer under the condition that the basic information of the first user passes verification.
In the embodiment of the application, the back-end service layer comprises a service component and a basic component, the service component comprises a plurality of service modules which independently process different service logics, and the basic component comprises a basic data component, a mail service component, a workflow service component and a file service component. The service module in the business component may be a system operation and maintenance application form service module, a basic operation and maintenance application form service module, a Database administration (DBA) application form service module, a resource Management (CMDB) service module, and the like, which are not specifically limited herein. The business assembly is divided into a plurality of service modules, so that the disorder of information under the condition of complex resource types can be avoided, the clarity of bottom data is ensured, and the maintainability and the extendibility of the system are utilized. It can be understood that the service module may be modified according to the enterprise resource application requirement, for example, a new server application service module is created according to the business requirement, or a basic operation and maintenance application form service module is deleted, which is not specifically limited herein.
In this embodiment of the present application, the first resource application information and the first resource service module have a corresponding relationship. That is to say, after determining that the corresponding service module in the service layer is the first resource service module according to the first resource application information in the first resource access request, the interface layer sends the first resource application information to the first resource service module. For example: the method comprises the steps that a user A needs to apply for system operation and maintenance, a user B needs to apply for basic operation and maintenance, a front-end page sends a system operation and maintenance service application triggered by the user A and a basic operation and maintenance service application triggered by the user B to an interface layer, the interface layer sends the system operation and maintenance service application of the user A to a system operation and maintenance application form service module in a rear-end service layer, and the basic operation and maintenance service application of the user B is sent to a basic operation and maintenance service module in the rear-end service layer. It is to be understood that the above examples are illustrative only and are not to be construed as limiting.
In the embodiment of the application, the back-end service layer is constructed by using a micro-service technology system different from the front-end page. That is to say, the front-end architecture and the back-end architecture are separated in the system development process, the front-end architecture considers page expression, browsing speed, browser compatibility, user experience and the like in a centralized manner, and the back-end architecture considers the problems of service logic, data security and storage in a centralized manner, so that the purpose of complete decoupling of front-end development and deployment is ensured.
In this embodiment of the present application, the interface layer may be a Gateway (Gateway) for implementing network interconnection between a front end and a back end of a system, and the interface layer may be used for wide area network interconnection and may also be used for local area network interconnection, which is not specifically limited herein. It can be understood that the interface layer is unique, that is, data of all front ends and data of all back ends interact through a unified gateway, so that the gateway can conveniently perform processing of related services such as unified risk interception, user right verification and the like.
S103: the first resource service module calls one or more basic components in a back-end service layer to complete a first resource application service according to the first resource application information, and sends the first resource application service completion data to a first resource database of the back-end resource layer.
In this embodiment of the present application, the first service module and the first resource database have a corresponding relationship. The back-end resource layer comprises a cache library, a workflow database, a service information database, a CMDB database and a file storage database. The cache library stores public information among all components in a back-end resource layer; the file storage database stores uploading files; the workflow database and the workflow service component have a corresponding relation, and data in the workflow database comprises one or more of workflow model information, workflow application records, approval information and workflow authorities. The service information database and a plurality of service modules in a back-end service layer service assembly have a corresponding relation, and data in the service information database comprises one or more of application form details and resource detailed attributes; the CMDB database is used for storing all the warehoused resources and is the only storage position after the resources are warehoused. Fig. 2 shows the correspondence between the service modules in the back-end service layer and the databases in the resource layer. It should be understood that fig. 2 is only an example and is not a specific limitation, and the resource application processing system provided by the present application may have more service modules and databases. The system is provided with a plurality of service modules, and a plurality of databases corresponding to the service modules can ensure that modules of different services can realize effective isolation of application information and resource information while ensuring independent service processing, ensure effective isolation between the resource information, know the allocation condition of resources in time and quickly position system errors for processing.
In this embodiment of the present application, the specific steps of the first resource service module in the backend service layer calling one or more basic components in the backend service layer to complete the first resource application service according to the first resource application information are as follows: the first service module calls one or more of a workflow service component, a file service component, a mail service component and a basic data component in a back-end service layer according to the first resource application information to execute an approval process of the first resource application; the first service module confirms a first resource state of a first database of a rear-end resource layer under the condition that the first resource application approval process passes; and under the condition that the first resource state is callable, calling the first resource from a back-end resource layer, and sending the first resource application service completion data to a first resource database of the back-end resource layer.
In this embodiment of the application, after the first service module calls the first resource from a backend resource layer, the method further includes: the first service module calls a mail component in the basic component and sends the first resource information to the first user mailbox; or, the first service module sends the first resource information to the interface layer; the interface layer sends the first resource information to the front-end page; the front-end page presents the first resource information to the first user. It can be understood that, when the first resource is a certain service resource, for example, a certain user a applies for a system operation and maintenance service, the first resource information after successful approval may be information that is applied successfully and waits for processing of the operation and maintenance service; when the first resource is a data application, for example, a user a applies for using administrator authority, and the first resource information after successful approval may be an administrator account password, etc., it should be understood that the above example is only used for specific description, and cannot be specifically limited.
For example, fig. 3 is a flowchart of a back-end service layer completing a system operation and maintenance resource application service provided by the present application. As shown in fig. 3, the first resource application at this time is a system operation and maintenance resource application, and the first service module is a system operation and maintenance service module, so that after the system operation and maintenance service module receives the system operation and maintenance resource application sent by the interface layer, the system operation and maintenance service module calls the basic data component and the workflow component to automatically execute the approval process, and after the approval process passes, the system operation and maintenance resource is called from the service database of the back-end resource layer under the condition that the system operation and maintenance resource state in the service database is determined to be callable, thereby completing the system operation and maintenance resource application service. It can be understood that when the approval process fails or the system operation and maintenance resource state is not adjustable, the application failure information is sent to the interface layer, the interface layer returns the application failure information to the front-end page, the front-end page displays the application failure information to the user, or the back-end service layer directly calls the mail component to send the application failure information to the user mailbox. It should be understood that the flow chart shown in fig. 3 is for illustration only and is not to be construed as being particularly limiting.
In this embodiment of the application, when the first resource service module calls the workflow service component, the workflow component automatically executes the first resource service logic according to a predefined flow, and after each activity in the workflow flow is completed, the completed data is stored in the workflow database in the resource layer, and then the next activity is performed, so that the whole-flow tracking, approval and statistics of the workflow are realized. Meanwhile, the workflow service component can be added into a user-defined authority system, and the authority control of the workflow is flexibly changed according to business requirements. Taking fig. 4 as an example, the workflow component of the present application is further described, fig. 4 is a schematic flow diagram of the workflow component provided in the present application for executing a system operation and maintenance resource business logic, as shown in fig. 4, after receiving a system operation and maintenance resource application, a back-end service layer invokes a basic data component and the workflow component to process the system operation and maintenance resource application, and the workflow component automatically executes the business logic of the system operation and maintenance service according to a predefined flow and stores a result of each flow activity in a workflow database in a resource layer, where the workflow flow shown in fig. 4 is only used for illustration, and in an actual system operation and maintenance service flow, more approval flows or confirmation flows may be possessed.
The following takes the user a as an example to further describe the embodiment of the present application, and assuming that the user a needs to apply for the system operation and maintenance resource, the user a first needs to log in an account name and a password on a front-end page, after the user a passes the verification, the user a may click a link applied for the system operation and maintenance on the front-end page, and then the user a may wait for the completion of the verification to obtain the system operation and maintenance resource. In the process of the user a system operation and maintenance application process, users with corresponding rights (for example, a department manager B and a system operation and maintenance responsible person C of the user a) can correspondingly receive an audit notification mail corresponding to the application, and the department manager B and the system operation and maintenance responsible person C can directly audit the application through the resource service application system by clicking a link in the mail. It is to be understood that the above examples are illustrative only and are not to be construed as limiting.
In this embodiment of the present application, the backend service layer further includes a service management component, where the service management component includes a plurality of management modules, and the plurality of management modules are configured to manage configuration, registration, and inter-component call management of business components and basic components in the backend resource layer. The service management module may be a registration discovery module, a gateway service module, a configuration management module, etc., and is not particularly limited herein. For example, a configuration management module in the service management component is used for creating a server application service module according to a service requirement, or deleting a basic operation and maintenance application form service module and the like; for example, using gateway management in the service management component to perform custom modifications on the interface layer gateway, etc., it should be understood that the above examples are only for specific illustration and are not to be construed as specific limitations.
According to the method, a first resource access request triggered by a first user is sent to an interface layer through a front-end page, the interface layer sends first resource application information to a first resource service module in a rear-end service layer under the condition that basic information of the first user passes verification, so that the first resource service module in the rear-end service layer calls one or more basic components in the rear-end service layer to complete a first resource application service according to the first resource access request, and first resource application service completion data are sent to a first resource database of the rear-end resource layer. By the scheme, the resource access request triggered by the user on the front-end page is sent to the service modules corresponding to the resources for processing, each service module uses the basic component to finish the corresponding service, and calls the corresponding resources on the resource layer, so that various resources of an IT department are managed in an integrated mode, data isolation is guaranteed, and the problems of disordered application of offline processes and fragmentation of data management are solved.
Fig. 5 is a schematic structural diagram of a processing resource application system provided in the present application, and as shown in fig. 5, the processing resource application system provided in the present application includes a front-end page 510, an interface layer 520, a back-end service layer 530 and a back-end resource layer 540,
the front-end page 510 is configured to send a first resource access request triggered by a user accessing the front-end page to the interface layer 520.
The interface layer 520 is configured to send the first resource application information to a first resource service module in a back-end service layer when the basic information of the first user passes verification, where the first resource application information and the first resource service module have a corresponding relationship, and the back-end service layer is constructed using a micro service technology system different from a front-end page.
The back-end service layer 530 is configured to use a first resource service module to call one or more basic components 532 in the back-end service layer according to the first resource application information to complete a first resource application service, and send data that the first resource application service is completed to a first resource database of the back-end resource layer, where the first resource module and the first resource database have a corresponding relationship.
In this embodiment, the first resource access request includes the basic information of the user and first resource application information. The basic information of the user may be verification information such as an account name and a password of the user, and may also be basic information of the user, for example: user name, department of belongingness, job title, etc. The first resource application information may be a software resource application, a software resource management application, a hardware resource management application, a version release information management application, a data authority management application, an MQ account management, and the like, and is not particularly limited herein.
In this embodiment of the present application, the front-end page 510 may show a resource application system interface to a user and interact with the user, and the user may start an application process of a resource by accessing the front-end page, where the front-end page may be a WEB page, an APP page, and the like, and the way for the user to access the front-end page may be through a PC, a mobile device, or other terminals, and is not specifically limited herein. Wherein, the development of the front-end page can be realized by using foreground codes, such as: HTML, CSS, JavaScript, HTML5, SVG, and the like, which are not particularly limited herein.
In this embodiment, the sending of the first resource access request to the interface layer 520 may be performed in a wired or wireless manner. The wireless mode includes GPRS, WLAN, ZigBee, Bluetooth, NFC, etc., and the wired mode includes network cable, copper wire, RS232, RS458, etc. It should be understood that the above examples of communication methods are merely for illustration and should not be construed as limiting.
In the embodiment of the present application, the back-end service layer includes a service component 531 and a basic component 532, the service component includes a plurality of service modules that independently process different service logics, and the basic component includes a basic data component, a mail service component, a workflow service component, and a file service component. The service module in the business component may be a system operation and maintenance application form service module, a basic operation and maintenance application form service module, a DBA application form service module, a CMDB service module, and the like, which is not specifically limited herein. The business assembly is divided into a plurality of service modules, so that the disorder of information under the condition of complex resource types can be avoided, the clarity of bottom data is ensured, and the maintainability and the extendibility of the system are utilized. It can be understood that the service module may be modified according to the enterprise resource application requirement, for example, a new server application service module is created according to the business requirement, or a basic operation and maintenance application form service module is deleted, which is not specifically limited herein.
In this embodiment of the present application, the first resource application information and the first resource service module have a corresponding relationship. That is to say, after determining that the corresponding service module in the service layer is the first resource service module according to the first resource application information, the interface layer sends the first resource application information to the first resource service module. For example: the method comprises the steps that a user A needs to apply for system operation and maintenance, a user B needs to apply for basic operation and maintenance, a front-end page sends a system operation and maintenance service application triggered by the user A and a basic operation and maintenance service application triggered by the user B to an interface layer, the interface layer sends the system operation and maintenance service application of the user A to a system operation and maintenance application form service module in a rear-end service layer, and the basic operation and maintenance service application of the user B is sent to a basic operation and maintenance service module in the rear-end service layer. It is to be understood that the above examples are illustrative only and are not to be construed as limiting.
In the embodiment of the application, the back-end service layer is constructed by using a micro-service technology system different from the front-end page. That is to say, the front-end architecture and the back-end architecture are separated in the system development process, the front-end architecture considers page expression, browsing speed, browser compatibility, user experience and the like in a centralized manner, and the back-end architecture considers the problems of service logic, data security and storage in a centralized manner, so that the purpose of complete decoupling of front-end development and deployment is ensured.
In this embodiment of the present application, the interface layer 520 may be a Gateway (Gateway) for implementing network interconnection between a front end and a back end of a system, and the interface layer may be used for wide area network interconnection and may also be used for local area network interconnection, which is not limited herein. It can be understood that the interface layer is unique, that is, data of all front ends and data of all back ends interact through a unified gateway, so that the gateway can conveniently perform processing of related services such as unified risk interception, user right verification and the like.
In this embodiment of the present application, the first service module and the first resource database have a corresponding relationship. The back-end resource layer comprises a cache library, a workflow database, a service information database, a CMDB database and a file storage database. The cache library stores public information among all components in a back-end resource layer; the file storage database stores uploading files; the workflow database and the workflow service component have a corresponding relation, and data in the workflow database comprises one or more of workflow model information, workflow application records, approval information and workflow authorities. The service information database and a plurality of service modules in a back-end service layer service assembly have a corresponding relation, and data in the service information database comprises one or more of application form details and resource detailed attributes; the CMDB database is used for storing all the warehoused resources and is the only storage position after the resources are warehoused. Fig. 2 shows the correspondence between the service modules in the back-end service layer and the databases in the resource layer. It should be understood that fig. 2 is only an example and is not a specific limitation, and the resource application processing system provided by the present application may have more service modules and databases. The system is provided with a plurality of service modules, and a plurality of databases corresponding to the service modules can ensure that modules of different services can realize effective isolation of application information and resource information while ensuring independent service processing, ensure effective isolation between the resource information, know the allocation condition of resources in time and quickly position system errors for processing.
In this embodiment of the present application, the specific steps of the first resource service module in the back-end service layer 530 invoking one or more basic components 532 in the back-end service layer according to the first resource application information to complete the first resource application service are as follows: the first service module calls one or more of a workflow service component, a file service component, a mail service component and a basic data component in a back-end service layer according to the first resource application information to execute an approval process of the first resource application; the first service module confirms a first resource state of a first database of a rear-end resource layer under the condition that the first resource application approval process passes; and under the condition that the first resource state is callable, calling the first resource from a back-end resource layer, and sending the first resource application service completion data to a first resource database of the back-end resource layer.
In this embodiment of the application, after the first service module calls the first resource from a backend resource layer, the method further includes: the first service module calls a mail component in the basic component 532 and sends the first resource information to the first user mailbox; or, the first service module sends the first resource information to the interface layer; the interface layer sends the first resource information to the front-end page; the front-end page presents the first resource information to the first user. It can be understood that, when the first resource is a certain service resource, for example, a certain user a applies for a system operation and maintenance service, the first resource information after successful approval may be information that is applied successfully and waits for processing of the operation and maintenance service; when the first resource is a data application, for example, a user a applies for using administrator authority, and the first resource information after successful approval may be an administrator account password, etc., it should be understood that the above example is only used for specific description, and cannot be specifically limited.
For example, fig. 3 is a flowchart of a back-end service layer completing a system operation and maintenance resource application service provided by the present application. As shown in fig. 3, the first resource application at this time is a system operation and maintenance resource application, and the first service module is a system operation and maintenance service module, so that after the system operation and maintenance service module receives the system operation and maintenance resource application sent by the interface layer, the system operation and maintenance service module calls the basic data component and the workflow component to automatically execute the approval process, and after the approval process passes, the system operation and maintenance resource is called from the service database of the back-end resource layer under the condition that the system operation and maintenance resource state in the service database is determined to be callable, thereby completing the system operation and maintenance resource application service. It can be understood that when the approval process fails or the system operation and maintenance resource state is not adjustable, the application failure information is sent to the interface layer, the interface layer returns the application failure information to the front-end page, the front-end page displays the application failure information to the user, or the back-end service layer directly calls the mail component to send the application failure information to the user mailbox. It should be understood that the flow chart shown in fig. 3 is for illustration only and is not to be construed as being particularly limiting.
In this embodiment of the application, when the first resource service module calls the workflow service component, the workflow component automatically executes the first resource service logic according to a predefined flow, and after each activity in the workflow flow is completed, the completed data is stored in the workflow database in the resource layer, and then the next activity is performed, so that the whole-flow tracking, approval and statistics of the workflow are realized. Meanwhile, the workflow service component can be added into a user-defined authority system, and the authority control of the workflow is flexibly changed according to business requirements. Taking fig. 4 as an example, a workflow component of the present application is further described, fig. 4 is a schematic flow diagram of the workflow component provided in the present application for executing a system operation and maintenance resource business logic, as shown in fig. 4, after receiving a system operation and maintenance resource application, a back-end service layer invokes a basic data component and the workflow component to process the system operation and maintenance resource application, and the workflow component automatically executes the business logic of the system operation and maintenance service according to a predefined flow and stores a result of each flow activity in a workflow database in a resource layer, where the workflow flow shown in fig. 4 is only used for illustration, and in an actual system operation and maintenance service flow, more approval flows or confirmation flows may be possessed.
The following takes the user a as an example to further describe the embodiment of the present application, and assuming that the user a needs to apply for the system operation and maintenance resource, the user a first needs to log in an account name and a password on a front-end page, after the user a passes the verification, the user a may click a link applied for the system operation and maintenance on the front-end page, and then the user a may wait for the completion of the verification to obtain the system operation and maintenance resource. In the process of the user a system operation and maintenance application process, users with corresponding rights (for example, a department manager B and a system operation and maintenance responsible person C of the user a) can correspondingly receive an audit notification mail corresponding to the application, and the department manager B and the system operation and maintenance responsible person C can directly audit the application through the resource service application system by clicking a link in the mail. It is to be understood that the above examples are illustrative only and are not to be construed as limiting.
In this embodiment, the backend service layer further includes a service management component 533, where the service management component includes a plurality of management modules, and the plurality of management modules are configured to perform configuration management, registration management, and inter-component call management on the service component and the basic component in the backend resource layer. The service management module may be a registration discovery module, a gateway service module, a configuration management module, etc., and is not particularly limited herein. For example, a configuration management module in the service management component is used for creating a server application service module according to a service requirement, or deleting a basic operation and maintenance application form service module and the like; for example, using gateway management in the service management component to perform custom modifications on the interface layer gateway, etc., it should be understood that the above examples are only for specific illustration and are not to be construed as specific limitations.
According to the method, a first resource access request triggered by a first user is sent to an interface layer through a front-end page, the interface layer sends first resource application information to a first resource service module in a rear-end service layer under the condition that basic information of the first user passes verification, so that the first resource service module in the rear-end service layer calls one or more basic components in the rear-end service layer to complete a first resource application service according to the first resource application information, and first resource application service completion data are sent to a first resource database of the rear-end resource layer. By the scheme, the resource access request triggered by the user on the front-end page is sent to the service modules corresponding to the resources for processing, each service module uses the basic component to finish the corresponding service, and calls the corresponding resources on the resource layer, so that various resources of an IT department are managed in an integrated mode, data isolation is guaranteed, and the problems of disordered application of offline processes and fragmentation of data management are solved.
In the embodiments provided in the present application, it should be understood that the disclosed method and system can be implemented in other ways. For example, the above-described system embodiments are merely illustrative, and for example, the division of the units is only one logical functional division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. Further, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, systems or units, and may also be an electrical, mechanical or other form of connection.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may also be distributed on multiple network units, and some or all of the units may be selected according to actual needs to implement the embodiments of the present application.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially or partially contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
While the invention has been described with reference to specific embodiments, the scope of the invention is not limited thereto, and those skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the invention. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A method for processing a resource application, comprising:
the method comprises the steps that a front-end page sends a first resource access request triggered by a first user to an interface layer, wherein the first resource access request comprises basic information of the first user and first resource application information;
the interface layer sends the first resource application information to a first resource service module in a back-end service layer under the condition that the basic information of the first user passes verification, wherein the first resource application information and the first resource service module have a corresponding relation, and the back-end service layer is constructed by using a micro-service technology system different from a front-end page;
and the first resource service module in the back-end service layer calls one or more basic components in the back-end service layer to complete a first resource application service according to the first resource application information, and sends the first resource application service completion data to a first resource database of the back-end resource layer, wherein the first resource module and the first resource database have a corresponding relation.
2. The method of claim 1, wherein the back-end service layer further comprises a business component, wherein the business component comprises a plurality of service modules that independently process different business logic, and wherein the base component comprises a base data component, a mail service component, a workflow service component, and a file service component.
3. The method of claim 2, wherein the invoking, by the first resource service module in the backend service layer according to the first resource application information, one or more base components in the backend service layer to complete the first resource application service comprises:
the first service module calls one or more of a workflow service component, a file service component, a mail service component and a basic data component in a back-end service layer according to the first resource application information to execute an approval process of the first resource application;
the first service module confirms a first resource state of a first database of a rear-end resource layer under the condition that the first resource application approval process passes;
and under the condition that the first resource state is callable, calling the first resource from a back-end resource layer, and sending the first resource application service completion data to a first resource database of the back-end resource layer.
4. The method of claim 3, wherein after the first service module invokes the first resource from a backend resource layer, the method further comprises:
the first service module calls a mail component in the basic component and sends the first resource information to the first user mailbox; or,
the first service module sends the first resource information to the interface layer;
the interface layer sends the first resource information to the front-end page;
the front-end page presents the first resource information to the first user.
5. The method of claim 2, wherein the back-end service layer further comprises a service management component, and the service management component comprises a plurality of management modules, and the plurality of management modules are configured to perform configuration management, registration management, and inter-component call management on the business components and the base components in the back-end resource layer.
6. A system for processing resource application is characterized by comprising a front-end page, an interface layer, a back-end service layer and a back-end resource layer:
the front-end page is used for sending a first resource access request triggered by a user accessing the front-end page to the interface layer;
the interface layer is used for sending the first resource application information to a first resource service module in a back-end service layer under the condition that the basic information of the first user passes verification, wherein the first resource application information and the first resource service module have a corresponding relation, and the back-end service layer is constructed by using a micro-service technology system different from a front-end page;
the back-end service layer is used for calling one or more basic components in the back-end service layer by using a first resource service module according to the first resource application information to complete a first resource application service and sending the first resource application service completion data to a first resource database of the back-end resource layer, wherein the first resource module and the first resource database have a corresponding relation;
the back-end resource layer is used for providing and storing data.
7. The system of claim 6, wherein the back-end service layer further comprises a business component, wherein the business component comprises a plurality of service modules for independently processing different business logic, and wherein the basic component comprises a basic data component, a mail service component, a workflow service component, and a file service component.
8. The system of claim 7, wherein the back-end service layer is specifically configured to use the first service module to invoke one or more of a workflow service component, a file service component, a mail service component, and a basic data component in the back-end service layer according to the first resource application information, and execute an approval process of the first resource application;
the back-end service layer is specifically configured to confirm a first resource state of a first database of the back-end resource layer by using the first service module when the first resource application approval process passes;
the back-end service layer is specifically configured to call the first resource from the back-end resource layer and send the first resource application service completion data to a first resource database of the back-end resource layer when the first resource state is callable.
9. The system of claim 8,
the first service module is also used for calling a mail component in a basic component after calling the first resource from a back-end resource layer, and sending the first resource information to the first user mailbox; or,
the first service module is further configured to send the first resource information to the interface layer;
the interface layer is further configured to send the first resource information to the front-end page;
the front-end page is further used for displaying the first resource information to the first user.
10. The system of claim 7, wherein the back-end service layer further comprises a service management component, and the service management component comprises a plurality of management modules, and the plurality of management modules are configured to perform configuration management, registration management, and inter-component call management on a plurality of components and modules in the back-end resource layer.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811433139.XA CN109740841A (en) | 2018-11-28 | 2018-11-28 | A kind of method and system of process resource application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811433139.XA CN109740841A (en) | 2018-11-28 | 2018-11-28 | A kind of method and system of process resource application |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109740841A true CN109740841A (en) | 2019-05-10 |
Family
ID=66358176
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811433139.XA Withdrawn CN109740841A (en) | 2018-11-28 | 2018-11-28 | A kind of method and system of process resource application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109740841A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110457890A (en) * | 2019-07-15 | 2019-11-15 | 中国平安人寿保险股份有限公司 | Right management method and device, electronic equipment and storage medium based on multisystem |
| CN112085412A (en) * | 2020-09-21 | 2020-12-15 | 王渡江 | Resource optimization distribution system and distribution method |
| CN112464194A (en) * | 2020-11-25 | 2021-03-09 | 数字广东网络建设有限公司 | Resource acquisition method and device, computer equipment and storage medium |
| CN113419732A (en) * | 2021-06-30 | 2021-09-21 | 青岛海信智慧生活科技股份有限公司 | Property service management system, deployment method and device, equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140075004A1 (en) * | 2012-08-29 | 2014-03-13 | Dennis A. Van Dusen | System And Method For Fuzzy Concept Mapping, Voting Ontology Crowd Sourcing, And Technology Prediction |
| CN105872094A (en) * | 2016-05-31 | 2016-08-17 | 山东大学 | Service robot cloud platform interface system based on SOA and working method thereof |
| CN107612896A (en) * | 2017-09-05 | 2018-01-19 | 新智云数据服务有限公司 | Employee's self-aid system and its application process |
| CN107786379A (en) * | 2017-11-15 | 2018-03-09 | 四川省龙逸凤集网络科技有限公司 | A kind of layering cloud management platform based on micro services framework |
| CN108346028A (en) * | 2017-01-24 | 2018-07-31 | 阿里巴巴集团控股有限公司 | A kind of business approval processing method, apparatus and system |
-
2018
- 2018-11-28 CN CN201811433139.XA patent/CN109740841A/en not_active Withdrawn
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140075004A1 (en) * | 2012-08-29 | 2014-03-13 | Dennis A. Van Dusen | System And Method For Fuzzy Concept Mapping, Voting Ontology Crowd Sourcing, And Technology Prediction |
| CN105872094A (en) * | 2016-05-31 | 2016-08-17 | 山东大学 | Service robot cloud platform interface system based on SOA and working method thereof |
| CN108346028A (en) * | 2017-01-24 | 2018-07-31 | 阿里巴巴集团控股有限公司 | A kind of business approval processing method, apparatus and system |
| CN107612896A (en) * | 2017-09-05 | 2018-01-19 | 新智云数据服务有限公司 | Employee's self-aid system and its application process |
| CN107786379A (en) * | 2017-11-15 | 2018-03-09 | 四川省龙逸凤集网络科技有限公司 | A kind of layering cloud management platform based on micro services framework |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110457890A (en) * | 2019-07-15 | 2019-11-15 | 中国平安人寿保险股份有限公司 | Right management method and device, electronic equipment and storage medium based on multisystem |
| CN112085412A (en) * | 2020-09-21 | 2020-12-15 | 王渡江 | Resource optimization distribution system and distribution method |
| CN112085412B (en) * | 2020-09-21 | 2023-11-17 | 王渡江 | Resource optimization distribution system and distribution method |
| CN112464194A (en) * | 2020-11-25 | 2021-03-09 | 数字广东网络建设有限公司 | Resource acquisition method and device, computer equipment and storage medium |
| CN113419732A (en) * | 2021-06-30 | 2021-09-21 | 青岛海信智慧生活科技股份有限公司 | Property service management system, deployment method and device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7516103B1 (en) | Method and apparatus for facilitating electronic acquisition and maintenance of goods and services via the internet | |
| CN109740841A (en) | A kind of method and system of process resource application | |
| US8965801B2 (en) | Provision of support services as a service | |
| CN102663531B (en) | Cloud based master data management | |
| US9584949B2 (en) | Cloud based master data management architecture | |
| JP2007287151A (en) | Software model business process variant type | |
| EP3020017A1 (en) | Method and system for creating tax configuration templates | |
| EP2289030A2 (en) | Business software application system and method | |
| CN113312116B (en) | System and method for offloading application extension script execution from an application hosting infrastructure | |
| CN112801607A (en) | Management service platform and construction method | |
| US20090171758A1 (en) | Architectural design for physical inventory application software | |
| CN105931004A (en) | Webpage-based multi-terminal storage electronic business management system | |
| CN115705560B (en) | Message mapping method and system for handling template changes | |
| CN105335811A (en) | Mobile communication-based commodity information management system | |
| AU2008203816B2 (en) | Message sequence management of enterprise based correlated events | |
| US8321308B2 (en) | Architectural design for manual invoicing application software | |
| CN112347344A (en) | Management method and device for multi-period additional resource certificate and electronic equipment | |
| Funk | The future of mobile phone-based Intranet applications: A view from Japan | |
| KR102311511B1 (en) | Open market system with enhanced security by applying blockchain | |
| EP2145297A1 (en) | Methods and apparatus for exposing workflow process definitions as business objects | |
| CN114693035A (en) | Method, system and device for generating time limit task of enterprise intellectual property management system | |
| CN110032703A (en) | A kind of enterprise web site trustship method and system | |
| CN113643014B (en) | Block chain-based transaction management method, apparatus, device, medium, and program | |
| Sadewa et al. | Complaint Handling Ticketing Application Web Based Using Codeigniter Framework (Case Study at PT Indosat Ooredoo Tbk Jakarta) | |
| CN118071504B (en) | Transaction information penetration management method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 518000 Guangdong city of Shenzhen province Qianhai Shenzhen Hong Kong cooperation zone before Bay Road No. 1 building 201 room A (located in Shenzhen Qianhai business secretary Co. Ltd.) Applicant after: Shenzhen Rongyimai Information Technology Co., Ltd. Address before: 518000 Guangdong city of Shenzhen province Qianhai Shenzhen Hong Kong cooperation zone before Bay Road No. 1 building 201 room A (located in Shenzhen Qianhai business secretary Co. Ltd.) Applicant before: Maimaiti Mdt InfoTech Ltd, Shenzhen |
|
| CB02 | Change of applicant information | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20190510 |
|
| WW01 | Invention patent application withdrawn after publication |