Installation and Upgrade Guides › Policy Server Installation Guide › Unattended Installation › How to Run an Unattended Administrative UI Install

How to Run an Unattended Administrative UI Install

To run an unattended Administrative UI install, complete the following procedures:

1. If you are:
   • Using the prerequisite installer, review the installation checklist.
   • Installing to an existing application server infrastructure, review the installation checklist.
2. Review the guidelines for silent installation.
3. Determine which properties file to use.

   Note: The Administrative UI installation option determines the properties file that you use.

4. From an Administrative UI host system, complete the following steps:
   1. Copy the properties file. If you are:
      • Reinstalling the Administrative UI, copy this file to a temporary location.
      • Installing the Administrative UI to a new system, copy this file to a temporary location on that system.
   2. If you are using the prerequisite installer, navigate to admin_ui_home\SiteMinder\adminui and review the JBoss license agreement (JBoss-ORG-ULA.txt). The prerequisite installer properties file includes a Lesser General Public License parameter. You update this parameter to verify that you have reviewed and agree to the JBoss license agreement.
5. Copy the installation media to the same location to which you copied the properties file.

   Note: The Administrative UI installation option determines the executable that you use.

6. Modify the properties file.
7. Run the Administrative UI installer.
8. Register the Administrative UI with a Policy Server.

Modify the Prerequisite Installer Properties File

If you are using the stand-alone option to install the Administrative UI, modify the prerequisite installer properties file to define installation variables. The default values reflect the information entered during the last Administrative UI installation.

More information:

Administrative UI Properties Files

General Information

This section lets you specify the root folder of the Administrative UI installation:

DEFAULT_INSTALL_FOLDER

Specifies the root folder under which all sub-folders are created during the installation.

Server Information

This section lets you specify information about JBoss and the Administrative UI host system. This section contains the following parameters:

DEFAULT_APP_SERVER_PORT

Specifies the port on which JBoss should listen for HTTP requests.

DEFAULT_APP_SERVER_HOST

Specifies the fully qualified name of the Administrative UI host system.

End User Licensing Agreement

The prerequisite installer installs JBoss, which requires you to accept a Lesser General Public License. This section lets you indicate that you have reviewed and accept the License Agreement.

To accept the license:

1. Be sure that you have reviewed the JBoss License Agreement (JBossORG-EULA.txt).

   The license is available on an Administrative UI host system in the following location:

   admin_ui_home\siteminder\adminui.

   admin_ui_home

   Specifies the Administrative UI installation path.

2. If you accept the License Agreement, change the value of ACCEPT_LGPL_EULA to the following:

   YES

   Specifies that you have reviewed and accept the License Agreement.

Modify the Administrative UI Installer Properties File

If you are installing the Administrative UI to an existing application server infrastructure, modify the Administrative UI installer properties file to define installation variables. The default values in this file reflect the information entered during the last Administrative UI installation.

More information:

Administrative UI Properties Files

General Information

This section lets you specify the root folder of the Administrative UI installation:

DEFAULT_INSTALL_FOLDER

Specifies the root folder under which all sub-folders are created during the installation.

Application Server Information

This section lets you specify information about the application server to which the Administrative UI is to be deployed. This section contains the following parameters:

DEFAULT_APP_SERVER

Specifies the application server type. This parameter uses the following settings:

JBoss

Specifies that the application server type is JBoss.

WebLogic9

Specifies that the application server type is WebLogic.

WebSphere6

Specifies that the application server type is WebSphere.

DEFAULT_NETE_JAVA_HOME

Specifies the path to the required JDK or JRE for the application server. This value depends on the type of application server:

JBoss

Specifies the path to the minimum version of the required JDK.

WebLogic

Specifies the path to the minimum version of the required JDK or JRE.

WebSphere

Specifies the path to the minimum version of the required JDK or JRE.

DEFAULT_APP_SERVER_URL

Specifies the fully qualified URL of the system on which the application server is installed.

JBoss Information

This section lets you specify additional information about JBoss.

Note: If you did not enter JBoss as the value of DEFAULT_APP_SERVER, a value is not required for this section.

This section has the following parameter:

DEFAULT_JBOSS_FOLDER

Specifies the path to the JBoss installation directory.

Note: The path cannot contain spaces.

WebLogic Information

This section lets you specify additional information about WebLogic.

Note: If you do not enter WebLogic9 as the value of DEFAULT_APP_SERVER, values are not required for this section.

This section has the following parameters:

DEFAULT_BINARY_FOLDER

Specifies the path to the WebLogic installation directory.

DEFAULT_DOMAIN_FOLDER

Specifies the path to the WebLogic domain you created for the Administrative UI.

DEFAULT_SERVER_NAME

Specifies the name of the WebLogic server on which the WebLogic domain is configured.

WebSphere Information

This section lets you specify additional information about WebSphere.

Note: If you do not enter WebSphere6 as the value of DEFAULT_APP_SERVER, values are not required for this section.

This section has the following parameters:

DEFAULT_WEBSPHERE_FOLDER

Specifies the path to the WebSphere installation directory.

DEFAULT_WAS_NODE

Specifies the name of the node in which the application server is located.

DEFAULT_WAS_SERVER

Specifies the name of the application server.

DEFAULT_WAS_CELL

Specifies the name of the cell in which the application server is located.

WAS_PROFILE

Specifies the name of the profile being used for the Administrative UI.

Run the Administrative UI Installer

You run an unattended installation to install the Administrative UI without user interaction.

Before You Install

Consider the following items before installing the Administrative UI:

• You install the Administrative UI using the installation media on the Technical Support site.

  Note: For a list of installation media names, see the Policy Server Release Notes.

• Important! The installation zip contains a layout.properties file and a Framework folder at the same level as the installation media. If you moved the installation media after extracting the installation zip, move the following to the same location or the installation fails:
  • layout.properties file
  • Framework folder
• The installation zip contains the prerequisite installer and the Administrative UI installer.

  If you are installing the Administrative UI using the prerequisite installer, place both executables are in the same location. The prerequisite installer automatically calls the Administrative UI installer to complete the installation.

More information:

Locate the Installation Media

Installation Media Names

Windows

To run an unattended Administrative UI install, run the following command from the directory to which you copied the Administrative UI installation media and the properties file:

installation_media -f properties_file -i silent

Important! Before running a CA SiteMinder® utility or executable on Windows Server 2008, open the command line window with administrator permissions. Open the command line window this way, even if your account has administrator privileges.

installation_media

Specifies the name of the Administrative UI installation executable. The Administrative UI installation option determines the executable that you use.

-f properties_file

Specifies the path to the properties file. The path must include the properties file name. The Administrative UI installation option determines the properties file that you use.

Note: Use double quotes if the argument contains spaces.

-i silent

Specifies that the installer run silently.

Example:

installation_media -f "C:Program Files\CA\SiteMinder\adminui\install_config_info\properties_file" -i silent

The installer uses the parameters in the properties file to install the Administrative UI.

You complete the installation by registering the Administrative UI with a Policy Server:

• If you installed the Administrative UI using the stand-alone option, see How to Register the Administrative UI.
• If you installed the Administrative UI to an existing application server infrastructure, see How to Register the Administrative UI.

UNIX

Follow these steps:

1. Open a shell
2. Run the following command from the directory to which you copied the Administrative UI installation media and the properties file:

   ./installation_media -f properties_file -i silent
   

   installation_media

   Specifies the name of the Administrative UI installation executable. The Administrative UI installation option determines the executable that you use.

   -f properties_file

   Specifies the path to the properties file. The path must include the properties file name. The Administrative UI installation option determines the properties file that you use.

   -i silent

   Specifies that the installer run silently.

   The installer uses the parameters in the properties file to install the Administrative UI.

3. Complete the installation by registering the Administrative UI with a Policy Server:
   • If you installed the Administrative UI using the stand-alone option, see How to Register the Administrative UI.
   • If you installed the Administrative UI to an existing application server infrastructure, see How to Register the Administrative UI.