Implement Your ESB Using a Stepwise Approach

Bring order to the chaos of your system traffic to share, organize, and monetize your data.

Unlock

This content requires an active subscription.

Access this content by logging in with your Info-Tech Research Group membership or contacting one of our representatives for assistance.

Speak With A Representative Sign In
or Call: 1-888-670-8889 (US) or 1-844-618-3192 (CAN)

Your Challenge

  • Due to application proliferation, organizations today are having trouble integrating an increasing amount of data between siloed business unit applications.
  • This creates frustrations not only for IT, where a complex integration environment complicates its ability to support the business, but can slow the speed of business, impacting the bottom-line and profitability.
  • The ESB market is a crowded space, with differentiation focused around architecture and deployment models rather than out-of-the-box functionality.

Our Advice

Critical Insight

  • De-risk your ESB with a pilot deployment. Learn from a small town road trip before tackling the big city traffic. A pilot project will grow confidence in the project team and expose gaps that should be addressed early.
  • Not all systems should be passengers on the bus; grow your passenger base with the right systems. Target the high-priority systems that will provide the business with the greatest benefit from ESB integration.
  • ESBs – like real vehicles – need regular maintenance. Define integration governance measures to take care of the maintenance and keep the bus in top running order.

Impact and Result

  • With the increasing focus on SOA, and the growing connectivity and messaging requirements expressed by the business, IT departments require an integration solution that is scalable and highly flexible.
  • Integration connections become more brittle and complicated as environments change and grow. Integration middleware, namely an enterprise service bus (ESB), streamlines application integration by serving as a central connector.
  • The ESB implementation project helps you to prepare for the ESB implementation, to implement the selected ESB platform, and to test and sustain the ESB solution. An ESB implementation plan will be created to guide implementation effort and to plan for an ESB proof-of-concept project. An ESB architecture will be designed to support the implementation.
  • A test plan will be established to test the implementation holistically. By doing so, the ESB will lead to cost reduction by aligning data and services, increasing security, and creating an IT environment that is easier to support and maintain.
  • While the ESB implementation is underway, this blueprint helps you to establish necessary governance to make sure processes and governance bodies are in place to operate application integration effectively. A repeatable ESB development framework is created to streamline future ESB development.

Implement Your ESB Using a Stepwise Approach

Start here – read the Executive Brief

Read our concise Executive Brief to find out why you should implement your enterprise service bus using a stepwise approach, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.


1

Stage the environment for the ESB

Help the team gain an aligned and in-depth understanding of what an ESB is and how it will benefit the organization, and determine if the organization is ready for it.

2

Test and implement your ESB pilot project

Use this phase to help you get started with an ESB pilot project, which will help you to build confidence in the project at a smaller and more manageable scale.

3

Plan and implement the full ESB

After completing your pilot project, now is the time to begin the full project. Plan, implement, and test the full ESB solution to integrate the organization’s applications and data seamlessly.

4

Implement governance and maintenance of the ESB

Establish an enterprise integration center of excellence to scope, evaluate, and architect your organization’s integration governance and maintenance using your ESB solution.

Onsite Workshop

Book Your Workshop

Onsite workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost onsite delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

Module 1: Stage the Environment for the ESB

The Purpose

  • Develop a foundation of knowledge regarding the ESB and what it takes to be ready to start the project, as well as the estimated return on investment for the project.

Key Benefits Achieved

  • Clear objectives of the ESB project, as well as tools for communicating the benefits of the ESB to secure sustained buy-in from management.
  • Gain knowledge of how the ESB can benefit both IT and the business.
  • Understand the critical aspects of an organization that need to be in place before starting to implement the ESB, and strategies to become ready if these aspects are not in place already.

Activities:
Outputs

1.1

Facilitate activities from Phase 1 including project scoping, ROI calculations, and resource planning.

  • ESB Readiness Assessment Tool

1.2

Begin conducting an inventory of the organization’s integration environment.

  • ESB ROI Calculator Tool

1.3

Map integration scenarios.

1.4

Meet with system and data owners to discuss pertinent implementation details and get them on board.

Module 2: Architect and Plan Your ESB Pilot Project

The Purpose

  • Create a plan for the pilot project, which will help you to start with a more realistic scope of implementation and achieve quick wins.
  • Choose systems that will most benefit from being a part of the pilot project.

Key Benefits Achieved

  • Having a fully scoped implementation and test plan for the pilot ESB will ensure that the greatest benefit for the least risk is achieved.

Activities:
Outputs

2.1

Document the architecture environment.

  • ESB System Identification Tool

2.2

Make critical architecture decisions. Identify the systems that will be the first to be a part of the ESB solution as a pilot.

  • ESB Implementation Plan

2.3

Begin creating the ESB implementation plan.

  • ESB Test Plan

2.4

Document high-level solution requirements and complete the pilot implementation and test plans.

Module 3: Architect and Plan Your ESB Solution

The Purpose

  • Determine a strategic plan that outlines the key steps required to implement the full ESB solution.
  • Determine timing of system onboarding.

Key Benefits Achieved

  • Establish a clear plan for the ESB solution.
  • Build a step-by-step outline of how to effectively implement the ESB.
  • Have prioritized initiatives with dependencies mapped out.

Activities:
Outputs

3.1

Produce detailed plans regarding the full implementation of the ESB after the pilot, including a system onboarding roadmap.

  • ESB System Identification Tool
  • ESB Implementation Plan Template

3.2

Review testing principles and procedures that will ensure that the ESB is providing the expected ROI.

  • ESB Test Plan Template

Module 4: Set up an Effective SOA Governance Program

The Purpose

  • Identify the roles required for effective SOA governance.
  • Understand how to set up an integration CoE and how to integrate ESB governance bodies with existing data governance bodies.

Key Benefits Achieved

  • Without effective governance and controls of the ESB integration solution, the project could end up providing less value than promised.
  • Proper oversight of the solution will ensure that the technology provides the business with the data it needs.

Activities:
Outputs

4.1

Identify and begin to create the relative policies and procedures for effective governance of the ESB.

  • ESB Implementation Plan Template

4.2

Meet with the project manager to discuss results and action items.

  • Integration Center of Excellence Charter

4.3

Wrap up outstanding items from the workshop.

Search Code: 81460
Published: August 16, 2016
Last Revised: August 16, 2016