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


Chapter 4 Managing TIBCO Object Service Broker Data Definitions : Post Table Definition Optional Tasks

Post Table Definition Optional Tasks
 
Task A Dynamically change server parameters
Tools for Dynamic Modification
At runtime, you can dynamically modify the server parameters using the tools SETXPARM and RESETXPARM. The use of these tools reduces the number of table definitions required to map the external data. The changes to the server parameters are stored in either of the following two session tables:
The changes are in effect for the duration of the transaction or until SETXPARM is invoked again or the overrides are reset. The changes apply to definitions at locations specified as arguments to SETXPARM and RESETXPARM.
The Server Parameters That Can Be Overridden at Runtime
The following server parameters can be changed dynamically with SETXPARM and RESETXPARM:
Examples Using SETXPARM and RESETXPARM
CALL SETXPARM('TABLETYPE', 'SLK', 'SERVERID', 'TORONTO');
CALL RESETXPARM ('TABLETYPE', 'SLK', 'SERVERID', '');
See Also
TIBCO Object Service Broker Shareable Tools for detailed descriptions of the SETXPARM and RESETXPARM tools.
Task B Extract SLK dictionary data
Step 1: Execute the @SLKEXTRACT Rule
To begin copying dictionary data from an external DBMS into the shadow dictionary, run the @SLKEXTRACT rule from the workbench. The @SLKEXTRACT rule produces a screen similar to the one shown below:

 
External Server Metadata Extract/Clean Utility
Please enter
EITHER
Serverid | The ID of a running SLK server
DBSource | A preconfigured ODBC data
| source
 
OR
Tablename | An existing table of type SLK
| to reference both of the above
ALSO
If your SLK server is running remotely, please enter
location | A DOB node where
| your server is running
---------------------------------------------------------------------------
Search pattern (TABLES and COLUMNS only)
Tablename | These refer to the tables
Qualifier | in the external DBMS
Owner |
Table types (TABLES only) : TABLE Y VIEW Y SYSTEM TABLE N
ALIAS N SYNONYM N
PFKEYS: 3,12=EXIT Extract: 4=tables 5=columns 6=qualifiers 9=owners
Clean up the dictionary: 16=tables 17=columns 18=qualifiers 21=owners

 
Step 2: Enter the Serverid, DBSource, and Location
In the displayed screen, enter the Serverid, DBSource, and Location and press Enter.
If you already have an SLK table defined with the Serverid and DBSource jointly denoting the external DBMS from which you want to extract metadata, enter the name in the TableName field and press Enter. The Serverid, DBSource, Qualifier, and Owner fields are filled in automatically.
If the SLK table definition resides on a remote node and you enter this location, the values for Serverid, DBSource, Qualifier, and Owner are extracted from the definition at that location.
Step 3: Extract the Desired Information
Use the PF keys listed below to extract the desired information. After making a selection, you are prompted for confirmation.
Filters
If extracting columns and/or tables, you can restrict the amount of metadata extracted by using the filters in the lower portion of the screen. The following filters can be used with both tables (PF4) and columns (PF5):
If selecting tables only (PF4), you can also specify Y or N in each of the five fields (Table, View, System Table, Alias, and Synonym). Specifying N means that dictionary information for tables of this type is not extracted.
Step 4: Clean Up the Shadow Dictionary
After extracting the desired information, use the PF keys listed below to clean up the shadow dictionary. After making a selection, you are prompted for confirmation.
Task C Optimize access to the SLK table definition
Binding the Table Definition
To optimize access to the SLK table, you can bind an SLK table definition; you cannot bind its data. SLK tables for which you request binding are bound to both the Execution Environment and the Gateway when they are accessed from a rule.
You can dynamically request a re-bind for the Execution Environment if you want to change a bound definition. To do this, modify the definition using the Table Definer and run the $BINDOBJECT routine against the new definition. Subsequent access requests against this definition, issued within the Execution Environment where you run $BINDOBJECT, refresh the definition in the Gateway.
See Also
TIBCO Object Service Broker Application Administration for information on binding tables and on the $BINDOBJECT routine.

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