Install > Installing or enabling additional software > Configure Social Commerce


Configure social commerce to use a custom 32-bit JDK on WebSphere Application Server 64-bit

As sMash currently does not run with a 64-bit JDK you can use this feature when configuring Social Commerce on a 64-bit machine.


Procedure

  1. Install WebSphere Commerce.

  2. Enable and configure the Social Commerce feature.

  3. Open the Administration Console.

    You will see following errors in the WebSphere Application Server log:

    MgmtProxy resolveAppLocation The custom JDK location from the config service is null
    MgmtProxy start CWXCX0007E: The Social Commerce feature could not be started : Application status is STOPPED

    The trace logs in C:\WebSphere\AppServer70\profiles\AppSrv01/installedApps/wsi20Node01Cell/soccom.ear/ SocApp/logs should help identify the problem.

    Looking at theSmash Application log at AppSrv01/installedApps/wsi20Node01Cell/soccom.ear/SocApp/logs, you will see:

    SEVERE [ CWPZC8029E: ZSO could not be located for the current platform of OS=windows, arch=x86_64. ]
    SEVERE [ CWPZT0601E: Error: Command start failed ]

  4. Download the 32-bit JDK. It is located on the 64-bit WebSphere Application Server Customized Installation Package (CIP) in the following location:

    • disk1/custom/sMash/<ibm_jdk>.zip

    • disk1/custom/sMash/<ibm_jdk>.gz

    where <ibm_jdk> is the name of the particular JDK to download.

  5. Uncompress the JDK.

    • Unzip the file into a directory of the choice, for example C:\WC\.

    • Run the gunzip command to unzip the .gz file to a directory that you specify: 

      gunzip
<ibm_jdk>.gz

      Run the tar command to untar the tar file: 

      tar -xf
<ibm_jdk>.tar

  6. Go to AdminConsole > Environment > WebSphere Variables and configure the JDK custom variable CUSTOM_SOCCOM_JDK with the address of the 32-bit JDK.

    For example: 

    CUSTOM_SOCCOM_JDK=C:\WC\ibm-java-sdk-60\sdk

  7. Restart WebSphere Application Server.

  8. Verify that Social Commerce started correctly.

    You should see the following messages in the WebSphere Application Server log: 

    MgmtProxy resolveAppLocation The custom JDK location from the config service is C:\WC\ibm-java-sdk-60\sdk
MgmtProxy start CWXCX0006I: The Social Commerce feature has been started.

  9. Confirm the following message is found in installedApps\wsi20Node01Cell\soccom.ear\SocApp\logs\starttrace.log: 

    INFO [ CWPZT0600I: Command start was successful ]

  10. Start the Social Commerce application and verify you can access it via a Browser.


+

Search Tips   |   Advanced Search