SOA解决方案介绍分析.ppt

* One of the challenges many portal customers face is that of existing rigid infrastructure where the primary view of application functionality across divisions is from the enterprise application perspective. These silos tend to stand alone, and trrough acqusition, over time, replicate making the situration worse. Click – from a user perspective this requires many different application interfaces, logins, and user confusion. Too much to manage at an user level which in turn tends to be costly, inefficient, and a negative impact on service whether the customer is an employee or external purchaser. Main Points: The traditional approach focusing on function undermines portal success Questions: Do you have many portals that follow this approach? Across what functional areas? What challenges do you see? Script: When you consider how portals have evolved over the last few years you see a trend where silos that are front-ended by portals predominate and result in a proliferation of different portals that end users must navigate through. Unfortunately this undermines the success of the portal as it places additional burden on the user reducing - instead of improving productivity and adoption. Its easy to see that an HR portal that is used only once in a while will require relearning with each visit. So what is a better approach? * Another key area we see increasing benefits coming from is through portal federation – a way to deploy standards-based distributed portals that provide benefits for both IT and the busienss….. ----------- Federated Portals is all about empowering users to share their applications across the network with different Portals. It is also about discovering remote applications and bringing them into the Portal. In this picture you can see how different portlets could be made a available in the network as remote resources, remote portlets, using WebLogic Portal. Those portlets can then be aggregated into another portal that exposed