Here is how ids should match up:

com.avaya.sce.core.pluggableConnector/connectorId
should match
com.avaya.sce.callflow.ui.dataConnectorUI/connectorId

com.avaya.ade.common.core.avResourceType/id
should match
com.avaya.sce.callflow.ui.dataConnectorUI/id

So mainly there are 2 different ids for the plugin - one is the connctor id that identifies the connector plugin overall, and the other is the resource or type id that the flow item carries to identify any underline resource it references.
Since you don't have any resource for the node item to reference, you really don't need to implement the avResourceType extension.

If you can't get it to work for the search, you can send me the project and I can take a look. Our code may not be bullet proof since the search feature has only been used for internally developed plugins and not tested for external use. But I think we can make it work for you.

I need help... LOL I've sent the source code to your email. Thank you *very* much!

Michael