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.
Samples
Aurora starter store
The Aurora starter store showcases the latest in storefront features, and models best practices in store development, demonstrating a wide scope of retail scenarios. Simplify your responsive B2C or B2B direct web store implementation and reduce your time-to-market by using the Aurora starter store as your development base.
Testing your store
WebSphere Commerce provides a test assets package that contains documentation and tools to help introduce, plan, and run Functional Verification Testing (FVT) for your store.
Updating the Functional Verification Test Case document
When features are added or altered to the project, you must update the Functional Verification Test Case document.
... AccessControl
Lists the Negative access control test cases. Positive access control is implicitly tested by running regular FVT test cases that are based on the roles that are provided in the test case itself.

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.
- Administering
- Tutorials
  WebSphere Commerce provides many tutorials to help you customize and understand your WebSphere Commerce instance and stores.
- Samples
  - Aurora starter store
    The Aurora starter store showcases the latest in storefront features, and models best practices in store development, demonstrating a wide scope of retail scenarios. Simplify your responsive B2C or B2B direct web store implementation and reduce your time-to-market by using the Aurora starter store as your development base.
    - Site level features
      Using site level features, you can customize the look and feel of your storefront. Site level features are visible from every page in your store.
    - Category level features
      Category level pages in the Aurora starter store are designed to assist customers in narrowing the product selection to find the preferred item.
    - Product level features
      Product level features in the Aurora starter store are designed to provide details about a specific product in your store.
    - Aurora as a B2B direct starter store
      You can publish the Aurora starter store as a B2B direct store and take advantage of features that are offered by the Aurora starter store plus extra B2B capabilities. Get your B2B e-commerce site up and running faster at a lower cost by using the Aurora starter store as your starting point. With B2B-optimized features built right into the storefront, you can minimize the amount of customization that is required to provide an optimal shopping experience to your business customers.
    - Publishing the Aurora starter store
      The Aurora starter store can be used only as a storefront asset store in the Extended Sites business model. It is not possible to deploy Aurora as a stand-alone B2B or B2C store. The Aurora.sar archive contains the organization structure, predefined user roles, and access control policies necessary to create either a B2C storefront asset store or a B2B storefront asset store.
    - jQuery Aurora starter store
      The Aurora starter store in WebSphere Commerce is completely written in jQuery 3.1.0, which is one of the most commonly used JavaScript libraries used in dynamic websites. The jQuery AJAX and events API provides an easy to use framework that meets most AJAX requirements for storefront development.
    - Aurora starter store functions
      For the Aurora starter store, you can select certain functions to include in your store and disable the ones that you do not need. Use the Store Management tool in Management Center to control which functions are enabled for your store.
    - Accessibility
      The Aurora starter store follows the IBM accessibility guidelines to implement accessibility features. Accessibility features help users who have a physical disability, such as a visual impairment, hearing impairment, or limited mobility, successfully use the store.
    - Search features
      WebSphere Commerce comes with a powerful and fully integrated search function. The search functions in WebSphere Commerce provide an enriched customer experience, with features such as automatic search term suggestions and spelling correction. Since it is built on open standards, WebSphere Commerce Search is highly flexible and extensible. Starter stores can use the search engine's most sophisticated features without requiring extra customization. A key feature of Search is that sales personnel can create and manage search term associations, and search-based merchandising rules, from within the Management Center and Store view.
    - Responsive Web Design (RWD)
      Responsive Web Design (RWD) is a web design approach that is aimed at crafting pages that are optimized for a wide range of devices. It advocates the use of primarily fluid layouts and media queries to optimize a site for different devices, instead of designing a separate site for each device.
    - Aurora starter store companion assets
      The IBM Starter Store Companion Assets are a customizable set of resources that are designed to reduce the overall cost of implementation. You can use the assets to understand, customize, test, and develop your store that is based on the starter store.
    - Replacing an existing store with Aurora
      Usually, new features that are introduced in feature pack releases require storefront changes. These changes can be in the form of data model changes, or modifications to the storefront JSP files to use new or updated APIs. For this reason, moving to the latest starter store is the easiest way to have newer components work on your existing store. Depending on the age and design of your site, this retrofitting can be done through several different approaches. If your site is relatively up-to-date, and you are interested in a particular feature, then you can find the migration steps for that solution or component and apply them to your store. Alternatively, you can attempt to replace the entire store with the Aurora starter store by following this set of high-level instructions.
    - Upgrading your store assets
      For existing WebSphere Commerce customers who are looking to upgrade to the next release, there are a number of approaches that you can take to upgrade your store. Review your requirements, and chose the proper path to upgrade your store assets to take advantage of the supplied features in the Aurora starter store.
    - WebSphere Commerce Dojo Enhancements API
      WebSphere Commerce extends the Dojo AJAX and events API, providing an easy to use framework that meets most AJAX requirements for storefront development.
    - Developing Aurora starter store pages
      Developing and maintaining store pages can become an efficient and consistent process by following the general practices that are used in existing Aurora starter store pages.
    - Site flows and interactions
      The site flows provide a screen capture and a detailed description for each store page. Store developers can use the site flows as a high-level guideline for each page to identify starting points when store pages are changed.
    - Checkout flows
      Checkout flows describe pages that your customers use to complete the checkout process.
    - Site flows
      The site flows provide a screen capture and description for each store page that includes Apple Pay on the Web functions.
    - My Account flows
      The My Account flows describe pages your customers use to register with the online store and maintain their account with the store. The My Account pages include the account summary, personal information, address book, personal wish lists, coupons, orders, order details, and browsing history. Certain pages are optional and are available to customers only if your store chooses those functions.
    - IBM Customer Service for WebSphere Commerce
      IBM Customer Service for WebSphere Commerce provides customer service enhancements that enable a customer service representative (CSR) to resolve common issues and capture orders. These capabilities are built into the WebSphere Commerce Aurora storefront and enable a CSR to complete key tasks on behalf of a guest and registered customers for both B2B and B2C stores. Customer Service for WebSphere Commerce is offered for both Professional and Enterprise editions.
    - Additional flows
      The Additional flows describe the supplementary pages that are required to maintain your online store.
    - Organization and buyer administration flows (B2B)
      In the B2B direct business model, each company that purchases from your store must have one or more registered users who are assigned the Buyer Administrator role. Buyer Administrators administer the company's organizations, and they manage the company's buyers, including assigning roles and approving new buyers who register. The Aurora starter store provides a series of self-serve pages for Buyer Administrators to do their work directly in the storefront, rather than using the Organization Administration Console.
    - Order approval flows
      During organization setup, order approvals and contracts can be configured to set the criteria that determines which orders require approval. When order approvals are enabled, a Buyer Approver or Buyer Administrator must approve orders that exceed the order total limit that is specified in the contract before orders are submitted for processing. The Aurora starter store contains pages in which Buyer Approvers and Buyer Administrators can view and manage order approvals.
    - Buy-on-behalf-of flows
      The buy-on-behalf-of feature allows a Buyer Administrator to shop on behalf of a buyer in the same organization. After signing in to buy on behalf of a specific buyer, the Buyer Administrator sees the store exactly the way that buyer would see the store. The Buyer Administrator can then lock an order and proceed to create, modify, or view the buyer's information such as saved orders, order history, and requisition lists. When an order is locked, a symbol appears beside the order number.
    - Enabling punch-out payment
      You can enable punch-out payment in starter stores. Punch-out payment is a payment model where a third-party payment service provider processes payments for orders.
    - Facebook integration
      Use the power of the world's biggest social media community to spread the word on products or your store with embedded Facebook Like or Send/Share buttons.
    - Apple Pay on the Web integration
      Apple Pay on the Web integration with WebSphere Commerce provides you with an easy and secure way to accept and process payments. Apple Pay on the Web enables customers to purchase products in the Aurora starter store with a single touch in Safari on Mac, iPhone, and iPad.
    - Testing the WebSphere Commerce and Sterling Configurator integration
      After you install and configure the software components for the WebSphere Commerce and Sterling Configurator integration, test the integration with sample data and sample procedures.
    - Testing your store
      WebSphere Commerce provides a test assets package that contains documentation and tools to help introduce, plan, and run Functional Verification Testing (FVT) for your store.
      - Testing on smartphone devices
        You can configure your test environment to include smartphone devices.
      - Viewing mobile store pages by using desktop Web browsers
        You can configure your desktop Web browser to simulate the mobile environment to view your mobile site without using a mobile device.
      - Creating a high-level functional verification test plan
        The high-level functional verification test (FVT) plan is a document that is written at the beginning of the test cycle. The document is an agreement between the development team, project management team, and the FVT team on the test coverage and scope for the project. Before you begin functional verification testing, the plan is reviewed and approved by appropriate stakeholders.
      - Updating the Functional Verification Test Case document
        When features are added or altered to the project, you must update the Functional Verification Test Case document.
        ... GeneralSetup
        Describes the applications, tools, or software packages, such as an email server, Payment Gateway simulator, or back-end stubs, you must configure before you can run the test cases.
        ... TestOverview
        A summary of test cases that are documented in the Functional Verification Test Case document.
        ... UsecaseScenarioMap
        Use Case to Scenarios mapping provides a link between the project Use Cases that are identified for implementation and the test scenarios to run.
        ... ScenarioUsecaseMap
        Scenarios to Use Cases mapping table provides a list of Use Cases that are covered by each Test Scenario. This is a reverse mapping of the previous Use Case to Scenario mapping. The Use Cases in these Test Scenario tables are referenced from Use Case to Scenario mapping. The Additional Document Links provide relevant information for each use case that can be used as reference material.
        ... TestcaseTasks
        TestcaseTasks lists common procedure steps that are used in the test cases. The common tasks are separated from the Test Cases so that procedure steps can be easily modified, shared, and maintained. Test cases reference this tab for steps that are listed in the Procedure column. You can update a single task to affect all related test cases. TestcaseTasks help you ensure that the testcase execution steps are consistent between testcases and any inconsistencies can be quickly resolved.
        ... Testcases
        Test Cases contain the most detailed level of information in the Functional Verification Test Case Document. A Test Case is a collection of connected Use Cases, Procedures, Data, and Expected Results that describe a user flow through the system. In Test Cases, test Cases are grouped by Test Scenarios.
        ... TestCondMatrix
        The Test Condition matrix provides a high-level view of the different permutations and combinations of parameters and test data that is used in each test case. Each scenario has its own matrix.
        ... Data
        Data lists test data that is used in the test cases. The data is separated from the Test Cases tab so that data can be easily modified and maintained. Test cases reference this tab for all data purposes. This allows data sets to be easily shared between test cases. You can update a single location to affect all related test cases. This single tab has the benefit of easing the communication with the data creation team to ensure that all test data is available at the start of the FVT phase.
        ... Messages
        Messages and warnings that are referred in the Test Cases are specified in this tab. These messages and warnings are specified in the WebSphere Commerce properties file. The message and value pairs can be copied and pasted into this tab. The messages and warnings are separated from the test cases so that they can be easily updated and maintained. If a message or warning is used in multiple places and if it changes, one place update in the messages and warning tab is adequate to update the test cases.
        ... Accessibility
        Accessibility test cases are written based corporate accessibility standards and guidelines.
        ... Globalization
        Globalization test cases are written based on your corporate globalization standards and guidelines.
        ... AccessControl
        Lists the Negative access control test cases. Positive access control is implicitly tested by running regular FVT test cases that are based on the roles that are provided in the test case itself.
        ... TestcaseMatrix
        The test case matrix summarizes the test cases into separate buckets.
      - Storefront Test Automation Engine usage
        This section describes how you can use the Storefront Test Automation Engine to use data files, enable change flows in tests, capture screenshots while tests are running, work with Secure Socket Layer certificates, and increase the reliability of your tests.
      - Setup and run tests
        The setup and run tests section describes the Storefront Test Automation Engine as well as the test bucket projects for starter stores. You can configure and run some tests to familiarize yourself with the assets.
      - Customizing tests
        You can create customized automation scripts for your storefront by extending specific scenario steps within the automation scripts. The advantage of extending the existing test bucket to create your own customized test bucket is that you can continue to use your customization when you acquire new releases of the Storefront Test Automation Engine.
      - Commerce Auto Generated Service Layer (CASL) test harness
        The commerce auto-generated service layer (CASL) framework is a test harness. CASL facilitates the process of building and transmitting REST or web service requests directly to the WebSphere Commerce Server, without the need of going through the storefront UI.
  - Extended sites starter store
    Use an extended sites starter store to get started on setting up an extended sites solution that will allow your selling organization to provide unique storefronts for different enterprise customers or showcase a number of branded storefronts.
  - Sample stores
    A sample store is for learning purposes and some tutorials can use a sample store. Do not use a sample store as the base for building your site. Sample stores might not be accessible or translated.
- 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

Updating the test case document: AccessControl

Lists the Negative access control test cases. Positive access control is implicitly tested by running regular FVT test cases that are based on the roles that are provided in the test case itself.

Procedure

New access control role added
1. Add access control test cases to verify the role updates.
2. Add negative access control test cases or reference to the newly written negative access control test cases.
Access to existing role updated
1. Add access control test cases to verify the role updates
2. Add negative access control test cases or reference to the newly written negative access control test cases