Unable to Consume Remote Portlet

[vinuneelu]

Hi,

I am a new user in JBoss. I have installed JBoss Portal Server 2.6.2 integrated with JBoss App Server 4.2.1. I am trying its WSRP services.
I tried to access a Remote portlet from Webspere portal Sever. But I got an error like this.

" The Producer environment has timed out. The Consumer needs to invoke initCookie() again "

Both mine and Remote OS is WindowsXP.

It would be great if anybody can help me to know I can configure my consumer so that it can invoke Producer's initCookie() method.

Thank You
Vinu

[claprun]

Could you provide more details as to what you are doing that is causing the problem? Your consumer shouldn't have to require any specific configuration to invoke initCookie. Could you send the service description sent by Websphere portal, please?

[vinuneelu]

Hi Chris,
I am very sorry for the late reply since I was on a new assignment.

here are the service descriptions I used.

http://10.114.110.85:10038/wps/WSRPServiceDescriptionService

http://10.114.110.85:10038/wps/WSRPBaseService

http://10.114.110.85:10038/wps/WSRPRegistrationService

http://10.114.110.85:10038/wps/WSRPPortletManagementService

With these descriptors, I am getting the erros...

Thank You
Vinu

[claprun]

Can you attach the WSRP service description as returned by the producer?

[vinuneelu]

Hi Chris,
I am sending the service description sent by the Websphere Portal.

<?xml version="1.0" encoding="UTF-8" ?>
<wsdl:definitions targetNamespace="urn:oasis:names:tc:wsrp:v1:wsdl"
xmlns:bind="urn:oasis:names:tc:wsrp:v1:bind"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">

<wsdl:service name="WSRPService">
<wsdl:port binding="bind:WSRP_v1_Markup_Binding_SOAP"
name="WSRPBaseService">
<soap:address
location="http://10.114.110.85:10038/wsrp/WSRPBaseService" />
</wsdl:port>
<wsdl:port binding="bind:WSRP_v1_ServiceDescription_Binding_SOAP"
name="WSRPServiceDescriptionService">
<soap:address
location="http://10.114.110.85:10038/wsrp/WSRPServiceDescriptionService" />
</wsdl:port>
<wsdl:port binding="bind:WSRP_v1_PortletManagement_Binding_SOAP" name="WSRPPortletManagementService">
<soap:address location="http://10.114.110.85:10038/wsrp/WSRPPortletManagementService" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>


Thank You
Vinu.

[claprun]

This is not the service description sent by the producer (well it kind of is, but not in the WSRP sense). What I need to see is the result of a WSRP call to getServiceDescription...

[vinuneelu]

Sorry Chris, I didnt get u actually. Did u mean the error message I get after trying the WSRP Service to get the Remote Portlet?

[claprun]

The error could indeed be useful but this is not what I am asking for. getServiceDescription is one of the first messages that a consumer would send to a producer to learn about its capabilities. I would need to see the response to that request to see what Websphere sends...
I would suggest that you read the WSRP specification for more details.

[vinuneelu]

Hi Chris,
I found one wsdl file named "wsrp_v1_bindings.wsdl" in Webspere Portal.
Inside that there is one entry for getServiceDescription. Could you please tell me whether you meant this description?

<wsdl:binding name="WSRP_v1_ServiceDescription_Binding_SOAP" type="intf:WSRP_v1_ServiceDescription_PortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>

<wsdl:operation name="getServiceDescription">
<soap:operation soapAction="urn:oasis:names:tc:wsrp:v1:getServiceDescription"/>
<wsdl:input name="getServiceDescription">
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output name="getServiceDescriptionResponse">
<soap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="InvalidRegistration">
<soap:fault name="InvalidRegistration" use="literal"/>
</wsdl:fault>
<wsdl:fault name="OperationFailed">
<soap:fault name="OperationFailed" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>

[claprun]

"vinuneelu" wrote:
Hi Chris,
I found one wsdl file named "wsrp_v1_bindings.wsdl" in Webspere Portal.
Inside that there is one entry for getServiceDescription. Could you please tell me whether you meant this description?

<wsdl:binding name="WSRP_v1_ServiceDescription_Binding_SOAP" type="intf:WSRP_v1_ServiceDescription_PortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>

<wsdl:operation name="getServiceDescription">
<soap:operation soapAction="urn:oasis:names:tc:wsrp:v1:getServiceDescription"/>
<wsdl:input name="getServiceDescription">
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output name="getServiceDescriptionResponse">
<soap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="InvalidRegistration">
<soap:fault name="InvalidRegistration" use="literal"/>
</wsdl:fault>
<wsdl:fault name="OperationFailed">
<soap:fault name="OperationFailed" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>

This is the web service description of the web service operation. What I'd like to see is the result of calling this operation. This won't be a static file that you can find, but rather the SOAP response to a call to that getServiceDescription operation.
You might want to consider getting professional support from us, as it would help you solve your issue and get up to speed faster.

[vinuneelu]

We are facing some problems while working on the WSRP in the JBoss 2.6.2 GA+ Application Server 4.2.1

We are referring to the manual at the location :

http://docs.jboss.com/jbportal/v2.6.2/referenceGuide/pdf/JBossPortalreferenceGuide.pdf which specifies in detail about working on the WSRP in JBoss.


IBM Websphere portal server is able to consume the JBoss portlet but not the other way round. We have followed the below steps and the errors which we get for each step are mentioned in detailed below -

1) When we create a xml file named as websphere-wsrp.xml and put in the server/default/deploy directory we get the following error in the console -

cannot access the imported wsdl http://www.w3.org/2001/xml.xsd connection timed out: connect
There was a problem initializing the WSRP interface for producer "websphere". The cosumer will not be available.

2) We have then added the following content to the default-wsrp.xml and put the default-wsrp.xml in the server/default/deploy directory



<wsrp-producer id="WebSphere" expiration-cache="120">
<endpoint-wsdl-url>http://localhost:10038/wps/wsdl/wsrp_service.wsdl</endpoint-wsdl-url>
<registration-data/>
</wsrp-producer>


We get the following message in the console :
Added consumer for producer "websphere" with status :inactive.

3)Login to the Portal Server/admin/WSRP

4)We are able to see the websphere as a consumer added in the consumers list.

5)We are then clicking on configure to configure. & then "Save&Refresh" . We get the following error -

java.lang.RuntimeException: java.lang.RuntimeException: Couldn't initialize services for WSDL at 'http://localhost:10038/wps/wsdl/wsrp_service.wsdl' Cause: java.lang.RuntimeException: Couldn't initialize services for WSDL at 'http://localhost:10038/wps/wsdl/wsrp_service.wsdl'


6) We then modified the entry in the default-wsrp.xml for the websphere producer as follows -

<endpoint-config>
<service-description-url>http://localhost:10038/wps/WSRPServiceDescriptionService</service-description-url>
<markup-url>http://localhost:10038/wps/WSRPMarkupService</markup-url>
<portlet-management-url>http://localhost:10038/portal-wsrp/PortletManagementService</portlet-management-url>
</endpoint-config>

We get the following error again when we click on Save&Refresh in the portal.

java.lang.RuntimeException: java.lang.RuntimeException: Couldn't initialize services for WSDL at 'http://localhost:10038/wps/wsdl/wsrp_service.wsdl' Cause: java.lang.RuntimeException: Couldn't initialize services for WSDL at 'http://localhost:10038/wps/wsdl/wsrp_service.wsdl'

Kindly help us out at the earliest.

Best Regards
Vinu

[claprun]

"vinuneelu" wrote:

1) When we create a xml file named as websphere-wsrp.xml and put in the server/default/deploy directory we get the following error in the console -

cannot access the imported wsdl http://www.w3.org/2001/xml.xsd connection timed out: connect
There was a problem initializing the WSRP interface for producer "websphere". The cosumer will not be available.

Are you behind a firewall? If yes, please look at http://wiki.jboss.org/wiki/Wiki.jsp?page=WSRPOfflineInstructions

"vinuneelu" wrote:

6) We then modified the entry in the default-wsrp.xml for the websphere producer as follows -

<endpoint-config>
<service-description-url>http://localhost:10038/wps/WSRPServiceDescriptionService</service-description-url>
<markup-url>http://localhost:10038/wps/WSRPMarkupService</markup-url>
<portlet-management-url>http://localhost:10038/portal-wsrp/PortletManagementService</portlet-management-url>
</endpoint-config>

If you have already configured a producer with the same name in the admin portlet, the database configuration will take precedence over the XML descriptors... So changes made to the XML configuration won't have any effect.

"vinuneelu" wrote:

java.lang.RuntimeException: java.lang.RuntimeException: Couldn't initialize services for WSDL at 'http://localhost:10038/wps/wsdl/wsrp_service.wsdl' Cause: java.lang.RuntimeException: Couldn't initialize services for WSDL at 'http://localhost:10038/wps/wsdl/wsrp_service.wsdl'

I would need to see the exception stack for this particular exception (this can be found in server.log). However, I believe that this error is due to your network issue as highlighted by 1) above.

"vinuneelu" wrote:

Kindly help us out at the earliest.

This forum is only monitored from time to time, and we have no obligation to provide support here. If you need more immediate support, please consider buying professional support from us.

[vinuneelu]

As suggested by you, we have done exactly what the link
http://wiki.jboss.org/wiki/Wiki.jsp?page=WSRPOfflineInstructions
specifies to do ie... place the following in the run.conf file in the jbossserver/bin directory.

JAVA_OPTS=-Dhttp.proxyHost=proxy1.wipro.com -Dhttp.proxyPort=8080 -DproxySet=true

But still we get the same problem. Is it that we need to specify the authentication details also for the proxy somewhere ?

Our JBoss Server run behinds the proxy and surely not behind the Firewall.