|
|
 |
Extended Enterprise::Exposed Router application pattern::Guidelines
The last step in designing your e-business application is to review the guidelines for how to design, develop, deploy, and manage e-business applications. The guidelines help you customize the solution design, maximize performance, and select platforms on which to deliver the solution
General guidelines for designing all solutions include:
-
Pay attention to all components of the solution.
-
Understand in detail the interfaces and flows between the various components.
-
Plan for growth of the design.
-
Use the latest levels of infrastructure and system software.
-
Cache as much as possible.
This work is written primarily for IT architects and IT specialists but will be of use to anyone designing an e-business application.
|
Recommended technology options |
|
Chapter 7 of
Patterns: SOA with an Enterprise Service Bus in WebSphere Application Server V6, SG24-6494,
discusses the technologies that are used to implement the SOA patterns.
Three standards are of particular importance to an SOA implementation.
These are:
- Web services
- Java Message Service (JMS)
- J2EE Connector Architecture
The chapter describes SOA implementations in WebSphere Application Server V6.
The key technology to implementing in WebSphere Application Server V6 is:
Chapter 7 of
Patterns: Broker Interactions for Intra- and Inter-enterprise, SG24-6075,
has recommendations that are guided by the demands of reuse,
flexibility, and interoperability, and subsequently are based on the open industry
standards outlined by Java 2 Platform, Enterprise Edition (J2EE). Many of the
choices continue to evolve and expand as the J2EE specification matures to
include a broader view of the enterprise architecture. These recommendations
are based on the J2EE1.3 specification and parts of the J2EE1.4 specification.
|
Application design
|
|
Chapter 11 of
Patterns: SOA with an Enterprise Service Bus in WebSphere Application Server V6, SG24-6494,
exposes services outside the enterprise. The chapter builds on
the scenario described in “Enterprise Service Bus pattern: router scenario”.
The scenario adds a gateway which supports
interactions with services located outside the enterprise. The Manufacturers are
placed outside of the enterprise and communicate with the ESB using a gateway.
The following points are discussed:
- The business needs addressed by the sample scenario, and the use of the
Exposed ESB Gateway runtime pattern to address these business needs.
- The design decisions made in order to implement the chosen scenario.
- Development guidelines used in order to implement the chosen scenario.
- Runtime guidelines used in order to implement the scenario.
|
Application development
|
|
Chapter 11 of
Patterns: SOA with an Enterprise Service Bus in WebSphere Application Server V6, SG24-6494,
exposes services outside the enterprise. The chapter builds on
the scenario described in “Enterprise Service Bus pattern: router scenario”.
The scenario adds a gateway which supports
interactions with services located outside the enterprise. The Manufacturers are
placed outside of the enterprise and communicate with the ESB using a gateway.
The following points are discussed:
- The business needs addressed by the sample scenario, and the use of the
Exposed ESB Gateway runtime pattern to address these business needs.
- The design decisions made in order to implement the chosen scenario.
- Development guidelines used in order to implement the chosen scenario.
- Runtime guidelines used in order to implement the scenario.
|
System management
|
|
Chapter 11 of
Patterns: SOA with an Enterprise Service Bus in WebSphere Application Server V6, SG24-6494,
exposes services outside the enterprise. The chapter builds on
the scenario described in “Enterprise Service Bus pattern: router scenario”.
The scenario adds a gateway which supports
interactions with services located outside the enterprise. The Manufacturers are
placed outside of the enterprise and communicate with the ESB using a gateway.
The following points are discussed:
- The business needs addressed by the sample scenario, and the use of the
Exposed ESB Gateway runtime pattern to address these business needs.
- The design decisions made in order to implement the chosen scenario.
- Development guidelines used in order to implement the chosen scenario.
- Runtime guidelines used in order to implement the scenario.
|
Congratulations, you've completed all the steps to design your e-business application! There are some additional related links, that you might find helpful, including customer experiences, test reports, and Redbooks.
| |
|
