I am new to Liferay portal. Is there any possibility within Liferay portal to extract portlet as different web application?
Plugin portlets are typically deployed as a separate web application. If you're asking about Liferay's core portlets: No, they are contained in Liferay. All of the plugins are downloaded separately and installed as a different web application
If you want share your portlet, Liferay has some features.
Drag and drop your portlet in page and then click on configuration icon.
In the popup select Sharing tab
You can choose your preferred sharing mode (embedded javascript, facebook,.).
When you share a portlet, be careful about permission settings otherwise users will not be able to view it.
Another chance is to use porltet url, see FriendlyUrlMapper wiki
This is an example for portlet HelloWorld in /web/guest/home page
http://localhost:8080/web/guest/home?p_p_id=helloWorld_WAR_HelloWorld&p_p_lifecycle=0&p_p_state=maximized&p_p_mode=view&p_p_col_id=column-1&p_p_col_count=1
Related
Is it possible to develop an sapui5 application inside liferay portal?
I've saw a post which describes a liferay with Jquery (https://web.liferay.com/pt/web/nathan.cavanaugh/blog/-/blogs/using-jquery-or-any-javascript-library-in-liferay-6-0).
Anyone has tried run sapui5/openui5 application inside liferay portal?
I have a Portlet that I know works and deployed successfully about 3 years ago. Now someone has asked for a change and I've totally forgotten how to deploy it for development on my local machine.
I have a local copy of IBM Portal server and have exported the portlet as a war file and deployed inside IBM Portal Server like so.
Go to http://mymachine:10038/wps/portal/. Under Portal Management
Select portlets.
I then selected Web Modules and installed my way file successfully.
Now it appears under the Portlets tab...
So far so good. But I am stuck now on how to hit my Portal application in the browser. How do I actually get to the Portlet url?
thanks
1) Build portlet as .war file
2) In portal Administration go to Web Modules
3) Lookup installed portlet and press Update or Instal button if new
portlet application
4) Go to Manage Pages and create empty page or select existing page
5) Press pen button to select and put portlet on the page
6) Open the page and you should see your portlet
Reading this question regarding using portal engine vs. aspx, there is also the option for a "Mixed" template which the training defines as:
This page template is based on an ASPX page located in the path specified in the File name field. ASPX+ Portal page templates are based on an ASPX page with additional page components that enable the Design tab.
What isn't clear is what the use case is for this mixed template. When would you use this versus the other two?
Update
I read the following in the Developer Training materials:
Sometimes, you may need to combine ASPX page templates or external ASPX pages with
Portal Engine page templates on a single web site. When developing or maintaining a
web site built on ASPX page templates, you must manually modify the code of a page
every time you want to change its design. But you can add flexibility to ASPX templates
by defining areas that can be edited directly through the browser using the CMS
administration interface (similar to the Portal Engine development model).
This explains clearly that it is a true hybrid where you have both ASPX template and Portal Engine functionality, but it isn't clear what benefit you have by using this approach versus a Portal Engine template that utilizes widgets or web parts.
I'd say there is no "benefit" as such. You can use this mode e.g. when you are migrating existing ASPX web site to Kentico portal engine pages and replacing components (such as controls and web parts) one by one. When you finish the migration you can switch to portal engine mode. The goal was to provide this functionality for those who need it. It is recommended to use portal engine as you have complete control over the pages from CMS Desk.
The most common place I use them is when adding templates to a site using ASPX page templates, usually sites tend to have a content page, where I can swap out the controls (usually editable regions) with web part zones, then use that one template file to create multiple ASPX + Portal templates.
That way I can add a lot of new functionality into an existing site, without having to create half a dozen new .aspx templates.
I imagine it's also still useful for a new project where you want to keep your templates under source control, while utilizing the portal engine/web part functionality of Kentico.
I am new to Liferay, how to add specific web content to only single page.for example i have 2 pages like Financial Service and Products.I have related web contents for those two pages.If i add those web contents to pages,both the contents are displaying in both of the pages.
Add a page on your portal
http://www.liferay.com/documentation/liferay-portal/6.0/administration/-/ai/page-creation-and-manageme-2
Then you can add two web-content portlets pointing to those 2 pages.
I am trying to implement personalization (WebPartManager and WebParts) on ASP.NET application deployed to SharePoint as application pages (Separate application and aspx pages deployed to _layouts).
I'd like to take advantage of SharePoint personalization provider, so I can just wire up the provider to WebPartManager in the ASP.NET application. However SharePoint seems to call SPRequest object to perform these tasks, and does not have a provider for personalization.
The second option I tried was to use SharePoint WebPartManager on these pages but it does not seem to work because application pages are not uploaded pages inside the SharePoint content database, so I receive errors when I try to add/personalize a webpart.
Does anyone know a clean way to utilize SharePoint personalization on application pages?
Normally, application pages are not tied to a specific site. And the webpart manager keeps the personalization values with the page in the site the page comes from.
You can probably accomplish what you are trying to do by using ASP.NET personalization. But then you have to use the ASp.NET personalization infrastructure which [I think] wants to use SQL Server by default.
Of course, the drawback to this is that you will have 2 personalization infrastructures implmented. This could mean deployment headaches.
Roger Williams
Franklin Laboratory
You may want to use page layouts with publishing pages instead of application pages.
Application Pages are ment to be shared across the Application in the Farm and doesnt support personalization. You need to deploy them as the Publishing pages to make use of the Personilization. You can try upload these files using features and as the Ghostable. So that you dont need to place them in the Pages Library you can have it in any web folder you want . For more information refer this link