Install > Installing or enabling additional software > Configure Social Commerce


Configure Social Commerce in WebSphere Commerce Developer using the Integration Wizard

Configure Social Commerce in WebSphere Commerce Developer is accomplished by using the Integration Wizard, and then performing manual configuration steps.


Before you begin


Procedure

  1. Navigate to the following directory:

    WCDE_INSTALL/bin

  2. Run the following command:

    • WCIntegrationWizard.bat

  3. A prerequisites page is displayed. Click Next after ensuring that you meet the prerequisites.

  4. Select Social Commerce on the Choose an integration task panel.

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

  6. 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:

      1. Review the warning message that is displayed and click OK.

      2. Skip to step 11.

    • If you have chosen LDAP as the registry type, continue to the next step.

      You must choose LDAP as the registry type if you are using Lotus Connections.

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

  8. 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:

    1. Select Enable Application Security.

    2. Complete the following fields:

      • WebSphere Commerce RunAs ID DN

      • WebSphere Commerce RunAs ID DN password and verification

  9. On the Single Sign-On panel, enter following information:

    • Domain name

    • Check whether to use JAAS Authentication Module

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

  11. Check that the following log file was generated:

    • If you have a personal firewall enabled on the desktop you may be prompted to unblock a process called zso to accept incoming requests. This process is part of the Social Commerce runtime and is run as part of the Rational Application Developer publish operation that starts the WebSphere Application Server and the Social Commerce feature. Unblock this process.

    • If you receive an error related to SSL handshake failure, follow these troubleshooting steps.

  12. Open WebSphere Commerce Developer and ensure that the following three projects have been generated and show up in the workspace:

    SocApp

    The WebSphere Commerce sMash Application that performs most Social Commerce functions. This project is used primarily for configuration. You may need to change files in this project to update the configuration and override CSS files.

    SocCore

    The Social Commerce repository used by the SocApp application. This project is used primarily to publish new extensions (service adapters) to Social Commerce. Do not modify any of the existing modules in this project.

    soccom

    JEE Application for management of the SocApp project. In WebSphere Commerce Developer, it includes a development proxy to route HTTP requests to the SocApp project. This project is used for starting or stopping the Social Commerce feature. This project is for IBM internal use only.

  13. Configure the sMash application with Pluck, Bazaar Voice, or Lotus Connections configuration specific to the the environment.

    1. Edit...

      To open the file within WebSphere Commerce Developer, open the SocApp project and navigate to the config directory.

    2. Update the adapter.config file with environment specific information. Use the following examples to help you configure the application:

      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.

      • 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"

        restAdminUser and restAdminPassword are configured as part of the Tivoli Directory Integrator setup with Lotus Connections. scopeHandle is the homepage blog handle which is configured as part of the Lotus Connections setup.

    3. Restart the Social Commerce application after you complete your changes to the adapter.config file.

  14. If you are not using LDAP (for example, if you are using Pluck as a service provider) proceed to customizing the store by Add Social Commerce widgets to store pages. Do not perform step 15.

  15. Optional: If you are using LDAP, manually configure these additional WebSphere Application Server security properties:

    1. Configure the WebSphere Commerce Test Server properties.

      1. Right-click on the server and select Open.

      2. Navigate to the Security panel.

      3. Select Security is enabled on this server.

      4. Enter the user ID and password for the current active authentication settings.

        The user ID and password should be the same as the WebSphere Application Server Primary Administrative User provided using the WebSphere Commerce integration wizard.

      5. Select Automatically trust server certificate during SSL handshake.

    2. Optional: If Application Security is enabled, configure security in WebSphere Commerce Developer.

      1. Open WebSphere Commerce Developer.

      2. Open the META-INF\ibm-application-bnd.xml file in the WebSphere Commerce EAR project.

      3. Expand and select Security Role (WCSecurityRole).

      4. Click Add, select User and click OK.

      5. Under the Details heading, enter the distinguished name of the RunAs ID user.

      6. Save the changes.


What to do next

Add Social Commerce widgets to store pages


+

Search Tips   |   Advanced Search