|< Day Day Up >|| |
The next step is to choose Runtime patterns that most closely match the requirements of the application. A Runtime pattern uses nodes to group functional and operational components. The nodes are interconnected to solve a business problem. Each Application pattern leads to one or more underpinning Runtime patterns.
We can overlay the Application pattern onto the Runtime pattern to identify where business logic is deployed on nodes. The Runtime patterns illustrated give some typical examples of possible solutions, but should not be considered exhaustive.
To understand the Runtime pattern, you will need to review the node definitions provided in 5.1, "Node types" on page 98.
We cover Runtime patterns for Direct Connection in this section. Look for details on the Broker runtime pattern or the Serial/Parallel Process runtime patterns in a future redbook.
When using the Direct Connection runtime pattern, shown in Figure 3-11, the source application uses a connector to access the target application.
Figure 3-11: Direct Connection runtime pattern
The connector itself may be explicitly or implicitly modeled. If the connector is explicitly modeled, the modeler can use decomposition and abstraction techniques to expand the connector to the appropriate level of detail.
The term Connector may be qualified by both the connector variation and by the interaction variation. Some examples are:
Call Adapter Connector
The source and target applications both rely on services provided by their respective hosting servers. These are modeled using the Application Server/Services component.
The Rules Directory and Domain QoS Providers may or may not exist. If they do exist, it is a modeling decision as to whether they need to be shown in the Runtime pattern. For example, analysis may determine that connection rules are not an important part of the solution, so the Rules Directory may be left off the Runtime pattern.
The basic Direct Connection runtime pattern allows integration between a source and target application that use different protocols using a single adapter connector. Direct Connection using a single adapter connector is shown in Figure 3-12.
Figure 3-12: Direct Connection using single adapter
Direct Connection can also be implemented using coupling adapter connectors, as shown in Figure 3-13, to improve reuse potential in multiple point to point scenarios. It supports conversion of the request and response into a common protocol between the adapters.
Figure 3-13: Direct Connection using coupling adapters
You may notice that we don't have separate Runtime patterns for the message and call variations of the Direct Connection application pattern. It is still important to identify that your business scenario requires a message or call application pattern, because you can use this knowledge as a consideration when selecting a Product mapping. In the next section we highlight Product mappings that have a more natural fit to the Application pattern message variation or to the Application pattern call variation.
|< Day Day Up >|| |