Installing Rapido

Dynamicweb Rapido is a highly configurable implementation of a frontend, and functions as a starting point for developing and implementing solutions on Dynamicweb.

In practical terms, Dynamicweb Rapido consists of:

  • Files folder containing templates and other static ressources
  • database with demo data - pages, products, paragraphs, etc.

To install Dynamicweb Rapido on top of an empty solution, you must then do the following:

  • Download the latest Rapido release
  • Extract the files folder and use that in place of the default application files folder
  • Restore the database
  • Edit the globalsettings.aspx file and point it to the restored database

Simply follow the steps below!

This install guide presupposes that you have access to the server where your dynamicweb solution is installed. You can also install a solution locally, of course.

The first step is downloading and using a files folder containing the Rapido design, item types, and other static content. You must use this files folder instead of the one provided by the install wizard.

First download and extract the files folder:

  • Download the latest Rapido Files zip here
  • Create a subfolder in the Solutions folder you created earlier – name it after this solution
  • Extract the Files folder to the subfolder

Next, you must create a virtual directory on your website and point it to the Rapido files folders using the Internet Information Services (IIS) Manager. Use the procedure described here.

In theory, you can stop here and use the various Rapido resources to create a custom implementation from scratch, but in most cases you want access to the demo data as well – pages, paragraphs, products, etc.

And to access the demo data you must use the Rapido database.

The second part of installing Dynamicweb Rapido is restoring a Rapido database containing demo data such as pages, paragraphs, item types, products, etc.

The Rapido database is packaged as a .bacpac file which requires the following to be unpacked: 

  • Microsoft SQL Server Management Studio 2014 version 12.0.4237 or newer 
  • Microsoft SQL Server 2012 with 2014 Client Tools

If you've followed the Installing Dynamicweb guide, you should already have Microsoft SQL Server 2014 and only need to update Management Studio 2014 to a newer version.

Once you're running the right versions:

  • Download the latest Rapido database zip here
  • Extract it to an easily accessible location
  • Open SQL Management Studio and connect to your server
  • Right-click the server and open Properties Security
  • Verify that Server authentication is set to “SQL Server and Windows authentication mode” (Figure 3.2)
Figure 3.2 Check the Security settings

Right-click the Databases node and click Import Data-tier Application. This opens the Import Data-tier Application window (Figure 3.3). Click Next.

Figure 3.3 Importing a Data-tier Application (.bacpac-file)

If not already selected, select Import from local disk and click Browse and locate your .bacpac-file (Figure 4.1). Then, click Next.

Figure 4.1 Import settings

Name your new database (Figure 4.2). You can also change the Data file path and Log file path for the SQL Sever (optional).

Click Next to proceed to the Summary step and verify that the settings are correct, and then click Finish.

Figure 4.2 Name your new database

When the operation is done, the Rapido database should now be accessible from the Databases node (Figure 4.3).

Figure 4.3 The Rapido database is now accesible from SQL Management Studio

Since this is a restored database you must manually map your SQL user to the database.

  • Go to Security > Logins  and open your SQL user (double-click)
  • Open the User Mapping node
  • Click the Map checkbox for the restored database (Figure 5.1)
  • Check the db_datareaderdb_datawriter and db_ddladmin roles for the user
  • Click OK
Figure 5.1 Mapping your SQL user to the extraxted database

To make your solution run on the extracted database you must edit the GlobalSettings.aspx file of the Rapido installation:

  • Go to the Files folder and open Globalsettings.aspx in e.g. notepad or notepad++
  • Locate and edit the Database-section to match your user and database details (Figure 6.1)
  • Save
Figure 6.1 Pointing your solution to the extracted database

You should now recycle the application pool for the site in your IIS Manager (Figure 6.2) – occasionally the SQL user credentials are cached and will prevent you from connecting properly to the database.

Figure 6.2 Open the IIS Manager and locate the application pool for your site to recycle it

The final step before your Rapido installation is ready to use and show off is building the various indexes needed to e.g. render products in frontend.

To build your indexes:

  • Go to and log in using the administrator credentials you created earlier
  • Go to Settings > Repositories
  • Open the Files repository and click on the Files index
  • Under Builds click on the yellow Files button to build the files index
  • Repeat these steps for the remaining indexes – PIM, Products & Secondary users

You have now built the indexes – open the frontend and verify that products are now being rendered.

And that’s all :) You now have a local installation of Dynamicweb Rapido to play around with.

After playing around with Rapido for a while, you should read through the Rapido documentation.

With Dynamicweb Rapido, you can easily configure and deploy most projects with a minimum of hassle – and custom projects are also guaranteed to be off to a good start, as we provide the foundation with a clean, maintainable and highly customizable code base.

In the documentation you will be introduced to the following:

  • The item types, which are used to both configure a solution and to create content
  • The templates, some of which are ViewModel-based and all of which easy to work with
  • The CSS projects – BaseRapido & Ignite – which are at the core of the Rapido philosophy of making everything maintainable, configurable, and extendable
  • The dos and don’ts of JavaScript and Ajax on Rapido – especially the don’ts
  • And much, much more…

We will also discuss some general principles for working with frontend development in teams, which will help you make your projects maintainable – and will save you lots of time in the long run.