V. Process integration model
The model of process integration has exceeded the concept of "process operation model". But as a very popular trend of "system integration", get here.
The current business is increasingly complex, cross-regional, cross-sectoral information interactive mode needs to be more obvious, and cross-regional, cross-sectoral business cooperation is more and more. From the development of information integration, "application-oriented data level integration" and "service-oriented interface layers integration" are gradually tiered to "BMP" mode: multiple subflows controlled by the central mainstream (distributed in different regions or different departments, " Individually independent processes) work together to achieve the operation of the entire business logic.
In fact, in the "Process Activation Model" model of the second chapter, I have already mentioned some, just not clear. So let's take a look at an ordinary "process integration", please see the picture below.
The actual integration is more complicated than this picture. Maybe there will be some information exchange interfaces such as JMS / WebService, may be used to different manufacturers of data exchange platforms, or news middleware, etc.; of course, those safety measures must also May not be less.
Simple integrated model, basically use "mainstrection control": controlling the entire process of the entire process by a main process, complete a task, and returns the processing result to the main proximity. After the primary proximity is determined correctly / processes the processed information, the other sub-process will be activated in a predetermined process route.
In some process integration design, the main process itself does not complete any task (responsible for operation control); and in some design, the main process itself needs to complete some tasks.
Figure (5-1)
At this point, the operation model of the process is basically ended. In reality, the model that may exist is more complicated than these "graphics", and many factors (organizational models, security, information documents, etc.) are considered. The more factors considering, the higher the complexity involved, the higher the requirements for the workflow engine. In fact, a very common workflow engine is difficult to exist. Because a workflow engine not only needs to parse the predetermined process, but also the data information in the maintenance process operation (many business data is very strong), and most of the workflow engines are positioned in one direction. Solve a certain type of problem.
I hope that the above text can let everyone know some of the general process running models. Really in use, you still need to go to explore yourself and accumulate.
I also want to put the "state model" of the process, but consider this status model itself is enough to say a lot, so I will go later, and I will specifically write an article that explores the status model.
After all, it is inevitable that there is a misfortune.
postscript:
I finally finished writing, I have painstable. There are more than 20 photos in light. However, it is worth a lot. I used these models in my brain. I thought it was very perfect. As a result, when I truly wrote it, I found it really.
These two years, popular "workflow", "integration", "content management", etc. It has far beyond the simple MIS concept a few years ago, and it is known that there is more information development. In fact, the concept of workflow has been out of time, but in recent years, it is only popular in China's software industry, so, no matter from theory, it is still far away from the practice.
In fact, many ways, we are all behind, although we can keep up with new concepts of foreign countries. But the concept of people is slowly accumulated from practice, and we are deepening; and we are mostly "introduced". DEV2DEV participating in BEA a few days ago, I feel deeply. If you sigh, don't say much, I hope everyone will gradually "deepen" in the future applications.
