Sorry but at this point, the easiest thing to do is to reinstall the EDB node from the .ova.

Okay, you must have an older release than I was using. Do you know if the install was done via an .ova or a .iso?
If it was done from a .iso, you should have a directory /opt/ASMinstall. The setup_ISM.sh script should be there.
Try it from there.

It sounds like the ISM bus did not get setup correctly. Please login to the Breeze node as root and run the command /opt/Avaya/aus/bin/setup_ISM.sh. After that completes then run the command "restart WebSphere". Hopefully this will clear your problem.

Your snap-in can define service attributes that can be administered on the SMGR at the Global, Cluster and Service Profile Levels.
The values can then be read from your snap-in. Please refer to the Service Attribute section of the Snap-in Developer's Guide.
It shows you how to define them in your properties.xml and there is a code example that shows how to read the values in your snap-in.

Attribute names are scoped by Snap-in name. So Snap-in A and Snap-in B can both define an attribute named "timezone" for example.
Different versions of the same snap-in must define the same attribute exactly the same. That is if A-1.0 defines "timezone" as a string with default "EST", then A-2.0 can not define "timezone" as an encrypted string with default "MDT".