Portal & InteroperabilityPortal & Interoperability-share ESG Portlets to support EIE through JSR 1/268 & WSRP-share ESG Portlets to support EIE through JSR 1/268 & WSRP

Chaowei Yang, Zhenlong Li, Wenwen LiChaowei Yang, Zhenlong Li, Wenwen Li

Joint Center for Intelligent Spatial ComputingJoint Center for Intelligent Spatial Computing

NASA GIO & College of Science, GMUNASA GIO & College of Science, GMU

Table of ContentsTable of Contents

• NASA GIO & ESIP Partnership• An EIE demo with questions• Introduction to JSR 168/268• Liferay Portal Architecture• EIE/ESG Portal Architecture• Sharing ESG functions inside EIE• Conclusion & Discussion

NASA GIO and ESIP partnershipNASA GIO and ESIP partnership

• Facilitate access to Earth Science Information through Science Information through interoperable approaches.

• Support NASA’s Earth Science Applications Areas and GEOSS societal benefit areas.

• Through Partnership of NASA GIO, NOAA, EPA, ESIP, GMU, UAH, and other organizations, such as IGES.

– Air Quality: DataFed, EPA, NASA ASP AQ, NOAA, etc.– Water Cycle: CREW, NOAA, etc. – Public Health: NASA ASP PH, EPA, EDAC, etc. – …

• Leverage the interoperability prototype of NASA ESG as the backbone to support the ESIP EIE.

An EIE Demo with QuestionsAn EIE Demo with Questions

• How the interface is organized?

• Where does the information come from?

• How was the system organized?

• What was shared among portals?

• How did the portlets shared between ESG & EIE?

JSR168 & 268

JSR 168/268 IntroductionJSR 168/268 Introduction

– A set of APIs for Portal computing addressing the areas of aggregation, personalization, presentation and security to enable interoperability between Portlets and Portals.

– Any portlet that’s developed in compliance to this specification can be easily integrated to other JSR168-compliant portal server.

JSR168 documentation: http://developers.sun.com/portalserver/reference/techart/jsr168/pb_whitepaper.pdf

Role of JSR168 in Portal and Role of JSR168 in Portal and Portlet communicationPortlet communication

Client Portal Web Service Portlet Container Portlet 1 Portlet 2 Portlet 3 Portlet 4

Client Request

Action RequestAction()

render()

Fragment

render()

Fragment

render()

Fragment

render()

Fragment

Fragment

Fragment

Fragment

Fragment

Portal Page

Render Request

Render Request

Render Request

Applications/Services

Access w

rapped Services

JSR 168/268

(Yang et al 2007)

Client Request Handling Sequence DiagramClient Request Handling Sequence Diagram Web Portal Service Container Portlets

1: Discover

2: Establish Relationship

3: Learn Cap & Services4: Establish Relationship

Page request

6: Interactions

7: Destruct of relations

Clients

6: Interactions 6: Interactions

Applications

WSRP JSR 168/268 Fragment Logic (Yang et al 2007)

AdvantagesAdvantages

– Portability

Code written according to the specification will be easier to move to among portal servers.

– Easier Federation

Exposing JSR-168 Portlets via Web Services for Remote Portlets (WSRP) producers is easier when portlets adhere to the JSR-168 specification. WSRP provides a standard to federate portlet content via Web services. JSR-168 and WSRP 1.0 portlet capabilities are tightly coupled. JSR-168 to WSRP portlet bridges utilize JSR-168's URL rewriting APIs.

Liferay Portal Architecture

What is a Portal?What is a Portal?

• A Portal is a site that functions as a point of access to information on the WWW.

• Portals present information from diverse sources in a unified way.

e.g. MSN,Yahoo,EIE,ESG

http://en.wikipedia.org/wiki/Web_portal

What is a Portlet?What is a Portlet?

• A Portlet is a pluggable user interface component that is managed and displayed in a portal.

• Portlets produce fragments of markup code that are aggregated into a Portal page.

http://en.wikipedia.org/wiki/Portlet

What is LiferayPortal ?What is LiferayPortal ?

• LiferayPortal is an open source enterprise portal solution.

• It uses the latest in Java, J2EE, and Web 2 technologies .

• It delivers solutions for enterprises across both public and private sectors.

http://www.liferay.com/web/guest/products/portal

Liferay 4.x.x Portal ArchitectureLiferay 4.x.x Portal Architecture（ （ High Level Overview High Level Overview ））

Users can access the portal from traditional and wireless devices.

Developers can access the portal from the exposed APIs via SOAP, RMI, and custom tunneling classes.

http://wiki.liferay.com/index.php/Liferay_4.x.x_Portal_Architecture

POJO: Plain Old Java Object, which only contains some private parameters and defines "get" and "set" methods for each parameter.

Why use Liferay Portal?Why use Liferay Portal?

• Liferay Portal provides a lot of flexibility and control to customize the user experience of the portal.

• The availability of different ways to manage, use and display CMS content and portlets give limitless possibilities for innovation using Liferay Portal.

http://wiki.liferay.com/index.php

EIE & ESG Arch.

Spatial Web Portal ArchitectureSpatial Web Portal Architecture

• Web Portal Spatial Web Portal (SWP)– Web Portal Architecture

• SWPs– EIE: Earth Information Exchange– ESG: Earth Science Gateway

• Cross-SWPs Sharing

• Graphical User Interface (GUI)

Web Portal Arch.Web Portal Arch.Client GUI

Web Portal Page

Web Page Fragment 1

Web Page Fragment 4

Web Page Fragment 3Web Page Fragment 2

Web Portal Service

Portlet Container

Portlet 2 Portlet n….. Portlet 4 Portlet 3Portlet 1

Internet

Local Access or Remote Access through WSRP

Security and Privacy

Information Dissemination Channels

(Yang et al 2007)

ESG ArchitectureESG ArchitectureDiscovery/Access to NASA components within International

Initiatives

NASA components viewable in 3D/4D

browsers

NASA components used in Partner Agency Decision Support

Systems

KnowledgeBase, EOS Catalogs:

GCMD, ECHO

Models, Sensors, Projects:

EO-1, MAP, PHAirs

Grant RecipientsUCAR, WU,GMU

NASA Components

Mission Data ProductsDAACS: GES, LP, SEDAC

Portal to data, Portal to data, information,knowledge information,knowledge about the Earth Systemsabout the Earth Systems

ProcessingServices

PortrayalServices

CatalogServices

Extensible, open portal architecture

WM

SW

CS

WFS

Cata

log

Earth Science Gateway OG

C In

terfa

ce

s, W

MS

, WC

S, C

ata

l og

, etc

.

EIE ArchitectureEIE Architecture

EIE leverages ESG as a backbone to support the Earth science communities, such as Earth Science Application Areas and GEOSS Societal Benefit Areas.

Cross-SWPs SharingCross-SWPs Sharing

NASA Services

GOS

NGA Portal

NGO Portal

Other Agencies

States

Other Portals

NGO Services

NGA Services

Services from other Agencies

States’ Services

Other Services

ESG

GOS Services

Users

Users

Users

Users

Users

Users

Users

Interoperable Environment

(Yang et al 2007)

ESG-GUIESG-GUI

EIE-GUI EIE-GUI

Sharing of ESG to Support EIE

““IFrame” TAGIFrame” TAG

• “IFrame” TAG is an easy and efficient way to share contents and functions between different Portals.

• It makes it possible to embed another HTML page inside the current page by creating a simple JSP portlet.

Create a JSP portlet in LiferayPortal Create a JSP portlet in LiferayPortal development environmentdevelopment environment

Fragment from portlet.xml• <portlet-name>wesclient</portlet-name> • <display-name>WES Client</display-name> • <portlet-class>com.liferay.portlet.JSPPortlet</portlet-

class>

Fragment from view.jsp• <iframe scrolling=no hspace="0" name="wesclient"

src="http://129.174.65.112/wes/ClientDisplay/client.jsp?height=700 width="100%" ></iframe>

Deploy the “WES Client” portlet into EIEDeploy the “WES Client” portlet into EIE

Select the wesclient.war and then click Deploy.

Select wesclient.war and then click “Deploy”

Add “WESAdd “WES Client” portlet into EIEClient” portlet into EIE

Interoperable Web Service’s ClientInteroperable Web Service’s Client

IE7+ & Firefox

Conclusion & DiscussionConclusion & Discussion1. JSR 168/268 facilitate the sharing of portlets cross portals2. Interoperable Geospatial Web Services are shared from other

resources, such as JPL WMS3. ESG functions are easily integrated to support EIE4. More Interoperability research & developments need to be done,

e.g.• Ontology-based Semantic Search• Quality of Services of different Geospatial Web Services

should be maintained up-to-date• Integration/Federation of different catalogs need to be tested• Performance need to be improved through contemporary IT

advancements5. More EIE portlets need to be populated6. Need help from everyone to participate

ReferencesReferences

• JSR 168/268 docs http://developers.sun.com/portalserver/reference/techart/jsr168/pb_whitepaper.pdf

• Spatial Web Portal paper Yang C., Evans J., Cole M., Alameh N., Marley S., and Bambacus

M., 2007. The Emerging Concepts and Applications of the Spatial Web Portal , PE&RS , 73(6):691-698.

http://www.cisc.gmu.edu/publication/papers/2007/pe-rs-swp.pdf

• Earth Information Exchangehttp://eie.esipfed.org/

• Earth Science Gatewayhttp://esg.gsfc.nasa.gov/

Links & Technical ContactLinks & Technical Contact

EIE: eie.esipfed.orgESG: esg.gsfc.nasa.gov

PhilChaowei Yang

cyang3@gmu.edu703-993-4742 or 301-286-5329