Chapter 2. Configuration

Components
ActivityManager
SpaceService
IdentityManager
ProfileConfig
ServiceProviderStore
External component plugins
MentionsProcessor
PortletPreferenceRequiredPlugin
AddNodeTypePlugin
RelationshipManager
SpaceIdentityProvider
SpaceApplicationHandler
ExoPeopleService
Space Service
Description
Components configuration
External plug-in configuration
Activity Manager
Description
Component plug-in configuration
External plug-in configuration
Identity Manager
Description
Component plug-in configuration
OpenSocial Rest Context Configuration
Description
Component plug-in configuration
Spaces Template configuration
Configure the oauth 2 legged scenario
Generate the certificates
Configure the property file
Configuration name Data type Default Value Description
allowedTags String list b, i, a, span, em, strong, p, ol, ul,li, br, img html tags
Configuration name Data type Default Value Description
SpaceActivityStreamPortlet String SpaceActivityStreamPortlet
space.apps String list DashboardPortlet:true, SpaceSettingPortlet:false, MembersPortlet:true
Configuration name Data type Default Value Description
providers String org.exoplatform.social.core.identity.provider.SpaceIdentityProvider
Configuration name Data type Default Value Description
nodetype.emails String exo:profileKeyValue
nodetype.phones String exo:profileKeyValue
nodetype.ims String exo:profileKeyValue
nodetype.urls String exo:profileKeyValue
nodetype.address String exo:profileAddress
nodetype.experiences String exo:profileExperience
nodetype.education String exo:profileEducation
forceMultiValue String xxxxxxxxxxxx
Configuration name Data type Default Value Description
sample-provider properties-params sample service provider
Configuration name Data type Default Value Description
priority String 2 priority of this processor (lower are executed first)
Configuration name Data type Default Value Description
portletsPrefsRequired String list SpaceActivityStreamPortlet, SpaceSettingPortlet, MembersPortlet
Configuration name Data type Default Value Description
autoCreatedInNewRepository String jar:/conf/portal/core-nodetypes.xml Node types configuration file

The Service is used to manipulate user relationships.

The provider is to give identity space instances.

The service is to handle all events related to creating and managing all the application spaces.

The service is to manipulate all data related to people in the Portal.

Component name Description
SpaceServiceImpl Implementation class of Space Service.
Configuration name Data Type Possible value Default Value Description
SpaceActivityStreamPortlet String N/A SpaceActivityStreamPortlet The name of portlet displaying activities of spaces
space.apps String list Porlets' name: true/false DashboardPortlet:true; SpaceSettingPortlet:false; MembersPortlet:true The list of configurations for portlets used as portlet applications.

In which:

Name Set-method Type Description
PortletPreferenceRequiredPlugin setPortletsPrefsRequired org.exoplatform.social.core.application.PortletPreferenceRequiredPlugin Configure the list of portlet names which will have portlet preference of space context.
Name Possible value Default Value Description
portletsPrefsRequired Portlet names SpaceActivityStreamPortlet; SpaceSettingPortlet; MembersPortlet List of portlets which need to be saved and get the space context name.

In which,

Name Set-method Type Description
OSHtmlSanitizerProcessor addProcessorPlugin org.exoplatform.social.core.processor.OSHtmlSanitizerProcessor The plugin that renders valid html tags appearing in the Activity body (content).
Name Possible value Default Value Description
allowedTags html tags b, i, a, span, em, strong, p, ol, ul,li, br, img To process and render html tags in the activity content (body).

In the eXo Spaces, we may have two space types (classic and webos spaces). This is for the classic mode (it's the only one implemented now).

For the classic space, we can pre-configure the template, meaning that you can set up where your menu will be displayed or where your application will be displayed.

Here is an example of configuration file that displays the menu on the left. The Application will be inserted in the container with the id Application:

In this example, the outer container contains two inner containers: one container has id as Menu for your Menu and another has id as Application containing your applications.

If you want to put your menu in right and your application in left, you can swap the declared position of two containers:

Here is the configure file in FishEye: http://fisheye.exoplatform.org/browse/social/trunk/extension/war/src/main/webapp/WEB-INF/conf/portal/template/pages/space/page.xml.

In your tomcat, this configuration file is at $EXOTOMCAT/webapps/social-ext/WEB-INF/conf/portal/template/pages/space/page.xml.

This is to explain how to configure the oAuth 2 legs scenario in openSocial.

For more information about this, visit the website: great article