1) Compilation
I usually compile on the policy server, and point the javac to the one that the policy server is running.
But usually using future version of javac, it is compatable.
2) Debugging classpath JVMOptions.txt
It is easiest to use option 2: from here : run smpolicysrv from the command line :
Helping to debug SSO Policy Server java processes - redirecting stdout/stderr to timestamped file.
that way you see all the normal java stdout logs.
Then add -verbose to JVMOptions.txt and it will show you which .jar files it loads classes from.
Then you will also get full stacktrace as per normal java failure as well - and that helps isolate the cause.
For classnotfound exceptio : 'java.lang.ClassNotFoundException: com.netegrity.sdk.javaazapi.DTChangePasswordResponse
usually it will be something simple and the .jar file is not in the classpath correctly. Maybe .jar file created with wrong version of java, so not readable or can be some dependant class is not found - something like that.
That should help you progress.
Cheers - Mark