About Possible Architectures

The following diagrams focus on REST server components. ENOVIA components are displayed in blue. ER Agent components are displayed in green.

This page discusses:

See Also
Standalone ERAgent Security Recommendations

3DSpace Architecture



In a 3DSpace architecture:

  • The ERAgent is fully embedded into the 3DSpace web application. There is no need to deploy it.
  • The ERAgent native API handles queries and forwards them to the ENOVIA API and the FCS API.
  • Security is delegated to the 3DSpace security component that provides ENOVIA connections to the ERAgent native API.

Standalone Agent Architecture



In a standalone mode:

  • Deploy the ERAgent. See Installing the ENOVIA Standalone ERAgent.
  • The ERAgent components are embedded into a Jetty server provided with the Standalone agent package.
  • The ERAgent native API is strictly the same as the 3DSpace mode one.
  • The ERAgent manages security and delegates authentication to the ENOVIA API.
  • All ENOVIA native components run inside the java process of the Jetty server. There is no other process for the ERAgent.