Hi Avinash,
.. how to put this nicely... I can't, yuck. IPC to do this is gross, and completely unecessary if you ask me. IPC was introduced in Portlet 2.0 to allows portlets to talk to each other in a safer way than putting things in the top level request or session, but truthfully, after more than 10 years working with portals? I think there has been exactly one, maybe two times that I have found Eventing useful. Up to you I guess, but I wouldn't do that.
.. I am hardcoding the pid as an example to show you that there is an attribute on the tag you can use. Of course you would get the pid dynamically. There is a method on the LayoutLocalService that you can use to get a Layout for a group based on the friendly url. I am assuming that you would know the page the other portlet lives on -- for example /search or /details or something like that. So you would look up that plid either server side in your Command or Portlet class and pass it to the JSP, or handle it through a portlet configuration ir just grab it via service in the JSP using a scriptlet. I didn't realize you wanted me to actually code it for you. If you do, then you might want to actually provde me all the details
... seems to me that maybe you need to read a little more about portlets and how they work. The answer I gave you, to create a render URL targeting the portlet and page, is all you need to do to achieve this. The public render parameter (which is IPC in fact) allows the parameter, which is not considered secure, hence why it is PUBLIC, to be available to ALL the portlets on the page. Once you configure it, it will make sense since the resulting page url has a p_r_p in the query string, and since all portlets can access the public url, they can see the parameter.
embedding the portlet in the theme doesn't matter -- that just means that it is automatically there on every page so that you don't have to manually pass it. So let's say you have this ..
1. Home Page -- embedded portlet
2. Search Results Page -- embedded portlet and results portlet
You user is on the homepage and types in some keywords into your embedded (search) portlet. Your form uses a RENDER URL that will pass the keywords value as a parameter (dynamically). Because you have configured the keywords to be a PRP in both portlets, when the form is submitted it will go into the url and because your RENDER URL is specifying a portlet that is on another page, the request will be routed to THAT portlet. That portlets RENDER method will be able to see the keywords, so it can read them, perform the search, and then render IT'S view.jsp which is on the Search Results Page.
Basically, the render url will take the user to the other page automatically because that it what you have configured the url to do by specifying the plid for the new page.
Thanks for the reply but I am using IPC via public render parameter and I have 1st portlet using <liferay-portlet:actionURL>
and in action method of first portlet I use processAction to set the renderResponse which will be used in the 2nd portlet.
.. how to put this nicely... I can't, yuck. IPC to do this is gross, and completely unecessary if you ask me. IPC was introduced in Portlet 2.0 to allows portlets to talk to each other in a safer way than putting things in the top level request or session, but truthfully, after more than 10 years working with portals? I think there has been exactly one, maybe two times that I have found Eventing useful. Up to you I guess, but I wouldn't do that.
Also in the example you mentioned you are hard coding the plid .
.. I am hardcoding the pid as an example to show you that there is an attribute on the tag you can use. Of course you would get the pid dynamically. There is a method on the LayoutLocalService that you can use to get a Layout for a group based on the friendly url. I am assuming that you would know the page the other portlet lives on -- for example /search or /details or something like that. So you would look up that plid either server side in your Command or Portlet class and pass it to the JSP, or handle it through a portlet configuration ir just grab it via service in the JSP using a scriptlet. I didn't realize you wanted me to actually code it for you. If you do, then you might want to actually provde me all the details
Is there some other way to dynamically open the portlet added in any page of liferay when clicked from one portlet?
And if I use <liferay-portlet:renderURL> in 1st portlet how to pass the data from one portlet to another portlet using public render parameter?
Also my first portlet I load via theme in the header.
... seems to me that maybe you need to read a little more about portlets and how they work. The answer I gave you, to create a render URL targeting the portlet and page, is all you need to do to achieve this. The public render parameter (which is IPC in fact) allows the parameter, which is not considered secure, hence why it is PUBLIC, to be available to ALL the portlets on the page. Once you configure it, it will make sense since the resulting page url has a p_r_p in the query string, and since all portlets can access the public url, they can see the parameter.
embedding the portlet in the theme doesn't matter -- that just means that it is automatically there on every page so that you don't have to manually pass it. So let's say you have this ..
1. Home Page -- embedded portlet
2. Search Results Page -- embedded portlet and results portlet
You user is on the homepage and types in some keywords into your embedded (search) portlet. Your form uses a RENDER URL that will pass the keywords value as a parameter (dynamically). Because you have configured the keywords to be a PRP in both portlets, when the form is submitted it will go into the url and because your RENDER URL is specifying a portlet that is on another page, the request will be routed to THAT portlet. That portlets RENDER method will be able to see the keywords, so it can read them, perform the search, and then render IT'S view.jsp which is on the Search Results Page.
Basically, the render url will take the user to the other page automatically because that it what you have configured the url to do by specifying the plid for the new page.
Ok, I think I see what is happening. This is a bit of a mess -- I'm guessing you are maybe new to Liferay? 
Looking at your code.
1. I would enocourage you to use the aui taglibs so that you don't have to add the namespace to yourself
2. I removed the method from the form -- you don't need a post in this case
3. You have some parameters in the Render URL that are not required because they are in fact the defaults
Now the reason it's not working. When you define your render url you are doing this.
That tag is put together server side, when the page is being assembled which means your user has not yet entered any data. So the first time you go to the page, the parameter will contain a value of blank. So when you hit the submit button, you send across blank -- even though your user has entered ABC. On the results page you now created a render url with ABC. So the user enteres EFG, but your render url has ABC as the parameter. This is why you are always one behind. What you shoud be doing is this:
NOTE: This code is untested as I have no project to run it through -- so all of this is from memory
The javascrpt has no value. All it is doing is outputting the wrong value (not the one entered by the user) and submitting the form, so I deleted it. The render url only needs to provide the target portlet and page. You set the form action to be the render url and the parameters in your form will be passed over automatically. Notice though that in my version the render url has no parameter defined in the tag itself. But, when you click the submit button, it will include the form parameters because that is what a submit action does. The input field is RENAMED to a name that must MATCH your public render parameter name. This way Liferay will detect that this parameter is supposed to be public and will put it in the correct parameter map. I've also changed your form to use the AUI taglibs so that you need only specify the name. The namespace is added automatically, and the id will be populated based on the name field (they will have the same value).
I also noticed that you have a hidden field with _3_groupId. The _3_ is the portlet namespace for the search portlet in 6.2, so you don't need that here, groupId alone should suffice but if you are hard coding it to "0" to mean a global scope to retrieve content across all sites (that's what it means for the search portlet) then I would argue you can simply omit it as a parameter altogether and just implement that global scope logic in your handler.
Looking at your code.
1. I would enocourage you to use the aui taglibs so that you don't have to add the namespace to yourself
2. I removed the method from the form -- you don't need a post in this case
3. You have some parameters in the Render URL that are not required because they are in fact the defaults
Now the reason it's not working. When you define your render url you are doing this.
<liferay-portlet:renderurl var="SearchAction" windowstate="normal" portletmode="view" portletname="MySearchPortletResult_WAR_liferaymysearchportlet" plid="<%=plid%>">
<liferay-portlet:param name="mysearchresponse" value="<%=query%>"></liferay-portlet:param>
</liferay-portlet:renderurl>That tag is put together server side, when the page is being assembled which means your user has not yet entered any data. So the first time you go to the page, the parameter will contain a value of blank. So when you hit the submit button, you send across blank -- even though your user has entered ABC. On the results page you now created a render url with ABC. So the user enteres EFG, but your render url has ABC as the parameter. This is why you are always one behind. What you shoud be doing is this:
<liferay-portlet:renderurl var="SearchAction" portletName="MySearchPortletResult_WAR_liferaymysearchportlet" plid="<%=plid%>" />
<div class="search" id="mysearch-new-container">
<aui:form name="SearchForm" action="<%=SearchAction%>">
<div id="mysearch-new-container-top">
<aui:input type="text" cssClass="searchtext" size="30" name="<%=SEARCH_QUERY%>" list="suggestion-datalist" id="mysearchresponse" placeholder="What are you looking for?" onkeypress="doAutoComplete()" autocomplete="false" />
<datalist id="suggestion-datalist"></datalist>
<aui:input type="hidden" name="groupId" value="0" />
<aui:input type="submit" cssClass="button" value="search" />
</div>
</aui:form></div>
NOTE: This code is untested as I have no project to run it through -- so all of this is from memory
The javascrpt has no value. All it is doing is outputting the wrong value (not the one entered by the user) and submitting the form, so I deleted it. The render url only needs to provide the target portlet and page. You set the form action to be the render url and the parameters in your form will be passed over automatically. Notice though that in my version the render url has no parameter defined in the tag itself. But, when you click the submit button, it will include the form parameters because that is what a submit action does. The input field is RENAMED to a name that must MATCH your public render parameter name. This way Liferay will detect that this parameter is supposed to be public and will put it in the correct parameter map. I've also changed your form to use the AUI taglibs so that you need only specify the name. The namespace is added automatically, and the id will be populated based on the name field (they will have the same value).
I also noticed that you have a hidden field with _3_groupId. The _3_ is the portlet namespace for the search portlet in 6.2, so you don't need that here, groupId alone should suffice but if you are hard coding it to "0" to mean a global scope to retrieve content across all sites (that's what it means for the search portlet) then I would argue you can simply omit it as a parameter altogether and just implement that global scope logic in your handler.
Community
Company
Feedback