Full Source Code Manual Installation

{anchor:Start ScreenSteps Content}
This guide will explain how to set up the ECF Full Source package manually on your local machine. A typical installation will take about 1 hour, but will vary depending on your knowledge and experience with IIS and ECF.

If this is your first time manually installing ECF, this might feel overwhelming. A good knowledge of IIS, SQL Server, and XML will be helpful, but we provide step-by-step instructions to show one of common ways to install the package.

*Before proceeding*, review the System Requirements *[here|ecf51installanddeploy:System Requirements]*.


h3. Overview


Here's an overview of what you'll be doing during the full source code manual installation:

*Step 1*: Unzipping the ECF package
*Step 2*: Setting up your Web server
*Step 3*: Setting up your SQL Server database
*Step 4*: Modifying the config files to fit your environment
*Step 5*: Compiling your Full Source solution in Visual Studio
*Step 6*: Importing the Sample Site, catalogs, and Indexing your Search
*Step 7*: Starting your Quartz service
*Step 8*: Installing a license key

h3. Step 1: Unzipping the ECF Package


Once you obtain the Mediachase.ECF.FullSource package, unzip it and place the folder in a location you will be setting up the site (i.g., C:\Program Files or any other location you prefer).

For information on obtaining a package for evaluation or for purchase, please contact *[Sales|mailto:sales@mediachase.com]*.


h3. Step 2: Setting Up Web Server


*Configure Your Web Server for Window Server 2008, Windows 7, and Vista (IIS 7)*

Setup the Web Server by configuring IIS settings for Windows Server 2008, Windows 7 or Vista.

If you have a different operating system, select the appropriate links here to follow the instructions specific to the your system.

| *IIS5* | *IIS6* |
| [Web Server Setup for XP|#IIS 5 XP] | [Web Server Setup for Winodows Server 2003|#IIS 6 2003] |

1. Start Internet Information Services (IIS).

If you are using Windows Server 2008, go to *Start > Administrative Tools > Internet Information Services (IIS) Manager    *
        If you are using Windows 7, select *Start >* and type *"IIS"* in the search field.

2. Stop the Default Web Site

3. Add a new web site
* Right click on *Sites* and then click on *Add New Site*
* Enter into the following fields:
** Site name: "eCommerceFramework - 80" or whatever you like
** Application pool: Keep it same as the site name
** Physical path: *C:\Mediachase.ECF.FullSource\PublicLayer\SDKs\B2CSampleSite* (or any other location you are using to set up the ECF)

4. Create a new Application Pool with a name identical to the Site name (e.g., eCommerceFramework - 80 in this case).
* Choose ".NET Framework v2.0.50727" for .NET Framework version option.
* Choose "Classic" for "Manage pipeline mode" option.

5. Add 3 Virtual Directories (*\_cmsbase*, *\_cmsctrls*, *Apps*) under the "eCommerceFramework - 80" web site you just created. This can be done by right clicking on the "eCommerceFramework - 80" web site and select the command to add a new virtual directory.

* First for "_cmsbase," enter the following information:
** Alias: \_cmsbase
** Physical path: "Mediachase.ECF.FullSource\PublicLayer\Cms.Website\ \_cmsbase"
** Virtual Directory Access Permission: Read & Execute
* Second for \_cmsctrls, enter the following information:
** Alias: \_cmsctrls
** Physical path: "Mediachase.ECF.FullSource\PublicLayer\Cms.Website\ \_cmsctrls"
** Virtual Directory Access Permission: Read & Execute
* Third for Apps, enter the following information:
** Alias: Apps
** Physical path: "Mediachase.ECF.FullSource\AdminLayer\ConsoleManager\Apps"
** Virtual Directory Access Permission: Read & Execute

Once you are done with these steps you should see something like this:



!ManualInstallationIIS7new.png|border=1!



{anchor: Step3}


h3. Step 3: Setting Up Your SQL Database


*Note:* Please ensure that the database name, database user name, and database user password you use to create this database is unique.

Open a command prompt and go to *Mediachase.ECF.FullSource\SqlScripts\Helpers*. Then run the following command:

{code}
call setup.bat (database admin user) (db admin password) (db server name) (db name) (db user) (db user password) (application name)
{code}

* *database admin user*: Admin username of the server hosting the database
* *db admin password*: Password associated with the admin username of the server hosting the database
* *db server name*: Name of the server
* *db name*: Choose the name of the database that will be created (e.g. ECF51_(VERSION#)_(InstalledDate))
* *db user*: Set a username that will access Commerce Manager
* *db user password*: Choose the password associated with the user you're creating
* *application name*: Set the application name of your choice when you're logging into Commerce Manager (e.g. ecommerceframework)

After you run the command you'll see the command line re-appear when the script is done.


!ManualInstallationDB_B2CSampleSite.png|thumbnail,border=1!


If the script ran successfully, you'll see the new database created in your SQL Server. If you access the Tables folder of the database as the image about, you should also see hundreds of table listed there

h3. Step 4: Updating your Configuration Files


You have two options for working with your config files.

  1) Use a [UpdateConfig|#Help Tool to Update Configuration Files] tool we provide in the package to expedite this process.  

  2) Use any text editor, such as Notepad, to manually modify all your ECF configuration files.

  If you choose to take option 2), you will need to edit the five types of configuration files located in the B2CSampleSite, Console Manager, Quartz Service, and LicenseManager folders. Read on for more details:

* connectionStrings.config
* Web.config
* ecf.app.config
* Mediachase.Search.config
* baf.config

*Configure Database Connection Strings*

The connectionStrings.config files are used to point the ECF solution your database you created in step 3 above.

The files are located in the following 3 places:
* \~\PublicLayer\SDKs\B2CSampleSite\connectionStrings.config
* \~\AdminLayer\ConsoleManager\connectionStrings.config
* \~\QuartzService\connectionStrings.config

Open the files and you'll see the placehoder values in all caps as shown here. Replace the placeholders with your database information.

{code}
<?xml version="1.0" encoding="utf-8"?>
<connectionStrings>
<add name="EcfSqlConnection" connectionString="Data Source=DATABASE SERVER;Initial Catalog=DATABASE NAME;User ID=SQL ADMIN;Password=SQL ADMIN PASSWORD;Application Name=eCommerceFramework" />
<add name="XmlActionSetProvider" connectionString="~/_cmsbase/Design/actions.config" providerName="XmlActionSetProvider" />
</connectionStrings>
{code}

+Property Definitions:+

* DATABASE SERVER: SQL Server name (e.g. localhost)
* DATABASE NAME: Name you set up for the database. In our example, it would be ECF51_B2CSampleSite.
* SQL ADMIN: Username for the SQL Administrator
* ADMIN PASSWORD: Password for the SQL Administrator

For more information on how ConnectionStrings elements are configured refer to [http://msdn.microsoft.com/en-us/library/bf7sd233.aspx].

*Configure Web Config Files*

The Web.config files are located the following two places:

* \~\PublicLayer\SDKs\B2CSampleSite\Web.config
* \~\AdminLayer\ConsoleManager\Web.config

Open the files and do a search on the following keywords:

Keyword 1: bin

<licenseProvider defaultProvider="sqlProvider" allowUpload="True" licenseServerUri="http://licensing.mediachase.com/2.0/License.aspx">
<providers>
<add name="fileProvider" type="Mediachase.Licensing.FileStorageProvider, Mediachase.Licensing" storagePath="(SITE ROOT FOLDER)\bin" />
<add name="sqlProvider" type="Mediachase.Licensing.SqlStorageProvider, Mediachase.Licensing" connectionStringName="EcfSqlConnection" tableName="" createTable="True" />
</providers>
</licenseProvider>
{code}

Keyword 2: NotificationTemplates The information pertaining to Order confirmation email templates will be the following With this search, you will be directed to the lines shown below.

{code:xml}
<templateService defaultProvider="XslTemplateProvider">
<providers>
<add name="XslTemplateProvider" type="Mediachase.Commerce.Engine.Template.Providers.XslTemplateProvider, Mediachase.Commerce" applicationName="APPLICATION NAME" templateSource="(SITE ROOT FOLDER)\App_Data\EmailTemplates(0)(1).xsl" />
</providers>
</templateService>
{code}

The contents of NotificationTemplates folder in the Full source package is located in \~\PublicLayer\Templates. Therefore, you will need to replace the (SITE ROOT FOLDER)\NotificationTemplates(0)(1).xsl with C:\Mediachase.ECF.FullSource.5.1.XX\PublicLayer\Templates(0)(1).xsl

Keyword 3: applicationName there are five applicationNames "Application Name" that needs to be specified. Just as the above step, replace "Application Name" with "eCommerceFramework", or an application name of your choosing.

{code:xml}
<dataService defaultProvider="SqlDataProvider">
<providers>
<add name="SqlDataProvider" type="Mediachase.Data.Provider.SqlDataProvider, Mediachase.SqlDataProvider" connectionStringName="EcfSqlConnection" applicationName="APPLICATION NAME" />
</providers>
</dataService>
{code}

{code:xml}
<imageService defaultProvider="HandlerImageProvider">
<providers>
<add name="HandlerImageProvider" type="Mediachase.Commerce.Engine.Images.Providers.HandlerImageProvider, Mediachase.Commerce" urlFormatString="~/images/t/(0).image.ashx" applicationName="APPLICATION NAME" />
</providers>
</imageService>
{code}
{code:xml}
<templateService defaultProvider="XslTemplateProvider">
<providers>
<add name="XslTemplateProvider" type="Mediachase.Commerce.Engine.Template.Providers.XslTemplateProvider, Mediachase.Commerce" applicationName="APPLICATION NAME" templateSource="(SITE ROOT FOLDER)\App_Data\EmailTemplates(0)(1).xsl" />
</providers>
</templateService>
{code}

{code:xml}
<membership defaultProvider="CMSMembershipProvider">
<providers>
<add connectionStringName="EcfSqlConnection" applicationName="eCommerceFramework" enablePasswordRetrieval="true" enablePasswordReset="false" requiresQuestionAndAnswer="false" requiresUniqueEmail="true" passwordFormat="Clear" passwordStrengthRegularExpression="" minRequiredPasswordLength="4" minRequiredNonalphanumericCharacters="0" name="CMSMembershipProvider" type="Mediachase.Commerce.Customers.Profile.Providers.CustomerSqlMembershipProvider, Mediachase.Commerce" />
</providers>
</membership>
{code}

{code:xml}
<roleManager enabled="true" cacheRolesInCookie="true" defaultProvider="CMSRoleProvider">
<providers>
<add connectionStringName="EcfSqlConnection" applicationName="eCommerceFramework" name="CMSRoleProvider" type="Mediachase.Commerce.Customers.Profile.Providers.CustomerSqlRoleProvider, Mediachase.Commerce" />
</providers>
</roleManager>
{code}
*Configure Search Index Folder*

In this section you will configure the Search Index folder for indexing catalogs. This is necessary so that the catalog items stored in database will be correctly displayed in the public front-end store.

Before you open the config files, first manually create a folder called "SearchIndex" in the root level of your solution package or anywhere else that is convenient for you.
Then, we will edit the Mediachase.Search.config files which are located in the following places:
\~\PublicLayer\SDKs\B2CSampleSite\Configs\Mediachase.Search.config
\~\AdminLayer\ConsoleManager\Configs\Mediachase.Search.config
\~\QuartzService\Mediachase.Search.config

You will see the following lines with the placeholder (SITE ROOT FOLDER)\App_data\ when you open the files:

{code:xml}
<?xml version="1.0" encoding="utf-8"?>
<Mediachase.Search>
<Indexers>
<add name="CatalogEntryIndexer" type="Mediachase.Search.Extensions.Indexers.CatalogIndexBuilder, Mediachase.Search.Extensions" basePath="(SITE ROOT FOLDER)\App_Data\SearchIndex">
</add>
</Indexers>
</Mediachase.Search>
{code}

Replace the place holder so that the file path points to the "SearchIndex" folder created in the previous step.

*Configure Application Name*

The ecf.apps.config files that you need to edit are located in the following two places:

\~\PublicLayer\SDKs\B2CSampleSite\Configs\ecf.apps.config
\~\AdminLayer\ConsoleManager\Configs\ecf.apps.config

{code:xml}
<?xml version="1.0" encoding="utf-8"?>
<Application defaultApplicationName="APPLICATION NAME">
{code}

Replace "Application Name" with "eCommerceFramework" or the application name you decided to use for the database script and in the Web.config files above.
*Note:* The same application name you use must be used for the database script, all lines in the Web.config, and ecf.apps.config files. Otherwise you will receive an error when trying to browse the ECF web site.

*Configure Asset Storage Folders*

In this section you will configure your digital asset folder. The digital assets you upload into ECF will be stored in this configured location.
First create a BlobStorage folder on the root level of your solution package or anywhere else that is convenient for you.
Next create a Public folder in the BlobStorage folder just created.

Access the two baf.config files are located in the following places:

\~\PublicLayer\SDKs\B2CSampleSite\Configs\baf.config
\~\AdminLayer\ConsoleManager\Configs\baf.config

Do a search on *BlobStorage* and you will find the lines shown here:

{code:xml}
<blobConfiguration>
<storageProvider defaultProvider="DiskBlobStorageProvider">
<providers>
<add name="DiskBlobStorageProvider" type=" Mediachase.BusinessFoundation.Blob.DiskBlobStorageProvider, Mediachase.BusinessFoundation" allowSearch="False" basePath="(SITE ROOT FOLDER)\BlobStorage" />
<add name="SqlBlobStorageProvider" type=" Mediachase.BusinessFoundation.Blob.SqlBlobStorageProvider, Mediachase.BusinessFoundation" allowSearch="True" />
<add name="PublicDiskBlobStorageProvider" type=" Mediachase.BusinessFoundation.Blob.PublicDiskStorageProvider, Mediachase.BusinessFoundation" allowSearch="False" basePath="(SITE ROOT FOLDER)\BlobStorage\Public" />
<add name="S3StorageProvider" type="Mediachase.Library.AmazonProviders.S3StorageProvider, Mediachase.Library.AmazonProviders" allowSearch="False" accessKeyID="id" secretAccessKey="secretkey" bucketName="ecf" useSSL="false" useSubDomains="true" expirationTimeSpan="1:0:0" />
</providers>
</storageProvider>
{code}

Replace the placeholder (SITE ROOT FOLDER) with the folder paths that points to the folders created at the beginning of this section.

h3. Step 5: Compiling your Full Source solution in Visual Studio


The solution needs to be complied before you can browse the ECF Site that you have set up. At the root level of your package, you will see the eCommerceFramework5.1 SDK.sln.


!FullSourcePackageSolution.png|thumbnail,border=1!


Open this file with your Visual Studio and Rebuild the entire solution at the top level.

h3. Step 6. Accessing the Commerce Manager and Importing the Sample Site and Catalogs


Now you are ready to access the ECF using your web browser.

Browse [http://localhost/]
Because currently there are no public site set up, this url will automatically redirect you to the Commerce Manager (a.k.a. back-end site).
At the log in page, enter the default authentication (User name: admin, Password: store) and select Log in.




!ManualInstallationLogin.png|thumbnail,border=1!


The Dashboard Home page of the Commerce Manager will open. The *Alerts* section indicate that Sites, Catalogs, and Search Indexes do not exist as shown below.



!ManualInstallationBack-End.png.jpg|border=1!



Follow the instructions for each alert in the order listed from top to bottom and import the sample site, catalogs, and finally build new indexes.
For the Search Indexes alert, click on the "Rebuild" button once you enter the Search Manager page.
Go here to see the detailed steps to import B2CSampleSite definition
Go here to see the detailed steps to import sample catalog files

*Important:* Make sure to import the sample site before importing the catalogs. DO NOT import the catalogs when there is no existing sites.

h3. Step 7: Starting Quartz Service


Go to the \~\QuartzService folder located at the root level of your package.
Run the following command in the Command Prompt:

From:

{code}
install.bat (application name) (e.g., eCommerceFramework or any other application name of your choice)
{code}

Open the Local Services from Start > Administrative Tool > Services
Find "Mediachase eCommerce Framework Service (eCommerceFramework)" from the list. Right click and choose "Start". The Status column will change from blank to "Started" confirming that the service has started.




!ManualInstallationService.png|thumbnail,border=1!


Starting the Quartz will by default automatically update catalog indexing every 5 min.
You can change the frequency of the job or add new jobs such as recurring payments or rotating encryption. To read more about Quartz, go here.

h3. Step 8: Installing your License Key


When browsing to the newly installed ECF Full Source package, you will notice that the status of the License at the upper right hand corner of the Commerce Manager is displayed as "unlicensed version" in red font. The installation will fully work as long as you are using localhost. You will need to install your license key, however, in order to browse your site with with a hostheader name or to browse your site remotely or one set up on a server.

To install your license click on the "unlicensed version" and you will be redirected to the Licensing page (this can also be accessed from Administration > System Settings > License Info). Enter your license file or your license key in the appropriate field and select Install. Your license info will appear at the bottom of the screen.




!Licensing.png|thumbnail,border=1!


h3. Browse the B2C Sample Site


*Now you are ready to browse the Public B2C Sample Site.*

Sign Out from the Commerce Manager and Browse the Public B2C Sample Site
Sign out from the Commerce Manager. The Sign Out option located in the pull-down menu of the "Welcome" button at the upper left corner of the screen.

You will be taken to the public B2C sample site (a.k.a. front-end site).




!ManualInstallationB2CDigitalCameras.png|thumbnail,border=1!

If everything works and looks good, you're done\! If problems do arise, please read our Troubleshooting section.

h1. Appendix

{anchor:IIS 6 2003}

IIS 6 Configuration on a Windows Server 2003 Workstation

This will go step-by-step how to setup IIS 6 in Windows Server 2003 for ECF.
* Click on Start \-> Administrative Tools \-> Internet Information Services (IIS) Manager
* Highlight Web Sites and stop the Default Web Site. Then right-click on Web Sites and select New \--> Web Site
** Enter in a description of the Web Site (e.g. eCommerce Framework - 80)
** Assign an IP or localhost and a TCP port
** Select a physical path to the Web content location (i.e. C:\inetpub\wwwroot\B2CSampleSite or any other IIS root location you are using)
** Check the following permissions: "Read" and "Execute"
* Add 3 Virtual Directories ("_cmsbase", "_cmsctrls", "Apps") in the "eCommerceFramework - 80" web site and set their physical paths to their respective folders in the Shared folder contained in the Mediachase folder you initially moved to Program Files
* Right click on the "eCommerceFramework - 80" web site. Select the command to add a new virtual directory and enter the following information:
** Alias: \_cmsbase
** Physical path: C:\Program Files\Mediachase\eCommerceFramework\5.1\Shared_cmsbase
** Virtual Directory Access Permission: Read & Execute
** Repeat these steps to create the other two Virtual Directories (_cmsbase and Apps).
** Right-click on each virtual directory you created and go to properties. Next to the Application Name field, click on Remove and OK.
* Right-click on the Web Site name (i.e. eCommerce Framework - 80) and select properties. Go to the ASP.NET tab make sure the ASP.NET version is set to 2.0.50727.

In the end, it should look like this:

!iis6-config-ecf51.png|thumbnail,border=1!



Click on this link to continue on to [Step 3: SQL Database Setup|#Step3].

{anchor:IIS 5 XP}

h3. *IIS 5 Configuration on a Windows XP Workstation*

Open up the IIS Management Console
* Create a new virtual directory and point it to your "B2CSampleSite" folder or whatever name you used earlier for your website root folder.
** When using the Virtual Directory Creation Wizard, specify the Virtual Directory alias - we use b2csamplesite as the default but feel free to use whatever name you like.
** Point the Web Site Content Directory to the location on your machine where the B2CSampleSite contents are located (i.e. C:\Inetpub\wwwroot\b2csamplesite)
** Change the access permissions of this directory to "Read" only.
* Go to the properties of the new "b2csamplesite" virtual directory that was created and set the following:
** Go to the ASP.NET Tab and select 2.0.50727 as the ASP.NET version
** On the Home Directory tab, set permissions to "Read," "Log visits," and "Index this resource."
** In the Home Directory tab, set the Execute Permissions to "Scripts only."
** Select "Create" in the Application Settings portion in order to establish the application name.
** Set the Execution Permissions to "Scripts Only."
** In the Documents tab, make sure you add "Default.aspx" and move it to the top of the list.
** Make sure that the virtual directory that was created belongs to the same application pool as the website.
* In IIS, set the permissions for the root home directory folder of your website to the following (the permissions to your "b2csamplesite" virtual directory should be inherited):
** Allow the following privileges for the IIS_WPG user group: "Read & Execute," "List Folder Contents," and "Read"
** Add the "Network Service" account by clicking "Add," "Advanced" and then "Find Now". Scroll to NETWORK SERVICE and then click OK to exit the window. Click OK again to go back to the Security tab properties. You should see NETWORK SERVICE in the list of Group or user names
** Verify that the "Network Service" account has "Modify" privileges.

In the end, it should look like this:

!ManualInstallationIIS5.png|thumbnail,border=1!




Click on this link to continue on to [Step 3: SQL Database Setup|#Step3].


h3. *Help Tool to Update Configuration Files*

We've put together a simple help tool to recursively search through a directory to find a set of configuration files that are meant to be particular to each environment. This includes connection strings, storage path, etc.

The tool consists of 4 parts (Mediachase.ECF.SDK.5.1 package\Tools\UpdateConfigFiles):

An executable file containing the program

Copy of MSBuild Community Tasks DLL required by the executable

A batch script to pass parameters to the executable

XML file containing all fields that need to be configured for a target environment

*How to use*

Open the UserProperties.xml file using a text editing tool such as Notepad and overwrite the placeholder info (in black fonts in all uppercase letters below) with information to match your setup you used.

Here are the contents of the UserProperties.xml file you will initially see:

{code:xml}
<?xml version="1.0" encoding="utf-8"?>
<UserProperties>
<DataSource>DATABASE SERVER</DataSource>
<DBMain>DATABASE NAME</DBMain>
<SqlUserId>SQL ADMIN</SqlUserId>
<SqlUserPassword>SQL ADMIN PASSWORD</SqlUserPassword>
<\!-\- Default application name \-->
<ApplicationName>APPLICATION NAME</ApplicationName>
<StorageBasePath>{SITE ROOT FOLDER}\BlobStorage</StorageBasePath>
<\!-\- Usually the same as storage base path above \-->
<PublicStorageBasePath>{SITE ROOT FOLDER}\BlobStorage\Public</PublicStorageBasePath>
<SearchIndexPath>{SITE ROOT FOLDER}\App_Data\SearchIndex</SearchIndexPath>
<\!-\- Network share form of search index path above \-->
<SearchIndexPathUnc>{SITE ROOT FOLDER}\App_Data\SearchIndex</SearchIndexPathUnc>
<TemplatePath>{SHARED FILES FOLDER}\NotificationTemplates\{0}\{1}.xsl</TemplatePath>
<\!-\- Usually set to {Directory containing ConsoleManager}\ConsoleManager\bin \-->
<LicenseStoragePath>{SITE ROOT FOLDER}\bin</LicenseStoragePath>
</UserProperties>
{code}
Run the following command in the Command Prompt:
{code}updateConfig.bat [directory containing the config files] (e.g., "C:\Program Files\ECFG51FullSource)"{code}

*Note:* For the optional line <SearchIndexPathUnc>, which can be left blank, use the format
\\
(SERVER NAME)(SHARED FOLDER PATH).

h3. Steps to Import B2C Sample Site Definition


Click on the link "here" to import a sample site. When the Import Site page opens, you should see one xml file available for import.
Click on the SiteExport-B2C.xml file to highlight it, then select the "Start Import" button. A progress window will open and the import should be complete in a few seconds.
Once the progress bar indicates that the import has been completed, select close.

*Note:* If the SiteExport-B2C.xml files does not appear in the Import Site page, you can find the xml file in the \Mediachase.ECF.SDK.5.1\Tools\DataFiles folder. Select the *Add New File button > Browse > Upload > Save the File* to add it to the Available for Import list.




!ManualInstallationSiteImport1.png|thumbnail,border=1!


h3. Steps to Import B2C Sample Catalog Files


IMPORTANT NOTE - PLEASE READ\! - We package the sample catalog data to use the native import functionality in ECF G5. The Brands Catalog and the Everything Store Catalog files will take a few Minutes to import so please leave the process running until it is complete and use this special time to grab a cup of coffee or a drink.

SECOND IMPORTANT NOTICE - PLEASE READ\! - Do not import the sample catalogs if you have not imported the B2C site definition in the previous step above. It is important that the Site definition is performed before the catalog data imports.

At the Dashboard home page (as shown two images above), click on the link "here" to import sample catalogs. When the Import Catalog page opens, you should see two xml files (CatalogExport-B2C-Brands.zip & CatalogExport-B2C-Everything.zip) available for import.

Click on one of the two zip files to highlight it, then select the "Start Import" button. A progress window will open and the import should be complete after a few seconds.

Once the progress bar indicates that the import has been completed, select close.

Highlight the other zip file, and repeat the import process.

Note: If the CatalogExport-B2C-Brands.zip & CatalogExport-B2C-Everything.zip files do not appear in the Import Site page, you can find the xml file in the \Mediachase.ECF.SDK.5.1\Tools\DataFiles folder. Select the *Add New File button > Browse > Upload > Save the File* to add it to the Available for Import list.

*Note:* Please make sure you import *both* files.


!ManualInstallationCatalogImport.png|thumbnail,border=1!




{anchor:End ScreenSteps Content}