Friday, November 20, 2015

Nifty, time saving tricks in Sametime config - Policy debug

Updating a policy in the Sametime System Console can be time consuming. I mean, changing the policy itself is quick, but waiting for the policy to be picked up by the Community server can take some time. I believe that the Media Manager policy is set to be spread out every 60 minutes?!

One way I learned that can spead up this process, is by manually stopping the Windows service called "ST Policy" on the Community server!!

Stopping this, and starting it again gives the Community Server a new and updated "policies.user.xml" and "policies.server.xml" file.




Try it your selv. Nifty.

And this also works if you want to debug the policies on the Community Server:

Editing the sametime.ini file, adding "POLICY_DEBUG_LEVEL=5" into the "Debug" section, and then restarting the "ST Policy" Windows service, gives you the trace files immediatly, without restarting the entire Domino server.
(Do remember to set the "POLICY_DEBUG_LEVEL" back to 1 when you´re done. Or else your disk will get filled up)


5 comments:

Carl Tyler said...

Another option is the stdebugtool

http://www-01.ibm.com/support/knowledgecenter/SSKTXQ_8.5.0/com.ibm.help.sametime.v85.doc/trouble/st_adm_security_runstdebug_t.html

Robert Farstad said...

Yeah, I tried that, but I couldn't the trace file output created after I set the trace setting in the stdebug tool. Weird.

Robert Farstad said...

If anyone knows how to restart the "ST Policy" in a Linux environment, please share.

Jared Wallace said...

Robert - use:

> pgrep stpolicy
3840 (or whatever process id)
> kill -HUP 3840

Robert Farstad said...

Ok? The -HUP parameters will restart the stpolicy process?