Difference between revisions of "Upgrade Plan 380 Portal"

Revision as of 11:26, 13 July 2015

Portals

The portals should be upgraded using the new mavenized portal bundle: org.gcube.portal.portal-bundle-3.5.0-0.tar.gz

Portals to upgrade:

• i-marine.d4science.org
• services.d4science.org
• egip.d4science.org
• descramble.d4science.org

New Portlets

Portlets to upgrade

Portlets to upgrade because of dependencies update

Standalone Web Applications

Libraries

With the adoption of the new portal-bundle and the new maven-portal-bom that makes the portlet take their deps in their context the $portal/gCube/lib folder can be replaced completely with the one contained in the the org.gcube.portal.portal-bundle.3-5-0 artifact released in gCube 3.8.0.

Servlets

• the social-mail-servlet and its related hook (mail-reader-hook) must be deployed on every portal instance

Configurations

• A new CustomField for type Organization should be added to every portal to give the possibility to make post notification via email by default (Key: PostNotificationViaEmail Type: Boolean)
• 4 New ServiceEndPoint should be added in the infrastructure scope and containing information about the pop3 email server to be used by the 4 portals to check replies form the users

Layouts