Simple WSRP producer in WebLogic9.2 without Portal?

I find quiet a lot or references that one should be able to deploy a simple WSRP producer in WebLogic server 9.2. The point of a simple producer is that no Portal component is required, right?
Unfortunately I can not find any documentation on how to deploy this on WebLogic server only. Can somebody please point me to a proper documentation on how to do that?
Thank you very much,
-- Bernd

No, the 8.1 instruction will not work with 9.2.
In 9.2 you do need to install WLP in order to get the correct templates
and jars.
Nate
Ranjan Saikia wrote:
You mean to say that the instructions for 8.1 will work for 9.2 too? I tried them out but could not find some of the jars(javelin.jar, knex.jar) in the 9.2 installation.
I was initially following the [url http://edocs.bea.com/wlp/docs92/federation/Chap-Working_With_Producers.html]instructions in the 9.2 docs but couldnt get the required facets until I installed the portal server.

Similar Messages

  • Federated Portal Network Blues - can not connect to WSRP producer

    Hi,
    I'd like to embed some JSR-168 portlets into my SAP EP but fail immediately when trying to add the WSRP content producer.
    I have a setup of two portals, one is SAP EP 2004s (SP13) and the other a JBoss Portal v2.6.4. I'd like to share my JBoss portlets to SAP and vice-versa for evaluating the interoperability of SAP systems with the real world.
    But alas, I'm struggling on the basic setup of my SAP EP...
    Here is my problem:
    When I configure a WSRP-producer it all seems to work right but I can not connect to it, e.g. I can not register and test the connection. The connection test fails because of :
    Producer object was found
    Could not retrieve the WSDL file; the handshake URL may not exist or may be invalid
    The SAP systems runs behind no proxy at all, so this can't be the issue. When testing the same WSRP producer URL from JBoss portal it all works fine. The URL I used was a WSRP test site from Oracle, see [http://portalstandards.oracle.com/portletapp/portlets?WSDL].
    Does anyone have a glue what might be missing on my SAP Portal? The standard log gives me no clues at all I've been tail minus effing the thing for hours...
    The SAP documentation - SAP Library, various E-Learning things - couldn't solve the problem for me...
    Thanks for your support!
    regards,
    Christian

    Hi,
    Unfortunately I do not have any experience with connecting to JBoss, but perhaps this document can help you analyzing your issue:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/703cfbbd-e85e-2a10-00a3-ecd502c08e82
    Good luck!
    Best regards,
    Jan Laros
    PS. Please award points when helpfull.

  • Portal Standards Website - WSRP Producer WSDL unavailable

    Hi,
    I'm trying to use the portal standards website as a WSRP producer to prototype some WSRP work I am undertaking. From reading the "Registering a WSRP Producer or Web Provider on OracleAS Portal / Verification Server" document I believe that to register Oracle's Sample WSRP Producer as a provider in JDeveloper I need to use the URL
    http://portalstandards.oracle.com/wsrp/jaxrpc?WSDL
    however if I try to hit this using a standard browser I just get a 404 Not Found error. Trying it in the WSRP Producer registration wizard in JDeveloper just gives a connection exception "Failed to read WSDL from http://portalstandards.oracle.com/wsrp/jaxrpc?WSDL:WSDL not found:"
    Is this WSDL no longer available?

    I have found the following manual:
    "Oracle® Application Server Portal Developer's Guide 10g Release 2" - Configuring Your Application Server to Run JPS-Compliant Portlets (including Data Sources's Configuration).
    I have followed the necessary steps, but when I tried to test it (Registering and Viewing Your Portlet's Section (create a WSRP Provider)), I have the same errorr:
    Internal error WWC-00006
    Unexpected error ORA-00932
    WWC-35000
    I have verified via web browser my WSRP Producer WSDL Page, and it is correct.
    I have tested with different users (orcladmin, portal, etc), even I have included them in PORTAL_ADMINISTRATORS group. But it doesn't work...
    Another thing I have tested is to apply 4640471 patch, although I am not sure it should be necessary, because in ReadMe file, it is only for Solaris Systems, and I am working with Windows Server 2003 SP1...
    I am really desesperate with this error, do you have any idea to solve it?
    Thank you and regards.
    Edited by: Mónica on 28-jun-2010 3:44

  • Error when extending portal domain to be a wsrp producer

    I have created a Weblogic Portal domain, and then created a Portal web application deployed in Weblogic Portal domain.
    Now, I would like to extend the domain to be a WSRP producer in order to consume som portlets in other Portals.
    When I try to extend the domain I get the following error:
    Domain Extension Application Failed!
    Domain Location: <DOMAIN_HOME>\base_domain2
    Reason: null
    Exception:
    Traceback (innermost last):
    File "<iostream>", line 14, in ?
    File "D:\Documents and Settings\E\Local Settings\Temp\WLSTOfflineIni61149.py", line 118, in create
    com.bea.plateng.domain.script.jython.WLSTException: com.bea.plateng.domain.script.ScriptException: com.bea.plateng.domain.ValidateException: Property "Name" of PKICredentialMapper with original name "Provider" is invalid. The property value is duplicated.
    Any ideas?
    Thanks in advance!!

    By default, portal domains include support wsrp producer - so there is
    no need to extend the domain.
    Subbu
    Espen Kj?lberg wrote:
    I have created a Weblogic Portal domain, and then created a Portal web application deployed in Weblogic Portal domain.
    Now, I would like to extend the domain to be a WSRP producer in order to consume som portlets in other Portals.
    When I try to extend the domain I get the following error:
    Domain Extension Application Failed!
    Domain Location: <DOMAIN_HOME>\base_domain2
    Reason: null
    Exception:
    Traceback (innermost last):
    File "<iostream>", line 14, in ?
    File "D:\Documents and Settings\E\Local Settings\Temp\WLSTOfflineIni61149.py", line 118, in create
    com.bea.plateng.domain.script.jython.WLSTException: com.bea.plateng.domain.script.ScriptException: com.bea.plateng.domain.ValidateException: Property "Name" of PKICredentialMapper with original name "Provider" is invalid. The property value is duplicated.
    Any ideas?
    Thanks in advance!!

  • Integrate OAS Portal with E1 - WSRP Producer

    Hello,
    I want to integrate OAS Portal with E1. I am following: "JD Edwards EnterpriseOne Tools Release 8.98 Portal Reference Guide for All Portals and Platforms" and I have a doubt about how to register a new WSRP producer for Oracle Portal Server.
    I am working with:
    - OAS Portal 10.1.4 (integrated with Windows Server 2003 SP1)
    - JDE E1 8.12 Tools 8.98
    - Each one are in a different physical machine.
    I am not sure what is exactlly WSRP producer. In the manual, it says that it is: JDE E1 HTML Web Server.
    When I amb in the second step to register the new WSRP (Provider Description (WSDL)) I have the following error:
    "Internal Error *(WWC-00006)*
    Unexpected error: *ORA-00932*: Inconsistent datatype waited an IN argument at position 2 that is an instance of an Oracle
    type convertible to an instance of a user defined Java class has obtained an Oracle type that could not be converted to a java class *(WWC-35000)*"
    In WSDL URL I have specified:
    http://HOST_E1:8083/jde/wsdl/WSRPService.wsdl
    And if it is acceded via web browser, the result is:
    - <definitions targetNamespace="urn:oasis:names:tc:wsrp:v1:wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:bind="urn:oasis:names:tc:wsrp:v1:bind" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <import namespace="urn:oasis:names:tc:wsrp:v1:bind" location="local.wsdl" />
    - <service name="WSRPService">
    - <port name="WSRPBaseService" binding="bind:WSRP_v1_Markup_Binding_SOAP">
    <soap:address location="http:///HOST_E1:8083/jde/WSRPBaseService" />
    </port>
    - <port name="WSRPServiceDescriptionService" binding="bind:WSRP_v1_ServiceDescription_Binding_SOAP">
    <soap:address location="http:///HOST_E1:8083/jde/WSRPServiceDescriptionService" />
    </port>
    </service>
    </definitions>
    1) Is correct this result?
    2) In which file can I find the port number that I need to register the WSRP?
    I am not sure about this port, but it is the number port to enter to JDE's Web (http://HOST_E1:8083/jde/E1Menu.maf)
    3) Is necessary to do any step before?
    Thank you and regards

    I have found the following manual:
    "Oracle® Application Server Portal Developer's Guide 10g Release 2" - Configuring Your Application Server to Run JPS-Compliant Portlets (including Data Sources's Configuration).
    I have followed the necessary steps, but when I tried to test it (Registering and Viewing Your Portlet's Section (create a WSRP Provider)), I have the same errorr:
    Internal error WWC-00006
    Unexpected error ORA-00932
    WWC-35000
    I have verified via web browser my WSRP Producer WSDL Page, and it is correct.
    I have tested with different users (orcladmin, portal, etc), even I have included them in PORTAL_ADMINISTRATORS group. But it doesn't work...
    Another thing I have tested is to apply 4640471 patch, although I am not sure it should be necessary, because in ReadMe file, it is only for Solaris Systems, and I am working with Windows Server 2003 SP1...
    I am really desesperate with this error, do you have any idea to solve it?
    Thank you and regards.
    Edited by: Mónica on 28-jun-2010 3:44

  • WSRP producer on WLS - license issues

    Hello,
    according to docs, WSRP producers can be run on plain WebLogic Server, no need for Portal:
    [url http://e-docs.bea.com/wlp/docs100/federation/Chap-Working_With_Producers.html#wp1010271]http://e-docs.bea.com/wlp/docs100/federation/Chap-Working_With_Producers.html#wp1010271
    However, in order to extend the domain, some templates (wsrp-simple-producer.jar) from a portal installation are needed, they are not part of the plain WLS installation. Maybe I could copy the scripts from our WLP to WLS (I haven't tried yet, maybe some JARs are needed too).
    My question is, whether this is legal, or if I need to buy a WLP license for each WLS modified this way.
    Thank you,
    Martin.

    The intended way to do this is use the Portal installer (portal license
    not required). Then build your domains as specified on e-docs. Only the
    WLS license will be checked at runtime.
    Hope this helps,
    Nate
    Martin Pl wrote:
    Hello,
    according to docs, WSRP producers can be run on plain WebLogic Server, no need for Portal:
    [url http://e-docs.bea.com/wlp/docs100/federation/Chap-Working_With_Producers.html#wp1010271]http://e-docs.bea.com/wlp/docs100/federation/Chap-Working_With_Producers.html#wp1010271
    However, in order to extend the domain, some templates (wsrp-simple-producer.jar) from a portal installation are needed, they are not part of the plain WLS installation. Maybe I could copy the scripts from our WLP to WLS (I haven't tried yet, maybe some JARs are needed too).
    My question is, whether this is legal, or if I need to buy a WLP license for each WLS modified this way.
    Thank you,
    Martin.

  • Namespace Error, while creating proxy for a WSRP producer(Created on Exo)

    Hi ,
    I have implemented and deployed WSRP producer on Exo portal container. When I was trying to create proxy for the same in weblogic portal 10.2 its giving me the following error. Upon submiting the WSDL URL
    !ENTRY com.bea.wlp.eclipse.common 4 4 2008-12-08 13:46:27.540
    !MESSAGE NAMESPACE_ERR
    !STACK 0
    org.w3c.dom.DOMException: NAMESPACE_ERR
         at weblogic.xml.domimpl.ElementNSImpl.<init>(ElementNSImpl.java:74)
         at weblogic.xml.saaj.SOAPElementImpl.<init>(SOAPElementImpl.java:40)
         at weblogic.xml.saaj.SaajDocument.createElementNS(SaajDocument.java:63)
         at com.bea.wsrp.util.DomUtils.createChildElement(DomUtils.java:386)
         at com.bea.wsrp.util.DomUtils.addChildElement(DomUtils.java:406)
         at com.bea.wsrp.util.DomUtils.addChildElement(DomUtils.java:371)
         at com.bea.wsrp.bind.serviceDescription.GetServiceDescriptionRequest.writeTo(GetServiceDescriptionRequest.java:40)
         at com.bea.wsrp.client.ProducerAgentImpl.getServiceDescription(ProducerAgentImpl.java:129)
         at com.bea.wsrp.client.ProducerAgentImpl.getServiceDescription(ProducerAgentImpl.java:80)
         at com.bea.wsrp.client.ProducerAgentImpl.getServiceDescription(ProducerAgentImpl.java:68)
         at com.bea.wsrp.client.ProducerAgentImpl.getServiceDescription(ProducerAgentImpl.java:57)
         at com.bea.wlp.eclipse.wsrp.portletbuilder.wsrp.ProducerAgent.getServiceDescription(ProducerAgent.java:99)
         at com.bea.wlp.eclipse.wsrp.portletbuilder.wsrp.ProducerAgent.<init>(ProducerAgent.java:57)
         at com.bea.wlp.eclipse.wsrp.portletbuilder.wsrp.ProducerAgent.<init>(ProducerAgent.java:45)
         at com.bea.wlp.eclipse.wsrp.portletbuilder.wizard.wsrp.SelectProducerPanel$ProducerInfoRunner.run(SelectProducerPanel.java:690)
    Could any one help me to solve this problem.
    Thanks & Regards,
    Naresh

    Hi Nate,
    Please find the following wsdl.
    <?xml version="1.0" encoding="UTF-8" ?>
    <wsdl:definitions targetNamespace="http://localhost:8080/wsrp/services/Version" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://localhost:8080/wsrp/services/Version" xmlns:intf="http://localhost:8080/wsrp/services/Version" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <!--
    WSDL created by Apache Axis version: 1.4
    Built on Nov 19, 2006 (02:31:34 GMT+00:00)
    -->
    <wsdl:message name="getVersionRequest" />
    <wsdl:message name="getVersionResponse">
    <wsdl:part name="getVersionReturn" type="soapenc:string" />
    </wsdl:message>
    <wsdl:portType name="Version">
    <wsdl:operation name="getVersion">
    <wsdl:input message="impl:getVersionRequest" name="getVersionRequest" />
    <wsdl:output message="impl:getVersionResponse" name="getVersionResponse" />
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="VersionSoapBinding" type="impl:Version">
    <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
    <wsdl:operation name="getVersion">
    <wsdlsoap:operation soapAction="" />
    <wsdl:input name="getVersionRequest">
    <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://axis.apache.org" use="encoded" />
    </wsdl:input>
    <wsdl:output name="getVersionResponse">
    <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/wsrp/services/Version" use="encoded" />
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="VersionService">
    <wsdl:port binding="impl:VersionSoapBinding" name="Version">
    <wsdlsoap:address location="http://localhost:8080/wsrp/services/Version" />
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    Thanks & Regards,
    Naresh

  • Unable to register WSRP producer

    We develop portlets for Oracle Application Server Portal.
    While trying to register WSRP producer we get error
    500 Internal Server Error
    java.lang.NoClassDefFoundError
    at oracle.xml.xslt.XSLSAXPrintDriver.printAttributes(XSLSAXPrintDriver.java:460)
    at oracle.xml.xslt.XSLSAXPrintDriver.startElement(XSLSAXPrintDriver.java:393)
    at oracle.xml.xslt.XSLEventHandler.reportStartElement(XSLEventHandler.java:267)
    at oracle.xml.xslt.XSLEventHandler.characters(XSLEventHandler.java:863)
    at oracle.xml.xslt.XSLCopy.processAction(XSLCopy.java:188)
    at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
    at oracle.xml.xslt.XSLTemplate.processAction(XSLTemplate.java:205)
    at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:242)
    at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:142)
    at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
    at oracle.xml.xslt.XSLCopy.processAction(XSLCopy.java:178)
    at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
    at oracle.xml.xslt.XSLTemplate.processAction(XSLTemplate.java:205)
    at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:242)
    at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:142)
    at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
    at oracle.xml.xslt.XSLTemplate.processAction(XSLTemplate.java:205)
    at oracle.xml.xslt.XSLStylesheet.execute(XSLStylesheet.java:581)
    at oracle.xml.xslt.XSLProcessor.processXSL(XSLProcessor.java:318)
    at oracle.xml.jaxp.JXTransformer.transform(JXTransformer.java:387)
    at com.sun.xml.rpc.server.http.ea.WSDLPublisher.publish(WSDLPublisher.java:58)
    at com.sun.xml.rpc.server.http.ea.JAXRPCServletDelegate.doGet(JAXRPCServletDelegate.java:284)
    at com.sun.xml.rpc.server.http.JAXRPCServlet.doGet(JAXRPCServlet.java:76)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.evermindhttp://Oracle Application Server Containers for J2EE 10g (10.1.2.0.2).server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
    at oracle.webdb.wsrp.server.ContextFilter.doFilter(Unknown Source)
    at com.evermindhttp://Oracle Application Server Containers for J2EE 10g (10.1.2.0.2).server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:16)
    at oracle.webdb.wsrp.server.ContextFilter.doFilter(Unknown Source)
    at com.evermindhttp://Oracle Application Server Containers for J2EE 10g (10.1.2.0.2).server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:659)
    at com.evermindhttp://Oracle Application Server Containers for J2EE 10g (10.1.2.0.2).server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
    at com.evermindhttp://Oracle Application Server Containers for J2EE 10g (10.1.2.0.2).server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
    at com.evermindhttp://Oracle Application Server Containers for J2EE 10g (10.1.2.0.2).server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
    at com.evermindhttp://Oracle Application Server Containers for J2EE 10g (10.1.2.0.2).server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
    at com.evermindhttp://Oracle Application Server Containers for J2EE 10g (10.1.2.0.2).util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
    at java.lang.Thread.run(Thread.java:534)
    portlets that were already registered work fine, but when trying to update their producers we get the same error.
    Versions:
    Oracle Application Server 10g Release 2 (10.1.2.0.2) for Microsoft Windows x86
    Oracle Database 10g Release 1 (10.1.0.2) Enterprise Edition for Microsoft Windows (32-bit)
    We use WSRP 2.0.
    We suppose that problem appeared after unsuccessfull attempts to deploy portlet which use Oracle ADF libraries.
    While trying to deploy that portlet we've got java.lang.outOfMemoryError, and logs of WSRP instance contained no errors.
    Any help would be appreciated.
    Thanks in advance,
    Yelena.

    portlets that were already registered work fine, but when trying to update their producers we get the same error.
    Versions:
    Oracle Application Server 10g Release 2 (10.1.2.0.2) for Microsoft Windows x86
    Oracle Database 10g Release 1 (10.1.0.2) Enterprise Edition for Microsoft Windows (32-bit)
    We use WSRP 2.0.
    We suppose that problem appeared after unsuccessfull attempts to deploy portlet which use Oracle ADF libraries.
    While trying to deploy that portlet we've got java.lang.outOfMemoryError, and logs of WSRP instance contained no errors.
    Any help would be appreciated.
    Thanks in advance,
    Yelena.--
    Edited by: AMN on Jul 2, 2009 12:41 AM

  • External Application without portal ?

    Hi all
    I have several applications built in JSP + BC4J , deployed in Oracle Application Server 10G (9.0.4) , operating system is windows 2000 server.
    Application server middle tier and infrastruture are in the same server.
    I have added all applications to SSO as External Application
    I'm not using Portal, so, how can i make this applications "visible" to end user ?
    Should i built and JSP page wich lists all External Applications, asks for login/password if authentication cookie not exits ??
    is there any other way of doing it without portal ???
    Best Regards
    Rui Madaleno

    Rui,
    actually the External Applications implementation is completely separate from the Portal and does not require it to function. (The external Applications Portlet is a simple interface to expose the list of external applications.
    If you are looking for a simple interface to expose the list, it is much as you describe. Building a simple Partner application which has links referencing the appropriate SSO server URLs. Storing the links in a table and simply querying them allows for a simple interface that can be secured/modified withour haveing to change the page itself.

  • Transitioning WSRP producer registrations from development to production

    Hi there,
    we're currently struggling a bit with the notion of producer registrations vs. the need for separating our development environment from production.
    Here's what we do:
    1. We create a producer connection in JDeveloper, but using the development server's portlet deployment as WSDL endpoint
    2. We then continue to create some pages, instantiating portlets from the newly created producer as we go along
    3. We deploy that to our development environment. All is well!
    4. We (at some time in our projects lifecycle) try to go ahead and deploy to production. For that, we'd like to change the URL of the producer connection while preserving all the pages we composed (at design time), so far.
    5. First, we simply change the producer url in connections.xml before starting to predeploy. -> Error, since the ID of the registration handle included in our local MDS doesn't match anything that exists in the actual production environment.
    6. Next, we try to predeploy/deploy the EAR file as is, then change the actual producer URL using WLST (setWSRPProducer, registerWSRPProducer, degisterWSRPProducer, etc) or the Fusion Enterprise Manager. -> Doesn't work either, since deregistration/registration invalidates all the existing portlet instance files we have in our original MDS/MAR file.
    So here's my question: What are best practices you can recommend when working with WSRP producers and a (clean) separation between development, testing and production environment? Are design-time producer registrations/portlet instantiations even possible in such a context? Should we perhaps use the preference data migration tool for migrating consumer registrations from one environment to the other? Even when one of those environments is unstable (dev) and the other supposed to be stable (production)? Or should we (at the portlet-level) disable consumer registrations entirely? If yes: How to do this in WebCenter?
    Help is deeply appreciated :-)!
    Cheers,
    Chris
    Edited by: ckesselh on Nov 3, 2011 8:14 AM

    Hi Chris,
    You raise good questions that I would love to explore further as well and it would be great if you could let me know what deployment approach you have come up with. Some of this is covered under section http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_imp_exp.htm and http://docs.oracle.com/cd/E17904_01/core.1111/e10105/deployer_role.htm which I am sure you have already reviewed. I have a much simpler problem with getting a Null Exception Error every time that I simply try to register a WSRP Producer with the sample .Net service - have you ever tried that and have come across the same issue?
    Thanks,
    Michael.

  • Configuring Custom JavaScript/CSS and YUI in WSRP Producer Portlet

    I am trying to find information on how to setup/configure WebCenter for WSRP Producer Portlets that have YUI and custom javascript/CSS. While we have gotten some of the YUI features and custom javascript/CSS to work, we find that some references are not loading such as custom CSS and images. This appears to be a result of the URL rewrite not occuring for some of these references. It appears that WebLogic Portal supports this capability and can be configured using a dependency file for such needs but I have been unable to find a equivalent for WebCenter.
    Any help would be greatly appreciated.
    Best Regards.
    Carl

    When you are providing javascript or css path,provide the absolute path.
    like src="http://<server>:<port>/portlet context root/images/some.png".
    In that way custom javascript/css will work.
    Regards,
    Hoque

  • Java.lang.ClassCastException: com.bea.wsrp.producer.descriptor.DefaultPortl

    Hi All,
    I am getting the java.lang.ClassCastException: com.bea.wsrp.producer.descriptor.DefaultPortletDescriptor
    while loading a portlet from a portal.
    I could see the jar for this class is wsrp-producer.jar.Is this due to a jar issue.I cant debug as it needs the java source files for the wsrp-producer.jar.Can anyone help us where we can get the source java files for the classes in wsrp-producer.jar.
    The weblogic server is weblogic-10.3.2
    Thanks in Advance
    Edited by: user7437632 on Oct 5, 2012 4:55 AM

    Hi All,
    I am getting the java.lang.ClassCastException: com.bea.wsrp.producer.descriptor.DefaultPortletDescriptor
    while loading a portlet from a portal.
    I could see the jar for this class is wsrp-producer.jar.Is this due to a jar issue.I cant debug as it needs the java source files for the wsrp-producer.jar.Can anyone help us where we can get the source java files for the classes in wsrp-producer.jar.
    The weblogic server is weblogic-10.3.2
    Thanks in Advance
    Edited by: user7437632 on Oct 5, 2012 4:55 AM

  • Where is the Oracle WSRP producer?

    Hi, I am looking for the Oracle WSRP producer located at http://portalstandards.oracle.com/wsrp/jaxrpc?WSDL before. But the URL does not exist now.
    Could anybody let me know the producer? In fact I saw those remote portlets on http://portalstandards.oracle.com/portal/page/portal/OracleHostedWSRPPortal/Samples. Thanks.
    Xiaobo Yang

    Thanks Sandeep. But it seems that I have set up such a producer by myself with what you mentioned. What I want is an existing Oracle WSRP producer which I can use for testing.
    Regards,
    Xiaobo

  • WSRP Producer registration (unstable behaviour)

    Hi,
    I'm currently using JDev 10.1.3.3.0 build 4157 and building a webcenter application which makes use of both WSRP and PDK-Java portlets. I'm getting strange errors with WSRP Producer registration: in order to simplify things this description refers to the RichTextPortlet which is a prebuilt portlet but the problem is happening with every WSRP portlet producer, not with PDK-Java producers:
    When I create the producer for the RichTextPortlet everything works perfectly, I run my app and personalize the portlet without problems. However, after several runs the portlets start to show the "Portlet unavailable" message and the server logs says something about the producer registration being wrong. When I test the producer connection in JDev it checks ok but if I try to refresh it, it fails. If I register an identical producer it works fine but the original producer doesn't.
    The exception I get when I refresh the producer registration is:
    oracle.portlet.client.container.PortletRemoteException: WSRP producer responded with an error (InvalidRegistrationException)
         at oracle.portlet.client.techimpl.wsrp.WSRPClientImpl.handleException(WSRPClientImpl.java:2462)
         at oracle.portlet.client.techimpl.wsrp.WSRPClientImpl.deleteRemotePortlet(WSRPClientImpl.java:1094)
         at oracle.portlet.client.techimpl.wsrp.WSRPClientImpl.delete(WSRPClientImpl.java:999)
         at oracle.portlet.client.techimpl.wsrp.WSRPClientImpl.refresh(WSRPClientImpl.java:1142)
         at oracle.portlet.client.containerimpl.wsrp.WSRPProducerImpl._refresh(WSRPProducerImpl.java:385)
         at oracle.portlet.client.containerimpl.wsrp.WSRPProducerImpl.refresh(WSRPProducerImpl.java:363)
         at oracle.adfinternal.model.portlet.manager.PortletProviderManager.refreshPortletProvider(PortletProviderManager.java:864)
         at oracle.adfinternal.model.portlet.manager.ProviderDT.refresh(ProviderDT.java:310)
         at oracle.adfdtinternal.model.portlet.wizards.registration.common.WizardUtils$3.doWork(WizardUtils.java:159)
         at oracle.ide.dialogs.ProgressRunnable.run(ProgressRunnable.java:159)
         at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
         at java.lang.Thread.run(Thread.java:595)
    Caused by: oracle.portlet.server.container.InvalidRegistrationException: oracle.portlet.wsrp.v1.InvalidRegistrationException: oracle.portlet.wsrp.v1.soap.InvalidRegistration
         at oracle.portlet.wsrp.v1.ServerToWSRPv1.destroyPortlets(ServerToWSRPv1.java:4835)
         at oracle.portlet.client.connection.wsrp.ActivityServerWrapper.destroyPortlets(ActivityServerWrapper.java:305)
         at oracle.portlet.client.techimpl.wsrp.WSRPClientImpl.deleteRemotePortlet(WSRPClientImpl.java:1088)
         ... 10 more
    Caused by: oracle.portlet.wsrp.v1.InvalidRegistrationException: oracle.portlet.wsrp.v1.soap.InvalidRegistration
         at oracle.portlet.wsrp.v1.WSRP_v1_PortletManagement_PortTypeJaxbToSoap.destroyPortlets(WSRP_v1_PortletManagement_PortTypeJaxbToSoap.java:220)
         at oracle.portlet.wsrp.v1.ServerToWSRPv1.destroyPortlets(ServerToWSRPv1.java:4785)
         ... 12 more
    Caused by: oracle.portlet.wsrp.v1.soap.InvalidRegistration
         at oracle.portlet.wsrp.v1.soap.runtime.WSRP_v1_PortletManagement_PortType_destroyPortlets_Fault_SOAPSerializer.deserializeDetail(WSRP_v1_PortletManagement_PortType_destroyPortlets_Fault_SOAPSerializer.java:94)
         at oracle.j2ee.ws.common.encoding.SOAPFaultInfoSerializer.doDeserializeSOAP11(SOAPFaultInfoSerializer.java:132)
         at oracle.j2ee.ws.common.encoding.SOAPFaultInfoSerializer.doDeserialize(SOAPFaultInfoSerializer.java:94)
         at oracle.j2ee.ws.common.encoding.ObjectSerializerBase.deserialize(ObjectSerializerBase.java:180)
         at oracle.j2ee.ws.common.encoding.ReferenceableSerializerImpl.deserialize(ReferenceableSerializerImpl.java:147)
         at oracle.portlet.wsrp.v1.soap.runtime.WSRP_v1_PortletManagement_Binding_SOAP_Stub._readBodyFaultElement(WSRP_v1_PortletManagement_Binding_SOAP_Stub.java:624)
         at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:321)
         at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
         at oracle.portlet.wsrp.v1.soap.runtime.WSRP_v1_PortletManagement_Binding_SOAP_Stub.destroyPortlets(WSRP_v1_PortletManagement_Binding_SOAP_Stub.java:76)
         at oracle.portlet.wsrp.v1.WSRP_v1_PortletManagement_PortTypeJaxbToSoap.destroyPortlets(WSRP_v1_PortletManagement_PortTypeJaxbToSoap.java:207)
         ... 13 more
    And its driving me mad...
    Hope someone can help.
    Thanks,
    Yoel

    Yoel,
    I think the WebCenter forum is probably the right place for this one.
    Oh, wait, I see you already cross-posted over there. You sneaky little devil ;)
    John

  • WSRP Producer Portlets

    Hi,
    Is it possible to make edk remote porlet
    to a WSRP producer porlet. Informations / references
    in doing this concept are solicited with thanks.
    Vignesh.

    Well thats a good question. As far as plumtree portlets are concerned, EDK portlets using the Portlet Context (IPortletContext) would not be able to run on any other portal.... the Gateway thing remembr !! so ideally the answer is No. Plumtree portlets are not WSRP producers though if yourapplication is deployed on weblogic portal referencing the EDK.JAR and you are just utilising the underlying PRC not the remote portlet APIs you might be able to expose the application in Weblogic as WSRP producer.
    let me know what you think

Maybe you are looking for