Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 Administering a Distributed Environment : Defining and Storing the Data

Defining and Storing the Data
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.
Definitional and Data Requirements
To access data that resides on another node, the following conditions for the table must be met:
The table containing the data must be defined with the same table name and the same location parameter name on both the local and the remote node.
If data is to reside on a particular node, the full definition for the table must exist on that node.
If data is not to reside on a particular node, only a minimal definition of that table is required at that node. Optionally, both nodes can have a full definition if this is preferred.
If data resides on both a local and remote node, the data on both nodes must be accessible when the data on the remote node is being accessed.
What is a Minimal Definition?
A minimal definition consists of:
The name of the remote node where the full definition is located. This name must be supplied through the use of the Default field, Src field and global default value for the user, or Src and Sourcename fields.
Binding 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.
Can a Parameterized Table be Stored Across Nodes?
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 following conditions apply to storing the data of different table instances across nodes:
Example
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.
See Also
TIBCO Object Service Broker Managing Data for detailed information about defining tables and inserting data into tables.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved