ax2012_enus_upg_01

Chapter 1: Overview

1-1

CHAPTER 1: OVERVIEW Objectives

The objectives are:

• Introduce the Source-to-target framework. • Describe the Preprocessing framework. • Discuss key features of Microsoft Dynamics® AX 2012 upgrade. • Introduce available resources for upgrading to Microsoft Dynamics

AX 2012.

Introduction Microsoft Dynamics AX 2012 provides a new approach to upgrade that significantly reduces downtime during the upgrade process. A shorter downtime has less effect on your business operations. Therefore, helping to reduce the total upgrade cost. The major features of this new approach include the following:

• Efficient handling of the large scale data model changes and normalization between Microsoft Dynamics AX 2009 and Microsoft Dynamics AX 2012.

• Preprocessing on source system. Processing is performed on the source system in either Microsoft Dynamics AX 4.0 or Microsoft Dynamics AX 2009, to reduce system downtime.

• Parallel processing for data copy, running code to upgrade data (postsynchronize), and synchronize. o Reduce time that is spent in system downtime. o Intelligent task prioritization for reducing downtime.

• Improve the upgrade's scalability. • Let administrators identify upgrade issues immediately by using the

Upgrade readiness check form.

Microsoft Official Training Materials for Microsoft Dynamics®

Your use of this content is subject to your current services agreement

Data Upgrade and Code Upgrade to Microsoft Dynamics® AX 2012

1-2

Scenario

Fabrikam is a fictional mid-market furniture company that currently uses Microsoft Dynamics AX 4.0 to run its business. The company wants to upgrade to Microsoft Dynamics AX 2012 to take advantage of the many new and improved features.

Fabrikam has created several customizations to enable the business to operate more efficiently. The company wants to move from its customizations to Microsoft Dynamics AX 2012 features where it is possible, and where it cannot do this, these customizations must be migrated to Microsoft Dynamics AX 2012.

Recent growth has increased transaction volume at Fabrikam and reduced the company's tolerance for downtime. Fabrikam's directors expect Microsoft Dynamics AX 2012 to be ready for new transactions within 36 hours of Microsoft Dynamics AX 4.0 being shut down.

Your job is to help Fabrikam prepare for and run an upgrade from Microsoft Dynamics AX 4.0 to Microsoft Dynamics AX 2012 which includes the following tasks:

• Planning • Code upgrade • Data upgrade • Running the upgrade.

Source-to-Target Framework Microsoft Dynamics AX 2012 uses a Source-to-target upgrade model that enables Independent Software Vendors (ISV) and upgrade developers to upgrade with minimal downtime.



Chapter 1: Overview

1-3

Earlier Framework

In ealier versions of Microsoft Dynamics AX, all upgrade tasks are performed on a single production system. A large part of the upgrade process was spent in single-user mode, with the system offline for regular users. Issues that arose during upgrade had to be resolved on the spot before usual business operations could resume.

FIGURE 1.1 EARLIER FRAMEWORK

Source-to-Target Framework

With Microsoft Dynamics AX 2012, you can preprocess your business data on the live source system (running Microsoft Dynamics AX 4.0 or Microsoft Dynamics AX 2009), free from time pressure and without halting regular operations. Meanwhile, you can build a separate, offline target system (running Microsoft Dynamics AX 2012).




1-4

When preprocessing on the source system is complete and the target system is ready, you can enter single-user mode on the source system, bulk copy your data into the target system, run postsynchronization upgrade scripts, and perform testing. When these steps are finished, the target system can go live.

FIGURE 1.2 SOURCE-TO-TARGET FRAMEWORK

Parallel Processing

The bulk copy of data from the source system to the target system is performed in parallel with running synchronization steps and post-synchronization steps on the data. Moving these steps in parallel will transparently merge what were formerly three steps into one single step, minimizing total system downtime for upgrade.

NOTE: Synchronization is broken into two parts. One part is performed to create the tables and their clustered indexes, default constraints, and views. The other part runs after the bulk copy creates non-clustered indexes and constraints.

Supported Upgrade Paths

You can upgrade to Microsoft Dynamics AX 2012 directly from either Microsoft Dynamics AX 4.0 service pack 2 or Microsoft Dynamics AX 2009 service pack 1. If you have a version that is earlier than Microsoft Dynamics AX 4.0, you must upgrade to Microsoft Dynamics AX 2009 before you can upgrade to Microsoft Dynamics AX 2012.

For information about supported system configurations, use the following links:

• System requirements for Microsoft Dynamics AX 4.0 (http://go.microsoft.com/fwlink/?LinkId=186400)

• Microsoft Dynamics AX 2009 System Requirements (http://go.microsoft.com/fwlink/?LinkId=244185)



Chapter 1: Overview

1-5

SQL Server Support

You cannot use an Oracle database together with Microsoft Dynamics AX 2012. If you are upgrading from an installation of Microsoft Dynamics AX that uses an Oracle database, you must first migrate your data to a Microsoft SQL Server database, and then upgrade to Microsoft Dynamics AX 2012.

Use the Oracle to Microsoft SQL Server Data Migration Assistant for Microsoft Dynamics AX tool to migrate your data to a SQL Server database. You can download the tool and the Oracle to Microsoft SQL Server Data Migration Assistant for Microsoft Dynamics AX Installation Guide from Customer Source (http://go.microsoft.com/fwlink/?LinkId=244189).

Preprocessing Framework The Preprocessing framework is a new upgrade approach that enables data upgrade on a live source Microsoft Dynamics AX system minimizing downtime.

Preprocessing

Preprocessing your data will limit the time that is spent with the system down. During preprocessing, scripts data is processed and then staged in a table with similar data structures to Microsoft Dynamics AX 2012. This makes the final copy of data more efficient.

To accommodate the fact that preprocessing is performed in a live environment preprocessing scripts are run one time, and then delta scripts are run to capture the changes between the last preprocessing script run and the current dataset. After the source system enters single-user mode, no new transactions can be entered, and a final delta script run is performed to capture the last changes to the system.

Preprocessing transformations—such as changing a string to a base enumeration—occur in staging tables (non-production tables in the production database) and no changes are made to the production table. Changes by preprocessing scripts are designed to have the least effect on the production system with an ability to manage the resource usage for the upgrade process. This is known as upgrade throttling.

Delta Scripts

Similar to the live preprocessing scripts, the delta preprocessing scripts run in the Microsoft Dynamics AX source system, while the Microsoft Dynamics AX source system is live and being used for production. To optimize performance, you can pause some or all of the delta scripts by using the Manage running tasks form.

NOTE: Some delta preprocessing scripts cannot be paused. These scripts appear in the grid with the Task state "The task does not support pausing".




1-6

You can run the delta preprocessing scripts multiple times until you are ready to enter single-user mode. To minimize downtime, make sure that you run the delta preprocessing scripts immediately before you enter single-user mode.

Upgrade Throttling

With upgrade throttling users can pause and resume the upgrade on the live system and decide how many resources are allocated to the upgrade process.

FIGURE 1.3 UPGRADE THROTTLING

Upgrade State Transfer Tool

In a Source-to-target upgrade, the most labor-intensive phase is data preprocessing. Assuming that you follow the best practice of performing an upgrade first on a non-production system, you will invest significant time completing data preprocessing on a test source system. The upgrade state transfer tool lets you capture that effort by transferring preprocessed data from a test system to your production system.

Upgrade Key Features In addition to the Source-to-target framework, Microsoft Dynamics AX 2012 upgrade includes several features that help ensure a simple and successful upgrade.

• Checklists • Upgrade readiness check • Attribute framework • Upgrade cockpit • Row count validation



Chapter 1: Overview

1-7

Checklists

The Microsoft Dynamics AX 2012 data upgrade framework, includes several checklists and related forms to help organize upgrade tasks on the source and target systems.

• Source checklist o Preprocessing upgrade checklist: tasks that prepare data on the

source system for Microsoft Dynamics AX 2012 database schema.

• Target checklists o AOD code upgrade checklist: tasks that are involved in

migrating metadata in AOD files to the Microsoft Dynamics AX 2012 model architecture

o Model code upgrade checklist: tasks that are involved in migrating metadata in models to Microsoft Dynamics AX 2012.




1-8

o Data upgrade checklist: tasks that are involved in upgrading data on the Microsoft Dynamics AX 2012 target system.

FIGURE 1.4 PREPROCESSING UPGRADE CHECKLIST

Upgrade Readiness Check

You can check upgrade readiness before you start to upgrade data on the Microsoft Dynamics AX source system. The readiness check produces a report that identifies issues that could potentially affect data upgrade. Checks include identifying data that could cause failure of the data upgrade scripts and identifying scenarios that will need additional planning before the upgrade. No change to data is made during the checks.



Chapter 1: Overview

1-9

The upgrade readiness check is optional, but recommended. By running the readiness check and fixing the data issues that the readiness checklists, you will reduce the number of times that you must run the live or delta preprocessing scripts.

FIGURE 1.5 UPGRADE READINESS CHECK

Attribute Framework

The upgrade framework in Microsoft Dynamics AX 2012 uses X++ attributes to define the upgrade scripts. This architecture simplifies coding upgrade scripts, reduces the possibility of defects, improves supportability, and makes extending the upgrade framework simpler. The biggest advantage of this feature is that users can run a dependency analyzer tool to optimize the upgrade script dependencies.

Upgrade Cockpit

The Data upgrade cockpit form provides the administrator a single interface to manage the actual processing of an upgrade. The Data upgrade cockpit form is used on the source system for managing preprocessing and in the target system for managing bulk copy and transformations. It also lets the administrator manage the tasks that are associated with an upgrade.

Through the Data upgrade cockpit form an administrator can manage how many threads are dedicated to the upgrade (Microsoft Dynamics AX 2012 target only), and also pause running preprocessing tasks. These abilities help an administrator throttle or expand the processing load of the upgrade.




1-10

The Data upgrade cockpit in the target Microsoft Dynamics AX 2012 system applies the new user interface changes which gives the administrator quick access to relevant information on the upgrade.

FIGURE 1.6 TARGET DATA UPGRADE COCKPIT

Row Count Validation

The Compare data upgrade row counts task in the Data upgrade checklist checks the data integrity on the Microsoft Dynamics AX 2012 target system following upgrade. Correctly correlated row counts between mapped tables will suggest, but does not confirm, that bulk copy and data upgrade finished successfully.

Upgrade References Considering the size of a project that a customer will generally perform on Microsoft Dynamics AX, performing upgrades is second only to performing implementations. Because of this Microsoft provides a large set of resources to guide customers and partners to a successful upgrade.

Code Upgrade Whitepapers

Microsoft provides a series of whitepapers to help with the Microsoft Dynamics AX 2012 code upgrade. These white papers provide an overview of code upgrades, details of some major technical changes, and show how many functional areas are refactored in Microsoft Dynamics AX 2012.

Microsoft Dynamics AX 2012 White Papers: Code Upgrade (http://go.microsoft.com/fwlink/?LinkId=244186)



Chapter 1: Overview

1-11

These white papers include the following topics:

• Code Upgrade Overview for Microsoft Dynamics AX 2012 • Developing with Table Inheritance • Eventing • Implementing and Extending the Organization Model in Microsoft

Dynamics AX 2012 • Implementing and Updating the Human Resources Framework for

Microsoft Dynamics AX 2012 • Implementing Budgeting for Microsoft Dynamics AX 2012

Applications • Implementing InventTrans Refactoring for Microsoft Dynamics AX

2012 Applications • Implementing the Item-Product data management framework for

Microsoft Dynamics AX 2012 • Implementing the Account and Financial Dimensions Framework for

Microsoft Dynamics AX 2012 Applications • Implementing the address book framework for Microsoft Dynamics

AX 2012 applications • Implementing the Agreement Framework • Implementing the Budget Control Framework for Microsoft

Dynamics AX 2012 Applications • Implementing the Operations Resource Model for Microsoft

Dynamics AX 2012 applications • Mapping the LedgerTrans Table to General Journal Tables • Migrating Extended Data Type Relations in Microsoft Dynamics AX

2012 • Shared Currencies and Exchange Rates for Microsoft Dynamics AX

2012 • Using date effective data patterns • Using the Enhanced Number Sequence Framework in Microsoft

Dynamics AX 2012 • Using the Policy Framework in Microsoft Dynamics AX 2012 • Using the refactored formletter framework




1-12

Data Upgrade Documents

Microsoft provides the following guides for performing an upgrade to Microsoft Dynamics AX 2012 and writing a data upgrade for Microsoft Dynamics AX 2012:

• Microsoft Dynamics AX 2012 Upgrade Guide (http://go.microsoft.com/fwlink/?LinkId=244187)

• Dynamics AX 2012 White Paper: How to Write Data Upgrade Scripts for Microsoft Dynamics AX 2012 (http://go.microsoft.com/fwlink/?LinkId=244188)

TechNet

The Microsoft Dynamics AX 2012 Technical Library on TechNet provides valuable technical information on Microsoft Dynamics AX 2012.

Microsoft Dynamics 2012 Technical Library (http://go.microsoft.com/fwlink/?LinkId=244190)

Microsoft Developer Network

The Microsoft Dynamics AX 2012 for Developers Microsoft Developer Network (MSDN) site has valuable information on most technical aspects of Microsoft Dynamics AX 2012.

Microsoft Dynamics AX 2012 for Developers (http://go.microsoft.com/fwlink/?LinkId=244191)

Microsoft Training

Microsoft offers training materials on major topics within Microsoft Dynamics AX 2012. These materials are offered as downloadable training materials, classes, e-learning, and hands-on labs (HOLs). The materials are available on Partner Source or Customer Source.

Summary The upgrade to Microsoft Dynamics AX 2012 includes improvements to simplify the administrator experience and minimize downtime. The upgrade is based on a Source-to-Target framework, that performs most of the processing that is required in an upgrade before the system downtime for copying data.

The upgrade process starts in parallel with preprocessing on the source system and configuring a target system. This includes installation and code upgrade. After preprocessing is finished on the source system, and the target system is configured, the period of system downtime for the upgrade can start. In the period of system downtime, the source system is put in single-user mode and final preprocessing steps are run. When these steps are completed, the rest of the upgrade is performed on the target system.



Chapter 1: Overview

1-13

Test Your Knowledge Test your knowledge with the following questions.

1. Which upgrade feature is used to identify data issues that could potentially affect data upgrade?

( ) Attribute framework ( ) Upgrade readiness check ( ) Row count validation ( ) Upgrade cockpit

2. On which systems can upgrade preprocessing be performed? (Select all that apply)

( ) Microsoft Dynamics AX 2009 source Production system. ( ) Microsoft Dynamics AX 4.0 source Test system, by using the

Upgrade State Transfer Tool. ( ) Microsoft Dynamics AX 2012 destination Production system. ( ) Microsoft Dynamics AX 2012 destination Test system, by using the

Upgrade State Transfer tool.

3. Match the Microsoft Dynamics AX 2012 reference with its description.

_____ 1. Microsoft Dynamics AX 2012 Technical Library and Microsoft Dynamics AX 2012 for Developers MSDN_____ 2. Write Data Upgrade Scripts for Microsoft Dynamics AX 2012 _____ 3. Microsoft Training_____ 4. Microsoft Dynamics AX Upgrade Guide _____ 5. Code upgrade whitepapers

a. e. Microsoft offers training materials on major topics within Microsoft Dynamics AX 2012. These materials are offered as written training materials, classes, and e-learning.

b. Guide for creating upgrade scripts in Microsoft Dynamics AX 2012

c. Web catalogs of technical information on Microsoft Dynamics AX 2012

d. Documents that provide an overview of code upgrades, detail some major technical changes, and show how many functional areas are refactored into Microsoft Dynamics AX 2012.

e. Guide for examining the whole upgrade process.




1-14

4. Which of the following are advantages of the Source-to-Target upgrade framework? (Select all that apply)

( ) Decreased system downtime ( ) Decreased overall processing time ( ) Handles the large scale data model changes and normalization

between Microsoft Dynamics AX 2009 and Microsoft Dynamics AX 2012

( ) Can be performed with only one database

5. Which versions are supported for the upgrade in the Microsoft Dynamics AX 2012 upgrade framework? (Select all that apply)

( ) Microsoft Axapta 3.0 ( ) Microsoft Dynamics AX 4.0 ( ) Microsoft Dynamics AX 2009 with an SQL database ( ) Microsoft Dynamics AX 2009 with an Oracle database



Chapter 1: Overview

1-15

Quick Interaction: Lessons Learned Take a moment and write down three key points you have learned from this chapter

1.

2.

3.




1-16

Solutions Test Your Knowledge

1. Which upgrade feature is used to identify data issues that could potentially affect data upgrade?

( ) Attribute framework (•) Upgrade readiness check ( ) Row count validation ( ) Upgrade cockpit

2. On which systems can upgrade preprocessing be performed? (Select all that apply)

(√) Microsoft Dynamics AX 2009 source Production system. (√) Microsoft Dynamics AX 4.0 source Test system, by using the

Upgrade State Transfer Tool. ( ) Microsoft Dynamics AX 2012 destination Production system. ( ) Microsoft Dynamics AX 2012 destination Test system, by using the

Upgrade State Transfer tool.

3. Match the Microsoft Dynamics AX 2012 reference with its description.

c 1. Microsoft Dynamics AX 2012 Technical Library and Microsoft Dynamics AX 2012 for Developers MSDN b 2. Write Data Upgrade Scripts for Microsoft Dynamics AX 2012 a 3. Microsoft Training e 4. Microsoft Dynamics AX Upgrade Guide d 5. Code upgrade whitepapers

a. e. Microsoft offers training materials on major topics within Microsoft Dynamics AX 2012. These materials are offered as written training materials, classes, and e-learning.

b. Guide for creating upgrade scripts in Microsoft Dynamics AX 2012

c. Web catalogs of technical information on Microsoft Dynamics AX 2012

d. Documents that provide an overview of code upgrades, detail some major technical changes, and show how many functional areas are refactored into Microsoft Dynamics AX 2012.

e. Guide for examining the whole upgrade process.



Chapter 1: Overview

1-17

4. Which of the following are advantages of the Source-to-Target upgrade framework? (Select all that apply)

(√) Decreased system downtime ( ) Decreased overall processing time (√) Handles the large scale data model changes and normalization

between Microsoft Dynamics AX 2009 and Microsoft Dynamics AX 2012

( ) Can be performed with only one database

5. Which versions are supported for the upgrade in the Microsoft Dynamics AX 2012 upgrade framework? (Select all that apply)

( ) Microsoft Axapta 3.0 (√) Microsoft Dynamics AX 4.0 (√) Microsoft Dynamics AX 2009 with an SQL database ( ) Microsoft Dynamics AX 2009 with an Oracle database




1-18

