A Microsoft Dynamics AX system is comprised of the following core computer roles:
Application Object Server (AOS)
An AOS:
- Is a Microsoft Windows service that controls communications among Microsoft Dynamics AX clients, databases, and applications.
- Can be installed on a single computer, or on a cluster using Windows load-balancing.
Microsoft Dynamics AX requires Windows-integrated authentication for all servers in the system, which means that you must have an Active Directory directory service system. For security reasons, the AOS must be installed on Windows Server 2003.
A system used for demonstrations, development or test can be set up to use more than one AOS instance.
Database
A Microsoft Dynamics AX database stores your Microsoft Dynamics AX data as part of an existing Microsoft SQL Server or Oracle database server installation. The database server must be set up with Windows authentication.
File server
The application file server contains the files in which the Microsoft Dynamics AX business logic is stored. Examples of the files in this directory include indexes, headers, and labels for each layer. The directory must be accessible to all AOS computers. Permissions on this directory should be highly restrictive because data stored can include sensitive customer data. Only the AOS Windows service and Microsoft Dynamics AX administrators should have write access to the directory. Client computers do NOT require access to the directory, and such access should not be granted.
Client
The interface to Microsoft Dynamics AX data and functionality.
When you use extended Microsoft Dynamics AX functionality, additional computer roles can be added to your system. None of these roles are required.
Enterprise Portal server
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.
Reporting server
A reporting server adds to the reporting functionality within Microsoft Dynamics AX by linking Microsoft Dynamics AX to Microsoft SQL Server Reporting Services. A reporting server provides enhanced support for ad hoc reporting.
Application integration server
An application integration server provides support for sharing data from Microsoft Dynamics AX with external parties, such as vendors and customers. It supports many scenarios, including Orders-to-Cash, Procure-to-Pay, and other enterprise application integration. It runs the Application Integration Framework (AIF), a document-based integration interface.
Custom client
A custom client is an application written by a partner or customer to access Microsoft Dynamics AX data. Custom client applications use an integration component--either the Microsoft .NET Business Connector or the COM Business Connector to connect to Microsoft Dynamics AX.
OLAP server
An OLAP server adds to the reporting functionality within Microsoft Dynamics AX by linking Microsoft Dynamics AX to SQL Server Analysis Services. An analysis server provides enhanced support for online analytical processing (OLAP).
The following common roles are also found in infrastructures that are running Microsoft Dynamics AX. This documentation does not include content on how to set them up, but provides information on how to use Microsoft Dynamics AX with them.
Messaging server
A messaging server enables sending and receiving e-mail messages and instant messages. Microsoft Dynamics AX can use e-mail to send alerts to users. Microsoft Dynamics AX requires a messaging server that supports SMTP.
Firewall server
A firewall server is part of a security system that helps protect a network from external threats, originating outside the network.
Aucun commentaire:
Enregistrer un commentaire