loading table of contents...

6.1.2. Configuration in workflowserver.properties

The file workflowserver.properties contains general configuration properties of the Workflow Server such as the mapping of LDAP groups to the workflow groups.

Property Value Default Description
workflow.server.ORBServerHost String   The host of the ORB which the Workflow Server instantiates. This property is deprecated and is ignored when using the application server's ORB.
workflow.server.ORBServerPort Int   The port of the ORB which the Workflow Server instantiates. This property is deprecated and is ignored when using the application server's ORB.
workflow.server.uapi.connectRetryDelaySeconds seconds 10 The delay in seconds the Workflow Server waits between retries to connect to the Content Server when starting.
workflow.user String workflow Define a user for the connection with the Content Management Server.
workflow.password String workflow Define a password for the connection with the Content Management Server.
mongoDb.clientURI String   The client URI to connect to MongoDB. Must be set to use the ArchiveProcess or RegisterPendingProcess actions. This is required for using workflows such as studio-simple-publication.xml and studio-two-step-publication.xml in Studio.
mongoDb.prefix String   The prefix for the MongoDB database name. Must be set to use the ArchiveProcess or RegisterPendingProcess actions. This is required for using workflows such as studio-simple-publication.xml and studio-two-step-publication.xml in Studio.
workflow.usecaplist String false Must be set to use the ArchiveProcess or RegisterPendingProcess actions. This is required for using workflows such as studio-simple-publication.xml and studio-two-step-publication.xml in Studio.
workflow.server.tx.max Int 20 Limits the maximum number of database connections.
roles.map.approver-role, roles.map.composer-role, roles.map.publisher-role String  

The predefined workflows require the groups approver-role, composer-role and publisher-role. These groups are automatically created. If you use an LDAP server for user management, you might not want to use the predefined groups. In this case, you can map an LDAP group to the appropriate workflow group, such as approver@example.org. The members of the LDAP group approver@example.org will be treated as members of the approver-role group etc. Note, that you can only map one LDAP group to one workflow group.

If you change this mapping after you have already uploaded workflow definitions, you have to reload the workflow definitions.

workflow.server.managers.<managerName>.class String   Register a custom manager for use in the Workflow Server. The manager is created when the server starts.
workflow.server.managers.<managerName>.order Int 0 The startup order for a custom manager. Managers are started in the given order. If the order is not specified, 0 is assumed. Managers with the same order are started alphabetically according to their name.

Table 6.1. workflowserver.properties


Prev Up Next
 Home