Skip to main content

eWam Service Configuration

Both eWamService.exe and Node-Hosting use a configuration file following the Description type below:

NameTypeDescription
administratorAdministratorApplicationDescAdministrator session configuration Do not mount in production or expose it on a protected port
applicationsObjectExposed applications
arguments?string[]CLI ewam arguments example: /DEBUG, /CONTINUEONTRAP...
maxThreadsCount?numberMax. concurrent work/request
minThreadsCount?numberMin. concurrent work/request, should be twice the nb of cpus
options?Object-
options.dontCatchException?booleanKeep it to false unless you are debugging eWam
options.enableInteract?boolean-
options.minimize-model-annotation?boolean-
options.show-model-annotation?boolean-
runtimeMode"Application" | "IDE"Runtime mode, using 'Application' will keep your TGV in readOnly mode

This Configuration can be used from a json file or via the API ewam.connect in node-hosting.

example: ./Admin/config-runtime.json
{
"runtimeMode": "Application", // IDE is also accepted
"minThreadsCount": 1,
"maxThreadsCount": 1, // should be twice the nb of cpus
"options": {
"show-model-annotation": true,
"minimize-model-annotation": true,
"use-X-Wyde-Profiling": false,
"enableInteract": false, //It is recommended to leave to false
"useNoCORS": true,
"dontCatchException": false, //leave it to false unless you are debugging ewam-kernel
},
"applications": {
"stateless": {
"type": "stateless",
"services": [
{
"className": "aInsuranceWebService"
},
{
//Swagger 3.0 documentation
"className": "aDocumentationService"
}
]
}
}
}
note

eWamService.exe shall not be used in production. It is mainly designed for development/unit test purpose.