Upgrade Plan 330 Portal

Portals

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

Portlets to upgrade

• org.gcube.portlets-admin.information-space-editor-portlet.2-8-0

• org.gcube.portlets-admin.ft-index-management-portlet.2-3-1
• org.gcube.portlets-admin.users-management-portlet.2-3-0

• org.gcube.portlets-admin.ir-bootstrapper-portlet.2-8-0

• org.gcube.application.aquamaps.aquamapsportlet.3-1-2

• org.gcube.portlets-user.statistical-manager-portlet.1-4-2

• org.gcube.portlets-user.tabular-data-portlet.2.3.0

• org.gcube.portlets-user.report-generator-portlet.4-10-0

• org.gcube.portlets-user.workspace-portlet.6-6-6

• org.gcube.portlets-user.shareupdates.1-5-1

• org.gcube.portlets-user.results-portlet.5-5-0

• org.gcube.portlets-admin.information-space-editor-portlet.2-8-0

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.

Configurations

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

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.