Skip to main content

Patterns for e-business > Select Business pattern > Select Application pattern >
c


Extended Enterprise::Exposed Broker application pattern::Runtime patterns

On this page, two categories of Runtime patterns are described:


Generic Exposed Broker runtime patterns

The Exposed Broker application pattern can be thought of as an extension to the Broker application pattern. It extends the solution to include external partners by exposing their processes to the broker.

Exposed Broker application pattern::Runtime pattern
(Click a node to get a detailed explanation.)
Design Last Updated: 11-11-2005
Exposed Broker::Runtime pattern Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information

The Exposed Broker node encompasses the functionality of a Broker node, and in addition, includes the means to expose partner processes to internal processes.

The Connector in the Enterprise Demilitarized Zone may or may not be modelled. It provides connectivity from the Enterprise Secure Zone to the Inter-enterprise Zone. It may be a low level component (e.g. TCP/IP infrastructure) which is omitted from the diagram or it may have more advanced capabilities such as caching of reusable content (e.g. a Web server).

The Directory and Security Services supplies authentication and authorization services. It also holds the user ID and password and related privileges. This node typically leverages LDAP-based directories. It also contains configuration information needed to support secure access between the enterprise and partner services.

SOA profile

In this second section we specialize the Exposed Broker pattern for the SOA environment using the SOA profile. The SOA profile terminology is indicated using the [SOA] qualifier.

The generic Exposed Broker, Rules Directory and Partner Infrastructure in the figure above are specialized in the SOA profile to:

  • an Exposed ESB Gateway (supporting the Exposed requirement)
  • an ESB (supporting the Broker and Rules Directory requirement plus the SOA infrastructure requirement for service location transparency and interoperability, encapsulated reusable business function and explicit implementation-independent interfaces)
  • Service Consumers and Providers representing the Partner infrastructure

[SOA]Exposed Broker runtime pattern (aka Exposed ESB Gateway composite pattern)
(Click a node to get a detailed explanation.)
Design Last Updated: 11-11-2005
Exposed Broker::Runtime pattern Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information

Next, review product mappings for this Runtime design.

c