A kiválasztott változat és az aktuális verzió közötti különbségek a következők.
| Előző változat mindkét oldalon Előző változat | |||
|
tanszek:oktatas:iss_t:enterprise_service_bus_esb [2023/04/24 18:07] knehez |
tanszek:oktatas:iss_t:enterprise_service_bus_esb [2023/04/24 18:12] (aktuális) knehez |
||
|---|---|---|---|
| Sor 22: | Sor 22: | ||
| * message routing – based on context and content | * message routing – based on context and content | ||
| * QoS (Quality of Service) – performance, security, reliability | * QoS (Quality of Service) – performance, security, reliability | ||
| - | * data enrichment – information extension with automatic extra data | + | * data enrichment – information extension with automatic extra data |
| + | |||
| + | |||
| + | |||
| + | +----------------------+ | ||
| + | | Integration | | ||
| + | | Repository | | ||
| + | +----------+-----------+ | ||
| + | | | ||
| + | +--------+---------+ | ||
| + | | Enterprise | | ||
| + | | Service Bus | | ||
| + | +--------+---------+ | ||
| + | | | ||
| + | +---------------------+--------------------+ | ||
| + | | | | | ||
| + | +-------+--------+ +-------+--------+ +-------+--------+ | ||
| + | | Application 1 | | Application 2 | | Application 3 | | ||
| + | +----------------+ +----------------+ +----------------+ | ||
| + | |||
| + | In this example, an Enterprise Service Bus (ESB) is positioned between multiple applications, represented by the boxes at the bottom of the diagram. The ESB serves as a central hub for managing the integration of these applications, and it communicates with each application using a standardized set of protocols and formats. | ||
| + | |||
| + | An Integration Repository is a key component of an Enterprise Service Bus (ESB) architecture. It is a centralized repository that stores information related to the integration of different applications and systems. | ||
| + | |||
| + | The Integration Repository typically contains information about the data structures, message formats, and protocols used by each application or system. This information is stored in a standardized format that is understood by the ESB, allowing the ESB to route messages and transform data between applications. | ||
| + | |||
| + | The Integration Repository also contains other artifacts related to integration, such as mappings between different data structures, transformation rules, and message schemas. | ||
| + | |||
| + | One of the main benefits of using an Integration Repository is that it provides a centralized location for managing the integration of multiple applications and systems. | ||
| + | * simplifies the integration process, reduce errors | ||
| + | * improve the overall efficiency of the integration process. | ||
| + | * by storing integration artifacts in a centralized location, it becomes easier to maintain and update the integration process. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||