Navigation: Filtering & Collection > Event Bindings >

Binding (Change)

Still need help? Create a Support Ticket with Stratum Support

Send comments on this topic.

← Previous Next →

 

Bindings (Change)

Listed below is a description/explanation of each attribute that can be used in a Binding setup. Not all parameters are used together as these cover a large amount of conditions. Note: whenever an existing Binding definition is changed, it will propagate out and change any Reader schedule that refers to that master binding definition.

Event Binding ID

The Binding ID

 

Binding Description

 A meaningful description of the Binding ID template

 

Protocol

The transport protocol defined for the binding

 

IP Address

The Server IP address that the Tag data is to be sent to

 

URI

URI string of payload being sent to subscribing system.

 

User Name

For those Bindings that require authentication (such Stored Procedure or Web Service), user name can be specified here

 

User Password

For those Bindings that require authentication (such Stored Procedure or Web Service), user pswd can be specified here

 

Data Format

Data format of payload being sent to subscribing system, Options are program LIST as well as XML, CSV or TSV documents.

 

Status

The current status of the Binding definition (either Active or Inactive).

 

Email Notification Recipient

The email address to send binding specific alerts. Note: This overrides the default SMTP Recipient value under System Settings

 

Advanced Notification (days)

Used for those Bindings where an expiry date has to be evaluated and emailed as a notification when object is read.

 

Antenna 1 Trigger

Specifies the state of a Trigger that will initiate a read on antenna 2. This is a binding specific parameter.

 

Antenna 2 Trigger

Specifies the state of a Trigger that will initiate a read on antenna 2. This is a binding specific parameter.

 

UDA Grouping 1

Specifies a grouping of UDAs (User Defined Attributes) to send with the payload. This is a binding specific parameter.

 

UDA Grouping 2

Specifies a grouping of UDAs (User Defined Attributes) to send with the payload. This is a binding specific parameter.

 

Dwell Time (min)

This is the time period that TagNet will ignore further read events until the dwell period has expired. For example, when a tagged object goes through a read zone and TagNet changes its location state from A to B, the dwell period gives it time to move away from the read zone before it is evaluated again for another inventory move (i.e returning back through same B to A).  The dwell time should be long enough to allow the object to move away from the portal read zone but not too long that if it is brought back in the reverse direction it will be not be ignored.

 

Dwell Time Option

Specifies the dwell option used in conjunction with the dwell time. There are (4) dwell time options in the dropdown:

[Global] indicates that if the Tag was seen previously at any TagNet Physical Reader its LRE (Last Read Event) will be taken into consideration.

[Location] indicates that only if the Tag was seen at a Physical Reader within the same Logical Reader group, will its LRE will be taken into consideration.

[Reader] indicates that only if the Tag was seen at the same Physical Reader (any antenna) will its LRE will be taken into consideration.

[Read Point] indicates that only if that Tag was seen at the same Antenna on a given Physical Reader will its LRE will be taken into consideration. Note: When implementing dwell by read point the antenna location name comes into play. Assigning the same antenna name to multiple antennas will group the antennas as one so a tag read from one antenna will entail that all antennas with the same name will be pooled to get the most recent tag date and time as logged in RFDTAGVS.

 

Note: The LRE time is updated every time the tag is read anywhere unless it is specifically filtered out in the Event Subscription Binding.  Though the tag event will be logged, it will not be evaluated for any business logic nor will it update the LRE. This filtering is typically done so that downstream read zones will not ignore it because its LRE was updated (e.g. if the tagged object has a specific inventory state or attribute that precludes it from being considered for dwell based logic).

 

Folder to Process

Specifies the folder path for the import to process

 

File to Process

Specifies the file path for the import file to process

 

Data Format

Specifies the type of the import file (CSV, TSV, XLS, XML)

 

Rename File As

Specifies the path and file to rename so there is no contention on new import files

 

Archive File As

Specifies the path and file of the import file to archive after being processed. This is intended as a backup only. It contains a mask variable of *yyyymmdd_*hhmmss that can be used to make the file absolutely unique.

 

Excel Sheet Name

The sheet name to be processed when the ‘File to Process’ has a data format of XLS 

 

Generate Audit File

When importing data from another system, specifies the name and path of the audit file

 

Audit File Format

The file format of the Audit File above, currently CSV and TSV are supported.

 

WSDL

The WDSL file (e.g. ParseRFID.xml)

 

WSDL Location

The WSDL file location (e.g. file:/C:/TagNet/rfid/wsdl/ParseRFID.xml)

 

Address Feature Enabled

Control the SOAP header (Action element, MustUnderstand=”1”). This is a binding specific parameter to RFDTHWS

 

Address Feature Required

Control the SOAP header (Action element, MustUnderstand=”1”). This is a binding specific parameter to RFDTHWS

 

Interface IP Address

The IP address of the device that the Tag data is to be sent to. Example would be IP to serial converter or a Hardware keyboard wedge. This is a binding specific parameter

 

Terminate With

Indicates to receiving endpoint that XML document is complete. Allows for blank, NULL, CR (Carriage Return), EOT (End-of-Transmission char), LF (Line Feed) or TAB (tab to next column) making it flexible depending on the requirements of the interface.

 

Query Interval (msec)

The time in milliseconds to query an external results table as a result of an integration call

 

Query Timeout (sec)

How long to wait before timing out on a response to an external results table as a result of an integration call.

 

Error Recovery Attempts

The number of attempts to send event payload before giving up

 

Error Recovery Delay (msec)

The amount of time in milliseconds to wait before reattempting socket connection to client

 

Inventory Movement Rules

Specifies whether to include IMOVE rules in the Binding. If *YES is specified then only tag events that have a valid IMOVE rule will be pushed to the PEV. If *NO specified, then all tag events will be pushed to PEV. If *RESULTSET specified (and Log Result Set = *YES) then Dwell Time is taken into consideration and only those tag events that exceed the dwell period since last read event will be pushed to PEV.

 

Move Children

Specifies whether to move any linked 'Child' tags to the same location as the parent tag when moved

 

Email Tag Exceptions

Specifies whether to send email notification based on IMOVE. If *YES is specified then only tag events that DO NOT have a valid IMOVE rule will sent via email. Note: if none of the tags in a given event payload make a hit on IMOVE or are unmapped, then no exception email will be sent (at least one tag has to make a valid hit to trigger email event), see IMOVE rules.

 

Tag Movement Rules

Specifies whether to include TMOVE rules in the PEVG binding. If *YES is specified then then the appropriate TMOVE rule will be displayed along with tag events on the PEV (but will not stop them from being displayed if no TMOVE rule exists). If *NO specified, then all tag events will be pushed to PEV but no TMOVE rules will be considered.

 

Log Result Set

If *YES selected, specifies whether the Dwell is taken into consideration on those tag events within a given event cycle. Those tags that exceed the dwell period from the last time seen will be pushed to PEV. Note: Result Set enablement also has a performance benefit as it calculates which tags meet the condition ‘post processing’ and stores it so the filtering overhead is not incurred at the time when the PEV requests the Event payload (keys).

 

Ping PEV Before Connecting

For large PEV distribution lists where the PEV client may not be up and listening all the time, specifying *YES will initiate a simple ping to that IP address before attempting to send the PEV payload.  This feature can save considerable CPU time if enabled. Note: if the Windows client has disabled the ping feature for security reasons, it will never receive a PEV payload. If this is the case disable local client firewall to allow pings.

 

Ping Command Options

Used in conjunction with above, these are standard DOS commands such as –n 1 (number of ping requests to send)  –w 50  (Timeout in milliseconds)

 

FTP Source Directory

Used in conjunction with the generic FTP ‘Tagnet’ binding that will poll this directory path looking for objects to send to the FTP site specified in the IP Address setting (e.g. C:\TagNet\rifd\extract). See example below.

 

User Authentication

When SSL is required for the secured transport (value 'Basic Authentication'

 

Certificate Keystore

Specifies where the PKI certificate is stored (value 'Windows')

 

Execute Command

Certain Bindings (currently only RFDXLOC) will execute the DOS command string at the end of the binding. RFDEXTP is mission specific and will only execute the command string.

 

Execute Command Timeout (msec)

Specifies the timeout value for command string

 

Auto Generate Item

Specifies whether to auto-generate a GTIN or Asset ID when importing tags (*YES or *NO). This is a Binding specific parameter

 

Item Prefix

The Item prefix used in conjunction with the above. This is a Binding specific parameter

 

Item Length

The Item length used in conjunction with the above. This is a Binding specific parameter

 

Check Part ID

Validate if the same part ID has been used for another Item (*YES or *NO). This is a Binding specific parameter

 

Endpoint Post

Specifies whether the payload should be send out to an HTTP end point (*YES or *NO) . This is a Binding specific parameter for RFDFULL where you can have the tag delta sent out to an endpoint

 

Entity Name

Specifies the UDA type to be used (RFDASSM or RFDLOCIN). This is a Binding specific parameter

 

Element Name

Specifics the UDA element to be updated. This is a Binding specific parameter.

 

 

 

 

Specifies the dwell option used in conjunction with the dwell time. There four values to choose from:

[Global] - read events from any reader location will be evaluated for last read time

[Location] - read events from only those physical readers linked to the logical reader location will be evaluated for last read time

[Reader] - only read events from that same physical reader will be evaluated for last read time

[Antenna] only read events from that same physical reader antenna will be evaluated for last read time

 

 


Copyright © 2023 Stratum Global, Inc.