Hi Peter,
Welcome to the community from a fellow Scandinavian!
If using the Java API are you then sure you need the extra :<some looooong number> @ <windchill-domain-name> part of the long form?
... So I'm curious what your use case is for needing the long form?
The reason I'm asking is that as far as I have seen (and can remember) that part of the obid is the same for all Info*Engine responses you receive for a given Windchill installation. Another experience I have is that for some I*E requests where I had to give an obid as parameter I even had to cut that part off to get Windchill to understand my request.
Unfortunately I have no documentation to back up these observations of mine. If your use case requires you to supply the long form I guess you could always make one I*E request to get it and then add it with manually pasting the Strings together if that is not too hackish for you ;-). That way you could replace lots of I*E calls with one I*E call followed by lots of Java API calls.
I have one data point though, which I just dug up on a hunch triggered by your post. In at least one of my systems it seems that <some looooong number> matches the guid and <windchill-domain-name> matches lastKnownDomain in row with displayName = Windchill in the REPOSITORY table of the database. This *might* back up the fact that this is static for a given Windchill instance. If it's available through some sort of API I do not know.
Cheers (or Skål),
Jørn