Portlets

Portlets in a page depends on the requirement. Even though it is better to use Ajax
calls if the data is required after the page load. Avoid loading huge data on page
load and better to use Liferay Search container. Using theme development Portlet
structure can also be designed and new css classes can also be added.
Access management (security/user profiles)
In Liferay we have Roles and permissions for access management. We can restrict
the resource using roles and permissions.
We even can have roles assigned to groups, sites and organizations. Resources
comes under those entities will get the inherited roles/permissions.
Liferay has special features like you can define your own permission to any Role. For
example - we have a role called Reviewer, so we can define permissions like has
access to articles, or can publish, can edit or etc. Can be restricted to access any
components like wiki, blogs, document and media etc
Liferay follows the OWASP and CWE/SANS to ensure that Liferay Portal is as secure
as possible.
Following these recommendations protects the portal against known kinds of
attacks and security vulnerabilities. For example, Liferay Portals persistence layer is
generated and maintained by the Service Builder framework which prevents SQL
Injection using Hibernate and parameter based queries.
To prevent Cross Site Scripting (XSS), user-submitted values are escaped on output.
To support integration features, Liferay Portal doesnt encode input. Data is stored in
the original form as submitted by the user. Liferay Portal includes built-in protection
against CSRF attacks, Local File Inclusion, Open Redirects, Uploading and serving
files of dangerous types, Content Sniffing, Clickjacking, Path Traversal, and many
other common attacks.
CMS integration & Document management
Liferay CMS can be integrated easily with other applications as by default Liferay
exposes many rest services related to cms. Which can be consumed and easily
integrated with 3td party applications.
In document management system, we can manage documents with folder
structure. All documents can be access based and can be deiced which role can
access the document. at the same time each and every document upload has a
unique URL to access. At the back end we set the source as different sources. Like
we can give any network drive, AWS drive or even Nexus repository and many more
Multi-tenancy and development approach
Multi-tenancy is very important in Liferay - we can achieve this in many ways but
using sites an instance is common.
Using different sites, we can have Multi-tenancy like all the contests is separated
from one site to another site. But at same time all the portlets can be used in any
sites. Liferay has special feature called Adaptor Hook, which give us power to
customize jsp different for different sites. Regarding instances in Liferay, we can
create a different portal which in which we can have same functionality as the real
one. Data cant be share but all the protests can be shared across. This concept is
based in company id in the Liferay. Most of the Liferay entities has companyids so
that it will accommodate in instances.
Naming standards
Since this new version of the portal utilizes OSGi to achieve modularity, the portal's
dependency artifact filenames follow the OSGi file naming convention using Bundle-
SymbolicName.
Liferay other features good to use.
Liferay supports session replication during clustering. Splitting a form into multiple
pages so that you can create wizard- like forms
Ability to control the layout of the form including organizing form fields into multiple
columns on a given form page. This can also support complex layouts wherein each
row can have a different number of columns.
Ability to populate a form dropdown (i.e. a Select field) with a REST Data Provider
this can be extremely useful when you need to let a user pick a value from a list,
where the list of values come from some back-end system such as SAP, Salesforce,
Oracle business Suite, and others.
Conditional display/hiding of a field i.e. making a field appear based on the value
entered into another field, enabling workflow for the form, providing a predefined
value or a placeholder value for a given field, Validating fields using a number of
different criteria, Redirecting users to a landing page (or a specific URL) after a form
submission
Liferay Service Builder.
Can be used with different data sources, by default ehCache is enabled for all
entities. Filters can be added with single and multiple variables.