- Exit all applications that are running.
After installation, you can find the installation log files in siteminder_home/install_config_info. The file names are:
- Download the Policy Server installation kit from the Technical Support site and save one of the following installation executables to a temporary location:
- nete-ps-6.0-sp6-sol.bin
- nete-ps-6.0-sp6-rhel30.bin.
- nete-ps-6.0-sp6-hp.bin.
Depending on your permissions, you may need to add executable permissions to the install file by running the following command:
chmod +x nete-ps-6.0-sp6-os.bin
Important! The Policy Server installer can crash when executed across different subnets. Install the Policy Server directly on the host system to prevent this problem.
- Open a command window, navigate to the installation executable, and enter:
sh ./nete-ps-6.0-sp6-os.bin
- os
-
Specifies sol, rhel30, or hp.
Setup verifies the following prerequisites:
- You are logged into an account with local administrator privileges.
- You have the appropriate operating system and web server listed on the SiteMinder Platform Support Matrix. To access this matrix, go to the Technical Support site and search for the SiteMinder Platform Support Matrix.
- The computer has necessary free disk space and the required JDK or JRE versions installed. For the required versions, search for the SiteMinder Platform Support Matrix on the Technical Support site.
- In the first Introduction dialog, be sure that the system has the prerequisites listed and click Next. If not, stop the installation and install the required prerequisites.
Note: The installer runs smpatchcheck to confirm that you have the required/recommended patches installed on the operating system. For a list of these patches, see the Policy Server Release Notes.
- (Optional) If the installer cannot locate the JRE, it prompts you for the location. Enter the appropriate location.
- Read the Software License Agreement, accept the terms if you agree, and click Next.
- Read the Release Notes, then click Next.
- Enter your name and company name and click Next.
- Accept the default Policy Server installation location or select a different one and click Next. If necessary, click Choose to browse to the appropriate location.
Note: If you cut and paste a path, the Next button is disabled. Type a character to enable the Next button.
- Enter the full path to the web browser on this system, including the executable, and click Next.
Note: The installer uses this information to make the SiteMinder documentation available from Policy Server User Interface.
- Select Yes or No to add the smprofile.ksh to the .profile file and click Next.
- In the Encryption Key dialog, complete the following:
- Enter a case–sensitive, alphanumeric encryption key. The encryption key is a key that secures data sent between the Policy Server and the policy store. The key can be from 6 to 24 characters in length. All policy servers that share a SiteMinder policy store must be configured using the same encryption key. For stronger protection, define a long encryption key.
- Re–enter the key to confirm the entry.
- Take note of this key for future reference and click Next.
- In the Choose Features dialog, select which Policy Server features you want and click Next.
- OneView Monitor GUI
-
The install program configures the OneView Monitor GUI to work on the web server you specify later in this procedure.
Note: To use the OneView Monitor, you must have the required version of Java SDK and ServletExec/AS installed. For the required versions, search for the SiteMinder Platform Matrix for 6.0 on the Technical Support site.
- Web Server(s)
-
The install program configures the Policy Server User Interface and, if selected, the OneView Monitor to work on this web server.
- SNMP
-
The install program configures SNMP to work with the Policy Server.
Note: The password of the root user and a native SunSolstice Master Agent are required to enable SNMP support.
- Policy Store
-
The install program configures an LDAP directory server as a policy store.
Additional Considerations
- You are installing the Policy Server using the smuser UNIX account. Do not configure the Sun Java System or Apache on Linux web server for the Policy Server User Interface or the OneView Monitor GUI. The installer modifies the web server configuration files and smuser does not have the appropriate root privileges. After the Policy Server installation is complete, run the Policy Server Configuration Wizard, which is located in siteminder_home/install_config_info/nete-ps-config.bin, as root to configure the Policy Server User Interface or the OneView Monitor GUI.
- The installer can automatically configure an LDAP directory server as a policy store. You can automatically configure the policy store in an instance of Sun Java System Directory Server Enterprise Edition (formerly Sun ONE/iPlanet), ADAM, or AD LDS. For other supported LDAP or relational database vendors, you configure the policy store manually after installing the Policy Server.
Note: If there is a problem with configuring the policy store, you can run the Policy Server Configuration Wizard, which is located in siteminder_home/install_config_info/nete-ps-config.bin, to fix the issue.
- (Optional) If you specified that the installer configure the OneView Monitor GUI, specify the following ServletExec information:
- Enter the ServletExec installation directory.
Example: /usr/local/NewAtlanta/ServletExecAS
- Enter the port number for the ServletExec instance.
- (Optional) If you have multiple ServletExec instances, select the se-hostname-server you want to configure for the OneView Monitor GUI
- Click Next.
- Enter the path to the root folder of a supported web server and click Next.
- Select the web server you want to configure with the Policy Server and click Next.
Note: Consider the following:
- Be sure that the web server instance is stopped.
- If you have multiple web servers, only select one. We recommend configuring one web server at a time. Use the Policy Server Configuration Wizard to configure additional web servers after installing the Policy Server. See Configure Additional Web Server Instances for the Policy Server for more information.
- If you are installing the Policy Server before the documentation, you are prompted to run the Policy Server Configuration Wizard to create the netegrity_docs virtual directory on the web server. This virtual directory lets you view the documentation using the Policy Server User Interface.
- In the first Policy Store dialog, select whether you want to configure a new policy store or update an existing one.
- In the second Policy Store dialog for the LDAP Server, click Next, and configure ADAM, AD LDS, or Sun Java System Directory Server Enterprise Edition (formerly Sun ONE/iPlanet) as a policy store.
Note: For other supported LDAP or relational database vendors, configure the policy store manually after installing the Policy Server.