Pulsar has developed its own GID Internet Development Platform starting from the standard JSParchitecture, allowing developing complex interactive internet-based application in a minimal time (GID1).
In a second phase, Eurocontrol/EATMP/DSA/AIM started a new project with Pulsar to enhance GID platform (GID2). Today both Pulsar and DSA/AIM teams benefit of the new platform and can make developments or enhancements by their own.
More, any technical team within Eurocontrol wishing to have the knowledge and develop itself based on GID platform can obtain freely the licensing for the Development phase. Thus, GID is today a stable platform fully compliant with the IT requirements in Eurocontrol.
Pulsar GID Platform Features
Benefits with Pulsar GID development platform
A stable and standard Web-enabled architecture: new applications or modules can be integrated smoothly and with minimal effort. This allows having the same look for Intranet and Internet screens and "publishing" new screens in Internet without any development effort.
|Portability: the new platform is as portable as possible from one IT system to another, allowing future changes of the technical infrastructure (OS, server hardware, devices, web and application server, etc) without or small impact in the application software.
Connectivity: the new system can assure a pre-defined frame, based on API layers to define, to easily connect to other Eurocontrol IT systems.
Availability: the new applications developed on this platform must be able to support a high availability towards user requests, not only during the office hours but also during the Week-End, late in the evening or early in the morning.
Standardization: for future evolutions preserving today’s investments, this is a unique and consistent open-source and EurocontrolÂ’s standard platform, open source minded. This avoids mixing technologies (like client-server, Access, etc).
Shared platform between Eurocontrol and Pulsar: GID allows EurocontrolÂ’s developers to develop by their own enhancements of the application or completely new modules. No dependency on Pulsar as a supplier of services (but at request we can offer the needed support or maintenance activities).
Any JDBC Relational Database: GID can connect to any JDBC relational database, including Access, to extract data.
Middleware: GID can act itself as a middleware, allowing connecting easily to other tools by different means: csv or XML files thru the file system, TCP/IP connection, etc. The technique is the same as for the rendering of HTML pages from database information: instead of the database a file is read, instead of rendering HTML page to the client he’s delivering the information to another application or another module of GID.
Evolution: GID allows thru its JSP architecture to easily plug new beans or other modules, specific to the business.
Pre-defined features: User Groups features, LDAP API, web security features + protected file system directories, dynamic error messages system, pre-defined system parameters table allowing to tune the functioning of the application thru administration parameters, etc.
GID Architectural Concepts and Components
Oracle Business Components (BC4J) = java layer abstracting the access to the database, implementing the structure of the database in entities and object views, using a caching system for performance reasons. The GID developers needs to create, with Oracle Jdeveloper tool, the Business Components specific to their client database (entities for tables, object views for joined tables, etc)
Server File System = server side file system, with protected directories for security, with possible sub-directories allowed for each user (for iUpl/iDownl)
The following technical components of GID are used to implement some of the flows (these components are only used by GID kernel and are not manageable by GID developers):
iError_Handler (iERR) = component implemented in java classes instantiated by iCTRL and/or iCALL whan an error occurs.
Database_Connection_Pooler (iPOOL) = singleton started by iCTRL that manage the connection to the database. Each bean or java class that needs to connect to the database asks a connection to iPOOL that offer it. When a component releases a connection, iPOOL recuperate it to use it for another component requesting a connection. In the configuration file of the application server some environment parameters define to which schema (in Oracle terminology) to connect.
ISEQUENCER (iSEQ) = singleton started at initialization of iCTRL that generates sequences and counters at request.
ClassLoader (iCLASS) = java component allowing GID to be "JVM-tolerant": GID loads its own libraries in the JVM independently from whatever other application present in the JVM, avoiding interference between different versions of the same library loaded by GID and another application.
The following main components of GID are highlighted in the diagram. These components are available to the GID developers:
|iBEAN_CALLER (iCALL)= bean started in the unique jsp page page by iCTRL, which connects to iREPO and fill-in a new jsp page with all beans of the page requested by the user
iRAD Wizard example: Users and Groups Association