| View: | [ 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 ] |
| Articles Presentations | Tutorials |
- Consumer self-service, Part 1: Help customers help themselves by providing services on the Web by Sharon Lymer - [Clicks: 50]
In today's electronic world, businesses often achieve customer loyalty by providing quality services on the Web and enabling customers to use those services without ever waiting for, or requiring help from, a human. This article describes the business requirements that lead to the adoption of a consumer self-service solution. It covers the business context, key business scenarios, roles involved in a consumer self-service solution, and a high-level overview of the architecture for building such a solution.
http://www-106.ibm.com/developerworks/library/i-selfserv1/ - Dec, 2003 - Consumer self-service, Part 2: Build a secure portal by Sharon Lymer - [Clicks: 61]
A typical consumer self-service solution uses a single point of access to a business through a Web-based portal. Naturally, consumers need to feel confident that the information and self-service features provided by the portal are secure. However, Web-based technologies are susceptible to security threats. A secure portal application providing centralized security management for authentication, authorization, and auditing is described in this article and an accompanying Redbook.
http://www-106.ibm.com/developerworks/ibm/library/i-selfserv2/ - Dec, 2003 - The Path to Portlet Interoperability by John Edwards - [Clicks: 96]
Easy, pain-free application integration tops the wish list of just about any organization engaged in enterprise portal projects. Hampered by proprietary APIs that impose reliance on a single portal platform, many developers find themselves forced to re-create the same portlet for different portal products. Relief is on the way, however, in the form of two new standards: Java Specification Request 168 (JSR 168) and Web Services for Remote Portlets (WSRP). Together, they promise to enable the development of portlets that work with various portal offerings.
http://otn.oracle.com/oramag/oracle/03-nov/o63tech_industry.html - Nov, 2003 - Introducing the Portlet Specification, Part 2 by Stefan Hepper, Stephan Hesmer - [Clicks: 151]
In this second and final article in Stefan Hepper and Stephan Hesmer's portlet series, the authors move beyond the Portlet API basics outlined in Part 1 to detail the API's reference implementation (RI), known as Pluto. They also offer a series of example portlets to illustrate how you can extend the API's standard functions.
[Includes source code]
http://www.javaworld.com/javaworld/jw-09-2003/jw-0905-portlet2.html - Sep, 2003 - Introducing the Portlet Specification, Part 1 by Stefan Hepper, Stephan Hesmer - [Clicks: 180]
Portlets are Java-based Web components, managed by a portlet container, that process requests and generate dynamic content. Portals use portlets as pluggable user interface components that provide a presentation layer to information systems. The next step, after servlets in Web application programming, portlets enable modular and user-centric Web applications. The goal of JSR (Java Specification Request) 168, the Portlet Specification, is to enable interoperability between portlets and portals. This specification defines the contract between portlet and portlet container, and a set of portlet APIs that address personalization, presentation, and security. The specification also defines how to package portlets in portlet applications. Part 1 of this two-part series describes the Portlet Specification and explains its underlying concepts. In Part 2, the authors explain the specification's reference implementation and show some portlet examples.
http://www.javaworld.com/javaworld/jw-08-2003/jw-0801-portlet.html - Aug, 2003 - Introduction to JSR 168 - The Portlet Specification - [Clicks: 245]
Java Specification Request (JSR) 168 enables interoperability among portlets and portals. This specification defines a set of APIs for portlets and addresses standardization for preferences, user information, portlet requests and responses, deployment packaging, and security.
[Download the sample portlet code. These freestanding code samples illustrate the use of the JSR 168 specification.]
http://developers.sun.com/prodtech/portalserver/reference/techart/jsr168/index.html - Jul, 2003 - Develop Java portlets by Carl Vieregger - [Clicks: 412]
While the public release of a common API for portlets is still a couple of months away, Java developers can use proprietary APIs from corporate portal vendors to experiment with portlet development. In this article, Carl Vieregger introduces SAP's portlet API and provides a detailed example that renders information from a remote database using single sign-on. He also demonstrates how you can run the example portlet within your own development and deployment environment based on SAP's Portal Development Kit.
[Use iViews to render data from a remote database]
http://www.javaworld.com/javaworld/jw-02-2003/jw-0207-iviews.html - Feb, 2003
- Building a Global Web Community with Open Source Java Technology by Matthew Schmidt, Matthew Porter - [Clicks: 46]
We show how the project used open-source technology in nearly every component and also give some insight into the workings of a large open-source project.
[JavaOne 2003 - Multimedia format]
http://servlet.java.sun.com/javaone/resources/content/sf2003/conf/sessions/pdfs/1657.pdf - Jun, 2003 - (PDF - 609 Kb)
- Portal Application Design and Development Guidelines - [Clicks: 422]
This Redpaper is a compilation of various IBM publications combined with the authors experience with large Portal implementations. The intention is to give you an comprehensive overview of Portal design/development concepts and coding guidelines that will ensure successful implementations.
http://publib-b.boulder.ibm.com/Redbooks.nsf/RedpieceAbstracts/redp3829.html?Open - Dec, 2003
