Safe Software FME

Views: 1.2k  |  Created: 06/01/2009

Average Rating: 0
FME has 1 inventory records, 0 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (1)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 3 / 5 (Average) based on 1 ratings
Most Commonly Reported Deployment Method
Vendor Provided Command Line (answer file driven)
or cancel
6
Note
Copied from http://www.fmepedia.com/index.php/Can_I_install_FME_from_the_command_line (because stuff goes missing after a while.)

Rumor is the next release of the PKG will be MSI. It could still be FME2009 but a different build number.
======================================================
Command Line Switches (flags) [for silent install]

The install only supports two switches at the actual command line. Directives must be placed in a parameter file and referenced (/m=<file>).

Switch Explanation

/m Manual-override (i.e. use directives). Specifies the path to a parameter file that contains directive values. This switch requires an equal sign (=) and then the full path to the parameter file. Example: fme_beta.exe /m=myparams.dat

/s Silent. The GUI will not be displayed. An icon will be displayed in the system tray. A tool tip will display overall progress.

*Parameter File Directives*

Directives are specified in the parameter file, one per line, in the following format:
<directive name>=<directive value>

*Installation Directory Directives*
By default, the installer places files in several locations. These directives allow those locations to be overridden as necessary. All directives need to be followed by an equal sign (=) and then the full path. See examples below.

Directive Explanation
MAINDIR Indicates the full path location of the main installation directory. If the directory does not exist, it will be created. Spaces are OK on the path. Quotes must not be used.
The default is C:\Program Files\FME Suite
SAFE_COMMON Indicates the full path location of the FME shared components (components shared between FME installations & other OEM applications) directory. If the directory does not exist, it will be created. Spaces are OK on the path. Quotes must not be used.
The default is C:\Program Files\Common Files\Safe Software Shared


NOTE! Do not use this directive unless you know what you're doing; it could really mess up how FME runs.
FME_OBJECTS_PATH Indicates the full path location to the directory where the FME Objects dll will be installed. If the directory does not exist, it will be created. Spaces are OK on the path. Quotes must not be used.
The default is C:\Program Files\Common Files\Safe Software Shared\FME Objects


NOTE! Do not use this directive unless you know what you're doing; it could really mess up how FME runs.


*Installer Behaviour Directives*

The installer's runtime behaviour can be changed via these directives.

Directive Explanation
ENABLE_SOUNDEVENTS Setup sound events.
Allowed values are yes and no. Default is yes.
CHECK_ADMIN_RIGHTS Check to ensure that the user installing FME has admin priviledges.
Allowed values are yes and no. Default is yes.
CHECK_INTERNET_EXPLORER Check if Internet Explorer > 5.5 is installed.
Allowed values are yes and no. Default is yes.
EDITORSUPPORTDIALOG Show the editor support wizard page.
Allowed values are yes and no. Default is yes.
USAGESTATISTICSDIALOG Show the usage statistics wizard page.
Allowed values are yes and no. Default is yes.
SERIALNUMBERDIALOG Show the serial number wizard page.
Allowed values are yes and no. Default is yes.
ENABLE_UNINSTALL Leave the proper bread crumbs that allow FME to be uninstalled.
Allowed values are yes and no. Default is yes.
ENABLE_SHORTCUTS Create shortcuts in the Windows Start Menu.
Allowed values are yes and no. Default is yes.
ENABLE_FILETYPE_REGISTRATION Register FME applications as being able to view, open, etc FME files and GIS data files.
Allowed values are yes and no. Default is yes.
ENABLE_DLL_SELF_REGISTER Self-register COM objects installed by the installer.
Allowed values are yes and no. Default is yes.
ENABLE_POST_INSTALL_TASKS Run the License Wizard & FME Administrator when the installer is finished.
Allowed values are yes and no. Default is yes.
ENABLE_SYSTEM_REBOOT Allows the installer to prompt the user to reboot the machine (if neccesary).
Allowed values are yes and no. Default is yes.
ENABLE_PATH_UPDATE Allows installer to update the 'PATH' environment variable.
Allowed values are yes and no. Default is yes.
ENABLE_STANDARD_EXE_INSTALLATION Install all the standard fme executables (viewer, workbench, etc).
Allowed values are yes and no. Default is yes.
ENABLE_LICENSE_COPY Allows installer to search for old license files, and copy them into the current install folder if present.
Allowed values are yes and no. Default is yes.
ENABLE_POST_INSTALL_TASKS Controls whether the license wizard is run after the installer has completed. See also FMEREG_CMDLINE.
Allowed values are yes and no. Default is yes.
FMEREG_CMDLINE Overides how the installer calls the license wizard post-installation.
Allowed values are any command-line parameters supported by the license wizard.
Using the value /no_extend will prevent the FME Administrator from auto-extending 3rd party applications supported by FME.
ENABLE_ZERO_SIDE_EFFECT Sets the following options to "no":

ENABLE_SOUNDEVENTS, CHECK_ADMIN_RIGHTS,CHECK_INTERNET_EXPLORER,EDITORSUPPORTDIALOG, USAGESTATISTICSDIALOG,SERIALNUMBERDIALOG,ENABLE_UNINSTALL,INSTALL_SYSTEM_DLLS, ENABLE_SHORTCUTS,ENABLE_FILETYPE_REGISTRATION,ENABLE_DLL_SELF_REGISTER, ENABLE_POST_INSTALL_TASKS,ENABLE_SYSTEM_REBOOT,ENABLE_PATH_UPDATE,ENABLE_LICENSE_COPY
Allowed values are yes and no. Default is no.
File Installation Directives

Some of the files installed by the installer can be omitted via these directives.

Directive Explanation
INSTALL_SYSTEM_DLLS Update older system dlls as needed, and run the Microsoft Visual Studio C++ Runtime Installer
Allowed values are yes and no. Default is yes.

Note: If set to 'no', the user is responsible for manually running the C++ Runtime installer, and ensuring that atl.dll and atl71.dll are installed on the target system. This option is not recommended, and may lead to non-functional FME installs.
INSTALL_THIRDPARTY Install Application Extenders.
Allowed values are yes and no. Default is yes.


Note: Enabling is controlled by the FME Administrator.
INSTALL_FMEOBJECTS Install FME Objects dlls and other components.
Allowed values are yes and no. Default is yes.
INSTALL_GALLERY Install the gallery directory.
Allowed values are yes and no. Default is yes.
INSTALL_HELP Install the help directory.
Allowed values are yes and no. Default is yes.
INSTALL_HELP_DLL Install the help dlls.
Allowed values are yes and no. Default is yes.
INSTALL_METAFILE Install the metafile directory.
Allowed values are yes and no. Default is yes.
INSTALL_PLUGINBUILDER Install the pluginbuilder directory.
Allowed values are yes and no. Default is yes.
INSTALL_REPROJECT Install the Reproject directory.
Allowed values are yes and no. Default is yes.
INSTALL_TCL Install the tcl directory.
Allowed values are yes and no. Default is yes.
INSTALL_WORKBENCH_EXE Install the workbench application. Allowed values are yes and no. Default is yes.
INSTALL_FME_EXE Install the fmeapplication.
Allowed values are yes and no. Default is yes.
INSTALL_FMEADMIN_EXE Install the fme administrator application.
Allowed values are yes and no. Default is yes.
INSTALL_FMEVIEW_EXE Install the fme viewer application.
Allowed values are yes and no. Default is yes.
INSTALL_FMEGUI_EXE Install the fme universal translator gui application.
Allowed values are yes and no. Default is yes.
INSTALL_FMEREG_EXE Install the fme license wizard application.
Allowed values are yes and no. Default is yes.
INSTALL_DFAD_DLL Install the dfad dll.
Allowed values are yes and no. Default is yes.
INSTALL_WHATSNEW Install the what's new/great text files.
Allowed values are yes and no. Default is yes.
INSTALL_FMECOMUTIL_DLL Install the fmecomutil dll.
Allowed values are yes and no. Default is yes.
INSTALL_FME_SHELLEXT_DLL Install the fme shell extension dll.
Allowed values are yes and no. Default is yes.
INSTALL_SPATIAL_ASSISTANT_EXE Install spatialassistant.exe.
Allowed values are yes and no. Default is yes.
INSTALL_FMEGEOS_DLL Install geos_fme.dll.
Allowed values are yes and no. Default is yes.
INSTALL_SDE_DLL Install the sde dlls.
Allowed values are yes and no. Default is yes.


*undocumented Directives*
ENABLE_NAD83_NAD27_DATUMSHIFTS installs the files nessary for the "Canadian NAD83<->NAD27 DATUM Shift"
Allowed values are yes and no. Default is no.

ENABLE_PATH_UPDATE=yes Appends the PATH environment variable with the value of MAINDIR (e.g. c:\Program Files\FME) Allowed values are yes and no. Default is no.

ENABLE_OVERRIDE_REALDWG Yours to discover, Allowed values are yes and no. Default is no.

FLAG_MRSID_LICENSED Yours to discover, Allowed values are yes and no. Default is no.


*Examples*
fmeinstaller.exe /M=values.dat

This will throw up the installation GUI, but the default installation directory will be replaced with whatever is specified after MAINDIR= in values.dat.

fmeinstaller.exe /S

This will install in the default directory for the installer but will not display the GUI while doing so.

fmeinstaller.exe /S /M=values.dat

This will silently install into the directory specified after MAINDIR= in values.dat. The following are examples of the contents of the values file. This file does not have to be called values.dat, but must be a text file.

MAINDIR=C:\Program Files\FME2004Test

MAINDIR=C:\Program Files\FME Suite Test Installation directory
SAFE_COMMON=C:\Program Files\New FME Common


Notes
When the installer runs silently from the command line, it appears to return immediately, with the installation process occurring in the background. The process has actually been relegated to running in the system tray. A tool tip will display overall progress. A file called INSTALL.LOG is placed in MAINDIR after installation has completed.

When the installer runs silently from a script, the script waits for the process to end. It is always a good idea to check INSTALL.LOG in MAINDIR for error messages before proceeding.


*How to automate the licensing* (UNDOCUMENTED!)
-Install and License manually.
-Then copy c:\Program Files\FME\licenses\flexlm_config.dat
and c:\Program Files\FME\licenses\fme_license.dat
Insert these file into all future installs.
Hint: use ENABLE_POST_INSTALL_TASKS=no to stop the licensing wizard from appearing.


*Unattended UNinstall*
C:\PROGRA~1\FME\UNWISE.EXE /S C:\PROGRA~1\FME\INSTALL.LOG

@echo Make sure any project info is backed-up
@echo then to delete the remaining files
@Pause

RD /s /Q "C:\Program Files\FME"
RD /s /Q "C:\Documents and Settings\All Users\Start Menu\Programs\FME"

pause
::CAVEAT: the PATH env. var. Will still have C:\Program Files\FME at the end!


=======================================================

BTW, if you want to repackage into MSI please be aware of:
During install with Original source, copies TWO VCREDIST exes to C:\Program Files\FME
vcredist_x86_vs2008.exe
vcredist_x86.exe
Which are installed and then deleted!
Python 2.5 also included with FME2009 (FME will only use its Python when no other installation of Python can be detected.)
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

FME

Version

9

Questions & Answers (0)

Questions & Answers related to Safe Software FME

Blogs (0)

Blog posts related to Safe Software FME

Reviews (0)

Reviews related to Safe Software FME