OK, here's what I found:
1) The Information Item is linked to its associated Information Flow connector by an entry in table t_xref in the EA database, as below:
Fields:
XrefID, Name, Type, Visibility, Namespace, Requirement, Constraint, Behavior, Partition, Description, Client, Link
Values:
{755E6BE2-3935-4251-8EFE-3FC343EC5327}, MOFProps, connector property, Public, , , , conveyed, 0, {153649D7-4576-43e3-AFC9-164C8E54F20F}, {35FF94D1-A91D-46ff-99E7-8DA48A27150E}, <none>
The fields 'Description' and 'Client' are the ea_guids for the information item and the information flow, respectively.
2) If another connector (say, an association) realizes an information flow, the connector and the information flow are linked by an entry in table t_xref in the EA database, as below:
Fields:
XrefID, Name, Type, Visibility, Namespace, Requirement, Constraint, Behavior, Partition, Description, Client, Link
Values:
{8CB6EFC6-E0E0-4614-92E2-1895BAF4C3C5}, MOFProps, connector property, Public, , , , abstraction, 0, {35FF94D1-A91D-46ff-99E7-8DA48A27150E}, {DA2F4C80-6125-453b-AAF3-51B81B9DDD82}, <none>
The fields 'Description' and 'Client' are the ea_guids for the information flow and the association, respectively.
3) If you want to do this programmatically, it appears that you would need to add the necessary rows to table t_xref yourself, either by using the undocumented AI method Repository.Execute(<SQL statement to add a row>) (see
http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1284736693/1#1 for more info) or by accessing the database directly using the database driver of your choice.
Word to Sparx - this outta be addressed in the API.