Monitoring from global distributed locations helps to see your applications as perceived by your end user community. However, in some situations, companies would like to check response times and availability of their application within their local network. There are two cases in which customers decide to use a private agent:
- The application under monitoring is not available from the Internet
- Performance and uptime comparison – Lan vs WAN
Both are good reasons and therefore we provide a private agent which can be installed on a dedicated Windows Server within your data center. Once the private agent has been installed you can configure ServerView, UserView or BrowserView monitoring scripts to be executed on this internal private agent.
This guideline walks you through all steps required to prepare the installation, execute the setup and configure your devices to use the private agent. Additionally, it provides some answers to frequently asked questions.
- 2-core CPU or higher
- 8GB RAM
- 2 GB Hard Drive space +1MB per monitoring results saved
- OS Windows Server 2008 R2 or higher 64bit
- .NET Framework 4.5 (exactly 4.5)
- Windows Media Player
- Administrative Access
We highly recommend using a dedicated Windows Server for your private agent installation. Depending on the number of monitoring devices you are going to simulate on your private agent, the load can be high and can have an impact on CPU or Memory utilization of this server.
Follow all preparation steps below once you’ve selected your private agent server.
|1 Open Server Manager||
Click the Server Manager icon
Click Add roles and features
Click 4 x Next until Features is selected
Select User Interface and Infrastructure / select all check boxes below
Select Media Foundation
Select .Net Framework 4.5 Features and all Items below
Close the Server Manager dialog
|8||Restart your Windows Server|
Once all preparation steps are done you can install the private agent software on your server. This section covers all installation steps. Follow those instructions step by step.
|1 Account with Admin Permission||You will need an account with Admin permission for this Private Agent installation. Ask your domain admin to get administrative rights on your Windows Server.|
|2 Configure Private Agent||
2.1 Login to your DCM Account
2.2 Click Configure / Private Agent
2.3 Click Add Agent
2.4 Add the Agent details such as Name and Description
2.5 Click the Add button
Then new Private Agent will appear
|3 Setup Private Agent||
3.1 Login to your Windows Server (with Admin Account)
3.2 Start a browser on your Windows Server
3.3 Login to your DCM Account
3.4 Click Configure / Private Agent
3.5 Click Download Private Agent
If the Download Private Agent button is disabled, please contact dotcom monitor support team.
3.6 Click Download
3.7 Click the Save button in the displayed popup
3.8 Click the Run button after all files have been downloaded
3.9 Click Next in the Setup Wizard
3.10 Select I accept and click Next
3.11 Click Next to confirm the Destination Folder
3.12 Click Install
3.13 Click Finish
3.14 The Private Agent Registrator dialog appears
Add your DCM User ID and Password
3.15 Summary Dialog
Make sure that all prerequisites are completed
3.16 Choose the Private Agent in the list
3.17 Review your details and click Continue
3.18 Registration of Private Agent will take a few minutes
3.19 Dialog Setup Successful, Click Close
|4 Check Services on your Windows Server||
4.1 Open Service Overview on your Windows Server
There are 5 services with the name Dotcom-Monitor Private Agent
Those are used to simulate up to 5 monitoring devices in parallel
|5 Check User on your Windows Server||
5.1 Open Task Manager
Check if there is a user called DotcomMonitorRdpUser
6.1 Restart your Windows Server
In some cases, the Private Agent can’t be used without a restart. It’s recommended to restart your Windows Server now.
|1 Login DCM Account||Use your DCM account and login|
|2 Configure a Device to use Private Agent||
2.1 Open the Device Manager
2.2 Select a Device / Select Edit from context Menu
2.3 Select the new Private Agent
2.4 Scroll Down / Click Continue
2.5 Scroll Down / Click Continue
2.6 Click on Return to Device List
Question: Why are there 5 Dotcom-Monitor Private Agent Services?
Question: Why is there a new DotcomMonitorRdpUser on my Window Server?
Question: Will this DotcomMonitorRdpUser block a Client RDP License?
Question: How many Private Agents will be required?
Those services are used for executing monitoring devices on your new Private Agent. After the installation one of those is running and the other four are in the Manual Start Type. Each of those services can run a single monitoring device in parallel. If you configure multiple monitoring devices to run on your Private Agent those services will be started and used to execute your devices.
This user has been created during the private agent installation. It will be used for the communication with the dotcom-monitor private agent services and is required for execution of monitoring devices on your private agent server
Our DotcomMonitorRdpUser will block one RDP License. After the private agent has been installed you won’t be able to establish two parallel RDP connections to your private agent server.
Avoid overload situations. If you configure 20 devices to run on a 5-minute frequency and each device will take 5 minutes to complete, the Private Agent won’t be able to execute those. The number of Private Agents required depends on:
- Execution Frequency
- Execution Duration of your Devices
# Private Agents = ((# Devices * Duration (min)) * (1 / Frequency (min)) / 5 Devices in parallel
5-minute Execution Frequency
5-minute session time of each device (Duration)
# Private Agents = ((20 * 5)*(1 / 5) / 5 = 4 PA will be required