We are performing numerous MemPut interactions, however the mpi_entique_id table is not being populated.
Two possible causes for this scenario are having the Input Queue disabled, or having Optimized Put enabled.
Entity Input Queue Disabled
Verify that the Input Queue is enabled for the specific entity type (in this case "id"). To do this, open Workbench and load the proper Hub Configuration file (.imm). Next, navigate to the Member Types tab and select the appropriate Member Type. On the Entity Types sub-tab, select the appropriate Entity Type and check the "Uses an input queue" parameter in the Properties panel. If it is set to false, then it is expected that no rows are added to the mpi_entique_id table.
Optimized Put Mode Enabled
This mode allows the Engine to perform a quick check during the MemPut interaction to determine if any of the attributes involved in the algorithm have been modified. If none of the attributes have changed, then there is no need to perform Entity Management again on that member. To check this parameter, open Workbench and load the proper Hub Configuration file (.imm). Next, navigate to the Member Types tab and select the appropriate Member Type. In the Properties panel, check to see if the "Optimized Put Mode" parameter is set to true or false. If it is set to true and the data you're loading does not change any Algorithm involved attributes, then no rows in the mpi_entique_id table would be expected.
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.