Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

livelink xmlimport problem

Status
Not open for further replies.

nino232323

Programmer
Dec 12, 2011
6
hi,
i'm new of this world.

my problem is this one.

i used XMLExport for create a new xml file from a category.

then i used XMLImport for create it in my other livelink server. and it works(it create category and attributes).
when my friend used the same file with the same XMLImport URL in another livelink server different from mine, it works but it create only the category envelope without attributes.
why these differences with the same procedure and xml-file?
what could be the difference
 
obviously the code base of your friends livelink may be different.One would put logs on your friends to analyze what is different.

A simple e.g to illustrate that.Create a catgory(131) subtype is all the same for all livelinks.however if your category attribute type is a ADN or TableKeyLookup type,it works in your instance by having the ADN module or AttributeExtensionsModule.Assume your friends livelink does not have these two optional modules.It will try to add those but does not find the code to do it....


That is why it will be different across livelinsk as livelink code can greatly differ by having more modules isn them

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010
 
the livelink installations are the same because we installed them simultanly on 2 machines, and we haven't these modules.
 
on a third machine it works too, only on one doesn't work
 
run logs on the machine that does not work.On the machine it does not work you may want to put these things into the opentext.ini

DEBUG=2

wantLogs=True

re-start and re-attempt and send logs to OT or look in them for abvious stuff.If a trace<threadnumber>.out happens then a livelink thread has crashed equivalent to unhandled exceptions.that is how in livelink you figure out problems.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top