![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
MAP tables are unlike other TIBCO Object Service Broker tables because the system has no inherent knowledge of how many occurrences exist in the table. For this reason, it is your responsibility to ensure that GET and FORALL statements do not sweep through storage unconstrained. A GET or FORALL statement that attempts to access unregistered storage causes the DATAREFERENCE exception to be raised; however, it is your responsibility to ensure that registered storage contains meaningful data in a format suitable for the syntax of the fields in the MAP table definition.For FORALL statements, we strongly recommend using the count parameter to limit the number of occurrences in storage that TIBCO Object Service Broker attempts to process on a MAP table access request. Other approaches include specifying suitable key ranges and condition testing using the UNTIL clause on the FORALL statement.
• You can browse or edit a MAP table in the same way you would browse any other TIBCO Object Service Broker table with the following exceptions:
• Do not use the ORDERED primary command with the Table Browser or Table Editor since ordering is not supported on MAP tables.
• Data in transaction storage cannot be browsed or edited because the Table Browser and Table Editor run in their own transaction.Accessing storage data using the rules language is similar to accessing data. Refer to Using Rules to Access Storage Data.
• If you use the default parameter value, you can access at least 16 MAP tables per transaction; more, depending on the size of the MAP table definitions, because the more fields you define, the more space is required to hold the definition in the memory in the Data Object Broker and the Execution Environment.TIBCO Object Service Broker Programming in Rules for information on writing rules and transactions.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |