Extension deployment method of portal system in multiple data centers

Abstract

The invention provides an extension deployment method of a portal system in a multi-data center, and the method comprises the steps: determining a first portal system which carries a first business system, the first portal system comprises a first middle channel application and a first database, and a data read-write link is configured between the first middle channel application and the first database; at least one second portal system is configured on the basis of the first portal system, a second service system is mounted on the second portal system, the second portal system comprises a second middle station application and a second database, and a data reading link is configured between the second middle station application and the second database; a data writing link is configured between the second middle table application and the first database, a data copying link is configured between the second database and the target database, and the target database is the first database or a database which keeps data synchronization with the first database. Therefore, the requirements of different types of data centers on the portal system can be met, and the expansibility of the portal system is improved.

Description

Technical Field

[0001] The present disclosure relates to the technical field of software development, and particularly to a method for expanding and deploying a portal system in multiple data centers. Background Art

[0002] A portal system is a front-end system that integrates multiple applications. It is the first system that users encounter after logging in, and generally, it can be used to jump between multiple similar business systems. Multi-Active Data Center means that multiple data centers geographically distributed in different regions provide services externally simultaneously, and data real-time synchronization and load balancing can be achieved between these data centers. The main purpose of this architecture is to ensure that enterprise critical business systems can still operate stably and maintain business continuity in the face of various unexpected events.

[0003] In the related art, portal systems generally integrate multiple sets of business systems, and it is relatively difficult to achieve expanded deployment in multiple data centers. Summary of the Invention

[0004] The present disclosure aims to solve at least one of the technical problems in the related art to some extent.

[0005] To this end, an object of the present disclosure is to provide a method, device, computer device, and storage medium for expanding and deploying a portal system in multiple data centers, whereby it can adapt to the requirements of different types of data centers for the portal system, thereby effectively improving the expanded deployment effect of the portal system in multiple data centers.

[0006] To achieve the above object, the method for expanding and deploying a portal system in multiple data centers according to the first aspect embodiment of the present disclosure includes:

[0007] Determine a first portal system, where the first portal system mounts a first business system, and the first portal system includes: a first middleware application and a first database, and a data read-write link is configured between the first middleware application and the first database;

[0008] Configure at least one second portal system based on the first portal system, where the second portal system mounts a second business system, and the second portal system includes: a second middleware application and a second database, a data read link is configured between the second middleware application and the second database, a data write link is configured between the second middleware application and the first database, and a data replication link is configured between the second database and a target database, where the target database is the first database or a database that keeps data synchronized with the first database.

[0009] Optionally, in some embodiments, the method further includes:

[0010] Configuring a first disaster recovery portal system based on the first portal system, where the first disaster recovery portal system mounts a first disaster recovery service system corresponding to the first business system. The first disaster recovery portal system includes: a first disaster recovery middleware application and a first disaster recovery database. A data reading link is configured between the first disaster recovery middleware application and the first disaster recovery database, a data writing link is configured between the first disaster recovery middleware application and the first database, and a data replication link is configured between the first disaster recovery database and the first database.

[0011] Optionally, in some embodiments, the method further includes:

[0012] Configuring a second disaster recovery portal system based on the second portal system, where the second disaster recovery portal system mounts a second disaster recovery service system corresponding to the second business system. The second disaster recovery portal system includes: a second disaster recovery middleware application and a second disaster recovery database. A data reading link is configured between the second disaster recovery middleware application and the second disaster recovery database, a data writing link is configured between the second disaster recovery middleware application and the second database, and a data replication link is configured between the second disaster recovery database and the second database.

[0013] Optionally, in some embodiments, the target database is determined in the following manner:

[0014] Marking the first portal system and the portal systems extended and deployed based on the first portal system as deployed portal systems;

[0015] Determining the data transmission distance between the second portal system and each of the deployed portal systems;

[0016] Determining the minimum value among at least one of the data transmission distances;

[0017] Taking the database in the deployed portal system corresponding to the minimum value as the target database.

[0018] To achieve the above object, an extended deployment device for portal systems in multiple data centers according to the second aspect embodiments of the present disclosure includes:

[0019] A determination module, configured to determine a first portal system, where the first portal system mounts a first business system, and the first portal system includes: a first middleware application and a first database, and a data reading and writing link is configured between the first middleware application and the first database;

[0020] A first configuration module, configured to configure at least one second portal system based on the first portal system, where the second portal system mounts a second service system, and the second portal system includes: a second middle platform application and a second database, a data reading link is configured between the second middle platform application and the second database, a data writing link is configured between the second middle platform application and the first database, a data replication link is configured between the second database and a target database, and the target database is the first database or a database that keeps data synchronized with the first database.

[0021] Optionally, in some embodiments, the apparatus further includes:

[0022] A second configuration module, configured to configure a first disaster recovery portal system based on the first portal system, where the first disaster recovery portal system mounts a first disaster recovery service system corresponding to the first service system, and the first disaster recovery portal system includes: a first disaster recovery middle platform application and a first disaster recovery database, a data reading link is configured between the first disaster recovery middle platform application and the first disaster recovery database, a data writing link is configured between the first disaster recovery middle platform application and the first database, and a data replication link is configured between the first disaster recovery database and the first database.

[0023] Optionally, in some embodiments, the apparatus further includes:

[0024] A third configuration module, configured to configure a second disaster recovery portal system based on the second portal system, where the second disaster recovery portal system mounts a second disaster recovery service system corresponding to the second service system, and the second disaster recovery portal system includes: a second disaster recovery middle platform application and a second disaster recovery database, a data reading link is configured between the second disaster recovery middle platform application and the second disaster recovery database, a data writing link is configured between the second disaster recovery middle platform application and the second database, and a data replication link is configured between the second disaster recovery database and the second database.

[0025] The computer device provided in the third aspect embodiment of the present disclosure includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, and when the processor executes the program, it implements the method for extended deployment of the portal system in multiple data centers proposed in the first aspect embodiment of the present disclosure.

[0026] The fourth aspect embodiment of the present disclosure proposes a non-transitory computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, it implements the method for extended deployment of the portal system in multiple data centers proposed in the first aspect embodiment of the present disclosure.

[0027] A computer program product is provided in the fifth aspect of the present disclosure. When the instructions in the computer program product are executed by a processor, the method for extended deployment of a portal system in multiple data centers as proposed in the first aspect of the present disclosure is executed.

[0028] The method, device, computer equipment, and storage medium for extended deployment of a portal system in multiple data centers provided by the present disclosure determine a first portal system, where the first portal system mounts a first business system. The first portal system includes: a first middleware application and a first database, and a data read-write link is configured between the first middleware application and the first database; at least one second portal system is configured based on the first portal system, where the second portal system mounts a second business system. The second portal system includes: a second middleware application and a second database, a data read link is configured between the second middleware application and the second database, a data write link is configured between the second middleware application and the first database, and a data replication link is configured between the second database and a target database, where the target database is the first database or a database that is synchronized with the first database in terms of data. Thus, it can meet the requirements of different types of data centers for the portal system, thereby effectively improving the extended deployment effect of the portal system in multiple data centers.

[0029] Additional aspects and advantages of the present disclosure will be partially given in the following description, partially become apparent from the following description, or be understood through the practice of the present disclosure. Description of the Drawings

[0030] The above and / or additional aspects and advantages of the present disclosure will become apparent and be readily understood from the following description of the embodiments in conjunction with the drawings, where:

[0031] Figure 1 is a schematic flowchart of a method for extended deployment of a portal system in multiple data centers proposed in an embodiment of the present disclosure;

[0032] Figure 2 is a schematic flowchart of a method for extended deployment of a portal system in multiple data centers proposed in another embodiment of the present disclosure;

[0033] Figure 3 is a schematic diagram of the initial portal system deployment structure proposed by the present disclosure;

[0034] Figure 4 is a schematic diagram of a multi-active architecture proposed by the present disclosure;

[0035] Figure 5 is a schematic diagram of a multi-active architecture and a disaster recovery architecture proposed by the present disclosure;

[0036] Figure 6 is a schematic diagram of a multi-computer room extension structure proposed by the present disclosure;

[0037] Figure 7 It is a schematic structural diagram of an extended deployment device of a portal system in multiple data centers proposed in an embodiment of the present disclosure;

[0038] Figure 8 It is a schematic structural diagram of an extended deployment device of a portal system in multiple data centers proposed in another embodiment of the present disclosure;

[0039] Figure 9 It shows a block diagram of an exemplary computer device suitable for implementing the embodiments of the present disclosure. Specific Embodiments

[0040] The embodiments of the present disclosure will be described in detail below. The examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements with the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present disclosure and should not be construed as a limitation of the present disclosure. On the contrary, the embodiments of the present disclosure include all changes, modifications, and equivalents that fall within the spirit and scope of the appended claims.

[0041] Figure 1 It is a schematic flowchart of a method for extended deployment of a portal system in multiple data centers proposed in an embodiment of the present disclosure.

[0042] It should be noted that, in this embodiment, the execution subject of the method for extended deployment of a portal system in multiple data centers is an extended deployment device of a portal system in multiple data centers. This device can be implemented in software and / or hardware, and this device can be configured in a computer device. The computer device can include, but is not limited to, a terminal, a server, etc. For example, the terminal can be a mobile phone, a personal digital assistant, etc.

[0043] As Figure 1 shown, the method for extended deployment of a portal system in multiple data centers includes:

[0044] S101: Determine a first portal system. Among them, the first portal system mounts a first business system. The first portal system includes: a first middle platform application and a first database, and a data read / write link is configured between the first middle platform application and the first database.

[0045] Among them, the first portal system may refer to the initial portal system that has not been extended in the embodiments of the present disclosure. The type of the first portal system is not limited in the embodiments of the present disclosure.

[0046] Among them, the first business system may refer to the business system carried in the first portal system.

[0047] It is understandable that in the embodiments of the present disclosure, one or more business systems can be carried on the first portal system, and there is no limitation thereto.

[0048] Among them, the first middleware application and the first database respectively refer to the middleware application and the database configured in the first portal system.

[0049] It is understandable that in the embodiments of the present disclosure, one or more first middleware applications can be configured in the first portal system, and there is no limitation thereto.

[0050] Among them, the data read / write link refers to a link that can implement data reading and data writing functions.

[0051] That is to say, in the embodiments of the present disclosure, the first middleware application can perform data reading and data writing operations on the first database.

[0052] S102: Configure at least one second portal system based on the first portal system. Among them, the second portal system carries a second business system. The second portal system includes: a second middleware application and a second database. A data reading link is configured between the second middleware application and the second database. A data writing link is configured between the second middleware application and the first database. A data replication link is configured between the second database and the target database. The target database is the first database or a database that is synchronized with the first database.

[0053] Among them, the second portal system refers to a portal system that is extended and deployed based on the above-mentioned first portal system in the embodiments of the present disclosure. In the embodiments of the present disclosure, there is no limitation on the type and quantity of the second portal system.

[0054] Among them, the second business system may refer to a business system carried on the above-mentioned second portal system. In the embodiments of the present disclosure, there is no limitation on the type and quantity of the second business system.

[0055] Among them, the target database refers to a database used for data replication of the second database in the embodiments of the present disclosure. For example, it may be the above-mentioned first database, or any database that is synchronized with the first database.

[0056] Optionally, in some embodiments, the target database is determined based on the following method: Mark the first portal system and the portal systems extended and deployed based on the first portal system as deployed portal systems; Determine the data transmission distance between the second portal system and each deployed portal system; Determine the minimum value among at least one data transmission distance; Use the database in the deployed portal system corresponding to the minimum value as the target database. Thus, the data transmission efficiency between the target database and the second database can be ensured, thereby effectively improving the working performance of the second portal system.

[0057] Among them, the portal system deployed by extending the first portal system can be, for example, the second portal system deployed previously, or the disaster recovery system corresponding to the first portal system, or the disaster recovery system corresponding to the second portal system, etc., and there is no limitation thereto.

[0058] Among them, the data transmission distance can be used to describe the distance that the data needs to pass through during the data transmission between different databases.

[0059] It can be understood that the transmission distance is related to the cost required for data transmission (economic cost and time cost). Therefore, in the embodiments of the present disclosure, the first transmission distance between the second disaster recovery database and the first database can be determined; the second transmission distance between the second disaster recovery database and the second database can be determined; the third transmission distance between the second disaster recovery database and the first disaster recovery database can be determined; the minimum value among the first transmission distance, the second transmission distance, and the third transmission distance can be determined; and the database corresponding to the minimum value is used as the target database to ensure the practicability of the target database.

[0060] Among them, the second middle platform application and the second database refer to the middle platform application and the database configured in the second portal system.

[0061] Among them, the data reading link refers to a link that can provide a data reading function.

[0062] Among them, the data writing link refers to a link that can provide a data writing function.

[0063] Among them, the data replication link refers to a link that can provide a data replication function.

[0064] That is to say, in the embodiments of the present disclosure, when configuring the second portal system based on the first portal system, the second database in the second portal system can be configured as a read-only slave, and the second database replicates the data in the target database through the data replication link to keep the data of the two databases consistent. The portal middle platform of the second portal system performs read-write separation, accessing the local database for read traffic and connecting to the first database for write traffic.

[0065] In this embodiment, a first portal system is determined. The first portal system mounts a first business system and includes a first middleware application and a first database. A data read-write link is configured between the first middleware application and the first database. At least one second portal system is configured based on the first portal system. The second portal system mounts a second business system and includes a second middleware application and a second database. A data read link is configured between the second middleware application and the second database, a data write link is configured between the second middleware application and the first database, and a data replication link is configured between the second database and a target database, where the target database is the first database or a database that keeps data synchronized with the first database. Thus, the requirements of different types of data centers for the portal system can be met, effectively improving the extended deployment effect of portal systems in multiple data centers.

[0066] Figure 2 It is a schematic flowchart of a method for extended deployment of a portal system in multiple data centers proposed in another embodiment of the present disclosure.

[0067] As Figure 2 shown, the method for extended deployment of the portal system in multiple data centers includes:

[0068] S201: Determine a first portal system, where the first portal system mounts a first business system and includes a first middleware application and a first database. A data read-write link is configured between the first middleware application and the first database.

[0069] S202: Configure at least one second portal system based on the first portal system, where the second portal system mounts a second business system and includes a second middleware application and a second database. A data read link is configured between the second middleware application and the second database, a data write link is configured between the second middleware application and the first database, and a data replication link is configured between the second database and a target database, where the target database is the first database or a database that keeps data synchronized with the first database.

[0070] For the description and explanation of S201 and S202, please refer to the above embodiment specifically and will not be elaborated here.

[0071] S203: Configure a first disaster recovery portal system based on the first portal system, where the first disaster recovery portal system mounts a first disaster recovery business system corresponding to the first business system and includes a first disaster recovery middleware application and a first disaster recovery database. A data read link is configured between the first disaster recovery middleware application and the first disaster recovery database, a data write link is configured between the first disaster recovery middleware application and the first database, and a data replication link is configured between the first disaster recovery database and the first database.

[0072] Among them, the first disaster recovery portal system refers to a dedicated facility or system that provides disaster recovery and data backup services for the first portal system. This first disaster recovery portal system can work instead of the first portal system when the first portal system is unable to provide services.

[0073] Among them, the first disaster recovery business system refers to the disaster recovery business system configured corresponding to the above-mentioned first business system, which is used to work instead of the above-mentioned first business system.

[0074] Among them, the first disaster recovery middle platform application and the first disaster recovery database refer to the middle platform application and database configured in the first disaster recovery portal system.

[0075] That is to say, in the embodiment of the present disclosure, a first disaster recovery portal system can be configured based on the first portal system. Among them, the first disaster recovery portal system mounts the first disaster recovery business system corresponding to the first business system. The first disaster recovery portal system includes: a first disaster recovery middle platform application and a first disaster recovery database. A data reading link is configured between the first disaster recovery middle platform application and the first disaster recovery database, a data writing link is configured between the first disaster recovery middle platform application and the first database, and a data replication link is configured between the first disaster recovery database and the first database. Thus, when the first portal system fails, the first disaster recovery portal system can replace it in time, thereby effectively improving the robustness of the working performance of the portal system.

[0076] S204: Configure a second disaster recovery portal system based on the second portal system. Among them, the second disaster recovery portal system mounts the second disaster recovery business system corresponding to the second business system. The second disaster recovery portal system includes: a second disaster recovery middle platform application and a second disaster recovery database. A data reading link is configured between the second disaster recovery middle platform application and the second disaster recovery database, a data writing link is configured between the second disaster recovery middle platform application and the second database, and a data replication link is configured between the second disaster recovery database and the second database.

[0077] Among them, the second disaster recovery portal system refers to the disaster recovery portal system configured for the second portal system in the embodiment of the present disclosure. This second disaster recovery portal system can work instead of the second portal system when the second portal system fails.

[0078] Among them, the second disaster recovery middle platform application and the second disaster recovery database refer to the middle platform application and database configured in the second disaster recovery portal system.

[0079] That is to say, in the embodiments of the present disclosure, the second disaster recovery portal system can be configured based on the second portal system. Among them, the second disaster recovery portal system mounts the second disaster recovery service system corresponding to the second service system. The second disaster recovery portal system includes: a second disaster recovery middleware application and a second disaster recovery database. A data reading link is configured between the second disaster recovery middleware application and the second disaster recovery database, a data writing link is configured between the second disaster recovery middleware application and the second database, and a data replication link is configured between the second disaster recovery database and the second database. Thus, the robustness of the second portal system can be effectively improved.

[0080] In this embodiment, by configuring the first disaster recovery portal system based on the first portal system, where the first disaster recovery portal system mounts the first disaster recovery service system corresponding to the first service system, the first disaster recovery portal system includes: a first disaster recovery middleware application and a first disaster recovery database. A data reading link is configured between the first disaster recovery middleware application and the first disaster recovery database, a data writing link is configured between the first disaster recovery middleware application and the first database, and a data replication link is configured between the first disaster recovery database and the first database. Thus, when the first portal system fails, the first disaster recovery portal system can replace its work in time, thereby effectively improving the robustness of the working performance of the portal system. By configuring the second disaster recovery portal system based on the second portal system, where the second disaster recovery portal system mounts the second disaster recovery service system corresponding to the second service system, the second disaster recovery portal system includes: a second disaster recovery middleware application and a second disaster recovery database. A data reading link is configured between the second disaster recovery middleware application and the second disaster recovery database, a data writing link is configured between the second disaster recovery middleware application and the second database, and a data replication link is configured between the second disaster recovery database and the second database. Thus, the robustness of the second portal system can be effectively improved.

[0081] Combining the above embodiments, the present disclosure designs a set of portal deployment architectures, which can well meet the requirements of different types of data centers for portal systems and are very easy to expand to more data centers. Among them,

[0082] (1) Portal system architecture

[0083] As Figure 3 shown, Figure 3 is a schematic diagram of the initial portal system deployment structure proposed according to the present disclosure. The portal is layered according to the front end, middleware gateway, middleware application, and database. Business systems A and B are mounted on the portal. The portal can be accessed through a domain name. Configuration information is stored in the database, that is, the location information of business systems A and B mounted on the portal, so as to facilitate accessing business systems A and B through the portal. The database of the portal system is a typical database with more reads than writes. Most of the traffic is requests to read configuration information, and very few traffic is used to write configuration information.

[0084] When you need to expand the deployment to a multi-active architecture, such as Figure 4 As shown, Figure 4 This is a schematic diagram of the multi-active architecture proposed in the present disclosure. In which, computer room 2 deploys another portal system based on computer room 1. The front desk, middle desk and application remain the same as the deployment mode of computer room 1, and the database is deployed as a read-only slave database of the database in computer room 1. The portals of the two computer rooms are mounted with different domain names.

[0085] The database in computer room 2 is read-only (not writable). The read-only slave database copies data from the master database in computer room 1 through a data replication link to keep the data in the two databases consistent.

[0086] The portal of computer room 2 can mount business systems C and D in computer room 2.

[0087] If the portal middle station in computer room 2 performs read-write separation, that is, when reading traffic, access the database of this data center; if writing is required, connect to the main database of portal 1.

[0088] When you need to expand the deployment to a multi-active architecture + disaster recovery architecture, such as Figure 5 As shown, Figure 5 This is a schematic diagram of the multi-active architecture and disaster recovery architecture proposed in the present disclosure. Both computer room 1 and computer room 2 can be expanded into a disaster recovery center. The database of the disaster recovery center is read-only, and the data is replicated read-only by a nearby data center. The disaster recovery center generally has no traffic. When switching disaster recovery, the domain name is replaced. There is a cascaded read-only replication between databases at all levels, refer to data replication link 1, data replication link 2, and data replication link 3 in the figure. The front desks of each center are consistent, and read operations are read from the computer room through the corresponding middle station, and write operations are written to the only master database through the middle station.

[0089] When more equipment rooms need to be expanded, such as Figure 6 As shown, Figure 6 This is the multi-computer room expansion structure proposed in the present disclosure. In which, an additional computer room 3 is added, and the expansion can be carried out in a similar manner as shown in the figure. In which, computer room 2 and computer room 3 can both be regarded as the above-mentioned second portal system.

[0090] Figure 7 It is a structural diagram of an extended deployment device of a portal system in multiple data centers proposed in an embodiment of the present disclosure.

[0091] like Figure 7 As shown, the expansion deployment device 70 of the portal system in multiple data centers includes:

[0092] Determination module 701, configured to determine a first portal system, where the first portal system mounts a first business system, and the first portal system includes: a first middle platform application and a first database, and a data reading and writing link is configured between the first middle platform application and the first database;

[0093] First configuration module 702, configured to configure at least one second portal system based on the first portal system, where the second portal system mounts a second business system, and the second portal system includes: a second middle platform application and a second database, a data reading link is configured between the second middle platform application and the second database, a data writing link is configured between the second middle platform application and the first database, and a data replication link is configured between the second database and a target database, and the target database is the first database or a database that keeps data synchronized with the first database.

[0094] In some embodiments of the present disclosure, as Figure 8 shown, Figure 8 FIG. is a schematic structural diagram of an extended deployment device of a portal class system in multiple data centers proposed in another embodiment of the present disclosure. The device further includes:

[0095] Second configuration module 703, configured to configure a first disaster recovery portal system based on the first portal system, where the first disaster recovery portal system mounts a first disaster recovery business system corresponding to the first business system, and the first disaster recovery portal system includes: a first disaster recovery middle platform application and a first disaster recovery database, a data reading link is configured between the first disaster recovery middle platform application and the first disaster recovery database, a data writing link is configured between the first disaster recovery middle platform application and the first database, and a data replication link is configured between the first disaster recovery database and the first database.

[0096] In some embodiments of the present disclosure, the device further includes:

[0097] Third configuration module 704, configured to configure a second disaster recovery portal system based on the second portal system, where the second disaster recovery portal system mounts a second disaster recovery business system corresponding to the second business system, and the second disaster recovery portal system includes: a second disaster recovery middle platform application and a second disaster recovery database, a data reading link is configured between the second disaster recovery middle platform application and the second disaster recovery database, a data writing link is configured between the second disaster recovery middle platform application and the second database, and a data replication link is configured between the second disaster recovery database and the second database.

[0098] It should be noted that the foregoing explanation of the extended deployment method of the portal class system in multiple data centers also applies to the extended deployment device of the portal class system in multiple data centers in this embodiment, and will not be elaborated here.

[0099] In this embodiment, a first portal system is determined. The first portal system mounts a first business system and includes a first middleware application and a first database. A data read-write link is configured between the first middleware application and the first database. At least one second portal system is configured based on the first portal system. The second portal system mounts a second business system and includes a second middleware application and a second database. A data read link is configured between the second middleware application and the second database, a data write link is configured between the second middleware application and the first database, and a data replication link is configured between the second database and a target database, where the target database is the first database or a database that is synchronized with the first database in data. Thus, the requirements of different types of data centers for the portal system can be met, and the expansion and deployment effect of the portal system in multiple data centers can be effectively improved.

[0100] Figure 9 A block diagram of an exemplary computer device suitable for implementing the embodiments of the present disclosure is shown. Figure 9 The shown computer device 12 is merely an example and should not impose any limitation on the functions and usage scope of the embodiments of the present disclosure.

[0101] As Figure 9 shown, the computer device 12 is presented in the form of a general-purpose computing device. The components of the computer device 12 may include, but are not limited to, one or more processors or processing units 16, a system memory 28, and a bus 18 connecting different system components (including the system memory 28 and the processing unit 16).

[0102] The bus 18 represents one or more of several types of bus structures, including a memory bus or a memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the multiple bus structures. For example, these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnection (PCI) bus.

[0103] The computer device 12 typically includes a variety of computer system-readable media. These media can be any available media accessible by the computer device 12, including volatile and non-volatile media, removable and non-removable media.

[0104] The memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. The computing device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used for reading and writing on a non-removable, non-volatile magnetic medium ( Figure 9 not shown, typically referred to as a "hard disk drive").

[0105] Although Figure 9 not shown in the figure, a disk drive for reading and writing on a removable non-volatile disk (such as a "floppy disk"), and an optical disk drive for reading and writing on a removable non-volatile optical disk (such as a compact disc read only memory (CD-ROM), a digital versatile disc read only memory (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 through one or more data media interfaces. The memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present disclosure.

[0106] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in the memory 28. Such program modules 42 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Implementations of a network environment may be included in each or some combination of these examples. The program modules 42 generally perform the functions and / or methods in the embodiments described in the present disclosure.

[0107] The computer device 12 can also communicate with one or more external devices 14 (such as a keyboard, a pointing device, a display 24, etc.), and can also communicate with one or more devices that enable a human body to interact with the computer device 12, and / or communicate with any device that enables the computer device 12 to communicate with one or more other computing devices (such as a network card, a modem, etc.). Such communication can be carried out through the input / output (I / O) interface 22. Moreover, the computer device 12 can also communicate with one or more networks (such as a Local Area Network (LAN), a Wide Area Network (WAN), and / or a public network, such as the Internet) through the network adapter 20. As shown in the figure, the network adapter 20 communicates with other modules of the computer device 12 through the bus 18. It should be understood that although not shown in the figure, other hardware and / or software modules can be used in combination with the computer device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0108] The processing unit 16 executes various functional applications and data processing by running the programs stored in the system memory 28, such as implementing the method for the extended deployment of the portal system in multiple data centers mentioned in the foregoing embodiments.

[0109] To implement the foregoing embodiments, the present disclosure also proposes a non-temporary computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, it implements the method for the extended deployment of the portal system in multiple data centers proposed in the foregoing embodiments of the present disclosure.

[0110] To implement the foregoing embodiments, the present disclosure also proposes a computer program product, and when the instructions in the computer program product are executed by a processor, it executes the method for the extended deployment of the portal system in multiple data centers proposed in the foregoing embodiments of the present disclosure.

[0111] Those skilled in the art will readily think of other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the present disclosure, which follow the general principles of the present disclosure and include the common general knowledge or conventional technical means in the technical field not disclosed in the present disclosure. The specification and embodiments are only regarded as exemplary, and the true scope and spirit of the present disclosure are pointed out by the following claims.

[0112] It should be understood that the present disclosure is not limited to the exact structures already described and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present disclosure is only limited by the appended claims.

[0113] It should be noted that in the description of the present disclosure, terms such as "first", "second", etc. are only used for descriptive purposes and cannot be construed as indicating or implying relative importance. In addition, in the description of the present disclosure, unless otherwise specified, the meaning of "a plurality of" is two or more.

[0114] Any process or method description shown in the flowchart or described in other ways herein can be understood to represent a module, segment, or part of code including one or more executable instructions for implementing a specific logical function or process. The scope of the preferred embodiments of the present disclosure includes additional implementations, where the functions may be executed in a substantially simultaneous manner or in a reverse order according to the involved functions, rather than in the order shown or discussed, which should be understood by those skilled in the technical field of the embodiments of the present disclosure.

[0115] It should be understood that each part of the present disclosure can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, any one or a combination of the following well-known technologies in the art can be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application specific integrated circuits having appropriate combinational logic gate circuits, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.

[0116] Those of ordinary skill in the technical field can understand that all or part of the steps carried by the method of the above embodiments can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.

[0117] In addition, each functional unit in various embodiments of the present disclosure can be integrated into one processing module, or each unit can exist physically alone, or two or more units can be integrated into one module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. When the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0118] The above-mentioned storage medium can be a read-only memory, a magnetic disk, an optical disk, etc.

[0119] In the description of this specification, the descriptions referring to terms such as "one embodiment", "some embodiments", "examples", "specific examples", or "some examples" etc. mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0120] Although the embodiments of the present disclosure have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present disclosure. Those of ordinary skill in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present disclosure.

Claims

1. An extended deployment method of a portal system in multiple data centers, characterized in that Including: Determine a first portal system, where the first portal system mounts a first business system. The first portal system includes: a first middleware application and a first database, and a data read-write link is configured between the first middleware application and the first database; Configure at least one second portal system based on the first portal system. The second portal system mounts a second business system. The second portal system includes: a second middleware application and a second database. A data read link is configured between the second middleware application and the second database, a data write link is configured between the second middleware application and the first database, a data replication link is configured between the second database and a target database, and the target database is the first database or a database that keeps data synchronized with the first database.

2. The method according to claim 1, wherein The method further includes: Configure a first disaster recovery portal system based on the first portal system. The first disaster recovery portal system mounts a first disaster recovery business system corresponding to the first business system. The first disaster recovery portal system includes: a first disaster recovery middleware application and a first disaster recovery database. A data read link is configured between the first disaster recovery middleware application and the first disaster recovery database, a data write link is configured between the first disaster recovery middleware application and the first database, and a data replication link is configured between the first disaster recovery database and the first database.

3. The method according to claim 2, wherein The method further includes: Configure a second disaster recovery portal system based on the second portal system. The second disaster recovery portal system mounts a second disaster recovery business system corresponding to the second business system. The second disaster recovery portal system includes: a second disaster recovery middleware application and a second disaster recovery database. A data read link is configured between the second disaster recovery middleware application and the second disaster recovery database, a data write link is configured between the second disaster recovery middleware application and the second database, and a data replication link is configured between the second disaster recovery database and the second database.

4. The method according to claim 1, characterized in that, The target database is determined based on the following method: Mark the first portal system and the portal systems extended and deployed based on the first portal system as deployed portal systems; Determine the data transmission distance between the second portal system and each of the deployed portal systems; Determine the minimum value among at least one of the data transmission distances; Use the database in the deployed portal system corresponding to the minimum value as the target database.

5. An extended deployment device for a portal - type system in multiple data centers, characterized in that, Including: A determination module, configured to determine a first portal system, where the first portal system mounts a first business system. The first portal system includes: a first middleware application and a first database, and a data read-write link is configured between the first middleware application and the first database; A first configuration module, configured to configure at least one second portal system based on the first portal system, wherein the second portal system mounts a second business system, and the second portal system includes: a second middle platform application and a second database, a data reading link is configured between the second middle platform application and the second database, a data writing link is configured between the second middle platform application and the first database, a data replication link is configured between the second database and the target database, and the target database is the first database or a database that keeps data synchronized with the first database.

6. The device according to claim 5, characterized in that The apparatus further includes: A second configuration module, configured to configure a first disaster recovery portal system based on the first portal system, wherein the first disaster recovery portal system mounts a first disaster recovery business system corresponding to the first business system, and the first disaster recovery portal system includes: a first disaster recovery middle platform application and a first disaster recovery database, a data reading link is configured between the first disaster recovery middle platform application and the first disaster recovery database, a data writing link is configured between the first disaster recovery middle platform application and the first database, and a data replication link is configured between the first disaster recovery database and the first database.

7. The device according to claim 6, characterized in that, The apparatus further includes: A third configuration module, configured to configure a second disaster recovery portal system based on the second portal system, wherein the second disaster recovery portal system mounts a second disaster recovery business system corresponding to the second business system, and the second disaster recovery portal system includes: a second disaster recovery middle platform application and a second disaster recovery database, a data reading link is configured between the second disaster recovery middle platform application and the second disaster recovery database, a data writing link is configured between the second disaster recovery middle platform application and the second database, and a data replication link is configured between the second disaster recovery database and the second database.

8. A computer device, characterized in that, Comprising: At least one processor; And A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and when the instructions are executed by the at least one processor, the at least one processor is enabled to execute the method according to any one of claims 1-4.

9. A non-transitory computer-readable storage medium storing computer instructions, characterized in that, Wherein, The computer instructions are used to cause the computer to execute the method according to any one of claims 1-4.

10. A computer program product, characterized in that, Including a computer program, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1-4 are implemented.

Images