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

  5. Administration Console

    Site Administrators use the Administration Console to control a site or store by completing administrative operations and configuration tasks such as publishing stores, refreshing the registry, and scheduling jobs. You can access the Administration Console at a site-level, or for a particular store.

  6. Transport methods

    WebSphere Commerce provides several transport methods. By default, the e-mail transport method is configured and active. You can also use these transport methods: File, WebSphere MQ, or a sample adapter. You can configure transport methods for the site, or for particular stores.

  7. Deactivating a transport method for a site or store

    Transport methods are deactivated in the Administration Console

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

        • Stores in WebSphere Commerce

          WebSphere Commerce supports several different types of entities that are defined as stores. The assets of these store entities may be edited using the WebSphere Commerce Accelerator.

        • Enabling registered users to access all stores in the Extended Sites business model

          WebSphere Commerce users can access storefronts by virtue of having the role of Registered Customer in the organization that owns the store, or in any organization above it. The roles a user has access to during registration are defined within the MemberRegistrationAttributes.xml file.

        • Preparing WebSphere Commerce for the peak shopping periods

          When preparing for peak shopping periods, such as the holiday season, use the following best practices to effectively manage your WebSphere Commerce environment for peak efficiency, and to ensure that your WebSphere Commerce site is ready to handle the increased load.

        • Configuration Manager

          To configure a WebSphere Commerce or a WebSphere Commerce Payments instance, use the Configuration Manager. The Configuration Manager interface shows mandatory fields and provides help.

        • Administration Console

          Site Administrators use the Administration Console to control a site or store by completing administrative operations and configuration tasks such as publishing stores, refreshing the registry, and scheduling jobs. You can access the Administration Console at a site-level, or for a particular store.

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

          • Opening the Administration Console

            Users with Site Administrator access can open the Administration Console.

          • Enabling WebSphere Commerce components

            Enabling a component with the Administration Console enables the component until the WebSphere Commerce Server is restarted. To permanently enable a component use Configuration Manager.

          • Disabling WebSphere Commerce components

            Disabling a component using the Administration Console disables the component until the WebSphere Commerce Server is restarted. To permanently disable a component use Configuration Manager.

          • Registry Manager

            The Registry Manager maintains a set of registries for caching WebSphere Commerce runtime data. Each registry provides methods to enable adding, deleting, and refreshing of the registry content. These methods are available to the URL interface by using the ListRegistry and the RefreshRegistry commands.

          • Scheduler

            The Scheduler is a background server that schedules and launches jobs, both at the site and store levels. From the Configuration menu of the Administration Console, the scheduler allows Site Administrators to schedule and configure jobs.

          • Message resend

            Site Administrators can use the resend function in WebSphere Commerce to resend messages that are stored in the WebSphere Commerce system.

          • Transport methods

            WebSphere Commerce provides several transport methods. By default, the e-mail transport method is configured and active. You can also use these transport methods: File, WebSphere MQ, or a sample adapter. You can configure transport methods for the site, or for particular stores.

            • Configuring a transport method for the site

              Transport methods are configured in the Administration Console.

            • Configuring a transport method for a store

              Transport methods are configured in the Administration Console.

            • Adding a transport method to a site or store

              You can add a transport method to a site or store in the Administration Console.

            • Adding a transport method to a store

              Transport methods can be added to your store in the Administration Console.

            • Assigning a message type to a transport method for a site or store

              If you assign a message type to a particular transport, the transport must first be set active. By default, only the e-mail transport is active at the site-level. If the store does not have a message transport assignment, then the site assignment is used.

            • Deactivating a transport method for a site or store

              Transport methods are deactivated in the Administration Console

          • Message types

            WebSphere Commerce predefines several message types and sets them as active. You can change the parameters for message types.

        • Organization Administration Console

          The Organization Administration Console enables administrators to manage organizations, business users and member groups. Access Control policies can also be managed and approval requests can be processed.

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

Deactivating a transport method for a site or store

Transport methods are deactivated in the Administration Console

Procedure

  1. Open the Administration Console and select Store on the Administration Console Site/Store Selection page.
  2. Click Configuration > Transports. The Transport Configuration page displays.
  3. Click the check box next to the transport you want to deactivate.
  4. Click Change Status. The page reloads, and the status changes.
  • Share: Email
  • Twitter
  • Disclaimer
  • Privacy
  • Terms of use
  • Cookie Preferences