Archive for September, 2011

UDK Games for iOS Mobile Platform

While ioQuake3 is still very cool, in a mostly nostalgic kind of way, I've decided after careful deliberation to go 'all in' with UDK.  Those who've been using the engine for years will no doubt chuckle over my belated 'revelation'.  Nevertheless, and for reasons not unique to many others modders, I've finally decided to let go of the past and move on to the bigger and better.  To chalk up my previous failures and successes to experience, and to rejoin my modding brethren in the modern era.  Nuff' said.


Now, the part of UDK Modding that has me most excited is the iOS Mobile Platform support!
Mobile anything is the future. We all know it. And honestly, even if UDK wasn't a fantastic NextGen engine to develop in (which it is), the fact that the engine is updated monthly with such awesome features as iOS Mobile support makes the choice crystal clear. Seeing no evidence to say otherwise, I foresee Epic Games continuing to support Mobile Platform Gaming, indefinitely.

Check this out…


UDK's highly optimized mobile renderer has support for per-pixel lighting, environment mapping, precomputed visibility and more! And of course, Unreal Lightmass computes stunning light and shadows to bring your scene to life. Harness the power of the same triple-A tools used to build ground-breaking games like Gears of War and iPhone Game of the Year Infinity Blade.

Honestly, gaming on mobile devices is sneered upon by many… even yours truly at times (ironically). But to not understand the exponentially growing Mobile trend out there, nor to fathom any possibility of overcoming such handheld device limitations, betrays a serious lack of creativity. Sign me up Epic! I'm all in…

Debugging .hprof files using the Memory Analyzer Tool

If a SiteScope GUI becomes completely blank, or is otherwise unavailable, one of the culprits may be a lack of available disk space – on account of SiteScope creating a number of large JVM debugging files (.hprof files).  Over 35GB’s worth is not out of the question, and this can clearly tank an application as a result.  Essentially, these files are memory dumps that indicate a problem with the application configuration.

To open and parse these files, use the Eclipse Memory Analyzer Tool (MAT).
Download the zip file and extract its contents into the same SiteScope directory where javaw.exe lives:  C:\SiteScope\java\bin

From here on you are on your own, but the basic gist of it goes like this:

  • Open the MAT .exe file, which is located in the same directory you extracted the zip into.
  • Import/Open the SiteScope .hprof files, which are located in SiteScope bin folder: C:\SiteScope\bin
  • …And run all of the canned analysis reports against the .hprof files as you wish

Unless you are a Java Developer, the memory analyzer will not be terribly useful to you.
However, MAT will automatically zip up every Report you generate – which is a perfect format to forward to HP Support, along with the raw .hprof files themselves.  The zipped Reports should end up in the SiteScope\Bin directory after being created.

As a final note, the MAT *should* work against any other HP BTO product that produces .hprof files, such as BSM, however I have not tested this and would only do so after performing a full file system/db backup.


Using the JMX console to reassign services between Data Processors

1) In a Web browser, open: http:// :8080/jmx-console
When prompted, enter the JMX Console authentication credentials (if you do not have these credentials, contact your BSM Administrator).

2) In the Topaz section, select service=hac-backup.

3) Invoke listServers()to display the hostname of your src/dst servers. Note these.

4) Return to the previous MBean, locate moveServices() and enter the following values:
– customerId. The default customer ID for a regular HP Business Service Management installation is 1.
– srcServer. The name of the source server from where you are moving services.
– dstServer. The name of the destination server to where you are moving the services.
– groupName. Leave this parameter value blank.

5) Click Invoke. All services running on the source server are moved to the destination server.

Return top