What are Search Field Expressions?
Eager to get started? Follow the How to use the Search Field Wizard user guide
Find and correlate your data no matter if it's within the payload (xml, edifact/X12/flatfiles, json,... ), context or even external sources using Nodinite Search Field Expressions or your own custom search field expression plugins.
Search field expressions are used to extract one or more unique values for Search Fields on selected Message Types. For example, an Order Number may exist in multiple messages (of different Message Types) and to find this Order Number one or more search field expression are used for the Search Field configuration.
- There can be any number of search field expressions for a given Search Field
- Each search field expression can be used on one or more message type
- The search field expression can be set as being Global* (used on all message types) - Use with care!!! This option may affect overall system performance.
- The search field expression can be set as being Optional - Missing data will then not render the event in the Processed with Warnings* state
A Search Field Expression retrieves values from either the:
- Messages (message body/payload) (and/or depending on plugin)
- Context properties (Meta data stored in a Key/Value Collection for the Event
- Custom Plugins: External source using data from message or Context
The extract operation performed by the Logging Service uses the statement from the Expression on the selected Message Type using the selected Search Field Expression Type. The latter is a .NET dll implementing the appropriate contracts. The DLL's are put into the 'Plugins' folder of the Logging Service.
We at Nodinite have created many Search Field Expression Type plugins for many common scenarios. There are many different formats and data may be within the payload or within context properties (key/value pairs). You may also have the need to clean the data to get the result you seek (for example you only wants to extract the filename without suffix from a logged full path).
Different plugins comes with a different restrictions on what's possible, please review each one and/or the Troubleshooting user guide for further details.
|Plugin Name||XML||EDIFACT/X12/FLATFILE||JSON||Context Property|
|Flat File CSV|
|Flat File Fixed Width|
|Message Context Key|
|RegEx on Message Context with capturing groups|
|RegEx on Message Context|
|RegEx with capturing groups|
|XPath on Message Context|
|XPath on Wrapped XPath|
|XPath with RegEx|
Nodinite is an extendable platform, you may write and add your own plugins. This is useful for special cases (lookup tables, API calls, ...) and encrypted messages.