What is the arbitration mechanism for finding out what index a subagent should use for a row in one of its tables?
In some circumstances, it may make sense for an application-specific mechanism to be used for determining the instance. When the instance of a MIB object must be unique but is arbitrary, or for other circumstances when an application-specific mechanism is not used, EMANATE provides an “instance reservation” mechanism. The instance reservation mechanism is described by a MIB, and the MIB is implemented in a subagent. Subagents cooperate by consulting the Instance Reservation Subagent before registering to support instances.
Related Questions
- Do we have to wait for General Ability Index (GAI) tables to be generated by outside researchers? Which tables are endorsed by Pearson?
- What is the arbitration mechanism for finding out what index a subagent should use for a row in one of its tables?
- Which SAP tables typically undergo index fragmentation?
