CHAPTER 2: PLANNING MICROSOFT DYNAMICS AX INSTALL

17 downloads 2263 Views 775KB Size Report
Explain the requirements for Microsoft Dynamics AX 2009 installation ... This training course focuses on a standard Microsoft Dynamics AX 2009 implementation in a ..... following: • Information on who owns the administration of the plan.
Chapter 2: Planning Microsoft Dynamics AX Install

CHAPTER 2: PLANNING MICROSOFT DYNAMICS AX INSTALL Objectives The objectives are: •

Show the Microsoft Dynamics® AX 2009 topology



Explain the requirements for Microsoft Dynamics AX 2009 installation



Learn how RAID disk subsystems can help customers achieve the best performance possible and help protect them from devastating data loss



This topic describes considerations in planning disaster recovery



Examine the skills that are needed by staff members to successfully install Microsoft Dynamics AX 2009



How to use the naming convention to keep Microsoft Dynamics AX 2009 installations organized

Introduction To successfully install Microsoft Dynamics AX, the application infrastructure must comply with system requirements. These requirements include the following: •

Microsoft Dynamics AX 2009 network infrastructure requirements.



The hardware and software requirements for various deployment scenarios.



The skills required to successfully install Microsoft Dynamics AX

This training course focuses on a standard Microsoft Dynamics AX 2009 implementation in a Windows™ Server 2003 environment. However, there is mention of other available scenarios. NOTE: In the classroom-training environment, students will install Microsoft Dynamics AX on a VPC configured to run Windows Server 2003.

2-1

Installation and Configuration in Microsoft Dynamics® AX 2009

IMPORTANT: The Microsoft Dynamics AX 2009 Implementation Guide delves into areas the organization might have to address depending on the deployment requirements. In addition to the standard system requirements presented in this course, the Implementation Guide contains many additional tasks to consider depending on the system configuration. Microsoft also has a Web site that contains the latest requirements and other information about Microsoft Dynamics AX 2009. Refer to PartnerSource for more information.

Scenario Contoso Entertainment is a mid-sized manufacturer of various entertainment products. Although their customer base spans multiple countries, their target is mainly North America. They plan to use Microsoft Dynamics AX 2009 to take advantage of the integration with their existing Microsoft products. Contoso uses many of the Microsoft products that will be required during the Microsoft Dynamics AX implementation. The company plans to hire consultants to implement the system, but will use Contoso in-house resources for ongoing maintenance of the system.

Problem Contoso's in-house staff has experience with Windows Server 2003, Active Directory, and Microsoft™ SQL Server. However, they do not have experience deploying a large-scale business system. The staff also has networking experience, but has not had to troubleshoot issues with large-scale data transfers with many users as expected with the new business system.

Goal The goal for Contoso is to have all the skill sets covered for the Microsoft Dynamics AX implementation. This includes Windows Server 2003, deployment issues, Active Directory, SQL Server, and Networking. In addition, it will help if administrators have proficiency in several other areas including Microsoft Exchange, Domain Controllers, SQL Reporting Services, and Web services.

2-2

Chapter 2: Planning Microsoft Dynamics AX Install Solution To make sure all the important skills are covered for the Microsoft Dynamics AX implementation, Contoso must find consultants with the required skills that Contoso does not have in-house. Because the Contoso staff has Windows Server 2003, Active Directory and SQL Server skills, they must use implementation consultants with deployment and networking skills. The implementation consultant must follow these steps: 1. Review the hardware and software requirement in the pre-installation checklist 2. Determine what hardware or software must be upgraded to support the Microsoft Dynamics AX deployment 3. Perform any necessary hardware and software upgrades 4. Determine whether any new servers or client computers must be purchased, and schedule those purchases to coincide with the project plan

Plan System Topology Performing the Microsoft Dynamics AX implementation in stages will help the installation go more smoothly. Consider the following factors during planning: •

Implementing a Microsoft Dynamics AX system on a local area network that has multiple-user access requires careful consideration and planning.



A large business with multiple locations might experience different challenges compared to a smaller business with one location and only a few users.



Start the implementation process with an inventory of the organization's current hardware and software.



Determine the deployment scenario that best meets the business’ current needs and allows for expected future growth.

Steps in System Planning before the actual installation occurs, implementers must collect information about the customer's requirements to help prepare the correct topology. 1. Define and document these items with the customer: o Number of transactions o Number of users o Uses of system (modules and features to be implemented) o External user access required o Web access required

2-3

Installation and Configuration in Microsoft Dynamics® AX 2009 o o o

Required availability Projected growth rate Number of sites

2. Evaluate and document the existing infrastructure: o Existing hardware o Bandwidth o Operating system o Databases present o Applications to integrate 3. After collecting this information, determine how to structure the system. Key decisions are as follows: o If there are any computer roles that can be combined on a single computer. If computer roles can be combined, consider which ones to combine. o Determine whether there are any network load-balanced clusters to host the AOS. o Select a backup system for the Microsoft Dynamics AX environment.

Base Topologies If there are no users outside the domain (external users) that must access data, use one of the following basic topologies. This one uses three computers. NOTE: Although an implementer can install all the Microsoft Dynamics AX components on a single computer for development and trial purposes, in a production environment the single computer install is not supported.

2-4

Chapter 2: Planning Microsoft Dynamics AX Install The figure shows one of the more common topologies that uses three computers.

FIGURE 2.1 MINIMAL BASE TOPOLOGY

Clustered Base Topologies The figure shows a base system topology running on clustered servers.

FIGURE 2.2 CLUSTERED BASE TOPOLOGY

NOTE: Installing the application file server on an AOS is acceptable. Because there can only be one application file server in the environment it need only be installed on a single AOS computer in the cluster.

Intranet Enterprise Portal An Enterprise Portal server hosts and provides site definitions for a Microsoft SharePoint site that can present live Microsoft Dynamics AX data and functionality to trusted users, and can present restricted functionality, such as catalog information and questionnaires, to anonymous users.

2-5

Installation and Configuration in Microsoft Dynamics® AX 2009 Intranet-Only Enterprise Portal The figure shows a topology for a simple intranet-only Enterprise Portal.

FIGURE 2.3 SIMPLE INTRANET-ONLY ENTERPRISE PORTAL

2-6

Chapter 2: Planning Microsoft Dynamics AX Install The figure shows a large-scale intranet-only Enterprise Portal.

FIGURE 2.4 LARGE-SCALE INTRANET-ONLY ENTERPRISE PORTAL

Internet-Facing Enterprise Portal There are two recommended topologies for Internet-facing Enterprise Portal, the Standard Perimeter Network and the Traditional Perimeter Network. The primary difference between the two topologies is how access to Enterprise Portal is managed for external users. The topics titled Standard Perimeter Network and Traditional Perimeter Network describe two options for configuring a perimeter network to support Microsoft Dynamics AX 2009.

Standard Perimeter Network With a standard perimeter network the Active Directory domain contains: •

All internal users to be added to Microsoft Dynamics AX 2009.



Special users required for Microsoft Dynamics AX functionality.

2-7

Installation and Configuration in Microsoft Dynamics® AX 2009 •

An organizational unit that contains any users from outside the organization that require Enterprise Portal access. These users’ rights must be restricted in that the users cannot: o o

Log on locally Access network

NOTE: The organizational unit can contain other organizational units, as long as the top node is associated with Microsoft Dynamics AX 2009. The illustration shows a standard perimeter network configuration.

FIGURE 2.5 STANDARD PERIMETER NETWORK

Traditional Perimeter Network The traditional perimeter network contains two Active Directory domains: the internal domain and the external domain. The internal domain contains:

2-8



All internal users to be added to Microsoft Dynamics AX 2009.



Special users required for Microsoft Dynamics AX functionality.



Group required for application integration server functionality.

Chapter 2: Planning Microsoft Dynamics AX Install The perimeter network contains a second domain controller with a one-way trust relationship to the first domain controller. The second domain controller contains any users from outside the organization that require Enterprise Portal access. These users cannot have any rights in the internal domain, and their rights must be restricted in the perimeter network domain so that the users cannot: •

Log on locally



Access network

NOTE: On the Enterprise Portal computer, the Group Policy must be overridden. Set the policy to Cannot access network. The illustration shows a traditional perimeter network configuration.

FIGURE 2.6 TRADITIONAL PERIMETER NETWORK

Reporting Server Topology Reporting server is installed on an Internet Information Services (IIS) server that is not Internet-facing.

2-9

Installation and Configuration in Microsoft Dynamics® AX 2009 The illustration shows a simple reporting server topology.

FIGURE 2.7 SIMPLE REPORTING SERVER TOPOLOGY

Application Integration Server Topology An application integration server is installed on an Internet Information Services (IIS) server that is not Internet-facing. The illustration shows a simple application integration topology.

FIGURE 2.8 APPLICATION INTEGRATION SERVER TOPOLOGY

2-10

Chapter 2: Planning Microsoft Dynamics AX Install Short Answer 1 What information must be obtained before you install Microsoft Dynamics AX?

Short Answer 2 What are the three servers required for a basic installation of Microsoft Dynamics AX without external users?

2-11

Installation and Configuration in Microsoft Dynamics® AX 2009

Planning Hardware and Software Selecting appropriate hardware for a Microsoft Dynamics AX installation depends on many factors. The table shows some factors that implementers must be aware of when they are determining hardware in the environment. Factor

Description

Number of Transactions per Hour

The total average number of the following transactions processed per work hour is a key indicator of the size of database system needed: • Sales orders •

Purchase orders



Accounts payable



Accounts receivable



Production orders



CRM orders



General ledger journal transactions

In Microsoft Dynamics AX 2009 a transaction is defined a single line item. For example, a sales order with 1000 line items would be considered 1000 transactions. Number of Concurrent Users

A key indicator of the size of the Application Object Server system needed. It also affects the appropriate bandwidth and latency for the network.

Number of Concurrent Enterprise Portal Users

A key indicator of the size of the Windows SharePoint Server system needed.

Number of Remote Connections

The number of remote connections affects the determination for bandwidth and latency requirements for the network.

Number of locations

The number of locations and how they must interact also affects the infrastructure.

TABLE 2.1: ENVIRONMENTAL FACTORS

2-12

Chapter 2: Planning Microsoft Dynamics AX Install Network Requirements The table lists the minimum network requirements for client/server connections in a Microsoft Dynamics AX system. Value

Application Object Server (AOS)

Database

Bandwidth (b)

100 MB per second

100 MB per second

Latency (l)

Less than 5 milliseconds

Less than 5 milliseconds

TABLE 2.2: NETWORK REQUIREMENTS

The following formula expresses the total response time for running a task in Microsoft Dynamics AX 2009: (Number of calls to and from the server * l) + (number of bytes sent /b) Domain Requirements Consider the following domain requirements when installing Microsoft Dynamics AX: •

Computers running Microsoft Dynamics AX components must have access to other computers in the same Active Directory directory service domain, with Active Directory configured in native mode.



In the recommended production configuration, Microsoft Dynamics AX components are installed on multiple servers (such as the AOS server, the database server, and the Enterprise Portal server). In a configuration with multiple Microsoft Dynamics AX servers, the domain must use Kerberos authentication.



To support e-mail alerts in Microsoft Dynamics AX, an SMTP (Simple Mail Transfer Protocol) server must be present in the environment.

64-bit Operating Systems Microsoft Dynamics AX server components can be installed on either a 32-bit or a 64-bit operating system. Client components, except for the .NET Business Connector, must be installed on a 32-bit operating system. When installing on a 64-bit operating system, Setup will also install the 64-bit versions of most prerequisites. Setup installs both the 32-bit and the 64-bit versions of the .NET Business Connector when running on a 64-bit OS. Because the 32-bit and 64-bit components run in different modes on a 64-bit computer, it is necessary to provide different installation paths during Setup.

2-13

Installation and Configuration in Microsoft Dynamics® AX 2009

NOTE: 64-bit Itanium is not supported.

Client Requirements The table lists the operating system requirements for the client computer. Operating System Requirements (32-bit or 64-bit) Windows XP Professional, Service Pack 2 (SP2) Windows Vista Business, Enterprise, or Ultimate (SP1) Windows Server 2003 Standard, Web, Enterprise, Datacenter (SP2) Windows Server 2003 R2 Standard, Web, Enterprise, Datacenter (SP2) Windows Server 2008 Standard, Web, Enterprise, Datacenter TABLE 2.3: OPERATING SYSTEM REQUIREMENTS

The table shows the software that is required for installing and running the Microsoft Dynamics AX client. Component

Version

State during install

Microsoft .NET Framework

3.5

Must be installed before the Microsoft Dynamics AX installation

Microsoft Windows Installer

3.0

Required

TABLE 2.4: SOFTWARE REQUIREMENTS

NOTE: The Setup Wizard does not install the Microsoft .NET Framework 3.5. If Microsoft .NET Framework 3.5 is not already on the computer it must be installed from the Microsoft Download Center.

Application Object Server Requirements The table lists the operating system requirements for the AOS computer. Operating System Requirements (32-bit or 64-bit) Windows Server 2003 Standard, Web, Enterprise, Datacenter (SP2) Windows Server 2003 R2 Standard, Web, Enterprise, Datacenter (SP2) Windows Server 2008 Standard, Web, Enterprise, Datacenter TABLE 2.5: OPERATING SYSTEM REQUIREMENTS

2-14

Chapter 2: Planning Microsoft Dynamics AX Install The table shows the software that is required for running for installing and running the Microsoft Dynamics AX AOS. Component

Version

State during install

Microsoft SQL Server Native Client

2005 or 2008

Must be present before installation

Microsoft .NET Framework

3.5

Must be present before installation

Microsoft Windows Installer

3.0

Must be present before installation

TABLE 2.6: SOFTWARE REQUIREMENTS

The computer that is running the AOS must also have access to computers in the same domain running only one of the following: •

SQL Server 2005 SP2, Standard or Enterprise editions



SQL Server 2008, Standard or Enterprise editions

To support alerts in Microsoft Dynamics AX, you must have access to an SMTP (Simple Mail Transfer Protocol) server.

Database Server Requirements Every Microsoft Dynamics AX installation requires a database server where all the system and application data is stored. There may be multiple AOS computers and multiple clients. However, they all rely on the resources that are provided by the database server. Because of such high database server usage, and for optimal performance, Microsoft Dynamics recommends dedicating a computer specifically for the database server. Microsoft Dynamics AX 2009 uses Microsoft SQL Server as its database system. The following tables list the database server requirements. The table lists the operating system requirements for installing and running the database server for Microsoft Dynamics AX 2009. Database

Operating System

Microsoft SQL Server

Any operating system supported by SQL Server

Oracle

Only Microsoft operating systems are supported

TABLE 2.7: OPERATING SYSTEM REQUIREMENTS

The table lists the supported SQL Server versions.

2-15

Installation and Configuration in Microsoft Dynamics® AX 2009 Microsoft SQL Server Versions Supported Use the table to determine which versions support reporting functionality. Implementers can find the minimum hardware and operating system requirements on the SQL Server Web site. Database version (32-bit or 64-bit) Microsoft SQL Server 2005, Standard or Enterprise (SP2) Microsoft SQL Server 2008, Standard or Enterprise TABLE 2.8: SUPPORTED SQL SERVER VERSIONS

Supported Collations Microsoft Dynamics AX supports Unicode collations. The requirements for the Unicode collation are that the collation must: •

Be case-insensitive, accent-sensitive, or wide-sensitive



Match the Microsoft Windows locale of the computers that are running instances of Application Object Server (AOS).

When implementers set up a new Microsoft Dynamics AX 2009 installation, the recommendation is that they use Windows collation instead of an SQL collation. For more information about how to select a collation for a SQL Server database, refer to the SQL Server documentation.

Database Server Requirements and File Server Requirements Oracle Database versions supported Microsoft Dynamics AX 2009 supports Oracle Database 10g R2 Standard or Enterprise, in either 32-bit or 64-bit.

Authentication requirements

2-16



Microsoft Dynamics AX 2009 requires that the database use Windows Authentication to authenticate users.



For Oracle, the Windows native authentication adapter must be installed and configured. See the Oracle 10g documentation for more information.

Chapter 2: Planning Microsoft Dynamics AX Install Other SQL Server Requirements The computer that is running the Microsoft Dynamics AX 2009 database server must have access to computers in the same domain that are running: •

Active Directory configured in native mode.



SQL Server 2005 or SQL Server 2008 Reporting Services, to support reporting functionality.



SQL Server 2005 or SQL Server 2008 Analysis Services, to support analysis functionality.

File Server Requirements Implementers may position the Microsoft Dynamics AX 2009 application files on any Windows-based computer. There are no minimum requirements identified for this computer. However, it must be equipped with a fast network connection and fast hard drives for optimal performance. The computer must also be part of a domain that has access to computers in the same Active Directory domain running Active Directory configured in native mode. NOTE: The application file share cannot be configured as a Distributed File System (DFS).

RAID Subsystem With an ERP system such as Microsoft Dynamics AX 2009, the database server generally stores a very large amount of important data for the business. If this data is unavailable for any length of time, the business could experience significant financial losses. Using a Redundant Array of Independent Disks (RAID) can help reduce the possibility of this loss occurring. Another important aspect for a database server is fine tuning for optimal performance. A RAID disk subsystem can also be used to help achieve this goal. RAID refers to a group of two or more disks managed as a single unit to store the data together with additional, or redundant, information to provide recovery if there is a disk failure. Usually a failed disk in a RAID system can be replaced while the server is still running. This is one benefit of RAID. NOTE: More Information on RAID can be found on the Microsoft MSDN Web site.

2-17

Installation and Configuration in Microsoft Dynamics® AX 2009 Read/Write Performance - Hardware RAID controllers divide read/writes of all data from Windows and applications such as Microsoft SQL Server into slices (usually 16 KB - 128 KB) that are spread across all disks participating in the RAID array. Splitting data across physical drives distributes the read/write I/O workload evenly across all physical hard disk drives participating in the RAID array. This increases disk I/O performance because the disks participating in the RAID array are all kept equally busy, instead of some disks becoming a bottleneck because of irregular distribution of I/O requests. Fault Tolerance - RAID provides protection from hard disk failure and accompanying data loss with two methods: mirroring and parity. There are many types of RAID configurations; each is called a RAID Level, but only some RAID levels typically used with Microsoft Dynamics AX 2009.

RAID 0 RAID 0, which is not recommended for use with Microsoft Dynamics AX 2009, is typically defined as a group of striped disk drives, without parity or data redundancy. RAID 0 arrays deliver the best data storage efficiency and performance of any array type.

FIGURE 2.9 RAID 0

2-18

Chapter 2: Planning Microsoft Dynamics AX Install RAID 1 RAID 1 is also known as disk mirroring. This is merely a pair of disk drives that store duplicate data, but appear to the computer as a single drive. All writes move to both drives of a mirrored pair so that the information on the drives is kept identical. However, each drive can perform concurrent, independent read operations. Mirroring therefore doubles the read performance of a single nonmirrored drive, while the write performance is unchanged. RAID 1 delivers the best performance of any redundant array type.

FIGURE 2.10 RAID 1

RAID 5 RAID 5 is also known as a Rotating Parity Array. RAID 5 works by striping data and parity across all the drives. Typically RAID 5 arrays offer similar read performance as pure striping, although writes are slower because the parity information is updated every time. If one hard disk fails, it merely has to be replaced with a new one of equal or larger size and it rebuilds from the parity on the remaining drives.

FIGURE 2.11 RAID 5

RAID 0+1 RAID 0+1, is a dual-level RAID and achieves a balance between the increased data availability of RAID 1, mirroring, and the increased read performance of RAID 0, striping.

2-19

Installation and Configuration in Microsoft Dynamics® AX 2009 Do not to confuse RAID 0+1 with RAID 10, they work differently and RAID 0+1 is what is recommended.

FIGURE 2.12 RAID 0+1

For maximum performance configure the database server such as the following example: •

Two disk RAID 1 for the operating system and database software



A small, four disk RAID 0+1, or two disk RAID 1 for database logs



A larger RAID 0+1 for the main database files o

To reduce cost, swap out the RAID 0+1 for a RAID 5. However, this will result in slower performance.

Disaster Recovery It is important to prepare for future catastrophes. All companies should have a thorough Disaster Recovery Plan that describes what the company will do if a disaster happens. To determine what provisions to make for partial or complete loss of data, stakeholders must determine the total cost of rebuilding or replacing the organization's data. Consider the following: •

What are the costs of reconstructing the organization's financial, personnel, and other business data?



What does the business insurance cover with regard to replacing lost data?



How long would it take to reconstruct the business’ data? How would this translate into lost future business?



What is the cost per hour of server downtime?

Planning Disaster Recovery It is necessary to create a disaster recovery plan to make sure that all the systems and data can be quickly restored to regular operation if there is a disaster. When creating a disaster recovery plan, determine, and prepare for all the steps that are required to respond to each type of disaster. It is important to test the recovery steps in the disaster recovery plan by simulating a catastrophic event.

2-20

Chapter 2: Planning Microsoft Dynamics AX Install A disaster recovery plan can be structured in many different ways and can contain many types of information. Disaster recovery plans can include the following: •

Information on who owns the administration of the plan



A list of people to be contacted if there is a disaster and instructions on how to contact them



A list of potential disasters and a checklist for recovery from each disaster scenario



Procedure for performing backups



Off-site storage policies



Procedures for restoring servers and the network



A plan to obtain hardware, if it is necessary



How long recovery will take and the final database state the users can expect



Steps for reviewing the documentation whenever changes are made to the computers or network.

Disaster Readiness The following are activities to perform to make sure that the business is ready for disaster: •

Perform regular backups of the system and user databases, transaction log, and the Microsoft Dynamics AX application files to reduce how much lost data. o



How frequently a company performs backups depends on how much information that they can afford to lose compared to the overhead of performing backups too frequently.

Thoroughly test backup and recovery procedures on a regular, scheduled basis. o o o o o o

Testing makes sure that the backups are restorable and that the recovery procedures are clearly defined and documented. Make sure to document the following: Database and file user rights Product keys for all the software Service packs installed on Microsoft Windows, the database, and Microsoft Dynamics AX Documentation that relates to the recovery of other databases, such as the Windows SharePoint Services.

2-21

Installation and Configuration in Microsoft Dynamics® AX 2009

Staff Skills Review Although a successful implementation requires specific hardware and software components, it also requires a skilled staff to plan and implement the project. Whether in-house personnel or hired consultants, the staff must have expertise across various software areas. Some areas require more proficiency and skill, while others areas require a general level of understanding. Areas of Proficiency The areas in which the implementer must be proficient include the following: •

Windows Server 2003 or 2008



Microsoft Exchange 2003 or 2007



Active Directory



Domain Controllers



Domain Name Services



Networking



SQL Server 2005 or 2008



SQL Reporting Services



SQL Analytical Services



Visual Studio



Internet Information Services



SharePoint Services



.NET



Web services

Important Areas of Knowledge There are some areas of knowledge the implementer must have to successfully install Microsoft Dynamics AX 2009. These are areas where the implementers must have more proficiency and skill. The following is a summarized list of the topic areas:

2-22



Windows Server 2003 or 2008



Deployment Issues



Active Directory



SQL Server 2005 or 2008



Networking

Chapter 2: Planning Microsoft Dynamics AX Install Windows Server 2003 or 2008 •

Security features and requirements



Availability and scalability features

Deployment Issues •

The different variations of the domain topology and placement of servers and users supported with Microsoft Dynamics AX 2009 o

The customer's hardware requirements based on: o Number of users o Number of users who access the system at the same time o Level of downtime the customer will accept o Response time that is required from the servers o Amount of data expected to be created o Customer's budget

Active Directory •

Microsoft Dynamics AX 2009 components must be installed within the same domain.



Active Directory system administration functions including user creation and group membership. During installation, the implementer must set up user accounts and apply the correct permissions.

SQL Server •

Install SQL Server, set up a database maintenance plan, create indexes, and create jobs.



Move SQL logs to a different drive.



Select an appropriate RAID configuration.



Recommend a backup strategy to protect the customer's data.

Networking •

Troubleshoot networking issues related to latency and bandwidth.



Troubleshoot network connectivity issues.



Determine networking hardware and how they interrelate with one another and Microsoft Dynamics AX 2009.

Employee training is an investment. It can help employees start the correct way, make sure employees understand expectations, and complete their skill sets. There are many online resources available to help employees obtain the skills they need.

2-23

Installation and Configuration in Microsoft Dynamics® AX 2009 Short Answer What are the important topic areas for installing Microsoft Dynamics AX?

Naming Convention Because it is possible to have multiple applications, the naming convention is a very important aspect of any installation. A good practice is to use a name that clearly identifies the customer, version, and type of installation. The recommended name includes a short form of the customer name, the Microsoft Dynamics™ AX 2009 version, the service pack version, and a code for the installation type, such as Live, Test, or Dev.

Example The CON_AX2009_Live name signifies that this is a live, or production installation of Microsoft Dynamics AX 2009 without any service packs for the Contoso Entertainment customer. If the administrator wanted to track service packs, the name could be changed to CON_AX2009_SPxx_Live. where xx would be the number of the service pack installed. One reason for a good naming convention is that the Microsoft Dynamics AX client or AOS configuration links the application object together with the database. If the names are not clear, it is easy to accidentally set up a client to use development application objects and connect to a production database. This could result in lost or corrupted data. NOTE: Always use alphanumeric characters meaning a-z and 1-0. Do not use special characters such as # & ( ) and so on. Do not use blank spaces in names or directories, use - (dash) or _ (underscore) instead.

2-24

Chapter 2: Planning Microsoft Dynamics AX Install Follow good naming conventions for the database, application, client, and instance names, as follows: Install Type

Base Role

Good Naming Convention

Live Environment

Database Name Application Name AOS Name Client Name

CON_AX2009_DB_Live CON_AX2009_APP_Live CON_AX2009_AOS_Live CON_AX2009_Client_Live

Test Environment

Database Name Application Name AOS Name Client Name

CON_AX2009_DB_Test CON_AX2009_APP_Test CON_AX2009_AOS_Test CON_AX2009_Client_Test

Development Environment

Database Name Application Name AOS Name Client Name

CON_AX2009_DB_Dev CON_AX2009_APP_Dev CON_AX2009_AOS_Dev CON_AX2009_Client_Dev

NOTE: Be aware of possible customer sensitivity with regard to using the company name as part of the naming convention. Be certain that the naming convention is decided together with company executives.

Summary A successful implementation of Microsoft Dynamics AX 2009 depends on good preparation. When a company is suitably prepared for the Microsoft Dynamics AX 2009 installation, it enables the rest of the implementation to be a more straightforward process. To prepare for a successful implementation, companies must make sure of the following: The network infrastructure will handle the increased network traffic and deliver reliable network connections for the Microsoft Dynamics AX 2009 components. The company's hardware and software is compatible with Microsoft Dynamics AX 2009 components for the best interaction and least trouble. The staff's skills are appropriate to use and manage Microsoft Dynamics AX 2009 components and modules. After the preparation steps are complete, the implementer can move on to installing Microsoft Dynamics AX 2009. The section titled “Installing a Development System,” takes a step-by-step approach to installing the base Microsoft Dynamics AX 2009 components.

2-25

Installation and Configuration in Microsoft Dynamics® AX 2009

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

2.

3.

2-26

Chapter 2: Planning Microsoft Dynamics AX Install

Solutions Plan System Topology Short Answer 1 What information must be obtained before you install Microsoft Dynamics AX? MODEL ANSWER - Define and document: Number of transactions, Number of users, Uses of system (modules and features to be implemented), External user access required, Web access required, Required availability, Projected growth rate Number of sites Evaluate and document the existing infrastructure: Existing hardware, Bandwidth, Operating system, Databases present, Applications to integrate

Short Answer 2 What are the three servers required for a basic installation of Microsoft Dynamics AX without external users? MODEL ANSWER - – Domain controller – AOS and Application file server – Database

Staff Skills Review Short Answer What are the important topic areas for installing Microsoft Dynamics AX? MODEL ANSWER - - Windows Server 2003 - Deployment issues Microsoft® Active Directory® - SQL Server 2000 or 2005 - Networking

2-27

Installation and Configuration in Microsoft Dynamics® AX 2009

2-28