WFM does not use them, but you cannot save the DAP Application object unless these fields are filled in.
Prerequisites: You know the name of your new WFM Database, its location, its type, and the login name and password for a user with DBO privileges. Purpose: To enable WFM Server to specify the DAP on their Application object Connections tab. For WFM Daemon, no configuration is required.(These options are not set automatically during installation for these components.) In the WFM Server Application, WFM Builder Application, and Data Aggregator Application objects, set the backuphost and backupport options to take effect during startup.After you have made the changes, save the file and restart the host. For WFM Web, manually configure two optional keys backuphost and backupport in the ConfigServer.properties file located in the Tomcat directory webapps\wfm\WEB-INF (assuming WFM Web was deployed as wfm.war, otherwise replace wfm with the specified name).For WFM Server, Builder, and Data Aggregator this feature is implemented by setting the backuphost and backupport options in the Start command line or in the NT Service command line.For WFM Web and Daemon, this feature is implemented automatically during installation.To implement this feature in 8.1.3 and later releases If the primary Configuration Server is not available during startup, WFM Web, Server, Builder, Daemon, and Data Aggregator can connect to the backup Configuration Server.
If you have only one of the required components in the latest version, the software will not malfunction, but the new feature will not be available.īe sure to check the release number carefully when deploying or updating WFM software.Īfter installation, WFM components connect to Configuration Server to obtain information about the environment. 201.00), they might not appear in iteration 1 Or a new feature might require the latest version of multiple WFM components. For example, enhancements added to a feature in iteration 2 (perhaps 8.5. You can mix and match 8.5.2 components of different iterations-for example, you can run WFM Server 8.5.203.xx with WFM Web 8.5.202.xx-but if you do, you might notice that there are rules or exceptions about how new features appear, or if they appear at all. Note that the first iteration is 200 and not 201.Ĭurrently, this is applicable to 8.5.2 release only. For example, iterations for major release 8.5.2 might look like this: 8.5. You can determine the iteration number by checking the middle three digits.
Starting in 8.5.2, WFM is released in multiple iterations.
The major release stream is determined by the first three digits in the release number. Mixing components from different major release streams is untested and therefore, not supported in production environments. When installing WFM components, ensure they are all within the same major release stream.