Configuring Workflow
Documentation home
See also: Workflow Index
Introduction
This section of the documentation describes the way in which
the workflow system is configured for a particular installation. Properties can
be configured on both the server and the designer:
Server Properties
These are defined using server workflow properties
within the Server Administration Application.
·
Security Handler:
provides the class name for the implementation of the SecurityHandler interface. Two workflow security handlers are shipped with
the distributed Ebase Xi system:
- com.ebasetech.ufs.workflow.security.example EbaseSecurityHandler: provides minimal security
checking– all users are allowed to create new workflow jobs and display a
task list without any security check. In addition, if a workflow process
or node does not have a security expression configured, all other actions
are also allowed; when a security expression is configured, the accessing
user is checked for permission to access the workflow process or node.
- com.ebasetech.ufs.workflow.security.example EbaseStrictSecurityHandler: provides a higher level of
security checking - all users are allowed to create new workflow jobs
without any security check, but all other actions require security
authorization.
- Remote
Workflow Server URL: this property allows requests for new workflow
jobs to be passed to a workflow engine running on a remote server. When
not specified, all requests for new workflow jobs are passed to the
workflow engine on the same server. This parameter can be useful in the
scenario where a server system handling user requests exists in a DMZ and
a workflow server is running inside an inner firewall.
Designer Properties
These are configured using the workflow tab of designer preferences.
- Assignment Handler: this must
contain the same class name as configured on the server (see above)
- Security Handler: this must
contain the same class name as configured on the server (see above)
- Workflow Activity Types: provides
a comma delimited list of class names of supported activities. The system
includes three activity types as default, see Activity Types for more
details.