# Enterprise Edition - Probe Server

Enterprise Edition allows you to configure independent Applications Manager installations to monitor various resources and then collectively view the data from all these independent Applications Manager installations known as **Probe Servers**, from a single master server known as **Central Server**.

During installation, you need to select 'Enterprise Edition'. Next select the installation type as 'Probe Server'. Consequently, you need to enter the *HostName, SSL & webserver port* of the *Central Server*, to which the Probe Server is going to be connected. Probe Server's function is similar to that of a standalone Applications Manager, with the user configuring the various monitors, thresholds and alarms. HTTPS mode of communication is used for the communication with the Central Server.

Using the *Jump To* link in the Central Server (just above the toolbar) you can view the Probe Server web console.

- [Probe Server Configuration](https://www.manageengine.com/products/applications_manager/help/enterprise-managed-server.html#config)
- [Probe Server Actions](https://www.manageengine.com/products/applications_manager/help/enterprise-managed-server.html#actions)
- [FAQ](https://www.manageengine.com/products/applications_manager/help/enterprise-managed-server.html#faq)

**Note:**

- To **change a Professional Edition to Probe Server**, go to *Global Settings*, select '**Convert standalone server into Probe Server**'. This option is available only if you have installed the full build and not for upgrades through PPM.
- You need to make the following changes in the `Product_Home/conf/AMServer.properties` file and restart the server to convert to the Probe Server.

  ```properties
  am.ssl.enabled=true
  am.server.type=MAS
  am.adminserver.host=Central Server Host Name
  am.adminserver.port=Central Server SSL Port
  ```

- Visit [Enterprise Edition FAQ](https://www.manageengine.com/products/applications_manager/applications-management-productfaq.html#enterprise) for details on when to, how to set up Enterprise Edition.

## Probe Server Configuration

The Probe Server automatically gets registered with the Central Server when it starts up. In case you want to edit the configuration, go to **Settings** tab. Click on Probe Servers link. This will take you to the Probe Server page from where you can configure the Probe Servers. Alternatively, this can be done by clicking on the Probe Servers link just below the main tabs.

**Steps to add a Probe Server**

1. Click on the **Add New** link to open the **Add New Probe Server** form.
2. Enter the **Display Name** of the Probe Server.
3. Enter the **Probe Server Group** to which the Probe Server belongs.
4. Enter the **Host Name** of the Probe Server.
5. Enter the **External Host Name** used to access the Probe Server externally, if it differs from the host name.
6. Enter the **Web Server Port**, which is the port used by the web client to connect to the Probe Server.
7. Enter the **SSL Port**, which is the port used for secure communication between the Central Server and the Probe Server.
8. Enter the **Server ID**. You can find this ID in the *Installation Information* table under **Settings** > **Tools** > **Support** on the Probe Server.
9. Enter the **Sync Retry Count**, which specifies the number of times the Central Server retries fetching data from the Probe Server if synchronization fails.
10. Enter the **Sync Timeout**, which specifies the HTTP timeout (in seconds) for the Central Server to wait for a response from the Probe Server during data synchronization.
11. Enter the **Admin Password** for the Probe Server.
12. Configure **E-mail me when the status of this server is up/down** to receive email notifications when the Probe Server goes down or becomes available again. Select **Choose Admin Email** to use an administrator email address, or select **Select Email Actions** to choose a configured email action. Click **Server down Instruction** to configure the instructions included in the notification.
13. Click **Add Probe Server**. The Probe Server is added and displayed under the **Probe Servers** link with details such as the number of monitors, status, and load factor.

**Note:** The Admin Password entered should be the same as that of the Admin role password of that probe server. If the user changes that password in the Probe server, then the user has to manually update the same in the central server.

The following Probe Server details are displayed in the table:

| Parameter | Description |
|---|---|
| Server ID | The unique identifier of the Probe Server. |
| Display Name | The name assigned to the Probe Server. |
| Probe Server Group | The group to which the Probe Server belongs. |
| Monitors Status | The health status of the monitors on the Probe Server. |
| Load Factor | The current load factor of the Probe Server. |
| Last Polled At | The time at which the Probe Server was last polled. |
| Synching | The current data synchronization status of the Probe Server, such as completed or in progress. |
| Download | The status of the Service Pack download. |
| Upgrade | The status of the Service Pack upgrade. |

You can select one or more Probe Servers and click the **Download Now** link at the bottom of the table to download the Service Pack and the **Upgrade Now** link to upgrade the Service Pack.

**Note:** In order to find if a particular Applications Manager installation is heavily loaded you can use the **Load Factor**, which is provided in the 'Support' tab under the 'Applications Manager Installation Information' category. The **load factor** follows the format x.y, where 'x' represents load on Applications Manager Server, while 'y' represents the load on the Database used by Applications Manager. A value of zero represents least loaded, while a value of nine represents most loaded. Hence Load Factor can take values from 0.0 to 9.9 (heavily loaded). The Load Factor of each of the Probe Servers is also displayed in the Central server under the "Probe Servers" option and you can use the same to distribute load evenly among the Probe Servers.

**Note:**

The Load Factor can be denoted by x.y where x represents Probe server polling load factor and y represents Probe server data base load factor.

The maximum value of x,y can be configured in the `AMServer.properties` file of Central server:

```properties
x - am.mas.polling.max.loadfactor - default value 5
y - am.mas.database.max.loadfactor - default value 5
```

## Probe Server Actions

**Fetch Data:** There is an option to fetch the data from the probe servers at the given instant, instead of waiting for the poll to happen.

**Edit:** You can edit the probe server details using this option.

**Enable/Disable Sync:** You can enable/disable data collection in the Probe Server. Note that when you disable, data collection will still take place, you only stop syncing with the probe server.

**Push Auth Key:** Allows you to push the auth key to selected Probe server(s), which is used to authenticate the sync between the Central server and selected Probe server(s).

**Admin Email Settings:** An EMail can be configured to be sent once a Probe Server goes down and also once every 24 hrs till the Probe Server is up again. The EMail setting is available in the Admin EMail Settings" option under the **Settings** tab. The option to enable/disable this EMail, is available in the "Edit" option of the respective Probe Server.

**Proxy Probe Server request through Central Server:** When you login to the Admin console, Graphs and images displayed for a monitor are retrieved directly from the corresponding Probe Server itself and are displayed in the Admin console. These graphs/images cannot be retrieved, if the Central Server is accessible from a particular machine/over the Internet and the Probe Server is not accessible.

In this case, select the *"Proxy Probe Server request through Central Server"* request option. This will result in the images/graphs being fetched to the Central Server from the Probe Server first and then the image from the Central Server is viewable in the Web Browser.

E.g., Central Server is running as part of IDC and accessible via the Internet (From a machine say "ClientMachine") but the Probe Servers are not accessible (from "ClientMachine") this option should be enabled.

**Note:** In case of a proxy server configured in the network, make sure to configure the proxy server for both Central and Probe servers.

**User Management:** In the Enterprise setup, the [User Management](https://www.manageengine.com/products/applications_manager/help/user-administration.html) module functions independently in the Central Server and Probe Server. Hence, a user-based view assigned in the Probe Server will not reflect in the Central Server and vice-versa. Since, you will be viewing the data collectively from the Central Server, you need to assign owners to the various Monitor Groups of the Probe Server in the Central Server. Of course, if it is assigned in the Probe Server it will function independently. Also, in the [Manager Console](https://www.manageengine.com/products/applications_manager/help/management-console.html) (SLA Management console), you can assign SLAs and associate actions to be invoked for SLA violation to the Monitor Groups in the Central Server.

**Probe Server Access**

Click on the **Jump To** link in the Central Server just above the toolbar, which brings down a list of the Probe Servers. Clicking on any of the Probe Server names in the list will take you to the web console of the respective Probe Server in a separate browser Window.

**Note:** ENTERPRISEADMIN role is used for logging into the Probe Server from Central Server for data synchronising. The username for this role is `systemadmin_enterprise` and the password is the regular ADMIN role password. This role is not exposed in the UI, it will be used internally.

**Important:** Visit [Enterprise Edition FAQ](https://www.manageengine.com/products/applications_manager/applications-management-productfaq.html#enterprise) for details on when and how to set up the Enterprise Edition.

## FAQ - How is the Probe server selected by APM using load factor?

The following two things are used to select the probe server automatically.

**Load Factor (x.y) where,**

```text
x represents Probe server polling load factor
y represents Probe server data base load factor
Max. value of x,y can be configured in AMServer.properties file of Central server
x - am.mas.polling.max.loadfactor - default value 5
y - am.mas.database.max.loadfactor - default value 5
```

**Maximum monitor allowed per Probe server**

The value can be configurable in `AMServer.properties`. The key is `am.max.monitorcount.mas` and default value is `500`.

The condition for choosing probe server is:

```text
x < maxAllowedValueOfPollingLoad (and)
y < maxAllowedValueOfDatabaseLoad (and)
n < maxMonitorAllowed
```

If the condition is not matched then we show the "No Probe server is available" message to the user.