(Doc ID 1231053.1)
Last updated on DECEMBER 03, 2010
Applies to:Oracle Communications Network Discovery - Version: 5.1.0 to 5.1.0 - Release: 5.1 to 5.1
Information in this document applies to any platform.
There are occasions where the data collected from a hardware device might contain data which is not formatted as desired or inoccasionally, incorrect. These situations are impossible to predict, but Oracle Communications Network Discovery is architected in anticipation of these eventualities, and can easily be modified to allow the user control over these situations.
In this specific case, the T2000 device is the device in question. On a discovery, it returns a values for name and nativeEMSName. The name attribute contains a key value, which would require a lookup table to map back to at actual device name. However, the nativeEMSName value is exactly what is needed. This example shows how to replace the name attribute value with the nativeEMSName attribute. The solution involves modifications to the code running at the Modeler EP.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document