technology used
Q: What technology does Arum DataEye® use?
A:

Arum DataEye® is built as a web application in Adobe Flex, with Java server side code and db4o, an object oriented database. The open source package, Solstice, is used as a container for the application. Solstice comprises and extends a number of open source packages, including OSGi and JBOSS. Users need the plugin for Adobe Flash Player 8 or later installed in a web browser.

Q: What is Adobe Flex?
A:

Flex is a highly productive, free open source framework for building and maintaining expressive web applications that deploy consistently on all major browsers, desktops, and operating systems.

Q: What is Java?
A:

Java is an object oriented programming language. The Java platform enables Java programs to be run on a variety of operating systems.

Q: What is db4o?
A: db4o is the open source object database that enables Java and .NET developers to store and retrieve any application object with only one line of code, eliminating the need to predefine or maintain a separate, rigid data model.
Q: What is Solstice?
A: Solstice is a RIA framework that fuses the power of Flex and OSGi to allow development of modular rich internet applications. Out of the box, Solstice provides the following features:
 
  • An OSGi 4 compliant container with Flex based management console
  • A platform for deploying modular Flex applications as OSGi bundles
  • Rich server functionality using Blaze DS to expose OSGi services as remote objects

Solstice is based on the following technology:
  • Adobe Flex
  • Adobe BlazeDS
  • OSGi
  • Eclipse Equinox
  • Eclipse Equinox Servlet Bridge
  • Felix
  • db4o
Q: What is OSGi?
A: OSGi is the dynamic module system for Java. OSGi technology provides a service-oriented, component-based environment for developers and it offers standardised ways to manage the software lifecycle. These capabilities greatly increase the value of a wide range of computers and devices that use the Java platform. Arum is an active founder member of the OSGi UK User Forum.
Q: What are Eclipse Equinox and Eclipse Equinox Servlet Bridge?
A:

OSGi technology is Universal Middleware. OSGi technology provides a service-oriented, component-based environment for developers and it offers standardised ways to manage the software lifecycle. These capabilities greatly increase the value of a wide range of computers and devices that use the Java platform.

Q: What is Adobe BlazeDS?
A:

Adobe BlazeDS is an open source server-based Java remoting and web messaging technology that enables developers to easily connect to back-end distributed data and push data in real-time to Adobe Flex applications for more responsive rich RIA experiences.

Q: What is Felix?
A:

Felix is a community effort to implement the OSGi R4 Service Platform, which includes the OSGi framework and standard services, as well as providing and supporting other interesting OSGi-related technologies.

Q: What is meant by Rich Internet Applications (RIAs)?
A:

Applications like Arum DataEye are often called rich internet application (RIAs). RIAs are web applications that have the features and functionality of traditional desktop applications. RIAs typically pass the processing necessary for the user interface to the web client on the user's internet device but keep the bulk of the processing (the state of the program, the data, etc.) back on the application server.

Q: What is meant by open source?
A:

Open source is a development methodology that offers practical accessibility to a product's source (both goods and knowledge). When applied to software, it refers to the fact that the software is made available for public collaboration, and it is usually released as open-source software.

Open source does not mean 'free to use'. There are different licences under which open source software is made available for various commercial and non commercial uses. Arum DataEye® includes several open source components.

Q: Are Arum DataEye® customers at risk because of open source?
A: The business risks that open source typically carry are lack of formal support and training, the potential speed of change and the lack of long term product development plans. The open source components on which Arum DataEye® are built are all widely used and actively supported, albeit by the distributed community and not a commercial company.

Many industrial strength applications are already built on Adobe Flex and several of the open source components in Arum DataEye® are central to Adobe's substantial RIAs plans. Thus Arum is confident that the quality and level of support for these components does not put Arum's clients at risk, and there is minimal risk of Arum DataEye® development plans being disrupted because of open source software issues.
component parts
Q: What are the components of Arum DataEye®?
A:

Arum DataEye® consists of:

  • (1) a server side application, whose functions are to:
    • manage the administration of Arum DataEye®
    • manage the data requirements of Arum DataEye® users
    • deliver data to the client RIA of an Arum DataEye® user
    • manage and deliver alerts to Arum DataEye® users through selected media
  • (2) a server side database, which stores and retrieves:
    • user logins and permissions
    • specifications of users’ data requirements
    • details of alerts to users
  • (3) data harvesters, which:
    • provide an interface to the customer’s key databases, gathering the required data as necessary
  • (4) a web application, running in an internet browser on the client machine, whose functions are to support different users in their respective functions:
  • Arum DataEye® administrator
    • manage Arum DataEye® licences
    • manage the configuration and operation of Arum DataEye®
    • define users, groups and permissions
    • edit the Data Point Registry
  • Arum DataEye® KPI builder
    • define the data requirements of different users, with reference to the key performance indicators (KPIs) that users may need to see
  • Arum DataEye® dashboard users
    • view KPIs on the charts that the KPI builder has created

    • Q: Which parts of an Arum DataEye® deployment are off the shelf and which are customised?
    A:

    Components 1 (server side application), 2 (server side database) and 4 (web application) come off the shelf. Component 3 (data harvesters) need to be custom built to interface with the customer's own databases. The Data Point Registry, which is constructed and edited through the administration function of Arum DataEye®, also needs to be custom built to define the data required by the customer in the construction of KPIs.

    Q: What is a harvester?
    A:

    A harvester is a software module that is responsible for interfacing directly with the customer's IT systems in which the key performance indicator (KPI) data are held. It is custom built in the Java language.

    Q: Who creates harvesters?
    A: Arum's software engineers build the harvesters in Java.
    Q: Who owns the harvesters?
    A:

    The customer owns the harvesters. Arum delivers both the installable executable files and the source code for the harvesters.

    Q: What is the Data Point Registry?
    A:

    The data point registry is a structure that defines the particular data required to work out the customer's KPIs. It makes reference to:

    • What data are required
    • What levels of aggregation of data are required
    Q: Who designs the Data Point Registry?
    A: This is designed by Arum, having worked with the customer to determine the customer's specific data requirements.
    Q: How is the Data Point Registry compiled?
    A:

    A user can log in to Arum DataEye® and edit the Data Point Registry.

    integration with existing systems
    Q: Which parts of Arum DataEye® interface with which parts of my existing systems?
    A:

    The Arum DataEye® harvesters interface directly with whatever parts of your IT systems contain the real time data required to monitor the KPIs displayed by Arum DataEye®.

    Q: Does Arum DataEye® control or write data to my existing systems?
    A:

    No

    Q: Do my existing systems have to be interrupted to accommodate Arum DataEye®?
    A: It depends on what your existing systems do and how they are scheduled.
    required skills and resources
    Q: What skills and resources does a purchaser of Arum DataEye® need to manage it?
    A:

    There is no need of special skills or resources. Arum DataEye® can be used by anyone with access to a computing device, from managers to operational staff. Arum DataEye® runs in a browser or on your desktop.

    Q: What skills and resources does a purchaser of Arum DataEye® need to set it up?
    A:
    It is best if Arum DataEye runs on a "dedicated" server, in other words one that has no other applications running on it. So it is best if you have someone who knows about setting up and running a server.

    If you have nobody in your organisation with these skills you should consider the "hosted" DataEye solution. In this case the DataEye server will be in a data centre off site from your premises and you will need a good internet connection. Arum and its suppliers will look after it on your behalf.
    integration process
    Q: What is the typical approach to getting Arum DataEye® running for a customer?
    A:

    We recommend going through a few cycles of several of the activities needed to integrate DataEye.
    This cyclical approach has several advantages:

    • At the end of each cycle, you  have a working integration (between DataEye and whatever existing IT systems the KPIs are coming from). So you will:
      • have real KPI information early in the project
      • be able to modify your view on KPIs and displays soon after they are created
      • be able to get buy-in from operational staff early in the project
    • You can modify your view on what you want, in the light of what you learn as the integration progresses. This can be very helpful because we all can change our perception of what is possible once the introduction of a new system is under way. In the alternative situation where there is single “sign-off” of requirements, this opportunity for change is often denied and this can lead to frustration.
    • In the long run, because you will have an integration that suits
      your needs better, you will need less effort and expense in the future
      to discuss and amend the DataEye operation and views.

    The cyclical approach does also mean, however, that it is important to get the appropriate contributions from your people when needed, particularly in planning the next cycle and in reviewing a completed cycle.

    product delivery and installation
    Q: How is Arum DataEye® delivered?
    A:

    DataEye is delivered either as a Java application on our customer's own environment or else as an internet service hosted by us. In either of these configurations the user access DataEye in a web browser.