Once you’ve completed, you can create the SAP MA which to do so, you need to input the XML configuration file that is created by the ECT. You should then be able to see the entire attribute list with all the normal functions of any other management agent.
How do my previous posts relate to where we are now; well here is how the MA works.
- Building the ERP MA configuration file using the ECT; the configuration of the MA is performed by discovering the SAP environment using the SAP connector for Microsoft .NET 2.0 and generating an XML. This essentially discovers all the BAPIs and stores them in a local cache file.
- Configuration UI communicates with SAP to discover the BAPIs and other configuration for display.
- XML configuration, proxy assemblies and schema definition file generated by the UI. You are building out your connector space.
- Creation of the MA happens in MIIS and consumes schema file which MIIS uses to synchronize with SAP.
- ERP MA SAP assembly consumes XML configuration and proxy assemblies at run time provides wrapper to RFC calls directly to SAP Server
The diagram below (provided from the CHM) details what happens under the covers.
Now that you understand the process for communication, you can now proceed to determine what to do with the data you import/export. Key things to understand when using the Microsoft ERP MA are the following:
***Understand the process of Alias and Alias-referencing. That is the core of how the MA works.
No comments:
Post a Comment