Managing users in the Workbench - Best practices

Oracle recommends the following best practices for managing users in the Workbench -

• Consider adding all users to groups to make managing permissions simpler

• Do not share the predefined admin user account. This makes it difficult to track who has made changes to Workbench. Create an account for each user or group that administers Workbench

• Do not let business users share accounts. Again, this makes it difficult to track changes in Workbench

• Create administrators in addition to the predefined admin. If one administrator loses a password, another administrator needs to reset it

• If you use LDAP, consider creating an LDAP group of administrators to add to the Administrators group in Workbench

About configuring Workbench resource caching in a Web browser - Endeca Workbench

If users are connecting to Workbench over a high-latency network, setting certain cache settings in the Web browser may improve performance. 

Workbench pages reference a number of assets such as images, CSS files, and JavaScript files. These assets are relatively static and are typically cached by the browser. They are served with HTTP headers that instruct the browser not to check for new versions of these files for a period of six hours. This results in better page load performance for users who connect to Workbench over a high-latency network. 

Oracle recommends setting your browser to check for new versions of pages automatically, and allocating 256MB or more of disk space to temporary files.

Endeca Tools which does not require baseline update? - Endeca Experience Manager

Below Search Tools does not require Endeca baseline update:
1) Keyword Redirects
2) Thesaurus
3) Automatic Phrasing

Endeca XM content promoted using the file-based method - Oracle Commerce v11.x

How to promote Endeca XM content using the file-based method?
 

Here are the steps:

     1) Update all store instances with correct shared location path

     Ex:

/dyn/admin/nucleus//atg/endeca/assembler/cartridge/manager/DefaultFileStoreFactory/

configurationPath=/opt/app/endeca/apps/CRS/data/workbench/application_export_archive/CRS

    2) Update LiveAppServerCluster.xml with all store instance details (refer DEV)

/opt/app/endeca/apps/CRS/config/script/LiveAppServerCluster.xml

    3) Update Workbench config file  as below:

/opt/app/endeca/apps/CRS/config/script/WorkbenchConfig.xml

  <![CDATA[

          IFCR.exportConfigSnapshot(LiveDgraphCluster);

         IFCR.exportApplication();

          LiveDgraphCluster.applyConfigSnapshot();

          AssemblerUpdate.updateAssemblers();

       //  IFCR.promoteFromAuthoringToLive();

          ]]>

applicationExportDir" value="/opt/app/endeca/apps/CRS/data/workbench/application_export_archive"

4) On the machine where the Oracle Commerce Platform is installed, mount the shared application_export_archive directory.

application_export_archive directory is used to store a ZIP file that contains content that is created by Experience Manager and then accessed by the Assembler. 
 

5)  Run Baseline update
/opt/app/endeca/apps/CRS/control:/>./baseline_update.sh

[04.01.16 17:44:41] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[04.01.16 17:44:43] INFO: Definition has not changed.
[04.01.16 17:44:43] INFO: Exporting MDEX tool contents to file CRS.mdex.2016-04-01_17-44-43.zip
[04.01.16 17:44:44] INFO: Exporting resource 'http://localhost:8006/ifcr/sites/CRS' to '/opt/app/endeca/apps/CRS/data/workbench/application_export_archive/CRS/CRS2016-04-01_17-44-44.zip'
[04.01.16 17:44:45] INFO: Finished exporting resource.
[04.01.16 17:44:45] INFO: Job #: update-dgraph-1459550685260 Sending update to server  - file: /tmp/soap-mdex2489908051012056922.xml
[04.01.16 17:44:45] INFO: The request to the Dgraph at localhost:15000 was successfully sent. The return code was : 200
[04.01.16 17:44:45] INFO: Job #: update-dgraph-1459550685260 Sending update to server  - file: /tmp/soap-mdex2489908051012056922.xml
[04.01.16 17:44:45] INFO: The request to the Dgraph at localhost:15000 was successfully sent. The return code was : 200
[04.01.16 17:44:45] INFO: Job #: update-dgraph-1459550685260 Sending update to server  - file: /tmp/soap-mdex2489908051012056922.xml
[04.01.16 17:44:46] INFO: The request to the Dgraph at localhost:15002 was successfully sent. The return code was : 200
[04.01.16 17:44:46] INFO: Begin updating Assemblers.
[04.01.16 17:44:46] INFO: Calling Assemblers to update contents.
[04.01.16 17:44:46] INFO: Updated Assembler at URL: localhost:8080/dyn/admin/assemblerAdmin/admin
[04.01.16 17:44:46] INFO: Finished updating Assemblers. Updating reference file.

Endeca Dimension Boost and Bury : Ordering Dimensions, Dimension Values and Dimension Group

Dimensions are attributes of your data that are used for navigation and searching. Each dimension has one or more dimension values.

       
       Ordering of dimensions 

By default, Endeca applications display dimensions, dimension values, and dimension groups in an order that is specified by the technical team.

Workbench User can override the default ordering of dimensions, dimension values, and dimension groups (including reordering dimensions and dimension values within dimension groups) in Endeca Workbench. 

How to Change the order using Endeca Workbench - Experience Manager? 

 

Discover Site Before and after changes: