Creating Portlet programatically in Portal 4 as in WLCS3.5

Can i create a portlet through some APIs in Portal4.0 ?
I guess this is possible in WLCS 3.5.

Hi Mere!
It is not an API but I am using PORTAL.WWV_THINGSAVE.saveitemCan you also tell me how to display item programmaticaly?
Thanks in advance,
Ervin!

Similar Messages

Create a new portlet in Deployed Portal in production environment

are there any ways to import or create a new portlet in Deployed Portal in production environment?
Edited by: user8322798 on May 1, 2011 7:26 AM

This can done via WSRP proxy portlets and streaming desktops. First, you'll need to have a WSRP producer setup somewhere. This could be another WLP webapp with portlets, or another server altogether. Or, you can use the JSR 286 WSRP import tool from within the Portal Administration Console (I think it's under Services | WSRP | Import Tool) -- this will allow you upload .war(s) of JSR 168 or 286 portlets, which will be turned into WSRP producer(s).
Then, you can use the Portal Administration Console to register a WSRP Producer, and then add portlets from the producer to your desktop (http://download.oracle.com/docs/cd/E15919_01/wlp.1032/e14235/chap_fed_books_pages.htm#FPGWP690). Additionally, once the producer has been registered in Portal Adminstration Console, an adminstrator user can use the Dynamic Visitor Tools from within the streaming desktop itself to add wsrp proxy portlets to the desktop (http://download.oracle.com/docs/cd/E15919_01/wlp.1032/e14243/dvt.htm#PDGWP691).
It is not possible to add new local .portlet files to a deployed application in production mode. This requires adding the file artifacts to the .ear/.war and redeploy the application.
Greg

Problem with creating new user in portal = portlet is not visible

Hi,
I've got a problem with creating new users in portal. In the Administer tab of the builder is the user portlet not visible.
How can I make this portlet visible?
Please Help
thank you...
Gilbert

Hi..my problem slightly similar.
I created one new user, and didn't select anything from "Public Groups Assignment" and "Privilege Assignment" for him.
I expect the user will be a public user.
But, when he try to logged in the portal,
He cannot see all the PORTLETS related to database values..
All he can see just LINKS -that all in my portal right now beside the report from database that the user cannot see :)
So, what did i do wrong?
Plz Advise, and thanks.

Creating a Exchange Outlook Portlet on your portal

I have been look around for a way to create an Exchange Outlook portlet on a 11g portal. I have been seeing many different post, but no direct answer. Could someone direct me in a way to accomplish this?
Im just looking for a way for users to see their emails, contact and calendar.
Thanks

Hi
We have a similar situation.We would like to use external apps .net Portal as landing site for external users. After they are logged in, they can click on istore (EBS) and access it without having to provide the credentials again. I know OAM can handle heterogeneous environments. But the question is how will the credentials be handed over to EBS HTTP server once users have logged into .net app? I know OAM creates the SSO cookies, but will it work ? How can we “hand-over” the credentials to EBS HTTP….
We cannnot show EBS as portlet in .net portal, atleast thats what my developers are telling me. Any input is highly appreciated.

Announcing: Developing JSF Portlets with WebLogic Portal Whitepaper

Just Released: Developing JSF Portlets with WebLogic Portal Whitepaper
A supplemental developer's guide has been published to help guide WLP 10.x customers that wish to use JSF as the web framework for building portlets on WebLogic Portal. This is a sizable document (150 pages) that covers a large number of topics. It also coaches developers on best practices and common pitfalls.
Important: It also clarifies the supported configuration of JSF within Portal Web Projects. Workshop for WebLogic by default configures a web project in a configuration that is not supported by WebLogic Portal. The guide explains how to address this:
* Change from the unsupported MyFaces JSF implementation to the supported Sun Reference Implementation (RI)
* Change from the unsupported "client" STATE_SAVING_METHOD to the supported "server"
The guide can be downloaded here:
http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf
To help internet searches locate this document, the table of contents is reproduced below:
Introduction
1.1. Prerequisites...................................................................... 8
1.2. Applicable Versions............................................................ 8
1.3. Native Portlet Bridges and Standard Portlet Bridges .......... 8
1.4. JSF Portlet Support Roadmap ........................................... 9
1.5. Whitepaper Structure ....................................................... 10
1.6. Look Before You Leap ..................................................... 10
1.7. For More Information........................................................ 10
Part 1: Converting JSF Applications into Portlets
2. IDE Support for JSF Portlets Chapter ...................................... 12
2.1. Workshop for WebLogic – WebLogic Portal's Supported IDE 12
2.2. Workshop Features for JSF Support in WebLogic Portal.. 12
3. Introduction to JSF Portlets Chapter ........................................ 18
3.1. Creating Your First JSF Portlet......................................... 18
3.2. Essentials of JSF Portlet Views........................................ 21
3.3. WebLogic Portal Artifacts................................................. 22
4. Configuring JSF within WebLogic Portal Chapter..................... 24
4.1. JSF Library Modules in WebLogic Server ........................ 24
4.2. Installing the JSF Libraries into a Portal Web Project ....... 25
4.3. JSF Configuration Settings............................................... 27
4.4. Configuring JSF 1.2 ......................................................... 29
4.5. Building an Unsupported JSF Implementation Library Module 31
4.6. Faces Configuration is Web Application Scoped.............. 31
5. Navigation within a JSF Portlet Chapter................................... 33
5.1. Navigating within a Portlet with the JSF Controller ........... 33
5.2. Redirects.......................................................................... 34
6. Namespacing Chapter ............................................................. 35
6.1. Namespacing Managed Bean Names.............................. 35
6.2. Client ID Namespacing with the View and Subview Components 35
6.3. Client ID Namespacing with the WLP NamingContainer .. 36
7. Logging, Iterative Development, and Debugging Chapter ........ 39
7.1. Logging............................................................................ 39
7.2. Iterative Development ...................................................... 39
7.3. Debugging ....................................................................... 40
8. Custom JavaScript Chapter ..................................................... 42
8.1. DOM Manipulation within a JSF ....................................... 42
8.2. Form Validation within a JSF Portlet ................................ 45
9. Preparing JSF Portlets for Production Chapter ........................ 46
9.1. Configuration.................................................................... 46
9.2. Performance and Scalability............................................. 47
9.3. Security............................................................................ 49
9.4. Localization...................................................................... 50
Part 2: Interacting with the Portal Environment
10. Native Bridge Architecture Chapter ...................................... 54
10.1. Container Architecture Overview.................................. 54
10.2. Container Architecture.................................................. 54
10.3. Container Interactions .................................................. 55
11. Interportlet Communication Chapter .................................... 56
11.1. Using Session and Request Attributes for IPC (Anti-pattern) 56
11.2. Using the WLP Event Facility for IPC with JSF Portlets 56
11.3. Notifications ................................................................. 60
11.4. Comparison of the IPC Approaches ............................. 60
12. Scopes Chapter ................................................................... 62
12.1. Conceptual Scopes for Standard JSF Applications ...... 62
12.2. Conceptual Scopes for Portal Applications................... 63
12.3. Implementation Patterns for Portal Scopes .................. 63
13. State Sharing Patterns Chapter ........................................... 66
13.1. State Sharing Concepts ............................................... 66
13.2. HttpSession Versus HttpServletRequest ...................... 66
13.3. Base Code for HttpSession Patterns ............................ 67
13.4. Single Portlet Pattern ................................................... 68
13.5. Multiple Portlet Patterns ............................................... 69
14. Rendering Lifecycles Chapter .............................................. 77
14.1. WLP and JSF Lifecycles .............................................. 77
14.2. Invocation Order of WLP and JSF Lifecycle Methods... 77
14.3. Accessing WLP Context Objects from JSF Managed Beans 78
15. Portal Navigation Chapter .................................................... 80
15.1. Programmatically Constructing JSF Portlet URLs ........ 80
15.2. Changing the Active Portal Page.................................. 80
15.3. Redirects within a Portal............................................... 83
16. Ajax Enablement Chapter .................................................... 85
16.1. Ajax in JSF Portlets...................................................... 85
16.2. Partial Page Rendering Pattern.................................... 85
16.3. Stateless API Request Pattern ..................................... 86
16.4. Portlet Aware API Request Pattern .............................. 87
16.5. Controlling the WLP Ajax Framework........................... 91
17. Additional WLP Features Chapter........................................ 93
17.2. Portlet Container Features ........................................... 93
17.3. Portal Container Features ............................................ 98
18. Example: Implementing a Login Portlet Chapter .................. 99
18.1. Login Portlet Motivation................................................ 99
18.2. Login Portlet Design..................................................... 99
18.3. Login Portlet Implementation...................................... 101
Part 3: Integrating Third Party Libraries
19. Integration Overview Chapter............................................. 111
19.1. Types of Libraries....................................................... 111
19.2. Roadmap for MyFaces Trinidad and ADF Faces Rich Client 111
20. Using the Facelets View Technology Chapter.................... 113
20.1. Introduction to Facelets .............................................. 113
20.2. Configuring Facelets Support ..................................... 113
21. Using the Apache MyFaces Tomahawk Component Library Chapter 115
21.1. What is Apache MyFaces Tomahawk? ...................... 115
21.2. Support for Tomahawk in WLP................................... 115
21.3. Tomahawk Component List........................................ 116
21.4. Installing and Configuring Tomahawk......................... 119
21.5. Resolving the Duplicate ID Issue................................ 120
21.6. Referring to Resources .............................................. 120
21.7. forceId Attribute.......................................................... 124
21.8. File Upload................................................................. 125
22. Using the Apache Beehive Navigation Controller Chapter . 126
22.1. Apache Beehive Page Flow ....................................... 126
22.2. JSF and Page Flows .................................................. 126
22.3. Configuring the JSF Integration with Page Flows ....... 127
Appendices
23. Appendix 1: Consolidated List of Best Practices ................ 130
24. Appendix 2: Known Issues and Workarounds.................... 132
24.1. CR383659, CR383662 Inconsistent failures with JSF portlets 132
24.2. CR342124: IllegalStateException due to duplicate client-id 132
24.3. CR384916: IllegalStateException due to duplicate client-id when using certain components such as Tomahawk and Trinidad...... 133
24.4. CR361477 Problems with the integration of JSF portlets with Apache Beehive Page Flows.................................................................. 133
24.5. CR377945 JSF 1.2 suffers from a memory leak during iterative development .............................................................................. 134
25. Appendix 3: The JSFPortletHelper Class ........................... 135
26. Appendix 4: The CleanupPhaseListener Class .................. 147

Hi Peter!
First, I wish to thank you for the great work.
We followed your whitepaper and managed to deploy a JSF portlet on WLS.
But we are not able to register it (consume it) as remote portlet in Oracle Portal 10.1.4. The error log is as follows:
An error occurred while trying to refresh the provider. (WWC-43190)
An error occurred during the call to the WSRP Provider:
java.rmi.RemoteException: serialization error: serialization error:
unexpected null value for literal data; nested exception is:
serialization error: serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
unexpected null value for literal data
Java stack trace from root exception:
unexpected null value for literal data
at
oracle.webdb.wsrp.RegistrationContext_LiteralSerializer.doSerialize(RegistrationContext_LiteralSerializer.java:107)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
oracle.webdb.wsrp.GetServiceDescription_LiteralSerializer.doSerialize(GetServiceDescription_LiteralSerializer.java:88)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
com.sun.xml.rpc.client.StreamingSender._writeRequest(StreamingSender.java:473)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:62)
at
oracle.webdb.wsrp.WSRP_v1_ServiceDescription_PortType_Stub.getServiceDescription(WSRP_v1_ServiceDescription_PortType_Stub.java:63)
at
oracle.webdb.wsrp.client.design.v1.OraWSRP_v1_ServiceDescription_PortType.getServiceDescription(Unknown
Source)Do you have any idea why this happens? Or you can provide some useful links to WLP -Oracle Portal federation?
Thank you and best regards,
PaKo

Problem by providing ADF portlet in Oracle Portal

Hi,
I have created a simple ADF application with one JSF with a simple outputtext label, using Jdeveloper 11.1.1.3.
I created a portlet out of it by Create Portlet Entry and deployed it on weblogic (WL_WSRP).
Then i created a WSRP Provider on Oracle Portal 11g (11.1.1.6) with success, so I put the portlet on a page, when Portal show the page its appear a error message, like this:
Error: Could not get markup. The cookie or session is invalid or there is a runtime exception.
If I create a portlet with JSP page instead of a JSF page its works fine, another situation: when I access the JSF page directly in browser tha page works fine too.
To create the domain for WLS_WSRP I used this document: Doc Id 1058565.1
These are the error messages in the Weblogic logs:
ContentFetcher Unexpected Exception Request Failed:oracle.webdb.wsrp.client.run.WSRPDispatcherException: An error occurred whilst invoking an operation on the Provider name=content-fetcher17 label=wsrpPortlet url=http://ovm063portaltbl.compasso.com.br:8090/portal/proxy/portal/TBLPORTAL_PORTAL/wsrp time=1633ms timeout=65000ms process=Dispatching
An internal error has occurred in method getMarkup. java.lang.NoClassDefFoundError: javax/portlet/PortletRequest at oracle.adf.share.portlet.PortletADFContext.getPortletRequest(PortletADFContext.java:108)
at oracle.adf.share.portlet.PortletADFContext.getUserPrincipal(PortletADFContext.java:141)
at oracle.adf.share.portlet.PortletADFContext.setUserPrincipal(PortletADFContext.java:124)
at oracle.adf.share.portlet.PortletADFContext.setSecurityContext(PortletADFContext.java:119)
at oracle.adf.share.ADFContext.getSecurityContext(ADFContext.java:830)
at oracle.adf.share.portlet.PortletADFContext.initialize(PortletADFContext.java:245)
at oracle.adf.share.portlet.PortletADFContext.initThreadContext(PortletADFContext.java:232)
at oracle.adf.model.portlet.PortletBindingRequestHandler.initADFContext(PortletBindingRequestHandler.java:49)
at oracle.adf.model.BindingRequestHandler.beginRequest(BindingRequestHandler.java:105)
at oracle.portlet.bridge.adf.lifecycle.ADFBindingBridgeLifecycleListenerImpl.onBeginRequest(ADFBindingBridgeLifecycleListenerImpl.java:94)
at oracle.portlet.bridge.adf.context.ADFPortletExternalContextImpl.<init>(ADFPortletExternalContextImpl.java:225) at oracle.portlet.bridge.adf.context.ADFPortletFacesContextImpl.<init>(ADFPortletFacesContextImpl.java:40) at oracle.portlet.bridge.adf.context.ADFPortletFacesContextFactoryImpl.getFacesContext(ADFPortletFacesContextFactoryImpl.java:41) at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:64) at org.apache.myfaces.portlet.faces.bridge.BridgeImpl.getFacesContext(BridgeImpl.java:989) at org.apache.myfaces.portlet.faces.bridge.BridgeImpl.doFacesRequest(BridgeImpl.java:535) at javax.portlet.faces.GenericFacesPortlet.doBridgeDispatch(GenericFacesPortlet.java:498) at javax.portlet.faces.GenericFacesPortlet.doRenderDispatchInternal(GenericFacesPortlet.java:449) at javax.portlet.faces.GenericFacesPortlet.doView(GenericFacesPortlet.java:241) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:243) at javax.portlet.faces.GenericFacesPortlet.doDispatch(GenericFacesPortlet.java:209) at javax.portlet.GenericPortlet.render(GenericPortlet.java:163) at oracle.portlet.bridge.adf.application.ADFBridgePortlet.render(ADFBridgePortlet.java:287) at oracle.portlet.server.containerimpl.ServerImpl.doRuntimeCall(ServerImpl.java:1316) at oracle.portlet.server.containerimpl.ServerImpl.getMarkup(ServerImpl.java:143) at oracle.portlet.server.containerimpl.ServerPerfLogger.getMarkup(ServerPerfLogger.java:559) at oracle.portlet.wsrp.v2.WSRPv2VersionWrapperServer.getMarkup(WSRPv2VersionWrapperServer.java:522) at oracle.portlet.wsrp.v2.WSRPv2ToServer.getMarkup(WSRPv2ToServer.java:11783) at oracle.portlet.wsrp.v2.WSRP_v2_Markup_PortTypeSoapToJaxb.getMarkup(WSRP_v2_Markup_PortTypeSoapToJaxb.java:81) at oracle.portlet.wsrp.v2.WSRP_v2_Markup_PortTypeSoapPerfLogger.getMarkup(WSRP_v2_Markup_PortTypeSoapPerfLogger.java:58) at oasis.names.tc.wsrp.v2.bind.runtime.WSRP_v2_Markup_Binding_SOAP_Tie.invoke_getMarkup(WSRP_v2_Markup_Binding_SOAP_Tie.java:814) at oasis.names.tc.wsrp.v2.bind.runtime.WSRP_v2_Markup_Binding_SOAP_Tie.processingHook(WSRP_v2_Markup_Binding_SOAP_Tie.java:1457) at oracle.j2ee.ws.server.StreamingHandler.handle(StreamingHandler.java:299) at oracle.j2ee.ws.server.JAXRPCProcessor.doEndpointProcessing(JAXRPCProcessor.java:442) at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:1112) at oracle.j2ee.ws.server.JAXRPCProcessor.doRequestProcessing(JAXRPCProcessor.java:333) at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:233) at oracle.j2ee.ws.server.JAXRPCProcessor.doService(JAXRPCProcessor.java:185) at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:485) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.portlet.server.service.ContextFilter.doFilter(ContextFilter.java:101) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Hi,
What errors did you get during indexing?
-Ron

Deploying ADF/JDeveloper portlets in WebSphere Portal

I'd like to use ADF/JDeveloper to build my application, but my customer is already heavily invested on a WebSphere Portal deployment platform. The JDeveloper/ADF documentation has extensive information on creating portlets in various ways, but they all seem focused exclusively on deploying in an Oracle platform. I have tried both the "Standards-Based" as well as the "JSF Portlet Bridge". I have tried to deploy the portlets in WebSphere Portal using both the generated WAR file, as well as by registering the WSRP producer. None work.
With the WAR file, WebSphere Portal seems to import the WAR file just fine, and I can add a portlet to a page, but the portlet always shows as "unavaiable"
With the WSRP producer, I can get something to show in the page, but the functionality within the portlet doesn't seem to work.
I've searched extensively, but cannot locate any documentation or use cases for deploying portlets from JDeveloper into WebSphere Portal. Does anyone have any thoughts?

Dvohra21, again, I apreciate the effort, but I think you're missing the fundamental question.
You've given me two types of articles/links. Some are generic WebSphere Portal documentation about deploying a portlet from a WAR file. Others are Oracle articles about who to generate portlets in JDeveloper, with examples deploying in Oracle/WebLogic servers. Unfortunately I don't have a problem with either of those.
I CAN deploy a portlet WAR file in WebSphere Portal, and sucessfully add it to a Portal page. I have done that with multiple WAR files generated from Rational Application Developer.
I CAN produce a WAR file from JDeveloper, following the instructions in the same resources you included, plus a few others.
The problem is, the WAR file from JDeveloper, does not successfully run on WebSphere Portal. I create a simple Hello World portlet in JDeveloper, and I can generate a WAR file from it, and seemingly deploy to WebSphere Portal. However when I add it to a Portal page, it always displays only a blank box with the text "This portlet is unavailable". This is in the same exact portal page, where the portlet created with Rational Application Developer shows up just fine right along side it.
Bottomline is, although there is a great deal of information an demos about generating portlets from JDeveloper within an Oracle environment, I could not find a SINGLE ONE, that goes through an end to end scenario where it is deployed in WebSphere Portal. Nothing in this forum, nothing in Oracle docs, and nothing I can find on a Google search.

NPE while registering Remote Portlet in Weblogic Portal 10.3

Hi,
I am on Weblogic Portal 10.3 and am trying to create a remote portlet in my portal application. The remote Portlet is hosted on OC4J 10.3.1.1.1 and is consumed properly on Oracle Portal without any errors, however, when I try to access the portlet's wsdl via the Remote Portlet Wizard, I get the following exception while registering.
bq. {color:#3366ff}!ENTRY com.bea.wlp.eclipse.common 1 1 2008-10-06 11:37:28.938{color} \\ {color:#3366ff} \\ !MESSAGE [Portal-ERROR|http://forums.oracle.com/forums/] There was a problem submitting registration for this producer.{color} \\ {color:#3366ff} \\ Reason = ProducerAgent::java.lang.NullPointerException: null{color} \\ {color:#3366ff} \\ !ENTRY com.bea.wlp.eclipse.common 4 4 2008-10-06 11:37:28.938{color} \\ {color:#3366ff} \\ !MESSAGE {color} \\ {color:#3366ff} \\ !STACK 0{color} \\ {color:#3366ff} \\ java.lang.NullPointerException{color} \\ {color:#3366ff} \\ at weblogic.utils.encoders.CharacterDecoder.decodeBuffer(CharacterDecoder.java:188){color} \\ {color:#3366ff} \\ at com.bea.wsrp.util.XmlUtils.decodeBASE64(XmlUtils.java:270){color} \\ {color:#3366ff} \\ at com.bea.wsrp.bind.RegistrationContextImpl.<init>(RegistrationContextImpl.java:44){color} \\ {color:#3366ff} \\ at com.bea.wsrp.client.ProducerAgentImpl.register(ProducerAgentImpl.java:258){color} \\ {color:#3366ff} \\ at com.bea.wsrp.client.ProducerAgentImpl.register(ProducerAgentImpl.java:221){color} \\ {color:#3366ff} \\ at com.bea.wlp.eclipse.wsrp.portletbuilder.wsrp.ProducerAgent.submitRegistrationDocument(ProducerAgent.java:384){color} \\ {color:#3366ff} \\ at com.bea.wlp.eclipse.wsrp.portletbuilder.wizard.wsrp.SelectProducerPanel$RegistrationRunner.run(SelectProducerPanel.java:1425){color} \\ {color:#3366ff} \\ !ENTRY com.bea.wlp.eclipse.common 1 1 2008-10-06 11:37:28.953{color} \\ {color:#3366ff} \\ !MESSAGE [Portal-DEBUG|http://forums.oracle.com/forums/] RegistrationPanel::could not submit registration document: null{color}
{color:#3366ff}
{color}
{color:#000000}This producer is fully WSRP compliant and works perfectly fine with Oracle Portal. Any pointers of where it might go wrong?{color}
Ansuman

Now I am able to display the initial page of the remote portlet. However, when I try to do some operations I m running into one more issue:
[WSRP-Consumer:420733]No markup received from the producer [oraclePortal_producer] for portlet with portletHandle[E:3:default].
Is there anything futher I need to do?
regards,
Ansuman

How to create portlet pages in oracle webcenter 11g?

Hi all,
currently we are using an application with oracle web portal 10g server. Is it possible to do migration all portlet pages 10g portal to 11g webcenter ?
and please clarify how to create a portlet page in webcenter 11g?
Regards
Nagarajan

Hi Nagarajan,
In webcenter there is no concept of portlets.Here you need to have all the portlets as WSRP.
So in a jist, you need to expose your current portlets as WSRP and the same should be consumed in webcenter portal pages.
Hope this make things clear.

Creating iViews Programatically

Hi all,
I have got a requirement to create iviews programatically.
The detailed requirement is :
Intially an excel file which is placed in clients pc will have all the information related to the kind of iViews required, like the name, properties, PCD , of which type etc., Now from portal we need to have the facility to access this excel file and read the information mentioned and create appropriate iViews.
If anyone has already implemented such a kind of requirement or has got any bit of idea on the same can pls share.
Thanks In Advance,
Vipin.

Hi Vipin,
You could instead create an excel sheet with macros which use the data in the excel sheet to create an XML file and then upload that file into the portal to create PCD Content.
Refer to this document, it talks about "How to Automate Content Creation via XML (XML Content and Actions) (NW 7.0)"
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/207a2141-c870-2910-e080-90c920b24f47
Thanks,
GLM

Documention for creating portlets using pl/sql???

Hi,
can anyone help me get links for any kind of documentation about creating portlets using pl/sql for Oracle Application Server Portal 10g
thanks
M

I think this will help out...
Check out Chapter 8, "Creating PL/SQL Portlets" in the Oracle Portal 10.1.4 Developer's Guide.
http://download-east.oracle.com/docs/cd/B14099_19/portal.1014/b14135/pdg_pdk_plsql.htm#BJEFHIBH

Error when creating portlet provider

I tried to call Forms Server application from Oracle Portal as
external application.
External application works fine if I execute link in External
application section.
Problem arrise when I tried to create Portlet Provider for this
external application.
Portlet Provider Implementation style is set to WEB. When I
choose Applay I get error:
Error: An error occurred when attempting to call the providers
register function. (WWC-43134)
An unexpected error occurred: ORA-29532: Java call terminated by
uncaught Java exception: java.io.IOException: Unexpected EOF.13
XML-0121 : (Fatal Error) End tag does not match start
tag 'INPUT'.
XML-0121 : (Fatal Error) End tag does not match start
tag 'FORM'.
XML-0121 : (Fatal Error) End tag does not match start
tag 'BODY'.
XML-0210 : (Fatal Error) Unexpected EOF. (WWC-43000)
An unexpected error occurred: java.io.IOException: Unexpected
EOF.13
XML-0121 : (Fatal Error) End tag does not match start
tag 'INPUT'.
XML-0121 : (Fatal Error) End tag does not match start
tag 'FORM'.
XML-0121 : (Fatal Error) End tag does not match start
tag 'BODY'.
XML-0210 : (Fatal Error) Unexpected EOF.
at oracle.webdb.provider.web.SoapResponseProcessor.getDocument
(SoapResponseProcessor.java:123)
at oracle.webdb.provider.web.SoapResponseProcessor.processSOAP
(SoapResponseProcessor.java:42)
at oracle.webdb.provider.web.HttpProviderDispatcher.dispatch
(HttpProviderDispatcher.java:877)
at
oracle.webdb.provider.web.HttpProviderDispatcher.registerProvider
(HttpProviderDispatcher.java:259)
(WWC-43000)
An unexpected error occurred: Unexpected EOF.
at oracle.xml.parser.v2.XMLError.flushErrors(XMLError.java:208)
at oracle.xml.parser.v2.XMLError.error(XMLError.java:114)
at oracle.xml.parser.v2.XMLError.error(XMLError.java:152)
at oracle.xml.parser.v2.XMLReader.popXMLReader
(XMLReader.java:380)
at oracle.xml.parser.v2.NonValidatingParser.parseElement
(NonValidatingParser.java:968)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement
(NonValidatingParser.java:237)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument
(NonValidatingParser.java:201)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:169)
at oracle.webdb.provider.web.SoapResponseProcessor.getDocument
(SoapResponseProcessor.java:117)
at oracle.webdb.provider.web.SoapResponseProcessor.processSOAP
(SoapResponseProcessor.java:42)
at oracle.webdb.provider.web.HttpProviderDispatcher.dispatch
(HttpProviderDispatcher.java:877)
at
oracle.webdb.provider.web.HttpProviderDispatcher.registerProvider
(HttpProviderDispatcher.java:259)
(WWC-43000)
I found unsolved forum with the same problem on Metalink: Doc
ID: 57590.996
How can I solve this problem?
Is it possible to add external application to portal as a
portlet without creatin a Portlet Provider?
Thanks,
Tomaz Podbersic

Tom,
A Connection timeout normally means that it is a valid
host.domain, but the listener was down or it could not access
that port.
You say that you can reach the URL, is it on the same domain?
Do you need a proxy to contact it. Can the Portal Machine see
it okay?
Sue

How can i download file from a pageflow portlet in Webloigc Portal?

How can i download file from a portlet in Webloigc Portal?
My Question is, when i download files used codes in a pageflow listed below,
it didn't work. but in non-portal environments, it worked well.
How can I download a file from a portlets in portal??
Thx in advanced.
this.getResponse().setContentType ( "application/ms-excel" ) ;
this.getResponse().setHeader ( "Content-Disposition" ,"attachment;filename="
+new String("Excel.xls".getBytes(),"iso-8859-1")) ;
sth.write(this.getResponse().getOutputStream());

i always use an old fashioned method when i have to do this, i create a new jsp that contains a scriptlet that writes to the ServletOutputStream.
<i>outputWriter.jsp</i>
// define your own class to get file here, otherwiser use netui-data:callControl tag
<code><pre>
File file = FileControl.getFile(fileName);
String fileName = (String) request.getParameter("fileName");
response.setContentType(file.getContentType());
ServletOutputStream sos = response.getOutputStream();
InputStream is = file.getInputStream();
for(int i = 0; (i = is.read()) != -1;)
sos.write(i);
sos.close();
</pre>
</code>
i then call this jsp from the jsp to which i forward in my action using a simple url rewrite with file name on the url.
<a href=outputWriter.jsp?fileName=nameOfFileToDownload

Creating portlet programmatically

Hi dev2dev
I want to create portlet programmatically
if there is any hints or package related pls do mail me
Thanks n Regards
Surya
[email protected]

Hi,
I am sure ( although without having testet it myself ) that the administrative EJBs behind the portal administration tool could be used here.
consult the java - doc for theese classes.
Are you sure this is the only solution to the problem ? If you could elaborate on the problem leading to you wanting to create portlets prgrammatically perhaps the community could provide you with another solution if there are any.
- Anders M.

Dynamic creating portlet

Hi,
Is it possible to create portlets dynamically?
For example, I click a button in a1 portlet, and
after IPs and PCs processing, show the results in a2 and
a3 portlets that these portlets did not visible orignally.
Thanks.

It's been that way since the first version of the portal. Annoying that you can't change the style of that table, isn't it? :-)
In a dynamic page, to show the data from a select statement however you want, you can do that with PL/SQL using a cursor for the sql query and looping through and printing the results of the select statement.
If you just need to return the date-time and the user that is currently logged in, you can do something like the following:
<ORACLE>
DECLARE
v_date DATE;
v_user VARCHAR2(100);
BEGIN
v_date := SYSDATE;
v_user := portal.wwctx_api.get_user;
htp.p(TO_CHAR(v_date,'Dy DD-Mon-YYYY HH24:MI:SS'));
htp.br;
htp.p(v_user);
END;
</ORACLE>

Creating Portlet programatically in Portal 4 as in WLCS3.5

Similar Messages

Maybe you are looking for