WebSphere Commerce V7.

0
Social commerce problem determination

© 2010 IBM Corporation

This presentation discusses problem determination for the social commerce feature in
WebSphere® Commerce V7.0.

SocialCommerceProblemDetermination.ppt Page 1 of 18

 Goals

� Learn file structure of social commerce application and sMash runtime

� Learn social commerce specific trace strings
� Learn basic troubleshooting

2 Social commerce problem determination © 2010 IBM Corporation

After viewing this presentation you should be familiar with the file structure of the social
commerce application and sMash runtime, how to enable trace for social commerce, and
basic troubleshooting.

SocialCommerceProblemDetermination.ppt Page 2 of 18
 Agenda

� Review basic file structure

� Application taxonomy and process structure
� Debug log location and contents
� Enabling trace
� Troubleshooting methodology

3 Social commerce problem determination © 2010 IBM Corporation

First, a review of the basic file structure of WebSphere Commerce applications is

provided, followed by a discussion of application taxonomy and processes, debug and
trace log location and contents, enabling trace, and troubleshooting methodology.

SocialCommerceProblemDetermination.ppt Page 3 of 18
 General file structure for server

� Based on WebSphere Application Server

� Same instance structure as V6
� Configuration manager creates instance which maps to application server profile
� Instance profile contains
– Logs directory and server1 subdirectory containing logs and trace files
– installedApps directory contains deployed applications
– Other configuration information

4 Social commerce problem determination © 2010 IBM Corporation

WebSphere Commerce is based on the WebSphere Application Server product. The

general file structure of WebSphere Application Server has not changed from V6 to V7.
Consequently, the file structure of WebSphere Commerce V7 is very similar to V6. The
configuration manager creates an instance which maps to an application server profile.
The instance profile contains a logs directory and an installedApps directory which
contains the enterprise applications. The profile also contains lots of other configuration
information which is not of interest for this presentation.

SocialCommerceProblemDetermination.ppt Page 4 of 18
 General file structure for developer toolkit

� Based on Rational® Application Developer

� Same developer project structure as V6
� Workspace directory holds Rational Application Developer projects and application code
� Wasprofile directory contains
– Logs directory and server1 subdirectory containing logs and trace files
– Other configuration information

5 Social commerce problem determination © 2010 IBM Corporation

WebSphere Commerce Developer is based on the Rational Application Developer

product. The general file structure of Rational Application Developer V7 has not changed
from V6. Consequently, the file structure of WebSphere Commerce Developer V7 is very
similar to V6. The workspace directory contains the projects and application code. The
wasprofile directory contains a logs directory and other configuration information which is
not of interest for this presentation.

SocialCommerceProblemDetermination.ppt Page 5 of 18
 Profile contents

� Deployed applications � Diagnostic logs

6 Social commerce problem determination © 2010 IBM Corporation

This slide shows the relative location of the logs and deployed applications directories in
the profile. The logs location applies to both WebSphere Commerce and WebSphere
Commerce Developer. The deployed applications directory only applies to WebSphere
Commerce.

SocialCommerceProblemDetermination.ppt Page 6 of 18
 Trace

� Trace specified in WebSphere Application Server administration console, same as V6

� Recommended trace string
com.ibm.commerce.soccom.*

7 Social commerce problem determination © 2010 IBM Corporation

Tracing is enabled in the same manner as in V6. The WebSphere Application Server
administration console is used to enable tracing by specifying a trace string specification.
The slide shows the specification you should use to enable tracing for social commerce
events.

SocialCommerceProblemDetermination.ppt Page 7 of 18
 Applications

� JEE applications
– WC
– Soccom
� JVM processes
– WebSphere Commerce
– sMash runtime

8 Social commerce problem determination © 2010 IBM Corporation

There are two deployed JEE applications after social commerce enablement is complete.
The WC application is the WebSphere Commerce application. The soccom application is
the social commerce runtime that includes the sMash runtime and SocApp application.
The slide shows a view of these applications from the WebSphere Application Server
administration console. The slide also three JVM processes that represent application
objects. The two Java™ processes correspond to the WebSphere Commerce server and
the sMash runtime. The javaw process corresponds to the WebSphere Commerce
Developer toolkit. This process would not exist in a server environment.

SocialCommerceProblemDetermination.ppt Page 8 of 18
 Developer toolkit Soccom projects

� Soccom - enterprise application container

� SocDevProxy – simple proxy for routing HTTP to
SocApp
� SocMgmtProxy – management Mbean
� SocCore - library and sMash CLI
� SocApp - sMash application that specifies
configuration and dependencies

9 Social commerce problem determination © 2010 IBM Corporation

After you import the social commerce project files into WebSphere Commerce Developer,
you see three new projects. Soccom is a thin container for the enterprise application which
contains deployment descriptors. Soccom contains two Web modules. SocDevProxy is a
simple proxy for routing HTTP requests to SocApp. SocMgmtProxy is the management
Mbean which controls starting and stopping the social commerce enterprise application.
SocCore is the sMash library and command line interface (CLI). SocApp is the main
sMash application that specifies the configurations and dependencies.

SocialCommerceProblemDetermination.ppt Page 9 of 18
 SocApp project details

� Logs
– Access.log similar to Web server
– Error logs showing error summaries
– Trace logs showing most detail
� Developer only - might need to refresh
SocApp project to show contents

10 Social commerce problem determination © 2010 IBM Corporation

Expanding the SocApp project reveals a logs directory. The logs directory contains one or
more log files. If you are in WebSphere Commerce Developer, you might need to refresh
the SocApp project to see the logs directory. The logs directory is created by the sMash
runtime and does not exist until it runs for the first time.

SocialCommerceProblemDetermination.ppt Page 10 of 18
 Log details

� access.log
127.0.0.1 - - [15/Sep/2009:13:41:52 -0500] "GET /soccom/ibm/social/images/button/secondary_button_bottom_bg_hover.gif

HTTP/1.1" 200 63 "3680/CF-WRK: 292098409 : 1" 110611

127.0.0.1 - - [15/Sep/2009:13:41:52 -0500] "GET /soccom/ibm/social/images/button/secondary_button_top_bg_hover.gif HTTP/1.1"

200 92 "3680/CF-WRK: 292098409 : 0" 176261

� error.log and trace.log

WARNING [ CWXCX0210: Error fetching the profile identified by key Could not read json

source: {"UniqueId":0,"Requests":]}. Fetch a user that has already been registered. Pluck

says: {1} ]

2009-09-15 11:29:52 com.ibm.commerce.soccom.handler.html.ReviewsHtmlHandler::onRetrieve

Thread-1

WARNING [ Error retrieving reviews item 10051_FULO-01. Cause: ERR_FETCHING_PROFILE ]

2009-09-15 11:33:05 com.ibm.commerce.soccom.bv.util.BVUtils::getReviewMap Thread-2

WARNING [ CWXCX0326W: Bad XML response from Bazaarvoice: No reviews returned for the

product ]

2009-09-15 11:42:26 zero.core.cfadapter.ZeroServer::stop Thread-3

11 Social commerce problem determination © 2010 IBM Corporation

This slide shows example contents of the access, error, and trace log files.

SocialCommerceProblemDetermination.ppt Page 11 of 18
 Troubleshooting basic configuration checklist

� Enable social commerce applications

– Run WCIntegration wizard or config_ant script
� Configure external provider adapters
� Configure IBM HTTP Server proxy instructions
� Publish store add-on feature to Madisons

12 Social commerce problem determination © 2010 IBM Corporation

The basic troubleshooting checklist mirrors the configuration steps covered in the
"Configuring social commerce" presentation. First you enable the social commerce
application by running the integration wizard or the config_ant script. Next, you configure
the external provider adapters by customizing the adapter configuration file. Next, you
configure the IBM HTTP Server proxy instructions. Finally, you publish the social
commerce add-on feature to the Madisons starter store. See the "Configuring social
commerce" presentation for more details on these configuration steps.

SocialCommerceProblemDetermination.ppt Page 12 of 18
 Troubleshooting

� Madisons store missing social commerce content page sections, such as a review and blogs
tabs, directly following add-on feature publish
– Remove Madisons JSP compilation directory

13 Social commerce problem determination © 2010 IBM Corporation

If the basic checklist has been covered, examine the error symptoms for potential
remedies. If the store is missing all social commerce content, and this is the first attempt
after publishing the add-on feature, then you need to check the JSP compilation directory.
Standard procedure is to remove the JSP compilation directory immediately after
publishing. See the presentation "Configuring social commerce" for more information
about how to do this task.

SocialCommerceProblemDetermination.ppt Page 13 of 18
 Troubleshooting

� Cannot view any social content, but pages show correct tabs
– Blogs, photo galleries, user profiles, reviews
• Verify external provider is accessible and operational
• Verify external provider parameters in adapter.config file
• Verify correct copy of adapter.config is being updated

14 Social commerce problem determination © 2010 IBM Corporation

If the symptom is that the store pages show page sections for social content, such as a
reviews tab on a product page, but the dynamic content is missing, then the remedy is to
verify the content provider service is working. The first step is to verify network
connectivity to the content service provider. Then verify the adapter.config file has the
correct contents that match the content service provider parameters. Then verify that the
adapter.config file that you are updating is the correct copy and that the live application
copy has the latest contents.
See the presentation "Configuring social commerce" for more information about the
adapter.config file.

SocialCommerceProblemDetermination.ppt Page 14 of 18
 Troubleshooting

� Can view existing social content, cannot post new social content
– Verify correct administration settings at the external provider
– Is there a link on the page to create new content?
• If not, are you signed in properly?

15 Social commerce problem determination © 2010 IBM Corporation

If the symptom is that the store pages show social content, but you can not post new
social content, then you need to isolate one of the following conditions. If you can not see
links to create new content, then the likely cause is that you are not properly signed in.
Either you did not sign in, or the user registry is having problems. If you do have a link to
create new contents, then that link should generate a new content form. If you can submit
the form, but the content is never posted, you might have a moderation policy on the
content provider that prevents automatic posting. You should check with the content
service provider to learn about managing content moderation policies.

SocialCommerceProblemDetermination.ppt Page 15 of 18
 Summary

� Review basic file structure

� Application taxonomy and process structure
� Debug log location and contents
� Enabling trace
� Troubleshooting methodology

16 Social commerce problem determination © 2010 IBM Corporation

This presentation discussed a review of the basic file structure of WebSphere Commerce
applications, application taxonomy and processes, debug and trace log location and
contents, enabling trace, and troubleshooting methodology.

SocialCommerceProblemDetermination.ppt Page 16 of 18
 Feedback

Your feedback is valuable

You can help improve the quality of IBM Education Assistant content to better meet your
needs by providing feedback.
� Did you find this module useful?
� Did it help you solve a problem or answer a question?
� Do you have suggestions for improvements?

Click to send e-mail feedback:

mailto:iea@us.ibm.com?subject=Feedback_about_SocialCommerceProblemDetermination.ppt

This module is also available in PDF format at: ../SocialCommerceProblemDetermination.pdf

17 Social commerce problem determination © 2010 IBM Corporation

You can help improve the quality of IBM Education Assistant content by providing
feedback.

SocialCommerceProblemDetermination.ppt Page 17 of 18
 Trademarks, copyrights, and disclaimers
IBM, the IBM logo, ibm.com, and the following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both:
IBM Rational WebSphere
If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law
trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of other IBM
trademarks is available on the Web at "Copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml
Rational is a trademark of International Business Machines Corporation and Rational Software Corporation in the United States, Other Countries, or both.
Java, JSP, JVM, and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. This document could include technical inaccuracies or
typographical errors. IBM may make improvements or changes in the products or programs described herein at any time without notice. Any statements regarding IBM's future direction
and intent are subject to change or withdrawal without notice, and represent goals and objectives only. References in this document to IBM products, programs, or services does not imply
that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Any reference to an IBM Program Product in this
document is not intended to state or imply that only that program product may be used. Any functionally equivalent program, that does not infringe IBM's intellectual property rights, may be
used instead.
THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IBM shall have no responsibility to update this information. IBM products
are warranted, if at all, according to the terms and conditions of the agreements (for example, IBM Customer Agreement, Statement of Limited Warranty, International Program License
Agreement, etc.) under which they are provided. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other
publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related
to non-IBM products.
IBM makes no representations or warranties, express or implied, regarding non-IBM products and services.
The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents or copyrights. Inquiries regarding patent or copyright
licenses should be made, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. All customer examples described are presented as illustrations of
how those customers have used IBM products and the results they may have achieved. The actual throughput or performance that any user will experience will vary depending upon
considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance
can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here.
© Copyright International Business Machines Corporation 2010. All rights reserved.
Note to U.S. Government Users - Documentation related to restricted rights-Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract and IBM Corp.

18 © 2010 IBM Corporation

SocialCommerceProblemDetermination.ppt Page 18 of 18