Searching in a mapping

Moogle tab contains search functionality for the mapping.

  1. Click the Moogle tab in the Mapping Console view.
  2. Select a category for the Search in field:
    Category Search in field
    Input Document Elements To search in elements and attributes for the input document.
    Mapping Elements

    To search in mapping elements, for example loop, function, and parameter names.
    Java Code

    To search in the Java code for all UVJ and UVB functions.
    Output Document Elements To search in elements and attributes for the output document.
    Note: When you select a category, a new search is completed. You can use the same search string in different categories.
  3. Specify a search string in the Search for field:
    Search for field Search string
    Search for document element name or a parameter name.

    The search string is case insensitive and matches part of element names.

    For example, a search for "bc", matches "ABCD".
    Search for unknown string.

    Use the wildcard character * (asterisk) in place of an unknown string.

    For example, a search for "b*d" matches "ABCD", "bed", and "abd-001".
    For advanced users, search using regex.

    Regex are case sensitive.

    For example, to search for all elements with the name ID, specify the search string #.*/ID.

    where:

    • "#" is the regular expression indicator.

    • ".*" indicates any character zero or more times.

    • "/ID" indicates the end of the XPath.

    See http://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html#sum, Wikipedia, or other resources on the internet.

    The paths for the elements are used for searching, not the element names. For example, if the name of a loop matches the search string, all functions and their parameters and inner loops within the loop are returned as search result because the name of the loop is part of their paths.

  4. Click Search.

    The search result is displayed in a table list. The number of matches is shown in the status bar at the bottom of Eclipse.

  5. Optionally, to further refine the search result:
    1. Specify a search string for the search result in the field Find in result.
    2. Click the drop-down arrow to select all fields or a specific field.

    This search filter applies to one or all of the columns. The search string is case sensitive and will match part of the column values. You can use the wildcard character (*) asterisk in place of an unknown string.

Search result

This table shows the search areas in the Name field drop-down list and the information in each search area:

Search area Details
Index

This area shows the element icons and the chronological index order of the element. You cannot search data in this column.

Example of icons include a repeating element, a UVJ function, or a parameter.
Name This area shows the element names in a mapping. This name does not need to match the search string. This name can be for a parent element in the element’s path that matches the search string.
Type This area shows the type of the element, for example, Doc Input or Doc Output.
Path This area shows the path of the element. An element in this path matches the search string.
Description This area is the description of the element. Multiline descriptions are shown in tool tips.

To find an element in the mapping editor, double-click an item in the table. The mapping editor expands the view of parent nodes, scrolls to the element, and selects the element.

Data for input and output document elements and attributes are read into memory only when they are used. Document elements and attributes in use means that they are connected or expanded in the current editing session. Also called "lazy loading", this method is used to avoid too much memory usage, for example, when you store data for a complete BOD schema in memory.

When searching for input or output document elements, search runs on both the memory and schema including all unexpanded elements.

These are the indications and details for search match on elements and attributes:

  • In memory, search matches are indicated by the icons as used in the document tree.

  • In the schema, search matches are indicated by a document icon. The same icon is used for schemas in the Mapping Explorer view.

  • In the schema, search matches are not shown if they are in use.

When you pause on the field headers, tool tips are displayed with brief details on how to run search.

When you pause on an item in the table, more information on the item such as description or data type and length may be shown in a tool tip.

When you search on schemas, all schemas known for a mapping are searched including custom schemas, if any. If there are matches in such schemas, the returned paths will be relative to the root element(s) of that schema and not relative to a root element of the input or output schema. In this case, the path is regarded only on the schema where the element is defined. If you double-click the result row, search does not locate the element in the mapping editor.