Scripting and Programming Guides › Developer's Guide for Java › Agent API › Pure Java Agent API Usage
Pure Java Agent API Usage
Backward compatibility
The pure Java Agent API maintains binary and source compatibility with the JNI Java Agent API. The pure Java Agent API supports all of the other SiteMinder Java SDK interfaces that rely on the Agent API for connectivity to the SiteMinder Policy Server, including the SiteMinder Policy Management API and the SiteMinder DMS API, in addition to extending the portability of those interfaces.
Configuration limitations
The pure Java Agent API does not change the configuration of either the SiteMinder Application Server Agents or any agents developed with the SiteMinder SDK. The configuration of the pure Java Agent API is identical to the configuration of the JNI Java Agent API with the following exceptions:
- Migration of UNIX agents from the JNI Java Agent API to the pure Java Agent API requires re-registration of the trusted host entity with the SiteMinder Policy Server because the shared secret in the JNI Java API is computed differently from the pure Java implementation.
- On both Unix and Windows systems (due to file-locking incompatibilities with the native code Agent API), the SmHost.conf file cannot be shared between agents using the C/C++ or JNI Java Agent API and agents using the pure Java Agent API. Therefore, a separate copy of the bootstrap configuration file must be kept for pure Java Agent API agents.
- To register a host for a 5.x-type custom pure Java Agent you must use smreghost.bat (or smreghost.sh on UNIX), not smreghost.exe.
- Upgrades from the JNI Java Agent API on Unix systems requires users of custom 4.x-based agents that use shared secrets encrypted with the 4.x encryptkey tool to update their shared secret on the agent side for upgraded agents.
