In the static OID model, you must manually assign OID parts to individual Rhino artifacts such as SBBs or parameter set types. Rhino combines different OID parts to form complete OIDs at deployment time.

The methods for assigning OID parts are as follows:

  • Use deployment descriptors

  • Use runtime code annotation introspection

  • Use an OID suffix mappings descriptor

Use deployment descriptors

This method applies to artifacts other than profile tables and resource adaptor entities.

To assign OID parts with this method, add OID assignment annotations onto the component’s Java class by importing the annotations from the slee-annotations or the stats-annotations module. From these annotations, the annotation processor automatically generates a deployment descriptor for the corresponding component at compile time.

Alternatively, create a deployment descriptor manually by writing appropriate static OID assignment elements in the deployment descriptor. For example, you can declare the OID suffix for an SBB by using the attributes of the <stats-presentation> element in the Rhino extension deployment descriptor.

Deploy the automatically generated or manually created deployment descriptors with relevant components. For more information, see Build and deployment script considerations.

Use runtime code annotation introspection

This method applies to artifacts other than profile tables and resource adaptor entities.

To assign OID parts with this method, import relevant annotations from the rhino-ra module, and then add annotations onto the component’s Java class that are read at runtime. This method doesn’t require any deployment descriptors.

For more information, see the usage extensions section in Rhino Extended APIs.

Use an OID suffix mappings descriptor

This method applies only to profile tables and resource adaptor entities.

You cannot assign OID parts for resource adaptor entities or profile tables during application development because their names aren’t known at the time. Assign OID parts for resource adaptor entities and profile tables in an application with an OID suffix mappings descriptor, which is a JSON document consisting of an identity and a list of OID mappings.

Deploy the OID suffix mappings descriptor document into Rhino together with the relevant application.

For information about creating an OID suffix mappings descriptor, see Create an OID suffix mappings descriptor.

Previous page Next page