The following arguments are available:
-f <script_file_name>
This argument executes the commands in the specified script file and then
exits.
@FILENAME
This argument allows you to read a set of
command line arguments from a specified file. The file must be a text
file containing command line arguments as they would usually appear on
a command line.
For example, if you had a file fipercmd.txt
in your home
directory that contained the following entries:
profile:acs1 logonprompt:no
# provide user name and password to connect
user:fiperacs pw:fiperacs
Then you could start the Command Line Client connected to the SIMULIA Execution Engine
with the following command (which assumes that the fipercmd.txt
file is located in the current working directory):
fipercmd @fipercmd.txt
You can also specify an absolute path to the directory containing the
fipercmd.txt
file:
fipercmd "@c:\documents and settings\user\fipercmd.txt"
Furthermore, you can mix and match the contents of the file with the actual
command line option at the command prompt. For example:
fipercmd @fipercmd.txt logonprompt:yes
Using the contents of the file created earlier, this argument would show
the logon dialog box (logonprompt
command) even though
the file provided everything necessary and also instructed the logon
dialog box to not appear.
The file you create can contain one or more lines. Each line can contain
one or more command line arguments. Arguments with spaces must be quoted
with single or double quotation marks. Comments lines are allowed (any
line starting with # is ignored). Empty lines are also ignored.
-help
This argument prints information about the available
command line arguments and then exits.
locale
This argument sets the locale (language environment)
for the current session. It is useful only when testing support for a
language. For example, typing fipercmd
locale:ja
displays all messages in Japanese. You can also use the shorter version
of this argument: -l
.
logfile
This argument allows you to specify a file
name and location for the Isight
log file.
loglevel
This argument allows you to determine what
information is sent to the terminal. Components create different levels
of log messages. You can define the minimum log information setting (debug),
and you will receive information on that particular level and all other
levels above it. For more information on log levels, see Setting Gateway Preferences.
The following log levels are available:
- syserror: a software system failure
- error: an error condition caused by usage, operational data, or some
other condition that can be corrected
- warning (default): a condition with which you should be aware but
does not generally indicate a failure
- info: routine status or other information
- debug: messages intended for debugging system or component code
logonmode:<gui|console>
This argument allows you to specify the type of logon you want to use.
The gui
option uses the Logon
dialog box. This setting is the default. The console
option allows you to specify connection information at the command prompt.
logonprompt:<yes|no>
This argument allows you to specify if the Logon
dialog box appears when the Command Line Client is executed. If you use
this argument to stop the Logon dialog box from
appearing (the no
option), you must specify a profile
name, user name, and password using the arguments in this list. Failure
to specify this information will cause the Command Line Client to cancel
the logon and to exit.
nogui:true
This argument prevents fipercmd
from attempting to use
the display. It implies logonmode:console
. Use this
when running fipercmd
in an environment with no display,
such as Windows service or Linux Remote terminal.
profile
This argument allows you to specify the connection profile that the Command
Line Client will use. If you specify this argument without the logonpromt:no
option, the Logon dialog box will appear with
the given connection profile preselected, and you will have to specify
the user name and password for the connection profile.
Connection profiles are either file names (e.g., standalone.cpr
)
or profile names (e.g., standalone
). Profile names are
searched for in all .cpr
files in your home directory
and in the SIMULIA Execution Engine
and/or Isight
install directory.
If the connection profile cannot be found, use a full path to the
profile. For example:
fipercmd profile:C:\SIMULIA\Isight\2024\config\standalone.cpr