Different ways to Search Content Server 16.x

Hello

Just getting started with the content server REST API..

My goal is to search content server 16.x

Till what I have explored I can see Two ways to achieve this

1. Using the llisapi.dll (ex-: http://contentServer/otcs/llisapi.dll/api/v2/search?where=110)

2. Using the Search API (ex-: http://contentserver/otcs/cs.exe?func=search&where1=110)

What is the best way to achieve this..in teams of performance, ease of use or I am missing something. Also what is the difference between the above two approaches?

Find more posts tagged with

Comments

Patrick Pidduck

To restate, this is a question of whether to use the Search XML API or the newer REST API for search. The use of llisapi versus cs.exe is not relevant.

The XML API is older, more mature, and has more features – although the extra features are minor and may not be important. It also does more legwork to populate “ready to use” URLs for some common actions.

The REST API is newer, and has changed with new capabilities between the various CS 16.x updates. Not quite stable yet. On the other hand, it emits JSON results. We are using this for our search widgets in the Smart UI, but haven’t yet formally released all the documentation. That should come in the next couple of updates.

For the most part, your preference for consuming and working with JSON versus XML results might be the single most important consideration. At this point, they are both production-ready and fully supported.

For completeness – the CWS/SOAP and the Enterprise Library Search APIs are not recommended.

Patrick

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Thursday, August 31, 2017 9:48 AM
To: eLink Recipient <devnull@elinkkc.opentext.com>
Subject: Different ways to Search Content Server 16.x

Different ways to Search Content Server 16.x

Posted by Devineni, Krishna On 08/31/2017 09:41 AM

Hello

Just getting started with the content server REST API..

My goal is to search content server 16.x

Till what I have explored I can see Two ways to achieve this

1. Using the llisapi.dll (ex-:http://contentServer/otcs/llisapi.dll/api/v2/search?where=110)

2. Using theSearch API (ex-:http://contentserver/otcs/cs.exe?func=search&where1=110)

What is the best way to achieve this..in teams of performance, ease of use or I am missing something. Also what is the difference between the above two approaches?

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

appuGmail

Adding a lil bit more "techie" to Patrick's excellent reply

Your First Format is the proper RESTAPI invocation

1. Using the llisapi.dll (ex-: http://contentServer/otcs/llisapi.dll/api/v2/search?where=110)

so even if you did this it will work

1. Using the livelink.exe or cs.exe (ex-: http://contentServer/otcs/cs.exe/api/v2/search?where=110)

Think of it as llisapi.dll,livelink.exe,cs.exe,,livelink all cgi based scripts that allow you to talk to the livelink server

There is no concept of accessing livelink through the GUI,Programs(Soap or REST) without providing a valid user/p/password

all the things you hear as Tokens,Cookies etc.Newer livelink systems accept a 'man in the middle' authentication mechanism called OTDS

when the ivelink server sees api/v2/search api/v2/search (what we call a glorified Request handler) it parses from your client code the

header and the token passed in and passes off the command to the livelink search engine.Anytime the livelink server does not like

the token(cookie) it will reject it and you see the dreaded invalid/username password,Common culprits no affinity to server,too short a time

etc,cookie from server1 passed to server2 .

When you use the livelink GUI and basically get set up your enterprise workspace should look something like this

http://<some server>/OTCS/llisapi.dll?func=llworkspace then if you move around and use fiddler you can see upto llisapi.dll is the

CGI script all the rest is parameters to the application but do not think of using livelink's web parameters as a proper API

when the RH changes to ?func=search this is the invocation to

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

Look at the date of the article by our esteemed DT 2003 so the livelink community has been using the searchAPI(formerly called XMLSearchAPI)

AFA efficiency goes you probably want to make use of how to return results in chunks not overwhelming the client application and the network

If you use the second format somehow you have to get livelink a cookie first,the REST API search RH is a specialized RH designed so that

you do not have to re-invent the wheel and it so happens REST can be invoked form any web page(hence the insistence on providing a header element)
and I think Patrick said it it provides JSOn preferred by new age apps.

And I didn't know REST search api isn't fully baked yet thanks Patrick for that info.Hopefully what works in func=search is what is needed in many cases.

the SOAP search api is quite tedious....

..... 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 Thu, Aug 31, 2017 at 8:47 AM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

Different ways to Search Content Server 16.x Posted byDevineni, KrishnaOn 08/31/2017 09:41 AM

HelloJust getting started with the content server REST API..My goal is to search content server 16.x
Till what I have explored I can see Two ways to achieve this

1. Using the llisapi.dll (ex-: http://contentServer/otcs/llisapi.dll/api/v2/search?where=110)

2. Using the Search API (ex-: http://contentserver/otcs/cs.exe?func=search&where1=110)

What is the best way to achieve this..in teams of performance, ease of use or I am missing something. Also what is the difference between the above two approaches?

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

redrock

Thanks Patrick..for the repsonce

Just to make sure when you say "The use of llisapi versus cs.exe is not relevant." Means both are same Right only diffrence is that

CS.exe run as a CGI within the web server and llisapi.dll is an ISAPI filter or there is more to it?

Quoted Patrick Pidduck on 08/31/2017 08:11 PM:

To restate, this is a question of whether to use the Search XML API or the newer REST API for search. The use of llisapi versus cs.exe is not relevant.

For completeness – the CWS/SOAP and the Enterprise Library Search APIs are not recommended.

Patrick

Different ways to Search Content Server 16.x

Posted by Devineni, Krishna On 08/31/2017 09:41 AM

Hello

Just getting started with the content server REST API..

My goal is to search content server 16.x

Till what I have explored I can see Two ways to achieve this

1. Using the llisapi.dll (ex-: http://contentServer/otcs/llisapi.dll/api/v2/search?where=110)

2. Using the Search API (ex-: http://contentserver/otcs/cs.exe?func=search&where1=110)

What is the best way to achieve this..in teams of performance, ease of use or I am missing something. Also what is the difference between the above two approaches?

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

Jean-Philippe_Martin

In terms of thread use or the impact on the server, would you recommand a solution instead of another ? Ex: do the REST API use the Admin Service for executing the search query ? I am a little bit cautious before developping something based on the search API, afraid to "hammer" too much the environnement. Is my worry warranted ?

Patrick Pidduck

Internally, these both execute mostly the same code. I’m not aware of any fundamental performance differences between them.

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Thursday, August 31, 2017 11:24 AM
To: eLink Recipient <devnull@elinkkc.opentext.com>
Subject: RE Different ways to Search Content Server 16.x 2

RE Different ways to Search Content Server 16.x 2

Posted by Martin, Jean-Philippe On 08/31/2017 11:23 AM

[To post a comment, use the normal reply function]
Topic:	Different ways to Search Content Server 16.x
Forum:	Content Server Development Forum
Content Server:	Knowledge Center CS16