I know that it normally works the other way around. People uses SNVP which pulls information from the SD db to display the relationships in graphical form.
Since you are interested in add Service to SD db, you can forget about sd_event as that will not do the job. It will have to be done via sd_export.bat or sd_export.sh and you are right, it's not a straightforward task as you will need to configure import mapping on SD's end as well.
SNVP relies on certain SD components to function so it might be possible if those components includes the client's bin folder which should have those batch or script file. If they are not there, forget it, if they are, check out the SD data exchange guide on how to use it.
Thanks Again. This is starting to get a little more clear.
I checked the SNVP - SD integration doc again, and it looks like the only real access into SD is a context sensitive OVO link to open the SD client and display the related incident or alarm.
Also, it looks like SNVP, when installed with the integration into an existing SD implementation, actually uses the SD server to store its data. The client can be anywhere, but the SNVP data seems to be saved on the SD (Application) Server.
Also, it does have access to reference much of the SD configured data, but it looks like this is only to be able to include those objects and their status into the Service Map in Service Navigator.
So, unless I'm missing something, I think it does not give the ability to actually push any service information to SD.
Thanks Again for the feedback.
Les (not as dumb as yesterday)
Why can't this thing do what I want and not what I type?