We're currently have a DMP web application deployed as a help system for an application. We're looking to enhance this by making it context sensitive. Does anyone have experience with implementing this? The documentation on the DMP JavaAPIstates "A file-name-to-ID mapping file named idmap.properties is generated during the publishing process."
I'm looking for this mapping file so I can identify the file id to call from the display method, but I can't find this mapping file. Does anyone know where it is or how I generate it? I can't find it in the WAR file the PE produces.
Thanks guys. I've tried composing a DMP Help System, DMP Image (DMP and Input Image),and DMP Web Application.None of them produce this file (that I can find). I might have to go directly to PTC to find and answer on this one. I'll report back anything I find.
I have noticed in working with DMP that the amount of information on it is considerably less than other Arbortext components; which made it kind of a bear for us to set up as a web app. I'm hoping we start seeing better information about all of its features.
In Reply to Paul Nagai:
I agree that there may be some ways to link into a DMP Consumer web
application and via map file info but haven't done it and don't know anyone
who has. Please post what you find.
Thanks for the reminder, Paul. Here is the official response from PTC:
I could not find anything other than the Arbortext Help topic you mentioned. A developer reviewed source code and found no mention of idmap.properties. As a result, we conclude this is an obsolete feature and has been worked out of the code.
The Editor communicates with Help Center via java rpc. See APTPATH/packages/tools/_helpcenter.acl for examples of how the Editor does context sensitive help via the dmphelp() ACL function. The topic IDs are compiled into the Editor binary via a build process that extracts some IDs from the documentation source.
For our own Help Center, we use the resourceid tag in the DITA topic prolog tag to hold a unique identifier for the topic. During the publishing process, the resourceid value is taken from the DITA source and put into a META tag in the head of the HTML topic. The META value is what the software looks for to find the right topic.
So that explains why I couldn't find idmap.properties and gives some insight on how we're supposed to call specific topics and how PTC does it for their help.
The push we had to do this fizzled out so we never ended up testing it out. If anyone has had any experience with it, I'd love to hear about what they did.