Results Analytics Servant and File Monitoring Services on Stations

Make several configurations for secure SSL/HTTPS communications between the 3DOrchestrate Stations and the client web apps (running in a web browser).

The simulation process web apps rely on 3DOrchestrate Stations in several ways:

Results Analytics Servant

Each station contains a Results Analytics servant that performs data computations for the app. The servant is essentially an HTTP server providing web services that operate on simulation data. See the following topic for more details:

Simulation | Simulation Process Modeling | Results Analytics | Introduction to Results Analytics | Results Analytics and 3DOrchestrate

File Monitoring Service

Each station also contains a file monitoring service that is used by the Simulation Companion, Performance Study, and Multiscale Experiment Creation apps.

The file monitoring service lets users monitor and navigate the results files created during execution of the simulation process. These files are kept in the execution directory. For more information, see Simulation Companion: Data and Jobs.

The client web apps communicate directly with an execution station using web services. With current web browsers, it is generally necessary that all communications between the web apps and stations be secure (encrypted) HTTPS. This means that the Results Analytics servant and file monitoring service require an SSL public key certificate, similar to any secure web server application. This certificate is separate from the certificates used by the rest of the 3DEXPERIENCE system: the reverse proxy server, 3DSpace, and other components.

The 3DOrchestrate Stations must also communicate securely with the 3DEXPERIENCE servers, usually through the reverse proxy server.

In a public (regular) station that is outside of the reverse proxy server, you must always configure a certificate for Results Analytics and file monitoring. In a private (local) station outside of the reverse proxy server, these web services are automatically preconfigured for HTTPS.

A public station provides remote execution—remote from the end user—with encrypted communication, without disabling the web browser security. Or, for a public station behind the reverse proxy server, only the standard ports (443) need penetrate through the firewall.

Detailed instructions for configuring station properties, SSL certificates, and the 3DEXPERIENCE reverse proxy server are provided in the following topics.