Sun Java System Federation Manager 7.0 User's Guide

The Silent Installation File

Before installing Federation Manager you must have a silent installation file for use as input to the installer. Included with the Federation Manager application is a template called fmsilent-template. After installation, fmsilent-template is located in the /FederationManager-base/SUNWam/fm/ directory. It is reproduced below and can be modified to create a silent installation file based on your deployment.

Example 2–1 fmsilent-template Silent Installation File Template


# The following entries contain sample values!
# These should be modified for your specific installation
# and then uncommented (remove the # from the line)


Delete the # before the variables you want to modify and enter the appropriate values. Save the file and install Federation Manager according to the instructions in Federation Manager Installation Options. Following are definitions of the variables in the fmsilent-template file.

Table 2–1 Silent Installation File Variable Definitions

Silent Installation File Variable 



Defines how the XML parser will read your character set. ISO 8859-1 defines the Latin 1 character set.


Defines the default installation directory for Federation Manager. By default, this is /opt. See Default Installation Directories for additional information.


Defines the default runtime directory for Federation Manager. This directory is created by fmwar with the contents assigned the user and group ownership specified by the values in FM_PROCESS_USER and FM_PROCESS_GROUP. For more information, see Default Installation Directories.


Defines whether the cookie should be encoded or not. By default, this value should be set to false. This attribute will update the property in

Caution – Caution –

The value of this property is dependent on the web container in which Federation Manager is deployed. For all currently supported web containers, the value must be left false.


Defines the protocol used by the web container on which Federation Manager will be deployed. 


Defines the Federation Manager WAR deployment URI. It is also used as the name of the generated .WAR file by default.


Defines whether the Liberty and SAML samples will be deployed as part of the Federation Manager installation. 


Defines the user under which Federation Manager runs. 

Note –

It is recommended that FM_PROCESS_USER specifies a user ID that is different from the super user like root. Typically this user is the same as the user under which the underlying web container runs.


Defines the group to which the FM_PROCESS_USER belongs.


Defines the root node for the Federation Manager configuration data. The value of this variable is written as dc=orgname,dc=com. If Federation Manager uses an LDAP directory to store its configuration, this becomes the root suffix. If Federation Manager uses a flat file to store its configuration, this value becomes the top level directory name of the file system by inverting the sequence and using the comma as a delimiter. Using the values from the template in Example 2–1, the flat file directory structure would be /var/opt/SUNWam/fm/federation/dc=com/dc=orgname.


Defines the host of the web container on which Federation Manager will be deployed. 


Defines the port of the web container on which Federation Manager will be deployed. 


Defines the password for the Federation Manager administrator. The default administrator is amadmin.