Configuring a New Station

You can configure various properties of each 3DOrchestrate Station on your network.

There are two ways to configure a station:

  • in the SMAExeStation.properties file and ApplicationInfo.xml file in the station installation
  • by using the Station Administration dashboard app

You can define a new station configuration in the Station Administration app either before or after the station software is installed on the physical computer.

See Also
In Other Guides
Station Properties File and Startup Command-Line Options
Configuring the Station's Applications in ApplicationInfo.xml
About Run-As Security
  1. Select the 3DOrchestrate Distribution Server that the new station is connected to (if you have more than one server).
  2. In the Properties Panel, click the Stations tab.
  3. Click Create Station .
  4. Enter or select the following properties:

    Property Definition
    Name The default station name is the hostname of the computer on which it is installed. End-users can enter the station name in the client app GUI to direct the execution of their job to this station computer.
    DescriptionDescription of this station.
    Operating SystemWindows or Unix. Linux is considered a subset of Unix in this classification.
    Temp Directory

    The directory in which the 3DOrchestrate Station writes temporary files and log files during job execution.

    If you want to change this setting from the default location, be sure to select a directory that has the following characteristics:

    • Is not a temporary file system. This disk space must never be reclaimed automatically. This rules out any directories that are cleared during a restart or during an automatic disk space cleanup.
    • Preferably on a local disk on the station computer. If there is insufficient local storage space, a NAS device can be used; however, this is not recommended.

    Important: You must change this setting if you will use the 3DOrchestrate Station run-as security feature. Use a directory that can be accessed by all users; for example, C:\temp\ on Windows or /var/tmp/ on Linux.

    Staging Directory Directory for large file management in the Process Composer client app; used for FCS checkins and checkouts. See Process Composer (Web) Administration Guide: Configuring Large File Management.
    Custom AffinitiesSpecify application affinity keywords for the station computer. The value must be one or more affinity keywords, separated by spaces. Example: Abaqus. End-users can enter affinity keywords in the client app GUI. See About Station Affinities for details.
    Allowed UsersSpecify a (space-separated) list of 3DEXPERIENCE platform user names that are allowed to execute their jobs on this station. Example: joesmith betsyjones. If the list is empty, all users are allowed to use the station.
    ConcurrencyBecause the Java technology used in the 3DOrchestrate Station prevents monitoring real usage of CPU, RAM, and I/O, this setting can be used to cap the maximum number of execution threads allowed on the station. A station can run only a limited number of work items concurrently. Once that limit is reached, further work items received must be queued until an active one terminates. Limiting concurrency prevents the station application from overloading the computer it is running on. By default, the concurrency is two times the number of processors on the computer.
    DomainSpecify the Windows security domain for authentication of user credentials (username/password) when the station has run-as security enabled. By default, the Windows domain configured in the 3DOrchestrate Distribution Server is used. This property is ignored on Linux stations.
    Station IPIP address of the computer on which the station software is installed.
    Log LevelDebug, Info, Message, Error, or SystemError.
    Run-As

    Enable or disable the run-as security feature on this station. By default, the station follows the run-as configuration of the 3DOrchestrate Distribution Server to which it is connected (as determined by the fiper.security.runas.enabled property in the SMAExeServer.properties file). You can use this property to force the station to run with run-as security disabled even if the 3DOrchestrate Distribution Server has run-as enabled.

    This property can have the following values:

    • Disabled – Turns off the run-as feature for the station. It is valid only if the run-as feature is active on the 3DOrchestrate Distribution Server.

    • Enabled – Turns on the run-as feature for the station. It is valid only if the run-as feature is active on the 3DOrchestrate Distribution Server.