An Order Metaconnector is one of the standard connection documents included with LEI. It's called a "metaconnector" because it doesn't connect to anything by itself - it gets attached to another connector to perform some operation. For example, an Order Metaconnector reads the data coming in from the connection, sorts it according to your criteria, THEN feeds it into LEI.
In the activity document, you will specify the metaconnector. Then the metaconnector has a place to specify what "actual" connector to use. That way, the metaconnector sits between the connector and the activity.
The usual strategy is to leave the Notes side alone, and force the back-end to conform to the Notes style of sorting (because Notes is a known quantity). You'd apply an Order Metaconnector to your back-end connection, and have it Sort Ascending using LMBCS as the Sorting Character Set.
I should note that this is only necessary if you're seeing a large number of unnecessary (or at least suspect) inserts and deletions every run of this activity. If not, then this may not help. You can find more info about the Order Metaconnector in the LEI help documentation. See Chapter 12 of this link:
http://publib-b.boulder.ibm.com/lotus/c2398640.nsf
Return to top
. . . . . . RE: What can cause an LEI Replicati... (Daniel W Heiche... 11.Feb.14)
Print this page
