|< Day Day Up >|| |
This chapter provides definitions of the nodes used in the intra-enterprise and inter-enterprise Runtime patterns that are described in 3.5, "Runtime patterns" on page 54 and 4.3, "Runtime patterns" on page 86.
It also provides Product definitions for the products used in the intra-enterprise and inter-enterprise Product mappings that are described in 3.6, "Product mappings" on page 57 and 4.4, "Product mappings" on page 88.
A Runtime pattern consists of several nodes representing specific functions. Most Runtime patterns consist of a core set of common nodes, with the addition of one or more nodes unique to that pattern. To understand the Runtime pattern, you will need to review the following node definitions.
The application server node provides the infrastructure for application logic and can be part of a Web application server. It is capable of running both presentation and business logic but generally does not serve HTTP requests. When used with a Web server redirector, the application server node can run both presentation and business logic. In other situations, it can be used for business logic only. The application server node supports hosting of Web services applications.
Applications may also rely on services provided by their hosting server to interact with other applications. Examples of services provided by the Application Server/Services node include:
A TCP/IP pipe established using the hosting operating system
A servlet or EJB invoked by WebSphere Application Server
The JMS or J2EE Connector APIs provided by WebSphere
Connectors provide the connectivity between two components. A connector is always present to facilitate interaction between two components.
Depending on the required level of detail, a connector can be:
A primitive (or unmodeled) connector, represented by a simple line between components.
A component (or modeled) connector, represented by a rectangle on a line between components.
A connector may be an adapter connector, a path connector, or both.
"Adapter connector" on page 98
"Path connector" on page 99
Adapter connectors are concerned with enabling logical connectivity by bridging the gap between the context schema and protocols used by the source and target components. An adapter connector is one that supports the transformation of data and protocols.
Path connectors are concerned with providing physical connectivity between components. A path connector may be very complex (for example, the Internet), or very simple (an area of shared storage).
The rules directory contains the rules generally used to control the mode of operation of an interaction, depending on external factors. Examples of such rules are:
Business data mapping rules (for adapter connectors)
Autonomic rules (such as priority in a shared environment)
Capacity and availability rules
The rules directory may or may not exist. If it does exist, it could still be left off the Runtime pattern, for example, when analysis determines that interaction rules are not an important part of the solution.
The integration pattern for a domain is composed of a topology pattern and domain QoS providers. Intra-enterprise integration and inter-enterprise integration are both examples of domains. This combination of topology pattern and QoS providers is used to describe observed patterns in the domain.
Integration pattern = topology pattern + QoS providers
The QoS capabilities framework can be used to address the particular QoS concerns for the domain:
The domain QoS providers may or may not exist. If they do exist, they can still be left off the Runtime pattern, for example, when analysis determines that domain QoS providers are not an important part of the solution.
A firewall is a hardware/software system that manages the flow of information between the Internet and an organization's private network. Firewalls can prevent unauthorized Internet users from accessing private networks connected to the Internet, especially intranets, and can block some virus attacks (as long as those viruses are coming from the Internet). A firewall can separate two or more parts of a local network to control data exchange between departments. Components of firewalls include filters or screens, each of which controls transmission of certain classes of traffic. Firewalls provide the first line of defense for protecting private information, but comprehensive security systems combine firewalls with encryption and other complementary services, such as content filtering and intrusion detection.
Firewalls control access from a less trusted network to a more trusted network. Traditional implementations of firewall services include:
Screening routers (the protocol firewall)
Application gateways (the domain firewall)
A pair of firewall nodes provides increasing levels of protection at the expense of increasing computing resource requirements. The protocol firewall is typically implemented as an IP router.
The domain firewall is typically implemented as a dedicated server node.
A domain firewall is usually used to separate a secure zone, such as the internal network, from a demilitarized zone. This provides added security protection from the un-secure zone, such as the Internet.
Partner infrastructure includes the partner's installed applications, data, computing, and network infrastructure. Partner infrastructure has unspecified internal characteristics; only the means with which to interact with it is specified.
Inter-enterprise network infrastructure includes the network infrastructure allowing connectivity between enterprises. Inter-enterprise network infrastructure has unspecified internal characteristics; only the means with which to interact with it is specified.
The Local Area Network (LAN) node is a communications network that serves users within a confined geographical area. It is made up of servers, workstations, a network operating system and a communications link.
The Wide Area Network (WAN) node is a communications network that covers a wide geographic area, such as a state or country.
|< Day Day Up >|| |