Ignite-LUX: Management and Integration of Ignite-UX Software on a Server Running Linux

11
CMS Integration with Ignite-LUX Software
The following sections are primarily intended to provide CMS developers with Ignite-LUX integration details.
CMS solution users might find this information useful for understanding Ignite-UX interaction, maintaining
their Ignite-LUX server, and assisting issue diagnosis.
HP-UX Ignite-UX and Linux Ignite-LUX servers include compatible CMS integration support with minor
differences. It is possible to use the same implementation for control of both types of servers.
CMS software generally uses the same Ignite-UX interface as the Ignite-UX software that runs on the HP-UX
server to control clients.
The Ignite-UX Administration Guide includes a section on Ignite-UX theory of operation that CMS developers
might find especially useful. The guide also includes information on handling complex networks that is very
likely to contain important, helpful details.
Caution: CMS developers and others performing automated control of Ignite-LUX functionality should only
use the methods and details presented in this section. Ignite-UX provides a rich set of features. Experience
has shown that exploring Ignite-UX capabilities and applying integration creativity can result in software
that does not provide a good overall solution later. For example, in some cases developers have used
automatically generated per-client config content placed in IINSTALLFS that worked well for limited
testing but prevented successfully scaling to a full solution.
Important: The Ignite-UX team might make product changes in the future releases that would break CMS
integration or other automated control that includes use of functionality not described here.
If functionality is required beyond what is presented here, you must request an integration enhancement so
the required functionality is added to the package if necessary and becomes documented in this section.
Future: Where noted, some of the interface details presented in this section have not yet been
implemented. This information about future plans reflects the Ignite-UX team’s perspective but is not a
commitment.
We recommend that CMS software developers consider developing to use these future planned interfaces
when present since when implemented they provide a better and more stable means of integration.
In addition to other future items in this section, the Ignite-UX team is investigating a Command Line Interface
(CLI), which makes use of XML for data interchange as an improved interface for Ignite-UX control. Due to
customer compatibility needs and other issues, the interface details included in this section will not be
immediately replaced by an improved interface.