Difference between revisions of "Upgrade Plan 330 Portal"
(→Configurations) |
(→Configurations) |
||
| Line 55: | Line 55: | ||
ASL servlets require some JBoss JAAS configuration. Apply steps 1, 3 and 4 from [http://wiki.gcore.research-infrastructures.eu/documentation/index.php/D4Science_Portal_LDAP_Authorization here] | ASL servlets require some JBoss JAAS configuration. Apply steps 1, 3 and 4 from [http://wiki.gcore.research-infrastructures.eu/documentation/index.php/D4Science_Portal_LDAP_Authorization here] | ||
| + | |||
| + | Deploy servlets under a standard name: | ||
| + | * '''application-support-layer-http-infrastructure-login-1.2.1''' should be deployed under the name '''aslHttpInfrastructureLogin''' (renamed to aslHttpInfrastructureLogin.war) | ||
| + | * '''application-support-layer-http-information-retrieval-1.8.1''' should be deployed under the name '''aslHttpInformationRetrieval''' (renamed to aslHttpInformationRetrieval.war) | ||
| + | * '''application-support-layer-http-content-access-1.3.1''' should be deployed under the name '''aslHttpContentAccess''' (renamed to aslHttpContentAccess.war) | ||
=== Layouts === | === Layouts === | ||
'''DONE''' The VRE/VO Layouts should be updated: Specifcially for share updates, users management portlet the chafe should be performed directly on the database. | '''DONE''' The VRE/VO Layouts should be updated: Specifcially for share updates, users management portlet the chafe should be performed directly on the database. | ||
Latest revision as of 15:31, 17 July 2014
Portals
DONE 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.
ASL servlets require some JBoss JAAS configuration. Apply steps 1, 3 and 4 from here
Deploy servlets under a standard name:
- application-support-layer-http-infrastructure-login-1.2.1 should be deployed under the name aslHttpInfrastructureLogin (renamed to aslHttpInfrastructureLogin.war)
- application-support-layer-http-information-retrieval-1.8.1 should be deployed under the name aslHttpInformationRetrieval (renamed to aslHttpInformationRetrieval.war)
- application-support-layer-http-content-access-1.3.1 should be deployed under the name aslHttpContentAccess (renamed to aslHttpContentAccess.war)
Layouts
DONE The VREVirtual Research Environment./VOVirtual Organization; Layouts should be updated: Specifcially for share updates, users management portlet the chafe should be performed directly on the database.
