Axapta 2009 Software and Hardware Requirements

three logical software components that are installed individually:
• Axapta client
• Axapta application
• Axapta Object Server (AOS)

General Recommendations
If you are a developer, system administrator, or a technically minded consultant installing a demo system, we recommend the following:
• Windows XP Professional, at least for the machines on which you plan to install server components.
• A minimum of an Intel Pentium III–class 1GHz CPU or equivalent AMD; an Intel Pentium 4 is best. An Intel Pentium II–class CPU will tax your patience and take the fun out of learning Axapta.
• A minimum of 512MB RAM—more is better, particularly on the systems where you plan to install server components.
• A decent 17-inch screen. We recommend the largest screen you can get your hands on. If you are a developer, having a system with two 19-inch screens is really great when you need to debug and/or run other applications, like Visual Studio, side by side with Axapta.

• At least 10GB of hard disk space, depending on how many companies and databases you will be setting up. The more drive space, the better.

Minimum Requirements

• Operating systems: Windows XP, Windows NT 4.0 Service Pack (SP) 6a, Windows 2000,Windows 2003, Windows 98. The Axapta Object Server requires the ability to run a Windows service, which excludes Windows 98 for the server. Windows 98 systems can be used as clients, but Windows 98 support is, for all practical purposes, discontinued by Microsoft Business Solutions. Actually, it was discontinued and then revived because of the installed base of clients, but it is not likely to be supported in Axapta 4.0. We highly recommend not using Windows 98. For the same reasons, we highly recommend not using Windows NT 4.

• Client hardware:Currentminimum hardware requirements for a client are officially 233MHz, 64MB RAM, 10Mbps network connection, or ISDN.Microsoft Business Solutions does not state which CPU it is referring to in the clock frequency specification. In practice, a low-end Intel Pentium II will do, but make sure you have at least 128MB RAM.

• Database: Stand-alone database server hardware sized according to the database of your choice—Microsoft SQL Server or Oracle—and the level of optimization desired. We also recommend the latest service pack. This system is either accessed directly by the Axapta clients or Axapta Object Servers that use it to persist data. Business applications are typically data-bound, so you need to pay particular attention to throughput, disk space scalability, network accessibility and latency, up time, and data security. Make sure someone who understands database performance and reliability configures this server for you. It’s wise to use multiple arrays and channels.

• Axapta application server: This is basically a file server where you can install as many Axapta application environments as you like. For example, developers typically have one for each customer, since customer-specific customizations must be maintained separately. So, you need to consider the same characteristics as those for a database: throughput, disk space scalability, network accessibility and latency, up time, and data
security. The data on this server is stored directly in the file system, so get the fastest hard disks you can afford.

• Axapta Object Server: This is the server that executes code on behalf of clients operating in 3-tier mode and communicates with the database system for thin clients. You can have multiple AOSs in a clustered environment. One of your AOSs will also need to run a server manager that takes care of starting up servers as required, grouping servers in clusters, and performing a simple round-robin form of load balancing. You need to keep in mind throughput, network accessibility and latency, up time, and CPU power, as these nodes crunch through much of the interpreted X++ code and meta data definitions of your system on behalf of Axapta clients, as well as data access in the case of thin clients in 3-tier mode.

Often, customers will choose to combine their application server and AOS into one server.

• Testing or development server: For this server, you should take into account all of the recommendations made for the preceding servers. It can also act as a redundant AOS, application, or database server in the case of a major failure.