Building module (advanced)
  • Updated on 11 Dec 2013
  • 1 minute to read
  • Print
  • Dark

Building module (advanced)

  • Print
  • Dark


A module is a zip file that contains files and folders that Service Host Manager interprets and places in the correct locations. This zip file can either be created manually or using the CreateModule.exe tool found in the Decisions SDK at C:\Program Files\Decisions\SDK\Tools\CreateModule.exe .

Building Using CreateModule.exe

To build a module using CreateModule.exe , call this exe with the following syntax: CreateModule.exe -buildmodule SampleModuleName -sdk "C:\Program Files\Decisions\SDK" -output ".\output\modules" -buildfile Module.Build.xml
The build file (named Module.Build.xml in the example syntax above) format looks like the following. In the example below the module will include a service dll and a number of Decisions objects, like flows and forms, that the module will import when it is deployed.


Below is an explanation of what each of these build file items is:
AgentDlls - Dlls for the Agents to extend Decisions agents.

CLIDlls - Dlls for Command Line.

ObjectToImport - Objects that need to be imported. e.g. Exported Decisions objects like flows and forms. These items will be imported when the module is deployed.

InstallScripts - CLI Scripts for Install

MvcViews - MVC Views that need to be deployed.

ServicesDlls - Silverlight dll's specified for the module and deployed with it

SilverlightDlls - NET dll's that should be provided with the module.

SQL - This has different sections for SQLScript / MySQLScript / OracleScript / AzureScript. These are database scripts that will run when the module is deployed. These are often used to add tables or stored procedures that this module relies on.

WebHostFiles - Dll files that need to be pushed to Decisions.Web.Host

WebPages - Pages that need to be deployed to Decisions.Web.Host

Building using zip

You can also manually build a module by creating a zip file with the proper folder structure. The folder structure corresponds to the XML tags described above. Use this list above to determine which folder to place your complied dll in. The most likely folder you will place compiled dlls in is the ServicesDlls folder.

Was this article helpful?