Install the Social Media Publisher
Follow these steps to install the Social Media Publisher on the authoring server, and then on any servers that subscribe from your authoring server.
If we migrated from a HCL WebSphere Portal version 7.0 or Web Content Manager version 7.0 server that was already using the Social Media Publisher, we also need to run these steps on the migrated system to enable the Social Media Publisher. All the data from the version 7.0 system is maintained.
- Ensure that we enable the following options correctly:
- 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 the server is behind a proxy.
- Edit WP_PROFILE/PortalServer/wcm/social/smp.properties file and to ensure that the configuration is correct for the current server or cluster node.
The parameter settings in smp.properties are case-sensitive.
- Run the following registration command from the WP_PROFILE/ConfigEngine:
./ConfigEngine.sh register-wcm-social
- Run the following deployment command from the WP_PROFILE/ConfigEngine:
./ConfigEngine.sh deploy-wcm-social
- If we are publishing to an IBM Connections server, then import the SSL certificate from the IBM Connections server into the HCL WebSphere Portal server. See the WebSphere Application Server documentation for instructions on importing certificates.
If the server is located behind a firewall, we might also need to import certificates for Facebook, LinkedIn, and Twitter. See 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 the environment. The settings that are defined for Shared Social database properties in the smp.properties file must be the same as the settings defined on the syndicator server.
The parameter settings in smp.properties are case-sensitive.
When we install on a server other than the authoring server, if the JCR database user name or password is different from the authoring server, then run the following command from the WP_PROFILE/ConfigEngine:
./ConfigEngine.sh action-set-wcm-social-datasource-credentials -DWcmSocialDSNewUserName=AUTH_DB_USERNAME -DWcmSocialDSNewPassword=AUTH_DB_PASSWORD
- If the server contains virtual portals, we must also run the following task for each virtual portal on the server:
./ConfigEngine.sh import-wcm-social-data -DVirtualPortalHostName=VirtualPortalHostName -DVirtualPortalContext=VirtualPortalContext
- Restart HCL WebSphere Portal.
- Repeat these steps on every server and cluster node.
Additional installation and configuration
- When you import or migrate a Social Media Publisher library, we must also migrate credential vault data using the XML configuration interface. See the HCL WebSphere Portal product documentation for further details.
- Two credential vault slots are required for Social Media Publisher configuration:
- A credential vault slot called socialPostUser is required for post workflow actions. See Social Media Workflow Actions. The socialPostUser slot is not displayed in the list of available vault slots when we create a Social Network Configuration document.
- We must also set up a credential vault for each social network. This action is selected when we create a social network configuration document. See Create a social network configuration document.
Both of these credential vault slots must be shared credential vault slots and store the admin user login information of the social network.
- Anonymous access to web content libraries, content items, and images are required for posting to external social networks. Single signon can also be enabled for IBM Connections.
- The Social Media Publisher uses the built-in JMS function 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.
- When we install the Social Media Publisher into a cluster that has a web-server in front of it, add the following Web Content Manager configuration setting. The settings allow the Social Media Publisher to make loop back requests to the current server:
wcm.local.host.port=LOCAL_PORTAL_PORT
Use the WAS console to add this setting to the WCM WCMConfigService service. LOCAL_PORTAL_PORT is the local WebSphere Application Server port for HCL WebSphere Portal. The default port is 10039.
Parent topic: Social Media Publisher