Previous Topic: Secure Proxy Server Pre-Installation StepsNext Topic: Proxy UI for the Secure Proxy Server


Configure the Secure Proxy Server Properties File

Set the parameters for the Secure Proxy Server installation.

You need the following information to complete the CSP console parameters.

General Information:
From the SiteMinder Policy Server properties file:

Follow these steps:

  1. Navigate to /tmp/properties.sh.
  2. In the properties.sh file, set the following parameters.
    _Environment

    Leave as the default, VMWare.

    _policy_server_hostname

    Enter the host name for the first SiteMinder Policy Server you installed.

    _im_hostname

    Enter the host name of the system where you plan to install the first Identity Management Server.

    _jcs_hostname

    Enter the host name for the first CA IAM Connector Server you installed.

    policy_server_password

    Password for the default SiteMinder Policy Server user. Enter the same password you entered for _ps_admin_password in the properties file for the Policy Server.

    _DomainSuffix

    Enter the domain name for your installation, for example, forwardinc.com

    JAVA64_LOCATION

    Location of an existing 64-bit JRE if preinstalled. Set this parameter if you choose to install your JRE separately. In this case, symbolically link /opt/java64 to your JRE.

    However, instead of installing a JRE separately, the system installer can do this automatically. We recommend that you download a JRE and allow the system to install it.

    See the JAVA64_KIT parameter.

    JAVA64_KIT

    Location of a 64-bit JRE that you download to the local system or to a file share. If this parameter is set, the server kit will install this JRE automatically.

    USER_JAVA64

    Leave blank for installation. This parameter is intended for upgrades, not installation.

    JAVA32_LOCATION

    Location of an existing 32-bit JRE if preinstalled. Set this parameter if you choose to install your JRE separately. In this case, symbolically link /opt/java32 to your JRE.

    However, instead of installing a JRE separately, the system installer can do this automatically. We recommend that you download a JRE and allow the system to install it.

    See the JAVA32_KIT parameter.

    JAVA32_KIT

    Location of a 32-bit JRE that you download to the local system or to a file share. If this parameter is set, the server kit will install this JRE automatically.

    USER_JAVA32

    Leave blank for installation. This parameter is intended for upgrades, not installation.

    _ntp_server

    Required. IP address or host name of the NTP user to use to synchronize the server time.

    SSL_ENABLE

    Required. Set to yes to run the Secure Proxy Server in SSL mode.

    CERT_SPS

    Enter the path to your Secure Proxy Server certificate file. Leave this value blank if you want the installer to create a self-signed certificate.

    Note: A production installation should not use a self-signed certificate.

    An example for an existing certificate file could be:

    /opt/mycerts/MySPS.crt

    KEY_SPS

    Enter the path to your Secure Proxy Server key file. Leave this value blank if you want the installer to create a key.

    _cert_passwd

    The password of the Secure Proxy Server self-signed certificate that the install will generate. Create any password.

    The value is required only if you want the installer to create a self-signed certificate. If your certificate already exists, leave this value blank.

    SSL_SUBJECT

    The subject of the certificate that the install will generate. The value is required only if you want the installer to create a self-signed certificate. The following shows an example format:

    /C=IN/ST=AP/L=HYD/CN=XYZ

    Where C = country name, ST = state, L = City, and CN = common name

  3. Back up the properties.sh file. Rename it to a logical name, for example, secureproxyserver1properties.sh.

    Note: This file is critical for upgrades. We recommend that you back up this file. This file contains passwords, so be sure to save it in a secure location.

    Important! The original properties.sh file resides in a temp folder. If the server is shut down, the properties.sh file is discarded. Therefore, rename and back up this file before proceeding with any further installation or use of the system.