LAPI performance issues

Has anyone encountered LAPI performance issues? Could you please recommend any alternates for bulk extraction of Metadata values (not actual data).

Please advise.

Thanks, Manoj

Find more posts tagged with

Comments

Nizar Ghazal

All category and attribute information that LAPI and the other APIs, will get at, is stored in the database.

You could likely craft a LiveReport or SQL report against LLAttrdata to extract the categories, the attributes, and their values, for a given set of DataIDs, and then likely do something with that.

That is if you want to cut out the middle-man, and bypass using LAPI/EWS.

Tomas Hansson

Another option may be to use Object Exporter and then parse through the XML data to get the values that you need.

Appu Nair

In all likelihood what you mean by this is

When we run it to extract 1000 docs metadata with 10 threads or less, the response time is almost 6-8 minutes per thread and after 4-5 threads

Is that 10 Thread? a invocation of the LAPI Client(Java,C#,C++ etc)

That thread is not equivalent to a Livelink Thread

Just like any web app LL will have bottle necks in performance at the code level and the DB level.

To increase through put what one should do is find form your OT Admin how many LL threads are configured per instance of livelink.In 971 its bound to be 5 or 7.That means if you send a request through any means(lapi,wr,soap,oscript) one thread of LL will be assigned and it will deliver,So what if 23 requests come to a LL server that has 5 threads to do the work load,18 will queue until one of them are able to get free.In LAPI you are talking to the server through a session mechanism who probably got you tied to a server and your job load is higher.

I have run LAPI applications in extraction scenarios with very high through put ,but that was because one knew how to go through the application scenarios well.You are also forgetting that all commercial product hitherto the advent of SOAP ran on LAPI.There were several commercial products that ran(Blue Baker,Formark,Authorlink,AutoCad ,Kofax Release and a lot of others) nobody would have bought them if LAPI apps were slow.

So blaming a product API is not the right thing to do .In fact in most lapi apps you are talking directly to the lapi port(2099) so you bypass the overhead of a web server to tunnel into 2099.

BTW I concur with Nizar Ghazal of OT that if you wanted to get metadata fast you do not need LAPI,the category attribute data are extremely easy once you understand how to get it out.

Appu Nair
Principal Architect | Alitek
Website: alitek.com

From: eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com>
Sent: Monday, April 16, 2018 1:45:25 PM
To: eLink Recipient
Subject: LAPI performance issues

LAPI performance issues

Posted by magrawal5@metlife.com (Agrawal, Manoj) On 04/16/2018 02:40 PM

Hi, Unfortunately we still run in LiveLink 9.7.1 and use LAPI. LAPI is used to get category and attributes metadata information for documents in a new project. It is very slow for bulk extraction. When we run it to extract 1000 docs metadata with 10 threads or less, the response time is almost 6-8 minutes per thread and after 4-5 threads, LAPI just dies down and does not even respond.Has anyone encountered LAPI performance issues? Could you please recommend any alternates for bulk extraction of Metadata values (not actual data).Please advise.Thanks, Manoj

[To post a comment, use the normal reply function]
Forum:	Content Web Services Forum
Content Server:	My Support

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.

Manoj Agrawal

Thankyou everyone for posting your responses. They are very helpful. if anyone has or comes across SQLs which have been used for category/attrobutes extraction, please share it with me. Meanwhile I will work on building a SQL too to pull the data.

appuGmail

When Lapi was prevalent in its hey day there were high level packages written by OT hobbyists I remember two distinct products called EasyLapi and SLapi one of them had a Very way way to create you a view to report on categories

Since LLAttrdata is the main table and it has enormous rows of data getting a single row of data is actually very easy . You need just the dataid of the category and join to dtree on versionnum

Search for terms like ‘ how to report on 9 categories’ or such terms

OT changed the category model in year 2000 and very little has changed after that

My blog livelink.in may have the exact OT link as well

Every LL customer uses a query or a view to report on that at least 1000’s of queries are available in the LR/ WR area

Ciao, Appu

On Apr 19, 2018, at 8:54 PM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

eLink : [EXTERNAL] - Re LAPI performance issues
[EXTERNAL] - Re LAPI performance issues Posted bymagrawal5@metlife.com (Agrawal, Manoj)On 04/19/2018 01:30 PM

Thankyou everyone for posting your responses. They are very helpful. if anyone has or comes across SQLs which have been used for category/attrobutes extraction, please share it with me. Meanwhile I will work on building a SQL too to pull the data.
[To post a comment, use the normal reply function]
Topic: LAPI performance issues
Forum: Content Web Services Forum
Content Server: My Support