Runtime Engine Version > Runtime Engine

The Runtime Engine is an optional add-on to the Enterprise version of DMC only. If you don't have the Enterprise version of DMC you will need to upgrade your license to the Enterprise version to use this feature.

The Runtime Engine allows you to distribute to YOUR end-users a small footprint (5 MB) engine of DMC. You can then Run on their machines ANY project that you pre-define on YOUR machine. The Runtime Engine does not have a user interface - you control it using Your application and Profiles You create on your computer.

For example, after you use DMC to Port your Application to SQL you still need to transfer the data on your client's computer to SQL. After testing your data transfer Project on your system you'll need to run that Project on each of your users computers. There's no need to buy and install DMC at each location. You simply use the Runtime Engine and the Project you created to make those changes through your application.

The Runtime Engine works for other DMC functions as well. You can create Cloning, Transfer and Backup Projects as well.

How it works :

The way your application communicates with the Runtime Engine (called RT) is simple.

1.	Create a Project using DMC (on your machine)

2.	Export a Project generates a special "LINK" table (TPS encrypted)

3.	The Demo App contains the necessary TXA, TXD & templates to control the project in your application

4.	Import those TXA, TXD & templates into your Clarion Appplication (or use the Demo app as a standalone executable)

5.	Install the Runtime Engine. This installer is silent and will remove itself when the Runtime Engine is installed.

6.	Include your DMC License File. The license file is located in your %datadir%_cgf_import and named dmcrt.lic. To determine where to place your license on their computer, read the location from the registry (see below).

7.	Deploy the TPS encrypted Project files to your user's computer (you control where these folders are located)

8.	From your Application (or the Demo app) you can customize Source/Destination and Owner attributes to match each user's configuration

9.	Execute the Project through your application (or Demo app)

How to set it up :

1.	From your machine's DMC Enterprise version create for example an SQL Backup Task and save it to a Project

2.	From your machine's DMC Enterprise version Export this Project

3.	In your application add the DMC RT template and import the TXD and TXA supplied (in application you need to use it in for MultiDll systems)

4.	Define all specifications in your application as explained in the RT Help so as to dynamically change some settings to match your end-users machine on path location or ODBC connections (see step 7. hereunder) and to call the RT engine.

5.	In your application Installer ADD the SB silent self deleting DMC RT installer and run it at end of install

6.	ADD in YOUR Installer YOUR DMC License File (see RT documentation for precise location of this file)

7.	ADD in YOUR Installer the FOLDER containing the Exported Project and install anywhere you want on your client's machine (you must "know" where this folder is to call it from your application)

General Rules :

You can distribute the RT engine up to 2 500 end users royalty free with the special Runtime Engine License (above 2 500 end users please contact us).

You can distribute as many Projects as you wish (older ones will be always structure wise updated by the RT itself when you start it)

You can place the Project folders anywhere you wish on your client's machine - simply you have to "tell" the RT engine where to look for them in YOUR application

You can use ANY type of Saved Projects generated from YOUR machine's DMC Enterprise version to be shipped to your end-users

You can also use the RT to simply open and Visualize ANY File - Table from your end-user's machine (careful to what you allow them to do here)

You can define if the RT will run Silently or not

You can define if you "pass" onto the RT the Path to look for your project from a Registry entry OR from an INI file (those two being always the same)

You can dynamically define from YOUR application for example the Charset to use in a Viewer List Box when displaying foreign language Tables.

You can add a "call" (or several) to the RT in your application in any Button or embed point code or even Timer event - you have a TXA to import in your application which is a centralized procedure to use (adding all code there to cope with the different projects you want to use)

The RT Installer is an auto delete typed one (Setup Builder) so as not to leave anything not needed on your end-users machines

The RT engine cannot be started by double-clicking on the executable in Windows Explorer - this is what you would see onscreen :

When NEW Features are added in DMC they are automatically added to the RT engine - in this case you will be informed of this and simply have to update the executable on your client's machine during your next application update

(if a full reinstall is required we will inform you of this case and then you will only need to add the RT installer to your updater)