WSRP administration made easy

    Anyone who has tried to use any WSRP implementation would know how difficult it is to get something working! So here is something simple to appease the famished.

    Sun's Open Source WSRP Project at java.net provides the implementation of the WSRP 1.0 specification and runs on Sun's Open Source Portlet Container. The instructions on the WSRP project site are detailed and are in easy to understand and use steps. Please follow the instructions to get the source, compile and create a distribution. Once you have the distribution, to administer and manage the WSRP Producer and Consumer, two administration portlets are provided with the source, which are built along with the other sources.
    Please ensure that JAVA_HOME is set to jdk 1.5 home as the admin server uses the platform MBean server to register the MBeans required for administration and management of WSRP Producer and Consumer. Follow the below steps to get your administration portlets up and running.

Start the Admin server:

  1. cd <wsrp-directory>/dist/wsrp
  2. Edit config/deployenv.conf file to provide the GLASSFISH_HOME and the data storage directory where the WSRP Producer and Consumer data will be stored. You may have already done this if you have deployed the WSRP Producer and Consumer. If so, then you can skip this step.
  3. cd <wsrp-directory>/dist/wsrp/admin
  4. $JAVA_HOME/bin/rmiregistry 1099 &
  5. $ANT_HOME/bin/ant -f run.xml

This will start the admin server and create a producers.xml file in the data storage directory specified in <wsrp-directory>/dist/wsrp/config/deployenv.conf and also a consumer.xml file containing the default information.

Deploy the Admin portlets: 

  1. Access the Portlet Container Driver at http://<hostname>:<port>/portletcontainerdriver/dt
  2. Click on the Admin tab.
  3. In the Deploy a Portlet section, browse to the directory <wsrp-directory>/dist/wsrp/admin and select the wsrp-producer-portlet.war.
  4. Deploy the portlet.
  5. Similarly browse, select and deploy wsrp-consumer-portlet.war.
  6. Click on the Portlets tab. You should be able to access both the administration portlets, with an entry for SampleProducer in the WSRP Producer Portlet.

Use the Admin Portlets:

  1. Click on the SampleProducer link and update the Producer by selecting the Portlets that you want to be exposed to the Consumers.
  2. Copy the WSDL url of the Producer. Save the Producer.
  3. In the WSRP Consumer Portlet, click on New button.
  4. Provide the WSDL url of the Producer. (Paste the copied url)
  5. Click on Get Info button. This will get the Service Description of the Producer.
  6. Provide the appropriate details. Click on Save.
  7. The newly created Consumer would be visible in a table in the WSRP Consumer Portlet.
  8. Click on the "Create" link in the newly created Consumer row. This is to create a channel.
  9. Select one of the Portlets whose display names are provided in a drop down list (these are the portlets that are made available in the WSRP Producer), and provide the name for the channel.
  10. Click on Save. This will create a new channel for the remote portlet.
  11. Click on the WSRP tab. You will be able to access the remote portlet.


That's all there is to it really. The number of steps may seem to be overwhelming, but it is very easy to follow and will indeed get you up and running very quickly. Try it out and if you have any doubts, concerns, comments or downright criticisms please feel free to let us know at users@wsrp.dev.java.net.

Rock on. :)


 

Comments:

I am in the process of evaluation WSRP project... I am able to deploy the producer and consumer in my local set up. The wsdl url for the Sampleproducer in my pc is http://localhost:8888/producer/wsrp/wsdl/SampleProducer when I Use this url in the browser i am getting the following error The XML page cannot be displayed Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later. -------------------------------------------------------------------------------- The following tags were not closed: wsdl:definitions, wsdl:service. Error processing resource 'http://localhost:8888/produc... Do you have any idea what went wrong here?

Posted by rahul mahapatra on December 11, 2006 at 03:33 AM PST #

Hi Rahul, I have replied to your email to the users mailing list. Basically it is a problem of how the paths have to be set in jvm option on Glassfish on Windows. So the workaround would be to remove the double backslash before the ":" in the value of wsrp.data.dir jvm option in the %GLASSFISH_DOMAIN%\\config\\domain.xml and save it and restart GlassFish. You should be able to access the WSDL. Do let us know if this works properly :) Cheers, Karthik

Posted by Karthik Sudarshan on December 11, 2006 at 03:02 PM PST #

Thanks a lot Karthik!!!! It worked...

Posted by Rahul mahapatra on December 13, 2006 at 01:14 AM PST #

That's great Rahul :) Please let us know if you face any further problems.

Posted by Karthik Sudarshan on December 13, 2006 at 01:46 AM PST #

HELLO

Posted by ASDFASDF on April 20, 2010 at 10:38 PM PDT #

Hi Karthik,

I am also getting the same issue. Please suggest me how to resove the problem.

<The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.

--------------------------------------------------------------------------------

The following tags were not closed: ARCRAXINV, LIST_G_1. Error processing resource 'http://fada1sap72.firstam-reis.net:8002...

;LIST_G_TAX_RATE />
<D_LINE_EXTENDED_AMOUNT>0.00</D_LINE_EXTENDED_AMOUNT>
<D_LINE_UNIT_SELLING_PRICE>0.00</D_LINE_UNIT_SELLING_PRICE>
<LINE_DESCRIPTION>Tax Exempt @</LINE_DESCRIPTION>
<LINE_TAXYN />

Thanks.
Satheesh

Posted by Satheesh on April 20, 2010 at 10:40 PM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

karthiksudarshan

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today