Performing an initial load of localized data

WFM uses Flyway, a database migration utility, to apply localization data to your database.

  1. You must ensure that the WFM_PRE_CLASSPATH environment variable exists and is pointing to the JDBC jar files you are using for your WFM deployment. This variable is normally already set during an installation of WFM. For example, in a Windows environment it may be set like this:
    WFM_PRE_CLASSPATH=C:\<Path_to_JDBC_Driver>\mssql-jdbc-7.2.2.jre8.jar
  2. Flyway files are located in the WBDatabase-<version>-Fixpack-<date>.zip file which is part of your WFM artifacts. Once you extract this file using your preferred utility, you will see a flyway directory.
  3. In the flyway\config directory of the extracted files, you must update the flyway.properties file with specific values for your database and other values recommended by Infor. Use your preferred text editor on your operating system to make these changes.
  4. Update all of the placeholder values in the flyway.properties file denoted by square brackets [placeholder value] which will permit a connection to the WFM database:
    • migration.dbtype=[flyway_db_type] - Specify one of SQLSERVER or ORACLE. For example:

      migration.dbtype=SQLSERVER

    • workbrain.db.driver=[flyway_driver] - Specify your database driver. For example:

      workbrain.db.driver=com.microsoft.sqlserver.jdbc.SQLServerDriver

    • workbrain.db.name=[flyway_dbname] - Your WFM database name. For example:

      workbrain.db.name=DBNAME

    • workbrain.db.instance=[flyway_url] - Your database instance name. For example:

      workbrain.db.instance=jdbc:sqlserver://SQLSERVERINST:1433;databaseName=DBNAME

    • workbrain.db.username=[flyway_username] - Your database user name. For example:

      workbrain.db.username=workbrain

    • workbrain.db.password=[flyway_password] - Your database password. For example:

      workbrain.db.password=workbrain

    • workbrain.db.schema=[flyway_schema] - Your database schema. For example:

      workbrain.db.schema=dbo

      Note: For some databases such as Oracle, this value can be case-sensitive.
    • workbrain.db.server=[flyway_server] - Your database server name. For example:

      workbrain.db.server=localhost

    • workbrain.db.port=[flyway_dbport] - Your database port. For example:

      workbrain.db.port=1433

    • Using the same technique, you must now also specify values for these properties of the WFM archive database:

      • workbrain.archive.db.name=[flyway_archive_dbname]
      • workbrain.archive.db.instance=[flyway_archive_url]
      • workbrain.archive.db.username=[flyway_archive_username]
      • workbrain.archive.db.password=[flyway_archive_password]
      • workbrain.archive.db.schema=[flyway_archive_schema]
      • workbrain.archive.db.server=[flyway_archive_server]
      • workbrain.archive.db.port=[flyway_archive_dbport]
  5. Uncomment the migration.languagePacksLocations=classpath:db.localization value in the flyway.properties file. This value tells Flyway to look for localization data.
  6. If you are loading multiple language packs, change the migration.outOfOrder value to true in the flyway.properties file.
  7. Download the appropriate language pack(s) from Infor and extract into the flyway\db\localization directory. Be careful to maintain the core and translations directories within the flyway\db\localization directory.
  8. In a command window, navigate back to the root flyway directory and execute Flyway with the localization flag. For example:

    run_flyway localization

    There is a log folder in the root Flyway directory along with all Flyway artifacts. The wbflyway.log file in this directory contains all logging information during Flyway execution. It can be modified by changing the appropriate line in the logback.xml file.

  9. After executing the Flyway script, you will now see a series of messages in the command window. If there are no errors in the command window, you can check if there is a SCHEMA_VERSION_LOC table created and populated in your WFM database. This table contains an audit log of all the changes that have been applied to your database and if this table is created and populated, then the Flyway localization script has been successful.