On-Premise Installation - Overview

ConceptShare provides an installer application which helps facilitate the installation of a ConceptShare instance. When you are given a link to download the installer application you will also receive a license file containing your installation (instance) information that the installer will require. If you do not have this particular file please contact our Sales Engineering team via

The installer facilitates the following functionality:

  • Manage multiple instances (if applicable).
  • Managing the ConceptShare Database
    • Downloading of the template (boiler plate) database for initial installation.
    • Initialization of the database (setting license/contractual settings, and configuration of database specific features).
  • Management of the ConceptShare Queue Server
    • Installation / Updating of the Windows Service
    • Uninstallation of the Windows Service
  • Management of the ConceptShare website
    • Installation / Updating of the website files
  • Management of ConceptShare Updates
    • Installation of ConceptShare updates (as released for your particular instance).
  • Ability to update various installation settings and client licenses.

There are several deployment scenarios where various components can be broken out into individual servers or additional servers. The installer application is optimized for a single server deployment and can facilitate a dual server deployment where the database (SQL) resides on a separate server. All other deployment configurations (multiple web-servers, queue services, DB clustering, etc.) is beyond the scope of the ConceptShare installer and will require application of manual updates to individual pieces.


In this scenario, all ConceptShare services (web, queue, and database) reside on the same server. This is common deployment scenario for a development, QA, or small on premise installation.

In this scenario, all ConceptShare services with the exception of the database reside on the same server. This is where a centralized SQL instance is available instead of a dedicated instance directly on the server. Installation is generally the same as the single server deployment with the exception of some pre-flight steps which must be performed manually (highlighted/noted in the Installation Instructions).

In this scenario, each ConceptShare service is carved off into its own dedicated server. This is common when the Queue service (the main processor) is doing a fair amount of asset, event, and email processing to warrant segregating it on dedicated (and potentially more powerful) hardware.

To utilize the installer in this scenario, updates to the Queue must be copied over and applied manually as highlighted/noted in the Installation Instructions.

There are many configuration options here where you can create a high-availability (HA) environment. For example, you can add a load-balancer in front of a couple of web-servers and load-balance that portion of the application if the load requires.

Furthermore, you can similarly create multiple queue servers and even change the configuration of each queue server to handle different asset types and to process different queue items. A queue service handles assets, as well as all the operational functionality within ConceptShare such events, callbacks, workflows, reminders, and other core services.

In order to make the database server high-availability you can utilize all the Microsoft technologies available for clustering and fail-overs.

You can also make use of the following high-availability scenarios:

  • Hot/Hot - All services are active and balancing the various loads.
  • Hot/Warm - A primary set of services are active and a secondary set are online and ready to go in the event of a failure.
  • Hot/Cold – A primary set of services are active and secondary set is available offline but can be turned on and configured if the primaries are unavailable.

 Load Balancing has been subdivided into the following categories:

ConceptShare can be placed behind a load-balancer to improve responsiveness and availability. You can choose whichever load balancing scheduling algorithms you prefer such as: fault-tolerant, load-balanced by number of connections, round-robin or by others. When load balancing we recommend you use session persistence or stickiness.

ConceptShare also provides a heart-beat functionality which will ensure that IIS can properly serve a request and that the underlying database is acceptable. You can configure your load-balancers to test this URL and upon failure can take that system out of the rotation. The heart URL will return “OK” in the content body of the response if all the checks are fine. The URL to use is: "http://your.cs.server.domain/system.ashx?f=hb"

NOTE: ConceptShare does not provide direct support or assistance with configuring or managing load-balancer hardware or systems, as that is the responsibly of the infrastructure team.

All database clustering is performed at the SQL instance level or lower (Windows Clustering / SQL Clustering). ConceptShare can run within a cluster but ConceptShare cannot provide support on creating, configuring or maintaining such clustered environments. Please contact your infrastructure team for assistance.

The ConceptShare queue service can be load-balanced across multiple machines to provide high-availability. Each queue service can run the same configuration to provide an even balance across the cluster. Alternatively, the individual queues can be configured so that certain types can be processed by one queue service and not others. For example, in some high video transcoding environments you might have a server with more processing power than the others. You can configure that queue to process only video, and configure the remaining servers to handle the rest of the queue traffic. Each queue can be independently configured (on/off, maximum number of threads). The service has several ‘queues’ which are processed as noted below (along with their default maximum number of threads):



You have captured an understanding of the high level setup for establishing your On Premise deployment.


Further Reading:

Was this article helpful?
0 out of 0 found this helpful