How to retrieve Category and Attribute Value using LAPI

We have a business requirement to extract attribute value for certain category name. Document count would be in millions. While going thru LAPI document, I came across function called AttrGetValues, although per documentation(link below), it does not seem to list any unique identifier which can pull attribute values of exact object.

https://knowledge.opentext.com/knowledge/llisapi.dll/fetch/16060242/llesapi/v090701/llesapi-pgd/en/html/_manual.htm

Please advise if there is a way to extract attribute values via LAPI,

Thanks, Manoj

Find more posts tagged with

Comments

appuGmail

Why use LAPI if it is to get attribute data you can use search or SQL

Can’t you? Nobody uses LAPI nowadays so your responses will be only very small.

CWS can enumerate the attributes. So can REST

Ciao, Appu

On Jan 11, 2018, at 3:28 PM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

eLink : How to retrieve Category and Attribute Value using LAPI
How to retrieve Category and Attribute Value using LAPI Posted bymagrawal5@metlife.com (Agrawal, Manoj)On 01/11/2018 04:26 PM

We have a business requirement to extract attribute value for certain category name. Document count would be in millions. While going thru LAPI document, I came across function called AttrGetValues, although per documentation(link below), it does not seem to list any unique identifier which can pull attribute values of exact object. https://knowledge.opentext.com/knowledge/llisapi.dll/fetch/16060242/llesapi/v090701/llesapi-pgd/en/html/_manual.htmPlease advise if there is a way to extract attribute values via LAPI,Thanks, Manoj

Attachment Links:
LAPI Documentation
[To post a comment, use the normal reply function]
Forum: Content Server Development Forum
Content Server: My Support

David Templeton

What version of CS are you wanting to access? LAPI has been deprecated and removed from the product.

Regards

David

Manoj Agrawal

Hi Appu, thankyou for responding. The reason we wanted to use LAPI is because there is a framework being built around LAPI to pass the attribute to downstream system. If we use SQl, wit can fetch the data but another service would need to be built to consume that data for further processing. Also we are not sure if it will impact performance due to direct database hits as we have close to 10 million documents for a particular category.

Thanks

Manoj Agrawal

Hi David, we are using LiveLink 9.7.1. Yes we understand LAPI is deprecated now but for 9.7.1 until we upgrade we wanted to use LAPI for short term.

Thanks, Manoj

appuGmail

As DT indicated LAPI is dead(almost) Very few people know its Oscript side and its client side to help you.You would be better off doing this in a supported API.

I have not heard of a LR/SQL of 10 million rows causing any problems if the report writer knows how to page it correctly.Obviously your framework/client will choke if you send 10 million rows

into it .You would use API's only if you needed something to do with it like -Download the document,change its metadata and such.More like document related functionality but not

like reading values of it.

While OT says LAPI is dead they are not telling you the whole truth legacy applications such as ESCAN/webinterface are yet to convert to pure Soap code ,so one would install a new module called

"Private Bridge Interface " which brings back the LAPI support OSpaces .It is pretty apparent what OT is doing they don't want client applications to do LAPI so they can retire or pull support at any

time so no point in fighting with a behemoth in this field like OT.

You also can use Search XML API if your search system works.

..... appnair appunair( Livelink Rocks )

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Fri, Jan 12, 2018 at 8:28 AM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

[EXTERNAL] - Re How to retrieve Category and Attribute Value using LAPI Posted bymagrawal5@metlife.com (Agrawal, Manoj)On 01/12/2018 09:27 AM

Hi Appu, thankyou for responding. The reason we wanted to use LAPI is because there is a framework being built around LAPI to pass the attribute to downstream system. If we use SQl, wit can fetch the data but another service would need to be built to consume that data for further processing. Also we are not sure if it will impact performance due to direct database hits as we have close to 10 million documents for a particular category.Thanks
[To post a comment, use the normal reply function]
Topic: How to retrieve Category and Attribute Value using LAPI
Forum: Content Server Development Forum
Content Server: My Support