Starting Fire

Syntax

fire { application } { options ... }

Description

Enter the Fire application development environment.

Parameters

• application
  A Fire application archive (.mxa or .fsa) to execute. If omitted, the macro indicated by the -start option is executed.

Options

• -reg
  Register the Fire environment with the Windows registry. Any other command options are also registered for future ole deployment. Fire will not execute, but confirmation of successful registration is given via a message window. This option must not be used if Fire is located outside of the Xmarc installation file hierarchy.

The -reg option is applicable to Windows systems only.

• -env{=<dir>}
  If specified as a command line parameter, the following environment variables are set:

  Variable	Value
  MXSITE	<dir>/config (standard deployment)
  MXSITE	<dir>/web_config (browser deployment)
  MXSYS	<dir>/system
  MXBIN	<dir>/mx/<arch>/<os>/bin

  If the option is present but no value is supplied, then <dir> is derived from the location of the fire executable, by traversing up the file hierarchy.

• -root{=<dir>}
  If specified as a command line parameter, then similar to -env, but variables MXSITE, MXSYS and MXBIN will only be set to the above if they are not already defined.

• -h
  Prints a summary of the program usage (Unix systems only).

• -alog=<num>
  The initial level for service log messages when running as a service, registered to a FireRender service broker. If the -url option is not present, this option is ignored. The default value is 2.

• -appstart=<file>
  Run an application via a .fsc or .xml configuration file.

• -cd=<dir>
  Change to a new current working directory before executing the first language statement.

• -devel
  Start the Fire development system. The default behavior is not to. This can also be indicated by an entry in the Fire Configuration File (fire.ini). The development system will be invoked before any start macro or command line application is executed.

• -display=<dpy>
  Provide an X server/display for Fire to run in. The default is the value of the Unix environment variable DISPLAY. The -display option is applicable to Unix systems only.

• -fxenc
  Encode all database connection strings.

• -log=<host>:<port>
  Details of a service agent when running as a service, registered to a FireRender service broker. Service log messages are directed to this host. If the -url option is not present, this option is ignored. This option is appended automatically by the service manager system and s such should not be added manually.

• -mess=<>file>
  Use <file> as the source of system messages displayed by Fire. If this is omitted, the message file indicated in the Fire Configuration File (fire.ini) is used.

• -monitor=<num>
  Show the monitor window in full or iconic form on start-up. <num> should have a value of 1 or 0. The option -no_monitor is an alternative to -monitor=0. The default behavior is for the monitor window to be in full, i.e. not iconic. The initial state of the monitor window may also be supplied by a monitor entry in the Fire Configuration File (fire.ini).

• -monlog
  Save monitor output in a log file. The default behavior is (-no_monlog), do not save monitor output. This may also be provided by a monlog 1 (or monlog 0) entry in the Fire Configuration File (fire.ini).

• -netsock=<port>
  A socket through which peer processes can connect to Fire. This option determines the value of the system identifier network_socket. If omitted, a value zero is used, which means a port number will be chosen arbitrarily when required. It may also be provided by a netsock entry in the Fire Configuration File (fire.ini).

• -proxy=<string>
  Set details of a proxy web server for outgoing internet traffic. This is equivalent to setting the MXPROXY environment variable, and is typically not necessary on Microsoft Windows systems.

• -rt
  Run time only, no keyboard command input facilities (afire only).

• -sock=<port>
  A socket through which external commands are to be received (browser-deployment). This option is called automatically when Fire is invoked from a browser. It should not be used when Fire is started manually.

• -start=<file>
  Execute the macro file <file> on start-up. If this is omitted, the start macro as indicated in the Fire Configuration File (fire.ini) is executed. Use the option -no_start to suppress macro execution on start-up. Parameters within parentheses may be passed to the macro but the whole string, including file name, should be enclosed within double quotes to avoid problems with shell handling of special characters.

• -no_start
  Do not execute a macro on startup.

• -timreg=<num>
  When registering as a service set a timeout (in seconds) when waiting for the service broker to respond. The default is 30 seconds. This is only used in combniation with -url.

• -url=<url>
  Run as a service, registered to a FireRender service broker. <url> is the registration url.

• -web
  Run in browser-deployed mode (as a browser plug-in). This option is called automatically when Fire is invoked from a browser. It should not be included manually.

• -wm=<text>
  Provide the name of the X window manager. This is usually redundant since Fire attempts to detect it automatically. It may also be provided by a wm entry in the Fire Configuration File (fire.ini). The -wm option is applicable to Unix systems only.

• -xfont=<font>
  Provide a default X font for text display in widgets and graphics. If this is omitted Fire uses a default according to workstation type. It may also be provided by an xfont entry in the Fire Configuration File (fire.ini). The -xfont option is applicable to Unix systems only.

Options

As well as the above options, you can pass your own options to Fire. Their values can be accessed by the config function.

See Also