This shows you the differences between two versions of the page.
plugins:beetle [2017/12/21 14:06] 127.0.0.1 external edit |
plugins:beetle [2021/11/21 17:18] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Beetle Info ====== | ====== Beetle Info ====== | ||
---- | ---- | ||
- | {{:plugins:beetle:6.png }}**Beetle Info** is an agent software application available for **Wincor Beetle Point-Of-Sales** products. Thanks to **proVconnect's Beetle Info Plugins**, you can now enjoy **to collect** your Beetle specific **device data** and **to monitor** the usage of your POS systems within **proVconnect** console. | + | {{:plugins:beetle:6.png }}**Beetle Info** is an agent software application available for **Wincor Beetle Point-Of-Sales** products. Thanks to **Xcalibur W's Beetle Info Plugins**, you can now enjoy **to collect** your Beetle specific **device data** and **to monitor** the usage of your POS systems within **Xcalibur W** console. |
===== Beetle Info Inventory and Monitoring data ===== | ===== Beetle Info Inventory and Monitoring data ===== | ||
Line 35: | Line 35: | ||
---- | ---- | ||
- | Once loaded onto **proVconnect** server, the **Beetle Info Plugins** appears within your **Plugins List** as shown below. | + | Once loaded onto **Xcalibur W** server, the **Beetle Info Plugins** appears within your **Plugins List** as shown below. |
{{ :plugins:beetle:1.png }} | {{ :plugins:beetle:1.png }} | ||
Line 45: | Line 45: | ||
===== Using Beetle Info Inventory Data ===== | ===== Using Beetle Info Inventory Data ===== | ||
---- | ---- | ||
- | In order to collect Inventory Data, a new command module is available within the proVconnect's | + | In order to collect Inventory Data, a new command module is available within the Xcalibur W's |
- | [[manage_devices:tasks_and_creating_tasks#available_commands_tab|Command List]]. You can use this command to **refresh on demand** the Inventory Data from your Beetle POS Systems. However, keep in mind that this **[[manager_options:settings#automatic_inventory_settings |inventory can be done automatically]]** at each device startup if your proVconnect server is set to do so. | + | [[manage_devices:tasks_and_creating_tasks#available_commands_tab|Command List]]. You can use this command to **refresh on demand** the Inventory Data from your Beetle POS Systems. However, keep in mind that this **[[manager_options:settings#automatic_inventory_settings |inventory can be done automatically]]** at each device startup if your Xcalibur W server is set to do so. |
{{ :plugins:beetle:2.png?200 }} | {{ :plugins:beetle:2.png?200 }} | ||
- | Once collected, the **Beetle Info** Inventory data are added & merged to the proVconnect device data available within the [[commands_glossary:commands_to_single_device#monitor|Inventory]] sections of your devices. | + | Once collected, the **Beetle Info** Inventory data are added & merged to the Xcalibur W device data available within the [[commands_glossary:commands_to_single_device#monitor|Inventory]] sections of your devices. |
{{ :plugins:beetle:4.png }} | {{ :plugins:beetle:4.png }} | ||
Line 57: | Line 57: | ||
---- | ---- | ||
- | In addition to the static inventory data, **Beetle Info** offers monitoring data which can be used with proVconnect's [[monitoring_and_preventive_maintenance:overview|Monitoring and Preventive Maintenance]] tool. | + | In addition to the static inventory data, **Beetle Info** offers monitoring data which can be used with Xcalibur W's [[monitoring_and_preventive_maintenance:overview|Monitoring and Preventive Maintenance]] tool. |
When creating a new [[monitoring_and_preventive_maintenance:rules_and_creating_rules|Monitoring Rule]], you have access to **Beetle's specific Triggers** as shown below. | When creating a new [[monitoring_and_preventive_maintenance:rules_and_creating_rules|Monitoring Rule]], you have access to **Beetle's specific Triggers** as shown below. | ||
Line 63: | Line 63: | ||
{{ :plugins:beetle:5.png }} | {{ :plugins:beetle:5.png }} | ||
- | For each of the above triggers, proVconnect will raise an **alert**, open an **incident** and notify by **email** - whenever the specified component reaches a **Warning** or **Critical** state. | + | For each of the above triggers, Xcalibur W will raise an **alert**, open an **incident** and notify by **email** - whenever the specified component reaches a **Warning** or **Critical** state. |