X hits on this document

PDF document

WebSphere Portal Server and - page 12 / 22

62 views

0 shares

0 downloads

0 comments

12 / 22

WebSphere Portal Server and Web Services

UDDI

Portlet Info Portlet Info

Find Portlet

Portlet Info

Publish Portlet

SOAP

SOAP

Portal

Portlet

Remote

Portal

Aggregation

Proxy

RPI/SOAP

Portlet

Aggregation

Figure 11: Finding and binding to remote portlets

When a page that references a remote portlet gets rendered, the portal uses a portlet proxy to invoke the remote portlet web service through the Remote Portlet Invocation (RPI) protocol (see Figure 12). The portlet invokes the portlet proxy exactly like it would invoke a local portlet, passing PortletRequest and PortletResponse objects. The portlet proxy internally invokes a SOAP proxy to marshals all parameters into a SOAP request and sends it to the remote server hosting the portlet web service. The SOAP wrapper on the web service side unmarshals all information in the incoming request and calls on the remote portlet.

Portal Administration

Portal Administration

Bind Portlet by

adding Portlet Proxy Entry

Invoke Remote Portlet

Portlet Entry

Portlet Registry

Portlet Registry

Portlet Proxy Entry

Portal

Portlet Web Service

Portal

Portlet

SOAP

SOAP

Remote

Servlet

Engine

Portlet

Proxy

Proxy

Soap

Wrapper

Portlet

Servlet

Portlet

Soap

Request

Request

Request

Response

Response

Response

Figure 12: Remote Portlet Invocation (RPI)

For the remote portlet, it is transparent whether it is invoked directly by a portal engine or indirectly through the web service interface. In each case, it processes the input parameters and

returns a PortletResponse object.

12

Document info
Document views62
Page views62
Page last viewedSun Dec 11 06:12:50 UTC 2016
Pages22
Paragraphs486
Words6216

Comments