How to run an Unattended Standalone Upgrade Installation of the Wamui (Windows and UNIX)
search cancel

How to run an Unattended Standalone Upgrade Installation of the Wamui (Windows and UNIX)

book

Article ID: 36167

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On

Issue/Introduction

 

Introduction/Summary: 

How to run an Unattended Standalone Upgrade Installation of the Wamui (Windows and UNIX) 

Background:  

 

After running the Prerequisite installer and the Administrative UI installer for and attended installation to create the required files for unattended installations

Environment:  

Windows 2008 r2  Windows 2012    Linux/Unix 

Instructions: 

Follow these steps: 

 

1. Determine which properties file to use based on what os you are using: 

?Windows: Only the prerequisite-installer.properties file. The prerequisite installer kicks off the Administrative UI installer. 

 

?UNIX/Linux The prerequisite-installer.properties and the smwamui-installer.properties 

 

On UNIX/Linux systems, the prerequisite installer does not automatically launch the Administrative UI installer. 

 

2. Navigate to the directory admin_ui_home\siteminder\adminui\install_config_info on the Administrative UI system where you ran the attended installation. 

 

3. Copy the properties file(s)   “smwamui-installer.properties” and “prerequisite-installer.properties”   from Install_Home\CA\siteminder\adminui\install_config_info\ from the Administrative UI host system to a temporary location on the new host system. 

Very important – After copying prerequisite-installer.properties, delete prerequisite-installer.properties and  smwamui-installer.properties  files from Install_Home\CA\siteminder\adminui\install_config_info

 

4. In the prerequisite-installer.properties file, verify that the ACCEPT_LGPL_EULA parameter is set to YES 

 

5.Go to the location where you extracted the installation zip file for the attended installation. Copy the following files to the same location where you copied the properties file(s):

 ?installation executable (prerequisite and UI) 

? layout.properties file 

For example copy the extracted file ca-adminui-12.52-sp1-cr02-win32.exe and layout.properties file to \sso_sofware\adminiui\smwamui-installer.properties  

 

In Windows.

 From the directory where you copied all the files, run the prerequisite installer by entering the following command: 

 prerequisite_installation_file -f “path of properties_file” -i silent 

 For  example \sso_software\adminui-pre-req-12.52-sp1-cr02-win32.exe -f " sso_software\adminui \prerequisite-installer.properties " -i silent 

 For Windows systems, the prerequisite installer automatically launches the Administrative UI installer 

______

In Unix/Linux.

For example copy the extracted file  adminui-pre-req-12.52-sp1-cr02-linux.bin  and layout.properties file to \sso_sofware\adminiui\smwamui-installer.properties  

From the directory where you copied all the files, run the prerequisite installer by entering the following command: 

For example    \sso_sofware\adminui-pre-req-12.52-sp1-cr02-linux.bin -f " sso_software\adminui \prerequisite-installer.properties " -i silent 

______________________

  

To start a Unix/Linux install  

Important -.(UNIX only): Run the Administrative UI installation by entering the following command. On UNIX systems, the prerequisite installer does not automatically launch the Administrative UI installer. 

Command - installation_file name -f “path of properties_file” -i silent 

 Full Command with path for example: is ca-adminui-12.52-sp1-cr02-linux.bin -f \sso_sofware\adminiui\smwamui-installer.properties" -i silent 

 

Above Command installation_file name -f “path of properties_file” -i silent  explained below

   Installation_file name specifies the name of the Administrative UI installation executable used to first install the UI. 

 -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. Use double quotes if the argument contains spaces. 

 -i silent specifies that the installer run silently. 

 - Register the Administrative UI with a Policy Server. Refer to the Administrative UI installation instructions for registration procedures. 

Environment

Release:
Component: SMSSO