We are delighted to inform you about the new Self-Healing Xporter - an initiative which aims to address communication issues within Xporter. In the unlikely event of a problem, Self-Healing Xporter allows Xporter to analyse its environment & do everything possible to fix the problem and re-establish connectivity to the outside world, vastly cutting down on any support time required to resolved issues. These being;
- Xporter’s ability to connect to the MIS being interrupted.
- Xporter’s ability to access the Internet being interrupted.
Let’s look at these in a little more detail.
A typical problem that occurs with running background tasks, such as Xporter, is that it isn’t allowed to access network drives and doesn’t by default have any proxy configuration. However, this is not unique to Groupcall Xporter and you will find that any company using a background application will have the same problems. Meaning we have to do a couple of 'tricks' at installation. Specifically, we copy the proxy and MIS connection settings for the user that runs the installer and store them in Xporter’s configuration. The problem here is of course that over time both the proxy and MIS settings that Xporter has become invalid.
We have looked into some options and probably the most key of these is being able to tell at a distance that something is wrong. To do this we needed to make our Xporter Heartbeat (which reports health to Groupcall Dashboard and picks up repair actions) more intuitive. We did this in our spring Dashboard release, and the Heartbeat will now search for alternative proxies. What we’re trying to do here is get that link back to Dashboard as resilient as it can be.
We’ve also looked at the MIS connection issue and discussed it to a great extent. We’d never want to do anything automatic in the MIS – it’s just not our data to touch. For example, even if we could guess the correct SIMS server name, we could easily get the wrong database and that again is absolutely a risk we can’t take.
However, what can’t be done automatically can at least be made easier. We’ve recently produced an Xporter Repair Installer; if run interactively by a user at the school on the Xporter PC then it will refresh the installation by updating the proxy settings and reconnecting it to the MIS. We’re happy with this because it means somebody at the school has a final say on the settings Xporter has detected. We’re also working on enabling the Heartbeat to fix a wider range of issues in Xporter without requiring a remote session to be set up.
So what we have at this point is some tools to make fixing a problem easier, and some changes to make sure that Dashboard is able to pick up any errors from schools even if the proxy has been changed.
And I’m sure you can see our overall plan here; armed with a reliable connection to get the error logs from schools and a suite of tools for the most common unattended fixes all we need now is for something to analyse those logs and queue up automatic repair actions automatically. I’m sure we have a product for that too… oh, of course, Dashboard!
So with that we end up with the building blocks for something really quite cool, which we’re calling Self-Healing Xporter. Run behind the scenes & given a bit of guidance from Groupcall Dashboard, Xporter can now effectively come of age and start to look after itself, all on its own.
For more information contact us on 020 8502 7344 or email firstname.lastname@example.org.