Configuring deployment modes

The deployment mode that WFM operates in is controlled using JVM parameters. These JVM parameters must be configured in the application server and job scheduler so that the application can start up in the appropriate mode:

Parameter Description Allowed values Default value
wb.running.inside.container Specifies if WFM is running in a container-based deployment. true, false false
wb.cloud.provider Specifies the cloud environment where WFM is deployed. aws, gov-cloud, or empty empty

This table describes the various modes that the application starts up when these parameters are configured in different combinations:

wb.cloud.provider="aws" wb.cloud.provider="gov-cloud" wb.cloud.provider=""
wb.running.inside.container="true" Application is running in Commercial Cloud mode. Application is running in GovCloud mode. Application is running in a container-based deployment, outside of any supported cloud environment.
wb.running.inside.container="false" Not supported Not supported Application is running in Legacy mode.

As of release 6.4.0, both these parameters must be set, unless you are running WFM in Legacy mode. When these parameters are not provided, the application starts up using the default values.

When running in Commercial Cloud or GovCloud mode, these additional parameters must be set:

Parameter Description Allowed values Default value
wb.tenant.id Specifies the tenant ID. The tenant ID is a unique identifier that represents the customer and customer environment. A valid tenant ID default
wb.storage.s3.dataBucket Specifies the name of the Amazon S3 data bucket to be used with WFM. An S3 data bucket must be specified when operating WFM in either Commercial Cloud or GovCloud mode. The name of an S3 data bucket empty
wb.tenant.aws.kms.alias Specifies the AWS KMS alias. In AWS KMS, an alias is a display name for a customer master key. The name of the alias created as part of tenant creation empty

See the Infor Workforce Management Installation and Configuration Guide for details on setting JVM parameters on the job scheduler. For details on setting the JVM parameters on the application server, see the documentation for your application server software.