Академический Документы
Профессиональный Документы
Культура Документы
0 Install
Introduction
To successfully install Microsoft Dynamics AX 4.0, the application infrastructure
must comply with Microsoft Dynamics AX 4.0 system requirements. These
requirements include the following:
Scenario
Global Trade and Manufacturing (GTM) is a mid-sized manufacturer of various
light products. Although their customer base spans multiple countries, their target
is mainly North America. They plan to use Microsoft Dynamics AX 4.0 to take
advantage of the integration with their existing Microsoft products.
GTM uses many of the Microsoft products that will be required during the
Microsoft Dynamics AX 4.0 implementation. The company will hire consultants
to implement the system, but will use GTM in-house resources for ongoing
maintenance of the system.
Problem
GTM's in-house staff has experience using Microsoft Windows Server 2003,
Microsoft® Active Directory®, and Microsoft® SQL Server®, but 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 GTM is to have all the critical skills covered for the Microsoft
Dynamics AX 4.0 implementation. This includes Windows Server 2003,
deployment issues, Active Directory, SQL Server, and Networking. In addition,
it will help if users have proficiency in several other areas including Microsoft
Exchange, Domain Controllers, SQL Reporting Services, and Web Services.
Solution
To make sure all the critical skills are covered for the Microsoft Dynamics AX
4.0 implementation, GTM will have to find consultants with the required skills
that GTM does not have in-house. Because the GTM staff has Windows Server
2003, Active Directory and SQL Server skills, they will have to use
implementation consultants with deployment and networking skills.
Database
A database stores the Microsoft Dynamics AX 4.0 data as part of an existing
Microsoft SQL Server database server installation. When setting up the database
server, make sure to use Windows authentication.
File server
The application file server contains the files in which the Microsoft Dynamics
AX 4.0 business logic is stored. Examples of the files in this directory include:
• Indexes
• Headers
• Labels for each layer
Permissions on this directory must be highly restrictive because stored data can
include sensitive customer data. Only the AOS Windows service and Microsoft
Dynamics AX 4.0 administrators can have write access to the directory. Client
computers do not require access to the file server directory, and for security
reasons, make sure that the clients are not granted access.
Client
The client is the user interface to Microsoft Dynamics AX 4.0 data and
functionality.
Core Topologies
If there are no users outside the domain (external users) that must access data,
then use one of the following basic topologies, the minimal core installation or
the clustered core installation.
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.
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 4.0.
NOTE: The organizational unit can contain other organizational units, as long as the
top node is associated with Microsoft Dynamics AX 4.0.
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 to allow access to that computer.
Factor Description
Number of Transactions The total average number of the following
per Hour 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 4.0 a transaction is
defined a single line item. For example, a sales
order with 1000 line items would be considered as
1000 transactions.
Number of Concurrent A key indicator of the size of the Application
Users Object Server system needed. It also affects the
appropriate bandwidth and latency for the network.
Number of Concurrent A key indicator of the size of the Windows
Enterprise Portal Users SharePoint Server system needed.
Number of Remote The number of remote connections affects the
Connections 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: HARDWARE FACTORS
Network Requirements
Table 2.2 lists the minimum network requirements for client/server connections
in a Microsoft Dynamics AX 4.0 system.
The following formula expresses the total response time for running a task in
Microsoft Dynamics AX 4.0:
Domain Requirements
The computers that are running Microsoft Dynamics AX 4.0 components must
have access to each other in the same Active Directory directory service domain
running Active Directory configured in native mode. If Active Directory in not
configured in native mode then Microsoft Dynamics AX 4.0 may not be able to
authenticate with other computers on the network.
Client Requirements
Table 2.3 lists hardware requirements for installing and running the Microsoft
Dynamics AX 4.0 client from a workstation. Table 2.4 lists the operating system
requirements for the client computer. Table 2.5 shows the software required for
installing and running the Microsoft Dynamics AX 4.0 client.
NOTE: Microsoft supports installing Microsoft Dynamics AX 4.0 on the 64-bit versions
of the operating systems listed, but runs in 32-bit mode if installed.
NOTE: The Setup Wizard installs the U.S. English version of the Microsoft .NET
Framework version 2.0. If an alternate language of the .NET Framework is needed, it
can either be downloaded and instaledl beforeinstalling Microsoft Dynamics AX 4.0, or
reinstalled in the language of choice after installing Microsoft Dynamics AX 4.0.
NOTE: Microsoft supports installing Microsoft Dynamics AX 4.0 on the 64-bit versions
of the operating systems listed, but runs in 32-bit mode if installed.
The computer that is running the AOS must also have access to computers in the
same domain running only one of the following:
To support alerts in Microsoft Dynamics AX 4.0, the system must have access to
an SMTP (Simple Mail Transfer Protocol) server.
The following tables list the database server. Table 2.9 lists software
requirements for installing and running the SQL Server on Microsoft Dynamics
AX 4.0. Table 2.10 lists the supported SQL Server versions.
Database version
Microsoft SQL Server 2005, Enterprise Edition, SP1 or later
Microsoft SQL Server 2005, Standard Edition, SP1 or later
Microsoft SQL Server 2000, Enterprise Edition, SP4 or later
Microsoft SQL Server 2000, Standard Edition, SP4 or later (Demo only,
no reporting support)
TABLE 2.10: SUPPORTED SQL SERVER VERSIONS
NOTE: Microsoft supports installing Microsoft Dynamics AX 4.0 on the 64-bit versions
of the operating systems listed, but runs in 32-bit mode if installed.
Supported Collations
Microsoft Dynamics AX 4.0 supports Unicode collations. The requirements for
the Unicode collation are that the collation must:
• Be case-insensitive
• Match the Microsoft Windows locale of the computers running
instances of Application Object Server (AOS).
Authentication requirements
Other Requirements
The computer running the Microsoft Dynamics AX 4.0 database server must
have access to computers in the same domain that are running:
NOTE: The share where the application files are installed cannot be configured as a
Distributed File System (DFS).
RAID Subsystems
With an ERP system like Microsoft Dynamics AX 4.0, 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 suffer significant
financial losses. One of the most important aspects of fine tuning a database
server for optimal performance is driving subsystem performance. To accomplish
this goal we use Redundant Array of Independent Disks (RAID). Briefly, this
refers to a group of two or more disks managed as a single unit to store the data
along with additional, or redundant, information to provide recovery in the event
of a disk failure. Usually a failed disk in a RAID system can be replaced while
the server is still running. This is a benefit of RAID.
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.
Fortunately for us, there are only a few RAID levels commonly used with
Microsoft Dynamics AX 4.0. We are now going to look at those that might be
choosen for a Microsoft Dynamics AX 4.0 installation.
RAID 1 is also known as disk mirroring, which is simply a pair of disk drives
that store duplicate data, but appear to the computer as a single drive. All writes
go to both drives of a mirrored pair, so that the information on the drives is kept
identical. However, each individual drive can perform simultaneous, independent
read operations. Mirroring thus doubles the read performance of a single non-
mirrored drive, while the write performance is unchanged. RAID 1 delivers the
best performance of any redundant array type.
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.
For maximum performance, configure the database server with a RAID 1 with 2
disks for the operating system and database software, a small RAID 0+1, with 4
disks or RAID 1 with 2 disks for database logs, and a larger RAID 0+1 for the
main database files. To reduce cost, swap out the RAID 0+1 for a RAID 5 for the
database files, but this results in slower performance.
Naming Convention
Since 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
version, the service pack version, if used, and a code for the installation type,
such as Live, Test, or Dev.
Example
The GTM_AX40_Live name signifies that this is a live, or production
installation of Microsoft Axapta 4.0 without any service packs for the Global
Trade & Manufacturing customer. If there are service packs installed, then
change the name to GTM_AX40_SPxx_Live.
One of the reasons for a good naming convention is that the Microsoft Dynamics
AX client or AOS configuration links the application object 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, which
could result in lost or corrupted data.
NOTE: Always use alphanumeric characters meaning a-z and 1-0. Do not use special
characters like # & ( ) and so on. Do not use blank spaces in names or directories, use
− (dash) or _ (underscore) instead.
Follow good naming conventions for the database, application, client, and
instance names, as follows:
NOTE: Be aware of possible customer sensitivity in regard to using the company name
as part of the naming convention. Be certain that the naming convention is decided upon
in conjunction with company executives.
Areas of Proficiency
The areas in which the implementer must be proficient include the following:
Deployment Issues
At minimum, implementers must be proficient in the following deployment
areas:
Active Directory
At minimum, implementers must be proficient in the following Active Directory
areas:
SQL Server
At minimum, implementers must be proficient in the following SQL Server
areas:
Networking
At minimum, implementers must be proficient in the following Network areas:
Conclusion
A successful implementation of Microsoft Dynamics AX 4.0 depends on proper
preparation. When a company ensures its readiness for the Microsoft Dynamics
AX 4.0 installation, it allows the rest of the implementation to be a more
straightforward process.
The network infrastructure will handle the increased network traffic and deliver
reliable network connections for the Microsoft Dynamics AX 4.0 components.
The company's hardware and software is compatible with Microsoft Dynamics
AX 4.0 components for the best interaction and least trouble.
The staff's skills are appropriate to use and manage Microsoft Dynamics AX 4.0
components and modules.
After the preparation steps are complete, the implementer can move on to
installing Microsoft Dynamics AX 4.0. The section titled "Installing a Core
System," takes a step-by-step approach to installing the core Microsoft Dynamics
AX 4.0 components.
1.
2.
3.