Difference between revisions of "Upgrade Plan 330 Portal"

From D4Science Wiki
Jump to: navigation, search
(Portlets to upgrade)
(Configurations)
Line 43: Line 43:
 
=== Configurations ===
 
=== Configurations ===
  
The Resource Registry should be configured as updater in the only iMarine Portal.
+
'''Done''' The Resource Registry should be configured as updater in the only iMarine Portal.
  
The information Space Editor portlet should be deployed at VRE Level in iSearch and marineSearch VREs, and removed from the VOs.
+
'''Done''' The information Space Editor portlet should be deployed at VRE Level in iSearch and marineSearch VREs, and removed from the VOs.
  
 
=== Layouts ===
 
=== Layouts ===
  
 
The VRE/VO Layouts should be updated for share updates, users management portlet.
 
The VRE/VO Layouts should be updated for share updates, users management portlet.

Revision as of 14:35, 17 July 2014

Portals

The portals should be upgraded using the new mavenized portal bundle version 3.1.0-3.3.0.

Portlets to upgrade

Portlets to upgrade because of dependencies update

Libraries

With the adoption of the new portal-bundle and the new maven-portal-bon 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-0-0 artifact released in gCube 3.3.0.

Servlets

Configurations

Done The Resource Registry should be configured as updater in the only iMarine Portal.

Done The information Space Editor portlet should be deployed at VREVirtual Research Environment. Level in iSearch and marineSearch VREs, and removed from the VOs.

Layouts

The VREVirtual Research Environment./VOVirtual Organization; Layouts should be updated for share updates, users management portlet.