Wsrp portlet discovery

Hello!
I have just installed websynergy-gfv2-linux and started playing with it. I am interested in the WSRP support of the product. Right now, I am trying to do a simple test: I want to use the WSRP portlet discovery mechanism to search for a portlet in a UDDI registry, and then start a WSRP consumer that consumes that remote portlet. The question is: is this operation supported through the admin interface of websynergy? I ask because when I get to the WSRP Consumer Admin interface, I get only the oprion to specify the URL of the producer to which the consumer must connect.
Thanks,
Florin.

Registry support i.e both publishing and discovering is not there in websynergy. There is no plan right now to support it, older portal version esp 6.x had ebxml registry support but this was later dropped.
However if registry server provides users the option to publish and discover artifacts, you can use it. Its just like publishing and discovering any other artifact on a registry server.

Similar Messages

How to show the logged in User's displayName in a custom wsrp portlet

Hi,
I have a custom wsrp portlet added to webcenter space. Within the portlet I need to show the logged in(sso) user's displayName. I have tried using #{webCenterProfile[securityContext.userName].displayName} but its not working. Any pointers would be highly appreciated.
Regards,
Ann

You might want to post that in the [WebCenter Suite - Framework|http://forums.oracle.com/forums/forum.jspa?forumID=354] discussion board.
This area is strictly WebCenter Interaction which is a completely different product than Spaces.

Trouble with WSRP portlets

Problem: at one moment all deployed WSRP portlets was crushes.
The following error shows in portlet window: Error: Could not get markup. The cookie or session is invalid or there is a runtime exception
Remote debugging shows, what portlets really works, but Portal server can't get markup after portlet was executed.
And similar following exceptions I has found in portal's application.log:
06/06/20 15:16:44 portal: DEBUG: active=26 id=91794728298,1 Content Fetcher Caught Dispatcher Exception :
oracle.webdb.utils.PortalExceptionImpl: An error occurred whilst invoking an operation on the Provider
     at oracle.portal.PortalException.<init>(Unknown Source)
     at oracle.webdb.dispatcher.DispatcherException.<init>(Unknown Source)
     at oracle.webdb.wsrp.client.run.WSRPDispatcherException.<init>(Unknown Source)
     at oracle.webdb.wsrp.client.run.WSRPRenderDispatcher.dispatch(Unknown Source)
     at oracle.webdb.wsrp.client.run.WSRPDispatcher.dispatch(Unknown Source)
     at oracle.webdb.wsrp.client.run.WSRPCacheDispatcher.dispatch(Unknown Source)
     at oracle.webdb.wsrp.client.run.WSRPMainDispatcher.dispatch(Unknown Source)
     at oracle.webdb.page.ContentFetcher.run(Unknown Source)
Caused by: java.rmi.RemoteException: Runtime exception; nested exception is:
     XML parsing error: com.sun.xml.rpc.sp.ParseException:1: Document root element is missing
     at com.sun.xml.rpc.client.StreamingSender._handleRuntimeExceptionInSend(StreamingSender.java:269)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:251)
     at oracle.webdb.wsrp.WSRP_v1_Markup_PortType_Stub.getMarkup(WSRP_v1_Markup_PortType_Stub.java:205)
     ... 5 more
Caused by: XML parsing error: com.sun.xml.rpc.sp.ParseException:1: Document root element is missing
     at com.sun.xml.rpc.streaming.XMLReaderImpl.next(XMLReaderImpl.java:110)
     at com.sun.xml.rpc.streaming.XMLReaderBase.nextContent(XMLReaderBase.java:23)
     at com.sun.xml.rpc.streaming.XMLReaderBase.nextElementContent(XMLReaderBase.java:41)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:116)
     ... 6 more
caused by: java.rmi.RemoteException: Runtime exception; nested exception is:
     XML parsing error: com.sun.xml.rpc.sp.ParseException:1: Document root element is missing
     at com.sun.xml.rpc.client.StreamingSender._handleRuntimeExceptionInSend(StreamingSender.java:269)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:251)
     at oracle.webdb.wsrp.WSRP_v1_Markup_PortType_Stub.getMarkup(WSRP_v1_Markup_PortType_Stub.java:205)
     at oracle.webdb.wsrp.client.run.WSRPRenderDispatcher.dispatch(Unknown Source)
     at oracle.webdb.wsrp.client.run.WSRPDispatcher.dispatch(Unknown Source)
     at oracle.webdb.wsrp.client.run.WSRPCacheDispatcher.dispatch(Unknown Source)
     at oracle.webdb.wsrp.client.run.WSRPMainDispatcher.dispatch(Unknown Source)
     at oracle.webdb.page.ContentFetcher.run(Unknown Source)
Caused by: XML parsing error: com.sun.xml.rpc.sp.ParseException:1: Document root element is missing
     at com.sun.xml.rpc.streaming.XMLReaderImpl.next(XMLReaderImpl.java:110)
     at com.sun.xml.rpc.streaming.XMLReaderBase.nextContent(XMLReaderBase.java:23)
     at com.sun.xml.rpc.streaming.XMLReaderBase.nextElementContent(XMLReaderBase.java:41)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:116)
     ... 6 more
Need help to solve this problem.
P.S. Sorry for bad english.
Message was edited by:
Yarrow

Oracle Portal version 10.1.4

Handling large files in scope of WSRP portlets

Hi there,
just wanted to ask if there are any best practices in respect to handling large file upload/download when using WSRP portlets (apart from by-passing WebCenter all-together for these use-cases, that is). We continue to get OutOfMemoryErrors and TimeoutExceptions as soon as the file being transfered becomes larger than a few hundred megabytes. The portlet is happily streaming the file as part of its javax.portlet.ResourceServingPortlet.serveResource(ResourceRequest, ResourceResponse) implementation, so the problem must somehow lie within WebCenter itself.
Thanks in advance,
Chris

Hi Yash,
Check this blogs for the strcuture you are mentioning:
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
Regards,
---Satish

Handle HttpRequest and Responce in WSRP Portlets

Hi all,
I have deployed a fusion ADF application as a WSRP portlet on webcenter portal.
In my portlet application code i want to perform some file handling operations(like open a file in browser) using ADF table components.
I had used Http sevlet request and responce but portlet throws a following exception.
java.lang.ClassCastException: org.apache.myfaces.trinidadinternal.config.dispatch.DispatchResourceResponse cannot be cast to javax.servlet.http.HttpServletResponse
Any one has some idea about how to handle http request and responce in WSRP portlets.

Hi
Portlets don't use HttpServletRequest & HttpServletResponse.
Use instead of them: PortletRequest & PortletResponse
Regards.

WSRP Portlet open new window

Hello allm
I have three wsrp portlets on a page, (Applications navigator, favourites, worklist) and when I click them I get the correct link so they work just fine. MY problem is, clicking any link in a portlet will open that link in the current window, thus loosing the portlet window. Does anyone know how I can force this to open in a new window? It sounds like a simple task but have not been able to find that conig setting just yet..
Thanks in advance.
Grummy

For anyone else that stumbles upon this issue, the resolution is as follows:
Edit the region where the portlet resides
go to Attributes
move 'Link - Display Name' to the 'Displayed Attributes'
Back on the main edit page, click actions on the portlet, edit portlet, and then select display as Link That Displays Portlet In New Browser Window, done.

Can I expose Oracle Reports as a WSRP Portlet

We need to make reports created in Oracle Reports available to other portals, can this be done by exposing the reports as WSRP portlets, if not is there any other way to do this?

I'm trying to determine the best architecture for a (sometimes) disconnected java application. We want to create a java swing application (deployed using java web start) which will enable users to enter data while being disconnected from the network. When they connect, the application should upload all the entered data to a database.
We would like to use bc4j to implement client side business logic (deploy the bc4j classes with the swing user interface through java web start). For this to work, i think we would also have to deploy a small database which bc4j uses untill we have a network connection.

WSRP Portlet deployment

I have a simple WSRP portlet, which I developed in JDev as an ADF app using a Business Object bound to an ADF Form, via JDBC to a remote Oracle 11g database, and portletized using the Portlet Bridge/Wizard.
Everything works fin locally on the Integrated WL server, but when I deploy it to my Weblogic Managed Server, it tries to run, but just hangs perpetually at the twirling O initialization progress indicator.
I've isolated the problem to being related somehow to the database connection, by creating an identical app with the same adf form elements, sans the database binding, and it works fine.
I've double checked that the jdbc connection, which I have depolyed to the same wls target that I'm deploying the portlet to, works and is using the same driver, and that the jndi names match, but am at a loss now as to where else to look to find this apparent disconnect.
Would love to hear from anyone that may have experienced this and found the cause, or anyone who might have any suggestions as to further troubleshooting steps I could take.
Thanks!
Edited by: ray.mccormick on Mar 16, 2012 11:25 AM

Found the solution on Metalink (Note 437789.1) by editing the existing v1 wsdl and creating a dummy one in my deployment file.

WSRP Portlet registration error

Using the Portal Developer's guide, I created a Java/WSRP portlet and deployed it to a portlet_container. I am now trying to register the portlet and receive this error message from the Oracle Portlet Verification portal and my own Oracle Dev. Preview WSRP Portal:
An error occurred when attempting to call the providers register function. (WWC-43134)
An error occured during the call to the WSRP Provider: An error occurred whilst invoking an operation on the Provider
Java stack trace from root exception:
java.rmi.ServerException: Internal Server Error (caught exception while handling request: oracle.webdb.wsrp.server.ContainerRuntimeException: An internal error has occurred in method <init>)
at com.sun.xml.rpc.client.StreamingSender._raiseFault(StreamingSender.java:384)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:245)
at oracle.webdb.wsrp.WSRP_v1_Registration_PortType_Stub.register(WSRP_v1_Registration_PortType_Stub.java:70)
at oracle.webdb.wsrp.client.design.v1.OraWSRP_v1_Registration_PortType.register(OraWSRP_v1_Registration_PortType.java:74)
(WWC-10001363)
Any ideas?
Thank You,
Justin

After using a TCP monitor, I found out that the WSRP was not being contacted at all by the portal upon adding the portlet to the page. In my case, the WSRP was running on port 7778. However, when I changed OC4J listener port to 80 and redeployed all worked well. At this point I am trying to determine if this is a firewall issue or something else.

What is the difference between JSR 168 portlets and WSRP portlets?

What is the difference between JSR 168 portlets and WSRP portlets?

Here is the difference between JSR168 and WSRP:
The WSRP specification does not make any statements as to implemention. Java's portlet specification, JSR 168, and WSRP are not competing technologies. JSR 168 may be used to define a portlet, and WSRP may be used to define a portlet's operations to remote containers. JSR 168 portlets and WSRP may be used together to define a portlet and to provide remote operations. Similarly, .NET portlets may be created for use with WSRP. Interoperability between JSR 168 and .NET WSRP implementations has been demonstrated

WSRP portlets - consumer-side backing files

I'm trying to find a way to send the consumer-side portlet instance label and the desktop definition label into my WSRP portlets. The BEA WSRP documentation indicates that using a backing file is the way to do this. The only problem is that even though creating a backing file and extracting the two strings is straightforward, it isn't clear how to go about communicating the information from the backing file to the WSRP portlets, since the session and request spaces are independent. I could use some recommendations. Thanks in advance.

There is limited support for this in 10.3, in 10.3.2 there are some javascript libraries to help you add parameters to URL.
In 10.3 your best bet is as follows:
Do NOT modify the URL, instead do a POST to your actionUrl and pass in the parameter in the POST body. You, will also need to do use a PortletXMLHttpRequest to avoid getting the entire page returned.
Good luck,
Nate

Passing parameter to a portal page that display a WSRP portlet ?

I have created, deployed and regisered a WSRP portlet to Portal 10.1.4. I also create a portal page used to render this portlet. I would like to pass in a parameter xx (thru the HTTPRequest) when calling this page and have it visible to the portlet inside the page. Something like http://host:port/portal/page/portal/myPortlets/portletA?xx=123 where
"http://host:port/portal/page/portal/myPortlets/portletA" represented my portal page and "xx=123" is what I want my page to see.
Is it even possible/support by Portal 10.1.4 ?
Thanks.
Kim

HI Alejandro,
Did the same what you have told me. I am getting the following error
oracle.jbo.JboException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-29000. Error message parameters are {0=java.io.EOFException, 1=null}
at oracle.adf.model.bc4j.DCJboDataControl.setCurrentRowWithKey(DCJboDataControl.java:1554)
at oracle.adf.model.binding.DCIteratorBinding.setCurrentRowWithKey(DCIteratorBinding.java:3829)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.doIt(JUCtrlActionBinding.java:1588)
at oracle.adf.model.binding.DCDataControl.invokeOperation(DCDataControl.java:2189)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.invoke(JUCtrlActionBinding.java:751)
at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.executeEvent(PageLifecycleImpl.java:407)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding._execute(FacesCtrlActionBinding.java:255)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding.execute(FacesCtrlActionBinding.java:213)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.el.parser.AstValue.invoke(AstValue.java:254)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:302)
Thanks

OutOfMemoryException in WSRP portlet in 10.1.4

We are facing the OutOfMemory exception when recieving a PDF file (10KB) as byte stream from the AXIS Webservice client, inside the WSRP portlet.
Portlet log simply states OutOfMemory and no stacktrace is available.
Surprisingly, if the webservice returns String of the same PDF instead of the byte array, it works. Any idea how overcome the OutOfMemory without changing the webservice?
Thank you

We found the following trace after increasing the log level in web.xml file:
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (500)Internal Server Error
faultActor:
faultNode:
faultDetail:
     {}:return code: 500 Request timed out.
Server Error in '/WebService' Application. An unhandled exception occurred during the execution of the current web request.
Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.HttpException: Request timed out.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and
location of the exception can be identified using the exception stack trace below
Stack Trace
[HttpException (0x80004005): Request timed out.]
;Version Information:</b>&nbsp;Microsoft .NET Framework Version:2.0.50727.42; ASP.NET
Version:2.0.50727.210
[HttpException]: Request timed out.
-->
     {http://xml.apache.org/axis/}HttpErrorCode:500
(500)Internal Server Error
     at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:744)
     at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
     at org.apache.axis.client.Call.invoke(Call.java:2767)
     at org.apache.axis.client.Call.invoke(Call.java:2443)
     at org.apache.axis.client.Call.invoke(Call.java:2366)
     at org.apache.axis.client.Call.invoke(Call.java:1812)
     at com.hm.webservice.direct.cssp.CSSPWebServiceSoap_BindingStub.getPDF
(CSSPWebServiceSoap_BindingStub.java:1543)
     at com.hm.web.data.impl.direct.AxisMemberDataRetrievalImpl.getePDF(AxisMemberDataRetrievalImpl.java:243)
     at com.web.portal.AllowancesState.doDispatch()
     at com.web.portal.Portlet.doDispatch(.java:194)
     at javax.portlet.GenericPortlet.render(Unknown Source)
     at oracle.webdb.wsrp.server.Server.getMarkup(Unknown Source)
     at oracle.webdb.wsrp.WSRP_v1_Markup_PortType_Tie.invoke_getMarkup(WSRP_v1_Markup_PortType_Tie.java:98)
     at oracle.webdb.wsrp.WSRP_v1_Markup_PortType_Tie.processingHook(WSRP_v1_Markup_PortType_Tie.java:495)
     at com.sun.xml.rpc.server.StreamingHandler.handle(StreamingHandler.java:230)
     at com.sun.xml.rpc.server.http.ea.JAXRPCServletDelegate.doPost(JAXRPCServletDelegate.java:153)
     at com.sun.xml.rpc.server.http.JAXRPCServlet.doPost(JAXRPCServlet.java:69)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
     at oracle.webdb.wsrp.server.ContextFilter.doFilter(Unknown Source)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)

Error in registering WSRP portlet producer with Oracle Portal 10.1.4

Hi all,
I am using OC4J 10.1.3.4.0 as producer of portlets and Oracle Portal 10.1.4 as consumer. I am encountering error in registering the producer WSDL. Here's the stack trace:
An error occurred when attempting to call the providers register function. (WWC-43134)
An error occurred during the call to the WSRP Provider: java.rmi.RemoteException: Runtime exception; nested exception is:
deserialization error: deserialization error: XML parsing error: com.sun.xml.rpc.sp.ParseException:1: com.sun.xml.rpc.sp/Illegal Namespace prefix: xml
com.sun.xml.rpc.encoding.DeserializationException: deserialization error: deserialization error: XML parsing error: com.sun.xml.rpc.sp.ParseException:1: com.sun.xml.rpc.sp/Illegal Namespace prefix: xml
com.sun.xml.rpc.encoding.DeserializationException: deserialization error: XML parsing error: com.sun.xml.rpc.sp.ParseException:1: com.sun.xml.rpc.sp/Illegal Namespace prefix: xml
com.sun.xml.rpc.streaming.XMLReaderException: XML parsing error: com.sun.xml.rpc.sp.ParseException:1: com.sun.xml.rpc.sp/Illegal Namespace prefix: xml
Java stack trace from root exception:
com.sun.xml.rpc.sp.ParseException:1: com.sun.xml.rpc.sp/Illegal Namespace prefix: xml
at com.sun.xml.rpc.sp.Parser2.fatal(Parser2.java:2015)
at com.sun.xml.rpc.sp.Parser2.fatal(Parser2.java:2000)
at com.sun.xml.rpc.sp.Parser2.processStartElement(Parser2.java:2794)
at com.sun.xml.rpc.sp.Parser2.parseContent(Parser2.java:3036)
at com.sun.xml.rpc.sp.Parser2.parse(Parser2.java:2360)
at com.sun.xml.rpc.streaming.XMLReaderImpl.next(XMLReaderImpl.java:105)
at com.sun.xml.rpc.streaming.XMLReaderBase.nextContent(XMLReaderBase.java:23)
at com.sun.xml.rpc.streaming.XMLReaderBase.nextElementContent(XMLReaderBase.java:41)
at oracle.webdb.wsrp.PortletDescription_LiteralSerializer.doDeserialize(PortletDescription_LiteralSerializer.java:94)
at com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalDeserialize(LiteralObjectSerializerBase.java:174)
at com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.deserialize(LiteralObjectSerializerBase.java:84)
at oracle.webdb.wsrp.ServiceDescription_LiteralSerializer.doDeserialize(ServiceDescription_LiteralSerializer.java:88)
at com.sun.xml.rpc.encoding.literal. (WWC-43273)
Note that when the producer is OC4J 10.1.3.1.1 then it works fine. The OC4J log file is also not throwing any exception. So, i think some problem with Oracle Portal 10.1.4.
Thanks
Tarun

Please follow the instructions given in https://metalink.oracle.com/help/usaeng/Search/search.html#file with document id 341922.1

WSRP Portlets - HTML elements renamed

Moved from Webcenter Spaces.
All,
I have a JSR-168 portlet that I WSRP-ed using the wsrp-predeploy tool. I have this registered in Weblogic as a WSRP producer and added to Webcenter Spaces. What I notice is that when rendered on Spaces, the HTML elements including javascript function names are renamed and prefixed with some string values. For e.g. my input fields have "_adfp_portlet_field___adfpfp_f1723360181_adfpsep_f0_adfpsep_" added at the beginning and my javascript function names (within the script tag) have "adfp1723360181_" added.
The portlet I have (it's the JasperServer portlet fwiw) uses Javascript functions for navigation. As a result of this renaming, none of the button controls work in the portlet.
Is there anything I can do about this?
Bijesh

Yannick,
That was brilliant. It worked.
BTW, I notice that the edit mode of my portlet always opens in the Maximized state. This happens even though the portlet render url is constructed with "normal" window state. Is there anything else I need to do so Webcenter displays the portlet in normal mode?
Edited by: Bijesh Krishnadas on Dec 5, 2010 7:33 PM

Wsrp portlet discovery

Similar Messages

Maybe you are looking for