Portal Component Architecture

1
Portal Component Architecture

• Overview/motivation (Dennis)
• components and reusability and driving motivation
• Grid technolgies and services (Mary)
• Portal Architecture
• What are the choices? (tbd)
• Jetspeed (Marlon)
• GridSphere (Mike R.)
• Genius (Andrea)
• WebSphere (Mary)
• Others (contact folks to contribute .NET, SUN
  ONE)
• Summary/Comparison/futures (tbd)
• Using Portlets
• Overview (Charles)
• Examples/summary of where we are today, discuss
  difficulties
• difficulties encountered (Mike)
• lessons (all/tbd)

2
Portal Component Architecture

• Future Vision
• New paradigms
• Emerging technologies (Charles)
• Application metadata (Tom)
• Exposing interfaces to web services (Andrea)
• Generic interfaces to grid services (Greg)
• Enhancing old paradigms
• Bringing current portlet standards meet grid
  requirements (Mike)
• Deployment (Charles)
• portlet repository (Gregor)
• Security (Jason, Greg)
• Others (Marlon)
• Portal Component Design issues
• Architecture (Charles, others)
• "Design Pattern" (Jason)
• Characteristics of portal components (Dennis

3
Portal Component Architecture

• Appendix A GCEShell capabilities done with
  current Portal architectures
• NCSA Example (Alameda)
• EU Example (GridSphere, Mike)
• Texas example (Mary)
• Michigan Example (Charles)
• MISS Portal (Haupt)
• Others?

4

• Forming a document (community) what is its
  purpose?
• Charter is to describe portals
• A human interface to services on the grid and
  applications
• As currently proposed, it is highly portlet
  focused and user interfaces
• Should we address services and user interface?
• Component exchange is another aspect
• Service vs visible???
• Do not want to compete with other working groups
• These may be user interface components or some
  value added thing (e.g. blast)
• If component, do we need to address CCA? No bcs
  that is just one instance of a component
  architecture

5

• Application manager service and workflow are key
• Want to shop for components to put into a portal
  that are useful to community
• How should we organize these components?
• Web applications support portlets
• Clear separation between architecture or portal
  and what services are useful to portal community
• Need a package spec for these portlets, XML in
  tarball java classes and you have a service
• Standards for packaging and APIs
• Goal make it easy to set up a GCE
• Deployment process local vs remote is more
  complicated

6

• Exposing/exchaning portlet services
• Layered model Visual (portlet) services layer
  interface actual services
• ogsa portal is an interface to a set of services
• What about beans? Is this the answer, NEESGrid
  uses Turbine beans are java classes management
  of life cycle

7
Portal Component Architecture

• Section 0
• Is this a roadmap/consensusor a best practice
  need a future vision for sharing components that
  we can use for building grid portals
• this discussion why are we doing this? What is
  our motivation
• Want to share our work old way need to recode
  want to share web content
• Different from building portlets and definign
  that process
• Could define how to implement into portal, how to
  implement the JSR
• Everything we are building is not a grid service
• Grid service has specific technical definition
• Take advantage of this new architectural
  development it facilitates ability of portal
  developers to share services
• Fact that we are using ogsi/ogsa is not
• for user access to grid services via portlet
  technologies
• Ogsi and other component architectures
• Is web service component architect
• Component model dfn framework that allows
  components to reused
• What are our components? Entities embedded in
  portlets or some other portal technology Chuck
  wants a tarball he can untar and have it work
  whterh it is a bean or some other thing.
• We are coupling the portlet component arch to the
  ogsi and other component/services architectures
• Completes the component picture.
• Define some interface standards
• Web application

8
Section 1

• What are the choices?
• Beans jsp portlets (appears to be a reliable
  model out there)
• Grid community needs to be able to expose grid
  services to the portal/web community this is of
  value to the grid community
• Define a generic way to map wsdl for a grid
  service into a portlet.
• Registry browser portlet

9

• GCE larger than portals
• We should define a standard to express how to
  expose a user interface for the grid community to
  be consumed by both JSP or portlets

10
(No Transcript)
11
(No Transcript)
12
(No Transcript)