previous
next
If the basic automated installation approach needs to be modified for your system, consider these variations:
Use this option if your UNIX platform (such as z/OS, Mac, HP-UX, non-SPARC Solaris, and other Linux systems) requires a version of a Java Runtime Environment (JRE) other than the one provided by the installer.
No JRE is installed with these installer files.
Look in your download location for an installer with nojre in the filename. For example:
Automated installer: mss-12.3.<nnn>-prod-unix-nojre.sh, where <nnn> is the build number.
Manual installer: mss-prod-unix-nojre-manual.tar.gz
Proceed with the installation, using your existing JRE.
If you use a servlet runner other than the default Tomcat servlet runner, such as IBM WebSphere, you must manually install the Management and Security Server components. For details, see Manual Installation.
Configure Management and Security Server as a web application, following the instructions provided by your servlet runner
If you are using SiteMinder, you may need to update the server's path reference to the SiteMinder native libraries.
In MSS/server/conf, inspect the property named wrapper.java.library.path.2 in the container.conf file. Verify that its value matches the path to the SiteMinder native libraries on your system. For example:
wrapper.java.library.path.2=C:/Program Files/CA/webagent/win64
If a change to this property is required, you must restart the server for those changes to take effect.
You can also run the installation tool in console mode for non-Windows systems. Console mode enables you to use a command line for input and output rather than a graphical user interface (such as X Windows).
All screens present their information on the console and allow you to enter the same information as in the automated installer. This option is useful if you want to run the automated installer on a headless or remote server.
To use Console Mode: Run the automated installer executable for your platform with a -c parameter.
You can also run the Initial Configuration Utility and the Configuration Upgrade Utility in console mode.
Management and Security Server installation is based on install4j technology, which supports unattended mode. Unattended installation enables you to install the product the same way on a series of computers.
NOTE:The Configuration Utilities do not support an unattended mode. These utilities run with a graphical user interface (or in an attended console mode). For more information, see Appendix A. Configuration Utilities, which are optional for many upgrade scenarios.
To use Unattended Installation:
Install Management and Security Server on a machine using the automated installer. You can use the graphical interface or console mode (-c) to install the product.
The installation process creates a text file, response.varfile, that contains the selected installation options. The file is located in [MssServerInstall]\.install4j\response.varfile
Copy response.varfile to another machine where you would like to install Management and Security Server.
Locate the appropriate executable (listed in Step 1: Run the automated installer) to install the product. Launch the installation program using the -q argument and a -varfile argument that specifies the location of response.varfile.
For example, to install Management and Security Server on a 64-bit Linux platform with a response.varfile located in the same directory, use this command, where <12.3.nnn> is the product version and build number:
mss-<12.3.nnn>-prod-linuxx64.sh –q –varfile response.varfile
You could also add the –c option to install in console mode, which would provide feedback such as "Extracting Files" and "Finishing Installation."
If you are unable to use an automated installer, you can use multi-component installation files to manually install Management and Security Server. See the Manual Installation section.