A Reference table holds information common to all LU instances or to multiple LU. For obvious optimization reasons, this information is stored in an external table and not in each LUI MicroDB.
Go to Project Tree > References , right click Create References Based On DB Tables to display the DB Browser menu, Context menu and References popup window.
Click DB Connection (top of the window) and select the Data Source Interface to display the Tables directory in the source DB.
Select the table. To select multiple tables, press the Ctrl key.
Add a prefix to the Reference table's name in the Name Prefix field (window's footer).
To populate the Reference Table using a Broadway flow, tick the Table population based Broadway flow box.
Reference tables can be edited by either changing the default data mapping, adding transformations or adding or removing columns like in LU tables.
When the Broadway flow population option is selected as defined above in Step 4, the table population process can be edited using the Broadway flow described here.
To access the Reference Viewer do the following:
Go to Project Tree > References, right click References Viewer, and then select the table. The Data Viewer window is displayed according to its hierarchy in the Instances Tree pane.
Click the data file to display the components hierarchy in the Instance DB Tree pane.
Additional properties can be defined in the Table Properties panel in the right pane of the selected Table tab.
By default Reference tables are synched in the background of each table according to the defined Sync policy. The following Sync options can be selected in the Table Properties panel:
None, default value, synchronization is according to the Sync policy defined.
Time Interval, set in days.hrs:min:sec
format.
Decision function, syncs the table according to the Decision function defined under the References > Java folder.
Functions or other tables can be attached to the Reference table:
Before accessing the Reference Table from a specific LU, or before it can be used as a lookup object, it must be attached to the LU.
Open the LU Schema Window
In the right panel, select the References tab.
Check the relevant Reference table(s) option.
Note: Reference tables can also be accessed via Lookup tables, Web Services, functions, jobs and Broadway Actors.
Reference Tables must be deployed before being used. As a result of the deployment, a synchronization job process is triggered in the background to ensure that all commonDB copies are kept in-sync across the Fabric Cluster.
To deploy the Reference Tables, go to the Project Tree, right click References, select Deploy to Server and then the Server to deploy to the Reference table.
Note:
If the reference table as been attached to an LU Schema as described above, the LU must also be (re-)deployed.
A Reference table holds information common to all LU instances or to multiple LU. For obvious optimization reasons, this information is stored in an external table and not in each LUI MicroDB.
Go to Project Tree > References , right click Create References Based On DB Tables to display the DB Browser menu, Context menu and References popup window.
Click DB Connection (top of the window) and select the Data Source Interface to display the Tables directory in the source DB.
Select the table. To select multiple tables, press the Ctrl key.
Add a prefix to the Reference table's name in the Name Prefix field (window's footer).
To populate the Reference Table using a Broadway flow, tick the Table population based Broadway flow box.
Reference tables can be edited by either changing the default data mapping, adding transformations or adding or removing columns like in LU tables.
When the Broadway flow population option is selected as defined above in Step 4, the table population process can be edited using the Broadway flow described here.
To access the Reference Viewer do the following:
Go to Project Tree > References, right click References Viewer, and then select the table. The Data Viewer window is displayed according to its hierarchy in the Instances Tree pane.
Click the data file to display the components hierarchy in the Instance DB Tree pane.
Additional properties can be defined in the Table Properties panel in the right pane of the selected Table tab.
By default Reference tables are synched in the background of each table according to the defined Sync policy. The following Sync options can be selected in the Table Properties panel:
None, default value, synchronization is according to the Sync policy defined.
Time Interval, set in days.hrs:min:sec
format.
Decision function, syncs the table according to the Decision function defined under the References > Java folder.
Functions or other tables can be attached to the Reference table:
Before accessing the Reference Table from a specific LU, or before it can be used as a lookup object, it must be attached to the LU.
Open the LU Schema Window
In the right panel, select the References tab.
Check the relevant Reference table(s) option.
Note: Reference tables can also be accessed via Lookup tables, Web Services, functions, jobs and Broadway Actors.
Reference Tables must be deployed before being used. As a result of the deployment, a synchronization job process is triggered in the background to ensure that all commonDB copies are kept in-sync across the Fabric Cluster.
To deploy the Reference Tables, go to the Project Tree, right click References, select Deploy to Server and then the Server to deploy to the Reference table.
Note:
If the reference table as been attached to an LU Schema as described above, the LU must also be (re-)deployed.