In order for Dynamics AX to function at its best, hardware and network infrastructure has a large effect on the level of performance a company will experience. Luckily, there are requirements to ensure that Dynamics AX will function at its best. You can also expand on these requirements to provide even better performance. For example, you can certainly expand and implement a better infrastructure (scaling out) that supports more network bandwidth or implement more data capacity or processing power as well (scaling up).
The requirements of the network and hardware are determined by the number of concurrent users and transactions as well as the other services whose demands will take up network resources alongside Dynamics AX.
Since Dynamics AX is a modular server system, requirements are also based on which of these systems will need to be utilized and to what degree. For example, for the Enterprise Portal, you will need to decide if it will be accessible using an Intranet on a Local Area Network (LAN) or using the Internet on a Wide Area Network (WAN).
In this case, your hardware, software, and even network requirements will have to compensate to handle the bandwidth, security, and load. Another example may be that your implementation may be running many batch jobs in which they handle large sums of data. For that reason, you may consider implementing extra Application Object Servers (AOS) to compensate for the batch loads and demands.
You may also want to be prepared for emergency scenarios or for compensating additional demands that occur from company expansions.
Microsoft Dynamics Sure Step implementation methodology (http://www.microsoft.com/dynamics/support/implementation/success.aspx) is an excellent collection of guidelines for successful implementations, especially for Dynamics AX. The following table is adapted from the Sure Step methodology and provides an overview of processes during an implementation:
|
Phase |
Tasks during phase |
|---|---|
|
Diagnostics |
|
|
Analysis |
|
|
Design |
|
|
Phase |
Tasks during phase |
|---|---|
|
Development |
|
|
Phase |
Tasks during phase |
|---|---|
|
Deployment and Operation |
These are on-going activities that continue after the project is closed and throughout any future involvement with the client |
|
Phase |
Tasks during phase |
|---|---|
|
Optimization |
The purpose of this phase is to help the customer optimize the benefit they get from the business solution. |
|
Upgrade |
|
Before beginning a Dynamics AX implementation, it is important that roles are determined and delegated. This ensures a steady process throughout the implementation and lessens the possibility of any bottlenecks occurring. The following table shows a theoretical sequence of the initial phase of an implementation:
|
Sequence or Priority |
Responsible party (Company, Implementer, or Both) |
Action item |
Description |
|---|---|---|---|
|
1 |
Both |
Choose required features that a company will need to perform business functions. |
Specific licenses will need to be purchased to enable certain functions in Dynamics AX to be useable. Also, third party modules may need to be utilized. |
|
2 |
Company |
Gather current network, hardware, and software capabilities. |
Review installed software such as operating systems, hardware such as processing speed, available RAM and HDD space. Also review current bandwidth capacity and current network load. |
|
3 |
Implementer |
Gather user, usage, and topology requirements. Estimate projected growth rate. |
Number of total users in the company, number of concurrent users, and number of transactions per minute. Topology requirements, such as Intranet or Extranet (VPN). |
|
4 |
Company |
Install any new hardware, software and/or configure the network to fit the previously mentioned requirements. |
Examples of modifications at this phase are to set up the Windows Domain Controller to support Kerberos authentication. |
|
5 |
Company |
Set up user accounts. |
Create users that will need to have specific privileges from the implementation company to perform installation, setup, and the configuration of Microsoft Dynamics AX 2009. |
|
6 |
Implementer |
Create implementation directories. |
Specific directories for Dynamics AX configuration files, user documentation, installation and utilities, or any other miscellaneous yet relevant files for the implementation. |
|
7 |
Implementer |
Install required software for Dynamics AX 2009. |
Install required software that the Dynamics AX 2009 installation program needs in order to install and run base and server components. For example, Internet Information Services (IIS) and Windows SharePoint Services will need to be installed and set up for the Enterprise Portal to be installed. |
|
8 |
Implementer |
Create and set up development environment. |
In conjunction with the previous step, there should be a server dedicated to development. The development environment will contain everything that the production environment has; however, the base and server components can run on the same system. Sometimes, the test environment can also reside on the development server. |
|
9 |
Implementer |
Create and set up test and staging environment. |
Similar to the previously mentioned; however, these environments will resemble the production more so. Typically, the staging environment is practically identical to the production environment. |
|
10 |
Implementer |
Create and set up production environment. |
The production environment should be considered an "island" from the other environments and should be treated as sacred. |
|
11 |
Implementer |
Import users. |
Import company users into required environments. |
A well-coordinated team with specific tasks is an integral part of a successful implementation. Without such a team, unforeseen failures and setbacks may occur. Each role is required due to the responsibilities incurred during an implementation lifecycle. The following roles will need to be occupied by qualified professionals:
A Project Manager is a person who will oversee the implementation process. Such an individual may encompass some skill sets of each preceding role. Ultimately, the job of the project manager is to orchestrate each individual during the process of an implementation and also communicate with the business to create functional and technical requirements.
An Architecture specialist is one who can determine methods to balance performance and scalability with manageability, interoperability, security, and maintainability.
A Developer is responsible for tailoring Dynamics AX 2009 to a company's specific needs by providing custom development and integration.
A Tester is an individual with functional knowledge of developed modifications and functionality of Dynamics AX.
The role of a Trainer can be fulfilled by a Tester who will be in charge of specifically training individuals on how to use the systems for business functions.
A System Administrator would typically already be working at a position in the company that requires familiarity with network topology and server hardware. The primary goal of this individual, especially during the implementation phase, would be to monitor and ensure that all resources are operating sufficiently, enabling them to provide optimal performance and meet service level agreements.
Note
At times, responsibilities fluctuate, consolidate, and deviate from the initial roles. The previously mentioned list provides mere guidelines to understand the typical responsibilities required for an implementation. Keep in mind, the larger the implementation, the greater the responsibilities, as the number of roles required will increase proportionally.
Setting up an environment for Dynamics AX 2009 follows similar guidelines to other Microsoft infrastructure methodologies. A list of possible implementation methodologies are as follows: