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


Chapter 5 Binding : Binding Tables, Screens, and Rules

Binding Tables, Screens, and Rules
What is Binding?
Binding is the copying of the definition of a table, screen, or rule, or the data of a table into the shared storage of an Execution Environment when the first access is made to it within a session. Subsequent references within the session access this copy.
Advantages
Binding can significantly reduce I/O between the Execution Environment and the Data Object Broker, therefore optimizing access to the database. If binding is not in place, upon each subsequent reference to a table, screen or rule, a new copy is brought back into storage from the data store.
How Long is the Use of a Bound Copy in Effect?
The use of the bound copy is in effect for the life of the session. If a parameterized table is bound, only the table instances that have been referenced are brought into the shared storage, even though the bind is on the whole table.
If required, you can refresh the bound copy during the life of a session. Refer to Refreshing the Bound Copy for more information.
Types of Binding
There are two types of binds:
You can bind the definitions of tables and screens. Refer to Definition Binding for more information about binding table and screen definitions. Rules are automatically bound when they are promoted into the installation or system library.
You can bind the data of TDS tables. If you bind the data, you must also bind the definition of the table. Refer to Data Binding for more information.
Maximum Number of Binds
An Execution Environment parameters determine the limits of bound storage: REGIONTABLESIZE.
If a user tries to access a bound table that cannot fit within the allocation for the Execution Environment, the user’s application signals a DEFINITIONFAIL error.
Storage Limits for Bound Tables
In addition to bound storage limits in the Execution Environment, each bound table has a storage limit of 26.5 KB. This does not include additional storage required for indexing. The limit represents the sum of sizes of all occurrences retrieved by the Data Object Broker. The size of additional storage is (number of occurrences) x (keysize + 4).
See Also
TIBCO Object Service Broker Parameters for more information about the REGIONTABLESIZE Execution Environment parameters.

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