Tutorials > Customize > Rapid store development and deployment

< Previous


Run WebSphere Commerce utilities

This step explains the loading of the necessary assets into your store and also summarizes the tutorial.

In this step of the tutorial, we will use all of the utilities described in step 1 to extract, transform, resolve, and load the necessary assets into the store.

Before continuing with this step of the tutorial, ensure you have downloaded and extracted the ZIP file supplied in the resource section.

Follow these steps to execute the WebSphere Commerce utilities:


Procedure

  1. Select a subsystem to which a subset of data can be extracted (for example, this paper provides directories to help extract data for 'account', 'tax', 'catalog' and 'pricing') Note: For each example provided, there is a directory for each subset of data to be extracted. Each directory has its own 'extract.xml' file which can be updated using SQL to extract the subset of data you would need.

  2. From the Account example, change into the 'account' directory

    • From the source tower WCS instance, extract account data:

         Step1-extract.bat
      

    • From either the target tower or the source tower WCS instance, transform account data:

          Step2-transform.bat
      

    • From the target tower WCS instance, resolve identifiers:

         Step3-idresgen.bat
      

    • From target tower WCS instance, massload data:

         Step4-massload.bat
      

  3. From the Tax example, change into the 'tax' directory

    • From the source tower WCS instance, extract tax data:

          Step1-extract.bat
      

    • From either the target tower or the source tower WCS instance, transform tax data:

         Step2-transform.bat
      

    • From the target tower WCS instance, resolve identifiers:

         Step3-idresgen.bat
      

    • From target tower WCS instance, massload data:

         Step4-massload.bat
      

  4. From the Catalog Pricing example, change into the 'catalog' directory first

    • From the source tower WCS instance, extract catalog data:

          Step1-extract.bat
      

    • From either the target tower or the source tower WCS instance, transform catalog data:

          Step2-transform.bat
      

    • Change into the pricing directory and from the source tower WebSphere Commerce instance, extract catalog data:

         Step1-extract.bat
      

    • From either the target tower or the source tower WCS instance, transform catalog data:

         Step2-transform.bat
      

    • Merge the two transformed output files into a file called catalogPricingTransform.xml

    • From the target tower WCS instance, resolve identifiers:

         Step3-idresgen.bat
      

    • From the target tower WCS instance, massload data:

         Step4-massload.bat
      

  5. For each case, if the Step4-massload.bat was successful on your test database, then archive the transformed XML files

  6. Match the transformed XML files to the files found in the Store SAR

  7. Update the SAR with the new transformed XML files (for example, the tax files that are extracted and transformed can be mapped to existing tax files within the SAR)

  8. Either republish the updated SAR or massload the XML files on a new environment


Summary

In this tutorial you learned that there are utilities supplied by WebSphere Commerce which can extract, transform, resolve, and load store assets to other stores. You also learned that there are a series of steps that need to be done in order to use the rapid store solution. Those steps include consolidating the environment, identifying assets, consolidating asset templates, extracting data assets from source, transforming data assets, resolving identifiers on target, loading data assets on target, and packaging store assets. In step 2 you learned that the env.bat file needed to be updated to match the WebSphere Commerce configuration. Finally, in step 3 you learned that by running the supplied batch files, all the necessary utilities were executed in order to load the store assets.

< Previous


+

Search Tips   |   Advanced Search