Extending WSSR to Legacy Applications
•Download as PPTX, PDF•
0 likes•794 views
Speaker: Animesh Jain, Prolifics Almost all organizations today have embraced the concept of SOA and is aligned to the path of application agility. Bottlenecks can come in the form of legacy applications where the endpoint of the service provider is stored either in a constant or in a property file. This restricts the ability to change both at the service provider and consumer end. Applications integrated with WSRR have the ability to select the endpoints based on policy. Not only are they immune to constructive changes at the service provider, but this also eases the overall governance process. In this session, we will focus on: pattern to integrate WSRR with legacy java applications based on Spring framework, different scenarios in which it should be use, deep dive into the development and maintenance aspect, and extending this pattern to make it framework independent. http://www.prolifics.com
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (8)
Similar to Extending WSSR to Legacy Applications
Similar to Extending WSSR to Legacy Applications (20)
More from Prolifics
More from Prolifics (20)
Recently uploaded
Recently uploaded (20)
Extending WSSR to Legacy Applications
- 1. CONNECT WITH US: IT: Customized to Your Advantage IBM IMPACT 2014 Conference Session 2740: Extending WSRR to Legacy Applications ANIMESH JAIN Solution Architect Public | Copyright © 2014 Prolifics
- 2. CONNECT WITH US: Do I need registry? This could become… The promise of SOA … like this A pile of services 2
- 3. CONNECT WITH US: Customer Story Major Health Care Client In House JAVA .NET MainFrame Acquisitions JAVA .NET MainFrame Services with similar functionality Lack of Version Control Lack of Discovery Application Specific Services Multiple Integration Points 3
- 4. CONNECT WITH US: What was needed: ORGANIZER Holistic View Inventory Management Scalability 4
- 5. CONNECT WITH US: Why SOA? Ever changing business Hone the Strategic advantage Regulatory changes and quick time to market Need of Agility 5
- 6. CONNECT WITH US: INTEGRATE –COMPOSE-ORCHESTRATE 6 APP A APP B
- 7. CONNECT WITH US: INTEGRATE –COMPOSE-ORCHESTRATE 7 APP A APP B
- 8. CONNECT WITH US: INTEGRATE –COMPOSE-ORCHESTRATE 8 APP A APP B
- 9. CONNECT WITH US: WSRR to rescue 9
- 10. CONNECT WITH US: WSRR: Promotion of Policy and Endpoint 10
- 11. CONNECT WITH US: Lifecycle States for a WSDL in WSRR 11
- 12. CONNECT WITH US: WSRR Governance and Runtime Topology 12
- 13. CONNECT WITH US: INTEGRATION NEEDS ABILITY TO MAKE CHANGE SUPPORT RESTRICTED NUMBER OF VERSIONS REDUCE FAILURE POINTS REDUCE MAINTENANCE COST Why governance for legacy applications? 13
- 14. CONNECT WITH US: Preferred Path 14
- 15. CONNECT WITH US: Intermediate Path 15
- 16. CONNECT WITH US: Intermediate Path 16
- 17. CONNECT WITH US: Intermediate Path 17
- 18. CONNECT WITH US: Intermediate Path 18
- 19. CONNECT WITH US: Summary Can become… The promise of SOA … like this A pile of services 19
- 21. CONNECT WITH US: 21 Session Topic & Description Date & Time Room BDL-3320 BPM, Rules & Analytics - A Business Trilogy - Are You Part of the Story, or Reading About it? Mon, Apr 28, 2014 [12:00 pm - 12:30 pm] EXPO Theater SCU-2695 BMI: Innovating with IBM Business Process Manager, IBM Operational Decision Manager, and Integration Tue, Apr 29, 2014 [10:30 am - 11:20 am] Venetian-Palazzo K ICU-3319 The Power of 3: PureApps, Softlayer and General Operational Effectiveness Tue, Apr 29, 2014 [12:00 pm - 12:45 pm] Delfino 4005 ICU-3358 How PSCU Implemented their Intelligent Platform through a SOA COE Tue, Apr 29, 2014 [2:15 pm - 3:15 pm] Marcello 4402 INO-2740 Extending IBM WebSphere Service Registry and Repository to Legacy IBM WebSphere Application Server Wed, Apr 30, 2014 [2:15 pm - 3:15 pm] Marcello 4405 ICU-2748 Enabling a Digital Strategy that Fits the Healthcare System around the Consumer Using BPM SOA COE @ AETNA Wed, Apr 30, 2014 [5:00 pm - 6:00 pm] Marcello 4401A ICU-2800 An Approach to an SOA Appliance and Application Center of Excellence by Staples Thu, May 1, 2014 [9:00 am - 10:00 am] Marcello 4401A Join Prolifics thought leaders and our clients at the following sessions… 21
Editor's Notes
- Most of you would have already seen this slide. This is a slide that IBM uses often to facilitate the need of registry. Almost all organization today has embraced the concept of SOA. They need SOA to make their application agile. We frequently create services with the thought that services will derive all the benefits of SOA. However, services are just a stepping stone in the right direction. What happens is, that we keep creating services and integration points and finally they become a liability more than an asset. Not generic Client specific Duplicate functionality and finally become difficult to manage. **************************************** In our closet, we want all our dress to arranged, so that I can find the right dress quickly, We are creating services, however the governance aspect needs to catch up with the development. IT industry IT industry has been looking at ways to help them decouple the components and reduce point to point integration.
- Last Year a major health care provider reached out to us. Like most of us, they have different flavors of applications. Some are built in .net, some in java, while some are mainframe apps. They also acquired another company, which added to their list of applications to manage. Their development teams pressed the panic button as absorbing any change was getting very effort intensive, thereby running up the overall maintenance cost. They started feeling SOA as an overhead instead of an asset.
- As you know, there are multiple ways to organize our closet….. The basic ideology is that an organizer should Ease of access Holistic view of what I have and what I may need Helps understand what we need to take out and donate In this picture you can see trhat WSRR is our organizer here…..
- SOA provides a paradigm for interaction, but it doesn’t enforce the implementation.
- There are various paths that we can take to reach from point A to point B. Which path we take, will determine the adv and disadv.
- Which comprise of middle layer….. ESB+WSRR
- In our day-to-day application maintenance, we all come across applications that makes call to another service with the endpoint stored either in a constant or in a property file. This tight coupling not only increases the complexity at the service consumer but also restricts the service provider in its ability to make any change that can have a potential impact in its exposed endpoint. Very often the service provider is required to support multiple versions till the consumer has the bandwidth to make the switch. This greatly increases the overall cost of application maintenance and also increments the number of failure points.
- Let all the legacy applications interact with each other via ESB layer.
- Let all the legacy applications interact with each other via ESB layer.