Difference between revisions of "Social Portal Extension Setup"

Revision as of 11:11, 4 February 2013

Get the latest gCube Portal Bundle

http://gcube.wiki.gcube-system.org/gcube/index.php/GCube_Portal_Installation and install it.

Get the needed dependencies for the Social Extension

Social Networking Library from maven (get the latest) nexus-search;quick~social-networking

<dependency>
  <groupId>org.gcube.portal</groupId>
  <artifactId>social-networking-library</artifactId>
  <version>1.0.0-SNAPSHOT</version>
</dependency>

• Create a folder _social-library in $GLOBUS_LOCATION/lib
• Copy in the yet created floder the SNL Dependencies & the Netflix Astyanax Dependencies:

<dependency>
  <groupId>com.netflix.astyanax</groupId>
  <artifactId>astyanax</artifactId>
  <version>CHECK THE VERSION IN SNL POM</version>
</dependency>

• Get the latest ASL Social Extension and copy it into the $GLOBUS_LOCATION/lib/_application-support-layer folder

Notifications

For notifications to work you will need to deploy the Notification Servlet on the Portal. The client code is instead implemented in the social-dockbar-hook provided in the portal bundle.

<dependency>
  <groupId>org.gcube.portal</groupId>
  <artifactId>notificationchecker</artifactId>
  <version>0.1.0-SNAPSHOT</version>
  <type>war</type>
</dependency>

Create the Social Portal Layout on Liferay

The Layout of the Data e-Infrastructure Gateway Community must be updated, the following pages should be created (pay attention to friendly url and the hidden property)

• Workspace
  • Name: Workspace
  • Friendly URL: workspace
  • Visibility: hidden

• Messages
  • Name: Messages
  • Friendly URL: messages
  • Visibility: hidden

• Notifications
  • Name: Notifications
  • Friendly URL: notifications
  • Visibility: hidden

• Profile
  • Name: Profile
  • Friendly URL: profile
  • Visibility: visible

• Join New
  • Name: Join New
  • Friendly URL: join-new
  • Visibility: visible

Populate the pages with the related portlets.

Staging Procedure

The Cassandra Cluster needs to be "staged" the first time you are going to use it.

• Create the RuntimeResource
  • The Runtime Resource with name SocialPortalDataStore must be created in the root Vo of the infrastructure.
    • The Access Point part should have the following settings:

...
 <AccessPoint>        
         <Description>$CLUSTER_NAME</Description>
         <Interface>
            <Endpoint EntryName="$KEYSPACE_NAME">$HOST:$PORT</Endpoint>
         </Interface>
....