Need clarification regarding XMA

Hi,
am writing an XMA for SCCM. To export data to SCCM, I would like to go for 
Call-Based Extension by implementing IMAExtensibleCallExport. How can I 
import data from SCCM to connector space. I can only see 
IMAEXtensibleFileImport, but my data source is not a XML file. 

Any suggestion would be appreciated.

Thanks,

Ram wrote:
> Hi,
> am writing an XMA for SCCM. To export data to SCCM, I would like to go for

> Call-Based Extension by implementing IMAExtensibleCallExport. How can I 
> import data from SCCM to connector space. I can only see 
> IMAEXtensibleFileImport, but my data source is not a XML file. 

This is a method in which You have to create Your inport file.
So when You will execute MA Import profile this method will get called 
and it is your responsibility here to contact your data source, read all 
the data and generate import file which ILM will consume.

Basically XMA is acting like file MA on import operation, however you 
are in control of creating method which will generate this file.

-- 
Tomasz Onyszko
http://www.w2k.pl/ - (PL)

Hello Tomasx,
Thank you very much for the response. If I understand it correctly, here are 
the steps that I would be doing to complete SCCM XMA development.
1) Implement IMAExtensibleCallExport interface methods, which are used 
during Export processs into external data store(SCCM in our schenario).
2) Implement IMAEXtensibleFileImport interface methods to obtain data from 
external data store and prepare xml file that is consumed by ILM.

Thanks,
Ramesh V
"Tomasz Onyszko" wrote:

> Ram wrote:
> > Hi,
> > am writing an XMA for SCCM. To export data to SCCM, I would like to go
for 
> > Call-Based Extension by implementing IMAExtensibleCallExport. How can
I 
> > import data from SCCM to connector space. I can only see 
> > IMAEXtensibleFileImport, but my data source is not a XML file. 
> 
> This is a method in which You have to create Your inport file.
> So when You will execute MA Import profile this method will get called 
> and it is your responsibility here to contact your data source, read all 
> the data and generate import file which ILM will consume.
> 
> Basically XMA is acting like file MA on import operation, however you 
> are in control of creating method which will generate this file.
> 
> -- 
> Tomasz Onyszko
> http://www.w2k.pl/ - (PL)
> http://blogs.dirteam.com/blogs/tomek/ - (EN)

Ram wrote:
> Hello Tomasx,
> Thank you very much for the response. If I understand it correctly, here
are 
> the steps that I would be doing to complete SCCM XMA development.
> 1) Implement IMAExtensibleCallExport interface methods, which are used 
> during Export processs into external data store(SCCM in our schenario).
> 2) Implement IMAEXtensibleFileImport interface methods to obtain data from

> external data store and prepare xml file that is consumed by ILM.

Correct. Just to clarify - this can be any of file formats which are 
supported by ILM. Of course it can be XML as well

-- 
Tomasz Onyszko
http://www.w2k.pl/ - (PL)

Hi Tomasz,
In all online documentations there was an assumption that only object exist 
and schema file contains only one object. For ex: In Developing call-based 
export the schema was 

objectclass, delta, anchor-attribute, name, email

In File based import mdsn documentation also the schema was the same. In our 
schenario, I have to export two different object typess and import two 
different object types. That means I should able to define two objects in 
schema file. In creating management for ECMA also was an option to feed in 
template file and asks the user to select the delimiter. How can define 
multiple objects with corresponding anchor tags to them.

Thanks,
Ramesh V

"Tomasz Onyszko" wrote:

> Ram wrote:
> > Hello Tomasx,
> > Thank you very much for the response. If I understand it correctly,
here are 
> > the steps that I would be doing to complete SCCM XMA development.
> > 1) Implement IMAExtensibleCallExport interface methods, which are used

> > during Export processs into external data store(SCCM in our
schenario).
> > 2) Implement IMAEXtensibleFileImport interface methods to obtain data
from 
> > external data store and prepare xml file that is consumed by ILM.
> 
> Correct. Just to clarify - this can be any of file formats which are 
> supported by ILM. Of course it can be XML as well
> 
> -- 
> Tomasz Onyszko
> http://www.w2k.pl/ - (PL)
> http://blogs.dirteam.com/blogs/tomek/ - (EN)