wcs

IBM® WebSphere® Commerce V7.0 Feature Pack 8 delivers enhanced e-commerce capabilities for B2B businesses that help accelerate time-to-market and deliver engaging brand experiences through an updated WebSphere Commerce Aurora store. Using best practices for store implementations and management, the Aurora store now provides a single starter store that supports both B2C and B2B models and takes advantage of the WebSphere Commerce representational state transfer (REST) application programming interface (API). With Feature Pack 8, B2B and B2C businesses are able to benefit from leading capabilities designed to: ·          Enable sellers to engage with buyers through their chosen devices using Responsive Web Design (RWD) to optimize the storefront search and browse experience. ·          Achieve faster time-to-market for new campaigns and initiatives. IBM Commerce Composer for WebSphere Commerce reduces the dependency on IT departments and gives business users unprecedented control

         The introduction of IBM Commerce Composer for WebSphere Commerce (IBM Commerce Composer). Commerce Composer enhances the customer experience management capabilities of WebSphere Commerce and helps enable greater business user control over store creation, management, and preview by offering the ability to create and modify page layouts and content without the need for IT          Advanced, WYSIWYG HTML editing capabilities to help simplify the creation of web content through built-in CKEditor integration with Management Center          Support for responsive design to foster efficient management of a common experience across mobile, tablet, and desktop design        Pre-built integration to IBM Web Content Manager to help improve the creation and delivery of digital content to customers and enhance the online experience ·         Improved site search performance and scalability ·         An ecosystem of independent software vendors with pre-integrated solutions t

Objective: Through following steps, we will: a.         Use WCS search preprocess to create additional temporary tables to hold the flatten attributes. b.         Update Solr schema to support new fields c.         Update DIH configuration SQL to fetch new data from temporary table. d.         Extended search profile to allow new Solr fields to be in Solr search result e.         Update jsp to use new search profile. Procedure: 2.         Configuration in search preprocess: Add new configuration file in directory: WC_installdir /instances/ instance_name /search\pre-processConfig/ MC_ masterCatalogId / databaseType , For example:  search/MC_10001\DB2 a.         Name:  wc-dataimport-preprocess -<your own name> .xml ; keep the prefix as “wc-dataimport-preprocess”.  (A little trick is that you can name your own file name starting with “a”, for example, wc-dataimport-preprocess-a-mynewdata-attribute.xml ,so the pre-process shell script will run it first by al

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 WebSphere Commerce business objects. 3.              Allocates and resolves WebSphere 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 CSVReader then your input file must be a CSV file. The three configuration files are listed below. 1.              wc-dataload-env.xml 2.              wc-dataload-loader.xml 3.              wc-dataload.xml wc-dataload-env.xml holds the environment settings such as database name,encrypted password,data