Create an OID suffix mappings descriptor document for assigning OID suffixes to resource adaptor entities and profile tables in an application either manually or from an input template.

This section provides instructions on creating the document manually. For information about creating the document using an input template, see Substitute OID mappings in OID suffix mappings descriptors.

The process of creating an OID suffix mappings descriptor is as follows:

  1. Find out what resource adaptor entities and profile tables you need to deploy with the application.

    • Decide the OID mappings by the deployment of the whole application rather than individual components.

    • Consider co-deployments of the application with other applications.

      The OID suffix mappings descriptor of an application assigns the OID suffixes of the resource adaptor entities or profile tables in the application. There may be potential OID conflicts between the OID suffix mappings descriptors of different applications.

      Tip Resource adaptor entities with different names should generally have different OID suffixes.

    • For the deployment of an existing application, find out what resource adaptor entities and profile tables are currently deployed by using the listraentities and listprofiletables Rhino management console commands.

  2. Create an OID suffix mappings descriptor to assign an OID suffix to each resource adaptor entity and profile table in the application.

    The following example adds OID suffix mappings for three HTTP resource adaptor entities with an OID suffix mappings descriptor.

    {
  "name": "HTTP",
  "vendor": "OpenCloud",
  "version": "1.0",
  "resourceAdaptorEntities": [
    {
      "name": "${httpserver.ra.raentity}",
      "oidSuffix": "1"
    },
    {
      "name": "${httpclient.ra.raentity}",
      "oidSuffix": "2"
    },
    {
      "name": "duplicate-${httpclient.ra.raentity}",
      "oidSuffix": "3"
    }
  ]
}
Previous page Next page