Alfresco:Portal:Integration
Un article de Bluexml.com.
 Home
|  Official WebSite
|  Download
|  Forum
|
|---|
 |
Languages : | English |
Sommaire |
Why use a portal ?
Pros
A portal provides :
- an unified way to access applications and data
- a client to add content dynamically in it
- a set of portlets you can immediately use to decorate your portal
Cons
A portal :
- makes navigation more complicated : you have to express parameters' communication between portlets. In summary, a portlet when clicked may update another portlet, eventually in another tab/subtab ... Portals don't always provide this feature. For example, until 4.3 version, liferay didn't.
- needs every content to be a ... portlet ... and need your development to be JSR 168 compliant. It is not a big work to do, but it is best to have it in mind before starting to code.
Preamble
The main problem with portal is Inter Portlet Communication (IPC). It may be solved at the browser level with AJAX or server level with standard technologies. A library has been developed to make IPC easier. You will find more information at the following link :
Tests
Portal tested :
- Liferay (course)
- Exoportal
- JBoss Portal
Liferay
Integration
To integrate this portal, just follow this doc.
You may have the following errors :
- dir.root is relative, and it seems to be a problem in portal context
- index isn't synchronized
- content store is not present
To solve these problems, just :
- fix dir.root in alfresco/WEB-INF/classes/alfresco/repository.properties with an absolute path
- fix index.recovery.mode in alfresco/WEB-INF/classes/alfresco/repository.properties with FULL
- drop you mysql database for alfresco with db_remove.sql then recreate it with db_setup.sql
And just restart, it should work
Result
Here are a few screenshots
