a.
Accessing/generating
service WSDL file in Producer portal
i. Producer portal needs to provide WSRP service WSDL URL to consumer
, generally URL will be like
For my local
Or
<wsdl:definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:v1bind="urn:oasis:names:tc:wsrp:v1:bind" xmlns:v2bind="urn:oasis:names:tc:wsrp:v2:bind"xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="http://www.ibm.com/xmlns/prod/websphere/portal/wsrp/wsdl">
<import namespace="urn:oasis:names:tc:wsrp:v2:bind" location="wsrp-2.0-bindings.wsdl"/>
<import namespace="urn:oasis:names:tc:wsrp:v1:bind" location="wsrp_v1_bindings.wsdl"/>
<wsdl:service name="WSRPService">
<wsdl:port binding="v1bind:WSRP_v1_Markup_Binding_SOAP" name="WSRPBaseService">
<soap:address location="http://sivapc.sivavaka.com:10057/wsrp/WSRPBaseService"/>
</wsdl:port>
<wsdl:port binding="v1bind:WSRP_v1_ServiceDescription_Binding_SOAP" name="WSRPServiceDescriptionService">
<soap:address location="http://sivapc.sivavaka.com:10057/wsrp/WSRPServiceDescriptionService"/>
</wsdl:port>
<wsdl:port binding="v1bind:WSRP_v1_PortletManagement_Binding_SOAP" name="WSRPPortletManagementService">
<soap:address location="http://sivapc.sivavaka.com:10057/wsrp/WSRPPortletManagementService"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="WSRPService_v2">
<wsdl:port binding="v2bind:WSRP_v2_Markup_Binding_SOAP" name="WSRPBaseService">
<soap:address location="http://sivapc.sivavaka.com:10057/wsrp/WSRPBaseService_v2"/>
</wsdl:port>
<wsdl:port binding="v2bind:WSRP_v2_ServiceDescription_Binding_SOAP" name="WSRPServiceDescriptionService">
<soap:address location="http://sivapc.sivavaka.com:10057/wsrp/WSRPServiceDescriptionService_v2"/>
</wsdl:port>
<wsdl:port binding="v2bind:WSRP_v2_PortletManagement_Binding_SOAP" name="WSRPPortletManagementService">
<soap:address location="http://sivapc.sivavaka.com:10057/wsrp/WSRPPortletManagementService_v2"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
ii.
WSRP1.0 vs WSRP2.0
1.
WP7 and above supports both
WSRP version 1.0 and 2.0
2.
JSR168/IBM Portlets
supports both WSRP 1.0/ 2.0
3.
JSR286 portlets supports
WSRP 2.0
iii.
You can change this WSDL
file settings using different ways as below and it uses the fallback approach
1.
url parameters
2.
Settings in the portal Config Service
3.
Values from the incoming
request
a.
Configuring the security
i. Configure security using the WS-Security (webservice security) :
This requires to update and re-pacakage the wps war file.
ii. Configure security using the SSL client certificate :
iii. Disable the security (You can't use the portal access control
settings) : By default Portal Access Control is enabled for the Producer
portal. If you want to disable Portal Access Control when using WSRP with
WebSphere Portal, deactivate the WSRP security by setting the portal
configuration parameter wsrp.security.enabled in the portal Config Service to
false. With this setting all portlets that your Producer portal provides can
be accessed through the WSRP protocol without any authentication.
b.
Producer checklist for
exchanging the information between consumer.
i. The WSDL document that contains the WSRP service description of
the Producer.
ii. security information (if producer portal has security setup done)
- user registry information. The
Consumer needs this in most cases if the Producer has configured
security by using WS-Security token forwarding.
- SSL server certificate.The
Consumer needs this if the Producer portal has security set up with SSL
client certificate authentication.
iii. Registration information. The Consumer needs this if the Producer
requires registration.
iv. Group IDs and handles of portlets. The Consumer needs these if the
Consumer administrator consumes a WSRP service from a Producer portal by using
the XML configuration interface.
The portlet handle and group ID are listed in the service
description of the Producer. The portlet handle for each portlet that the
Producer provides is listed in a portletHandle tag. The group ID for each
portlet that the Producer provides is listed in the groupID tag of the service
description.
c.
Providing Portlets
(providing WSRP services as producer) :
i. To provide or withdraw a portlet for WSRP services, you can use
either of the following options:
- Using Manage Portlets.
b.
Withdraw portlet
2.
Using XML configuration
interface, more
details on this can found in info center (refer the links in references
section)
NOTE
i. When a Producer provides a portlet, the portlet itself is
provided, not an instance of it. Therefore only settings made in the Configure
mode of the portlet are available at the consumed remote portlet. Adding a
remote portlet to a page on the Consumer side creates a new instance of the
provided portlet on the Producer side. But this instance can only be modified
on the Consumer and is not visible on the Producer portal.
ii. Customization of the Producer portlets by Consumer portal users
can be exported by using the XML configuration interface.
iii. The current implementation of the WSRP Producer in the portal does
not support the WSRP registration interface
iv. you cannot use the Web Services Configuration portlet to perform
the following tasks:
- Provide Web services: To provide
your portlets and make them available to other portals as remote Web
services, use the Manage Portlets portlet.
- Consume Web services: To
integrate Web services provided by a Producer as remote portlets in your
portal, use the Manage Web Modules portlet.
References
a.
Customizing the WSRP
configuration of your Producer portal
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg){kind=link}