tag:blogger.com,1999:blog-43563006781090909112024-02-21T19:11:08.325+05:30Liferay DXP SolutionsIt's all about Liferay DXP Solutions & Support
Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.comBlogger226125tag:blogger.com,1999:blog-4356300678109090911.post-21071517221977388612020-04-12T12:52:00.000+05:302020-04-12T12:52:03.287+05:30Liferay 7.3 compatibility matrix
Compatibility Matrix
Liferay's general policy is to test Liferay Portal CE against newer
major releases of operating systems, open source app servers, browsers,
and open source databases (we regularly update the bundled upstream
libraries to fix bugs or take advantage of new features in the open
source we depend on).
Nothing has been removed from the matrix, however a couple things
have Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.comtag:blogger.com,1999:blog-4356300678109090911.post-61669449283264661902020-04-12T12:34:00.000+05:302020-04-12T12:53:23.895+05:30Liferay 7.3
Lets have quick look how Liferay 7.3 looks.
1) You would have docker ready image provided by liferay now
docker run -it -p 8080:8080 liferay/portal:7.3.1-ga2
2) Dependency management improved
If some of you have used earlier version 7.0, 7.1 and 7.2 may aware that we had to add many compilation dependencies for liferay library it self which confusion got removed now Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.comtag:blogger.com,1999:blog-4356300678109090911.post-18888813704216709622020-04-12T12:01:00.000+05:302020-04-12T12:01:58.343+05:30SAML
The Liferay DXP’s SAML (Security Assertion Markup Language) adapter
lets you execute Single Sign On (SSO) and Single Log Off (SLO) in your
deployment. Each Liferay DXP instance serves as either the Service
Provider (SP) or the Identity Provider (IdP). This article provides the
conceptual framework for Liferay DXP’s SSO solution.
Single Sign On
Identity Provider initiated SSO
Service Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-66031813670756931672020-04-12T12:00:00.002+05:302020-04-12T12:00:54.892+05:30SAML Setup
SAML
is an XML-based open standard data format for exchanging authentication
and authorization data between parties known as an identity provider
and a service provider. For more fundamental information on SAML and
Liferay DXP, refer to the SAML introduction.
An
identity provider is a trusted provider that provides single sign-on
for users to access other websites. A service provider is Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-80866807894295234132020-04-12T12:00:00.000+05:302020-04-12T12:00:08.910+05:30How to Generate Liferay SAML Environment's metadata.xml
Description
This article describes how to generate Liferay SAML metadata from a web browser. SAML metadata in an XML
file is configuration data required to automatically negotiate
agreements between system entities, comprising identifiers, binding
support and endpoints, certificates, keys, cryptographic capabilities
and security and privacy policies. (See SAML V2.0 Metadata Guide.)
Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-42940613406449772422020-04-12T11:59:00.000+05:302020-04-12T11:59:53.767+05:30Setup SAML on Liferay DXP
Description
This article serves as a guide is for deploying SAML on Liferay DXP both as an Identity provider and Service provider
Table of Contents
Introduction
Setting Up Liferay SAML as an IdP
Setting Up Liferay SAML as an SP
Use Case #1: Salesforce Integration
Use Case #2 Liferay as Both IdP and SP
Add a Service Provider
IdP-initiated SSO
SP-initiated SSO
Use Case #3: User AttributesJignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-40544834439039180062017-12-08T17:04:00.004+05:302017-12-08T17:04:39.230+05:30Create Servlet Project as Module
You would have seen that many times we are writing out own servlet in Liferay portal to achieve some specific use case.
In DXP, You can still cont. with such implementation and here you will see how you can write your servlet application as module.
Create liferay module type of API using developer studio or blade ci.
In bnd file:
Bundle-Name: test-servlet
Bundle-SymbolicName: Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-38178140757671338322017-12-08T15:24:00.002+05:302017-12-08T18:00:23.643+05:30Liferay DXP clustering
Hello Friends,
I am sure you would be looking for simple steps for DXP clustering.
Note:Liferay 7 clustering you can visit https://community.liferay.com/news/new-clustering-code-for-liferay-portal-community/
Steps for Liferay DXP clustering :
Liferay Setup:
- Setup liferay DXP in 2 separate servers which can be accesses using separate IP
- Both servers should be accessible toJignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-80968095826082199462017-12-07T15:32:00.000+05:302017-12-07T15:32:36.740+05:30Liferay DXP setup with Weblogic
Download latest DXP version
For Enterprise Edition, we need to download Liferay DXP
For Community Edition, we need to download Liferay Portal
As we are using (EE ) Enterprise Edition, we will download Liferay DXP.
Note:Download Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-77919292459320528142017-12-04T16:55:00.000+05:302017-12-04T16:55:08.977+05:30Login Authentication Solutions
Hello Friends,
This article will be helpful to you when you choose to customize login with various Liferay DXP supported authentication mechanism.
And this is almost common requirement for each implementations so I will provide all possible ways to customize login functionality based on my knowledge and provide solution.
1) Liferay OOB Login Customization
Custom Module implementation
2) Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-64329644281666880732017-07-19T11:26:00.000+05:302017-08-01T18:05:23.689+05:30REST Client OSGi Bundle
Hello Friends,
If you are planing to create HTTP REST client using OSGi, Just follow the steps.
1) Create bundle project of type API using IDE
2) Write one Class called RestClient.java
import org.apache.http.HttpEntity;
import org.apache.http.HttpHost;
import org.apache.http.auth.AuthScope;
import org.apache.http.auth.UsernamePasswordCredentials;
import org.apache.http.client.AuthCache;
Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-74963357437662672382017-06-13T19:32:00.002+05:302017-06-13T20:01:47.952+05:30Captcha & reCaptcha with Liferay 7
If you are planning to integrate captcha in you liferay custom portlet then use below stuff
view.jsp:
<%@taglib uri="http://liferay.com/tld/captcha" prefix="liferay-captcha" %>
<portlet:resourceURL id="/login/captcha" var="captchaURL"/>
<liferay-captcha:captcha url="<%=captchaURL%>" />
Write CaptchaMVCResourceCommand.java :
@Component(
propertyJignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-34127339643615151192016-11-23T13:08:00.001+05:302016-11-24T12:35:30.866+05:30Spring MVC Portlet Migration - DXP
Friends,
Do you want to migrate your Spring MVC portlet into DXP ? yooo here are the steps you will have to follow to get it migrate.
Before we jump into steps, let me light up regarding spring mvc. Actually Spring MVC is purely used for web project architect and there is no any specific intention to get it convert into OSGi module jar. So here we may not be able to convert it into moduleJignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-26089902012876108672016-11-22T17:24:00.005+05:302016-11-24T12:36:06.137+05:30Custom portlet configuration - DXP
Hello Folks,
Here I have tried to put all the possible steps which we would required to introduce custom portlet configuration.
1) Create new Liferay module using mvcportlet template
2) Define below highlighted property in your controller class:
@Component(
immediate = true,
property = {
&Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-64039991736386590032016-11-22T17:00:00.000+05:302016-11-24T12:37:09.758+05:30Overriding classes and properties using OSGi - DXP
Hello Friends,
Here i have published all possible ways to override Liferay classes and properties for which we were using hook in older Liferay version.
1) Create Custom portlet data handler
@Component(
property = {
"javax.portlet.name=com.sample.portlet"
&Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-47614328318541895142016-11-22T16:34:00.001+05:302016-11-24T18:02:08.242+05:30Liferay MVC Portlet with Service Builder - DXP
Friends,
Here you will see how you can create Liferay MVC portlet with best practice.
If you remember, we were creating portlets in 6.X by selecting specific portlet type from IDE and choosing weather we have to use service builder or not. So there it was creating only one single portlet including service layer.
Now in DXP, you will have to separately create service layer and web portlet Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-86473627929997990462016-11-11T12:22:00.003+05:302017-01-05T14:41:24.296+05:30Issues During 6.X to DXP migration
There are couple of common problem which we might facing during migration or upgration from 6.X to Liferay DXP.
We will discuss all possible items over here.
1) Module not showing active state in OSGi ?
If you have deployed your module and not showing active state then go to gogo shell and tun lb command to check status if its active or not and if its not active (Installed state) then runJignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-73443554533287064452016-09-27T15:44:00.000+05:302016-11-23T13:41:13.392+05:30Overriding LPKG Files : Liferay DXP
Liferay provides a way to update modules without modifying the original LPKG
file they're packaged in. You can do this by overriding the LPKG file.
To override a JAR or WAR from any LPKG other than the Static LPKG,
1) first create
a folder named override in the Liferay instance's osgi/marketplace folder.
2) Drop the updated JAR into this folder, making sure its name is the same as theJignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-65611115541403301642016-09-22T18:52:00.000+05:302016-11-23T13:41:13.372+05:306.X Portlet to DXP Module Convesion
Follow below steps to convert Liferay MVC Portlet to Module:
1) First Step is, you will have to download plugin-sdk for DXP/Liferay 7 because Liferay has provided one tool which gives you facility to show breaking API changes in your portlet.
2) Once you run this tool, it will give you all the breaking Liferay API (Not Custom code) report for Java and JSP files.
Note: Sometimes Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-54304668289934626482016-09-22T15:02:00.001+05:302016-11-23T13:41:13.364+05:30DB Upgrade 6.X to DXP
As you know Liferay is moved to DXP version now and all existing Liferay customer will migrate or upgrade to newer version of DXP.
Here in these series of blogs, you will see all step by step guide which will help you to follow all the necessary steps for the migration to DXP.
As a part of migration/up-gradation, Database comes first everywhere which you must require to migrate toJignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-51223783167497383342016-09-20T19:13:00.000+05:302016-11-23T13:41:13.360+05:30Liferay DXP Setup
Follow below steps to setup local Liferay DXP :
Below Tools and software are required to setup Liferay DXP in local machine :
A. JDK-8B. JPM
C. BladeD. Liferay DXP (Tomcat bundle)E. Liferay Plugin-SDK
A. Install JDK-8
Install latest JDK-8 from the oracle site based on your operating Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-88798340801149842522016-08-16T01:25:00.002+05:302016-11-23T13:41:13.399+05:30Know Module And Component
The main reason for LIFERAY to move into module framework is,
Creating small modules (Tightly coupled)
Publish and consume other modules features (Inflexible)
Working without static dependencies (Dynamic dependencies)
To use module framework,
You mainly need to understand below 3 concepts :
Modules
Components
Application Lifecycle
Module:
Module is something Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-28867278698946642722016-08-16T01:08:00.001+05:302016-11-23T13:41:13.341+05:30What is OSGi ?
OSGi : Open Service Gateway Initiative
OSGi is architecture to develop and deploy a modules in modular (Some times refers as Micro Services) application.
OSGi containers such as knopflerfish, Equinox and Apache Felix are responsible to divide and load your modules dependencies.
OSGi Specifications:
=> Set of services that OSGi container implements
=> Contract Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-46599644815637634252016-07-22T01:56:00.003+05:302016-07-29T08:23:33.981+05:30Sharepoint REST API call
Guys, I am sure this snippet will help you a lot when you do sharepoint REST integration to read files
import java.io.File;
import java.io.InputStream;
import java.io.StringWriter;
import org.apache.http.Header;
import org.apache.http.HttpEntity;
import org.apache.http.HttpHeaders;
import org.apache.http.HttpStatus;
import org.apache.http.auth.AuthScope;
import Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0tag:blogger.com,1999:blog-4356300678109090911.post-44168492218798306162016-03-30T00:35:00.001+05:302016-07-29T09:59:09.330+05:30Useful Roles and permission API
Reading portlet resources and model resources:
<pre>
List<String> portletResources = ResourceActionsUtil.getPortletResourceActions(PortletLocalServiceUtil.getPortletById(portletId).getPortletId());
List<String> modelResource = ResourceActionsUtil.getPortletModelResources(portletId);
</pre>
Adding and removing permission:
for(String resouce : portletResources){
Jignesh Vachhanihttp://www.blogger.com/profile/18040117955302228816noreply@blogger.com0