Skip to main content

Difference between Accelerator and Management Centre

Management Centre vs Commerce Accelerator

1.For promotions and espot configurations, which is a better approach - management center or accelerator?
Considering the management center's design, its complex structure takes more time in implementing new modifications as compared to accelerator modifications.

2.We can view the status what change's we did in Management Center, If we did any wrong it shows an error, but in Accelerator the error is not shown.

3.Management center provides a rich UI with features like drag and drop. There is a possibility that in some future releases Commerce Accelerator may be removed. With current release it is not possible as it is tightly coupled with the framework.

4.For an end user perspective Management Center will be the preferred tool. Being a flash based tool it is slow but very user friendly.

5.Management Center, It's sometimes slow but it provides more usability such as drag and drop,etc which makes it a favorite tool for the business user.

=============

Accelerator:
Create content spot and schedule
Management Center:
Moving forward, no separate object for content spots, will be phased out
Content spot was originally created for performance reasons,
New caching of e-spots eliminates need for content spots
Now, changing from static (content spot) to dynamic (e-spot) content does not require change in code/jsp
Previous in Management Center – Campaign, Web Activity, Marketing Experiment, Email Activity, Promotion, Content
New in Management Center – Customer Segment, e-Spot, Dialog Activity

Comments

Popular posts from this blog

Issues While Starting WAS Server

This happens when there is other application which is also using the same port 8880. To resolve the issue, we need to find which application is using the port 8880 through 'netstat' command in command prompt or update our WAS server to not use 8880. We can update the WAS server through these steps: 1) Stop  WAS. 2) Browse to or search for the serverIndex.xml, for example, at "C:\WAS\AppServer\config\yourNode\nodes\yourNode\serverindex.xml" 3) Open the file and locate the following lines:               endPointName="SOAP_CONNECTOR_ADDRESS"> 4) Change "port 8880" to an available port 5) Save the serverindex.xml and restart WAS

Dataload Utility

Data can be loaded into WCS tables using data load utility. WCS Data Load utility performs the following functions in a single operation: 1.                Reads the data from the input source file. 2.                Transforms the source data to Web Sphere Commerce business objects. 3.                Allocates and resolves Web Sphere Commerce business objects to physical data. 4.                Loads the physical data into the database. There are three configurations files and a input source file required to complete the data loader setup. WCS supports only CSV File Reader for other input source you have to write your own Reader Class. This means that if you are using OOB CSV Reader then your input file must be...

Webpshere Commerce Registry

Registry is an another solution for those which can’t be cached using Dyna cache. Another use would be to store configuration data for a store. By using registry, you don't need a server   restart   every time as organization admin console provides an   interface   to refresh registry. The new custom registries will be appearing in the admin console under the   registry section. Steps to create a new custom registry in WCS Step 1. Register the registry in wc-server.xml. <Registries> ...... ..... <registry name="TestRegistry" regClassName="com.wcs.registry.TestRegistry "/>   </Registries> Step 2.Create  a class that implements   interface   com.ibm.commerce.registry.Registry package com.wcs.registry; import java.util.HashMap; import com.ibm.commerce. exception .ECException; import com.ibm.commerce.registry.Registry; import com.ibm.commerce.registry.RegistryManager;     public  cla...