The architecture of Fura EE has been designed to be extremely agile and scalable. The robust Grid Container allows the development of Grid Services which can easily be tailored according to the customers' needs in order to dynamically adapt to the IT environment. The following list provides a view of the standard services in Fura EE, but developing new services to comply with the existing or future needs of our customers and partners is extremely easy:

• File & User System: This Grid Service provides Authorization, access Policies, and an Virtual File System, and it is a fundamental piece of Fura EE.
• Agent Broker: This Service allows a semi-automatic splitting of tasks in smaller microtasks, which will become the pieces of computation sent to the computing resources.
• Computing Resource Manager: This Service registers and manages the computing resources present in the grid.
• Monitoring and Metering: This Service stores different average values and summaries regarding the Grid usage, and can be used to develop billing systems.
• Module Manager: It allows the grid-enabling of applications by providing the Grid with the metadata necessary for the execution of a certain application (input parameters, input files, output, exit codes, meaning of the parameters, invocation on different operating systems, etc.)
• Server Execution: This Grid Service provides the interface for launching jobs on the server machine where the Grid Container is running on. The Grid Service is capable of managing a list of processes (starting, killing, retrieving standard output and error, etc.)
• Subordinate Server: This Grid Service converts a computing resource where it is installed as a subordinate or secondary Grid Server that can receive microtask assignments from another Grid Server and assign it, in turn, to the computing resources that depend on it. It should only be installed in subordinate Servers.
• Subordinate Server Broker: This Grid Service is responsible for managing the communications and work assignments between a main grid Server and a subordinate Grid Server (those with Subordinate Server installed). This Service is to be installed only on the main Server, and only if a subordinate Server will be part of the Grid.
• Messaging: This Grid Service is a mailing service that can be used by other Grid Services. Currently, messaging is used by other services so that users are notified via e-mail when a task finishes and when a scheduled task begins its execution.
• Task Submission: It allows the creation, edition, and execution of those grid-enabled applications defined by the Module Manager. Part of this component is in charged of dispatching the computable items (microtasks) to the computing resources. It is also able to handle caching requirements and monitoring executions in order to assure a proper quality of service.
• Workflow: This Service executes and manages the execution of sequenced Fura EE tasks according to the requirements established by the user.
• Etc.

A more detailed description of the services and architecture can be found in the documents available in our Download/Product Documentation section.

A Fura EE platform contains a collection of production tools developed by GridSystems that can be launched from the Grid Portal. These graphical tools are designed to facilitate the configuration, and management of the Grid platform:

• Fura EE Portal: The Portal is the web-based graphical interface to access all of Grid functionalities and objects, including the rest of tools.
• GridTask: GridTask is the tool used to create and manage tasks. Tasks are the actual Grid work which will be divided and distributed to the appropriate Agents to be executed.
• Resources: Resources is the graphical interface to configure and manage all the grid resources, meaning all the Grid working units. This is the interface to the Fura Agents or any other resource able to receive a Grid command from a Fura Server and execute a grid work.
• Security: Like any operating system nowadays, Fura is designed with a user system to authenticate, authorize, and log Grid access and usage. Access to the grid is organized through authenticated users. This tool is used for the management and configuration of users and roles (groups of users).
• File Viewer: File Viewer is the interface to the Server's File System. It allows the uploading, downloading, moving, etc of files as well as the management of files and folders and their permissions.
• GridView: GridView is the monitoring tool; it gathers and shows statistical data on the use of the Grid. Through this tool, the Grid administrator can visualize and monitor the Grid performance. This tool can also be used for billing purposes.
• Workflow: Workflow is an extension of the GridTask tool. The workflow tool allows you to concatenate several Grid tasks.

• GridStudio: GridStudio is an graphical tool for rapid application virtualization. For example, it is possible to virtualize legacy applications in minutes.

• Software Development Kit (SDK): All the graphical tools explained above are just the implementation of a subset of all the Fura EE functionalities, which are accessible through the API. The SDK does include access to all the API functionalities; plus, it comes with all the necessary documentation for you to understand its functionality and use.