IOAI: The Gory Details

When leveraging IOAI, we need to focus on the information. We assume that the systems participating in the application integration problem domain can both produce and consume information. What's more, we assume that we can understand the structure and content of information coming from a source system or systems, account for the differences in a schema and content transformation layer, and publish that information, using the appropriate structure and content in the target system or systems. We can do this one-to-one, one-to-many, or many-to-many.

Moreover, we may mix and match integration types, as we stated above; thus, you may find that while ten systems participate in the application integration domain using IOAI, three may leverage application services and all ten may be integrated using business process integration. What's more, we may externalize information from all integrated systems to a Web site using portals (see Figure 2.3). Clearly, in many instances, the application integration problem domains are complex, requiring many types of integration approaches.

Figure 2.3. Remember, within application integration problem domains you're going to mix and match integration approaches.

graphics/02fig03.gif



Next Generation Application Integration(c) From Simple Information to Web Services
Next Generation Application Integration: From Simple Information to Web Services
ISBN: 0201844567
EAN: 2147483647
Year: 2005
Pages: 220

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net