Install > Installing or enabling additional software > Configure Social Commerce
Configure Social Commerce using the Integration wizard
To enable and configure Social Commerce you use the Integration wizard; then you manually configure the Web server.
Before you begin
- You have created a WCS instance
- WebSphere Commerce is started.
- You must be using IBM HTTP Server as the Web server.
- sMash is supported on a subset of platforms that WebSphere Commerce supports, see What platforms are supported?
Procedure
- Open the following file in a text editor:
- WC_INSTALL/components/social-commerce/config/port.config
- Check that the value for /config/http/port is set to the port to use as the internal port that the sMash application listens on.
- Save the changes and exit.
- To configure the sMash application with Pluck, Bazaar Voice, or Lotus Connections configuration specific to the environment:
- Edit...
- WC_INSTALL/components/social-commerce/config/adapter.config
- Update the adapter.config file with environment-specific information. Use the following examples to help you configure your application:
- Pluck:
#------------------------------------------------------------------------ # Configuration for Pluck (staging server provisioned for IBM test/dev) #------------------------------------------------------------------------ /config/soccom/pluck/server = "pluckstage.yoursitename.com" /config/soccom/pluck/sharedSecret = "" /config/soccom/pluck/adminUser = "" /config/soccom/pluck/defaultBlogPublishState = "true"
- Bazaar Voice:
#------------------------------------------------------------------------------- # Configuration for Bazaar Voice (staging server provisioned for IBM test/dev) #------------------------------------------------------------------------------- /config/soccom/bv/serverURL = "http://Bazaar Voice IP/Bazaar Voice URL" /config/soccom/bv/clientCode = "" /config/soccom/bv/sharedKey = ""
- Lotus Connections:
#-------------------------------------- # Configuration for Lotus Connections #-------------------------------------- /config/soccom/lc/server = "LC SERVER HOSTNAME" /config/soccom/lc/tdiServer = "TDI SERVER HOSTNAME" /config/soccom/lc/scopeHandle = "LC SCOPE HANDLE" /config/soccom/lc/adminUser = "LC ADMIN ID" /config/soccom/lc/adminPassword = "LC ADMIN PASSWORD" /config/soccom/lc/restAdminUser = "LC REST ADMIN ID" /config/soccom/lc/restAdminPassword = "LC REST ADMIN PASSWORD"
There are two configurations shown in this example: Pluck + Bazaar Voice, and Lotus Connections + Bazaar Voice. See the Social Commerce overview for a general explanation of the Social Commerce feature.
- Navigate to the following directory:
WC_INSTALL/bin
- Run the following command:
- WCIntegrationWizard.bat
Run this command as the non-root user: ./WCIntegrationWizard.sh
- A prerequisites page is displayed. Click Next after ensuring that you meet the prerequisites.
- On the WebSphere Commerce information panel, select the WebSphere Commerce instance name, and enter the database password in the WebSphere Commerce database password field. Click Next.
- Select Social Commerce on the Choose an integration task panel.
- On the User Registry panel, select the registry type to use with Social Commerce.
- LDAP
- Uses the Lightweight Directory Access Protocol to authenticate users.
- Database
- Uses the WebSphere Commerce database to authenticate users.
- Other
- Uses an alternate registry that you have configured with your WebSphere Application Server. See you WebSphere Application Server documentation for details.
- Click Next. Depending on the registry type you have chosen, the wizard has slightly different behavior:
- If you have chosen Other or Database as the registry type:
- Review the warning message that is displayed and click OK.
- Skip to step 13.
- If you have chosen LDAP as the registry type, continue to the next step.
- Enter the information specific to your LDAP server to configure WebSphere Application Server security for the WCS instance.
The following fields are available, depending on the LDAP server configuration:
- Realm name
- WAS primary administrative user
This user should not exist on the LDAP server or federated repositories.
- WAS primary administrative user password and verification
- LDAP base DN
- LDAP bind DN
- LDAP bind DN password and verification
- LDAP user search filter string
- Optional: You can enable application security if it is required. However, it is not a recommended approach due to performance implications.
To enable application security:
- Select Enable Application Security.
- Complete the following fields:
- WebSphere Commerce RunAs ID DN
- WebSphere Commerce RunAs ID DN password and verification
- On the Single Sign-On panel, enter following information:
- Domain name
- Check whether to use JAAS Authentication Module
- On the Confirm Configuration Settings page, click Next. Wait for the configuration to complete; a message is shown telling you if the configuration was successful or not.
- Verify that the enablement was successful:
- In the administrative console, check that a new application called WC_soccom was deployed to the WebSphere Application Server and started.
- Check that the following log files were generated:
- WC_INSTALL/instances/instance/temp/proxy.config
- WC_INSTALL/instances/instance/logs/enablesocial-commerce_timestamp.log
- Update the Web server configuration file to include the modproxy, and enable the modules mod_proxy and mod_rewrite.
- Open the Web server httpd.conf file in a text editor. See the IBM HTTP Server documentation for details.
- Uncomment the following lines if they are not already uncommented (if they do not exist at all, add them):
LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule rewrite_module modules/mod_rewrite.so LoadModule proxy_balancer_module modules/WebSphereCE/mod_proxy_balancer.so
LoadModule proxy_module /QSYS.LIB/REWHTTP.LIB/QZSRCORE.SRVPGM LoadModule proxy_http_module /QSYS.LIB/REWHTTP.LIB/QZSRCORE.SRVPGM LoadModule proxy_balancer_module /QSYS.LIB/QHTTPSVR.LIB/QZSRCORE.SRVPGM
- Copy the contents of the following file to the clipboard:
- WC_INSTALL/instances/instance/temp/proxy.config
- Paste the contents inside of each VirtualHost element for the IBM HTTP Server httpd.conf file.
There are at least two VirtualHost elements; one for http and one for https. The default http virtual host begins with the section <VirtualHost servername:80> and the default https virtual hosts begins with the section <VirtualHost servername:443>
In the following example, the sections associated with the RewriteRule and LocationMatch are inserted in to the appropriate VirtualHost sections in the httpd.conf file.
Sample for non-clustered configuration
#Instance name : demo <VirtualHost myserver.myhost.com:80> ServerName myserver.myhost.com Alias /wcsstore "C:\WAS7\profiles\demo\installedApps\WC_demo_cell\WC_demo.ear/Stores.war" Alias /wcs "C:\WAS7\profiles\demo\installedApps\WC_demo_cell\WC_demo.ear/CommerceAccelerator.war" RewriteRule ^/soccom$ /soccom/ [R] <LocationMatch "/soccom" > ExpiresActive Off Order allow,deny Allow from all ProxyPass http://myserver.myhost.com:9980/soccom ProxyPassReverse http://myserver.myhost.com:9980/soccom </LocationMatch> </VirtualHost> <VirtualHost myserver.myhost.com:443> SSLEnable SSLClientAuth 0 ServerName myserver.myhost.com Alias /wcsstore "C:\WAS7\profiles\demo\installedApps\WC_demo_cell\WC_demo.ear/Stores.war" Alias /wcs "C:\WAS7\profiles\demo\installedApps\WC_demo_cell\WC_demo.ear/CommerceAccelerator.war" RewriteRule ^/soccom$ /soccom/ [R] <LocationMatch "/soccom" > ExpiresActive Off Order allow,deny Allow from all ProxyPass http://myserver.myhost.com:9980/soccom ProxyPassReverse http://myserver.myhost.com:9980/soccom </LocationMatch> </VirtualHost>
- Save and close the file.
- Restart the Web server and the Social Commerce application.
- If you are using a clustered environment, restart the cluster.
What to do next
- Configure Social Commerce content provider information
- Lotus Connections
- Configure Social Commerce integration with Lotus Connections
- Pluck
- When Pluck is used as a service provider set the system time on the Pluck servers to GMT with daylight saving time disabled. This configuration step must be performed by Pluck when provisioning a new server.
- BazaarVoice
- BazaarVoice allows customers to configure the minimum and maximum length for the userNickName field (4 - 25 characters). However, the WebSphere Commerce starter store, does not restrict the minimum number of characters for the userId. Verify the storefront and BazaarVoice server enforce the same minimum length requirement. For example, if you are using the WebSphere Commerce starter store as a basis for development, set the BazaarVoice minimum value to userNickName to 1.
- Add Social Commerce widgets to store pages