Incorrect time in logs of Content Collector for SAP after changing of timezone

In our Filenet ECM system we use Content Collector for SAP.
After changing time in October 2014 (in our case - Russia, Moscow, UTC+3) we patched all of Java jre in our environments using IBM jtzu patch. After that WAS shows correct time in the logs but Content Collector - does not. In spite of update it shows old time (UTC+4).
What to do?

IBM BPM: java.lang.OutOfMemoryError: PermGen space during bootstrapProcessServerData

During bootstrapProcessServerData step in IBM BPM installation you can get the message:

java.lang.OutOfMemoryError: PermGen space

I got it on Solaris SPARC.

2014. Moscow goes back to winter

Not having found a more smart targets, we decided to return the Winter Time. So in the night of 25/26.10 Moscow will set time upon hour ago.

It is very joyful news for any Russian sysadmins which always waiting for a possibility to work in the weekends. It is the sarcasm.

My quick way for WAS admins and others.