Install > Installing or enabling additional software > Configure Social Commerce


Configure Social Commerce from the command line

To enable and configure Social Commerce from the command line, you can replace the automated steps performed by the Integration Wizard with manual configuration steps.


Before you begin


Procedure

  1. Open the following file in a text editor:

    • WC_INSTALL/components/social-commerce/config/port.config

    1. 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.

    2. Save the changes and exit.

  2. To configure the sMash application with Pluck, Bazaar Voice, or Lotus Connections configuration specific to the environment:

    1. Edit...

      • WC_INSTALL/components/social-commerce/config/adapter.config

    2. 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.

  3. Copy the following file:

    • WC_INSTALL/components/social-commerce/properties/sc.properties

    to

    • WC_INSTALL/instances/instance/properties/sc.properties

  4. Open WC_INSTALL/instances/instance/properties/sc.properties in a text editor. Specify which provider types to configure, following the comments in the file.

    If you specified sc.userRegistry=LDAP in sc.properties, perform these additional steps:

    1. Copy WC_INSTALL/components/ldap/properties/vmm.properties to WC_INSTALL/instances/instance/properties/vmm.properties.

    2. Copy WC_INSTALL/components/sso/properties/ltpa.properties to WC_INSTALL/instances/instance/properties/ltpa.properties.

    3. Open the files you copied in a text editor and ensure the values are set to appropriate values for the LDAP environment:

      • WC_INSTALL/instances/instance/properties/vmm.properties

      • WC_INSTALL/instances/instance/properties/lpta.properties

  5. Open a command prompt and navigate to WC_INSTALL/bin

  6. Run the following command:

    config_ant.bat –buildfile ../components/common/xml/enableFeature.xml 
    -DinstanceName=instance
    -DfeatureName=social-commerce
    -DdbUserPassword=<dbUserPassword>
    

    Run the following command as the non-root user:

    config_ant.sh –buildfile ../components/common/xml/enableFeature.xml 
    -DinstanceName=instance
    -DfeatureName=social-commerce
    -DdbUserPassword=<dbUserPassword>
    

  7. Verify that the enablement was successful:

    1. In the administrative console, check that a new application called WC_soccom was deployed to the WebSphere Application Server and started.

    2. Check that the following log files were generated:

      • WC_INSTALL/instances/instance/temp/proxy.config

      • WC_INSTALL/instances/instance/logs/enablesocial-commerce_timestamp.log

  8. Update the Web server configuration file to include the modproxy, and enable the modules mod_proxy and mod_rewrite.

    1. Open the Web server httpd.conf file in a text editor. See the IBM HTTP Server documentation for details.

    2. 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
      

    3. Copy the contents of the following file to the clipboard:

    4. 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>
      

    5. Save and close the file.

  9. Restart the Web server and the Social Commerce application.

  10. If you are using a clustered environment, restart the cluster.


+

Search Tips   |   Advanced Search