ClearSCADA Mobile is a useful add-on to ClearSCADA. It can consolidate data from several systems and provide it to remote users in their handheld or tablet devices. Because it is not easy here are some instructions on how to set it up!
Disclaimer: I am putting this together so I can remember how to do this myself. Each time I do a CS Mobile install it takes a couple hours to hammer everything out.
There are three parts to ClearSCADA Mobile:
- ClearSCADA Mobile App (Android and iOS)
- Mobile Server (Windows IIS app that serves client devices and is the ‘bridge’ to the ClearSCADA mobile companion)
- Mobile Companion (the server module that communicates with the CS server)
For everything to work there are a couple of secure TCP (TLS encrypted!) connections that need to be made. Your ClearSCADA Server’s Mobile Companion needs to be able to connect to the Mobile Server listen port (secure or insecure, your choice). Your user’s devices need to be able to connect to the Mobile Server over the secure web port of IIS (always secure). Your users’ devices also need to be configured in the Mobile Configuration app or they will not be allowed to browse for systems or make any meaningful connections.
What You Need Before You Begin
- A ClearSCADA server with the Mobile Companion installed (I show how to do that later)
- A stand-alone IIS web server for the Mobile Server installation.
- Proper TLS certificates for the machines involved, especially important if your mobile server is going to be available publicly over the Internet.
- A degree in Windows IIS web apps, TLS and troubleshooting TCP connections. I say this as a joke, but CS Mobile depends heavily on TLS connections. It has been my experience that the error information in the logs can be very confusing and uninformative for the uninitiated.
- A license for ClearSCADA Mobile with enough systems and devices. Provide the CS Mobile Server Machine Id to your distributor or SE rep. to get this going.
Install the Mobile Server
- Stand-up a new Windows IIS Web Server on your network or in your DMZ. You will probably want a Windows install with the GUI available.
- Optional: If you need a TLS certificate for the CS Mobile IIS app, install it on the machine now.
- Transfer over the ClearSCADA ISO and start the CS Mobile installer.
- Click on Next to get into the installer.
- Read and accept the License Agreement.
- Select the port for CS Mobile to server its info up on. Pick your certificate if you have one. Choose the self-signed cert if you do not. I am choosing the self-signed certificate. I also recommend port 443 because then the user doesn’t have to enter a port number in the mobile app on their device.
- Pick the Listen Port and write it down somewhere. This is the TCP port on which the Mobile Server listens for Mobile Companion connections. It is hard to change later so make sure you set it right the first time.
- Select the install location. Default is best.
- Finish up the install and Restart.
- Open up your Windows Firewall and add an exception for the Listen Port.
- Click on Inbound Rules. Add a new rule.
- Set the rule type to Port.
- Apply the rule to TCP port 8008 (or whatever listen port you selected in Step 7)
- Allow the connection (use allow if secure if you know what you are doing).
- Apply to all connections (restrict if you know what you are doing).
- Give the rule a name and optional description.
- Restart for good measure.
Install and Configure the Mobile Companion
- Shutdown your ClearSCADA server.
- Re-run the ClearSCADA Server installer, or modify the install from Control Panel->Programs and Features. Add the Mobile Companion option under Server.
- Start the ClearSCADA Server.
- Open Server Configuration (from the icon or the start menu) and click over to System->Mobile. Configure the Mobile Companion settings. Set the correct Mobile Server name/address, listen port and enter the system name for this ClearSCADA system.
- Restart the ClearSCADA Mobile Companion using the Windows Services Window.
- Wait a minute or two and check the Mobile Companion log files.
Bad Logs – Companion not able to communicate with Mobile Server
Good Logs – Companion Connected
If you do not have communication between the Mobile Companion and the Mobile Server at this point you should take some time to figure that out. Things to check: Firewall settings (Windows and hardware between CS Server and Mobile Server), TLS/Secure settings, TLS Certificates, restart Mobile Companion, restart Mobile Server (did this once a week or so ago, saved my life. After a couple hours of troubleshooting. Doh!). The Mobile Companion logs will tell you if you have a solid connection. Call Schneider Electric tech support if you need help (Or call me! We have reasonable rates).
That is probably enough for now. I will leave setting up the rest of ClearSCADA Mobile for another blog post. At this point you should have the Mobile Server installed on a stand-alone IIS server and the Mobile Companion installed on your ClearSCADA server with an active connection between the two systems.