Navigation

Fimasys Technology Technical Architecture J2EE Framework
J2EE Framework

Fimasys J2EE Framework

The J2EE framework is the basic technological layer for the development of all Fimasys products, implementing Java technology in a multi-tier environment. 

This framework includes a software subletting, development norms and numerous transverse tools ensuring a uniform and rapid production of our applications, the re-use of functions built and a tolerance regarding enhancements. The objective being to enable R&D teams to use the tools to increase productivity and development homogeneity.

The framework enables Fimasys to: 

  • Increase the productivity 
  • Focus the development teams on the field and not on the technology
  • Ensure realisation homogeneity
  • Warranty performance level

Fimasys Application Resource Manager (FARM)

FARM is a comprehensive and flexible tool for managing the technical content of ProFinance and can be used to define reports and interfaces

The majority of Fimasys' applications are graphed to the FARM structure (Fimasys Application Resource Manager). This structure proposes a great number of functionalities.

Content and Access

FARM provides the capability to store the lexical content of our applications under a hierarchic and typified form. Therefore, it is possible to determine objects able to correspond to a reference, to an image or to the wording of a button field or menu item.  It is possible to define help pages, to link them to the pages of the application. The users of the application have a "web" profile and an access profile. The Web profile allows administrators to define translations for each of the objects and pages of help, and then to configure different regional parameters such as the date separator to use, or the number of decimals, which includes the rates. Regarding the access profile, it facilitates the restriction of access by user to certain pages or objects. 

Parameter setting FARM

This function enables the parametrisation of our applications and in particular all that concerns the editions and the referential tables of the logged application. We are able to define editions, their content, link them to access profiles and finally, link them to specific pages. Finally, it is possible to parametrise the reference of the application by specifying the administration tables of the application database that has to be parametrised. This means that we do not need to develop administration functions (creation, modification, suppression) for a large part of the reference parameter tables of any other application, by using a generic interface of administration of the content of these tables.

The FARM application

In order to simplify the different parameter settings explained above, our database is accompanied by an application allowing our developers to inform the base, and allowing our customers to change and to customise their application.

The software subletting

In order to normalise and facilitate our applications development, we have set-up a software subletting J2EE. Our developers are then able to find themselves easily from an application to another and especially, not to worry about programming and optimisation of redundant functional building blocks. A great number of functionalities are already taken into account by our data-processing structure, in particular session management, applications or session data framework, the automatic redirection to the correct page according to the navigation parameters or the feedback included in FARM. This subletting was set-up according to some object concepts. Its main structure was based on the Model View Controller (MVC-2) pattern.

The model

Our model uses the EJB Session Façades above EJB Session themselves graphed to CAD. This policy was adopted whereas the EJB technology was very young. It seemed to be the best compromise between facility of development and performances. Indeed, at this period, the use of EJB Entity wasn't satisfactory. Our policies is being changed for the use of these Entity with the advent of the EJB 2 norm. 

The view

Our view is realized with the help of the JSP technology enriched of a template system and of a Tag Library.

The controller

Our Controller is a mono Servlet system. This Servlet interprets a received request and delegates its treatment to the concerned "sub-controller" which is a simple Java class. This "sub-controller" queries the model and feeds the data in session.

Transverse libraries

Fimasys develops software libraries gathering tools giving the possibility to face the redundant problems. These libraries can be divided in 2 categories, JavaScript libraries and Java Libraries. 

JavaScript libraries

These libraries include tools allowing to simplify the navigation through our applications. We can note structures of help at seizure or of format control or of type of field (numerical, dates...).

Java Libraries

They propose HTML generation tools for the elaboration of functional complex structures such as trees or multi pages lists.

Moreover, they offer lower level tools such as XML parsers, mask systems, or classes facilitating the access to the databases or to the JNDI trees.