Introduction

This illustration shows the architecture of the Hackystat system itself:

As we can see there are some internal services (Green circles) that are interacting with each other and with external services (Gray circles). The HSM provides an architecture for managing the internal services.

HSM Architectural Overview:

The picture shows three layers.

1. The Hackystat system and its internal services
2. The Agent Layer that implements monitoring (M) and execution (E) functions
3. The Hackystat Service Manager layer that holds following conceptual components:

• Analysis Component
• Plan Component
• CBR component
• Graphical User Interface (GUI)

The Agent Layer

Each Hackystat service is associated with its Agent, the Agent implements monitoring and execution functions on the Hackystat service. Agents them self are SOA services and implemented in RESTlet. Thus distributed services can be accessed from the HSM. An agent has no direct dependency on a Hackystat service but uses its REST API and monitors the environment it is running in. Therefore an Agent has to be installed on the same machine as the Hackystat service.

Hackystat Service Manager layer

Autonomic computing suggests that one follow the M*onitor, A*nalysis, P*lan and E*xecute cycle (MAPE) as described in this illustration:

As we can see the HSM architecture is implementing the MAPE-cycle. In the implementation it is a Java Thread with four appropriate functions

• monitor()
• analysis ()
• plan()
• execute()

that are executed in one after another in the run()-method if needed. For example if the analysis returns a positive result no planning and execution is needed.

The plan()-method sends a request of the actual case to the CBR-engine which is implemented with jCOLIBRI 2.1.

For more inside into the architecture please refer to the Developer-Guide, User-Guide and Source code.