Dimension not showing in Endeca Workbench

  1. Home
  2. Blog
  3. Dimension not showing in Endeca Workbench

Dimension not showing in Endeca Workbench

Endeca Workbench doesn’t query MDEX directly for getting information on “Dimension Ordering” which mostly Endeca JSP Ref app does. For workbench to know the newly created Dimension and Dimension Values execute

Plain text
Copy to clipboard
Open code in new window
EnlighterJS 3 Syntax Highlighter
ConfigManagerComponent.updateWsDimensions()
// If it's Oracle Endeca Commerce 11.1
WorkbenchManager.updateWsConfig();
ConfigManagerComponent.updateWsDimensions() // If it's Oracle Endeca Commerce 11.1 WorkbenchManager.updateWsConfig();
ConfigManagerComponent.updateWsDimensions()

// If it's Oracle Endeca Commerce 11.1
WorkbenchManager.updateWsConfig();

Deployment template Baseline Update script is configured to call this method after index distribution completes.

Plain text
Copy to clipboard
Open code in new window
EnlighterJS 3 Syntax Highlighter
// if Workbench is integrated, update Workbench with latest
// dimension values
if (ConfigManager.isWebStudioEnabled()) {
// Clears the webStudioTempDir ( Location:data/web_studio/temp/ - default paths)
ConfigManager.cleanDirs();
// Copies Location: data/forge_output/[prefix].dimensions.xml.gz to Location: data/web_studio/temp/ - default paths.
Forge.getPostForgeDimensions();
// Updates Workbench instance configuration with latest post-Forge dimensions, Location:data/web_studio/temp/[prefix].dimensions.xml.gz
ConfigManager.updateWsDimensions();
}
// if Workbench is integrated, update Workbench with latest // dimension values if (ConfigManager.isWebStudioEnabled()) { // Clears the webStudioTempDir ( Location:data/web_studio/temp/ - default paths) ConfigManager.cleanDirs(); // Copies Location: data/forge_output/[prefix].dimensions.xml.gz to Location: data/web_studio/temp/ - default paths. Forge.getPostForgeDimensions(); // Updates Workbench instance configuration with latest post-Forge dimensions, Location:data/web_studio/temp/[prefix].dimensions.xml.gz ConfigManager.updateWsDimensions(); }
// if Workbench is integrated, update Workbench with latest 
 // dimension values
 if (ConfigManager.isWebStudioEnabled()) {

// Clears the webStudioTempDir ( Location:data/web_studio/temp/ - default paths)
 ConfigManager.cleanDirs();

// Copies  Location: data/forge_output/[prefix].dimensions.xml.gz to  Location: data/web_studio/temp/ - default paths.
 Forge.getPostForgeDimensions();

// Updates Workbench instance configuration with latest post-Forge dimensions, Location:data/web_studio/temp/[prefix].dimensions.xml.gz
 ConfigManager.updateWsDimensions();
 }
Plain text
Copy to clipboard
Open code in new window
EnlighterJS 3 Syntax Highlighter
// If it's Oracle Endeca Commerce 11.1: Upload the generated dimension values to Workbench
WorkbenchManager.cleanDirs();
CAS.copyOutputDimensionsFile("${lastMileCrawlName}", WorkbenchManager.getWorkbenchTempDir());
WorkbenchManager.updateWsDimensions();
// Upload the generated config to Workbench
WorkbenchManager.updateWsConfig();
// If it's Oracle Endeca Commerce 11.1: Upload the generated dimension values to Workbench WorkbenchManager.cleanDirs(); CAS.copyOutputDimensionsFile("${lastMileCrawlName}", WorkbenchManager.getWorkbenchTempDir()); WorkbenchManager.updateWsDimensions(); // Upload the generated config to Workbench WorkbenchManager.updateWsConfig();
// If it's Oracle Endeca Commerce 11.1: Upload the generated dimension values to Workbench
     
WorkbenchManager.cleanDirs();
CAS.copyOutputDimensionsFile("${lastMileCrawlName}", WorkbenchManager.getWorkbenchTempDir());
WorkbenchManager.updateWsDimensions();
        
// Upload the generated config to Workbench
WorkbenchManager.updateWsConfig();

We can also run these methods manually from command-line without running a full baseline update, using control/runcommand.sh(.bat).

If still doesn’t show we are getting same error. Make ensure that there are no locks in Workbench, when instance configuration is being updated. Else the updates will fail due to lock resource exception, also review Location:data/forge_output/[prefix].dimensions.xml.gz or Location:data/web_studio/temp/[prefix].dimensions.xml.gz.

1 2 3 20
Let's Share
Hide Buttons
follow me on twitter
follow me on facebook
follow me on Linkedin
100%