Microsoft Dynamics AX provides a set of Web modules that give you access to Microsoft Dynamics AX data and allow you to participate in business processes using Web-based Microsoft Dynamics AX forms. These modules and the portal system are collectively called Enterprise Portal. Enterprise Portal is built on Microsoft Windows SharePoint Services or Microsoft Office SharePoint Server.

Microsoft Dynamics AX and the Enterprise Portal framework include customizable home pages called Role Centers. Role Centers display reports and other business intelligence information, transaction data, alerts, links, and common tasks associated with a user's role in the company. Role Centers are available in both Enterprise Portal and the Microsoft Dynamics AX Windows client.

Factors impacting Enterprise Portal topology

  • Internet Information Services (IIS) and either Windows SharePoint Services (WSS) or Microsoft Office SharePoint Server are the primary requirements for Enterprise Portal. For up-to-date hardware and software requirements for Microsoft Dynamics AX, see the system requirements Web page.

  • You can deploy Enterprise Portal on the same IIS server or IIS farm where you deploy Workflow, Application Integration Framework (AIF) Web services, and Reporting Services. However, we recommend using a dedicated IIS server or IIS farm for deploying Enterprise Portal.

  • Consider the following information when you calculate expected workload for the Enterprise Portal server:

    • All Web users access the Microsoft Dynamics AX application through Enterprise Portal.

    • All browser-based clients and Microsoft Dynamics AX Windows clients access Role Centers through Enterprise Portal. Microsoft Dynamics AX Windows clients use a browser control to display Role Centers.

    • Enterprise Portal uses the Report Viewer Web part to display reports that exist on the SQL Server Reporting Services server.

    • Enterprise Portal uses ASP.NET user controls and the Enterprise Portal framework to display Microsoft Dynamics AX data and reports.

    • Enterprise Portal uses .NET Business Connector to interact with the Application Object Server (AOS).

  • If you have external users who require access to Enterprise Portal, you need to carefully plan your Active Directory user topology and use either a standard perimeter network or traditional perimeter network. For more information about setting up a perimeter network, Web users, and Active Directory topology, see Active Directory user topology.

Sample deployment scenarios

Sample deployment scenarios are provided to assist you in planning your infrastructure and server requirements. The sample deployment scenarios range from a single server deployment to a large-scale distributed deployment. These scenarios do not provide any infrastructure sizing guidelines. For more information, see Sample deployment scenarios.