If you have lost the "wasadmin" account password or any other local WebSphere account, there is a rather simple way to recover it. Just connect to the server where WebSphere Deployment Manager is running, via RDP or SSH, depending on the OS of the server, and open the "security.xml" file located under "<WebSphere_Installation_Directory>/AppServer/profiles/<Deployment_Manager_Profile>/config/cells/<Cell_Name>" for example…

Supose you want to use the userpictures from Connections, but don’t want to use the FileViewer from Connections. There is no documentation, for sofar i could see, about this subject. So i opened a case for it and they came with this perfectly working solution.

Your TDI solution directory contains a couple of files which all start with employee. These files tell you which records were added, updated, deleted, skipped or produced an error. The last file is usually the most interesting one. Often employee records give an error because a user was deleted at an earlier stage and recreated with a different GUID. Sometimes users are created with the same login ID as a previous user, which was long deleted and there are more relatively obvious reasons like that why an employee record would create an error. However, sometimes you are just completely in the dark of why a record gives an error. That’s when this little tip helps you to determine the problem.

I am currently sitting in my hotel room near Amsterdam Schipol airport. I missed my flight in the morning because the Dutch train canceled several connections and the train I was in finally also had delays due to technical issues on the track. Another delay resulted in the need to change the train at Amsterdam Central. Anyway, I didn't make it in time, I was about 1 hour late. But why I am here?

Although Day 1 was long, the start of Day 2, which was already at 8 am, did not allow much rest. The composition of the program did not allow a thorough tour of the zoo, but Burgers’ Ocean really surprised me.