Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
The supplemental string is mandatory to understand the nature of the device.
For example, for power related devices, phase and bank information is present in the supplemental string used in ITA to create an object of the device.
A number of sensors are also used from the DCE web service interface /integration/services/ISXCentralSensorService_v2_0?wsdl
To create an object to be used for the sensors, use:
Note
Index is being used to identify which module and phase are reporting data.
That means index must be unique across sensorType on a given device
It is NOT allowed to have e.g. 2 sensors of the same sensorType reporting same index. For example a single phase rack PDU with 2 banks and reporting phase information as well. Same sensorType having same index:
At sensor level, the sensorType is used to specify a modular PDU reporting data and the index is used to identify the phase reporting on a module. In this example breaker module 5, phase 3 (index 5,3):
<ns2:ISXCSensorType>MODULE_OUTPUT_POWER</ns2:ISXCSensorType> <ns2:index>b,p</ns2:index> - e.g. <ns2:index>5,3</ns2:index>
Data Collection
The data collected from DCE via the power sensors is Peak and Average data. Peak and Average power data is queried for an interval of one day, 1 time/day. Additionally, peak power data is queried every 5 minutes since last time queried.
We store the data and calculate Peak and Average values based on a setting in the ITA server (10, 20, 30 days).
Summary
The expected values used to specify and map the device in ITA:
ISXCDevice - Supplemental
ISXCSensor
PhaseCount
BankCount
Index
SensorType
Device example
1
1
Ignored
OUTPUT_POWER_TOTAL_WATTS
rack PDU
1
>1
1 digit = Bank number
OUTPUT_POWER_WATTS
rack PDU with banks
1
-
Ignored
OUTPUT_POWER_TOTAL_WATTS
3
1
1 digit = Phase number
OUTPUT_POWER_WATTS
UPS or (RM)PDU
3
>1
2 digit = Module, Phase
MODULE_OUTPUT_POWER
Modular PDU
3
-
1 digit = Phase number
OUTPUT_POWER_WATTS
Note
Supplemental is mandatory and must include phase information
PhaseCount references InputPhaseCount and OutputPhaseCount which is expected to be the same number.
DCE exposes information through various web services.
Fordevice information, ITAuses:
getAllDeviceGroups
getDevicesForGroupID
Forsensor informationand data, ITAuses:
getSensorsByType
getMultipleAverageSensorData
getMultiplePeakSensorData
Verifying DDFs with Soap-UI
The walkthrough below is done with SoapUI 5.4.0. You can download the latest version here: https://www.soapui.org/
When setting up a new project, chose the SOAP project type.
Screenshot1_360006754317.png
The initial WSDL link should be
http://X.X.X.X/integration/services/ISXCentralDeviceService_v2_0?wsdl for the device endpoint.
http://X.X.X.X/integration/services/ISXCentralSensorService_v2_0?wsdl for the sensor endpoint.
Where X.X.X.X is ip address for the DCE server.
Screenshot2_360006754317.png
When prompted for the username and password, provide those used for logging into the DCE server.
Running a request against the DCE server
When running a request against the endpoint, first choose the endpoint in the list, and fold out so you can see the sample request.
Screenshot3_360006754317.png
Before running the request, you need to setup authentication:
Chose 'Basic'
Enter in the username and password for the DCE server
Screenshot4_360006754317.png
Then press play to run the request.
Dependent on the request it might be necessary to fill in a number of parameters.
When you have identified the correct device use the sensor end point to ensure that sensors with the correct type are available.
Running requests to verify sensors with the correct type are available
Getting the sensors for a specific device.
Several of the end point are of interest, this is just an example on one why to do the verification.
Given an ID for a device, all the sensors for the device can be gathered with the getSensorsForDevice request.
Screenshot5_360006754317.png
Fill in the ID for the device
Screenshot6_360006754317.png
Check that sensors with the types mentioned in the first part of this document are present. One example for the OUTPUT_POWER_WATTS sensor type is shown below.