Installing the Social Media PublisherAdded by IBM | Edited by IBM on June 18, 2013 | Version 3 (Show original)
|Follow these steps to install the Social Media Publisher on your authoring server, and then on any servers that subscribe from your authoring server.
Note: If you have migrated from a WebSphere® Portal version 7.0 or Web Content Manager version 7.0 server that was already using the Social Media Publisher, you will also need to run these steps on a version 220.127.116.11 system to enable the Social Media Publisher. All your data from your version 7.0 system will be maintained.
- Ensure that the following options have been correctly enabled:
- That the WasPassword and PortalAdminPwd passwords are set in the wkplc.properties file.
- That the jcr.DbPassword password is set in wkplc_dbdomain.properties file.
- That a proxy server is configured if your server is behind a proxy.
- Edit wp_profile_root/PortalServer/wcm/social/smp.properties file and to ensure the configuration is correct for the current server or cluster node.
- Run the following registration command from the wp_profile_root/ConfigEngine directory:
ConfigEngine.bat register-wcm-socialAIX®, Linux™, Solaris
./ConfigEngine.sh register-wcm-socialIBM® i
- Run the following deployment command from the wp_profile_root/ConfigEngine directory:
ConfigEngine.bat deploy-wcm-socialAIX, Linux, Solaris
./ConfigEngine.sh deploy-wcm-socialIBM i
- If you are publishing to an IBM Connections server, then import the SSL certificate from the IBM Connections server into the WebSphere Portal server. See the WebSphere Application Server documentation for instructions on importing certificates.
If your server is located behind a firewall, you may also need to import certificates for Facebook, LinkedIn and Twitter. See Working with social media certificates
for further information.
- Restart the server.
- Add the Social Configuration library to all syndication relationships.
Repeat these steps for each subscriber server in your environment. The settings defined for Shared Social database properties
in the smp.properties
file must be the same as those defined on the syndicator server.
When installing on a server other than the authoring server, if your JCR database username or password is different from the authoring server, then run the following command from the wp_profile_root/ConfigEngine
ConfigEngine.bat action-set-wcm-social-datasource-credentials -DWcmSocialDSNewUserName=AUTH_DB_USERNAME -DWcmSocialDSNewPassword=AUTH_DB_PASSWORDAIX, Linux, Solaris
./ConfigEngine.sh action-set-wcm-social-datasource-credentials -DWcmSocialDSNewUserName=AUTH_DB_USERNAME -DWcmSocialDSNewPassword=AUTH_DB_PASSWORDIBM i
ConfigEngine.sh action-set-wcm-social-datasource-credentials -DWcmSocialDSNewUserName=AUTH_DB_USERNAME -DWcmSocialDSNewPassword=AUTH_DB_PASSWORDz/OS
./ConfigEngine.sh action-set-wcm-social-datasource-credentials -DWcmSocialDSNewUserName=AUTH_DB_USERNAME -DWcmSocialDSNewPassword=AUTH_DB_PASSWORD
- If your server contains virtual portals, you must also run the following task for each virtual portal on your server:
ConfigEngine.bat import-wcm-social-data -DVirtualPortalHostName=VirtualPortalHostName -DVirtualPortalContext=VirtualPortalContextAIX, Linux, Solaris
./ConfigEngine.sh import-wcm-social-data -DVirtualPortalHostName=VirtualPortalHostName -DVirtualPortalContext=VirtualPortalContextIBM i
ConfigEngine.sh import-wcm-social-data -DVirtualPortalHostName=VirtualPortalHostName -DVirtualPortalContext=VirtualPortalContextz/OS
./ConfigEngine.sh import-wcm-social-data -DVirtualPortalHostName=VirtualPortalHostName -DVirtualPortalContext=VirtualPortalContext
- Restart WebSphere Portal.
- Repeat these steps on every server and cluster node.
Additional installation and configuration
Parent topic: Social Media Publisher
- When importing or migrating a Social Media Publisher library, you must also migrate credential vault data using the XML configuration interface. See the WebSphere Portal product documentation for further details.
- Anonymous access to web content libraries, content items and images is required for posting to external social networks. Single signon can also be enabled for IBM Connections.
- The Social Media Publisher utilizes the built-in JMS functionality of Web Content Manager to monitor and respond to events that are occurring within a system. When the Social Media Publisher is running within a cluster, each server needs to be configured to match the WebSphere Application Server JMS policy type in effect. The jms.processRemoteMsgs global setting must be set to either true or false depending on the WebSphere Application Server JMS policy type. See Global configuration settings for further information.