As described in Starting Fluent In Server Mode, when you start a Fluent as a Server session, a keyfile is created in the session working directory that contains the information required for a client application to connect to the session. The keyfile is simply a text file containing an Interoperable Object Reference (IOR) string that contains encoded information about the host, port number, and protocol for connecting to the Fluent as a Server session.
The keyfile will be named according to the first value from the following hierarchy:
the name specified with the Fluent command line
option, —aas_key_file=<keyfilename>.
the value of the FLUENT_AAS_KEY_FILE environment variable.
the default name, aaS_FluentId.txt.
If the desired keyfile name already exists and refers to a running Fluent as a Server session, the new Fluent as a Server session will fail to start. This is to prevent inadvertently overwriting a keyfile that may be needed by another user.
Important: While it is technically possible to start multiple Fluent as a Server sessions in the same working directory by specifying different keyfile names, this is not recommended as it could lead to inadvertent user file conflicts or corruption. For instance, two users, each running their own simulations, could both attempt to write out contour plots titled pressure_contours.png leading to one user inadvertently overwriting the other’s file.
Note that spaces are allowed in the filepath
of the keyfile, even though typically Fluent text commands cannot
access such filepaths. For example, the following File Session Manager
command would not return an error: fsm.connect_to_session
"C:/Path With Spaces/aaS_FluentId.txt".