APC NetBotz 320 Rack Appliance NBRK0320E Manuel D’Utilisation
Codes de produits
NBRK0320E
What’s New?
Using Your Appliance
3
BotzWare Version 2.2.2 Features
In addition to additional hardware support and performance improvements, BotzWare 2.2.2 introduced
the following new features and enhancements:
the following new features and enhancements:
• 4-20mA Sensor Pod Support: Support for the 4-20mA Sensor Pod, which enables you to connect
up to four 4-20mA sensors to your NetBotz 420 or NetBotz 500 appliance. For more information
see “Configuring 4-20mA Sensor Pods” on page 24 and “Sensor Pods” on page 97.
see “Configuring 4-20mA Sensor Pods” on page 24 and “Sensor Pods” on page 97.
• BotzWare now supports the use of 0-5V sensors, which can be connected to any external sensor
port using a NetBotz 0-5V Sensor Cable. 4 external sensor ports are integrated with NetBotz 320 or
420 appliances, and are included on each Sensor Pod 120 as well.
420 appliances, and are included on each Sensor Pod 120 as well.
• Added BotzWare Web Services Interfaces: The NetBotz BotzWare Web Services interfaces are
intended to provide a set of common, programmer-friendly APIs to 3rd party product and solution
developers, as well as end customers. For more information, see the BotzWare V2.x Web Services
Specification PDF, included on your BotzWare CD and available from the NetBotz support web
site.
developers, as well as end customers. For more information, see the BotzWare V2.x Web Services
Specification PDF, included on your BotzWare CD and available from the NetBotz support web
site.
• Call Web Services Alert Receiver (New Alert Action): A new alert action that is designed for use
with the BotzWare Web Services Interface (see above).
• Added support for the SeaLINK PIO-48. When you connect a SeaLINK PIO-48 (available from
Sealevel Systems) to a USB port on your NetBotz 500 or NetBotz 420 appliance, it provides 48
digital connections. This enables you to connect and monitor up to 48 dry contact sensors from a
single appliance without requiring you to purchase and deploy a large number of Sensor Pod 120s.
digital connections. This enables you to connect and monitor up to 48 dry contact sensors from a
single appliance without requiring you to purchase and deploy a large number of Sensor Pod 120s.
• Added support for RAEWatch (new sensor type).
• New Simplified Basic View for Use with Supported PDAs: NetBotz appliances now support a
simplified version of the Basic View that can be viewed using supported Personal Digital Assistants
(PDAs). Supported PDAs include Palm Tungsten handhelds running Palm OS 5.2.1, HP iPAQ
handhelds running Windows Mobile Pocket PC 2003 or Windows Mobile Pocket PC 2003, and
Blackberry 6xxx & 7xxx Series Devices running 3.7 OS. For more information see “Using the
Simplified Basic View” on page 14.
(PDAs). Supported PDAs include Palm Tungsten handhelds running Palm OS 5.2.1, HP iPAQ
handhelds running Windows Mobile Pocket PC 2003 or Windows Mobile Pocket PC 2003, and
Blackberry 6xxx & 7xxx Series Devices running 3.7 OS. For more information see “Using the
Simplified Basic View” on page 14.
• Send Custom Text File to FTP Server (New Alert Action): Sends a customized text file with
user-specified content to an FTP server. This alert action type enables you to use macros supported
by BotzWare (including Appliance, Location, and Alert macros) to define the name of the directory
on the server in which custom text files will be stored and the base filename that will be used for the
text files.
by BotzWare (including Appliance, Location, and Alert macros) to define the name of the directory
on the server in which custom text files will be stored and the base filename that will be used for the
text files.
• Advanced Device Crawlers has been enhanced to enable it to monitor NetBotz appliances
running BotzWare 2.x.
• Additional Network Interface Settings: When configuring a network interface, you can now
specify both the network speed and the duplex mode for the interface.
• Added Include XML-encoded Alert Parameter (xmlalert), a check box for the Custom HTTP
Get action that appends the parameter xmlalert=<xml alert encoding> to the provided URL for the
action. The encoded XML is the same as is generated by the HTTP POST code, but is URL-
action. The encoded XML is the same as is generated by the HTTP POST code, but is URL-