WSRP Portlet and Default Minimized Property

Good Morning, i'm working with Oracle WLP 10.3.4 and i have a problem with Default Minimized Property for a Remote Portlet.
I set this property to true for a portlet and if i run it in a local environment this portlet show, correctly, itself minimized.
When i use the same portlet like "remote portlet" -configuring the producer from the administration console- it is not minimized.
There is no way, for a remote portlet, to show itself minimized by default?
Thanks
Alessio

Hello,
Many thanks for this quick feedback. It does work.
We were configuring our producers & portlets directly through WLP admin console : we were expecting WLP to recognize automatically this "defaultMinimized" flag from the remote portlet and configure the proxy portlet with this flag set as same. It is indeed not the case, so we did as follows :
- Create proxy portlet on our consummer application, with defaultMinimized=true
- Add this portlet to our .portal file
Thanks again.
FLC

Similar Messages

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.

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.

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

How do you set a default format property for a formula defined in the AWM?

Is there a way to define a default format property for a formula that I create in the AW?
For example, if I define a formula in AW I can assign it a datatype of decimal. But what property do I need to add if want that formula to by DEFAULT always display a certain way, regardless if I use the Discover Plus with OLAP option or OracleBI Spreadsheet Addin?
Example: want to display it by default, in the AW cube, as being associated to a format of 00.0000 or 00.0000% or $###,##0.00 etc. This way, no mater what tool I use to view the cube, it will by default inherit my default format (set in the AW).
Thanks.

Okay, but if I use the out-of-the-box products Oracle provides (ie: Discover Plus with Olap, and the OracleBI Spreadsheet Addin) I still dont understand what my solution is?
The only other solution we tried was to create formulas using AWM template files. The issue here is trying to find out what property syntax needs to be added to the XML code, so that my formula, by default, is associated to a certain formating style (ie: 00.00). And then when you reference that formula in those out-of-the-box Oracle products, it displays as expected.

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 Portlets in Oracle WebCenter: transforming task flows(ADF) in portlets

I am doing some research on the portlets offered by WebCenter, but I have some problems related with transferring parameters between them. My idea was to create 2 portlets: a department portlet where I can chose a departmentId which is sent as a parameter to the second portlet, employees, so I will have a table with the corresponding employees from the specified department. These 2 portlets are constructed based on some page flows. The department portlet works fine, but with the employees portlet, I have some problems.
The JSP page fragment corresponding to the employees has a table based on a ViewObject which has behind him a query based on a bind variable. I have created an EmployeesBean, where I have the method that takes the received parameter and executes the query with this bind variable. Here is the code:
import javax.el.ELContext;
import javax.el.ExpressionFactory;
import javax.el.ValueExpression;
import javax.faces.application.Application;
import javax.faces.context.FacesContext;
import oracle.adf.view.rich.context.AdfFacesContext;
import oracle.jbo.ApplicationModule;
import oracle.jbo.Row;
import oracle.jbo.ViewObject;
public class EmployeesBean {
private static final String DEPARTMENT_NUMBER_KEY = "DEPTNO";
private static final int DEPARTMENT_NUMBER_NULL_VALUE = -1;
public EmployeesBean() {
super();
public void getEmployees(String deptno) {
System.out.println("enters in getEmployees()");
int filterDeptno = findDepartmentValue(deptno);
FacesContext facesContext = FacesContext.getCurrentInstance();
Application app = facesContext.getApplication();
ExpressionFactory elFactory = app.getExpressionFactory();
ELContext elContext = facesContext.getELContext();
ValueExpression valueExp =
elFactory.createValueExpression(elContext, "#{data.AppModuleDataControl.dataProvider}",
Object.class);
ApplicationModule am = (ApplicationModule)valueExp.getValue(elContext);
ViewObject emplVO;
emplVO = am.findViewObject("EmployeesVO1");
emplVO.setNamedWhereClauseParam("deptno", filterDeptno);
emplVO.executeQuery();
Row r = emplVO.first();
System.out.println(r.getAttribute("FirstName"));
public void setDepartmentNumber(String deptno) {
selectDepartment(deptno);
public void selectDepartment(String deptno) {
System.out.println("aici e problema");
AdfFacesContext afContext = AdfFacesContext.getCurrentInstance();
System.out.println(deptno);
afContext.getPageFlowScope().put(DEPARTMENT_NUMBER_KEY, deptno);
public int findDepartmentValue(String defaultValue) {
AdfFacesContext afContext = AdfFacesContext.getCurrentInstance();
String deptno =
(defaultValue == null ? (String)afContext.getPageFlowScope().get(DEPARTMENT_NUMBER_KEY) :
defaultValue);
return (deptno == null ? DEPARTMENT_NUMBER_NULL_VALUE :
Integer.valueOf(deptno));
I have also dragged on the employees.jsff the getEmployees() method so if I go to page definition I have there a binding, which will determine the getEmployees method to be executed every time an event appears. All this mixed with the departments.jsff works in a .jspx page if I create the Event mapping
Now I am trying to transform this task flow into a portlet. After I create a portlet entry for the page flow, I need to create a navigational parameter, and I am doing this in the employees.xml:
<input-parameter-definition>
<description>Main context parameter</description>
<display-name>Department Number</display-name>
<name>deptno</name>
<value>#{pageFlowScope.contextProvider.departmentNumber}</value>
<class>java.lang.String</class>
</input-parameter-definition>
<managed-bean>
<managed-bean-name>contextProvider</managed-bean-name>
<managed-bean-class>view.EmployeesBean</managed-bean-class>
<managed-bean-scope>pageFlow</managed-bean-scope>
</managed-bean>
Everything works fine, but when I am trying to use this as a portlet in a WebCenter application, when I select a department the departmentId is transferred to the employees portlet, the selectDepartment is called, but the getEmployees() is never called(the event is not propagated), so no data is returned in my table. I'm a beginner in portlets and I can't see what the problem is. Can anyone give me some ideas?

issue is described in Unable To Register EBS WSRP Producer In Webcenter (Doc ID 1567314.1)
Cause
The root cause is the current implementation of JOC within Oracle Applications which initiates JOC within the Applications rather than at the J2ee level.
Bug 9850207 - DOC: PORTLET PROVIDER REGISTRATION ISSUE WITH OACORE PROCESSES > 1
Solution
There are two workarounds for the issue described
1. Reduce number of J2EE OACore (OC4J) porcesses to 1.
2. Add to the OACore J2ee startup parameters -Doracle.ias.jcache=true
Note: This changes have to be done in the Oracle E-Business Suite portlet producer installation.

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

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.

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.

Create and Register Custom Property Panels

Is there anyone who worked on "Custom Property Panel" in Webcenter? However, I have tried something using the following link but it seems not working.
http://docs.oracle.com/cd/E16340_01/webcenter.1111/e10148/jpsdg_page_editor_adv.htm#CHDCJGEC
Can anyone suggest me the possible approaches step by step?
Thanks in advance.

Hi again!
Section 20.2, "Creating Oracle Composer Add-Ons": Refers to Oracle Composer buttons that appears in top of it like "Page properties" or "View". In this image http://4.bp.blogspot.com/-o0-wHhGzAg/TrgeohaGM8I/AAAAAAAAASQ/yfQqqU8faY/s1600/Composer6.png "Chane Logo" is a Composer addon (panel).
Section 20.3, "Creating Custom Property Panels": Refers to add more tabs/configurations by default provided by Oracle Composer to configure the components added in the page. For example "Parameters" tab. In this image http://1.bp.blogspot.com/-G5lnUwO_mhM/TrgeqZlTT_I/AAAAAAAAASY/vTvznOakpL8/s1600/Composer7.png "Display options" and "Style" are property-panels
Regards.

Deferred syntax error while integration WSRP Portlets

Hi,
I have a webcenter application, in which :-
1. I have created WSRP Producer portlet from connection>New Connection>Portlet Producer in application Navigator.
2. Portlet Producer is created succesfully and started appearing under the resource pallet.
3. Later I create a new .jspx page and ran the page. It ran succesfully
4. Then I drag that portlet on the .jspx page and ran it again , then it errored saying :
"Error: Encountered deferred syntax #{ in template text. If intended as a literal, escape it or set directive deferredSyntaxAllowedAsLiteral"
If require I'll send the entire stack trace.
Please let me know if have any pointers, any leads will be really helpful.
Thanks,
Amrita

Hello
Did you resolved this?
I've deployed 11.1.1.6.0 and applied patch 14361677.
I've deployed my portlet to a custom portal and using EM, attached the WSS 1.0 SAML Token with Message Protection Service policy. I registered the WRSP portlet and specified WSS 1.0 SAML Token with Message Protection under the security section.
The portlet works fine in composer - it's when I save the page that I am finding problems.
Once I saved the page and try to stress test the portlet (i.e., press the button twice for instance), an error page is displayed indicating a time out.
If I navigate to another page and return to my page, the portlet does not render.
When I log out of WebCenter, the exception described in your post is thrown.
It would be great if Oracle provided documentation we are looking for.

WSRP Portlet and Default Minimized Property

Similar Messages

Maybe you are looking for