Social Lists - Post-migration

After migrating from a previous WebSphere Portal Version to v8.5, run a configuration task to deploy the new web content library and templates before using the Social Lists features. If we already used the social rendering feature from 8.0.0.1, the existing web content libraries and all portlet clones created during the enablement on 8.0.0.1 is not changed.

cd wp_profile_root/ConfigEngine
./ConfigEngine.sh action-enable-social-rendering -DPortalAdminPwd=foo -DWasPassword=foo

Verify the web content library Social Lists 1.0 was created by accessing...

Administration | WebSphere Portal | Portal Content | Web Content Libraries

By default, the task is run on the base portal. To run this task on a different virtual portal, add one of the following parameters to the command line...

VirtualPortalHostName	Host name of the virtual portal. For example, vp.example.com
VirtualPortalContext	Virtual portal context that identifies the virtual portal. For example, VP1.

For example...
./ConfigEngine.sh action-enable-social-rendering -DPortalAdminPwd=foo -DWasPassword=foo -DVirtualPortalContext=VP1

To continue to use the old toolbar, use the following configuration task to deploy new social portlets to that toolbar.

./ConfigEngine.sh action-deploy-social-shelf-category-and-portlets -DPortalAdminPwd=foo -DWasPassword=foo


Parent Add-ons, features, and third-party integration tasks