You should never run any third party apps on a call manager, regardless of whether you can or not. Perhaps you've had to fix a cisco server before when a client thought "hey I know windows, so let's reconfigure a bunch of stuff".. while that can work, you really should adopt a hands off attitude towards those servers. While I don't quite understand how software can be written that doesn't run on a regular system (and it does after all.. I have ccm, crs and cuc running on standard servers and it works fine and no amount of patching ever introduced a problem), I'd just stick to reminding Cisco every now and then that it's not hard to write a normal app but leave your call manager alone.
If you read the developer documentation, it clearly states you shouldn't install any phone apps on the call manager. The appliance model just enforces the hands-off policy.
Keep in mind that phone apps generally don't use a lot of resources, so if you have another regular server, you can just install your apps there... I usually have my application webserver co-located on another already existing box.. if you're a Windows show, you'll probably have a few machines with a running IIS anyway.
I guess you're in need for a lookup app then. Now it depends what kind of data source you're trying to access. If it's ldap, just take the ccm4 directory, put it on an external server, and make the required changes to reflect your ldap data source. But even if it's not ldap, you could take the directory from ccm 4.x as a starting point and just swap out the lookup for some sql routines (or calls to a webservice, or whatnot).
Or, you could take the ldap routines in the SDK and the jsp photodirectory as a basis for your own jsp app.
Or, you could try and open a case and get temporary root access to your ccm 5.x, then copy the files and if you're lucky and it's all done in JSP and / or done in a way that allows you to still use their lookup routines, you could take this as a starting point.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.