Three ways for Enterprise IT to increase the reliability of Business App delivery over Hybrid IT

Part 1 of 3: Three ways for Enterprise IT to increase the reliability of Business App delivery over Hybrid IT

Enterprise CTOs want to accelerate business application modernization and cloud adoption. The journey begins with a review of each on premises legacy app, in order to assess whether it will be easy or problematic to move to cloud, and to decide which parts should be moved first. The app owner asks IT some ‘simple’ questions: Where is my app? What infrastructure does my app depend on? Can you give me a ‘map of my app’? In many enterprises today, it’s still not easy for IT to provide the app dependency visibility needed.

IBM Business Partners have the opportunity to help clients step beyond basic discovery, increase automation and map the application dependencies. In this three part blog series, we will discuss the following ways to improve reliability:

  • Plan app modernization to minimize business user impact based on understanding legacy app dependencies on Hybrid IT
  • Shorten the time to isolate the origin of app user issues (Check back 11/14)
  • Manage Hybrid IT infrastructure change to avoid business app user impact (Check back 11/27)

Before tackling the job of modernizing applications, Dev and Ops teams need to understand the application inventory from a modernization perspective and classify the application portfolio. As legacy apps and workloads are evaluated for migration to cloud, it becomes clear that not all apps will be modernized, nor all components. Enterprises will want to modernize the interactive parts facing the end users first. However, the decision to move a specific workload to the cloud is not a trivial one.

App owners need a deeper understanding of the app delivery environment. To identify workloads that might be re-located to cloud, you need to understand all the physical, logical, and operational relationships and dependencies between resources. For this reason, app owners are looking to IT for more visibility into the end-to-end hybrid infrastructure that their apps depend on. They need a deep understanding of the app’s dependency on a complex delivery infrastructure comprising middleware, specialized servers and sub-components, cloud, virtualized and physical environments, and resources provided by dedicated storage and network infrastructure.

Dependencies between components also need to be understood. For example, duplicated system resources may be used for backup and disaster recovery. Specialized resources may be used for performance optimization (e.g., clustering, load balancing). The app may also have dependencies on additional centrally controlled services like authorization and security.

IT needs to provide the app owners with topology map views showing the app dependencies on the underlying Hybrid IT. This app dependency data is critical input from the initial analysis phase to the final phase of validating the application after components are moved to the cloud.

It’s time to reach out to your customers and become their trusted advisor.

Let your clients know the added value they can unlock from IBM Tivoli Application Dependency Discovery Manager (TADDM), e.g. to leverage their BigFix investment to automate discovery behind firewalled zones, and implement application dependency mapping to increase visibility and understanding across the business. Let your clients know they can extend their discovery solution with new agile service management capabilities from IBM.

Your CTO and CIO will thank you!

Colette Finneran
IBM Cloud – Offering Management – ITSM/Operations Management


For more infoplease connect with Paul Watkins, Technical Leader for IBM’s Service Desk, Application Dependency Discovery Manager and Systems Automation capabilities, to get the latest roadmap update.

You are invited to join Paul’s Webinar on November 12 at 11 AM Eastern Standard Time (EST) to hear more about Application Modernization and the Value of Service Management. You can register here.