Installation
You will need someone comfortable with IIS and web service configuration.
Requirements
Section titled “Requirements”- Windows Server 2012 or higher
- IIS, with the required server roles and features installed
- A free TCP port, opened on the server firewall — and on the physical firewall if your site has one
Download
Section titled “Download”The service ships as a zipped Visual Studio solution:
The archive also contains Documentation/Phantom WebService SDK.pdf, the
original SDK document this section was transcribed from.
Install
Section titled “Install”-
Choose a port and allow it through the server firewall with an inbound rule. If your company has a physical firewall, add the same port there.
-
Create the application folder under the IIS web root:
C:\inetpub\wwwroot\PhantomWebService\ -
Point the service at your storage. Edit
Web.configand set where the JSON files will be written:Web.config <add key="DirectoryPath" value="E:\" /><add key="NamePath" value="Test_WS_Phantom" />DirectoryPathis the drive or path where data is stored andNamePathis the folder created inside it. -
Create the website in IIS Manager, using the port from step 1 and the folder from step 2.
-
Verify it is running. Open a browser on the server:
http://localhost:[yourPort]/PhantomService.svcYou should see the WCF service page. You can also call
GET /PhantomService.svc/ServiceOk. -
Point the gateway at it. Install the PHANTOM® Manager app (Android and iOS), then:
- Enable Send data to cloud
- Set your time zone
- Open Alternate Cloud URL
- Enter
http://[your IP]:[yourPort]/PhantomService.svc
Use the server’s reachable IP address here, not
localhost.
What the folder contains
Section titled “What the folder contains”DirectoryC:\inetpub\wwwroot\
DirectoryPhantomWebService/
- Web.config the file you edit in step 3
- PhantomService.svc
Where data lands
Section titled “Where data lands”Accelerometer, settings and status data from vibration sensors are written to a
folder named EINA inside the path you configured.
Verify data is arriving
Section titled “Verify data is arriving”Once a sensor reports, call one of the read endpoints for today’s date — for
example getStateData, which returns quickly. A status of 500 (“No data”)
means the service is up but nothing has been stored for that sensor and day
yet.