X hits on this document

PDF document

WebSphere Portal Server and - page 20 / 22

49 views

0 shares

0 downloads

0 comments

20 / 22

WebSphere Portal Server and Web Services

Content Providers publishing Content through Remote Portlets

Today, most content providers publish their content live on the internet using HTTP or FTP servers or they provide client software that replicates and caches content via proprietary protocols. In each case, integrating content into a portal is a difficult task. While portals will provide some portlets supporting some content sources out of the box, it will be necessary to develop and install additional portlets for the remaining content sources, i.e. the party that sets up the portal needs to spend a lot of money and effort in order to aggregate a rich set of content from different sources. This is not only a bad situation for portal owners but also for content providers as the fact that it is relatively hard to include their content limits business growth of content providers to depend on services capacities.

In order to allow for integration of their content in portals without any programming or service effort, content providers can use WebSphere Portal Server to surface their content as portlets and publish these portlets as remote portlet web services in the public, global UDDI directory. Figure 23 gives an example where a content provider does not only provide raw content for rendering by portals but also easily integratable content portlets.

Weather Portlet Description

UDDI

Stocks Portlet Description

News Portlet Description

Portal

Sports Portlet Description

Weather Portlet Proxy

Stocks Portlet Proxy

News Portlet Proxy

Sports Portlet Proxy

Content Provider's

DB

WPS Installation

DB

for serving

DB

Remote Portlets

DB

SOAP/HTTP

HTTP

Weather Portlet

Stocks Portlet

News Portlet

Sports Portlet

DB

DB

DB

Content Provider's Classic Content Server

DB

Figure 23: WebSphere Portal Server used to publish content through remote portlet web services

In order to provide this value add to customers, the content provider runs a WebSphere Portal Server installation serving remote portlets in addition to the classical content server. Once the content provider has used the publish function provided by WPS to advertise the remote portlet web services in UDDI, administrators of portals who wish to use content from the content provider can simply look up the content provider’s business entry in the UDDI directory and bind to remote portlet web services that provide the desired content. The portlets on the content

20

Document info
Document views49
Page views49
Page last viewedSun Dec 04 12:53:51 UTC 2016
Pages22
Paragraphs486
Words6216

Comments