Corporation Server User Manual

Dictionary
Programming Oracle Diameter Applications B-5
And then select the application's JVM from the local list. The Diameter MBeans should
be visible under the MBeans tab.
Dictionary
This section includes the following topics:
■ "Dictionary Composition"
■ "Dictionary Extension"
Dictionary Composition
When a user’s application requires using commands or AVPs that are not defined in
the default loaded application dictionary, the user can extend the dictionary to define
new commands and/or AVPs syntaxes to be used by the Diameter stack.
dictionary Element
The root or top-level element of a Diameter dictionary extension is the
<dictionary> element:
<dictionary>
.... (other elements)
</dictionary>
The <dictionary> element contains zero or more <vendor> elements and zero or
more <application> elements.
vendor Element
The <vendor> element defines a vendor by a name and associated IANA.
The <vendor> attributes are:
1. The vendor id attribute must be unique across all <vendor> element definitions
of the dictionary. The value 0 is dedicated to the base protocol which corresponds
to the syntaxes defined in [RFC-3588] and [RFC-4006].
2. The vendor name attribute is some text describing the vendor.
In Example B–4, the <vendor> element defines the vendor named "3GPP" whose
enterprise code is 10415:
Example B–4 Defining a Vendor
<dictionary>
<vendor id=
" 10415 " name= " 3GPP " >
....(other elements)
</vendor>
</dictionary>
The <vendor> element contains zero or more <returnCode> elements and zero or
more <avp> elements.
application Element
One of the ways in which the Diameter protocol can be extended is through the
addition of new applications.
The <application> element defines the new commands needed to support a new
vendor Diameter application.