Tables with the same names on different nodes do not have to be related to each other. A relationship must be explicitly established through the use of a location parameter in the definition of the related tables. When this relationship is established, data can be stored remotely or locally to the definition.
In a production environment, it is advisable that you bind this definition. If this table is not bound, the minimal definition is brought into storage each time the table is accessed. For more information on binding, refer to
Chapter 5, Binding.
The location parameter of a table determines the node on which each table instance of a parameterized table can be stored. Two table instances with different values for their location parameter can have the same values for their data parameters. The values for the data parameters do
not have to be unique across the nodes.
The DEPARTMENTS table on NODE1 can have a data parameter value of 10 and occurrences with primary key values of 51, 52, and 58. The DEPARTMENTS table on NODE2 can also have a data parameter value of 10 and occurrences with primary key values of 52, 53, 58, and 59.
TIBCO Object Service Broker Managing Data for detailed information about defining tables and inserting data into tables.