Preparing for Installation
The following sections contain information you should know as you prepare your environment for installing Federation Manager.
Installation Requirements
Following are the minimum requirements for your Federation Manager installation:
-
CPU and memory requirements are based on the needs of the web container.
-
100 MB of disk space for the working files used to create the WAR file, which is deployed to the web container.
-
100 MB of disk space where the application is deployed.
-
You must have system administrator privileges to install and run Federation Manager.
Selecting and Installing a Web Container
Before deploying Federation Manager, you must install one of the supported web containers. See Supported Web Containers to choose an appropriate server. See your chosen container's documentation for installation instructions.
Default Installation Directories
During a Federation Manager installation, two default directories are configured: /opt and /var/opt.
|
/opt |
The default installation directory where the Federation Manager package, SUNWamfm, is physically copied. Note – The default installation directory can be changed before installation by modifying the file you create from the fmsilent-template. For more information, see The Silent Installation File. |
|
/var/opt |
The default runtime directory which contains debug and log file directories, a staging directory (containing the files used to generate the WAR), and default user and configuration data files. |
Staging Directory
Before a Federation Manager web archive (WAR) is generated, the files in the WAR are placed in a staging directory. The staging directory should be kept in a permanent directory as it will be used whenever Federation Manager is redeployed or, the SAML v2 Plug-in for Federation Services is installed and its operational commands used. The recommended path is /var/opt/SUNWam/fm/war_staging. The staging directory can not be moved after it is created without reinstalling the product. From the staging directory, the web container deploys an instance of the web application. Thus, any modifications to the Federation Manager web application must first be made to the staging directory which is then re-archived and the resulting WAR, redeployed.
Caution – Do not put the staging directory in a volatile place such as /tmp.
See Detailing the fmwar Syntax for more information on creating a Federation Manager WAR and staging directory for the first time.
- © 2010, Oracle Corporation and/or its affiliates