My blog is yet again up and running after about two days of downtime. The issue has been related to my ISP having moved my domain to another server. This caused http://hellem.org to reply with another ip than http://www.hellem.org. In addition the database server had been moved so I had to update the configuration files to the blog.
But, now back again!
Needed to know how much disk space all *.ear-files was consuming in a directory on one of our Linux-servers
Then I used Google to make the number human readable, https://www.google.no/search?q=9606676582+bytes+to+gb
Ever been in the situation where you log on to a server as one user having X11 enabled, but then need to sudo to another one - and voila, your X11-sesison is long gone...
Solution provided here http://brandonhutchinson.com/wiki/X11_Forwarding_and_su/sudo
I did as root
and it all worked fine.
Navigate to Administration -> General Configuration -> Advanced
Needed to verify a lot of ports that should be opened making it possible to connect to three hosts. Had to do some surfing, and as always by the help of Google I managed to create a bash-script solving the issue for me.
...the difference between containment paths, configuration IDs and object names in WebSphere?s scripting interface wsadmin...
All very well explained in this blog post blog.xebia.com/../websphere-scripting-with-wsadmin-containment-paths-configuration-ids-and-object-names
Created this SQL-statement used for one of our JIRA-instances. Needed to get rid of a lot of open sub-tasks where the parent task had been cancelled. The statement also shows usage of inner join and self-join.
My blog has been unavailable for more than 48 hours due to the host server having had some DNS-issues. A call to my hosting company http://www.onnet.no/ and voila, fixed in a few minutes.
With Rational Application Developer installed you will find the needed file at
where the star indicates the version of UTC. There you will then find the IBMUTC.ear file which you then can install on your instance of WebSphere Application Server (or Tomcat or whatever application server).
Application will then be available at http://yourhost:yourport/UTC/