APPLICATION BRICKS

B1 Brick

a: "VISUAL PLANNING" rich client

The user connects from his workstation to the VPServer server using a W3C browser (IExplorer, Mozilla Firefox, Opera, Safari ...). The client application starts through the JavaWebStart module (java 1.7)

b: "VP Portal" web client

The user connects from his workstation to the VPServer server using a W3C browser (IExplorer, Mozilla Firefox, Opera, Safari ...).

c: “VPGO” mobile client

The user connects from a smartphone using the VPGO mobile application, available on Apple & Google app stores (Android 5 minimum, iOS 8 minimum).

B2 Brick: J2EE Server

The J2EE server is based on the TOMCAT 8.5 engine with JDK 1.7 or above. It is pre-set to receive the VPlanning application.

B3 Brick: VPlanning Application

The VPlanning application is the server part of Visual Planning and is pre-deployed on the J2EE server.

B4 Brick: Database Management System

(Can be MySQL 5.6 to 5.7, or Microsoft SQL Server 2008 to 2016, or Oracle 9i and above, or PostgreSQL 9.3, or MariaDB 10.1)

The DBMS server stores data of planners created and managed by VPlanning. The database is solely used for storage. The application does not use any type of trigger routine or stored procedure. Only the application server connects to the DBMS server.

B5 Brick: External Authentication Server (optional)

The Visual Planning Application uses its own management system to authenticate users. However, it is possible to shift the authentication system to external solutions such as LDAP (OpenLDAP, Lotus, Active Directory…) or SSO.

ghostghostghostghostghost
loading table of contents...