Portal902 - DB portlets that use page parameters

Hi all.
I am trying to create a plsql portlet that will read the page parameters. I believe that this is the idea, right? Well, I don't know how to do it. Can someone tell me how to do it? Or tell me where to find an example?
Thanx, Mere. I had an example in which parameters were passed from one report to another:
Report 1: summary report
SQL report, on scott.dept:
select htf.anchor('http://<server>:<port>/servlet/page?_pa
geid=<page id>&_dad=<dad>&_schema=<schema>&_mode=3&dept='||deptno, deptno)
aaa, dname, loc from SCOTT.dept
The url here is the page url with extra parameter for dept, the bind
variable in the detail report
Report 2: detail report
SQL report, on scott.emp
select * from scott.emp where deptno = :dept
Add the following PL/SQL code in the "before displaying the page"
<portal schema>.wwv_name_value.replace_value(
l_arg_names, l_arg_values, p_reference_path||'.dept',
<portal schema>.wwv_standard_util.string_to_table2(nvl(get_value('dept'),
10)));
Build a page and include these 2 portlets, then when you click
on the link of the summary report, the page will be refreshed,
and the detail report changed based on the data from the summary report.
Hope this helps

Similar Messages

How to use page parameters with inline rendering portlet

I am trying to use the inline rendering portlet. Basic functionality works fine.
What I am trying to do is make the inline rendering portlet use a page parameter. Is this possible?
I have read pdk articles, but nothing seems to have what I need.
Any ideas are appreciated.

Perhaps i might have missed something, but what do you mean by the inline rendering portlet? Are you referring to the URL services portlets that rendered content inline (in the same Portal context & window without popping a new window)?
I would be able to look into this if you could elaborate on the issue at hand.
Regards,
Abhinav

Error running Portlet that uses JSTL

Anyone have any issues running a JSR 168 Portlet in Sun Portal Server that is running on Sun Web Server 7.0 update 2? This same portlet runs fine in the Portlet Driver application running on Glassfish. Seems to be an issue in the servlet/JSP implementation on Sun Web Server.
service-j2ee reports: StandardWrapperValve[jsp]: PWC1406: Servlet.service() for servlet jsp threw exception
java.lang.NoSuchMethodError: javax.servlet.jsp.PageContext.getELContext()Ljavax/el/ELContext;
at org.apache.taglibs.standard.tag.common.core.SetSupport.doEndTag(SetSupport.java:140)
at org.apache.jsp.jspf.summary_jspf._jspx_meth_c_set_0(summary_jspf.java:168)
at org.apache.jsp.jspf.summary_jspf._jspService(summary_jspf.java:110)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:105)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:917)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:359)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:403)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:311)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:917)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:391)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:297)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:178)
at mil.army.usaac.portlet.onthefloor.LogBackFilter.doFilter(LogBackFilter.java:43)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:178)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:270)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:241)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:182)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:160)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
at com.sun.webserver.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:149)
at com.sun.webserver.connector.nsapi.NSAPIConnector.service(NSAPIConnector.java:995)

Try bundling JSTL and Standard jars in the webapp and see whether the issue is resolved.
Else write a simple webapp that uses JSTL and deploy on Sun Web Server 7.0 update 2 and see whether you see the same exception. You can post the issue to WebServer forum.
Regards,
Deepak

Using Page Parameters to Construct a URL

Hi. I wonder if someone could tell me if this is possible. I have a URL which runs a report in Discoverer Plus. This report has parameters in it. If I want to I can pass in the parameter values in the URL e.g. param_Year=2005. What I would like to do is use a page parameter form to collect my report parameter values. In turn, I would then like to pass these values into the URL to run the report. So my page parameter form would have say 2 fields, myYear and my Period. I would then like my URL to directly reference these values: http://server/discoverer/plus?workbook=Test&param_Year=myYear&param_Period=myPeriod.
Does anyone know if this is possible? Thanks in advance.

Hey Eric,
The client gave you a legitimate file.
All he gave you was a 16x9 image with a PAR of 853x720 (0.844).
What I would do is change the pixel aspect ratio to 1:1 on the delivered file from your client. Once you do this, you will have a 720x480 (anamorphic image).
If you go to your QT movie properties (Quicktime PLayer > Window > Show Movie Properties or Apple + J [macros]) and highlight the Video Track and select the "Visual Settings" tab - Check OFF the "Preserve Aspect Ratio" checkbox and manually type in 720 x 480 in the "Scaled Size" edit boxes. Make sure that "pixels" is selected on the drop-down.
I am sure this is how you want your video to look.
Be aware that this ONLY changes the DAR, but you should be OK if you use Compressor to compress your video.
Save out a new file and you should be good to go...
Mike M.

Unable to bind portlet parameter with page parameter in webcenter portal

Hi All,
I am trying to bind portlet parameter with the page parameter so that I can ahieve some business requirements.
Here is what I did,
In my Portlet producer application:
1) Created standards based portlet (jsr 286) with view.jspx and edit.jspx with rest of the things being default.
2) In my portlet.xml created two parameters and assigned these parameters to the portlet created above.
3) In the view.jspx added couple of output label adf components in the page.
4) deployed this to integrated weblogic server.
In my WC portal application:
Created a new page and added the portlet to this page( WSRP connection already exists).
deployed portal application on integrated server.
In the edit mode of the page I added one page parameter(Param1) and some default (constant) value added.
What I want is this:
when Param1 value is One display first output label and
when Param1 value is Two display second output label.
I am using jdev 11.1.1.5.0 with integrated weblogic server.

There is no need to use page parameters for this.
You also have two types of parameters depending on what you want...
1) Preferences: these parameters can be used on a user based level. This means that users can personalize the portlets. When a user change the value of a preference, it is only applied for that specific user
2) Public parameters: these parameters are used to customize the portlet. The value you set in these parameter apply for all users.
I have made a simple example to show these two differences: http://www.yonaweb.be/PortletTest.zip
The portlet has 4 inputText on it. The first two can be set by specifying One or Two into the preference.
The other 2 inputText uses the value of the public parameter.
You should only deploy the portlet and consume it in a webcenter application. In the webcenter application, you don't need to do anything special. All is done in the portlet.
I am guessing you don't have written the code that will get the value of the parameter:
in case of a preference you will get the value by following code:
   PortletRequest request = (PortletRequest)FacesContext.getCurrentInstance().getExternalContext().getRequest();
   PortletPreferences preferences = request.getPreferences();
   return preferences.getValue("outputparam", "One");In case of a public parameter (for customization instead of personalization) you use following code to retreive the value of a public parameter:
PortletRequest req = (PortletRequest)FacesContext.getCurrentInstance().getExternalContext().getRequest();
String param = (String)req.getParameter("PublicParam");
if(param == null)
      return "Three";
return param;This code can also be found in the sample portlet application.

Multiple instances of same portlet on same page

Dead horse, I know, but I am afraid I still don't get it:
I use ONE JSP to extract data as XML, parse the data using XSL, render it. A portlet has some variables that may vary between instances of the same portlet on the same page. I am familiar with this document: http://portalstudio.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/PDK/ARTICLES/PRIMER.PORTLET.PARAMETERS.EVENTS.HTML
but still don't know how to make sure that every portlet gets it's 'own' parameters passed. I pass them and attempt to grap them in the jsp using request.getParameter().
I have played with making each parameter unique using the portlet instance name followed by a '.' and a name, e.g. 35024_LISTPORTLET_49519321.next_page=10.
Setting passAllUrlParams in provider.xml to true helps getting the parameters through, but the side effect is, of course, that all instances get mixed up. Setting it to false does nothing.
PLEASE, is there, somewhere, a document that tells us EXACTLY how to do this? JDev 10g, as10g.
Tnx.

Have you read the Public Portlet Parameters Support section of the Portal Developer's Guide?
The question is who passes the parameter to your portlets. If the parameters are passed from within the portlet instance itself, use qualified private portlet parameters. If they're passed from the outside, use page parameters and public portlet parameters.
Hope this helps.
Peter

Enhancement Request : Subscriptions where IR uses Page Items.

I'd like to request an Enhancement.
I'd like report subscriptions to keep track of the current values of any page items in the sql statement when the subscription is stored.
Currently any Interactive Reports that use page items run fine interactively, but subscriptions fail due to the page items having no values.

Oh ok I see what you're trying to do but that's not what I meant.
1. If your IR filters based on a page item and is a subscribable report, you have no choice but to work a NVL (or some other means) in there in order to make a true condition when the page item is null or nonexistent in order for the report to work at all during subscription.
2. If you never want the user to be able to query all rows in the application (that is, force them to enter something in the page item), you'll need a not-null validation on the page so when they submit their page item change that it validates not-null.
3. Use the filter in the IR (but NOT referencing a page item) such that the user can save/subscribe to an IR with the desired filter such that they get the properly-filtered named IR.
Does that make sense?

Disadvantages of using page flows

Hello Friends,
I am using page flows for the first time. I would also need to run the web application under another j2ee server. I know that we can use the portability kit to do this transformation.Even though I understand that using page flows have certain advantages, I wanted to know whether there are disadvantages to using it too?
Some specific questions I had was:
1. Does using page flows slow down the web application?
2. Does using page flows increase the web app size?
3. Does it make it difficult to maintain?
4. Does using the portability kit have some disadvantages?

Hi Gabriel,
using BPm is always advantageous only thing is that complex scenarios are named as BPM.So it is complex
once you get the idea of BPM then no disadvanges.
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm - Walk through BPM
/people/siva.maranani/blog/2005/05/22/schedule-your-bpm - Schedule BPM
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - Use of Synch - Asynch bridge in ccBPM
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] - Use of Synch - Asynch bridge in ccBPM
**PS:Reward points if useful**
Regards,
Sumit Gupta

IPC Between Two ADF Portlets on Same Page using Events Failure

Considering that a full page submit is required for the passing of parameters to work properly, I am trying to use IPC Events to pass a parameter from one ADF Portlet to another. There are no good examples out there, but I am trying to use what is out there in many different generic forms to make this happen with no success.
One portlet contains an ADF Table with a select column, I have a BackingBean to process the choosing of a row and that value is being retrieved and I am calling the set event.
public void selectPatient(ActionEvent e) {
FacesCtrlHierNodeBinding node = (FacesCtrlHierNodeBinding) tblPatients.getSelectedRowData();
String username = node.getAttribute(0).toString();
System.out.println("Selected Patient: " + username);
ActionResponse response = (ActionResponse)FacesContext.getCurrentInstance().getExternalContext().getResponse();
response.setEvent("selectPatientResult", username);
I then have a second portlet that is supposed to retrieve the value being passed from within the portlet class and then the second ADF portlet is supposed to display. I will eventually do more work with the value, but I am just trying to get the events to work properly first. Here is the code within the receiving portlet class:
public class drugallergies extends ADFBridgePortlet {
@ProcessEvent(name="selectPatientResult")
public void processSelectPatientEvent(EventRequest request, EventResponse eventresponse) throws PortletException, IOException {
Event event = request.getEvent();
String username = (String)event.getValue();
System.out.println("Selected Patient: " + username);
eventresponse.setRenderParameter("patient", username);
I have also made sure that I have put the following within my web.xml file for the application so that the events are being passed as portlet events and not faces events. I am still fairly new to ADF, but not to portals or portlets, which is why I am going this route.
<context-param>
<description>Allows for fired events to go to the portlet and not to the faces layer</description>
<param-name>javax.portlet.faces.autoDispatchEvents</param-name>
<param-value>false</param-value>
</context-param>
I am never seeing the receiving event get processed, meaning that I never see the println get processed with the receiving value. Please help because there are no examples out in the world for going this route. There are examples, but they require you to create an ADF application first and then convert the application to a portlet. I am using the Portlet Creation wizard within JDeveloper but creating ADF based pages for the Views modes.

Wait... You have to make a distinct difference between portlet events and contextual events in ADF.
Contextual events in ADF can be converted to portlet events.
If the full refresh of a portlet is an issue for you then even contextual events will not solve your problem.
Regardless the use of parameters or events, portlets do not support partial page rendering or ajax. In order for a parameter to pass or an event to be triggered, it need to have a reference to the ActionResponse or RequestResponse. If they don't have the proper reference they will not be able to trigger the event.
In the case you are talking about, the selection of a record, this won't be able to trigger an event because the selectionModel will be triggered by a partial submit.
The only work around for this problem is by adding a "select" button that will do a full submit.
This is not a limitation of ADF, it is a limitation of the portlet standar because the standard itself does not have anything that supports partial page rendering or ajax...

Portlet Chart error message with page parameters

I have a perplexing problem.
We're using portal 9.0.4. I've created a chart from a sql query using the portal builder tools. It's a complicated query with two parameters that have default values defined. The chart will run as a portlet from the portal provider edit page just fine.
I can place the chart portlet on a page without hooking up the page parameters and it runs just fine from the default values. However, when I hook up the page parameters to the chart parameters from the page properties area, the chart no longer works. It displays "Error Message" in the portlet header area with no other error messages. The other portlets continue to work just fine.
I've double checked the page parameter settings. I've built a second chart, and the same thing happens when I hook up the page parameters to the portlet on the page.
I traced through the portlet code in the generated package, and it seems to be failing on this statement:
l_cursor := PORTAL.wwv_user_utilities.bind_query (
p_module_id => 1182363588,
p_query => l_query,
p_arg_names => l_arg_names,
p_arg_values => l_arg_values,
p_bind_vars => PORTAL.wwv_standard_util.string_to_table2('p_grp_id:p_org_id'),
p_var_types => PORTAL.wwv_standard_util.string_to_table2('ARRAY:ARRAY'),
p_bind_null => true,
p_mode => p_mode,
p_prefix => p_reference_path);
If I comment this line and everything after it out, the portlet runs, although none of the chart is displayed the portlet header shows the correct title. If I uncomment this particular line, then the portlet errors out with a "Error: The listener returned the following Message: 404 Not Found" message.
Anyone have any ideas please??

Look at your code. Count <body> tags. How many do you
get? Yeah - that's
wrong. You didn't follow the video....
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"camelbreath" <[email protected]> wrote in
message
news:g680gh$3c$[email protected]..
> I'm not sure if this is a PM issue or a DWCS3 issue. The
only way to find
> out
> is to ask.
> I have gone through the process of creating a a library
item of a
> PopMagic menu according the the video provided by P7.
Works well.
> Then I added the library item to an existing DWCS3
template and saved
> it. When I attempt to create "new from template" page
from the template
> menu, I get this error message
>
>
http://www.jdcdemo.com/blf/error.html
>
> If I do the same with a template without the menu, the
> error message goes away.
>
> If I create a page with from a template where I've left
an editable
> region for the menu and then insert the menu and save
the page, I also
> get the error message, but the page seems to work ok.
>
> Since I can't create a new page with the template, I
opened it and saved
> it as
> a page:
>
>
http://www.jdcdemo.com/baim/BLF8/error-message.html
>
> What is going on here and is there a fix?
>
> Thanks,
> Joe
>

Passing parameters from portlet to portlet on same page

Hi,
can anyone please give me an example with the code. I have read that i should be using some api's but , don't know where to write them.
Thanks.

Hi,
What version of portal are u using.We have introduced the concept of Page Parameters in Portal 902 release which would do exactly the same thing. Where in a page parameter can be used b/w portlets on a page.
Thanks,
Anu

Clearing Page Parameters After Use

Whenever a parameter is sent to a page, either from a portlet event or otherwise, the parameter remains active accross multiple requests to the same page. This causes a problem in my particular scenario.
Consider a root page that has 2 tabs. Tab 1 has a portlet that raises an event and populates a parameter that is passed to the same page for use by another portlet in Tab 2. This works fine the first time the event is raised. However, multiple accesses to Tab 2 by means other than the event need to use a default value. But this only works if the event parameter does not exist.
Is there a way to set up my scenario so that the event parameter is cleared after its use?

Hello,
In your onchange event of the select list you can put some code like: onchange="javascript:$x('P1_POSTAL_CODE').value = '';$x('P1_ADDRESS').value = '';"
Instead of the inline javascript you can also create a function in javascript and just call the function in the onchange event.
I'm not sure anymore if it also works in 3.1.1 but in the latest version of APEX you can use $v('P1_POSTAL_CODE') = ''
Hope that helps.
Regards,
Dimitri
http://dgielis.blogspot.com/
http://www.apex-evangelists.com/
http://www.apexblogs.info/
REWARDS: Please remember to mark helpful or correct posts on the forum

Passing Page Parameters to a JSR168 Portlet - Enable Portlet Params

We have created a JSR168 portlet in JDeveloper. Once an instance of that portlet is added to a portal page, we want the portlet instance to also received a render request parameter from the page it has been placed on.
I know how to physically add/associate page parameters to a portlet via the portal's page properties tab. However, I am not sure how you configure the JSR168 portlet so that it has parameters that you can associated to the page parameter. Whenever I try to associate parameters to my portlet, it indicates that I have "no parameters".
Is there a special method to configure these parameters within the portlet so that they show up on the page property's parameter tab? Do I need to create entries in the portlet.xml file to enable this? Is there a special configuration setting on the provider?
Any help on this would be greatly appeciated.
Thanks,
Tony

Hi Tony,
As you said in your post,
"I know how to physically add/associate page parameters to a portlet via the portal's page properties tab. However, I am not sure how you configure the JSR168 portlet so that it has parameters that you can associated to the page parameter."
I think you first need to declare the public portlet parameters in the provider.xml of your JDeveloper project, eg.
<inputParameter class="oracle.portal.provider.v2.DefaultParameterDefinition">
<name>PortletPara_MainCat</name>
<displayName>PortletPara_MainCat</displayName>
<description>PortletPara_MainCat</description>
</inputParameter>
Then, on the page you add the portlet, you will see the declared portlet parameters in the parameter tag page. Finally, link the page parameters with portlet parameters.
thanks
George (HK)

Repost:Use Page style feature for portlet

All,
How do i simulate the 'use page style' feature for a custom portlet ? Currently, I have to hard code the style.
thanks

The following is from one of the sample portlets (comments incl):
Display the content of the portlet in the show mode.
Use the wwui_api_portlet.portlet_text() API when generating the content of the portlet so that the output uses the portlet CSS.
htp.p(wwui_api_portlet.portlet_text(
p_string => 'Hello World - Mode Show'
,p_level => 1
I assume this is what you are looking for--the level would be the Portlet Text level, and you could substitute a parameter.
HTH!

Survey portlets that can only be used once

All, I would like to create a survey portlet (or use an existing one) to do the following:
1) A user could define the criteria of the survey through a simple interface (i.e. data form)
2) The end user would see the survey on their default home page (this part is pretty simple).
3) Once the user responds to the survey, the survey portlet is replaced on the users home page by the results of the survey and the user can no longer respond to the survey (enforce a "respond-once" policy).
Questions: Does a portlet like this already exist? If so, where can I find it? If not, what is the easiest solution for creating this type of functionality?
Thanks,
Jon.

Hello, Not sure if this functionality already exists or not, but what you can try doing is this.
1. create a group with all users who are to take the survey
2. set permissions on the survey portlet to only allow people in this group to take the survey
3. With the assumption that you're dumping this data to a database table, create a trigger that will remove the user from the group when the user does a submit. (you can get the current user using portal.wwctx_api.get_user in the trigger). I can not think of it right now, but there are api's which you can call to remove a user from a group.
I hope this helps.

Portal902 - DB portlets that use page parameters

Similar Messages

Maybe you are looking for