You can use the ca-Federation-installer.properties file to propagate the Federation Manager installation setup to other systems in your network.
Important! You must first run an attended installation to generate the properties file.
With this properties file do the following:
The ca-Federation-installer.properties file is created in the following location:
Windows: federation_mgr_home\install-config-info
Solaris: federation_mgr_home/install-config-info
The default parameters and paths in the file reflect the information you entered during the initial Federation Manager installation.
To modify the Federation Manager installation properties file
Note: The properties file is case-sensitive.
The parameters are as follows:
Defines whether the installation is a new installation, an upgrade, or a re-installation.
Default: INSTALL
Default (Windows): C:\\Program Files\\CA\\FederationManager
(Notice the double back slashes.)
Default (Solaris): an account on the system
Example: /home/myacct/CA/FederationManager
DEFAULT_JRE_ROOT
Indicates the location of the JRE.
JDK_ROOT
Indicates the location of the JDK.
#FEDADMIN_PW
Defines the password for Federation Manager. This must be uncommented, and the password must be supplied in clear text.
For added security, use the ENCRYPTED_FEDADMIN_PASSWORD setting.
Note: The Federation Manager administrator password can contain only English (ASCII) characters.
ENCRYPTED_FEDADMIN_PASSWORD
Displays the Federation Manager password in encrypted form. We recommend using this encrypted password for added security.
If you want the same administrator password on all systems, leave this password in place and do not uncomment the FEDADMIN_PW property.
FED_FIPS_VALUE
Specifies the FIPS 140-2 mode of operation.
Limits:
DEPLOYMENT_MODE
Specifies the Federation Manager deployment mode.
Limits:
Proxy (uppercase P)
Standalone (uppercase S).
SITEMINDER_CONNECTOR_ENABLE
Indicates whether the SiteMinder Connector is configured.
Limits: true (configured), false (not configured)
PROXY_HOST_NAME
(Proxy mode only) Identifies the fully qualified domain name of the backend server where Federation Manager forwards the requests for federated resources. Define this setting using the syntax server_name.domain:port.
Example: myserver.mycompany.ca.com:5555
If you use this properties file on more than one Federation Manager system and these systems use the same proxy, this host name should be set to the same value for each system. Note that Federation Manager and the proxy host must be in the same domain.
| Copyright © 2010 CA. All rights reserved. | Email CA about this topic |