MS DAX2012_Training_Module 2 - Installation & Configuration

© Copyright IBM Corporation 2008

IBM Global Business Services

Course Title

Microsoft Dynamics AX 2012

Module 2 : Installation And Configuration


© Copyright IBM Corporation 2008AIS Multisite Engagements Leadership Workshop | IBM Internal Use | Document ID | 30-Jan-132

Overview & Planning Workflow

Course Outline

Installation Services



Module 2: Objectives

At the completion of this module you should be able to:

– Review the main concepts of Installation and Configuration in Microsoft DynamicsAX 2012.

– Discuss the system requirements of Microsoft Dynamics AX 2012.

– Install Microsoft Dynamics AX 2012.

– Describe architecture for Services and the Application Integration Framework.

– Explain the capabilities of workflow in Microsoft Dynamics AX 2012.

– Configure an approval workflow.



Module 2: Installation and Configuration : Agenda

Topic 1: Overview and Planning

Topic 2: Installation

Topic 3: Services

Topic 4: Workflow




– Objectives

– Server Setup

– Planning

– Architecture


Topic 3: Services

Topic 4: Workflow

Overview and Planning : Agenda



Objective

• Discuss the features and benefits of Microsoft Dynamics AX® 2012.

• List the servers in a Microsoft Dynamics AX installation.

• Review the requirements for domain accounts.

• Discuss the steps for planning a Microsoft Dynamics AXinstallation.

• Review the architecture for Microsoft Dynamics AX.




– Objectives

– Server Setup

– Planning

– Architecture


Topic 3: Services

Topic 4: Workflow




Server Setup

All Components

Web Server

Messaging serverAnalysis ServerDatabase Server

Domain ControllerReport ServerAOS Server

OtherCompleteMinimum

Firewall SettingsAllow outbound HTTP connections to access thedocumentations.Exclude the ports used by MSDAX and its components.Excludes the exe files used by client and debugger.

Account PermissionsDomain account is used with “Logon as Service” rights.Member of Local Administrator group.Member of dbcreator and securityadmin role is SQL ServerMember of SYSADMIN role in MSD AX, AdministratorGroup in Sharepoint and db_accessadmin role in SQL forEnterprise Portal, Business Intelligent and AIF.




– Objectives

– Server Setup

– Planning

– Architecture


Topic 3: Services

Topic 4: Workflow




Planning

System Planning Steps1. Define and document the following

o No. of transactionso No. of userso modules and features to be

implemented)o External user access requiredo Web access requiredo Projected growth rateo Number of sites

2. Evaluate and document the existinginfrastructure:

o Existing hardwareo Bandwidtho Operating systemo Databases presento Applications to integrate

3. Key decisions are as follows:o computer roles can be combinedo network load-balanced clusters too Select a backup system.

Pre-Installation Checklist1. Plan the Microsoft Dynamics AXdeployment.

2. Look for updated Microsoft DynamicsAX 2012 installation documentation on the web.

3. Review the system requirements.

4. Create domain accounts for Windowsservices to run as.

5. Copy the installation files to the shareddirectory.

6. Ensure that your domain account has theappropriate rights to perform the installation.

7. Verify you meet the prerequisites.




– Objectives

– Server Setup

– Planning

– Architecture


Topic 3: Services

Topic 4: Workflow




Microsoft Dynamics AX System Architecture

AIS Multisite Engagements Leadership Workshop | IBM Internal Use | Document ID | 30-Jan-1312




– Objectives

– Server Setup

– Planning

– Architecture


Topic 3: Services

Topic 4: Workflow





– Objectives

– Server Setup

– Planning

– Architecture


Topic 3: Services

Topic 4: Workflow







– Objective

– Install an environment

– Perform a single computer installation

Topic 3: Services

Topic 4: Workflow



Objective

• Review the features of the setup utility.

• Install the database, application object server, application files, and the client.

• Perform a single computer installation.



Installation : Agenda



– Objective



Topic 3: Services

Topic 4: Workflow



Setup Utility

Installation of Microsoft Dynamics AX 2012 starts with running Setup.exe file. Ithas following utilities.

Automatic update installer.Prerequisite validation

Stand-alone prerequisite validation utility Consolidated prerequisite verification Automatic prerequisite configuration

Post-Installation Configuration



Install an environment

NEW

ENVIRONMENT

Database installation

AOS Installation

Client Installation

Database Installation Prerequisite1. Prerequisite validation2. Domain account for SQL3. Permission checking

Install DatabaseDemo

AOS Installation Prerequisite1. Prerequisite validation2. Permission checking3. Service account for AOS

Install AOSDemo

Components

1) Interface2) Configuration Utility

Install ClientDemo



Installation : Agenda



– Objective



Topic 3: Services

Topic 4: Workflow



Perform single computer installation

1. Prerequisite Validation2. Single computer installation Demo






Topic 3: Services

– Objectives

– Services overview

– Integration and Planning

– Lab

– Troubleshoot and monitor services

– Demo

Topic 4: Workflow



Objective

• Review how documents are exchanged with the Application IntegrationFramework and discuss the system services.

• Describe the integration features and how to plan for the integration.

• Install web services on Internet Information Services (IIS).

• Review tools for troubleshooting and monitoring services.



Services : Agenda



Topic 3: Services

– Objectives



– Lab


– Demo

Topic 4: Workflow



Services Overview

The AOS is the Windows Communication Foundation (WCF) Service hostsfor Microsoft Dynamics AX 2012 services exposed to users andapplications on an intranet.

To consume services over the Internet host services on Internet InformationServices (IIS). IIS-hosted services use the WCF message routingservice. Microsoft Dynamics AX deploys the Web Services DescriptionLanguage (WSDL)-based service in a subfolder in the virtual directorythat is associated with the web site.

IIS routes all service requests (those originating on the Internet or theintranet) to the AOS. Then the AOS returns a response to the serviceconsumer through IIS. Exchanges configured to use web services areprocessed synchronously and do not use the Microsoft Dynamics AXqueues.

Types of Service

Document services: They are query-based services, andexchange data with external systems by sending and receivingXML documents. These documents represent business entities,such as customers, vendors, or sales orders.

Custom services: Used by developers to expose any X++ logic,such as X++ classes and their members, through a serviceinterface.

System services: Provided by Microsoft Dynamics AX. Systemservices include the Query service, the Metadata service, and theUser Session service. System services cannot be customized andthey are not mapped to any query or X++ code.

The inbound and outbound exchanges can be categorized as follows:

Send Data

Send data in response to requests

Receive & create data



Services : Agenda



Topic 3: Services

– Objectives



– Lab


– Demo

Topic 4: Workflow



Integration and Planning

Services has the following features - Supports XML using AIF and NON-XML file formats (csv or fixed width file) using transform pipeline.The transforms types supported are Extensible Stylesheet Language Transformations (XSLT) and .NETassemblies. Out-of-the-box integration "templates" for banking scenarios. Support for large messages import. Support for flexible error handling on large imports (Rollback, halt, and continue paradigms supportedin error).

The integration design decisions works with two primary categories – Data and Configuration.planning the integration process involves common steps –

1. Identify the document exchange needs. Once the documents are indentified the additional informationabout the data needs to be defined. These information can be -

a. What data is to be exchanged.b. Any business logic related to that data.c. The external systems with which data is to be exchanged.d. The conditions under which data is sent from or received by Microsoft Dynamics AX.

2. The hardware and software requirements for AIF needs to be compared with existing environment andany new hardware or software must be identified.3. Installation and configuration of the hardware and software for AIF.4. The document exchange programs has to be done along with any customization to the AIF documentsor any new documents creation to meet the requirements of the business users.5. Monitoring the document exchanges and troubleshoot any errors that are generated.



Services : Agenda



Topic 3: Services

– Objectives



– Lab


– Demo

Topic 4: Workflow



Lab

Setup Inbound and Outbound Port,Create a document service ,Configure

processing message



Services : Agenda



Topic 3: Services

– Objectives



– Lab


– Demo

Topic 4: Workflow



Troubleshooting and monitoring services

Document exchange maintenance and managing involve the following steps –

Monitor traffic and view document history as documents pass through theframework.

Clear and review messages in the queues for adapter-based exchanges. View the exception logs when problems arise. Edit and resubmit messages that contain formatting errors. Stop and start the batch services when necessary.

For both adapter-based and web services-based exchanges, information about messagesand document history is organized by service operation for each port. Thisinformation can be logged in parameter while configuring the troubleshootingoptions.

The information can be accessed from the following forms – Document history form Queue manager Exceptions

Services can also be debug from Visual Studio Debugger



Services : Agenda



Topic 3: Services

– Objectives



– Lab


– Demo

Topic 4: Workflow



Hands On

Demo






Topic 3: Services

Topic 4: Workflow

– Objective

– Architecture

– Create a workflow

– Graphical workflow editor

– Lab



Objective

• Discuss the architecture of workflow.

• Create a workflow and configure basic settings.

• Describe the features and use of the workflow editor.

• Configure an approval element.



Workflow : Agenda



Topic 3: Services

Topic 4: Workflow

– Objective

– Architecture



– Lab



Architecture

Workflow infrastructure consists of 2 components-

X++ workflow runtime

– Workflow runtime ApplicationProgramming Interface (API)

– A messaging batch job

– A message queue

Managed workflow runtime

– Windows workflow foundation (WWF)

– Microsoft Dynamics AX extensions

Both the X++ workflow and the managed workflowruntimes are hosted on the AOS. The workflowinfrastructure uses batch processing on theAOS and .NET Interop to integrate bothsubsystems and pass messages from onesubsystem to another. The X++ code executedin the batch processor is compiled to .NET CIL.The batch processing runs in the .NET commonlanguage runtime (CLR).



Workflow : Agenda



Topic 3: Services

Topic 4: Workflow

– Objective

– Architecture



– Lab



Create a workflow

DescriptionManaged byAction

This same messaging pattern is repeated as necessary throughout the life cycle of theworkflow instance.

BothWorkflowlifecycle

The messaging batch job reads the “workflow started” message from the message queueand invokes the application event handler to process a “workflow started” event. The batchjob then posts an acknowledgement message that the event was processed.

X++

Workflow

Runtime

Workflowstartedevent

.NET Interop from X++ receives the message and starts a new workflow instance throughWindows Workflow Foundation. This workflow instance performs a callback function to theX++ workflow runtime API through .NET Interop to X++ CIL and posts a message that theworkflow has started. After posting the message, the managed workflow runtime saves theidle workflow instance to the Microsoft Dynamics AX database. Runtime then removes itfrom memory. When the managed workflow runtime receives another message from theX++ workflow runtime for this workflow instance, it restores the workflow instance tomemory and resumes it.

Managed

Workflow

Runtime

Workflowinstancestarts

X++ code to activate a workflow instance by calling the workflow runtime API. Theworkflow runtime API posts a message to the message queue. The messaging batch jobreads the message and sends a workflow activation request to the managed workflowruntime.

X++

Workflow

Runtime

Usersubmits adocumentforapproval



Workflow : Agenda



Topic 3: Services

Topic 4: Workflow

– Objective

– Architecture



– Lab



Graphical workflow editor

The workflow editor is a graphicalinterface you can use to createMicrosoft Dynamics AX workflows byarranging workflow elements on adesign surface.

The workflow editor automatically saves aworkflow while working on it withoutcreating a new workflow version.However, while closing a workflow inthe workflow editor gives option to saveit and create a new version or to cancelit and discard the changes. If theworkflow is valid and contains no errorsor warnings then it can be activated.Documents can be submitted to theactive version of the workflow only.



Workflow : Agenda



Topic 3: Services

Topic 4: Workflow

– Objective

– Architecture



– Lab



Lab

Configure an Approval on a Workflow



Workflow : Agenda



Topic 3: Services

Topic 4: Workflow

– Objective

– Architecture



– Lab



Workflow : Agenda



Topic 3: Services

Topic 4: Workflow

– Objective

– Architecture



– Lab



Module 2 : Installation And Configuration: Summary

Discussed the features, benefits and architecture of MicrosoftDynamics AX® 2012.

Installed the database, application object server, applicationfiles, and the client.

Discussed how documents are exchanged with the ApplicationIntegration Framework and discussed the system services.

Discussed the architecture of workflow.