Front-End Integration

The Front-End Integration pattern describes those recurring designs that enable access to one or more Business patterns. In particular, this pattern enables access from multiple channels (devices) and integrates the common services required to support a consistent user interface.

If you're not yet sure that your business problem can be solved by the functionality enabled through a Front-end Integration solution design, the Front-End Integration general guidelines page provides additional information on choosing this Integration pattern. Business and IT drivers, the e-business context appropriate for this solution type, and additional solution details are discussed here.

If you've determined that the Front-End Integration pattern can provide an appropriate solution design for your business need, the next step is to select an Application pattern. The Front-End Integration pattern can be implemented using one of three Application patterns, providing solution flexibility so that the determined Integration pattern can address the specific needs of the business process being automated.

• Patterns for e-business naming conventions

• Renamed Access Integration patterns

  Updated: 10-16-2006
  The Access Integration patterns have been renamed the Front-end Integration patterns.

• New Client application pattern

  Updated: 03-08-2006
  The new Front-end Integration::Client application pattern extracted from the IBM Redbook Patterns: SOA Client - Front-end Integration Solutions(SG24-6775) replaces the Pervasive Device Access application pattern

• Feasibility:
  This material will help you determine the high-level shape of an Extended Enterprise solution, and can ensure your approach looks similar to other successful implementations. Reuse of prior approaches can be an effective way to begin most major projects. Obviously, modifications will be needed for any unique requirements of a given set of partners. This pattern provides a drill-down from high-level architecture to low-level designs and guidance.

• Risk:
  Basing new projects on prior designs and ideas helps to lower the risk of failure. Creating or inventing approaches for each project tends to result in a lower success rate. Frequently, projects begun "from scratch" simply do not work and have major exposures in such areas as security, performance, availability, undefined requirements, and cost overrun.

• Cost-benefit:
  By starting with reasonably complete architecture you can save considerable development time and can obtain assurance that the end solution will have a much higher chance of success. Actual savings will vary, but project teams have realized a 10% to 50% reduction of work effort in their design and architecture phases alone.