Automated Private Station for End Users

Station Launcher lets users start a local private 3DOrchestrate Station.

A private station will only execute simulation jobs initiated by the same user on the same computer. Only jobs from this user will be allowed to execute on this station computer.

You might need to install and configure an updated version of the Java Runtime Environment (JRE) to use 3DOrchestrate Stations in a production environment. For more information, see Java Runtime Environment (JRE) Requirements.

A 3DOrchestrate Station installed manually on any computer must normally be started from the command line using the following Windows batch file or Linux shell script: 

<station_install_dir>/<os>/code/command/SMAExeStation[.bat|.sh] [private:true}

Alternatively, an end user of the simulation client apps can start a local private station on their computer by choosing Station Launcher from the action bar or compass:



Station Launcher is available in the client apps UI from two places:

  • the Execution section of the action bar within the Process Composer native app
  • the 3DEXPERIENCE platform Compass in the simulation process web apps (Process Composer web, Performance Study, Results Analytics, Simulation Companion)

When the Station Launcher is used, the end-user is already authenticated by means of 3DPassport single sign-on (SSO). When a station starts in private mode from the command line, the user is separately prompted to enter 3DPassport authentication credentials (username and password).

In the Process Composer native app, users do not need to explicitly start the private station—when they execute a simulation process that specifies local execution, the 3DEXPERIENCE platform automatically starts the station on that computer.

A user who is connected to a Dassault Systèmes cloud server can also choose Station Launcher from the compass or action bar—the station software is automatically downloaded and installed on the user's computer. This action relies on the prerequisite 3DEXPERIENCE Launcher; for more information, see 3DEXPERIENCE Platform Guide: About the 3DEXPERIENCE Launcher.

The 3DEXPERIENCE Launcher is a prerequisite and must be installed before using the Station Launcher, for both on-premises and cloud servers.

The native simulation apps installation embeds the 3DOrchestrate Station software. If desired, this station can be customized by editing the SMAExeStation.properties file in this directory: 

<station_install_dir>/config/SMAExeStation.properties

See Station Properties File and Startup Command-Line Options for details.

Warning:

Simulation processes from any client app fail to execute on a private station if the 3DSpace server uses a DNS alias for the hostname. There are two possible workarounds for this problem:

  • Have users enter the actual hostname (not the alias) of the 3DSpace server when they start the 3DEXPERIENCE platform native client or web client.
  • Use a reverse proxy server in your 3DEXPERIENCE platform infrastructure to switch over to a different server, instead of using DNS aliases.