SAP MII is gaining importance as an integration and analytic platform rapidly in the manufacturing domain. Being an acquired product from outside SAP, it has some specific characteristics and features on its platform, which are quite different from other SAP products and solutions and typical of its own. Few examples are the proprietary graphical business logic modeling engine, configuration-based connectivity framework for manufacturing systems, messaging and data-buffering options, etc. While implementing SAP MII for customers one has to know and take care of these aspects and features and need to leverage them methodically to deliver effective solutions.
In this session at SAP TechEd Bangalore on 2nd December, 2010 (4:30-5:30 p.m.) I shall talk about the different architectural scenarios and decisions while implementing SAP MII and how we can leverage its standard features to address the gaps. Specifically I shall cover the following points in the session:
– SAP MII Deployment Architecture
– SAP MII Data Persistency Architecture
– SAP MII Integration and Messaging Architecture
– SAP MII User Interface Options and Architecture
– SAP MII Security Architecture
– Methods and Tools to Ease SAP MII Implementation
So if you are a SAP MII developer, technical lead or an architect working on SAP MII implementation or solution development, you may be able to find answers to lots of questions and challenges which you may have faced earlier while implementing SAP MII and can get ideas which you can implement in future projects.
Do let me know if you are planning to attend the session, via Twitter (@buddydip) or commenting on this blog. Also mention your expectation from the session which I shall try to address to my best.