Migrating application content to Workbench

Running the importApplication script uploads your migrated application content to Workbench.

Important

To guarantee consistent data, ensure that no baseline or partial updates are running during this process.

To upload migrated application content in Workbench:

  1. During the application deployment in the 11.3.1.5.0 release, you are no longer prompted for authoringApplicationExportDirectory. The deployment uses a default path. You must update repository.configuration.path in the assembler.properties file for the authoring application server and all live application servers to use the default directory paths. You must also remove authoringApplicationExportDirectory from $BASE_APP_FOLDER/config/migrate_config/configuration/tools/deploymentSettings/_.json, and applicationExportDirectory from $BASE_APP_FOLDER/config/script/WorkbenchConfig.xml.

    For the Discover application, the assembler.properties file is in these locations: 

    <ENDECA_TOOLS_ROOT>/reference/discover-electronics-authoring/WEB-INF/assembler.properties
<ENDECA_TOOLS_ROOT>/reference/discover-electronics/WEB-INF/assembler.properties

    The authoringApplicationExportDirectory and applicationExportDirectory properties are supported in 11.3.1.5.0. However, Oracle does not recommend their use. If you use these properties (which is not recommended), make sure that authoringApplicationExportDirectory is pointing to the correct location under $BASE_APP_FOLDER/config/migrate_config/configuration/tools/deploymentSettings/_.json, and applicationExportDirectory is added to $BASE_APP_FOLDER/config/script/WorkbenchConfig.xml.

  2. Navigate to $BASE_APP_FOLDER/Discover/control directory, and run the importApplication script, passing in the name of the directory into which the application configuration was backed up.

    For example: 

    C:\Endeca\apps\Discover\control>runCommand.sh IFCR importApplication 
$BASE_APP_FOLDER\config\migrate_config

    The entire application configuration is imported to Workbench, along with content privileges.

Repeat this procedure for every application that you are migrating.

Copyright © Legal Notices