Core Software - XPLProject

The building blocks required for an xPL installation. For help getting started, see the HowTo guides Get Started on Windows and Get Started using Java.


xPL Hubs

An xPL Hub is a mandatory part of any PC-based xPL installation, handling message traffic between xPL applications. Hubs are no longer built into any xPL applications, and therefore must be installed separately.

  • Windows xPLHub - This is the recommended hub for all Windows xPL installations, since it does not require the .NET framework, and will automatically run as a Windows Service or as a console application depending on the version of Windows being used.
  • Windows .NET xPL Hub - an implementation of an XPL hub in the Microsoft VB.NET programming language which installs as a Windows service.
  • Linux xPLHub - This hub is a very small, very robust, supervised hub for use on linux systems and other unix-like systems. The hub has been built with an eye toward stability and the included supervisor is always checking the status of the hub process and if it fails, stops it and starts a new one. The hub is provided as both a standard executable and a static one that should run on any platform. Source code is provided if you'd like to compile it (you'll need the xPL4Linux framework to do so).
  • Java xPLHub - This hub is written in Java and so can run on any platform that supports Java 1.5 or later. It is a stable, robust hub with support for multiple network configuration. Source is included, if you need it, but the included precompile executable jar is all most folks will need.
  • Perl xPL Hub - This hub is written in Perl and so can run on any platform that supports Perl. It is based on a Perl xPL API. This xPL hub is part of a series of xPL client scripts.

xPLHal

  • xPLHal - this is the controller at the core of any Windows-based xPL network. It provides a fully graphical interface for configuring and managing your entire xPL environment, as well as a complex logic engine and a scripting environment.
  • xPLHal Web Access - An ASP.NET Web application to allow control of the xPLHal Home Automation Manager through a Web browser. If used over an SSL-encrypted connection (HTTPS), it can provide you with a secure method of administering your entire xPL home automation environment over the Internet.
  • xPLHAL4Java - this is the controller at the core of any xPL network capable of running Java. That means your xPLHAL engine can run under Windows, Mac OSX, Linux, Solaris, etc. It is nearly a 100% compatible, mulit-platform implementation of xPLHAL (only scripting is different, as xPLHAL for Windows depends on Windows VBScript, where as xPLHAL4Java offers a variety of multi-platform capable scripts). Currently, you still need the xPLHALMgr GUI program to configure it (a Windows only program), but there will be a Web based, Java powered management console available in the not too distant future.

xPL4Java

  • xPL4Java - this is the "engine" for many xPL applications that are designed to run under the xPL4Java server. This provides an environment for running multiple xPL4Java based applications on any computer that supports Java 1.5 or later. It also provides a scripting engine that can be used on it's own as well as a few helpful modules such as a xPL system clock and an xPL event logger. The xPL4Java engine now comes with an fully xPLHAL compatible xPLHAL4Java engine for running determinators, events, etc allowsing xPLHAL to run on any platform.
  • DCM - DCM, or Device Configuration and Manager, is a Java based GUI that allows you to list, configure and command all the xPL devices on your network. It can run on any platform that supports Java 1.5 or later (aka Java5)
This page was last modified on 3 January 2009, at 13:14. This page has been accessed 15,586 times.