Jump to main content
HCL Logo Product Documentation
Customer Support Software Academy Community Forums
IBM WebSphere Commerce V7
  • Product overview
  • WebSphere Commerce search
  • Precision marketing
  • What's new
  • User Guide
  • Reference
  • Other versions
  1. Home
  2. User Guide

    The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.

  3. Administering
  4. Deploying

    The topics in this section describe how to publish stores to either a test or production environment, and how to deploy customized code.

  5. Publishing a store archive

    Publishing a store archive to a WebSphere Commerce Server allows you to create a running store. You have two options for publishing a store archive: Publishing a store archive using the Publish wizard, Publishing a store archive using the publishstore utility.

  6. Publishing a store archive using the Publish wizard

    Use the Publish wizard to create stores and store-related components.

  7. Configuring publish

    To avoid publishing problems, set database attributes, disable summary tables and increase transaction log size before you publish a store archive.

  8. Ensuring appropriate services and servers are running for publishing

    Before you publish a store archive, ensure that the appropriate services and servers are running.

  • User Guide

    The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.

    • 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 this section for information about installing the WebSphere Commerce product, associated maintenance, and WebSphere Commerce enhancements.

    • Migrating

      Before you migrate WebSphere Commerce, review this information for an overview of the migration process.

    • Operating
    • Administering
      • Overview of administering a WebSphere Commerce site

        In WebSphere Commerce the person who performs administrative tasks is called a Site Administrator. The Site Administrator installs, configures, and maintains WebSphere Commerce and the associated software and hardware. The administrator responds to system warnings, alerts, and errors, and diagnoses and resolves system problems. Typically, this person controls access and authorization (creating and assigning members to the appropriate role), manages the Web site, monitors performance, and manages load balancing tasks. The Site Administrator might be responsible for establishing and maintaining several server configurations for different stages of development such as testing, staging, and production. The Site Administrator also handles critical system backups and resolves performance problems.

      • WebSphere Commerce instance

        Every WebSphere Commerce installation requires at least one instance to function, and each WebSphere Commerce instance can contain one or more stores.

      • WebSphere Commerce Payments instance
      • Managing features

        You can administer the features for your store and site, such as attribute, catalog, promotion, marketing, order management features, and more. The administration tasks that you can complete differ depending on the type of feature and the tool that you use to administer your store and site.

      • Logging services

        WebSphere Commerce provides facilities for logging. For existing customers, ECTrace and ECMessage are still supported. For new implementations, use the WebSphere Application Server recommendation for logging and tracing.

      • Business auditing

        Business auditing is the capturing of the business logic and objects during a WebSphere Commerce operation. You may want to audit your business for various reasons: generic, such as to review various tasks performed weekly; or specific, such as to track the steps involved in a particular Customer Service Representative's order. A report on business auditing is available in the Administration Console.

      • Business events

        Each time that a command triggers a business event, a record is added to the BUSEVENT database table to persist data from the event. Event listeners and external systems (such as the Marketing component, a back end order management system, or an external analytics system) can use this data to perform further processing.

      • Staging server

        The WebSphere Commerce staging server is a part of the production environment where business and technical users can update and manage store data and preview changes. The changes can then be propagated to the production server.

      • Administering the WebSphere Commerce database

        As a site administrator, maintain the WebSphere Commerce database and ensure that any WebSphere Commerce utilities and processes that load and retrieve data from the database is configured to connect to the database properly.

      • Dynamic caching

        In general, caching improves response time and reduces system load. Caching techniques are used to improve the performance of World Wide Web Internet applications. Most techniques cache static content (content that rarely changes) such as graphic and text files. However, many websites serve dynamic content, containing personalized information or data that changes more frequently. Caching dynamic content requires more sophisticated caching techniques, such as those provided by the WebSphere Application Server dynamic cache, a built-in service for caching and serving dynamic content.

      • Transforming, loading, and extracting data

        WebSphere Commerce provides multiple utilities for preparing and loading data into a WebSphere Commerce database. The loading utilities are flexible and you can continue to use these utilities when you customize the WebSphere Commerce schema.

      • Inventory sharing in extended sites stores (non-ATP)

        The extended sites business model provides scalability and manageability improvements for WebSphere Commerce sites where there are multiple stores which can share assets including non-ATP inventory. The sharing of non-ATP inventory reduces the complexity of managing inventory assets for all the stores in the site. All stores in extended sites can share inventory from a single asset store with distributed fulfillment centers.

      • Tax sharing in an Extended Site model

        In extended sites store model, tax assets can be shared between the extended site asset store and the extended site store. You can manage the tax assets in an extended site store in WebSphere Commerce Accelerator.

      • Payment plug-ins
      • Deploying

        The topics in this section describe how to publish stores to either a test or production environment, and how to deploy customized code.

        • WebSphere Commerce Build and Deployment tool

          The WebSphere Commerce Build and Deployment tool is designed to address the error-prone and time-consuming nature of customized asset deployment. Manual customized asset deployment involves accessing and updating numerous systems, including your database, web server, application server, and WebSphere Commerce server. Manual customization can be problematic, especially for a production environment where downtime has a negative impact on the business. For a customization project with many developers, it is a challenge to ensure that each development environment setup is quick, easy, and repeatable to preserve productivity. The WebSphere Commerce Build and Deployment tool provides a starting point for you to automate your build and deployment processes in a standardized, controlled manner.

        • Managed asset deployment

          Managed assets are files that are uploaded by business users to be used for store marketing, or to supplement products. They are added to WebSphere Commerce through the Assets tool or the Marketing tool in Management Center. By default, managed assets are extracted and deployed through the WebSphere Commerce EAR. To maintain performance in a large-scale production environment, site administrators must switch to alternative extraction and deployment methods for managed assets.

        • Deploying customized assets

          When you deploy customized assets for WebSphere Commerce, consider the two stages: packaging and deploying.

        • Minimizing downtime during deployment

          Your WebSphere Commerce site is an integral part of your company's revenue flow, so disruptions and any downtime should be minimized. Moreover, taking down a site for long periods of time or frequently, reflects on the store's credibility and impacts the customer's shopping experience with and potential return visits to the site.

        • How to increase your success with WebSphere Commerce deployment

          Use these tips and best practices to help you successfully deploy WebSphere Commerce.

        • WebSphere Commerce deployment checklist

          The WebSphere Commerce deployment checklist is based on lessons learned from IBM internal groups, external customers and business partners deploying WebSphere Commerce-based solutions. This checklist is intended to provoke discussion; it is not a detailed set of instructions.

        • ***
        • Publishing a store archive

          Publishing a store archive to a WebSphere Commerce Server allows you to create a running store. You have two options for publishing a store archive: Publishing a store archive using the Publish wizard, Publishing a store archive using the publishstore utility.

          • Publishing a store archive using the Publish wizard

            Use the Publish wizard to create stores and store-related components.

            • Publishing organization structure store archives

              Publishing an organization structure store archive creates the organization structure, predefined user roles, and necessary access control policies for the selected business model in the database.

            • Publishing component store archives

              In order to publish any component store archives other than an organization structure store archive, you must first publish either a composite store archive, or an organization structure, as all component store archives must belong to an organization structure.

            • Publishing multiple store archives of one type per instance

              If a composite store archive for a store type is published, you can publish multiple composite store archives of the store type. Similarly, if a corresponding organization structure store archive for a store type is published, you can publish multiple organization structure store archives for the store type.

            • Options for publishing extended site store archives

              There are two methods for publishing an extended sites environment using the starter store archives. In both cases, the published environment includes the extended site store, the asset stores, a hub store, the organization structure, predefined user roles, and necessary access control policies. You can use the environment to learn about extended site structure and features.

            • Configuring publish

              To avoid publishing problems, set database attributes, disable summary tables and increase transaction log size before you publish a store archive.

              • Ensuring appropriate services and servers are running for publishing

                Before you publish a store archive, ensure that the appropriate services and servers are running.

              • Publish wizard parameters by store archive

                The parameters that are displayed in the Parameters page of the Publish wizard vary depending on the store archive that is selected.

            • Viewing publish status

              Use the Administration Console to view the status of your publishing jobs.

            • Adding a new store archive to the Publish wizard

              You can add a store archive to the Publish wizard in either the default view, or in a particular view. You must have Site Administrator access to complete either of these tasks.

          • Publishing a store archive using the publishstore utility

            Although the primary method of publishing a store archive is through the Administration Console, you can also publish a store archive using the command line. Only one store can be published at a time.

          • Publishing a WebSphere Commerce version 5.6.1 store archive in WebSphere Commerce version 7.0

            To publish a WebSphere Commerce version 5.6.1 store archive in WebSphere Commerce version 7.0, you must first migrate the store archive to WebSphere Commerce version 7.0.

          • Deleting a published store

            When you publish a store using WebSphere Commerce, store assets and database objects are saved within the WebSphere Commerce Server. If you want to delete the store, you must ensure that it is cleaned from the WebSphere Commerce system. You might want to delete a store if you encountered problems when you tried to publish the store, or you have a corrupted store. Once the store is cleaned from the WebSphere Commerce system, you can republish it.

          • Business accounts and contracts

            Some of the store database assets, (business accounts, and contracts) cannot be loaded by the loading utilities. You can publish these database assets by using the Administration Console or from the command line, as part of the Publish process, or you can publish business accounts and contracts using their corresponding commands.

          • Store publish process

            In order to create a functioning store, the storefront Web assets must be published to the WebSphere Commerce Server, and the store data must be published to the WebSphere Commerce database. In order to publish a store, you must have Site Administrator authority. Site Administrators can initiate the publish process using either of the following methods: Publish wizard, publishstore utility.

          • Publishing your store

            In order to create a functioning store, the storefront Web assets must be published to the WebSphere Commerce Server, and the store data must be published to the WebSphere Commerce database.

          • Publish wizard configuration parameters

            You can change the behavior of the Publish wizard by modifying configuration parameters in the WebSphere Commerce configuration file.

          • Publish wizard publish parameters

            The publish parameters used by the Publish wizard are defined by the store-refs.xml file in each store archive. Publishing parameters are only available through the Publish wizard. If you publish a store archive through the command line, you cannot specify parameter values. The default values contained in the store archive file are used.

          • Displaying additional stores in the Publish wizard

            Certain store archive (SAR) files are not displayed in the Publish wizard in the Administration Console. For example, store archives for deprecated stores are not displayed. If you want to publish these stores using the Publish wizard, you can move them to a location that makes them available for selection in the Publish wizard.

          • JSP batch compiler

            Compiling the JavaServer Page (JSP) files in your site or store will significantly reduce the amount of time needed to load your store. As a result, it is recommended that you batch-compile your store or site JSP files after publishing a store archive and after deploying JSP files to a production environment.

        • WebSphere Commerce store archive separation

          WebSphere Commerce provides the capability to separate the store (WAR) web application archive from the WebSphere Commerce (EAR) enterprise archive. When store developers create or change store assets, the assets must be included within the store WAR. Separating the store WAR from the WebSphere Commerce EAR, creates a new store EAR that contains a copy of the store WAR. Separating the store WAR can provide store developers the capability of packaging and deploying assets independently of developers that are deploying non-storefront assets.

      • WebSphere MQ

        WebSphere Commerce provides a listener for WebSphere MQ (formerly MQSeries) for inbound requests and an adapter for WebSphere MQ for outbound requests to allow you to integrate back-end and external systems with WebSphere Commerce using WebSphere MQ.

      • IBM Sales Center for WebSphere Commerce

        Today's marketplace includes inbound call centers where Customer Service Representatives (CSRs) manage inquiries from potential customers. The IBM Sales Center for WebSphere Commerce manages stores, customers, organizations, orders, quotes, and payment information. The IBM Sales Center is a rich client interface which is installed on CSRs' systems.

      • WebSphere Commerce integration with WebSphere Portal

        WebSphere Commerce provides integration code and support for WebSphere Portal Server. This integration allows to you aggregate WebSphere Commerce services and other content in a portal interaction environment.

      • Pinterest integration

        You can integrate WebSphere Commerce with Pinterest through Pinterest Buyable Pins that are available through the Pinterest iOS app. Use the WebSphere Commerce Pinterest Integration Accelerator to help with integration.

      • 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.

      • IBM Dynamic Pricing integration

        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.

      • 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.

      • Administering WebSphere Commerce search

        For a fully functioning WebSphere Commerce search implementation, you must understand and complete the search administration tasks which include deployment, search index management, and ongoing maintenance.

      • Configuring a cloned WebSphere Commerce environment

        A cloned virtual environment creates a separate copy of the original web server, application server, and database. After you clone a WebSphere Commerce virtual environment, you need to configure the clone to differentiate from the original environment.

      • Deploying a WebSphere Commerce dual cell environment

        Consider deploying a dual cell environment to achieve continuous availability and ensure that shoppers are minimally affected by planned or unplanned outages.

    • Tutorials

      WebSphere Commerce provides many tutorials.

    • 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

Ensuring appropriate services and servers are running for publishing

Before you publish a store archive, ensure that the appropriate services and servers are running.

Procedure

  1. Ensure that the database is started.
  2. Ensure that the Web server is started.
  3. WebSphere Commerce Developer Ensure that WebSphere Commerce is started.
  4. Ensure that WebSphere Commerce Payments is started.
  • Share: Email
  • Twitter
  • Disclaimer
  • Privacy
  • Terms of use
  • Cookie Preferences