Large File Management

Large file management is a system-internal utility that speeds up the transfer of files between your Process Composer file store and the 3DOrchestrate Station where the simulation application is executed. The Process Composer file store is part of 3DSpace.

This page discusses:

For complete information about large file management in the 3DEXPERIENCE platform, see the following topic:

Installation and Setup | Administrate | 3DEXPERIENCE Platform | 3DSpace Administration | File Collaboration Server | Large Files

After the system administrator has configured large file management on the FCS and 3DOrchestrate Stations, its use is transparent. Process Composer and the 3DOrchestrate Station automatically determine the most efficient method for transferring a file, and no additional action is required.

Configure Properties File on each 3DOrchestrate Station

To enable large file management for simulation files, you must configure every 3DOrchestrate Station on which Process Composer jobs will be executed.

Locate the following properties file in the station software installation:

<station_install_dir>/config/SMAExeStation.properties

Define the following values in the SMAExeStation.properties file on each 3DOrchestrate Station:

fiper.station.tempdir=temporary-directory-path
fiper.station.fcs.stagingdir=staging-directory-path
fiper.station.fcs.serverstagingdir=staging-directory-path-fully-qualified

Set these properties to point to directories that exist on the same file system as the File Collaboration Server (FCS) path, for example:

fiper.station.tempdir=/scratch/station/temp/
fiper.station.fcs.stagingdir=/scratch/station/staging/

The stagingdir is a staging directory for FCS checkins and checkouts. The stagingdir directory must be on the same physical device and logical file system as the station temporary directory (fiper.station.tempdir).

If you are enabling large file management on a Windows station computer, you should provide a complete UNC style path to the tempdir and stagingdir directories; for example, \\hostname\scratch\station\temp\. If you use a drive letter, it must be the correct mapping on both the FCS server and the station computer.

The server staging directory (serverstagingdir) should be set to the fully qualified path name of the stagingdir. The server staging directory defines how the 3DSpace Main Collaboration Server (MCS) will access the path defined in the stagingdir property. If the MCS can directly access the staging directory path, then the server staging directory path need not be defined. Otherwise use this property to define the exact path for how the MCS will find the staging directory.

For example, if the staging directory is defined as:

fiper.station.fcs.stagingdir=\\filer2sim\e4all_fs\vm8-29sim\home\STAGING

then you may need to define the server staging directory as:

fiper.station.fcs.serverstagingdir=/e4all_fs/vm8-29sim/home/STAGING

For complete information about 3DOrchestrate Stations and the SMAExeStation.properties file, see the 3DOrchestrate Administrator's Guide.

Configuring the Live Collaboration FCS File Store

To take advantage of large file management, you must have the station's temporary directory and the staging directory (stagingdir) on the same file system as the store directory that is used to store Process Composer data. See Vaults and Stores.

You can use the ENOVIA Studio Modeling Platform tools to create or edit the Process Composer file store such that the store directory is on the same file system as the staging directory and temp directory. You must use a captured store, and file name hashing must be enabled.

If you create a new file store, you must update the Simulation Document policy so that it uses the new store; the Simulation Document policy can be updated using the ENOVIA Studio Modeling Platform MQL app. For more information, see the following topic:

Installation and Setup | Customize | Legacy Tools | MQL Command Reference | Policy Command