LCSinActionWorkshop-Develop3 UpgradeAnalysis V2

Microsoft Dynamics AX
LCS: Develop Phase: Upgrade Analysis

Last Updated: August 2015
AX 2012 R3 / Version 2.1.0
Yuthana Arngmaneekul
Table of Contents
Introduction ...............................................................................................................................................................................................3
LCS: Develop Phase: Upgrade Analysis ..............................................................................................................................................3
Collect and upload files for analysis (full-version upgrade: Microsoft Dynamics AX 4.0 or AX 2009) ....................... 4
Install the Rapid Data Collector.................................................................................................................................................. 4
Upload and analyze files............................................................................................................................................................... 4
Collect and upload files for analysis (in-place upgrade: AX 2012) ....................................................................................... 5
Export and zip your model store................................................................................................................................................ 5
Upload and analyze files............................................................................................................................................................... 5
Download the report ......................................................................................................................................................................... 5
See also .................................................................................................................................................................................................. 6
How to: Export and Import a Model Store [AX 2012] ............................................................................................................ 12
Preparing the system ....................................................................................................................................................................... 12
Validate permissions.................................................................................................................................................................... 12
Exporting a model store ................................................................................................................................................................. 12
Export a model store (Windows PowerShell) ....................................................................................................................... 13
Export a model store (AXUtil) ................................................................................................................................................... 13
Importing a model store................................................................................................................................................................. 13
Import a model store to the dbo schema (Windows PowerShell) ................................................................................. 14
Install a model store to the dbo schema (AXUtil) ............................................................................................................... 14
Import a model store to a temporary schema, and then apply the model store (Windows PowerShell) .......... 15
Install a model store to a temporary schema, and then apply the model store (AXUtil) ........................................ 15
See also ................................................................................................................................................................................................ 16
Conclusion ............................................................................................................................................................................................... 20
Glossary and Additional Background Content ............................................................................................................................. 20
Disclaimer ................................................................................................................................................................................................ 21
Microsoft Dynamics AX 2012 R3 | LCS: Develop Phase: Upgrade Analysis | Last Updated: August 2015
Version
1.0
2.0
2.1
Description
Initial version (Winston Hait)
Additional information and updated document with July update (Yuthana Arngmaneekul)
Additional information and updated document with August update (Yuthana)
Date
June 2014
July 2015
August 2015
[https://technet.microsoft.com/en-us/library/dn268616.aspx]
Introduction
LCS: Develop Phase: Upgrade Analysis
Develop Phase Upgrade Analysis

LCS is a cloud-based, continuously updated set of services that helps you achieve repeatable and predictable
success with your Microsoft Dynamics AX 2012 R2 and later implementations. This demo will highlight the
features and functionality of Upgrade analysis.
For more details about Upgrade analysis click here.
Updated: August 18, 2014

In Microsoft Dynamics Lifecycle Services, Upgrade analysis helps users plan a full-version upgrade to
Microsoft Dynamics AX 2012 from Microsoft Dynamics AX 4.0 or Microsoft Dynamics AX 2009, or a minor
version or in-place upgrades from one version of AX 2012 to another.
The following chart illustrates how the service works for both full version upgrades and in-place upgrades.
Upgrade analysis uses a Rapid Data Collector (RDC) tool to analyze information about the existing
environment to help estimate the scale of the upgrade project.
For more information about full version upgrade, see Scenario: Upgrade AX 4.0 or AX 2009 to AX 2012 (all
versions).
Collect and upload files for analysis (full-version upgrade: Microsoft Dynamics AX 4.0 or AX 2009)
In order to use Upgrade analysis, you must install the Rapid Data Collector and then upload the Rapid Data
Collector files and AOD files.
The Rapid Data Collector collects metadata about the production environment, such as the number of records
in tables.
Important
Rapid Data Collector should be run in a copy of the production environment in which no
upgrade scripts have been loaded.
Install the Rapid Data Collector
1.
2.
3.
4.
5.
Go to Lifecycle Services.
Open a project, and then click the Upgrade analysis tile.
Click Add.
On the Upgrade analysis create job page, click Download in the source-to-target upgrade list).
Download the RapidDataCollector.msi file, save it, and then run it on a Microsoft Dynamics AX 4.0 or
Microsoft Dynamics AX 2009 client to install and run the Rapid Data Collector service.
The service will create a .zip file that contains Rapid Data Collector files.
6. Enter a name for the job, identify the version and build of Microsoft Dynamics AX that you are
upgrading from, and then click Create.
Upload and analyze files
You can upload the Rapid Data Collector files and AOD files in any order.
1.
2.
3.
4.
On the Upgrade analysis file upload page, click + (Add files).

Select the type of file to upload (Rapid Data Collector or AOD).
Enter the file location and click Upload.
After you upload all the files to analyze, click Analyze.
When the analysis process is complete, the status shows as Complete.

5. See the section Upgrade analysis (Lifecycle Services, LCS) for details about the available reports.
Collect and upload files for analysis (in-place upgrade: AX 2012)
For in-place upgrades, you must upload a model store that you have exported zipped.
Before you begin, perform the Scenario: Perform in-place upgrade to AX 2012 R2 or AX 2012 R3 steps in the
topic Scenario: Perform in-place upgrade to AX 2012 R2 or AX 2012 R3.
Export and zip your model store
1. Use Windows PowerShell or the AxUtil command line utility to export the model store from the
system that you plan to upgrade. For details, see How to: Export and Import a Model Store.
2. Use Windows or another system to zip (compress) the file.
Upload and analyze files
1. Sign in to Lifecycle Services, open a project, and then click the Upgrade analysis tile.
2. Click Add.
3. On the Upgrade analysis create job page, enter a name for the job, identify the version and build of AX
2012 that you are upgrading from, and then click Create.
4. On the Upgrade analysis file upload page, click + (Add files).
5. Browse to the zipped model store, and then click Upload.
After the file is uploaded, the file name and size are listed on the site.
6. Click Analyze Code to start the analysis process.
If no virtual machine is available when you start the process, the job will be listed as Process pending.
Note
The process will take 2-5 hours to complete, depending on the size of the model store.
You can close the website and log in again later to check on the progress of the
analysisprogress updates every 15 minutes.
7. When the analysis process is complete, the status shows as Complete.
8. See the section Upgrade analysis (Lifecycle Services, LCS) for details about the available reports.
Download the report
Upgrade analysis creates an overview report in HTML, and a detailed report as a Microsoft Excel file that you
can download and review.
To view the HTML report, click View.

To download the detailed report, click the Excel icon.
The following table lists the sheets provided by the report.

Sheet
Upgrade summary
Global tables
Customization Statistics
Description
List of key reports, and the number of
objects impacted by upgrade in each
module.
Input for
Lists tables that do not have DataAreaID Data upgrade, Code

values
upgrade
Lists all customizations
Number of customized tables and
classes
Code upgrade
Modified Objects
Modified Object Details
List of modified objects

List of what is modified in each object
Code upgrade
Code upgrade
Domain information
Lists companies, domains, and related

users
Security upgrade
Table statistics
Data upgrade,
Lists table size, properties, and counts of
Minimizing
rows and columns
downtime
Parameters
Lists parameter values
Data upgrade, Code

upgrade
Tables without DataAreaId
List of any tables that do not have a

DataAreaId.
Data upgrade
SysUtilElementsLog (AX
Object Usage Summary)
Lists usage patterns of MSDAX objects
Code upgrade
Customization View
Data upgrade
See also
Upgrading to a New Version of Microsoft Dynamics AX
Scenario: Perform in-place upgrade to AX 2012 R2 or AX 2012 R3
Upgrade analysis helps users plan a full-version upgrade to Microsoft Dynamics AX 2012 from Microsoft
Dynamics AX 4.0 or Microsoft Dynamics AX 2009 or a minor version or in-place upgrade from one version of
AX 2012 to another. The output reports can provide guidance on how much time and effort will be required
for the upgrade and can help in the decision process for upgrading from AX 4.0 and AX 2009
implementations.
Select the Upgrade analysis tile.
Here you see the main Upgrade analysis

page when you first start in LCS.
You will see two separate sections:
- The main dashboard showing the different
Upgrade analysis projects and their current
status, and the bar at the bottom of the
screen with an Add customization projects
button. A Remove button will appear after a
project has been created.
Click Add at the lower part of the

Project page.
Follow the steps based on the version of

Microsoft Dynamics AX that you are going to
upgrade.
When you have the appropriate files, you will
need to create a project and upload the files
for processing.
Click Create.
Click Add files, and upload the

relevant files to analyze.
Tip 1: For reference, the version type of the

project is displayed to help remind you of the
correct files to upload.
Tip 2: If you decide not to upload a file, just
click in the gray area to be returned to the
main Upload page.
If you need to remove a file before starting
the analysis:
Hover the mouse over the name.
Select the box in front of the name.
Click Remove.
After the files are uploaded:
Click Analyze code in the lower-right

corner of the Upload page.
The files will be processed and the progress will be shown by the chevrons at the top as they automatically
update. You do not have to stay on this page you can navigate away. You can come back anytime to Code
analyzer and click the file name from the main Project page to see how far along the progress is.
Tip: When the project is processing, it will

show an estimate in minutes of how long it
will take to run and show the progress it has
made so far. In my case it took around 4
hours.
Note: For reference, here is the view when

there are a number of projects. You can see
the status of each project: Describe (still need
to enter data/upload files), Processing, or
Processed.
Tip: You can sort the projects by column by
clicking the arrows next to each column
header.
When the analysis has finished, the status

changes to Processed on the main Project
page. To view the results:
Click the file name.
You are taken to the Completed page where

you can select from the three different
reports.
Note: The colors of the symbols in the reports reflect different meanings: red = errors, yellow = warnings, and
blue = information.
For the Excel version, click the first

Excel logo and it will open the Excel.
Tip: If you select the Excel version, make sure

Excel is installed and working correctly on the
system before you try to open the file.
Click the second, or bottom, Excel

logo to open the Log_ExcelReport.
Scroll down to see the results.
This report can be imported in the Microsoft

Dynamics AX developer environment
(MorphX) simply by saving the file to a
computer in your development environment
and then importing it through the compiler
output window.
10
11
Tip: Here is an example of the Excel report for

an upgrade from AX 4.0 or AX 2009. This is
from the sample file (Sample Upgrade
analysis report.xlsx) that is included in the zip
file.
How to: Export and Import a Model Store [AX 2012]
Updated: February 1, 2013

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012
Feature Pack, Microsoft Dynamics AX 2012
You can export and import a model store as a unit. If you must create similar environments, the preferred
method is to export and import a model store. Additionally, we recommend that you use this method when you
deploy major changes to a production environment. For more information about how to choose the method that
you use to deploy a solution, see Models, Layers, and the Model Store.
When you export or import a model store, you affect all model elements, layers, and models.
You can use either Windows PowerShell cmdlets or the AXUtil command-line utility to manage the model
store.
Preparing the system
Validate permissions
Validate that you have appropriate permissions to work with the model store:
o Administrative permissions on the local computer
o System Administrator rights in Microsoft Dynamics AX
o In Microsoft SQL Server:
Membership in the Securityadmin server role on the SQL Server instance
Membership in the db_owner role in the Microsoft Dynamics AX database
Exporting a model store
12
The model store that you export remains in the original environment. The model store is not deleted.
Export a model store (Windows PowerShell)
1. On the Start menu, point to All Programs, point to Administrative Tools, and then click Microsoft
Dynamics AX Management Shell.
2. At the Windows PowerShell command prompt, PS C:\>, type the following command, and then press
ENTER.
Windows PowerShell
Copy
Export-AXModelStore -File <Filename> -Details
This command exports the model store to an .axmodelstore file.

For more information, see Export-AXModelStore.
Export a model store (AXUtil)
1. On the Start menu, click Command prompt.

2. Navigate to the directory for the management utilities. Typically, the location of this directory
is %ProgramFiles%\Microsoft Dynamics AX\60\ManagementUtilities.
3. At the command prompt, type the following command, and then press ENTER.
Copy
axutil exportstore /file:filename [/verbose]
This command exports the model store to an .axmodelstore file.

Importing a model store
When you import a model store, you can import the new model store directly to the default schema, dbo.
Alternatively, you can import the model store to a different schema, and then apply the model store to the
default schema.
13
If you import the new model store directly to the dbo schema, downtime is likely to be greater, because
you must stop all Application Object Server (AOS) instances while the model store is imported.
If you import the model store file to a non-default schema, downtime may be less, because AOS
instances can remain active throughout the import process.
AOS instances must be stopped when the new model store is applied to the default schema. However, less time
is required to stop an AOS instance than to import a model store.
When you import a model store, you can back up the existing model store to another schema. The schema that
you back up the model store to cannot exist before you import the model store.
By default, if a conflict of element IDs occurs while an .axmodelstore file is imported, the import is stopped.
By default, optimization steps are performed if the number of elements in a model increases by more than 50
percent when a model or model store is reimported. For more information, see How to: Optimize a Model
Store for Runtime.
Import a model store to the dbo schema (Windows PowerShell)
1. Drain all client connections from the AOS instance that you are working with. For more information,
see Drain users from an AOS.
2. At the Windows PowerShell command prompt, PS C:\>, type the following command, and then press
ENTER.
Copy
Import-AXModelStore -File <Filename>
This command imports a model store to the Microsoft Dynamics AX database and associates the model
store with the default schema, dbo. You can also use the -BackupSchema parameter to copy the model
store that is overwritten to a new schema. The schema that is specified by the -BackupSchema
parameter cannot exist at the time that you run the cmdlet.
For more information, see Import-AXModelStore.
Install a model store to the dbo schema (AXUtil)
1. Drain all client connections from the AOS instance that you are working with. For more information,
see Drain users from an AOS.
2. On the Start menu, click Command prompt.
14
Copy
axutil importstore /file:filename
This command imports a model store to the Microsoft Dynamics AX database and associates the model
store with the default schema, dbo. You can also use the /BackupSchema parameter to copy the model
store that is overwritten to a new schema. The schema that is specified by the /BackupSchema
parameter cannot exist at the time that you run AXUtil.
Import a model store to a temporary schema, and then apply the model store (Windows
PowerShell)
1. For this example, the non-default schema is named TemporarySchema.

At the Windows PowerShell command prompt, PS C:\>, type the following command, and then press
ENTER.
Copy
Import-AXModelStore -File Staging.axmodelstore -SchemaName TemporarySchema
This command installs the model store file in the schema that you specify.
Note
The model store that you import to the non-default schema is not visible to Microsoft
Dynamics AX.
2. After the model store has been imported, drain all client connections from the AOS instance that you
are working with. For more information, see Drain users from an AOS.
3. After all AOS connections have been closed, type the following command, and then press ENTER.
Copy
Import-AXModelStore -Apply:TemporarySchema
This command applies a model store that was associated with the non-default schema,
TemporarySchema, to the dbo schema. The model store then becomes visible to Microsoft Dynamics
AX.
For more information, see Import-AXModelStore.
Install a model store to a temporary schema, and then apply the model store (AXUtil)
15
1. For this example, the non-default schema is named TemporarySchema.

On the Start menu, click Command prompt.
Copy
axutil importstore /file:filename /schemaname:name /verbose
This command installs the model store file in the schema that you specify.
Note
The model store that you import to the non-default schema is not visible to Microsoft
Dynamics AX.
4. Drain the client connections that are connected to the AOS instance that you are working with. For
more information, see Drain users from an AOS.
Copy
axutil importstore /apply /schemaname:TemporarySchema /verbose
This command applies a model store that was associated with the non-default schema,
TemporarySchema, to the dbo schema. The model store then becomes visible to Microsoft Dynamics
AX.
See also
Models, Layers, and the Model Store
AxUtil and Windows PowerShell Commands for Deploying Models
Administering Microsoft Dynamics AX by using Windows PowerShell
Windows PowerShell for Microsoft Dynamics AX
16
Run as administrator
This depend on your AXmodelstore. In my case, it

took 10 15 minute
Models are stored in the model store. The model
store is a database in which all application elements
for Microsoft Dynamics AX are stored. Customizations
are also stored in the model store. The model store
replaces the Application Object Data (AOD) files that
were used in earlier versions of Microsoft Dynamics
AX. Models that have been installed in the model
store are used at run time.
In Microsoft Dynamics AX 2012 R2, the model store
was moved into a database that is separate from the
business database.
17
18
In my case, 140 minute
Upgrade analysis helps you to estimate and understand the level of work necessary to upgrade to Dynamics
19
AX 2012 R3 from AX 4.0, AX 2009, AX 2012 RTM, Microsoft Dynamics AX 2012 Feature Pack, and AX 2012 R2
implementations. By analyzing the uploaded files, it identifies, both in HTML-based and Excel-based reports,
errors, warnings, and places for investigation. This can help identify and estimate the amount of work
necessary to do the upgrade prior to beginning work on the project and can help make educated decisions on
the correct ways to upgrade to Dynamics AX 2012 R3 from your current implementation.
Conclusion
The series of demo scripts in this collection walk you through the tools and services in the Develop phase of ALM
for LCS. These services help project managers and business analysts better analyze and plan usage, speed up and
increase user adoption, help meet regulatory requirements, maximize uptime, and help the organization realize
business value faster all while delivering amazing customer experiences.
Glossary and Additional Background Content

There is a series of three videos on LCS, one for each phase, which are available on YouTube:
Microsoft Dynamics AX 2012 R3 Lifecycle Services (LCS) Define Phase Demo and Discussion
http://youtu.be/ij28o4JznJA
Microsoft Dynamics AX 2012 R3 Lifecycle Services (LCS) Develop Phase Demo and Discussion
http://youtu.be/TTAuukkK5Mo
Microsoft Dynamics AX 2012 R3 Lifecycle Services (LCS) Operate Phase Demo and Discussion
http://youtu.be/Uiok3ziH2Eo
20
Disclaimer
2015 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista, Microsoft Dynamics
and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other
countries. Other names and brands may be claimed as the property of others.
The information herein is for informational purposes only and represents the current view of Microsoft
Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it
should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the
accuracy of any information provided after the date of this presentation.
Sample code included in this presentation is made available AS IS. THE ENTIRE RISK OF THE USE OR THE
RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE
INFORMATION IN THIS PRESENTATION. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR
OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS PRESENTATION.
Microsoft products are not intended for use in medical, life-saving, or life-sustaining applications.
Microsoft Dynamics is a line of integrated, adaptable business management solutions that enables you and your
people to make business decisions with greater confidence. Microsoft Dynamics works like and with familiar
Microsoft software, automating and streamlining financial, customer relationship and supply chain processes in a
way that helps you drive business success.
U.S. and Canada Toll Free 1-888-477-7989
Worldwide +1-701-281-6500 www.microsoft.com/dynamics
21

LCSinActionWorkshop-Develop3 UpgradeAnalysis V2

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

LCSinActionWorkshop-Develop3 UpgradeAnalysis V2

Загружено:

Авторское право:

Доступные форматы

Microsoft Dynamics AX

LCS: Develop Phase: Upgrade Analysis

Develop Phase Upgrade Analysis

Updated: August 18, 2014

On the Upgrade analysis file upload page, click + (Add files).

When the analysis process is complete, the status shows as Complete.

To view the HTML report, click View.

The following table lists the sheets provided by the report.

Lists tables that do not have DataAreaID Data upgrade, Code

List of modified objects

Lists companies, domains, and related

Lists parameter values

Data upgrade, Code

Tables without DataAreaId

List of any tables that do not have a

Lists usage patterns of MSDAX objects

Select the Upgrade analysis tile.

Here you see the main Upgrade analysis

Click Add at the lower part of the

Follow the steps based on the version of

Click Add files, and upload the

Tip 1: For reference, the version type of the

Hover the mouse over the name.

Select the box in front of the name.

After the files are uploaded:

Click Analyze code in the lower-right

Tip: When the project is processing, it will

Note: For reference, here is the view when

When the analysis has finished, the status

Click the file name.

You are taken to the Completed page where

For the Excel version, click the first

Tip: If you select the Excel version, make sure

Click the second, or bottom, Excel

This report can be imported in the Microsoft

Tip: Here is an example of the Excel report for

How to: Export and Import a Model Store [AX 2012]

Updated: February 1, 2013

Exporting a model store

This command exports the model store to an .axmodelstore file.

1. On the Start menu, click Command prompt.

This command exports the model store to an .axmodelstore file.

1. For this example, the non-default schema is named TemporarySchema.

1. For this example, the non-default schema is named TemporarySchema.

This depend on your AXmodelstore. In my case, it

In my case, 140 minute

Glossary and Additional Background Content

Вам также может понравиться