Book Image

Microsoft Dynamics AX 2012 Services

Book Image

Microsoft Dynamics AX 2012 Services

Overview of this book

Because an ERP system like Microsoft Dynamics AX 2012 plays a central role in an organization, there will always be the need to integrate it with other applications. In many cases, services are the preferred way of doing this, and Microsoft Dynamics AX 2012 is now more flexible than ever when it comes to the creation and use of these services. Understanding these services will help you identify where they can be used, and do so effectively."Microsoft Dynamics AX 2012 Services" is a hands-on guide that provides you with all the knowledge you will need to implement services with Microsoft Dynamics AX 2012. The step-by-step examples will walk you through many of the tasks that you need to perform frequently when creating and using services."Microsoft Dynamics AX 2012 Services" provides detailed and practical examples for creating and using services that will make it a resource you will consult many times during your implementationsThis book helps you to identify situations where services can be used for your implementations. By providing step-by-step instructions for many of the common tasks, you will gain practical know-how on to get the job done.Easy to follow instructions are provided for all types of services you will encounter. You will learn how to create document services using the AIF Document Service Wizard and how to use X++ to create custom services. You will also learn how to deploy services and web services and how you can consume them in both X++ and .NET. The services are also put to use in the SysOperation framework, which uses services to run business logic and is the new way to create batch processes in Microsoft Dynamics AX 2012.
Table of Contents (14 chapters)

SysOperation versus RunBaseBatch


Before going into the details on using the new SysOperation framework, let's put it next to the RunBaseBatch framework to find out what the main differences between the two of them are.

The first difference is that the SysOperation framework uses WCF services to run the processes and handle communication between the client and server. One of the advantages is that the client/server communication is less chatty so the connection doesn't need to be kept alive as opposed to the RPC communication of the RunBaseBatch framework.

The second big difference between the two is how they implement the Model-View-Controller (MVC) pattern. The RunBaseBatch framework uses one class that extends from the RunBaseBatch class. All of the components contained in the MVC pattern are contained within the same class.

  • The model is identified by the class members.

  • The view is handled by the dialog, putToDialog, and getFromDialog methods. These methods present a dialog to the user and...