Install > Installing or enabling additional software > Configure Social Commerce


Configure Social Commerce content provider information

If you change the Social Commerce content provider, you need to edit the adapter.config file, and run an ANT task to update the Social Commerce application.


Before you begin

Configure Social Commerce

These steps are necessary only to change your configuration after Configure Social Commerce. These steps are included when you first enable and configure Social Commerce.


Procedure

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

  2. For increased security in the Social Commerce sMash application, you can encrypt the sensitive pieces of information required by the service providers. The settings that can be encrypted are all found in the adapter.config file.

    The values that can be encrypted are:

    BazaarVoice

    /config/soccom/bv/sharedKey

    Pluck

    /config/soccom/pluck/sharedSecret

    Lotus Connections

    • /config/soccom/lc/adminPassword

    • /config/soccom/lc/restAdminPassword

    To encrypt the sensitive information:

    1. Use the wcs_encrypt command to encrypt the sensitive information. At this time, the "default merchant key" method is the only one that is supported. For example, to encrypt "mySharedKey", run the following command from a command line:

      wcs_encrypt mySharedKey
      The utility should return values like the following sample:
      ASCII encrypted string : /sheFEjWPZ3O9hbsF5pNww== HEX encrypted string : 2F73686546456A57505A334F396862734635704E77773D3D

    2. Modify the adapter.config file of the Social Commerce sMash application.

      For example, to use the ASCII value from step 2 for the Bazaarvoice /config/soccom/bv/sharedKey setting, set the following value in the adapter.config file:

      /config/soccom/bv/sharedKey = "<ascii>/sheFEjWPZ3O9hbsF5pNww=="

      For the HEX version, use the following format:

      /config/soccom/bv/sharedKey = "<hex>2F73686546456A57505A334F396862734635704E77773D3D"

      For the unencrypted plaintext value, use the following format:

      /config/soccom/bv/sharedKey = "mySharedKey"

    3. Save and close the adapter.config file.

  3. Open a command prompt and navigate to the following directory:

  4. Run the following command whenever you have made changes to the adapter.config file:
    config_ant.bat -DinstanceName=instance -buildfile ../components/common/xml/enableFeature.xml -DfeatureName=social-commerce UpdateAdapterConfig

    config_ant.sh -DinstanceName=instance -buildfile ../components/common/xml/enableFeature.xml -DfeatureName=social-commerce UpdateAdapterConfig


What to do next

Lotus Connections

Configure Social Commerce integration with Lotus Connections

Pluck

To ensure that dates are formatted correctly for date and locale, when Pluck is being used as a service provider the system time on the Pluck servers must be set to GMT with daylight savings time disabled. This is a configuration step that 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. By default, it is configured to be between 4 and 25 characters. However, the WebSphere Commerce sample store, we does not restrict the minimum number of characters for the userId.

To avoid problems where certain customers would not be able to post a review, ensure that the storefront and BazaarVoice server enforce the same minimum length requirement. For example, if you are using the WebSphere Commerce sample store as a basis for development, you should set the BazaarVoice minimum value to userNickName to 1.


+

Search Tips   |   Advanced Search