Integration overview with Dynamics Ax 2012

1. Integration With
Dynamics Ax
2012
Presenter: Ali Raza Zaidi (Dynamics
AX MVP )

3. What is ERP
• Enterprise resource planning (ERP) is a business management
software—usually a suite of integrated applications—that a
company can use to collect, store, manage and interpret data from
many business activities, including:
• Product planning, cost and development
• Manufacturing or service delivery
• Marketing and sales
• Inventory management
• Shipping and payment
• Financials

5. Business Success Demands Change

6. Dynamics AX 2012 Value Proposition
Powerful Agile
Simple
Pervasive Interoperability
Powerfully Simple

7. Powerful
Streamline essential service processes
with project-specific capabilities
Scale the firm to each new opportunity
with a global-by-design solution
Drive time-to-productivity for professionals
with RoleTailored user experiences
Deliver more value faster with a powerful unified solution

8. Agile
Adapt to changing process and regulatory requirements with
model-driven methods
Respond precisely to client needs with integrated relationship
management
Support timely decision-making with rich financial and
operational insights
Increase opportunities and reduce risk with an agile solution

9. Simple
Easy to learn and use across the service chain
Accelerate user onboarding and adoption
with a familiar, intuitive user experience
Connect easily with service teams, partners and clients
through integrated collaboration capabilities
Extend existing business processes and systems
with pervasive interoperability
Easy-to-use software drives adoption and lowers costs

10. Dynamics Ax 2012 Client Navigation Overview

11. Business Workloads

12. Enterprise Architecture
Enterprise
Application
Enterprise
Infrastructure
MorphX
App Server(s)
AOS Services
File system MSMQ
WCF Services

13. Microsoft Confidential
Microsoft Platform Interoperability:

14. Servers & Tools:
• Workflow enhancements incl. graphical workflow editor,
Work item queues
• Services (Sites, Payment, and Commerce)
• AIF enhancements (90 documents, non-XML file format)
• Role-based security and segregation of duties
• Pluggable User authentication
• New programmability Concepts (models)
• Upgrade framework enhancements
• Integrated Development Environment (IDE)
• Visual Studio Tools for Microsoft Dynamics AX 2012
• Simplified Installation experience
• New Help System

15. Microsoft Dynamics AX | At-a-Glance

16. Market Share

17. Implementation Cost
Average Cost to maintain and implement the ERP Tool
• SAP : $16 M
• Oracle : $12 M
• Microsoft :$3 M
• Others : $3.5 M
http://go.panorama-consulting.
com/rs/panoramaconsulting/images/Clash-of-the-
Titans-2014.pdf

18. Average implementation Time Duration :
• SAP : 18.5 Months
• Oracle : 22.5 Months
• Microsoft : 12.5 Months
• Others : 11 months
Reference :http://go.panorama-consulting.
com/rs/panoramaconsulting/images/Clash-of-the-Titans-
2014.pdf

19. Dynamics Ax Infrastructure
• Uses of the system: The components and modules of Microsoft Dynamics
AX that you plan to deploy
• The number of transactions over a period of time, and the total number
of transactions during peak business hours
• The number of active or concurrent users over a period of time, and the
total number of active or concurrent users during peak business hours
• The external user access that is required
• The web access that is required
• The required availability
• The projected growth rate
• The number of sites and the number of users who connect through a
wide area network (WAN)

20. Bandwidth

21. Basic Hardware Requirement

22. Processor and RAM requirements

25. Integration Scenario

26. Different Applications written in different language.
Applications can communicate independent to their technology.
Implementing the standards and protocols to work independent
of their technology. Services should be abstract, So people use
them without understanding of its internal working and how
data is store.
Self describing Meta data, In Dynamics Ax it is using Web Service
Description Language (WSDL).

27. Service-Oriented Architecture (SOA)
• “SOA is the architectural style that supports loosely coupled
services to enable business flexibility in an interoperable,
technology agnostic manner. SOA consists of a composite set of
business-aligned services that support a flexible and dynamically
re-configurable end-to-end business process realization using
interface-based service descriptions.”
• Evolution in 80 everything is OOPs, 90s everything based on
Component, 2000 and onward everything based on Service
Oriented.

28. Expose-Compose-Consume
Consume
Service Consumption
Compose
Service Composition
Devices
Portal and People
Data Mainframe Trading
Partners
LOB
Expose
Service Enablement
OBA Desktop

29. Windows communication foundation:
WCF is a programming Platform and run time system for
building, running and deploying the network distributed services.
It is the latest Service oriented technology. Interoperability is the
fundamental characteristics of WCF. It has web service, .Net
Remoting, MSMQ and COM+ features. It combines all these
things into a single umbrella. That means it provides a common
platform for all .Net communication.

30. What is ABC of WCF

31. Address
• In WCF, every service is associated with a unique address. The
address provides two important elements: the location of the
service and the transport protocol or transport schema used to
communicate with the service.
• http://localhost:8001
• http://localhost:8001/firstservice
• net.tcp://localhost:8002/firstservice
• net.pipe://localhost/piped
• net.msmq://localhost/firstservice

32. Bindings:
• Specifies how a service is accessible. In other words: how the two
parties will communicate in terms of transport (HTTP, TCP,
NamedPipe, Peer2Peer and MSMQ), encoding (text, binary etc.) and
protocols (like transactional support or reliable messaging).
• how the WCF Service Communicates with Request and Response
• Basic binding
• TCP binding
• Web Service (WS) binding
• MSMQ binding

33. Contract
Contracts are used to define what can be communicated. The
following are the three types of contracts:
• Service contracts: These describe the service functionality that is
exposed to external systems
• Operation contracts: These define the actual operations that will
be
available on the service
• Data contracts: These are used to shape the data that will be
exchanged by the operations of the service

34. System Architecture

35. AIF Architecture

36. AIF – Key Concepts
Axd<Document>
Axd<Document>
Axd<Document>
AIF Services Channel Endpoint
Document
Classes
Microsoft Dynamics AX
Endpoint
AOS
AIF
WS Adapter
DB

37. AIF – Key Concepts
Axd<Document>
Axd<Document>
Axd<Document>
AIF Services Channel Endpoint
Document
Classes
Microsoft Dynamics AX
Endpoint
AOS
AIF
WS Adapter
DB
XML Document
11010110011
1101
Entity Key

38. Types of Services In Dynamics Ax
There are many Services provided by Microsoft Dynamics AX 2012 to
work with third part components. These Dynamics AX 2012 Services
are actually programmable artifacts. Such Services are given in
normal X++ code, so that developers can easily modify them
depending on the specific needs of their business.
• Given below are the Services that are currently available in
Microsoft Dynamics AX 2012.
• Document Services
• Custom Services

39. Document Service
• This was introduced in Microsoft Dynamics AX 4.0. It enables the user to
exchange data between internal and external systems via XML
documents. Document Services are generated from a query that models
the business entity. For example, a customer query will run the
Document Service Generation Wizard to create the Service artifacts.
• Document Services include logic to handle the details of how a query will
be serialized or de-serialized from the XML that is sent across a network.
For synchronization of Document Services, there are two new entities
introduced in Dynamics AX.
• Developers need to extend these functions to enable their own scenario.

40. Custom Service
This Service enables developers to expose any logic written in x++
through a service interface. The support for Custom Services was
introduced in Dynamics AX 2009, but it was limited to some specific
data types. In Microsoft Dynamics AX 2012 with the integration of
Windows Communication Foundation (WCF), attributes can be set on
the Data Contract class to make them serialize and de-serialize
across the network connection.

41. Service Attributes
• SysEntryPointAttribute
• DataContractAttribute
• DataMemberAttribute
• AifCollectionTypeAttribute

43. Where to start…..?
Reduce the time and cost of custom development by using and adapting the
built-in services and functionality of Microsoft Dynamics AX.
For increased agility, create reusable components based on the core Microsoft
Dynamics AX functional types.
Data quality is essential to an effective ERP solution. Spend the time to define
data structures before starting to build a solution.
Focusing on the right integrations across the application portfolio increases
business value, drives visibility and effectiveness, and decreases operational
cost structures

44. Microsft’s guiding principles 
 Microsoft Dynamics AX is an ERP application
 DON’T integrate directly at the SQL-level
 Always use Dynamics AX runtime for integrations