Access Attributes and categories values in livelink using Livelink API coding

Hi All,

i am working on a POC to extract documents from livelink along with associated meta data into a xml format.

i have developed a code in java to extract the code using Livelink API coding however i am unable to take out attributes values along with each document extract. if any one who ever worked on similar kind of work?

or if there any code available to refer from?

Also concerning the extraction rate of document is quite poor around 240 doc per minute so please suggest any solution to improve the extraction rate.

Find more posts tagged with

Comments

HFCDev

When you say Livelink API, do you mean LAPI? If so, you really should be using either REST or Web Services. LAPI is deprecated from CS 10.0 on, and outright not there in CS 16.x. I don't have any WS code in front of me, but I think the process of getting the metadata involves first fetching the node object (not the same as downloading the document), I think, the DocumentManagement.GetNode() call. The Node object has a Metadata Object, and that's what you need to dig into. I warn you that it's not pretty, and if you don't already know the names associated with the category and attribute IDs, if could be quite tedious to convert that information into something you can use.

-Hugh Ferguson

Appu Nair

What Livelink Server version do you want code to run against?

Hopefully you are not using LAPI as in the old coding style.

Here's the vestigial info.

https://knowledge.opentext.com/knowledge/llisapi.dll/open/16361193

I used to do a lot of LAPI coding (that particular link is from 2004 or so I have no notion it will work) so that info what you want is retrievable although

my approach was to do it out of database queries and keep lapi to a minimum for performance.

LAPI has a XMLExport/Import which follows the standard livelink(I know content server:) functionality XMLexport/Import

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=39351127&objAction=viewincontainer&ShowReplyEntry=39293787#forum_topic_39293787

I would expect you to study the xmlexport and the various options in its programming guide,it is done by just adding more and more query string variables to a

livelink object.

If you can I would stay away from LAPI and switch to CWS(SOAP) or REST which has more forum support as well as in CS16 if you need LAPI code running you have to

do some acrobatics as well. LAPI will be replied only by people who has time to support you not very heavily used now.

AFA your complaint about 240 docs per minute one cannot say anything conclusively because it depends on other factors like size of the document,is the LL server thread starved and other aspects .I also don't remember much about lapi performance but that works out to be 4 documents per second which kind of my mind says is good.Is that rate one thread of your lapi program running or multiple lapi clients?

Appu Nair
Principal Architect | Alitek
Website: alitek.com

From: eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com>
Sent: Monday, June 12, 2017 8:09 AM
To: eLink Recipient
Subject: Access Attributes and categories values in livelink using Livelink API coding

Access Attributes and categories values in livelink using Livelink API coding

Posted by Sophia, Jansi On 06/12/2017 09:08 AM

Hi All,i am working on a POC to extract documents from livelink along with associated meta data into a xml format.i have developed a code in java to extract the code using Livelink API coding however i am unable to take out attributes values along with each document extract. if any one who ever worked on similar kind of work?or if there any code available to refer from?Also concerning the extraction rate of document is quite poor around 240 doc per minute so please suggest any solution to improve the extraction rate.

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Content Server:	Knowledge Center CS16

Confidentiality Note: This message contains information, which may be privileged or confidential, or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee responsible for delivering the message to the intended recipient, you are hereby NOTIFIED that any dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you receive this message in error, please notify sender immediately.

Alister Grigg

Hi Jansi

We have a utility that uses CWS to extract content, associated metadata, versions etc. It writes the content to a file share in their native format rather than XML though, with the original file name etc., so that may not help you if the XML is needed for another purpose. We could adapt it I guess, assuming xmlexport doesn't do what you want (I'm not technical ). If it's of interest feel free to drop me a note (alister.grigg@fastman.com)