The methods of assigning OID parts include using compile-time annotations, runtime annotations, manually created deployment descriptors, or OID suffix mappings descriptors. Each of these OID assignment methods requires its own support module.
The following table lists the modules required by different OID assignment methods:
| Module | Minimum version | Purpose |
|---|---|---|
|
3.1 |
Provides Rhino extension document type definitions (DTD). |
|
3.1 |
Supports compile-time annotation for OID and MIB alias assignments, and generates extension deployment descriptors. |
|
3.1 |
Supports compile-time annotation for OID and MIB alias assignments for resource adaptors, and generates extension deployment descriptors. These annotations support the Rhino-specific statistics model for resource adaptors. |
|
3.1 |
Supports runtime annotation for OID assignments. |
Each deployment descriptor for assigning static OIDs and MIB aliases must conform to a version of the relevant Rhino SLEE extension DTD,
which the slee-extensions module defines.
The following table lists the DTDs and their minimum versions required:
| Rhino extension DTD | Minimum version |
|---|---|
Profile specification |
1.1.3 |
Resource adaptor |
1.1.7 |
SBB |
1.1.4 |
Service |
1.4 |
Set the DTD version in the header of the deployment descriptor.
In the following example, the header of the oc-resource-adaptor-jar.xml extension deployment descriptor shows that the deployment descriptor uses the 1.1.7 version of the resource adaptor extension DTD.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE oc-resource-adaptor-jar PUBLIC
"-//Open Cloud Ltd.//DTD JAIN SLEE Resource Adaptor Extension 1.1.7//EN"
"http://www.opencloud.com/dtd/oc-resource-adaptor-jar_1_1_7.dtd">