WorkflowService
The WorkflowService is used to provide the runtime environment for PNML defined workflows.
Important note: This service has nothing to do with the add-on module Workflow and is not necessary for its operation!
XML configuration
Important note: The availability of a service depends on the license purchased and whether the service has been registered in the configuration file ./etc/factory.xml of the Service Factory (changes require server restart!). There you will also find the responsible configuration file for a service, otherwise you can also edit the configuration file of the service directly in the GUI of the service (changes require a service restart!).
The following XML fragment with all possible basic settings can be used to configure the workflow service.
<
Set
name
=
"databaseAlias"
>hub</
Set
>
<
Set
name
=
"dataService"
>JDOService</
Set
>
<
Set
name
=
"idleTime"
>2000</
Set
>
<
Set
name
=
"login"
>admin</
Set
>
<
Set
name
=
"logManager"
>LogService</
Set
>
<
Set
name
=
"password"
>admin</
Set
>
<
Set
name
=
"saveInterval"
>60000</
Set
>
<
Set
name
=
"storageService"
>StorageService</
Set
>
The parameters have the following meaning.
Parameter |
Description |
databaseAlias |
The database alias to be used with the JDOService. |
dataService |
The name of the JDOService to be used. |
idleTime |
The time, in milliseconds, to wait between two checks for new workflow steps. |
login |
The user name for the administrator of the workflow system. |
logManager |
The name of the LogManager to be used. |
password |
The password for the administrator of the workflow system. |
saveInterval |
The interval, in milliseconds, to wait between two saves of workflow steps. |
storageService |
The name of the StorageService to be used. |
Apart from the user settings for the administrator, the configuration of the WorkflowService generally does not require any changes to the default settings.
Log level dependencies
Changes to the log level of the LogService have no influence on the logging behaviour of the WorkflowService. Similarly, setting the mode has no effect.
If the service is set into verbose mode, added resources and the result of executed workflows are noted into the log.