Hi Mark,
First up all thanks for your reply and sorry for posting too many question. I am a newbie in this and I dont have much idea abt SPS. Forgive my ignorance.
I went through the product document and I noted down the folllowing points. Can you please correct me if I am wrong in any of these steps.
1. Backup the existing SPS install(using zip).
2. Run the installation program to upgrade from a previous version of SPS to the current version.
Right-click the executable and select Run as administrator.
Double-click ca-proxy-<version>-<operating_system>.exe.
Select OK to upgrade SPS version.
3. Follow the instructions from the installation wizard.
4. Restart the system after the installation completes.
5. Verify that the SSL configuration paths inside the ssl.conf file and the server.conf file are correct for our environment.
6. Modify the path to the proxy rules DTD file in the proxyrules.xml file.
7. Check the InstallLog file to verify that SPS installation is successful. By default, the InstallLog is installed in the following location on all platforms:
sps_home\install_config_info\CA_SiteMinder_Secure_Proxy_Server_InstallLog.log
8. To duplicate custom settings
Modify the httpd.conf file.
Modify the sps_home\httpd\conf\extra\httpd-ssl.conf file.
Modify the server.conf file.
9. Copy the existing custom session schemes and filter class files to the new installation.//***Where exactly I can find these files?
10. Deploy any custom Java class or .jar files related to the SPS filter or session scheme APIs. //** I am not sure whether any are available in our environment or not. How can I check?
11. You can customize Java Virtual Machine (JVM) parameters in the following files:
modify the SmSpsProxyEngine.properties file located in the directory sps_home\proxy-engine\conf.//** What is the use for this? What is the scenario I need to do this.
12. After you install SPS, run the configuration wizard. The configuration wizard lets you register the trusted host for the embedded SiteMinder Web Agent and performs some administrative tasks for the embedded Apache web server. (//Since smhost.conf file is already present, we can skip the option to register the trusted host. Is my understanding correct?)
According to product document we need to gather the following information before starting upgrade.
SiteMinder administrator name:
SiteMinder administrator password:
Trusted host name: (We can get this info from smhost.conf file)
Host Configuration Object: (We can get this info from smhost.conf file)
Agent Configuration Object: (We can get this info from WebAgent.conf file)
IP address of the Policy Server where the host is registered : (We can get this info from smhost.conf file)
Host Configuration File name and location : Location of smhost.conf file.
Name and location of the Web Agent configuration file: Location of WebAgent.conf file.
Fully qualified host name of the server: You can find this info in server.conf file
13. Follow these steps for upgradation:
Open a console window and navigate to the directory sps_home/secure-proxy.
Enter the following command: ca-sps-config.exe
Enter the details we gathered for upgradation in the configuration wizard.
Review the Configuration Summary
Click Install.
SPS is configured and the configuration files are installed.
Click Done to exit the wizard.
14. We can find the existing SPS configuration for our environment in following configuration files. Its recommendable to run a diff utility(to compare two files) such as windiff over config files such as httpd and make necessary changes in the new config files.
httpd.conf
Contains the settings for the Apache web server.
server.conf
Contains the settings that determine SPS behavior, including virtual hosts, and session scheme mapping.
logger.properties
Contains the settings that determine SPS logging behavior.
proxyrules.xml
Contains the rules that determine how SPS handles incoming requests.
Thanks in advance.
Regards,
Naveen