Server implementation examples
Use the Integration Flow Designer to define systems of varying complexity. The simplest case involves one system that runs on one server. The following sections describe various examples of systems with increasing complexity.
Multiple independent systems running on one server
You can define multiple systems that have no data dependencies among their components and are all executed on the same server.
Although all systems in this configuration are executed on the same server, data can still be gathered from and sent to remote server locations. This behavior is possible because you can set the sources and/or targets of maps contained in the systems to directly cause data to flow from and to remote servers when these maps are executed.
You can also have multiple independent systems running on multiple servers.
Multiple dependent systems running on one server
You can use the Integration Flow Designer to define systems that have data dependencies among their components and are all executed on the same server.
Data sources and targets can exist on remote servers.
Multiple dependent systems running on multiple servers
You can use the Integration Flow Designer to define distributed systems. A distributed system consists of only subsystem components, not map components directly. These subsystem components are distributed across more than one server. Data flows across servers from one subsystem to another based on the sources and targets of maps that you specify to cause this flow.
Complex combinations of systems
You can define varying combinations of the previously described systems to yield very complex systems. For example, you might have a system that is distributed across servers as well as completely independent systems running on the same servers. The design of your systems depends on your requirements.