If you use the CMDB-specific APIs, I am pretty sure (but not 100%) that you won't have any visibility of the non-core attributes that are in AST:Attributes.
However, if there are web services available for the Asset side of things, you could try that option, since if the WS uses an Asset view, then it will contain the join information from both the base asset form AND AST:Attributes.
The only issue is that the AST views don't have ALL the core attributes (kind of the reverse problem), but they may have enough!
Just a thought
Thanks Cary for your sharing your thoughts!
I'm also pretty sure that CMDB-specific APIs won't get it, but it would be nice to find some official documentation giving answers to this simple question and confirming our suspects.
Documentation talks about instances (how to query them?), retrieving attributes (which ones?)...
By the way, I don't think HP-DDM would be capable to deal with AST-Specific WS. One important think that HP-DDM will have to do is map what the query returns: instances belonging to different BMC Atrium CMDB classes (and not to information belonging to AST forms/joins) should be mapped against HP-BSM CMDB classes and also on AST, as you exposes, there will be sure problems with non existent CORE attributes...
CMDB WS is unable to fetch any AST:Attributes, those exist only in the AST world and they make sense only if you are looking into data from the AST:Class forms, which are joins of CMDB forms and AST:Attributes. They also only make sense in BMC.ASSET dataset, while CMDB WS are usable in all your datasets.
There are ITSM WebServices though, and also the new RESTAPI that can access any form to fetch instances.
I am not sure if this answer your question but it may be helpful.
cmdbdriver is a API program developed by BMC using atrium APIs.
So when you execute gi (get instance) command in cmdbdriver with all the valid parameters, It will return all the attributes. (Including custom attributes as well). You need to pass valid instance id.
Please refer below image: