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.

Similar Messages

  • 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

  • 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.

  • 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 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.

  • Migrate portlets deployed on Liferay to WebCenter

    Is there a way to convert a JSR-168 portlet WSRP portlet so that it can be deployed on WebCenter?
    The latest version of JDeveloper (11.1.2) supports importing of Maven projects but it does not support creation of WebCenter Applications.
    The Version 11.1.1.5 of JDeveloper Supports WebCenter Application creation but we were unable to import a maven project. We Want to port our portlets (JSR 168) running on liferay to WebCenter.
    Any hints on same would be helpful.
    Thanks

    I tell this also in all my courses I give.
    Standards are good but in the end when you migrate from one system to another, you almost always end up with rewriting the whole app...
    Most of the time you are interacting with the portal itself from within your portlet which completly removes the idea of loose coupling between portlet and portal.
    Then there is the JSR168 standard. If you are using inter portlet communication then you are using some special technique owned by the portal which measn that it cannot be migrated.
    Another thing is security. WebCenter does not work according the JEE roles which means that if you have defined security in your portlets in Liferay and used security, it will not work in webcenter unless you use WS-Security and configure quite a lot of mapping and security stores.
    SO as you can see, standards are good and well but in the end they are more a pain in the ....

  • 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

  • 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.

  • 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

  • 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.

  • 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.

  • Problem:programmatically portlet deployment

    Hi ...
    I want to programmatically deploy a portlet application in a portal's HOME page.
    For this i have identified following four steps:
    1. First step is to copy the J2EE resources of the portlet in a specific directory.
    2. Change the portal configuration file named xyz.portal to add this new
    portlet in the portal's HOME page.
    3. Run the "SYNC" utility to refresh the portal server.
    4. Now set the portlet properties "Visible" and "Available" to true.
    I am able to do things till step 3.
    Now i have two questions?
    1. I am able to set the property "visible" to true (by modifying the portletname.portlet
    file - mandatory element) but i could not find a way to directly
    set the "available property" to true. How can i do this programmatically.
    2. Is there a better way of doing the above four steps (for eg is there some utility
    which does the portlet deployment)
    Regards,
    Ubhay.

    Resolved it! :)
    This was the consequence of deploying portlets with invalid descriptor (not sure which one - web.xml or portal.xml - i will investigate later).
    It seems that Portal Server tries to reload all these portlets during
    "deploy redeploy" task.
    I use my own classes on portal, so executing "deploy redeploy" task is crucial for me. CLI171 error blocks the execution of this task!
    So, i deleted invalid wars and their descriptors from
    /var/opt/SUNWps/tmp/portlet/ and restarted application server - this
    solves the problem completely - and now i able to use "deploy redeploy".
    This tip may be useful during active portlet deployment:) Beware of CLI171 error! :)
    Vad.

  • Portlet Deployment Error

    Hello,
    I received this error when deploying JDeveloper 11g built PDK portlet:
    Deployment failed: Nested exception
    Resolution:
    Base Exception:
    java.rmi.RemoteException
    deploy failed!: ; nested exception is:
    oracle.oc4j.admin.internal.DeployerException: Unknown assembly root-tag attribute: xmlns:xsi. deploy failed!: ; nested exception is:
    oracle.oc4j.admin.internal.DeployerException: Unknown assembly root-tag attribute: xmlns:xsi
    Any help is appreciated. Thank you.

    There is no restriction on the number of portlets present in a war. What exceptions do you see? Which version of portal server are you using?
    Regards,
    Deepak

  • 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

Maybe you are looking for