Đó là "nhận thức" của thời gian và nó có thể được truy cập thông qua WWW. Mô tả chi tiết hơn IS Đó là "nhận thức" của thời gian và nó có thể được truy cập thông qua WWW. Mô tả chi tiết hơn ISCũng giống như các thành phần khác của thư viện, thay đổi kích thước xác định một lựa chọn của các sự kiện tùy chỉnh | . Juric et al. Patterns for Enterprise Application Integration 91 interfaces. The interoperability interfaces define what services the client applications can request from the server applications. Interoperability interfaces define the relations between applications on which the applications depend. Interfaces define the coupling between integrated applications as long living contracts. They provide a faẹade through which the client applications access the interoperability services and encapsulate the applications. As long as the interfaces stay unchanged we can replace parts or the whole server application without influencing any client application. Therefore a lot of effort has to be put into the definition of the interoperability interfaces. EjistingAppiication Figure 1 Integration broker pattern Integration Broker should support one or more of the following communication models - Synchronous one to one communication where the client requires immediate response from the server and waits blocks for the response. - Deferred synchronous one to one communication where the client asks for a response later or is notified by the server call back or event . - Asynchronous one to one communication where the client does not require an answer from the server nor does it require for the server to be online by the time of submitting the request. - Asynchronous one to many communication where a single client can communicate with more servers. This model is also called publish and subscribe . Typical representatives of Integration Broker pattern are common middleware technologies particularly remote method invocations object request brokers and message oriented middleware. Integration Broker pattern is usually implicitly used in integration. This pattern requires one or more middleware products which implement the functionality. As today a high level of abstraction is achieved this pattern is not modeled in the design time. However the architecture has to be aware of this .
