Configuration Manager - Commerce - Components
You can use the Configuration Manager to enable components, disable existing components, or create new components.
The following components are created automatically with your WebSphere Commerce instance:
Component | Enabled by default | Description |
---|---|---|
AccessLoggingEventListener | No | Enable access logging |
BusinessAuditCommandEventListener | Yes | Enabling business auditing |
BusinessFlowEventListener | Yes | Enabling business auditing |
Campaign Logging Event | No | Configuring Marketing Events statistical counters |
Campaign Logging Event Listener | No | Configuring Marketing Events statistical counters |
CampaignsCachingComponent | No | Enables the event that invalidates the cache that stores the content to be displayed in a Content Spot. See Cache invalidation |
ChangeExternalOrdersEventListener | No | Calls outbound change order services to notify the external orders system to change orders. |
Component Boot Manager | Yes | Preloads a set of components on server start up to avoid wait time on the first service call. |
ContentCacheInvalComponent | Yes | Cache invalidation |
DynaCacheCookie | No | Cache invalidation |
DynaCacheFilterMappings | Yes | Configures the mapping of request attributes to business context interfaces or custom implementations. See Dynamic caching. |
Enable Store Services | Yes | Reserved for IBM internal use. Do not disable this component. |
Experiment Evaluation Event Listener | No | Correlates a submitted order with the Marketing Experiment test elements that were displayed to the user. See Configuring Marketing Events statistical counters |
Experiment Logging Event | No | Enables the event that captures Marketing Experiment log and statistical data. See Configuring Marketing Events statistical counters |
Experiment Logging Event Listener | No | Updates the Marketing Experiment log and statistics tables with the Marketing Experiment log
information. See Configuring Marketing Events statistical counters. Note: You need to enable the appropriate marketing
listener to support some behavioral marketing features. For more information, see Enabling Management Center marketing features in the WebSphere Commerce configuration
file. |
Listener for IBM MQ (Transport Adapter) | No | Enabling the Listener for IBM MQ |
MessageMapperGroup | Yes | Adding message mappers |
Migrate Guest Orders Event Listener | No | Enabling persistent sessions globally |
Order Cost Calculation Event Listener | No | Enabling business events |
Order Creation Event | No | Enabling business events |
Order History Event Listener | No | Enabling business events |
Order Item Creation Event | No | Enabling business events |
Order Item Update Event | No | Enabling business events |
Order Submission Event | No | Enabling business events |
OrderCancellation Event | Yes | Enabling business events |
OrderItemShipment Event | Yes | Enabling business events |
OrderSubmit Event | Yes | Configuring Marketing Events statistical counters |
OrdersMgpPersistListener | Yes | Configuring Marketing Events statistical counters |
Payment Authorization Complete Event | Yes | Enabling business events |
Payment Rule Event | Yes | Payment events and task commands |
Payment Rule Listener | Yes | Payment events and task commands |
PaymentsPluginComponent | Yes | Payment plug-ins |
Perf Monitor | Yes | Enables custom performance counters for the Performance Monitor. |
Post Publish Event Listener | Yes | An implementation of WCSEventListener that listens for Common Base Event events and processes post-publish events. It is recommended that you do not change the default setting. |
RedirectEventListener | Yes | Listens for 301 redirects to occur. For more information, see URL redirects for SEO Overview |
Rule-based Discount Configuration | Yes | Initializes the runtime engine configuration for rule-based discounts (promotions). |
Scheduler | Yes | Scheduler |
Search Indexing Complete Event Listener | Yes | Processes search indexing complete events. |
SensorEventListener | No | If you want to use certain triggers and targets in marketing activities that wait for customer behaviors or events to occur, you must enable the sensor event listener. See Enabling Management Center marketing features in the WebSphere Commerce configuration file |
Telesales Response Builder Registry Configuration | Yes | This entry points to the response builder registry. You can use the default, or create a custom response builder registry. |
Tools | Yes | Enables or disables the Tools Framework for the WebSphere Commerce Accelerator. It is recommended that you do not change the default setting. |
UrlMapperConfig | No | Optimizing your site for search engines |
User Creation Update Event | Yes | An event that is triggered when the UserRegistrationAdminAddCmdImpl or UserRegistrationAdminUpdateCmdImpl commands are called to create or update a user. These commands are used in Organization Administration Console and WebSphere Commerce Accelerator. |
UserEntriesMigrationrEventForOrdeListener | No | Enabling order migration for guest shoppers |
UserTrafficEventListener | No | Configuring caching to capture user traffic data |
Wallet Guest User Migration Event Listener | Yes | Migrates a shopper's wallet from the old user to the new user. |
To create a new component, right-click on Components and select Create component. Complete the fields in the component wizard as follows:
- Component Name
- This is the name that you want to assign to the component that you are creating.
- Component Class Name
- This is the name of the class that will be associated with the new component
- Enable Component
- Select this check box if you want this component to be active immediately.
- Generate properties files only
- Select this box if you want to generate the properties files without enabling the component.
When you have completed all the fields, select Finish.