Rhino 3.1 introduces a static OID model. In this model, Rhino no longer dynamically assigns OIDs to statistics in an application.
The static OID model splits the OID of each statistic into OID parts. During application development, developers manually assign an OID part to each Rhino artifact, such as a service or a parameter set type. At deployment time, Rhino combines the OID parts of relevant artifacts to form a full static OID for each statistic.
Rhino uses OIDs to expose statistics through SNMP. The OIDs of the statistics that operators monitor through SNMP must remain the same when the relevant application is upgraded. Otherwise, the monitoring will break. As the static OID model ensures that the OIDs of the statistics don’t change between versions by assigning OIDs statically, operators can continue to monitor statistics after application upgrade. In addition, with the static OID model, administrators don’t need to manually retain the OIDs dynamically assigned in an earlier version.
The static OID model requires you to manually assign OID parts to Rhino artifacts during application development. Different assignment methods are provided to cater to different development situations. For example, you can use compile-time Java annotations to assign an OID for a resource adaptor. The Assigning OID parts sections provide detailed information about OID assignment methods and assignment examples.