KR20030064779A - Systems and Methods for Providing Centralized Management of Heterogeneous Distributed Enterprise Application Integration Objects - Google Patents

Abstract

In the distributed enterprise application integration system, modularized components located on multiple hosts are centrally managed so as to facilitate communication among application programs. Collaboration services traditionally associated with a central server, such as, for example, message queues, message publishers/subscribers, and message processes, are instead distributed to multiple hosts and monitored by a central registry service. This system allow configuration management to be performed in a central location using a top-level approach, while implementation and execution tasks are distributed and delegated to various components that communicate with the applications.

Description

System and Methods for Providing Centralized Management of Heterogeneous Distributed Enterprise Application Integration Objects}

The growth of the software industry has generally become useful for a wide range of applications, and electrical generality has relied heavily on these applications. In addition, it is common in businesses that use multiple tasks within the company for daily activity. Since these tasks are provided by various vendors, coordination to support the business control path is an important task that requires skilled personnel provided by resources used elsewhere. Therefore, it is important for businesses to interconnect their work and share information in a stable and secure manner.

There is a need to integrate their work so that businesses can cooperate and share information, but there are many difficulties in realizing such integration. One common problem with the conventional approach is that new solutions must be used to change or terminate business operations every hour. This approach is costly due to the massive disruption of the business, and may sometimes fail to achieve the purpose of the business and is not a solution for the future.

Another problem with conventional approaches is that manual adjustments to each task are necessary so that the task can be linked to other tasks in the business. In addition, this approach is costly and time consuming. In addition, this approach has the disadvantage of being inflexible when the business is updated, added or transformed.

A further problem with the conventional approach is that the liaison between all the tasks depends on the components that perform central management and processes. This "hub and spoke" model leaves the vulnerability that the entire business can be shut down by one problem, such as a failure of a central component. Moreover, when the central component is overloaded, the central component may suffer from parallelism, and thus the request may not be performed.

Summary of the Invention

In a centrally managed system, modular components located in multiple hosts are centrally managed to facilitate communication between business programs. For example, conventional cooperative services associated with a central server, such as message queues, message issuers / receivers, and message processes, are distributed and monitored by multiple central hosts instead of by central registry services. While management is distributed and delegated to the various components that are in contact with the work, it permits structural management to be carried out centrally using a higher level of access.

In one embodiment, the present invention is a standardizable enterprise business collaboration system capable of managing multiple reusable distributed objects running in heterogeneous business environments. The electrical standardizable enterprise business collaboration system includes a fault tolerant central registry system with a first central registry and a replicated central registry, manages a number of reusable distributed objects, and manages multiple reuse of electricity. Send configuration change alerts to distributed objects, which can provide configuration data to multiple distributed objects from either the first central registry or the replicated central registry, and the replicated central registry when the first central registry is unavailable. It includes a central host using. In addition, the standardizable enterprise business collaboration system includes a number of reusable distributed objects that contact the central host to receive configuration change alerts and download configuration data from the central host system's fault-tolerant central registry system. In addition, the standardizable enterprise business collaboration system includes a number of heterogeneous tasks configured to communicate through a plurality of reusable distributed objects in accordance with configuration data.

A further embodiment of the present invention is a method for centrally managing distributed components and actively executing configuration information related to the distributed components in a distributed enterprise business system. The electrical method includes storing, at a first computer system, a central registry database containing configuration information related to distributed components located in a remote controlled computer system, and receiving a request for configuration information update from the electrical distributed components. Steps. The method also includes determining a configuration change, executing in response to the posting request, and changing the central registry database to reflect at least a portion of the configuration change. Additionally, the electrical method may comprise allocating a configuration change corresponding to the distributed component; And communicating the configuration change to the corresponding distributed component, such that the configuration change is executed on the corresponding component.

Another embodiment of the present invention is a method for centrally managing distributed components and actively executing configuration information related to the distributed components in a distributed enterprise business system. The electrical method includes storing a central registry database in a first computer system, the central registry database comprising configuration information related to distributed components located in a remote controlled computer system, receiving data translations at the first computer system, Transmitting the configuration information accessed and modified by the user and sent to the first computer system. The method also includes determining a configuration information change, executing in response to the electrical message transmission and data configuration information, and changing the central registry database to reflect at least a portion of the configuration change. In addition, the electrical method may include assigning configuration changes corresponding to the distributed components located in the remote control computer system and transferring the configuration change information to the corresponding distributed components so that the configuration information changes are executed on that component. It includes a step.

Another embodiment of the present invention is a method for centrally managing distributed components and actively executing configuration information related to the distributed components in a distributed enterprise business system. The method includes storing a central registry database in the first computer system, the central registry database comprising configuration information related to the first distributed component located in the first computer system and the second distributed component located in the second computer system. Receiving a request for updating configuration information from at least one of the first distributed component or the second distributed component. The method also includes determining a configuration change, executing in response to the posting request, and changing the central registry database to reflect at least a portion of the configuration change. In addition, the electrical method includes assigning a configuration change to at least one of the first distributed component or the second distributed component and the configuration change to at least one of the first distributed component or the second distributed component. Delivering a configuration change, wherein the configuration change is executed on at least one of the first distributed component or the second distributed component.

Another embodiment of the present invention is a distributed enterprise business integration system that is used to centrally manage distributed components and to ensure that configuration data is actively executed on the distributed components. Electrically distributed enterprise business integration systems include a central registry database used to store configuration data for distributed corporate business systems, process configuration update requests for components, process changes for the central registry database, and And transmit the component configuration data to the distributed components of the computer, the central control module stored in the first computer. The electrically distributed enterprise business integration system also includes a corresponding component control module, which is a plurality of distributed components stored on a plurality of computers. The plurality of distributed components is configured to perform transmission activities related to the data in accordance with the component configuration data. In addition, the electrical component control module is configured to execute component configuration data, contact the central control module to receive the component configuration data, and request for component update to be sent to the central registry database.

Another embodiment of the present invention is a distributed multi-platform business integration system. The electrical system includes a central host that includes a central registry system. The electrical system also includes a corresponding control broker and includes a plurality of business hosts configured to contact the central registry system to receive configuration data. In addition, the electrical system includes a plurality of multi-platform tasks that correspond to a plurality of business hosts and are configured to contact through the plurality of business hosts in accordance with configuration data.

Another embodiment of the present invention is a method of integrating distributed tasks. The method includes managing at least a request for configuration change at a first resource and collecting configuration change information from a plurality of resources associated with the request for configuration change. In addition, the electrical method is distributed such that at least the first task is performed in the first regulating system, the second task is performed in the second regulating system, and the electrical first regulating system and the second regulating system are not the same regulating system. Spreading configuration change information associated with a request for a configuration change to a plurality of distributed components that provide a task.

Another embodiment of the present invention is a method for integrating distributed tasks, comprising forwarding a request for data and message related configuration changes from a first host to a central host. The method also includes receiving, at the first host, configuration change information from a central host associated with a request for a configuration change and translating the data and transmitting a configuration change message according to the electrical configuration change information at the first host. Steps.

Another embodiment of the invention is a method of integrating multiple multi-platform tasks located in a distributed network. The method includes providing a plurality of integrated modules that correspond to a plurality of multi-platform tasks and perform data-related and message transfers to enable communication between the plurality of multi-platform tasks. The method also includes providing a central host module that includes a central database of configuration data and manages and distributes the configuration data to multiple integration modules, the instructions including instructions for allowing communication between multiple multi-platform tasks. Include.

Yet another embodiment of the present invention is a method of implementing a business liaison system distributed between a first independent task and a second independent task. The method includes displaying a first set of data sent from a first standalone task to a data translation module, translated into a second set of data, and passed to a second standalone task. The method also includes converting an electrical representation into a set of data translation and command delivery and a first data translation execution module and a second data translation execution module that communicate the set of electrical data translation and command communication with the first independent task. Dispensing to. The first data translation execution module is in communication with the second data translation execution module, in accordance with a set of data translation and command delivery.

Yet another embodiment of the present invention is a distributed business integration system comprising a central host and a plurality of business hosts in communication with a plurality of multi-platform tasks. The electrically distributed work integration system includes a central host means for displaying the accumulated configuration information and a central host means for allocating a part of the accumulated configuration information to the plurality of work hosts. A plurality of business hosts communicate with a number of corresponding multi-platform tasks and execute some of the accumulated information that enables communication between a plurality of corresponding multi-platform tasks.

In order to summarize the invention, all aspects, advantages and novel features of the invention have been described herein. It is understood that not all these advantages are achieved by the specific embodiments of the present invention. Thus, it will be apparent to one of ordinary skill in the art that the present invention achieves one advantage belonging to a group of advantages without the other advantages achieved in the manner described herein.

The systems and methods of the present invention relate to the field of business integration.

1 shows a high level block diagram of one embodiment of a business integration system including a central management system.

2 shows a high level block diagram of one embodiment of a central registry system.

3A shows a screen shot of one embodiment of a central registry GUI.

3B shows a screen shot of one embodiment of a central registry GUI.

3C shows a screen shot of one embodiment of a central registry GUI.

4 shows a high level block diagram of one embodiment of a business connection.

5A shows a high level block diagram of one embodiment of a control broker.

5B shows a high level block diagram of a further embodiment of a control broker.

6 shows a flowchart of one embodiment of a configuration change process.

7 illustrates a flowchart of one embodiment of a configuration update request process.

8 shows a high level block diagram of a further embodiment of a business integration system including a central management system.

9 shows a high level block diagram of a further embodiment of a business integration system including a central management system.

The system and method shown in one embodiment and example of the invention will be described with reference to the drawings. In addition, variations of the systems and methods shown in other embodiments will be described. In the depicted embodiment, electrical systems and methods are used to allow communication between sets of business task programs.

Throughout the drawings, one embodiment will be depicted in the context of a business task program. The present inventors are not limited to the present invention by the type of program discussed, and the type of object may include all programs such as, for example, software modules, business work programs, databases, counting programs, music programs, telephone systems, and the like. Expected to be. However, the drawings and description relate to one embodiment of the present invention, the program being a business work program. Additionally, in other embodiments, systems and methods for centrally managing distributed objects may be implemented as a single module and / or in the form of being associated with analogs and equivalents of other modules. Moreover, the specific implementations described herein are for the purpose of describing the drawings and the invention is not limited thereto. The scope of the invention is defined by the claims.

Now, this feature will be described with reference to the above-mentioned drawings. The drawings and their associated descriptions are provided in the illustrated embodiments of the invention, but the scope of the invention is not limited thereto. Throughout the drawings, reference numerals may be reused to indicate correspondences between the recited parts. In addition, the first digit of each reference number indicates the drawing in which the electrical part is first shown.

In a centrally managed system, distributed components located in multiple hosts are centrally managed to facilitate communication between business programs. For example, conventional cooperative services associated with a central server, such as message queues, message issuers / receivers, and message processes, are distributed and monitored to multiple hosts instead by a central registry service. Such a system permits structural management to be performed centrally using a higher level of access, while the performance and execution of tasks are distributed and delegated to the various components in contact with the task.

To illustrate one embodiment, a user may use a graphical user interface (GUI) tool to generate a graphical representation of a business task indicating how he wishes to communicate with his task. The central management system assigns electrical indications and determines whether distributed components are required for the execution of the tasks that each distributed component should perform as well as the business process. Next, the central management system locates the distributed components and delivers their corresponding task information to them.

In addition, in one embodiment their architecture combines the separate modular components to provide a flexible topology, working together and replacing a single process flow execution. In general, in a central server system, transactions are performed based on first-in-first-out. In practice, however, most business processes require both parallel and serial processes. At times, this process may be necessary when simultaneously performing several heterogeneous tasks that are not located on different machines. The advantage of this embodiment is that the pediatric management system performs processes that require multiple connected parallel executions.

Additionally, in one embodiment, even a single process flow may fail in multiple components, or may be linked to sequences with individual components that perform fine tasks. For example, the chain of events according to the order item is a sequential step of locating goods ordered by the inventory system, receiving orders by the sales department, calculating and issuing bills, and sending the goods from the shipping department. Include as. The advantage of this embodiment is that the planning through the computer code or script record in which the action is performed is guided by the capacity and limitations of the computer language, whereas the technician graphically represents the business process in the order of the activities performed in each department. By presenting, the planning step can be simplified.

In addition, since the process of execution is modularized in graphical form, additional items can be easily integrated through reconfiguration of the modules. For example, in a series of activities after receiving an order, if a credit check is required after placing the ordered item in inventory, a module for credit check may be added graphically in the appropriate order. The electrical system engineer does not have to write any new code.

In addition, one embodiment may reuse the component. Once the process is modular, it can be used for later integration into other systems. For example, in a single transaction that requires two message translations, the input business message format may be translated into a database format, or from a database format to a subcontracting business format. The two message translations may be written as two separate series of components. Once developed, the first component, named input message translation, does not require a different outgoing format and may be reused for another implementation with the same input elements. The advantage of this embodiment is that the electrical integration process may be streamlined and customized in a way that many components are reused or combined.

The central management system may also change the distributed components. The electrical change may include updating the maintained configuration information by the electrical central management system keeping track of the components. Because changes in business process activity occur daily, if electrical changes occur at various locations, performance changes for distributed systems may be adapted tasks. By providing a central configuration registry, the integration engineer may manage and configure a myriad of components in a single location. An advantage of this embodiment is that the technician may distribute or warn of changes in the components in a single action for all affected components.

In addition, one embodiment supports heterogeneous work environments that require cooperation. A typical enterprise deploys a variety of computer technologies and systems hosted on different platforms to support their business needs. Sometimes, these systems require sharing of information, but do not require an integrated way to do so. The electrical central management system may provide a module to configure an interface with such disparate tasks. It also provides flexibility to the electrical system, providing other modules that contain business processes that occur between tasks. The advantage of this embodiment is that, on a corporate coordination basis, a central management system naturally transforms information and data.

In one embodiment, the central management system can measure and support the growth of the enterprise. Modular components may be added to the network supporting additional computer systems, and modular components may be strategically added to perform transactions quickly, as the data required increases as the business grows. The advantage of this embodiment is that once installed, the central management system is not reinstalled to adapt to the growth of the business.

In one embodiment the central management system is fault tolerant. Registry services may be separated from run-time collaboration services. If an electrical registry machine fails during operation, components that do not run on the same machine may continue to carry out the transaction process as required by business operations. In addition, since the electrical modules are distributed and run independently, if one component ceases operation, the other components in the central management system may not be affected. In addition, the electrical central registry system may be configured to route tasks to components that operate on failed components.

Another advantage of this embodiment is that updates and immobilizations to the central management system may be performed without distributing the entire system. For example, the central management system may suspend the execution of one message queue to perform updates without affecting other components and without causing the entire business to stop. Thus, the central management system maintains operation even when each component is stopped.

1 illustrates an embodiment of a business integration system in which central management system 110 facilitates communication between task A 120 and task B 130 via contact medium 140. The central management system 110 includes a central registry system 112, business interface A 114, and business interface B 116, which is executed on the first computer 150, and has a business interface. A 114 communicates with task A 120 running on second computer 160, and business interface B 116 communicates with task B 130 running on third computer 170.

In one embodiment, task A 120 and task B 130 are, for example, legacy tasks, databases, enterprise resource planning ("ERP") tasks (eg, SAP R / 3), object request brokers. (&Quot; ORBs ") (e.g., ORBIX of IONA Technology), internet work, electrical data exchange ("EDI") network work (e.g. SAP EDI), and the like.

In the embodiment shown in FIG. 1, central registry system 112, business interface A 114, and business interface B 116 are implemented as if separating components connected via contact medium 140. In other embodiments, central registry system 112 and business interface A 114 may be implemented as part of a single component or central registry system 112 and business interface B 116 may be implemented as part of a single component. have. Additionally, while task interface A 114 is shown as being performed as part of task A, in other embodiments, task interface A 114 and task A 120 are task interface B 116 and task B 130. May be implemented as if the components are separated as similarly recognized.

Additionally, although FIG. 1 illustrates two tasks and two task interfaces, more than one task and / or two or more task interfaces are included.

In one embodiment, central management system 110 includes central registry system 112. The central registry system 112 may control the storage and active distribution of system configuration information, system processes, monitoring access control, optional balance and selective delivery of data. For example, data may be selectively delivered to various receptors through various distribution channels (eg, via email, mail, fax) to provide alert notifications (eg, alerts, high priority alerts, emergency). . In one embodiment, the central registry system 112 may alert various components, such as when applying cargo balancing techniques, which, for example, reduce overall queue time and improve data transit time. Subscriber pooling can also be used. As noted above, in one embodiment, the central registry system 112 resides in its own computer device, and in other embodiments, the central registry system 112 belongs to one or more tasks.

The electrical computer device may be a device or a device capable of performing a task that allows a user to interact with the central registry system 112. In one embodiment, the electrical computer device is, for example, a Pentium processor, a Pentium II processor, a Pentium Pro processor, a Pentium III processor, an Adena processor, an xx86 processor, an 8051 processor, a RISC processor, a MIPS processor, a power PC processor or an alpha processor. A conventional computer using one or more microprocessors such as In one embodiment, the electrical computer device is, for example, Microsoft Windows 2000, Microsoft Windows 3.X, Microsoft Windows 98, Microsoft Windows NT, Microsoft Windows CE, Palm Pilot OS, Apple MacOS , Disk Operating System (DOS), IBM OS / 2 , IBM RX / 6000 AIX , Hewlett-Packard HP-UX , UNIX, Linux , SunOS Or Solaris OS Operate appropriate operating systems such as operating systems. In one embodiment, the electrical computer device is, for example, a conventional modem such as Ethernet (IEEE 802.3), Token Ring (IEEE 802.5), Fiber Distributed Datalink Interface (FDDI). Or network connection. Typically, in one embodiment, the electrical operating system includes a TCP / IP stack that regulates all input and output message traffic past the contact medium 140.

In another embodiment, a computer device may be, for example, a workstation capable of interacting using a contact medium, a local network of individual computers, an interactive television, an interactive kiosk, a portable digital assist, an interactive wireless communications device, It may be a portable computer, a telephone, a router, a satellite, a smart card, an inserted computer device, or an equivalent thereof. In each system, the operating systems will be different and they establish contact with the contact medium 140 by providing the appropriate contact protocol as needed.

2 illustrates a central registry system 112 that includes a GUI module 210, a registry process 220, and a registry database 230.

In one embodiment, the central registry system 112 includes a GUI module 210. The electrical GUI module 210 allows a user to interact with the central management system 110 to perform tasks such as, for example, input configuration information, time setting information, input data translation information, information representing business process flow, and the like. Do it. GUI module 210 may include, for example, business process modeling tools, business process rule generation tools, system monitoring tools, registry database tools, as well as other interface tools. In one embodiment, a user uses the business process modeling tool of the GUI module 210 to generate a graphical representation of a business process that indicates how he can contact his work. In addition, the user can use the business process rule generator to set rules and functions for how electrical tasks can be contacted.

The GUI module 210 may also be executed as a software program using text, graphics, audio, video or other types of media to represent and interact with the data. GUI module 210 may include any point addressable display, such as a cathode-ray tube (CTR), a liquid crystal display (LCD), a plasma display, or any other type and / or combination of displays; For example, input devices such as a mouse, trackball, touch screen, pen, keyboard, voice recognition module; And a combination of software having a suitable interface for the user to access data using, for example, stylized screen components such as menus, windows, toolbars, controllers (e.g., radio buttons, check boxes, sliding scales, etc.). May be

While the central management system 110 includes a GUI module 210, in other embodiments, other modules may have the GUI module 210 or may be used for connection independently. For example, central management system 110 may interact with a user by setting text-based entries of information as well as input of data.

As used herein, a word module, whether or not composed of upper or lower characters, refers to the collection of software instructions with breakdown points and descriptions written in hardware or firmware embedded in logic or programming languages such as C ++, for example. do. Software modules may be linked to compiled and executable programs, installed in active link libraries, or may be described in an interpreted language such as BASIC. It is appreciated that a software module may be called from another module or itself and / or may cause a reaction to detect or inhibit an event. Software instructions may be embedded in firmware, such as EPROM. In addition, it is appreciated that the hardware module may include connected logic units such as gates and flip-flops, and / or may include programmable units such as gate arrays or processors that may be programmed.

In one embodiment, central registry system 112 includes a collection of registry processes 220. The electrical registry process 220 performs various tasks for the central registry system 112, such as, for example, processing requests for configuration updates, modifying the contents of the registry database, and delivering updates to the appropriate components. In one embodiment, registry process 220 is executed as a multi-threaded program, where one or more registry processes may be executed concurrently, and a copy of a single process may also be executed. Additional information about the registry process 220 is described below.

In one embodiment, central registry system 112 includes registry database 230. The electrical registry database 230 stores the cryptic configuration of the system. Such information may include information about participating hosts, users, control brokers, monitors, modules, business interfaces, business queues, event formats, rules, processes, as well as other system components.

In one embodiment, the participating host information may include a host name, network name or IP address, network domain name, control broker name, and the like. In addition, the business interface information may include an IQ name, service, action, submission module, event format, schedule deletion, administrator name, and the like. Module information may include module name, participating host, control broker, module format, file name, configuration file name, variables for various commands, and the like. In addition, the module information includes user information, whether the electrical module is started automatically, whether automatic restart is possible, start schedule, shutdown schedule, log level, debug beacon, log file availability, IQ manager, TCP / IP port. And the like. While the above embodiments provide one embodiment of the information stored in the central registry, other embodiments indicate that an additional or subset of the above information may be included in the central registry.

In one embodiment, registry database 230 may be accessed via registry database tools in GUI module 210. Features of each component may be displayed as if the user selects the component through a menu. Sample screen shots of one embodiment of a registry database tool are shown in FIGS. 3A, 3B and 3C. In the left window of FIG. 3A, a group of various components is indicated as allowing the user to select a component. These choices may be in individual formats such as control brokers, interface queues, participating hosts, interface modules, and so forth. In one embodiment, the administrator may display all components with a choice of all options. In FIG. 3B, the participating host information is displayed in tabular form. In FIG. 3C, interface information is also displayed in tabular form. Although the registry database module of an embodiment displays information in the form of a table, other formats and other tools may be used in other embodiments.

In addition, in other embodiments, the central registry information may be accessed using a command line-environment in addition to or in place of the GUI module 210 described above.

In one embodiment, registry database 230 is executed in the form of a flat file. In other embodiments, the registry database 230 may be Sybase, Oracle, or Microsoft. SQL Server (Microsoft SQL Server), Times10, as well as other related databases (such as object-oriented databases) can also be used. Moreover, although the registry database 230 depicted in FIG. 2 includes a single database, in other embodiments, the registry database 230 may be a combination of database, tabular format, or database well known in the art, such as linked lists, binary trees, or the like. It can also run as a database database structure.

Although FIG. 1 illustrates a central management system 110 that includes a central registry system 112, in other embodiments, it may include multiple instances of central registry information.

In one embodiment, the central registry system 112 is executed in a hierarchical manner and may include a master registry and a multiple sub-registry. The change is sent to the master registry in such a way that the master registry conveys the appropriate information corresponding to the sub registry. This embodiment allows the central management system 110 to continue to run even if the master registry exists as a copy of the configuration information in the master registry distributed to the lower registry. Known techniques are used to drive data integration between the master registry and the composite sub-registry.

In another embodiment, the central registry system 112 may run in a non-ranked fashion and may include multiple replicated registries. Changes may be sent to the designed registry, and the designed registry may propagate the changes to another registry, or the changes may be propagated to all the registries in which each registry is known to transmit changes to the other registry. Known techniques are used to drive data integration between replicated registries.

In one embodiment, central management system 110 includes a collection of business interfaces. The business interface facilitates communication between the business and other tasks in the business integration system, as well as the communication between the business and the central registry system 112. In one embodiment, the task interface may vary for each task in the task integration system, or may include different components depending on how the user wishes to communicate with the task.

4 illustrates one embodiment of an interface configured to communicate task A 120 and task interface B 116. Business interface A 114 includes two interface modules 420, an interface queue 430, as well as a control broker 410 in communication with the central registry system 112. In operation, a component such as interface queue 430 sends an update request to control broker 410, which forwards the request to central registry system 112. The central registry system 112 may send appropriate update information to the control broker 410 or may contact the component directly.

In one embodiment, the business interface includes a control broker 410. The electrical control broker 410 maintains local configuration information for their corresponding tasks. For example, control broker 410 processes configuration changes and configuration change requests, facilitates communication between central registry system 112 and components, tracks the status of components, manages component alerts, Perform local maintenance events, other basic maintenance and managerial actions. For example, the control broker 410 may be in contact with the central registry system 112, for example, by performing, requesting or responding to an update when a change occurs in the central registry system 112 and the central monitor system. Allows local configuration to work with central registry system 112. In addition, the control broker 410 may be in contact with a chick monitor system that allows monitoring of distributed components. A detailed description of one embodiment of an electrical central monitor system is disclosed in US patent application Ser. No. 60 / 192,523, "System and Method for Analyzing Business Processes," filed March 28, 2000, which is incorporated herein by reference. It is. In one embodiment, the control broker 410 communicates with the central registry system 112 via TCP / IP communication. However, other contact media may be used.

In one embodiment, each control broker 410 is associated with a control broker 410 belonging to a single task and an electrical task. For example, the control broker 410 depicted in FIG. 4 is associated with task A 120 and belongs to task A. FIG. In other embodiments, control broker 410 may be associated with one or more tasks, belong to the associated task, or control broker 410 may belong to an independent device.

5A illustrates one embodiment of a control broker 410. The electrical control broker 410 includes a status file database 510, an alarm rule database 520, a notification queue 530, a configuration change process 540, a monitor process 550, a status process 560, and an information process 570. ). In addition, the electrical control broker 410 is in contact with a central registry system, a central monitor system, and / or various components (eg, business interfaces, work queues, etc.).

The electrical status file database 510 includes information about the status of components. As the component is updated, the control broker 410 may update the corresponding file of the component, causing the file to affect the current status of the component. In one embodiment, the status file database 510 is updated over time (eg, hourly, daily, weekly, etc.) so that the status file database 510 reflects the status of components at the last update time. In addition, in other embodiments, the status file database 510 may be located outside of the control broker 410, as shown in FIG. 5B.

The electrical alarm rule database 520 includes information about the actions that the control broker 410 may receive when an alarm is received. The rules database may include basic rules, user defined rules, notified parties, notification methods, and the like. For example, when the work queue is completely terminated, the work rule may be confirmed by a system manager by the pager, a design manager by e-mail, and a nearby work queue by instructions using the monitor process 550 below. In another embodiment, the alert rule database 520 may be located outside of the control broker 410 as shown in FIG. 5B.

The electrical notification queue 530 includes messages about alerts that occur and / or information about components for the individual and / or components that acknowledge the alert. In one embodiment, the notification queue 530 is located in the control broker 410, but in another embodiment, to store an alert message when the control broker 410 terminates in an emergency as shown in FIG. 5B. It may be located outside the control broker 410.

While FIG. 5B illustrates a status file database 510, an alert rule database 520, and a notification queue 530 that reside outside of the control broker 410, in other embodiments, one or two components control. It may be located outside the broker 410.

In one embodiment, the notification queue 530, alert rule database 520 and status file database 510 run as a flat file database. In other embodiments, the notification queue 530, alert rule database 520, and status file database 510 may be performed using other data structures, such as databases, link lists, queues, and the like known to those skilled in the art. In addition, the notification queue 530, alert rule database 520 and status file database 510 may be implemented as separate modules using different and / or identical data structures.

The electrical control broker 410 process may be executed at the same time or at the same time as other processes. As discussed above, the control broker 410 processor includes a configuration change process 540, a monitor process 550, a status process 560, and an information process 570.

The electrical control broker 410 may also receive and transmit configuration information for the various components to and from the round-trip central registry, including the configuration change process 540. Once the control broker 410 is started, the configuration change process 540 may request the central registry system and receive their configuration information. In addition, the configuration change process 540 may maintain a connection between the control broker 410 and the central registry for a period of time to monitor whether the electrical central registry has a configuration change of the component. In one embodiment, the configuration change process 540 contacts the central registry for a period of time, for example, every minute, every hour, every 12 hours, every day, and the like. However, in other embodiments, the configuration change process 540 may receive a message from the central registry when the configuration of the component is changed in the central registry. In addition, when the workload is less than or equal to the minimum amount, the configuration change process 540 may be connected to the control broker 410 of the central registry. In addition, the above-described elements may be used in combination. After the configuration change process 540 recognizes that the central registry has a configuration change for at least one of the components, the configuration change process 540 contacts the component to instruct an electrical component and contacts the central registry. To retrieve the configuration change. In other embodiments, configuration change process 540 retrieves configuration changes and passes them to the appropriate components.

The control broker 410 may also include a monitor process 550 that provides information for monitoring the system and / or passes commands to various components. Such instructions may include, for example, determination of component version numbers, start / end instructions, and the like, and may be communicated to components via control broker 410. In addition, the component may send a response or response from the control broker 410, such as, for example, the component's version number, a marker for the down connection, a marker for the failure situation, and the like.

The control broker 410 may include a status process 560 for receiving status information for the component from the status file database 510 and for storing the status information. In other embodiments, the status information may be passed to the status file database 510 or other component located outside of the control broker 410. In addition, the status process 560 may communicate status information to the central registry system and / or the central monitor system.

The control broker 410 may also include an information process 570 that alerts the system about possible volatile conditions, such as a work queue or maximum capacity that has stopped responding or a work queue. If the situation occurs, the component alerts the control broker 410. The electrical alert is processed by information process 570. The electrical information process 570 retrieves the command from the alarm rules database 520 to determine how to handle the alarm. As noted above, the alert rules database 520 includes a specified specification of the collection of rules, business logic, or methods of handling various alerts, notifiers and / or alerts. After the information process 570 determines how to handle the alert, the information process 570 may forward the alert to the appropriate party, central registry system, central monitor system, and / or notification queue 530. The information process 570 then waits for the alert to be resolved.

Alarms may be manually resolved through the central monitor system by a system administrator or alarm resolution process. If the electrical alert is properly resolved, the system administrator will display the resolved component and the information process 570 will receive the new status of the alert from the central monitor system. Information process 570 may then update the status of the alert in notification queue 530. If the electric alert is not properly resolved, the information process 570 sends a message to the notification queue 530, the central registry system and / or the central monitor system to inquire about the unresolved status.

In one embodiment, the business interface includes an interface module 420. The interface module 420 establishes a connection point between the task and the central management component. Accordingly, the interface module 420 can interact with various different tasks and different types of tasks using appropriate protocols. The interface module 420 may include, for example, rules that respond to acknowledgments, rules for generating acknowledgments, retransmission criteria, reconnection criteria, timeout logic, data analysis, data reformatting, buffer sizes, retrieval schedules, transmission schedules, and errors. In addition to managing, you can also manage fine communication in a variety of tasks, such as other fine communication.

In one embodiment, the central management system 110 includes a standard interface module 420 configured to communicate with standard tasks, a custom interface module 420 configured to communicate with non-standard tasks, and a modified standard interface module 420. A variety of internal interface modules 420 configured to communicate with other components, such as another interface module 420, interface queue 430, etc., as well as a modified standard interface module 420 configured to be in communication with other devices. The interface module 420 is used.

In one embodiment, the business interface includes an interface queue 430. The interface queue 430 provides reliable interprocess communication between business interfaces. Information may be transferred from one task to another through the business interface network and the interface queue 430, where the user views and translates the information. How to format, transfer; When the information is processed; When information is transmitted; Access to information; Related rules can also be created. Interface queue 430 ensures that information is delivered in a timely and secure manner, in order to queue various messages. In addition, interface queue 430 may help to provide message recovery after a system crash.

The interface queue 430 of an embodiment may be executed in accordance with a data storage component or may be executed using a standard database such as, for example, Sybase, Oracle, MQ, or the like. See US Patent Application No. 60 / 162,927, "System and Method of Cue With Information Processing Function," filed November 1, 1999, which is incorporated herein by reference, for a detailed description of the selective implementation of an electrical interface queue. In addition, a detailed description of one embodiment of an interface queue is disclosed in the recently filed specification, internal reference SOFTECP.013A, "System and Method of Queues with Message Delivery Function," which is incorporated herein by reference.

In one embodiment, central management system 110 includes contact medium 140. The contact medium 140 is provided for communication between the business interface and the central registry system 112. In one embodiment, the contact medium 140 is implemented as an internet protocol network that implements Transmission Control Protocol / Internet Protocol (TCP / IP), and is a hub that is connected to one or more other routing hubs over a high speed contact link. Specifies the path of the message that is routed to.

However, contact medium 140 may be comprised of one or more interactive media. For example, the communication medium may be an Ethernet network, an interactive television network, a telephone network, a wireless data transmission system, a two-way cable system, a custom-made computer network, an interactive kiosk network, an internet satellite transmission, an automatic conversation machine network, and / or the like. It may also contain water. In addition, in one embodiment, the communication medium 140 may include direct connections between the various components.

In one embodiment, central registry system 112 includes a collection of registry processes 220. The registry process 220 is for the central registry system 112, such as, for example, processing of requests for configuration updates, processes of changes in the contents of the registry database 230, and delivery of updates to appropriate components. Perform various tasks. In one embodiment, the registry process 220 includes a distribution configuration change process and a configuration update request process as well as other processes.

6 illustrates one embodiment of a distribution configuration change process wherein a user, such as an administrator, performs configuration changes via the GUI module 210. Configuration changes may, for example, modify the business process model implemented in the business interface system or change the way messages are sent from one task to another.

At the start in the starting status (block 610), the configuration change process receives a change of the user (block 620). Next, the configuration change process records the changes in registry database 230 (block 630) and notifies the appropriate control broker 410 that there is a configuration change to be executed (block 640). The control broker 410 notifies the notification. By changing the applicable tasks and components, the appropriate object contacts the central registry system 112 to retrieve the update (block 650). Finally, the update is retrieved by the task or component (block 680).

6 illustrates one embodiment of a distribution configuration process change, and the configuration change process may be implemented in different ways. For example, central registry system 112 may be in direct contact with the object and may send appropriate changes to the object. In another embodiment, the central registry system 112 may send the change to the appropriate control broker 410 so that the control broker 410 may send the change to the appropriate object.

7 illustrates one embodiment of a configuration update request, where a task requests a configuration change update. Also, in one embodiment, other components such as interface module 420, interface queue 430, control broker 410, and so forth may request configuration updates.

At the start at the starting status (block 710), the central registry system 112 receives a contact from the control broker 410 corresponding to the business update request (block 720). Next, if it can transmit to the task (block 730), the configuration update request process asks the central registry system 112 to determine update information. Next, the control broker 410 notifies the task that the configuration update request contacted the central registry system 112 (block 750) to trigger the task (block 740). Finally, the update is retrieved by task (block 760).

7 illustrates one embodiment of a configuration update request process, and the configuration update request process may be executed in different ways. For example, the object contacts the central registry system 112 and sends the update request directly. In another embodiment, the central registry system 112 may send the update to the appropriate control broker 410 in such a way that the control broker 410 sends the update to the appropriate object. In further embodiments, the central registry system 112 may automatically update the object without waiting for an update request.

The present invention may be applied to various tasks. For example, as shown in the business integration system shown in FIG. 8, the central management system 110 may be used in connection with a supply business, an inventory business, and a banking business. For example, the central management system 110 may be configured to receive an initial purchase request from a supply business, review the inventory if partially available, and calculate an appropriate quantity from the quantity of the consumer through banking.

The central management system 110 shown in FIG. 8 is executed in such a way that the central registry system 112 is located on its computer, the supplier / stock interface interfaces with the supplier business and the refurbishment, and where they are together. . The supplier service communicates with inventory through the supplier / stock interface, and the supplier service and inventory communicates with the bank through the banking interface.

Moreover, banking interfaces include interface queues that are performed using Sybase, while provider / inventory interfaces contain interface queues that are executed using Oracle and Sybase. In addition, the supplier service carried out is in contact with the Siebel service and the Siebel interface module, and the inventory service is the Sybase service in contact with the Siebel interface module.

Tasks, interface modules, and interface queues may be executed using various products, and embodiments illustrate, but are not limited to, the flexibility and standardization possibilities of central management system 110. In other embodiments, the tasks may be performed using a variety of systems, such as, for example, heritage services, databases, ERP tasks, ORBs, Internet tasks, EDI network tasks, and the like.

The user changes to configure the work integration system using the GUI module 210, and inputs the configuration change. For example, a user may want to change the rules for converting supply records into inventory records. Table 1 shows sample supply records and Table 2 shows sample inventory records.

Part number. number Last name text First name text Quantity number price money

Part number. text Name text number number cost money

In one embodiment, the user may want to change the configuration of the system to use only the last name of the supply record, such as the name of the inventory record, and to have the name field of the inventory record including the first name and last name of the supply record. have. Accordingly, the user may use the GUI module 210 to input the configuration change such that the name field of the inventory record = the first name field of the supply record + the last name field of the supply record.

After the user inputs the configuration change, the central registry system 112 receives the configuration change and stores the configuration change in the registry database 230. Next, central registry system 112 uses a registry process to determine which components require configuration changes. In an embodiment, the supplier / stock interface receives configuration changes and executes the rules for inventory configuration, thus, the central registry system 112 contacts the control broker with the supplier / stock interface and controls the modification. Notify broker 410. The control broker then identifies the appropriate interface module with the configuration change, and the appropriate interface module contacts the central registry system 112 to receive the change.

9 illustrates an additional implementation of a business integration environment that includes a loading host 950 and an external organization designated as a consumer order registration system 910, a bank 920, and a supplier 930 that communicate through an order registration host 940. In the sun, each external organ and host run on a different computer.

In the embodiment shown, the consumer may transfer the order from the consumer order registration system 910 to the order registration host 940. Information about the electrical order, for example, part number, catalog number, article description, and the like is received by the consumer order registration system interface module 941 and registered in the interface queue 942. The consumer may then instruct his bank 920 to send the cost for the order. The payment information is received by the bank interface module 943 and registered in the interface queue 944. The internal interface module 944 for the order registration host then consults the intelligent queues 942 and 944 to confirm that the order and the required costs have been received.

Assuming there is an order with the required cost, an event is sent to one of the loading host 950 and the interface queue 951. Internal interface module 952 for the loading host queries interface queue 951 for receipt of orders and processing of information. Next, the internal interface module 952 queries the loading task 960 via the interface queue 953 and the loading interface module 954 and determines whether the ordered item has been loaded. Once the electrical article has been loaded, the internal interface module 952 commands the loading module 970 via the interface queue 955 and the loading interface module 956 to send the article. If the electrical article is not loaded or the quantity is particularly low, the internal interface module 952 may accept the purchase request from the supplier 930 via the interface queue 957 and the supplier interface module 958.

In one embodiment, the central registry system 980 connects the control broker 946 of the order registration host and the control broker 959 of the loading host to centrally manage the order registration host 940 and the loading host 950. do.

9 illustrates one embodiment of a business interface system, and in other embodiments, other systems may be added or used. Further, for example, the system shown in FIG. 9 includes a financial host, a receiving host, a manufacturing host, and / or a technical host. Various embodiments of the present invention may be used, and the embodiments provided above are merely means for illustrating various uses of the present invention, and the present invention is not limited thereto.

While various embodiments of the invention have been disclosed, these examples are solely for the purpose of illustrating the invention in more detail, and the scope of the invention is not limited by these examples in accordance with the spirit of the invention. It will be self-evident for those of ordinary knowledge.

Claims (45)

Includes a fault tolerant central registry system with a primary central registry and a replicated central registry, manages multiple reusable distributed objects, and changes configuration to multiple reusable distributed objects A central host for sending alerts, providing configuration data to a plurality of distributed objects from one of the first central registry and the duplicated central registry, and using the replicated central registry when the first central registry is not available; A plurality of reusable distributed objects in contact with the central host to receive configuration change alerts and to download configuration data from the central host system's fault-tolerant central registry system; And, Includes a number of heterogeneous tasks configured to communicate through a number of reusable distributed objects in accordance with configuration data, Standardizable enterprise collaboration system for managing multiple reusable distributed objects running in heterogeneous business environments. Storing, at the first computer system, a central registry database containing configuration information related to distributed components located in the remotely controlled computer system; Receiving a request for updating configuration information from an electrically distributed component; Determining a configuration change and executing in response to the electrical request; Altering the central registry database to reflect at least some of the configuration changes; Assigning a configuration change corresponding to the distributed component; And, Delivering the configuration change to the corresponding distributed component, wherein the configuration change is executed on the corresponding component, In a distributed enterprise business system, centrally manage distributed components and actively execute configuration information related to the distributed components. The method of claim 2, The electrical configuration information includes at least one of load balancing, data mapping, data translation, routing, formatting, scheduling, collaboration, and message checking. Way. The method of claim 2, Electrical configuration information includes at least load balancing, data mapping, data translation, routing, formatting, scheduling, collaboration, and message checking. Way. The method of claim 2, The electrical central registry database contacts a plurality of sub-registry databases, and the electrical multiple sub-registry databases communicate with distributed components. Way. The method of claim 2, The electrical configuration information includes data translation and message confirmation. Way. The method of claim 2, The electrical configuration information includes a component and business logic connection information. Way. The method of claim 2, The electrical central registry database contacts a plurality of replication registry databases, and the electrical multiple registry registry database contacts a distributed component. Way. Storing a central registry database in the first computer system, the central registry database comprising configuration information associated with distributed components located in a remote controlled computer system; Receiving a data translation at a first computer system, and transmitting configuration information accessed and modified by a user in a configuration information input module and sent to the first computer system; Determining a configuration information change and executing in response to an electrical message transmission and data configuration information; Altering the central registry database to reflect at least some of the configuration changes; Assigning a configuration change corresponding to the distributed component located in the remote control computer system; And, Passing configuration change information to the corresponding distributed component, whereby the configuration change is executed on that component, In a distributed enterprise business system, centrally manage distributed components and actively execute configuration information related to the distributed components. The method of claim 9, The electrical configuration information includes at least one of load balancing, data mapping, data translation, routing, formatting, scheduling, collaboration, and message checking. Way. The method of claim 9, Electrical configuration information includes at least load balancing, data mapping, data translation, routing, formatting, scheduling, collaboration, and message checking. Way. The method of claim 9, The electrical configuration information includes data translation and message confirmation. Way. The method of claim 9, The electrical configuration information includes a component and business logic connection information. Way. The method of claim 9, The electrical central registry database contacts a plurality of sub-registry databases, and the electrical multiple sub-registry databases communicate with distributed components. Way. The method of claim 9, The electrical central registry database contacts a plurality of replication registry databases, and the electrical multiple registry registry database contacts a distributed component. Way. Storing a central registry database in the first computer system, the central registry database comprising configuration information related to the first distributed component located in the first computer system and the second distributed component located in the second computer system; Receiving a request for updating configuration information from at least one of the first distributed component or the second distributed component; Determining a configuration change and executing in response to the electrical request; Altering the central registry database to reflect at least some of the configuration changes; Assigning a configuration change to at least one of the first first distributed component or the second distributed component; And, Delivering the configuration change to at least one of the electrical first distributed component or the second distributed component, such that the configuration change is executed on at least one of the electrical first distributed component or the second distributed component. doing, In a distributed enterprise business system, centrally manage distributed components and actively execute configuration information related to the distributed components. The method of claim 16, The electrical configuration information includes at least one of load balancing, data mapping, data translation, routing, formatting, scheduling, collaboration, and message checking. Way. The method of claim 16, Electrical configuration information includes at least load balancing, data mapping, data translation, routing, formatting, scheduling, collaboration, and message checking. Way. The method of claim 16, The electrical configuration information includes data translation and message confirmation. Way. The method of claim 16, The electrical configuration information includes a component and business logic connection information. Way. The method of claim 16, The first central registry database is in contact with the first and second dependent registry databases, the first first registry database is in contact with the first distributed component, and the second second registry database is in the second distribution database. Characterized by being in contact with the component Way. The method of claim 16, The first central registry database contacts the first and second redundant registry databases, the first primary registry database contacts the first distributed component, and the second second registry database contacts the second distributed registry database. Characterized by being in contact with the component Way. Includes a central registry database used to store configuration data for distributed enterprise business systems, processes configuration update requests for components, processes changes for the central registry database, and provides components for multiple distributed components. A central control module configured to transmit configuration data, the central control module stored in a first computer; And, A corresponding component control module, configured to perform transmission activities associated with the data in accordance with the component configuration data, wherein the electrical component control module executes the component configuration data and contacts the central control module to perform component configuration data. A plurality of distributed components stored on a plurality of computers, the plurality of computers being configured to Distributed enterprise business integration system used to centrally manage distributed components and to ensure that configuration data is actively executed on distributed components. The method of claim 23, wherein The electrical configuration information includes at least one of load balancing, data mapping, data translation, routing, formatting, scheduling, collaboration, and message checking. Distributed Business Integration System. The method of claim 23, wherein Electrical configuration information includes at least load balancing, data mapping, data translation, routing, formatting, scheduling, collaboration, and message confirmation. Distributed Business Integration System. The method of claim 23, wherein The electrical central registry database contacts a plurality of sub-registry databases, and the electrical multiple sub-registry databases communicate with distributed components. Distributed Business Integration System. The method of claim 23, wherein The electrical central registry database contacts a plurality of redundant registry databases, and the electrical multiple redundant registry databases contact a distributed component. Distributed Business Integration System. A central host containing a central registry system; A plurality of business hosts, including a corresponding control broker, configured to communicate with the central registry system to receive configuration data; A distributed multi-platform business integration system, comprising a plurality of multi-platform tasks corresponding to a plurality of business hosts and configured to communicate through the plurality of business hosts in accordance with configuration data. The method of claim 28, And further comprising a plurality of task connectors to facilitate communication between the plurality of task hosts and the corresponding plurality of multi-platform tasks. Distributed multi-platform business integration system. The method of claim 28, The electrical central registry system is in contact with a plurality of sub registries, and the electrical plurality of sub registries is in contact with a plurality of business hosts. Distributed multi-platform business integration system. The method of claim 28, The electrical central registry system is in contact with a plurality of redundant registries, and a plurality of electrical redundant registries are in contact with a plurality of business hosts. Distributed multi-platform business integration system. The method of claim 28, The electrical central registry system comprises a central registry database configured to store configuration information for a plurality of business hosts; And a central registry service configured to communicate configuration updates for multiple business hosts. Distributed multi-platform business integration system. The method of claim 28, The electrical control broker includes a partial registry database configured to store configuration information for at least one of a plurality of business hosts; And a monitor module configured to monitor the business host. Distributed multi-platform business integration system. The method of claim 28, The electrical service host is configured to include at least one of load balancing, data mapping, data translation, routing, formatting, scheduling, collaboration, and message checking. Distributed multi-platform business integration system. The method of claim 28, The electrical service host is configured to include at least load balancing, data mapping, data translation, routing, formatting, scheduling, collaboration, and message checking. Distributed multi-platform business integration system. The method of claim 28, At least one of the many multi-platform tasks is a supply chain management system Distributed multi-platform business integration system. The method of claim 28, At least one of the many multi-platform tasks is a consumer related management system Distributed multi-platform business integration system. The method of claim 28, Wherein at least one of the many multi-platform tasks is an enterprise resource planning system Distributed multi-platform business integration system. The method of claim 28, At least one of the many multi-platform tasks is characterized by financial management and planning tasks. Distributed multi-platform business integration system. Managing a request for a configuration change on at least a first resource; Collecting configuration change information from a plurality of resources associated with the request for configuration change; And, At least a first task is performed in the first regulating system, a second task is performed in the second regulating system, and a plurality of providing distributed tasks, such that the electric first regulating system and the second regulating system are not the same regulating system. Distributing configuration change information associated with a request for a configuration change to the distributed component of the system. Forwarding a request for a data and message related configuration change from the first host to the central host; Receiving at the first host configuration change information from a central host related to the request for configuration change; Executing at the first host a translation of the data and a message delivery of the configuration change in accordance with the electrical configuration change information. Providing a plurality of integrated modules corresponding to a plurality of multi-platform tasks and performing data-related and message transfers to enable communication between the plurality of multi-platform tasks; And, Providing a central host module that includes a central database of configuration data and manages and distributes configuration data to multiple integration modules, the configuration data comprising instructions for allowing communication between multiple multi-platform tasks; How to integrate multiple multi-platform tasks located in distributed networks. The method of claim 42, The central database of electrical configuration data interacts with multiple sub-databases of the configuration information interface having a plurality of integrated modules. Way. Displaying a first set of data sent from the first standalone task to the data translation module, translated into a second set of data, and passed to the second standalone task; Converting the electrical representation into a set of data translation and command delivery; And, A first data translation execution module for communicating the first set of data translation and command communication with the first independent service, and a first data translation execution module for communicating with the second independent service according to the set of data translation and command transmission. And distributing to the data translation execution module. A method of implementing a business contact system distributed between a first independent task and a second independent task. Central host means for displaying the accumulated configuration information; And, For allocating a portion of the accumulated configuration information to multiple task hosts, in contact with a plurality of corresponding multi-platform tasks and executing a portion of the accumulated information that enables communication between a plurality of corresponding multi-platform tasks. A distributed business integration system comprising a central host and a plurality of business hosts in communication with a plurality of multi-platform tasks, including a central host means.