Note: documents can be either stored on file storages (e.g. file system) with a path reference in the database or as binary content (BLOB) in the database
For more details on generic integration components (webservices, I/O interface, etc.) please refer to the documents referenced in the Integration services section of the documentation index. Some of these generic webservices are wrapped into generic libraries/APIs in various technologies, please refer to the documents referenced in the APIs section of the document index.
Beyond these generic integration components, Simplicité being a Java platform, any kind of integration that is possible in Java is possible with Simplicité. Some examples are available in this document but many other third part public or private services integration can be implemented.
Please refer to this document for details on compliant components (OS, application servers, database, browsers, ...).
Exposing the application server thru a Apache/NGINX reverse proxy as described bellow is not mandatory but rather a good practice.
In this mode the publication layers (UI and API) have direct access to Simplicité engine.
JEE web profile mode
In this mode the publication layers (UI and API) have access to an EJB lite-wrapped Simplicité engine.
JEE full profile mode
In this mode the publication layers (UI and API) have access to an EJB wrapped Simplicité engine.
Simplicité instances can be clustered to provide several nodes using the same database, the right approach for load balancing being a sticky session load balancing.