Automating the collection of files

After you modify an application configuration, you must collect all of the files and artifacts for the application definition and store them in the Deployment Template's[appdir] directory, so they can be replicated to the other environments. This requires collecting files from various locations, including the Deployment Template's[appdir] directory, the Workbench, and arbitrary locations used by the application's scripts.

To create a script that collects these files:

  1. Use your editor of choice and specify all the Workbench parts of the application definition.
  2. In the same file, combine the Workbench parts with the remaining application definition stored in the Deployment Template's[appdir]directory.

Running the script results in collecting and storing all of the artifacts in subdirectories under [appdir], such as /config, /control, /test-data, data/state, and data/incoming.

A sample collection script, collect-app.bat, is shown below. You can write a similar script to fit your Endeca environment. This particular sample is provided as reference only. 

set app=wine
set wbench=localhost:8006
call %~dp0..\config\script\set_environment.bat
call %~dp0runcommand.bat ConfigManager updateWsConfig
xcopy /y %~dp0\..\data\complete_index_config %~dp0\..\config\pipeline
set templ=%~dp0\..\config\templates
mkdir %templ%
emgr_update --app_name %app% --host %wbench% --action get_templates --dir %~dp0\..\config\templates

You can also create a script to upload relevant parts of the updated application definition to the Workbench from the[appdir]directory. A sample script for upload.bat is shown as follows: 

set app=new-wine
set wbench=localhost:8006
call %~dp0..\config\script\set_environment.bat
emgr_update --app_name %app% --host %wbench% --action update_mgr_settings --dir %~dp0\..\config\pipeline --prefix %ENDECA_PROJECT_NAME%
emgr_update --app_name %app% --host %wbench% --action set_templates --dir %~dp0\..\config\templates
Note: Be careful when running the collect_app.bat and upload.bat scripts. These scripts can overwrite settings in the Developer Studio and the Workbench.