Web services for remote portlets:
WSRP is a web services protocol, which is used to bring together content and interactive web applications from remote sources. WSRP incorporates standards such as XML, SOAP, and WSDL to serve as a foundation, while allowing for the implementation of evolving standards.
A WSDL document is an XML file that contains information about the interface, semantics and other details of a call to a web service. When someone wants to use a service, they request a WSDL document to find out the location of the service, the associated function calls and how to access them. They then use this information in the WSDL to form a Simple Object Access Protocol (SOAP) request and send it via HTTP to the external system endpoint.
Producer: A web service that offers one or more portlets and implements various WSRP interfaces. A producer may offer just one portlet, or may provide a container for deploying and managing several portlets.
Consumer: A web service client that invokes producer-offered WSRP web services and provides an environment for users to interact with portlets offered by one or more producers.
A producer must implement the following WSRP interfaces:
Service Description Interface: Provides metadata of itself and the list of portlets it offers. The Consumer invokes the getServiceDescription operation of this interface to obtain the metadata.
Markup Interface: Generates markup and processes interaction requests. The Consumer invokes the getMarkup operation of this interface to obtain the portlets markup. They then invoke the performBlockingInteraction operation to process users interactions to the Producer.
WS-Security:
By implementing the WS-Security standard, PeopleSoft provides the ability to leverage emerging XML security technologies to address web services security requirements
By providing WS-Security capabilities, you can leverage the standard set of SOAP extensions, that you use when building secure web services, to implement message content integrity and confidentiality. WS-Security provides a way to insert and convey security tokens in SOAP messages.
Following are the terminologies related to this document:
WSRP | Web Services for Remote Portlets: A web services protocol for bringing together content and interactive web applications from remote sources. |
Extensible Markup Language: Describes data and focuses on what data is. XML is designed to structure, store, and send information. | |
Web Service Description Language: A XML language for describing web services; it defines the core language that can be used to describe web services based on what the services offer. | |
Simple Object Access Protocol: An XML-based messaging protocol framework for building and exchanging distributed, structured information in a decentralized and distributed environment. | |
Web Services Security Language: Supports security mechanisms, each using implementation and language-neutral XML formats. They include the use of: · XML signature to provide SOAP message integrity. · Use of XML encryption to provide SOAP message confidentiality. · Attaching and referencing security tokens and associating signatures with security tokens. |
Steps to consume and produce remote portlets:
1. configure the gateway in the configuration page
For consumption:
PeopleTools,àPortalàWSRP ConsumptionàDefine Producers
For production:
PeopleToolsàPortalàWSRP Production
The above provides a basic idea about WSRP. You can go through the cited examples in Oracle site for more indepth understanding. Please find the links for the same below.
· http://www.oracle.com/technology/products/ias/portal/standards.html
· To learn more about building and consuming portlets, refer to the Portal Developer's Guide
· http://portalstandards.oracle.com/portal/page/portal/OracleHostedWSRPPortal/Samples
· http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/wsrp/intro.html
· http://en.wikipedia.org/wiki/Web_Services_for_Remote_Portlets
No comments:
Post a Comment