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.
Developing
The topics in the Developing section describe tasks performed by an application developer.
Customizing WebSphere Commerce
You can extend the WebSphere Commerce product to fit your business needs. This topic describes the prerequisite skills and required knowledge that you need to customize business logic. After you have the required knowledge, use WebSphere Commerce Developer to take tutorials that guide you step-by-step through various customization scenarios.
Trading subsystem
Extensions to terms and conditions
You can use the special purpose entity bean, ExtendedTermConditionAccessBean and the corresponding data bean, ExtendedTermConditionDataBean, to extend the Terms and conditions ("terms") provided with WebSphere Commerce. Use the entity and data bean to provide access to the TERMCOND table.
Importing and exporting contracts with extended terms defined
Contracts to be imported can now have terms that are attached to them. The additional terms and the properties for those terms must exist in the TCMappingRegistry. In the contract.xml file that is used to import the contract by using WebSphere Commerce Accelerator, you update the file to include the TermCondition element.

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
- Developing
  The topics in the Developing section describe tasks performed by an application developer.
  - Functional architecture
    Functional architecture provides both the set of patterns used to implement the business functionality and the frameworks in which these business functions execute.
  - Persistent object model
    WebSphere Commerce deals with a large amount of persistent data. There are numerous tables defined in the current database schema. Even with this extensive schema, however, you might need to extend or customize the database schema for your particular business needs.
  - Presentation layer
    WebSphere Commerce uses Java Server Pages (JSP) to implement the view layer of the Model-View-Controller (MVC) design pattern. The view layer is in charge of retrieving data from the database through the use of data beans and formatting it to meet the display requirements. The view layers determines whether the request is sent to a browser or streamed out as XML. JSP files present a clean separation between data content and presentation.
  - Controller layer
    The Controller layer is the conductor of operations for a request. It controls the transaction scope and manages the session related information for the request. The controller first dispatches to a command and then calls the appropriate view processing logic to render the response.
  - Business logic layer
    The business logic layer is the business components that provide OAGIS services to return data or start business processes. The presentation layer uses these OAGIS services to display data, or to invoke a business process. The business logic provides data required by the presentation layer. The business logic layer exists because more than just fetching and updating data is required by an application; there is also additional business logic independent of the presentation layer.
  - Persistence layer
    The interaction between the business objects and persistence layer is isolated in an object called the Business Object Mediator. Business object document (BOD) commands interact with the Business Object Mediator to handle the interaction with the logical objects and how they are persisted.
  - Business model information model
    A business model, a representation of the business processes used throughout the site, provides a sample commerce solution which includes an organization structure, default user roles and access control policies, one or more starter stores, administration tools, and business processes that demonstrate best practices. A business model can be customized to support business requirements and scenarios. WebSphere Commerce provides sample business models that show some common commerce solutions. These business models are created by setting up an organization hierarchy structure, access control policies, stores, and contracts that help satisfy the necessary business requirements.
  - Business models
    Before starting to develop your site with WebSphere Commerce, you need to determine the business model supported by WebSphere Commerce that best represents the purpose of your site. Usually sites created with WebSphere Commerce will be implemented based on of one of these business models.
  - Store data information model
    Store data is the information that is loaded into the WebSphere Commerce Server database, which allows your store to function. The URL Registry Entries and View Registry Entries packages are included in the diagram, but they are not database assets. These entries are presentation configuration (that is, struts actions and forwards) that must be deployed. URL registry entries are shown in the diagram to illustrate the entire store data information model. To operate properly, a store must have the data in place to support all customer activities. For example, in order for a customer to make a purchase, your store must contain a catalog of goods for sale (catalog data), the data associated with processing orders (tax and shipping data), and the inventory to fulfill the request (inventory and fulfillment data).
  - Customizing WebSphere Commerce
    You can extend the WebSphere Commerce product to fit your business needs. This topic describes the prerequisite skills and required knowledge that you need to customize business logic. After you have the required knowledge, use WebSphere Commerce Developer to take tutorials that guide you step-by-step through various customization scenarios.
    - Understanding access control
      Access control in a WebSphere Commerce application is composed of the following elements: users, actions, resources, and relationships.
    - Supporting globalization
      The WebSphere Commerce architecture is designed to support globalization. Globalization is the proper design and execution of systems, software, services, and procedures so that one instance of software, running on a single server or end-user machine, can process multilingual data and present culturally correct data in a multicultural environment such as the Internet.
    - Adding and modifying price lists and price policies
      You can add additional price lists, if you require multiple price lists to support cost and list prices.
    - Business relationship assets
    - Catalog subsystem
      The catalog subsystem is a component of the WebSphere Commerce Server that provides online catalog navigation, partitioning, categorization, and associations. In addition, the catalog subsystem includes support for personalized interest lists and custom catalog display pages. The catalog subsystem contains all logic and data relevant to an online catalog, including catalog groups (or categories), catalog entries, and any associations or relationships among them.
    - Member subsystem
      The Member subsystem is a component of the WebSphere Commerce Server that includes data for participants of the WebSphere Commerce system. A member can be a user, a group of users (also known as a member group), or an organizational entity (which can be an organization, such as "IBM" or an organizational unit within an organization, such as "Electronic Commerce Division"). Business logic in the Member subsystem provides member registration and profile management services. Other services which are closely related to the Member subsystem include access control, authentication, and session management.
    - Currency
      You can display prices in your site in one currency, or you can use multiple currencies by following the instructions for the euro. For a site with multiple stores, you can use different currencies for the stores, or you can assign currencies to the store group. Depending on the type of site that you are creating, you can specify what currencies you want to use and how they are displayed. You can also allow customers to select a shopping currency.
    - Returns
    - Tax codes
      A tax calculation code indicates the tax calculation for order items. A store typically collects two type of taxes: sales or use tax, and shipping tax. The tax codes are unique within each tax type for a store. Only one tax calculation code of each tax type is applied to a particular order item.
    - Calculation framework
      Commerce systems need to calculate monetary amounts and apply them to business objects. Business rules and legal requirements specify how and when these monetary amounts should be calculated. When these rules and requirements change, a good commerce system can adapt to the changes with little or no programming changes.
    - Order Management subsystem
      The Order Management subsystem is a component of the WebSphere Commerce Server that provides shopping carts, order capture, order fulfillment, inventory, and payment function support.
    - Stored procedure error codes
      The following table describes the error codes that are returned by specific WebSphere Commerce stored procedures. You should receive these error messages only when a problem with the data requires further investigation by a technical person. If you receive one of these errors (other than error code 0) and you cannot determine the cause of the error, contact IBM WebSphere Commerce support for assistance.
    - Trading subsystem
      - WebSphere Commerce business policy framework
        Business policies are sets of rules followed by a store or group of stores that define business processes, industry practices, the scope and characteristics of a store or group of stores offerings, and how the store or site interacts with customers and other partners. For example, your site may have business policies determining when and how customers are allowed to return products to a store, or business policies that determine what payment methods your store accepts.
      - Extensions to terms and conditions
        You can use the special purpose entity bean, ExtendedTermConditionAccessBean and the corresponding data bean, ExtendedTermConditionDataBean, to extend the Terms and conditions ("terms") provided with WebSphere Commerce. Use the entity and data bean to provide access to the TERMCOND table.
        Creating an extended term and condition type for contracts and accounts
        You can create an extended term and condition (term) type for contracts and accounts. Create a term type when you need to supplement the default term types that are provided by WebSphere Commerce. For instance, when you have a preferred customer that you want to waive the application of a surcharge, or perhaps provide a different surcharge. A flexible surcharge waiver term is not provided by default, so to provide that term, you can create an extended term type.
        TCConfiguration.xml file
        The following table provides details for the attributes that you can use to define new term types within the TCConfigurationExt.xml file.
        Deploying custom extended terms
        When you created the entry in the TCSUBTYPE table for an extended term, you had a choice of specifying its deploy command. If you did not specify the value, then no deployment command is called to deploy the extended term during the contract deployment process.
        Importing and exporting contracts with extended terms defined
        Contracts to be imported can now have terms that are attached to them. The additional terms and the properties for those terms must exist in the TCMappingRegistry. In the contract.xml file that is used to import the contract by using WebSphere Commerce Accelerator, you update the file to include the TermCondition element.
        Adding a term to a contract or account
        Adding a term to a contract in draft state is straightforward. The term types that are defined in the TCConfigurationExt.xml file and the TCSUBTYPE table. The term types are loaded to TCMappingRegistry. You can open the contract and enter the values for the term properties. After the values are validated according to the data type of the TERMCOND table column to which they are mapped, the values are saved to the TERMCOND table. The number of properties for a term is limited by the columns of the TERMCOND table. If more properties are required, you must either change the table schema to add more columns (not recommended), or create an extra term to contain the properties.
        Updating extended terms of a contract or account
        Use WebSphere Commerce Accelerator to change the values of terms in contracts or accounts.
  - WebSphere Commerce development environment
    WebSphere Commerce Developer is the development toolkit for customizing a WebSphere Commerce application.
  - Web services and WebSphere Commerce
    A web service is an interface that describes a collection of operations that are accessible through the network by using standardized XML messaging.
  - WebSphere Commerce Search
    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.
- 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

WebSphere Commerce Enterprise

Importing and exporting contracts with extended terms defined

Contracts to be imported can now have terms that are attached to them. The additional terms and the properties for those terms must exist in the TCMappingRegistry. In the contract.xml file that is used to import the contract by using WebSphere Commerce Accelerator, you update the file to include the TermCondition element.

In the following example, the waiveSurCharge indicator is set to the Integer value 1 and the surChargeAmount is set to the Double value 50.00.


<BuyerContract>
...
<TermCondition type='SurChargeTC'>
        <Property name='waiveSurCharge' value='1'>
        <Property name='surChargeAmount' value='50.00'>
</TermCondition>
...
</BuyerContract>

The value attribute of the TermCondition element is mandatory and its value must match the type that you defined in the TCConfigurationExt.xml file.

When contracts to be exported contain extended terms, the extended terms are copied to the exported file, as shown in Copying and duplicating contracts.