Using SearchService in Livelink to retrive OTLocation resulting in <>location</>

[pradeepdsp]

Hi All,

I am facing a bizarre scenario, where we have integrated livelink with our Application using Java. We are using search service to retrive
data from livelink server, I am getting OTLocation value within <></> and - inbetween LocationId in customer environment, but in local i am unable to simulate. When is <> displayed in OTLocation, <> is not displayed for all Records.

Thanks in Advance...

 

[appnair]

Easy Stuff first,

Check whether in your system if OTLOCATION is Displayable or not.If it is just for kicks turn it off re-start ,turn it on again and re-start it is not any server re-start but using the search admin browser stuff in your SOV. the thing you are looking for is "Regions" in your search system.

Some tips .I never rely on searchservice or lapi for search because I know that search is already an api and can best be tested perfectly well using a ?func=search it is explained in this link

http://www.tek-tips.com/faqs.cfm?fid=3552.The

biggest things going for lapi search and searchservice search is you do not have to code the authentication part.OT says not to use either of the older methods but to use ?func=search
Now search requires a little bit of system administration knowledge on the livelink side like its architecture ,region settings etc.
So in your working system I would do a simple search on the place you want to search and output search as xml and see if OTLOCATION is actually coming in the results always using a privileged account with SA privs to see if you are getting thrown off by permissions.Now you would do the same on your non working server and compare and try to see if settings on your working server mirror the non working server.You can put search logs and even compare the LQL that it receives in the two systems and see if they make sense.
From what I know OTLOCATION is a manufactured region not available in any tables E.Also the intention of that is to show where one would find a document so if we assume the simplest case
Enterprise(2000):My Folder(12345):My Very Secret Folder(345678) when a SA searches the OTLOCATION will try to show you the breadcrumb trail
If My Very Secret Folder(345678) is opened to a group called "My Secret Group" and the user "appu" is part of that Group and say "appu" does not have System admin privs nor is anyway being able to see the previous ones when "appu" searches this livelink he will see "My Very Secret Folder" in a weird way .It will look like hanging at a top level.The documents inside will make sense if that guy is permitted on it.The fact is that livelink is going to obey the ACL as you set it up so usually people will spend some time to design the system properly.You will hear these things like (Taxonomy,Community security model etc etc) but they are just plain common sense.




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

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

http://www.livelink.in