The table below describes the key differences between the static OID model and the legacy OID model.
| Legacy OID Model | Static OID Model |
|---|---|
A statistic parameter set type can optionally declare a static OID, but it must be a complete OID. |
OIDs are split into a number of parts declared separately by SLEE components, statistic parameter set types, and OID suffix mapping descriptor documents. OID parts are combined at deployment time to produce complete static OIDs depending on the structure of components installed and resource adaptor entities and profile tables created. |
Statistic parameter set types that don’t declare a static OID are dynamically allocated an OID at deployment time. |
If not all the required OID parts are available at deployment time to generate a complete static OID for any given statistic parameter set type, no OID will be assigned to it. Dynamic OID allocation doesn’t occur. |
The OID assigned to a statistic parameter set type forms part of Rhino configuration state and may be arbitrarily changed at runtime using MBean operations. |
Static OIDs are set at deployment time and cannot be subsequently changed at runtime. Static OIDs don’t form part of Rhino configuration state. |
Statistic parameter set counter values are exposed as columns in SNMP tables. |
SNMP tables are only used for statistic parameter sets where static mapping of the parameter set name hasn’t been specified. Otherwise, SNMP scalar managed objects are used. |
