Why Enterprise Vault (EV) browser search (Search.asp) or EV Search should not be used to compare an Accelerator search results

Problem

Why Enterprise Vault (EV) browser search (Search.asp) or EV Search should not be used to compare a Compliance Accelerator (CA) or Discovery Accelerator (DA) search results in both Domino and Exchange environments

Cause

Several factors will change the number of hits returned between an EV browser search or EV Search and an Accelerator search.  Below will examine the differences between an EV Browser Search or an EV Search and a Discovery Accelerator (DA) or Compliance Accelerator (CA) search.  Note that EV Browser Search is available in all EV versions prior to 12.0.0 but can be disabled in EV 11.0.0 or 11.0.1 (base and all Cumulative Hot Fix releases).

EV Browser Search or EV Search versus DA Search
EV Browser Search and EV Search provides for a simple search of the EV indexes volumes of the single archive that has been selected to be searched.  By default, neither will apply filters.  If an index volume does not incorporate an ItemGranularityOnly Schema (Schema Type 1 or Schema Flag 3), EV Browser Search and EV Search only searches the top level document as well as secondary attachments.  When an item matches the search criteria, the top level document and all of its attachments are returned as individual hits.  (Example:  A document that has 4 attachments and matches the search criteria will return 5 hits).  Unlike the search using EV Browser Search or EV Search, a DA match of search criteria will return the top level document and all of its attachments as a single hit count.  See Article 000032798 in the Related Articles section for more information about item granularity.  See Article 000032240 in the Related Articles section for information on how to determine the Schema Type in 32-bit index volumes (64-bit index Volumes are equivalent to Schema Type 3).
 
Another example as to why EV Browser Search or EV Search should not be used to compare results with a DA search would be Date Range.  By default EV Browser Search and EV Search includes a separate query to attachments.  If the attachments have a different creation date than the top level document, the attachment creation date will be considered in determining qualification of an item.  This will allow more hits in the resultant set then a true top level document query from DA. 


EV Browser Search or EV Search verses CA Search
There are several factors that will cause the numbers to be different between an EV Browser Search or EV Search and a CA search.  Not only does a CA search treat ItemGranularityOnly in the same fashion as a DA search (reference EV Browser Search (Search.asp) or EV Search verses DA Search), but CA usually searches Journal archived indexed items for Message Direction and Department tagging.  Message Direction tagging is applied by the Journal Task while the Department tagging is applied by the Journal Connector in EV/CA versions 11.0.0 and prior or by the EV Storage Service in EV/CA version 11.0.1 and later.  Department tagging can be removed from the search criteria by unselecting the Department and selecting the Individual in the Authors and Recipients section of the CA search parameters during the search creation.  Message Direction is not used in the search criteria only when messages between CA Departments or internal to the organization are specified.  Message Direction is used in all other CA searches.  Refer to Article 000109550 in the Related Articles section for more information about message direction selection in CA searches.


EV Browser Search or EV Search verses CA or DA Search
A significant factor that will cause the numbers to be different between an EV Browser Search or EV Search and a CA or DA search is the archive selection for the search.  An EV Browser or EV Search can only be configured to search against a single archive's index volumes.  A CA or DA search can be configured to search against multiple archives' index volumes.  The ability to search against multiple archives allows CA and DA to return more hits that a search run using the EV Browser Search or EV Search utilities. 


How to determine if an index has ItemGranularityOnly enabled
1. Obtain the Archive ID under the Advanced tab of the Archive properties page from the EV Administration Console.
2. Locate the logical path to the index location (Under the Location tab of the Index Service properties page from the EV Administration Console).
3. Open a Command Prompt and navigate to the EV installation folder on the Indexing server.
4. Type:  IndexServer /summary "X:\PathToIndex\ArchiveID".
5. Locate the Schema Flag value in the returned pop up window.  If the Schema Flag value is 3, ItemGranularityOnly option is enabled on this index.


How to determine if items have Department tagging using EV Browser Search
1. Open the advanced, version three, EV Browser Search window (example URL is http://Servername/EnterpriseVault/search.asp?advanced=3 where Servername is the DNS name of the EV Indexing server).
2. Select the Vault to search from the Vault drop down menu.
3. Type into 'Other Result Attributes': KVSCA.Department.  (Case sensitive)
4. Press the Search button at the bottom of the web page.
5. If the Department tag is present in the index item, the attribute will appear on each of the indexed items.


How to determine if items have Message Direction tagging using EV Browser Search
1. Open the advanced, version three, EV Browser Search window (example URL is http://Servername/EnterpriseVault/search.asp?advanced=3 where Servername is the DNS name of the EV Indexing server).
2. Select the Vault to search from the Vault drop down menu.
3. Type into 'Other Result Attributes': Vault.MsgDirection.  (Case sensitive)
4. Press the Search button at the bottom of the web page.
5. If the Message Direction tag is present in the index item, the attribute will appear on each of the indexed items.


How to determine if items have Message Direction or Department tagging using EV Search
1. Open the EV Search window (example URL is http://Servername/EnterpriseVault/Search where Servername is the DNS name of the EV Indexing server)
2. Select the Vault to search from the listing of vaults that have been permissioned to be searched by the user.
3. In the item list pane, right click on the column header line.
4. Select the Columns option and then the Customize Columns option.
5. Select any of the rows that the Property Name column entry is not in bold text and has an empty check box to its left and the background of the columns are white (gray background rows cannot be changed).
6. Click the check box of that row to place a check mark in it, replace the Property Name column entry with 'Vault.MsgDirection' and then replace the Column Header column entry to 'Direction' to see the message direction tag if one has been applied.
7. Select any of the other rows that the Property Name column entry is not in bold text and has an empty check box to its left and the background of the columns are white (gray background rows cannot be changed).
8. Click the check box of that row to place a check mark in it, replace the Property Name column entry with 'KVSCA.Department' and then replace the Column Header column entry to 'CA Department' to see the CA Department ID tag if one has been applied.
9. Click the Done button to save the changes.  This will cause the current contents listing to refresh and display the new column headers and each item's appropriate data for that column.
 

Solution

Use EV Browser Search or EV Search to obtain only a very rough idea of the number of results for specific search criteria against a single archive's index volumes.  Expect a CA or DA search to return different numbers of search results due to the differences in the search criteria used by CA and DA and due to the possibility of a CA or DA search running against multiple archives' index volumes.

To see the differences in the search criteria passed to the search engine by an EV Browser Search, EV Search, CA or DA search, follow the steps below.
  1. Log onto the EV indexing server as the vault service account.
  2. Open a Command Prompt (can be in Administrator mode or normal mode).
  3. Change the drive\folder to the EV installation folder (default on a 64-bit version of Windows Server is 'C:\Program Files (x86)\Enterprise Vault').
  4. At the command prompt, type dtrace and then press the Enter key.
  5. At the dtrace prompt, type the letter v and then press the Enter key.  This will cause a listing of all EV processes to be displayed with a number associated with each process.
  6. Scroll through the listing and note the numbers associated with the following processes:
    1. EVIndexQueryServer     (This option is only needed if searching against 64-bit index volumes, such as those in an EV 10.x or later installation.)
    2. IndexBroker     (This option is only needed if searching against 32-bit index volumes, such as those in an EV 9.x installation.)
    3. IndexServer     (This option is only needed if searching against 32-bit index volumes, such as those in an EV 9.x installation.)
  7. At the dtrace prompt, type the word set followed by single space, the number for the EVIndexQueryServer process followed by a single space and then the letter v followed by pressing the Enter key.  For example, if the number associated with the EVIndexQueryServer process is 36, the command typed at the dtrace prompt would be set 36 v before pressing the Enter key.     (This option is only needed if searching against 64-bit index volumes, such as those in an EV 10.x or later installation.)
  8. At the dtrace prompt, type the word set followed by single space, the number for the IndexBroker process followed by a single space and then the letter v followed by pressing the Enter key.  For example, if the number associated with the IndexBroker process is 74, the command typed at the dtrace prompt would be set 74 v before pressing the Enter key.     (This option is only needed if searching against 32-bit index volumes, such as those in an EV 9.x installation.)
  9. At the dtrace prompt, type the word set followed by single space, the number for the IndexServer process followed by a single space and then the letter v followed by pressing the Enter key.  For example, if the number associated with the IndexServer process is 75, the command typed at the dtrace prompt would be set 75 v before pressing the Enter key.     (This option is only needed if searching against 32-bit index volumes, such as those in an EV 9.x installation.)
  10. At the dtrace prompt, type the word log followed by the path and name for the log file to be written to capture the dtrace entries and then followed by pressing the Enter key.  For example, to save the dtrace entries to a file named 'EVSearchCriteria.log in the folder 'C:\Traces', the command typed at the dtrace prompt would be log C:\Traces\EVSearchCriteria.log before pressing the Enter key.  Note that it is recommended to have the file name reflect the type of search being run. For example. a CA search log could be named 'CASearchCriteria.l.og' while a DA search log could be named 'DASearchCriteria.log'.
  11. Run the EV Browser Search, EV Search, CA or DA search to capture the search criteria passed to the search engine.
  12. When the search has completed, stop writing to the dtrace log file by typing log at the dtrace prompt and then pressing the Enter key twice.
  13. Repeat Steps 10 through 12 for the EV Browser Search, EV Search, CA or DA search (which ever was not run in Step 11).
  14. To close dtrace, enter the word exit at the dtrace prompt and then press the Enter key.
  15. Use a text editor to open each of the dtrace log files captured in Steps 10 through 13.
  16. Search the log file contents for the word parsed for 32-bit index volume queries or the words Velocity query for 64-bit index volumes to find the lines that contain the search criteria that was passed to the search engine.  It should be noted that a CA or DA search will have more criteria than an EV Browser Search or EV Search as CA and DA include additional criteria by default.

Examples:
- DA search for author or recipient "User 3" and subject or content "Daily":
{QueryTracer} [Search 9] [1/1] Velocity query:|<?xml version="1.0" encoding="utf-16"?>|<operator xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" logic="and">|  <operator logic="and" xmlns="urn:/velocity/objects">|    <operator logic="and">|      <term field="name" str="User.3" />|      <operator logic="range">|        <term field="date" str="1970-01-01T00:00:00Z" />|        <term field="date" str="2038-01-01T00:00:00Z" />|      </operator>|      <operator logic="range">|        <term field="anum" str="0" />|        <term field="anum" str="0" />|      </operator>|      <operator logic="and">|        <operator logic="not">|          <term field="_Vault.PolicyAction" str="EXCLUDE" />|        </operator>|      </operator>|      <operator logic="range">|        <term field="snum" str="1" />|        <term field="snum" str="2147483647" />|      </operator>|    </operator>|    <operator logic="and">|      <term field="x_text" str="Daily" />|      <operator logic="range">|        <term field="snum" str="1" />|        <term field="snum" str="2147483647" />|      </operator>|    </operator>|  </operator>|</operator>

- EV Search for author "User 3" and subject or content "Daily":
{QueryTracer} [Search 8] [1/1] Velocity query:|<?xml version="1.0" encoding="utf-16"?>|<operator xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" logic="and">|  <operator logic="and" xmlns="urn:/velocity/objects">|    <term field="pvid" str="1c78d24702a88074081137264c127d8b41110000evserver1.ev.local" />|    <operator logic="not">|      <operator logic="equal">|        <term field="x_sens" str="2" />|      </operator>|    </operator>|    <term field="x_auth" str="User 3" />|    <term field="x_text" str="Daily" />|  </operator>|</operator>
 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)