Home
User Guide
The information contained in this section applies to WebSphere Commerce Version 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in a newer section.WebSphere Commerce is a single, unified e-commerce platform that offers the ability to do business directly with consumers (B2C), directly with businesses (B2B), and indirectly through channel partners (indirect business models). WebSphere Commerce is designed to be a customizable, scalable, and high availability solution that is built to leverage open standards. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels.
Integrating
Topics in the Integrating category highlight the tasks that are commonly performed for using WebSphere Commerce in combination with other products.
Integrating IBM WebSphere ILOG JRules BRMS with WebSphere Commerce for pricing
IBM WebSphere ILOG JRules BRMS is a business rule management system that allows developers to easily build and deploy rule-based applications that automate fine-grained, variable decisions used by business systems. You can use WebSphere ILOG JRules to build pricing rulesets, and then reference those rulesets from WebSphere Commerce price rules you create in Management Center.
Configuring WebSphere Commerce to communicate with WebSphere ILOG JRules
Before you can begin using rules from WebSphere ILOG JRules in WebSphere Commerce, there are a series of configuration tasks you must perform. You must configure WebSphere Commerce to communicate with the WebSphere ILOG JRules Rule Execution Server to retrieve rules. You must also configure WebSphere Commerce to communicate with the Execution Unit component of the Rule Execution Server to execute rules. These configuration tasks involve deploying the WebSphere ILOG JRules JAR files, adding resource references in WebSphere Commerce JAR files, and modifying the connection properties.
Preparing the server for configuration
You must make sure the machine you want to integrate with WebSphere ILOG JRules for pricing is properly prepared.

User Guide
The information contained in this section applies to WebSphere Commerce Version 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in a newer section.WebSphere Commerce is a single, unified e-commerce platform that offers the ability to do business directly with consumers (B2C), directly with businesses (B2B), and indirectly through channel partners (indirect business models). WebSphere Commerce is designed to be a customizable, scalable, and high availability solution that is built to leverage open standards. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels.
- Planning
  Creating a custom implementation of a WebSphere Commerce store requires a significant amount of planning. From gathering client needs, to deploying the live solution, much work is needed to successfully deploy a custom client store. Use the resources in here to help you plan every phase of store creation.
- Installing
  Review the following sections for information about installing the WebSphere Commerce product, associated maintenance, and WebSphere Commerce enhancements.
- Migrating
  Before you migrate to WebSphere Commerce Version 8.0, review this information to help plan and execute your migration.
- Deploying
  The topics in this section describe how to publish stores to either a test or production environment, and how to deploy customized code.
- Operating
- Integrating
  Topics in the Integrating category highlight the tasks that are commonly performed for using WebSphere Commerce in combination with other products.
  - Integrating with back-end systems and external applications
    External systems integration is a key feature of the WebSphere Commerce solution. In WebSphere Commerce business logic is enabled for integration and built-in adapters and interfaces are provided for common integration points. Additionally, the WebSphere Commerce integration solution leverages integration standards by using various IBM connectivity solutions.
  - IBM Watson Campaign Automation integration
    You can integrate IBM Watson Campaign Automation with WebSphere Commerce so that transactional emails are sent by IBM Watson Campaign Automation.
  - Sterling Order Management integration
    The integration between WebSphere Commerce and Sterling Order Management combines the industry-leading front-end capabilities of WebSphere Commerce with the proven, back-end order and inventory management features of Sterling Order Management.
  - IBM MQ
    WebSphere Commerce provides a listener for IBM MQ for inbound requests, and an adapter for IBM MQ for outbound requests, to integrate back-end, and external systems with WebSphere Commerce.
  - Content management integration
    You can integrate WebSphere Commerce with an external content management system through a punch-out window from Management Center and through the web feed utility. You can integrate WebSphere Commerce with IBM Web Content Manager to provide Management Center users the ability to associate IBM Web Content Manager content with WebSphere Commerce objects.
  - Mobile applications that use IBM Worklight
    IBM Worklight is a mobile application platform that you can use to develop cross-platform hybrid applications for the Aurora starter store.
  - Facebook integration
    Facebook integration relies on several Facebook plugins to add the Connect to Facebook, Like, and Send buttons to the Aurora starter store.
  - Analytics for IBM WebSphere Commerce
    WebSphere Commerce provides a framework that you can configure to integrate your store with an external Web analytics solution. This framework includes a tag library that you can use in store page JSP files to provide appropriate analytics information to the external analytics system.
  - IBM Product Recommendations and WebSphere Commerce
    IBM Product Recommendations is an IBM Digital Analytics solution that you can subscribe to that automatically generates personalized product recommendations on the storefront. The recommendations are based on the browsing, shopping, and purchasing behavior of individual customers. If your site is integrated with IBM Digital Analytics, you can display recommendations from IBM Product Recommendations on your store pages.
  - IBM Marketing Center integration
    You can integrate Management Center with IBM Marketing Center, a cloud-based, all-in-one solution that combines customer analytics with real-time marketing. To integrate with IBM Marketing Center, you must configure the WebSphere Commerce biConfig.xml file to enable the integration. You can also configure single-sign on between Management Center and IBM Marketing Center.
  - IBM Digital Data Exchange integration
    To simplify the process of collecting and sending customer shopping behavior data to analytics providers, integrate WebSphere Commerce with IBM Digital Data Exchange (DDX). IBM Digital Data Exchange (DDX) is offered as part of the IBM Digital Analytics solution.
  - Administering IBM Enterprise Marketing Management
    If your site is integrated with IBM Enterprise Marketing Management applications, such IBM Digital Analytics, IBM Product Recommendations, or IBM Marketing Center, you can administer the application features that your site uses. For example, you can administer IBM Digital Analytics based customer segments and import recommendations for IBM Product Recommendations.
  - IBM Dynamic Pricing
    Dynamic Pricing 16.4 is a cloud-based pricing system that analyzes real-time market data to provide suggestions on how merchandisers can react to competitor pricing and shifts in market conditions. Data can be fed to Dynamic Pricing from multiple sources, including WebSphere Commerce. You can configure WebSphere Commerce to export pricing data to Dynamic Pricing for pricing analysis and adjustment. The adjusted pricing data can then be imported from Dynamic Pricing to WebSphere Commerce, so the prices can be propagated to your live store front.
  - Universal Behavior Exchange (UBX) integration
    You can integrate Universal Behavior Exchange (UBX) with WebSphere Commerce so that you can import and export WebSphere Commerce customer segments as UBX audiences between third-party applications.
  - Watson Content Hub integration
    You can integrate Watson Content Hub with WebSphere Commerce, so that you can manage content in Watson Content Hub and then use the content in the Management Center Catalogs tool.
  - Integrating IBM WebSphere ILOG JRules BRMS with WebSphere Commerce for pricing
    IBM WebSphere ILOG JRules BRMS is a business rule management system that allows developers to easily build and deploy rule-based applications that automate fine-grained, variable decisions used by business systems. You can use WebSphere ILOG JRules to build pricing rulesets, and then reference those rulesets from WebSphere Commerce price rules you create in Management Center.
    - Integration architecture
      WebSphere Commerce provides an integration architecture in which WebSphere ILOG JRules manages pricing rules and WebSphere Commerce uses these rules.
    - Installation overview
      Before installing WebSphere ILOG JRules with WebSphere Commerce, you should be aware of the installation requirements, the required WebSphere ILOG JRules products, and how to install and deploy WebSphere ILOG JRules on different topologies.
    - Configuring WebSphere Commerce to communicate with WebSphere ILOG JRules
      Before you can begin using rules from WebSphere ILOG JRules in WebSphere Commerce, there are a series of configuration tasks you must perform. You must configure WebSphere Commerce to communicate with the WebSphere ILOG JRules Rule Execution Server to retrieve rules. You must also configure WebSphere Commerce to communicate with the Execution Unit component of the Rule Execution Server to execute rules. These configuration tasks involve deploying the WebSphere ILOG JRules JAR files, adding resource references in WebSphere Commerce JAR files, and modifying the connection properties.
      - Preparing the server for configuration
        You must make sure the machine you want to integrate with WebSphere ILOG JRules for pricing is properly prepared.
      - Deploying the WebSphere ILOG JRules JAR files required for connectivity
        You must deploy two JAR files containing WebSphere ILOG JRules rule session configuration information to the WebSphere Commerce application. A rule session is a runtime connection between WebSphere Commerce and the WebSphere ILOG JRules rule engine.
      - Configuring the EJB session type (not required for the POJO session type)
        The recommended integration method for WebSphere Commerce and WebSphere ILOG JRules on the same system is using the POJO rule session type. The alternative is to use the EJB rule session type, which requires that you perform an additional configuration procedure in the development environment only. You do not have to perform this procedure on a WebSphere Commerce instance. For the POJO rule session type, no additional configuration is required.
      - Configuring the registry and proxy for the WebSphere ILOG JRules rule engine
        To complete the integration of WebSphere ILOG JRules with WebSphere Commerce, you must modify two properties files.
    - Descriptions of sample BOM entries, sample rules, and ruleset parameters
      The sample WebSphere ILOG JRules rule projects for pricing (WC_SDO_App, WC-SDO-rules, and WC-SDO-xom) include sample BOM entries, sample business rules, and ruleset parameters. You can use these samples as starting points for your own ILOG JRules pricing rulesets.
    - Propagating ILOG JRules rules using the stagingprop utility
      If you have configured a staging environment for ILOG JRules integration, you can use the stagingprop utility to propagate ILOG JRules rules data. The stagingprop utility first propagates rules data from the staging Rule Execution Server to the production Rule Execution Server. If the propagation is successful, the utility then propagates WebSphere Commerce data from the WebSphere Commerce staging server to the WebSphere Commerce production server, as usual.
- Administering
- Tutorials
  WebSphere Commerce provides many tutorials to help you customize and understand your WebSphere Commerce instance and stores.
- Samples
- Developing
  The topics in the Developing section describe tasks performed by an application developer.
- Compliance
  The following section describes how you can leverage WebSphere Commerce features and functionality to help your site be compliant with different privacy and security standards.
- Securing
  These topics describe the security features of WebSphere Commerce and how to configure these features.
- Performance
- Troubleshooting

Preparing the server before performing WebSphere ILOG JRules configuration tasks

You must make sure the machine you want to integrate with WebSphere ILOG JRules for pricing is properly prepared.

Procedure

Install the WebSphere ILOG JRules product according to the installation instructions provided with the WebSphere ILOG JRules software.
You can install this product on:
- The same machine as the WebSphere Application Server you plan to integrate with WebSphere ILOG JRules.
- A different machine; you can then deploy the JRules modules from this machine to the target WebSphere Application Server.
Complete the applicable steps in the WebSphere ILOG JRules PDF installation guide.
This guide contains step-by-step instructions for deploying the JRules modules on the WebSphere Application Server. The installer copies this PDF guide to:
<ILOGJRulesInstallDir>/doc/j2ee/WebSphere/doc/Installing_JRules_WebSphere.pdf