Difference between revisions of "GCube Portlets Deploying on Liferay"
From Gcube Wiki
| Line 1: | Line 1: | ||
| − | Porting and deploying the existing gCube portlets to Liferay portal is an easy task. The deployment of a portlet to Liferay requires an existing installation of the Liferay portal bundled with the Apache Tomcat server (For more information on how to install and configure Liferay portal visit: [[https://gcube.wiki.gcube-system.org/gcube/index.php?title=New_D4Science_Portal_Installation&action=edit&redlink=1 D4Science Portal Installation]] ) | + | == Gcube Portlets to Liferay == |
| + | Porting and deploying the existing gCube portlets to Liferay portal is an easy task. The deployment of a portlet to Liferay requires an existing installation of the Liferay portal bundled with the Apache Tomcat server (For more information on how to install and configure Liferay portal visit: [[https://gcube.wiki.gcube-system.org/gcube/index.php?title=New_D4Science_Portal_Installation&action=edit&redlink=1 D4Science Portal Installation]] ).<br> | ||
| + | The required changes are focused on the configuration files that Liferay requires and on the way the logged in user's information are retrieved. After setting up these information then the portlet can be compiled and deployed on liferay. | ||
Revision as of 14:16, 21 June 2010
Gcube Portlets to Liferay
Porting and deploying the existing gCube portlets to Liferay portal is an easy task. The deployment of a portlet to Liferay requires an existing installation of the Liferay portal bundled with the Apache Tomcat server (For more information on how to install and configure Liferay portal visit: [D4Science Portal Installation] ).
The required changes are focused on the configuration files that Liferay requires and on the way the logged in user's information are retrieved. After setting up these information then the portlet can be compiled and deployed on liferay.
