Generally, you must only edit the smagent.properties file to change SiteMinder Agent logging options or if you change the names or locations of your configured Agent configuration files. For example, if you are using a shared Agent configuration file.
In clustered and SSO WebSphere environments, the smagent.properties file is replicated on many systems. However, the SiteMinder Agent migh not be installed in the same file system location. The Agent configuration file locations specified in smagent.properties might not therefore be correct for all systems in such an environment.
To handle this situation, you can define a JVM system property, smasa.home, which defines the installed location of the SiteMinder Agent on the local host and then edit smagent.properties to remove absolute paths to the Agent configuration files. Where the absolute path is absent, the SiteMinder Agent uses the value of smasa.home to determine where to find the configuration files.
For example, change the first line to resemble the second line:
smazconf="c:\smwasasa\conf\AsaAgent-az.conf"
smazconf="AsaAgent-az.conf"
To set the smasa.home JVM system property (on each WebSphere server in the cluster or SSO environment)
Servers, Application Server, server1, Java and Process Management, Process Definition, Java virtual machine, Additional Properties, Custom Properties.
smasa.home=C:\smwasasa
Copyright © 2010 CA. All rights reserved. | Email CA Technologies about this topic |