Problem Statement:
Endeca Workbench user finds stale dimension values in the Editor and gets confused on which Dimension values to be selected.
Solution:
To manually clear the legacy Workbench state files:
1. Stop the Endeca Tools Service.
2. Take a back up of /opt/app/endeca/ToolsAndFrameworks/11.1.x/server/workspace/state/emanager/instances/app_name/resources
3. Remove the full contents of the/opt/app/endeca/ToolsAndFrameworks/11.1.x/server/workspace/state/emanager/instances/app_name/resources directory.
4. Start the Endeca Tools Service.
5. Run the following two commands to push your current (good) config back to Workbench:
- /control/update_web_studio_config.sh
(this pushes the XML files from /opt/app/endeca/app_name/data/cas_output up to Workbench. Workbench may still use some of the dimension settings from here.)
- the post-CAS dimension file, which pushes the dimension values generated by CAS to Workbench (here is working example from Discover, where you can switch out the app name references for your own):
/opt/app/endeca/PlatformServices/11.x/bin
emgr_update --host localhost:8006 --action set_post_forge_dims --post_forge_file C:\apps\Discover\data\workbench\temp\Discover.dimensions.xml --prefix Discover --app_name Discover
If you clear the browser cache, the next time you go back to the location dialogue, the stale dimension values should be gone and it should be functioning with current data.
Endeca Workbench user finds stale dimension values in the Editor and gets confused on which Dimension values to be selected.
Solution:
To manually clear the legacy Workbench state files:
1. Stop the Endeca Tools Service.
2. Take a back up of /opt/app/endeca/ToolsAndFrameworks/11.1.x/server/workspace/state/emanager/instances/app_name/resources
3. Remove the full contents of the/opt/app/endeca/ToolsAndFrameworks/11.1.x/server/workspace/state/emanager/instances/app_name/resources directory.
4. Start the Endeca Tools Service.
5. Run the following two commands to push your current (good) config back to Workbench:
- /control/update_web_studio_config.sh
(this pushes the XML files from /opt/app/endeca/app_name/data/cas_output up to Workbench. Workbench may still use some of the dimension settings from here.)
- the post-CAS dimension file, which pushes the dimension values generated by CAS to Workbench (here is working example from Discover, where you can switch out the app name references for your own):
/opt/app/endeca/PlatformServices/11.x/bin
emgr_update --host localhost:8006 --action set_post_forge_dims --post_forge_file C:\apps\Discover\data\workbench\temp\Discover.dimensions.xml --prefix Discover --app_name Discover
If you clear the browser cache, the next time you go back to the location dialogue, the stale dimension values should be gone and it should be functioning with current data.