Upgrade from AX 3.0 , AX4.0 to AX 2009

The steps below provide a high-level overview of the tasks that you must complete to upgrade from Microsoft Dynamics AX 3.0 to Microsoft Dynamics AX 2009.

•Back up your existing database and application files.

•Import two .xpo files from the installation media to assist with data upgrade.

• UpgradeColumnList.xpo, for 32-bit to 64-bit RecId field conversion.

• LeftJustified.xpo, for removing any trailing spaces from fields.

* Note: To help improve performance, you can apply the LeftJustified.xpo on the database that you create in step 4 after you’ve used the Microsoft Dynamics AX DB Upgrade Preparation tool but before you start the Microsoft Dynamics AX 2009 AOS.

•(Optional) To help improve performance, remove all user data and logs of Microsoft Dynamics AX 3.0. For example, clean up the SysDatabaseLog table.

•Create an empty database for Microsoft Dynamics AX 2009 in SQL Server 2005.

•(Optional) To help improve performance, set initial data and log file sizes so that they don’t increase while you perform the data upgrade process.

•(Optional) To help improve performance, set the recovery model to Simple for the Microsoft Dynamics AX 2009 Database.

•Run AXDBUpgrade.exe (The Microsoft Dynamics AX DB Upgrade Preparation tool). Note: To help improve performance, you can run this tool in Multithreaded mode. For example, to run this tool in 10 threads, enter AxDbUpgrade.exe P/10 at a command prompt.

•(Optional) Apply the LeftJustify file imported in step 2 to the Microsoft Dynamics AX 2009 database created in step 4.

•Back up your Microsoft Dynamics AX database. Your database is ready to be upgraded. •Run the Microsoft Dynamics AX 2009 Setup file from the installation media. During installation, select the database that you created in step 4.

•Copy your upgraded customized file into the correct application directory.

•Start the AOS.

•Start the Microsoft Dynamics AX 2009 client. The Upgrade checklist is displayed automatically.

•Complete the steps in the Upgrade checklist to finish upgrading.

The steps below provide a high-level overview of the tasks that you must complete to upgrade from Microsoft Dynamics AX 4.0 to Microsoft Dynamics AX 2009.

- Back up your existing database and application files. - (Optional) To help improve performance, remove all user data and logs of Microsoft Dynamics AX 4.0. For example, clean up the SysDatabaseLog table.

- (Optional) To help improve performance, set initial data and log file sizes so that they don’t increase while you perform the data upgrade process.

- (Optional) To help improve performance, set the recovery model to Simple for the Microsoft Dynamics AX 2009 Database. - Back up your Microsoft Dynamics AX database. Your database is ready to be upgraded.

- Run the Microsoft Dynamics AX 2009 Setup file from the installation media. During installation, select your existing Microsoft Dynamics AX database.

- Start the Microsoft Dynamics AX 2009 client. The Upgrade checklist is displayed automatically.

- Complete the steps in the Upgrade checklist to finish upgrading.

Upgrading to Microsoft Dynamics AX 4.0 and Microsoft Dynamics AX 2009 -convergence session please check following link Click Here

Web Service Basic

Introduction
We all talk about webservices, webservices can do this and webservices can do that. But when we are asked to make one, we hesitate. Maybe it's because we never made a webservice before, and all the time playing with Webforms and Windows Forms or even Console Applications. By the way, I love Console applications. In this article, I will show you how to create a simple webservice that is consumed by a Console application client.
Making the WebService:
First, start your Visual Studio .NET, and in the project type, select ASP.NET WebService. In the left pane, choose the language of your choice. In this example, I will be using Visual C#.NET. Once you select the project, a page will appear which will be more like a design page, switch to its code view. In the code view, you can see lot of comments and C# code already written for you. You will also see that at the bottom, there is a method HelloWorld which is written for you by default, so you can test your service and of course say hello to the world. After removing the unwanted code and comments, your code will look like this:

using System;
using System.Collections;
using System.ComponentModel;
using System.Data;
using System.Diagnostics;
using System.Web;
using System.Web.Services;
namespace WebServiceExample
{
public class Service1 : System.Web.Services.WebService
{
public Service1()
{

InitializeComponent();
}

// Add the Description Attribute so you
// will know the purpose of your WebService
[WebMethod(Description="This Method prints HelloWorld")]
public string HelloWorld()
{
return "Hello World";
}
}
}

Let's dig into this small code. [WebMethod] Attribute denotes that this method will be used by the clients, also this method has to be public in order for a client to use it. Description inside the WebMethod Attribute just gives the method more meaning. Don't worry about the InitializeComponent() method since it's written by default.
Running the WebService:
OK, now you have made your first kick ass WebService (without even writing a single line of code). Let's run it and check whether it gives the correct result or not. In the Solution Explorer, right click on the .asmx file, and select View in Browser

Once you click on "View in Browser", the next screen you will see will be something like this:

I have erased most of the stuff, so you can only see the method that you need in this example. Below, you can see the method HelloWorld and the description you wrote for the method.
Now, click on the HelloWorld method. I don't want to scare you with all the SOAP and HTTP code produced, so I am only going to paste the screen shot which will be relevant to this example.

Alright, so far so good. Now, just press the Invoke button to see the result of your method named HelloWorld().

This is cool. You have just tested your first webservice and it ran since you didn't coded it. I know what you are thinking right now. Is the client going to see the result like this strange format (this is XML format). Well, of course not. That's why you need to make a Proxy class which consumes this service.
Making a Proxy Client:
Let's make a Console application which consumes this service. You can use any language and platform to consume this service, that's the purpose of XML WebService. Now, this procedure requires some mouse clicking :). So I will write down the steps instead of pasting the screen shots.

• Start a new project which will be a Console Application in Visual C#.NET.
  
• Once you see the code view in the Console application, right click on the project name from the Solution Explorer. Remember that project name will be written in bold.
  
• Click on "Add Web Reference".
  
• Paste the URL of your WebService. You can get the URL of your WebService when you view your webservice in IE or any other browser.
  
• Click GO.
  
• Your webservice will be loaded. In the Web Reference Name textbox, write "MyService" and click Add Reference.
  
• You will see that the web reference has been added in your Solution Explorer, meaning that webservice is ready to kick some butt.
  

Now, all you have to do is to make the instance of the WebService class using the reference name that you provided, which is "MyService".

using System;
namespace MyClient
{
class Class1
{

[STAThread]
static void Main(string[] args)
{
// Make an instance of the WebService Class
// using the Web Reference you provided
MyService.Service1 service = new MyService.Service1();
// Assign message what ever is returned
// from HelloWorld in this case "HelloWorld"
string message = service.HelloWorld();
// Prints out the message on the screen
Console.WriteLine(message);
}
}
}

And that's it. You use the webservice class just like any other class. Something you need to keep in mind is that if you decide to make a new method in your webservice and want to make it available to the client, then always remember to build your webservice solution so that the assembly can be updated. If you don't build your webservice, you won't be able to see the methods on the client side.

Demo Data for Microsoft Dynamics AX 2009

The demo data for Dynamics AX 2009 has been released. Its "Contoso Entertainment Systems (CES)" . Now the Demo data comes in 2 flavours... standard dat/def & a SQL backup.

The Demo Data set for Microsoft Dynamics® AX 2009 is no longer based on the Global Trade and Manufacturing Company. Based on market feedback we have created a new Contoso Entertainment systems group of companies. It comes with 2 fiscal years of transactional data that enable us to demo our stronger Business Intelligence story and Role Center pages, while allowing us to easily expand the demo data story in future releases as we expand Microsoft Dynamics® AX’s functionality footprint.
Click the link below to download.
Demo Data for Microsoft Dynamics AX 2009 [Requires Partnersource Logon]

How Do I” Videos — Dynamics AX

On this page you will find videos designed for all Microsoft Dynamics AX developers, from the novice to the professional. New videos are added regularly, so check back often. (click here)
Microsoft has added following Videos
1. Forms Series #1 How Do I: Link Parent and Child Forms by Using Dynamic Links?(6 minutes, 47 seconds)
2. Enterprise Portal Series
#1 How Do I: Use Record Context in Enterprise Portal?(14 minutes, 51 seconds)

#2 How Do I: Create a Simple List Page in Enterprise Portal?(4 minutes, 52 seconds)

#3 How Do I: Create a Simple Task Page in Enterprise Portal?(4 minutes, 39 seconds)

#4 How Do I: Create a Simple Wizard Page in Enterprise Portal?(7 minutes, 39 seconds)

#5 How Do I: Call an X++ Class From an EP User Control?(7 minutes, 26 seconds)

#6 How Do I: Add a Range to a Dataset in an EP List Page?(5 minutes, 13 seconds)
3. User Interface Series #1 How Do I: Navigate the Client User Interface?(8 minutes, 53 seconds)
4. Application Integration Framework (AIF) Series #1 How Do I: Create a Custom AIF Pipeline Component?(7 minutes, 28 seconds)

Installing Ax 2009

Installing Microsoft Dynamics AX 2009 requires more than the installation DVD. This post will provide you with an overview of the software components and their download sources to get you better prepared for the installation.

Following Components are required to install Ax 2009

• Microsoft Dynamics AX 2009 Release DVD ISO which You may download from download the Microsoft Dynamics 2009 Release May Edition DVD ISO file (1.7 GB in size) from PartnerSource Since it is in ISO format, you may use any Virtual DVD software to mount it as a DVD disc to use it directly or to extract the files to a physical location.


• Microsoft .NET Framework 3.5 Microsoft Dynamics AX 2009 utilized the latest features from Windows Presentation Foundation, etc. You need to install Microsoft .NET Framework 3.5 before you are able to install Microsoft Dynamics AX 2009. The table bellow shows the options you have to get the .NET Framework 3.5 installed. Pick one that suits your need best

Microsoft .NET Framework 3.5 Live Installer

Microsoft .NET Framework 3.5 Full Package

• Service Pack 2 for Microsoft SQL Server 2005 If you are hosting your Dynamics AX 2009 data with Microsoft SQL Server 2005, you will need Service Pack 2 or later. This service pack has been released for over a year. In case you have not updated your Microsoft SQL Server 2005 to SP2, you may download the update at Microsoft Download: SQL Server 2005 SP2.


• Dynamics AX 2009 Demo Data Microsoft has not realeased any official demo data for Dynamics AX 2009 Release yet. but you can download and use Demo data AX 2009 CTP3 VPC Ver02


• Microsoft Windows Sharepoint Services 3.0 with Service Pack 1 Sharepoint Services 3.0 SP1 is required to host the Role Centers and Enterprise Portal. It is not included in the Dynamics AX 2009 Installation DVD. You have an option to use Microsoft Office Sharepoint Server 2007 or Microsoft Windows Sharepoint Services 3.0. It is available for download at Microsoft Download. Windows SharePoint Services 3.0 with Service Pack 1


• Microsoft Visual Studio 2008 Shell (isolated mode) Redistributable Package This package is required for the Reporting Extension to work. There are two Microsoft Visual Studio 2008 Shell redistributable package; isolated and integrated. Make sure you are having the isolated package. When you install this package, please note that the executable Microsoft Visual Studio 2008 Shell (isolated mode) Redistributable Package