Monitoring Microsoft Dynamics AX with Operations Manager enables administrators to proactively react to changes in the overall health of the AX environment and to adjust the system for optimal performance and reliability.
With this management pack, operators and administrators can view information about all Application Object Server (AOS) instances in the environment, take AOS servers offline for maintenance, and troubleshoot problems with AOS instances.
System Requirements
The System Center Management Pack for Microsoft Dynamics AX 2012 is cumulative for all versions of Microsoft Dynamics AX 2012, including the following:
- Microsoft Dynamics AX 2012
- Microsoft Dynamics AX 2012 Feature Pack
- Microsoft Dynamics AX 2012 R1
- Microsoft Dynamics AX 2012 R2
- Microsoft Dynamics AX 2012 R3
The System Center Management Pack for Microsoft Dynamics AX 2012 works with the following versions of System Center Operations Manager:
- System Center Operations Manager 2007
- System Center Operations Manager 2007 R2
- System Center Operations Manager 2012
- System Center Operations Manager 2012 R2
- System Center Operations Manager 2016
Installation
- Download the System Center Management Pack for Microsoft Dynamics AX 2012
- Extract the msi file in a default folder
- Import the mp files using the Operations Manager Console
Configuration
- Install the Operation Manager agent on all computers of the Dynamics AX infrastructure (AOS servers, database server, Enterprise Portal, Reporting Services, etc).
- Configure Run As Accounts for the Microsoft Dynamics AX 2012 Run As Profiles
Microsoft Dynamics AX 2012 administrator account. The account that is associated with this profile is used to run Microsoft Dynamics AX services. The account should be an administrator in Microsoft Dynamics AX. This user account should also be a member of the BUILTINAdministrators group on each monitored computer.
Microsoft Dynamics AX 2012 database reader account. The account that is associated with this profile is used to discover the Microsoft Dynamics AX environment. This account must have read access to the master database, as well as several tables in the Microsoft Dynamics AX database. We strongly recommend that you associate the AOS Service account with this account.
- Configure Run As Profiles.
Using the Monitoring Pack
To see an overview of the Dynamics AX Environment Health, select the Monitoring pane, click Microsoft Dynamics AX 2012, click on Health Environment. If you want to see a diagram that shows the health state of the environment components
To check the details of health state, open the Health Explorer
In this window, you will find the details of the health issue, the causes, and the resolution.
View Events from multiple AOS server in a single location
The management pack collects the most important events generated on the AOS server. Most informational events are not collected. Select the Monitoring pane, Application Object Servers (AOS), and click on Events.
Measure the activity using counters
The performance counters that are monitored for Microsoft Dynamics AX processes are a subset of those available for monitoring Windows services.
To view AOS counter, select the Monitoring pane, click Microsoft Dynamics AX 2012, click Application Object Servers (AOS), click Performance, and then click Process.
Make the administrative tasks simpler
This task enables you to work with AOS instances directly, without having to move work in Microsoft Dynamics AX. You can use tasks to manage and monitor settings for the AOS instances on a server.
To access tasks, select Monitoring pane, click Microsoft Dynamics AX 2012, click Application Object Servers (AOS), and then click Instances.
The available tasks are shown in the tasks pane on the right, and include:
For example, if you select View online users it reports all online users from all AOS instances in an environment:
Enjoy
Said Nikjou P.
Senior Premier Field Engineer
This post first appeared on MSDN Blogs | Get The Latest Information, Insights, Announcements, And News From Microsoft Experts And Developers In The MSDN Blogs., please read the originial post: here