Downloaded 2,322 times
Uploaded byVincent Perrin
WebSphere Portal Technical Overview
WebSphere Portal V6.1 provides a technical overview of the product's architecture and components. It discusses the portal tier, backend tier, security tier, content tier and how they work together. It also summarizes the main components of WebSphere Portal including the application server, database, directory server, and search. Finally, it highlights how WebSphere Portal works with various platforms, databases, directories, security managers, web servers and browsers.
More Related Content
![[Alexandria Devfest] the magic of flutter](https://cdn.slidesharecdn.com/ss_thumbnails/egyptdevfestthemagicofflutter-181114115455-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to WebSphere Portal Technical Overview
![[Day in a Life] Polycom & Kenexa Brass-Ring - Video Interview](https://cdn.slidesharecdn.com/ss_thumbnails/kenexa-140218030649-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
![Getting Started with Apache Spark: Big Data Made Simple [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/apachesparkgettingstarted-260203175547-8361bcc3-thumbnail.jpg?width=640&height=640&fit=bounds)
WebSphere Portal Technical Overview
- 1. © 2008 IBMCorporation IBM Software Group An IBM Proof of Technology Portal Technical Overview Discovering the value of IBM WebSphere Portal V6.1
- 2. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview WebSphere Portal Production Architecture WAS/WP Portal Tier Repository Collaboration Tier Backend Tier ERP EIS Enterprise Data Security Tier TAM LDAP Firewall Content Tier DB2 CM Web CM Browser Firewall DMZ Load Balancer Web Servers WebSEAL
- 3. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Works with your Environment ● Platforms AIX®, i5/OS®, RHEL and SLES Linux® (Intel®, pSeries®, zSeries®), HP-UX, zOS® (native)*, Solaris™ and Windows® ● Databases IBM DB2®, Oracle®, SQL Server®, Derby (Cloudscape®) ● Directories Microsoft® Active Directory, Novell® eDirectory, Sun™, Domino®, IBM Directory Server, Custom User Registry ● External Security Manger Tivoli® Access Manager, SiteMinder ● HTTP Web Servers IBM, Apache, Microsoft, Sun ● Browsers Microsoft Internet Explorer, Firefox® *Coming later in 2008
- 4. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview WebSphere Portal Main Components WebSphere Portal WebSphere Application Server Derby (database) IBM HTTP Server IBM Directory Server (LDAP) Search Web Content Management Personalization CollaborationCollaboration WebSphere Portlet Factory Also Domino, Microsoft, AD, Novell, Sun, etc Also IIS, etc. Also DB2, Oracle, SQL Server
- 5. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Architecture Overview WebSphere Portal V6.1 Portal Database(s) User profile Database LDAP Directorie(s) Page Aggregation Themes and skins Page Handler Dynamic UI Manager Rules Portlet Container and Services Portlet API Content access Search Portlet Preference Collab- oration AJAX Proxy Web clipper Live Text Site Admin Credential Vault Single Sign-on XML Access Portal Script REST / APP J2EE JCA Web Services EJB JMS JDBC Servlet Security Caching Enterprise Data, Applications, Internet Content Process Server Remote portlet producer AUTHENTICATION Desktop and mobile Browsers, Mashups and offline Clients Remote portlet consumer Policy Portal Model Template Composition Component Handler Application RuntimeAUTHORIZATION Feed Provider JSR286 WSRP 1.0 + 2.0 WSRP 1.0 + 2.0 Widgets ● JDBC = Java Database Specification ● JCA = J2EE Connector Architecture ● EJB = Enterprise Java Beans ● JMS = Java Message Service
- 6. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Portlet Perspective ● To an End User: a portlet is a window to display their preferred content ● To a Content Provider: a means for targeting content to the end user. ● Portal Administrator: a WAR file ● Portal Server: a component rendered and aggregated into one of its pages ● Developer: a java application whose lifecycle is managed by the container
- 7. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Portlet Standards ● Java™ Specification Request (JSR) 286 – Java Portlet Specification V2.0 IBM is leading this JSR, all major Java technology portal (commercial and open source) vendors represented Approved: March 04th 2008 (WebSite complete April 9th) ● Web Services for Remote Portlets (WSRP) V2.0 Standard protocol for accessing portlets as web service Defined at OASIS, chaired by IBM, Approved: March 31st 2008 ● Common goals Enable coordination between portlets and allow building composite applications based on portlet components (events and render context (e.g. public render parameters) ) ● WebSphere Portal seamlessly integrates JSR168, JSR286 and WSRP 2.0 Portlets. ● Also integrates IBM Portlet API and WSRP 1.0 04.03.2008: http://jcp.org/en/jsr/detail?id=286 31.03.2008: http://www.oasis-open.org/committees/ballot.php?id=1431
- 8. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Portlet Conceptual Flow (Server-Side Aggregation) ● 1. User clicks on portlet, request sent to action dispatcher function ● 2. Dispatcher sends input to portlet as a request object ● 3. Portlet accesses application that accesses data and returns to portlet ● 4. Portlet generates markup fragments and passes to page aggregation ● 5. Page aggregation builds page and returns to browser
- 9. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Portal Page Aggregation Process (Server Side Aggr) Layout system is called for the target markup. JSP templates define the overall page, rows, columns and decorations. Themes and Skins define the look and Feel Page Aggregation Servlet STEP 5 STEP 1 STEP 2 STEP 3 STEP 4 STEP 5 STEP 5 Servlet examines the request to determine device type, user and language Security settings are checked to determine which pages and portlets the user is authorized to see Processes portlet messages and sends events to other portlets. All events must be completed in this phase. Portlets render themselves in parallel
- 10. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Client Side Aggregation ● Turn your existing Portal Applications into “desktop like” applications Highly reactive and direct user interface Many actions possible without server roundtrips Avoids page reloads ● Improved performance and scalability Reduced server side processing Reduced bandwidth requirements Reduced client-side processing Improved cachability ● Browser-side Aggregation, Navigation and Customization Renders XML obtained from the server in the browser Implemented using Asynchronous JavaScript™ and XML (AJAX), XML, Dojo, and JavaScript *REST is the acronym for „Representational State Transfer“ It is the architectural model on which the WWW is based “Most existing Portlets benefit directly from Web2.0 rendering model without any changes.”“Most existing Portlets benefit directly from Web2.0 rendering model without any changes.” Gadgets Atom / RSS Feeds REST-accessible Markup Fragments Portlets or other WSRP Services
- 11. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Deployment MgrHTTP Server Directory Server Database Server ● WebSphere Portal (& WCM) utilize WAS clustering ● Portal ships with WebSphere Application Server ND (Network Deployment) in the box*. ● Search Server can be separated from Portal. Search Portlets communicate remotely ● Reference: Step-by-Step Cluster Guide for IBM WebSphere Portal v6.1 http://www-1.ibm.com/support/docview.wss?rs=688&uid=swg21313184 Portal Search WebSphere Portal Content Apps WebSphere Portal Content Apps WebSphere Portal Content Apps *Limited license for Portal Express The Basic Horizontal Cluster Multi-Node Portal Clustering
- 12. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview WebSphere Application Server (WAS) WAS Virtual Member Manager (VMM) Integration LDAP WAS Security WebSphere Portal PUMA SPI (public since v5101) VMM UR Adaptor DB Custom* Federated* WAS LDAP LDAP * Default Portal Install (Federated, File-based)
- 13. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview WebSphere Portal 6.1 Security ● Portal utilizes Virtual Member Manager (VMM) in WebSphere Application Server V6.1 VMM User Registry (UR) adapter acts as integration point between WebSphere Applicaiton Server security & VMM com.ibm.ws.wim.registry.WIMUserRegistry Public API for custom adapter ● Out of the box, VMM supplies adapters for File-based, LDAP & Database repositories ● WebSphere Application Security is enabled when Portal is installed ● Integration in WebSphere Security infrastructure Supports WebSphere TAI++ (Trust Association Interceptor) Enables establishment of trust without verification with WebSphere Portal 6.1 ● WebSphere Portal can bind to multiple LDAP directories ● SPNEGO support (Windows Desktop SSO) Automatically authenticate the user if logged into the desktop LDAP 1 Customers LDAP 2 Partners LDAP 3 Employees
- 14. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Customer identification with your Website can increase customer loyalty. Customer identification with your Website can increase customer loyalty. Remember Me and Step-Up Authentication The site recognizes me without login…The site recognizes me without login… …requires user authentication… Access to sensitive service or operation,... … before access is provided.
- 15. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Exceptional “User Experience” Drives Productivity ● Contemporary, Fresh Look and Feel ● Fly Out Menus and Page navigation ● Drag & drop support ● Portlet Palette ● Search ● Menus delivered “in context” Appropriate actions based on the portal object Only shows the “actions” allowed by the “User Role” (Security) ● Super-responsive, rich and interactive portlets, content and applications
- 16. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Putting Pages, Applications & Other Content into Portal 1. Display Existing HTML/Web Apps Web Clipping, Web Application Integrator* 2. Install Existing Portlets Out-of-the- Box or from the Portlet Catalog Enterprise Resource Planning (ERP), Customer Relationship Management (CRM), eMail, Green Screen, Dashboard, etc. (drag and drop on to pages) 3. Use HTML tools (“Static Pages”)* Build HTML/CSS with HTML editor. Add portlets, live text, instant messaging, etc. 4. Lotus® Web Content Management HTML/JS content, Personalization, Web Content Integrator, Doc Libraries* 5. Use Built-in Web 2.0 Services* Semantic Tagging (Live Text), Client-Side aggregation, AJAX, REST 6. Incorporate Collaboration Awareness, Instant Msg, Team spaces, etc. 7. Consume a Web Service or WSRP Standards based integration, WSRP 2.0* 8. Build Composite Applications, eForms & Business Processes Click to Action (C2A)*, Cooperative portlets, HATS, App templates, Process Portal, Lotus Forms 9. Develop Custom Portlets Portlet Factory, RAD, (Java, JSPs, Web Services, REST*, AJAX*, JSR 286*) Run .net apps as Java apps (Mainsoft™) 10. Extend the Browser Utilize rich/remote/mobile clients, e.g. Expeditor, Citrix® portlets, Mobile Portal *New for 6.1
- 17. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Portlets Provided with WebSphere Portal 6.1 ● Mail / PIM Solutions - Lotus Notes®, Exchange, IMAP/POP3 ● Web Apps Integration: Bookmarks, Banner, Quicklinks, Webpage, Web Clipper, Really Simple Syndication (RSS), File Server, Java Server Page (JSP) Server, Servlet Invoker, Web Services (producer and consumer) ● Personal Organization: Reminder, PDF Document Viewer, World Clock, My SQL Query Reports, Retirement Planner, Currency Calculator, My ToDo’s, Comma Separated Values (CSV) file viewer ● News and Information: Events, News, Links, My Weather, My Vertical News, My Stock, Company Tracker. ● Administration Portlets – Site Management, Manage Pages, Manage Portlets, Themes and Skins, Web Services, Manage Search, Web Content Libraries, Syndication, Virtual Portal manager, etc. ● Collaboration: Lotus Instant Messaging Contact List, Who Is Here, People Finder, My Team Workplaces, Web Conferencing, Domino Web Access, Domino Document Manager, NotesView, Notes Mail, Calendar, Tasks, ToDo, Discussion, Teamroom ● Utility Portlets: Login, Profile Management, About WebSphere Portal, Directory Search, Search Center, Instant Messaging connect ● Search: Document Search, Search Center, Suggested Links ● Content Integration: Web Content Management, Productivity Components, converters and viewers ● Business Process Integration: My Tasks and process portlets ● Sample Portlet Applications: Basic, Struts framework, cooperative portlets
- 18. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview IBM Provides Collaborative Capabilities Contact Information, Skills, Expertise Communities, Discussions Blogs/Wikis Shared Documents Shared Bookmarking Activites/ Project Management Instant Messaging, Web Conferencing E-mail, Calendar, Contacts Scorecards, Business Intelligence Telephony, Video, VOIP Documents, Presentations, Spreadsheets Composite Applications Business Mashups Electronic forms In Context Of How People Work
- 19. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview WebSphere Portal 6.1 and Web 2.0 ● Social Features Social Software with Lotus Connections Blogs and Wikis, and forums in Quickr™ User Contribution to portal sites through WCM Situational Development through the Portlet Palette, Drag and Drop page composition, Click-2-Action, Property Broker and Composite Application Templates ● Technical Features Support for AJAX Portlets Portlet Factory builder, RAD tooling, DOJO, AJAX Proxy, Samples,… Exploits AJAX for context menus, search menu, and more Provides REST services for browser side programming Client Side Aggregation improves user experience Semantic tags and Microformats support Smart Markup Provides and consumes ATOM Feeds
- 20. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Easily Deploy Content -- Web Content Management 6.1 ● Inline Editing for easy authoring ● User-friendly, simple templates for entering content ● Full text, attribute and taxonomy search ● Simplified process for including personalization rules in content & layout ● Views allow users to find their content easily ● User interface can be customized easily to provide tailored experience ● Link and Image Management
- 21. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Creating the personal touch you need Many ways to make a personalized site Profile Drives my look and feel by login Customization Allows the user to change their own interface. Personalization Drives a custom user experience at all levels based upon personal or other attributes
- 22. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Advanced Personalization ● Administrators can apply “Personalization rules” to both portlets and portal pages Use of Business logic to provide “dynamic” experience E.g. Show HR Benefits Page during enrollment period ● Personalization Engine in Portal used for: Client-tailored content Site Management (visibility rule) System Policies Custom Applications ● Personalization rules dialog is accessed in context
- 23. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Build Composite Applications ● Easily create new composite applications ● Deploy them to different communities with different… Look and feel, Parameters Members and Roles ● Application owners can then change it to meet new requirements
- 24. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Cooperative Portlets ● Regulated by the Property Broker ● Easily enable portlets to communicate using a Click-to-Action (C2A) menu or Portlet Wires
- 25. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Business Process Integration ● Having good business processes is not enough ● Efficient execution is becoming a key factor of success Provide access to everybody – employees, customers, suppliers Present the staff tasks to the right people at the right time Automatic fail-over for approvals
- 26. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Tooling for Portal Development ● WebSphere Portlet Factory One Designer license included with WebSphere Portal Eclipse tool using reusable components ● Rational Application Developer An open, comprehensive development environment for building e-business applications Portal Tools are fully integrated to support portal and portlet development Version 7.5 works with Portal 6.1
- 27. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview WebSphere Everyplace Mobile Portal Enable (WEMPE) Platform for device independent apps that operate in connected mode ● Lower development/maintenance cost through device independent XDIME markup - ‘Write once, render many’ ● Increased reach/target audience through content on a variety of channels – PDAs, Smartphones, Laptops, Desktops ● Reduced time to market and more revenue through device database with over 5000 preconfigured device profiles and automatic device update service ● Lower administration/integration cost through integration with WebSphere Portal WebSphere Portal based
- 28. © 2008 IBMCorporation TechWorks Discovering the value of IBM WebSphere Portal V6.1 - Portal Technical Overview Portal Single Sign On (SSO) Basic Authentication User Registry Domino EIS Application Back-end Systems Access to Domino External Security Managers HTTP WAS Portal HTTP WAS Portal HTTP WAS Portal WAS Portal HTTP HTTP TAI LTPA ● WAS = WebSphere Application Server ● TAI = Trust Association Interceptor ● LTPA = Lightweight Third-Party Authentication
Editor's Notes
- #3 Portal PoT Instructor Notes This chart is not designed to show any specific customer network configuration, just certain elements that may be contained in any network configuration. The network configuration is also key in developing a security implementation. Anyone who is familiar developing a web application architecture will not see many differences between a portal architecture and a web architecture. DMZ – most e-business customers implement a DMZ which is a semi-protected area between two or more firewalls. A firewall utilizes a combination of hardware and software to enforce security rules that determine what information is allowed to pass into your network. It creates boundaries between two or more networks and stands as a shield against unwanted penetrations into your environment. A load balancer such as Edge Server may be present to balance out demand during peak periods. A reverse proxy such as WebSEAL may be present to do early authentication. Web Servers are usually in DMZ but may also be behind the DMZ. Portal – This tier contains the WAS and Portal servers including the Portal user repository. The LDAP server may also be at this tier if there is not a separate Security tier containing an External Security Manager (ESM) such as Tivoli Access Manager (TAM). Security – This tier is present when the customer implements a ESM. The LDAP used by ESM for authentication must also be available to Portal as the user registry. Content – This tier may be available to support one or more content managers (CM) such as DB2 CM or Web CM. Other popular CMs are supported with portlets that can extract content generated by the CM. Collaboration – This tier may be available to support collaboration between users such as Lotus Collaboration Center. Backend – This tier is almost always present. It represents access to the systems the customer has invested in to actually run the business. It may consist of Enterprise Resource Planning (ERP) systems such as SAP or PeopleSoft, Enterprise Information Systems (EIS) such as CICS or IMS, Enterprise Data Systems such as DB2 or Oracle.
- #8 NEW API/ SPI Click to Action for every Portlet (API) Enable the Click-to-Action paradigm for standards portlets (using Semantic Tags), Integrated with server side eventing Portal Write Model (Java SPI and REST Service) Create your own administration portlets (supports: Content-, Navigation-, Layout- and Portlet-Model, Unique names) Client-side JavaScript library (API) Convenience JavaScript APIs simplifying portlet development (e.g. support authentication proxies) Step-up Authentication (SPI) Define your own authentication levels (beyond what Portal 6.1 provides OOB), check for the rememberMe cookie Login/logout/session validation Filters Plug into the login/logout/session validation flow of portal Property broker (SPI) Write your own wiring portlet Extend current portlet and portal models to support JSR 286 (SPI) All APIs/SPIs available to JSR286 Portlets Sitemanagment command (SPI) Write your own Sitemanagement application Encoding and decoding of friendly URLs (SPI) Create friendly URLs and decode friendly URLs, Integrates into the resource addressability framework Resource Addressability Data Source API (SPI) Serve your resource addressable data via the default content handler servlet LocalizedContext (API) Allows you to get the preferred locales and titles / descriptions of Localized resources Portal Frameworks – Supported by IBM Tooling Java Server Faces (JSF) 1.1 JavaEE standard Rational Application Developer (RAD) V7.0 Struts 1.1 IBM Struts Portlet Framework Supports JSR 168 property broker extension Rational Application Developer (RAD) V7.0 Portlet Factory Build portlets based on models and builders instead of fine-grained UI components Running on WebSphere Portal * JSF V 1.2 Apache JSF Portlet Bridge JSR 301 RI: Standard JSF-Portlet Bridge covering JSR 168 (JSF 1.2), JSR 286 (JSF 1.2), RI part of Apache JSF Bridge Apache Struts Portlet Bridge (V 1.x, V 2.0) Spring MVC 2.0 Adobe Flex Apache Wicket And many more ... The portlet bridge of the framework just needs to comply to either JSR 168 or 286
- #10 Portal PoT Instructor Notes There is a specific series of steps that are required as part of the Page Aggregation Process. Step 1, getting user, language and device type do not often change therefore can be cached. Step 2, This step must be processed when a user selects a new page. Remember that pages and portlets are separate resources types, therefore access to a page does not automatically mean you have access to the portlets on that page. Step 3, All of the markup fragments are collected that will be used to build the page. Step 4, All of the processing by a portlet is done on this step. This is sometimes referred to as the event phase. All events and actions must be completed in this step before the portlet can be rendered. Step 5, Since all events and actions have completed, each portlet can render content in parallel for faster processing. The parallel rendering uses Asynch Beans from Enterprise to render each portlet on a separate thread. Parallel rendering is set for the Portal as well as for the Portlet. The default for the Portal is parallel while a portlet must specify that it will support parallel rendering, it is not automatically set.
- #11 Think of each portlet skin as being an AJAX-enabled wrapper that calls back to the portal to get the embedded portlet's content. The server builds the code for the skin that contains and HTTP reference back to the portlet, embedded within an AJAX javascript call, and the browser invokes that.
- #13 Note that WAS supports only one realm. For multiple realms it must be configured in Portal. * Default Portal Install (federated, file based)
- #14 VMM replaces the WebSphere Member Manager (WMM) that came with WebSphere Portal prior to release V6.1 Using a file for the user registry ootb makes it easier for a development (or POC) environment VMM documentation available at http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wim.doc.en/welcome.html VMM API is based on Service Data Objects (SDO) Comprehensive VMM coding samples available at http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wim.doc.en/integratingwim.html Sample VMM adapter available from the WebSphere Application Server V6.1 Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rwim_dev_vmmca.html
- #16 New infrastructure supports Web 2.0 theme More responsive user interfaces provide better context awareness for the user through client-side aggregation of portal pages. Client-side mashups and interactive portal applications can be developed using Asynchronous JavaScript and XML (AJAX) with a Dojo-based client-side JavaScript programming model. Portal models like Navigation, Page Layout, and User information are remotely accessible through REST Services. Improved scalability results from enhanced caching capabilities. Page fragments can be cached separately rather than caching entire pages. Dynamic behaviors such as context menus, annotations, highlighting, and drag-and-drop interaction can be applied by an extensible set of semantic tags. The new Feedreader portlet is based on AJAX.
- #17 This slide lists all the ways that pages, applications and content can be put into Portal. Listed generally from easiest (least codig) to most. For this presentation we are focusing on new features in Portal 6.1, so existing methods for adding content, such as Web Clipping, should be briefly covered on this page, since they will not be addressed further in this presentation. Web Application Integrator was actually introduced with Portal V6.0.1.2 Displaying Existing HTML/Web Apps does includes SSO and common navigation, truly making that content a “part of portal” Reuse is fundamental for Portal TCO “Time to Value” is a key design goal for WebSphere Portal Composite Applications enhance functionality
- #18 Note tha Portlets can be administrative, e.g., “Manage Pages” and functional, e.g., “WSRP Proxy”, as well as user-oriented
- #20 REST Services open up portal for mashup applications – services for server persistence, portlet settings and user profile access to simplify Web 2.0 application development AJAX Portlet Programming Model Extensions based on Dojo + IBM Extensions Client Side Aggregation and Customization using REST Services for better UX and improved performance AJAX Client Side Feed Consumption to enable highly efficient integration of information through feeds (Atom and RSS) Semantic Tags to allow smart markup to enable value add by portal, e.g. dynamic menus Client Side C2A/Property Broker and Drag & Drop based on Semantic Tags integrated with server side property broker and C2A support to enable cross-portlet interaction locally in the browser as well as with server side code Sample AJAX Portlets with source exploiting the new capabilities to demonstrate and give samples are providing a jumpstart for you. Quickly connect to an author or an expert as a way to add more depth to an interaction in context to a Portal-enabled task/process; facilitates knowledge sharing and innovation Advanced profiles within a Portal enable an entirely new method to facilitate expertise location Communities are a good way to understand who else is a resource and has shared interests. Dogear is a new a way to add depth to Portal content and applications Read an article, see the dogears from the author and learn more Blogs are a simple and easy way to share expertise in context with more formalized documents or application Activities are a simple and fast way to get a project up and running. You can add them into a Composite Application or use it as a simple to do list mechanism
- #21 WWCM 6.1 starts by adding a new user friendly “Welcome Page” entry point for content authors, editors and managers. This new design provides a simplified authoring environment with access to templates, search, libraries, personalization, task bar and help information. We will delve deeper into WCM later today.
- #23 Advanced Personalization extends on the traditional strength of personalization by allowing personalization rules to apply to both portlets and applications. This allows for a more dynamic user experience, wherein the business logic within a personalization rule could, for example, display a particular enrollment application on an HR benefits page during open enrollment. Personalization rules can now also be edited in context with the related applications and pages. All of which provides for added business value, allowing business users to map the current needs of the business to the portal.
- #24 Portal Application Templates allow for easy creation of composite applications that can then be more easily deployed to different communities (e.g. departments, teams, other groups of users). Since such factors as ‘look and feel’, members and roles, as well as other definable parameters, are externalized via the templates, application owners can more easily change their applications to meet new requirements.
- #25 Deprecated the Portal Event Declaration Builder and Click to Action Builders—replaced by microformats. Can still use simple Event Declaration for communication between Portlet Factory portlets. Prior to WPF 6.0 Cooperative Portlet support was limited to Click-2-Action (C2A) events through the use of the C2A Builders. The C2A Builder set did not allow support for use with the WebSphere Portal Wiring tool. Events could be triggered by selecting the target from the C2A menu, but you could not have the action selection from the menu saved persistently. The new cooperative portlets support in WPS 6.0 primarily addresses the following two enhancements. Allow Click-2-Action portlets to be wired (only supported on IBM Portlet API not JSR 168) - Depending on the browser, a user can hold either CTRL or ALT while clicking a Click-to-Action icon action and chooses to have the action selection(s) from the menu saved persistently. This results in the property associated with the icon being wired to the target action(s). If a wire is present the next time the user clicks on the icon, no selection menu is shown. Instead the wired action(s) are automatically fired. Subsequent updates to that property are transferred without further deliberate user choice. Wires can also be created using the Portlet Wiring Tool. Enable Property Broker events in JSR-168 (WebSphere Portal JSR 168 API only – not supported on IBM Portlet API) - At runtime, the property broker matches the data type of output properties from a source portlet with the data type of input properties from one or more target portlets. If a match is determined, the portlets are capable of sharing the property. JSR-168 Portlets must be configured using the Portlet Wiring Tool in order to enable Property Broker events. The new Builder functionality allows you to trigger the event through a page link, or method action.
- #26 Workflow capabilities in your portal run off Process Server and BPEL engine. Allow us to define forward running business processes with many forks and joins. The user interaction interface can then be exposed through websphere portal. Additionally portal can keep track of where you are in the business process and what tasks need your attention.
- #27 Portal PoT Instructor Notes Point out that tools are needed to create portlets and there are several tools available. Only RAD is shipped with the Portal package. Bowstreet is sometimes shipped it depends on if we are running some sort of “deal”
- #29 Portal PoT Instructor Notes Before you decide to implement a SSO solution you need to understand that shared desktops will need to address security issues. Someone may not log out of their workstation and then the person that “shares” the workstation will have access to all applications that were provided through SSO. The definition of single sign-on (SSO) is that if a user has successfully authenticated once in the Single Sign On domain, then that user is not required to present his/her authentication information again. The established credentials are used to automatically authenticate them to the applications participating in the single sign-on domain. The SSO solution with External Security Managers such as Tivoli/Siteminder/etc will only work with the scheme level (security level) for Portal and the back end applications is the same and that they are all on the same domain. If they aren't then the Credential Vault solution will be needed. Many portals are required to access external applications that need some form of user authentication. In most cases, the user credentials required by these applications will differ from those used by WebSphere Portal. While it is possible for the portlet to prompt the user for this credential information and then present it to the external Application, such an approach is seldom implemented due to the unsatisfactory user experience. Hence the requirement for SSO in a Portal solution is to provide seamless access to the different applications. There are multiple approaches to SSO, this chart just covers some the ones commonly implemented in Portal. Use this chart to briefly introduce each approach, there is a separate chart that covers each approach in more detail. As an aside, shared desktops may have security concerns with SSO as a pure solution could allow users to accidentally access unauthorized resources.