nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

CWS Search Service Introduction

Dan_Anderson

I am new to CWS and our application will need to integrate with the available Search Services. I've looked over some of the API documentation and forums but I haven't found any examples for CWS on how to setup the SingleSearchRequest and SingleSearchResponse objects.

Our application will need to utilize the Full Text Search as well as searching by category(s). Any examples would be helpful or any links to other documentation would work.

Thanks,
Jeremy

Find more posts tagged with

Comments

Kyle_Swidrovich

Hi Dan,

Although there is a SearchService available with CWS, product management strongly recommends using the RESTful Search API instead of the CWS implementation.

The CWS implementation is quite complex and cumbersome, which is why no further development is going into that implementation.

All current development is going into the RESTful Search API implementation.

The RESTful Search API (aka the Search XML API) is a part of core Content Server (?func=search) and its full documentation can be found here:

https://knowledge.opentext.com/knowledge/cs.dll/Open/16579994

If you’re still interested to see what use of the CWS SearchService looks like, have a look at the 9.7.1 C# sample I posted and pinned here in OTDN:

https://knowledge.opentext.com/knowledge/cs.dll/Overview/16928016

Regards,

Kyle

Dan_Anderson

Thanks Kyle,

Do you have any examples for how to setup the REST/Search XML implementation using .Net? I read through some of the API Programming Guide and it seems you have to create the HTML interface by hand. It seems counterintuitive compared to the Search Service since .Net easily generates the web service proxies.

Our application as it stands now already utilizes the other web services such as DocumentManagement, Member, Collaboration etc. so just how much do you recommend using this other approach for searching? If the XML API is something that can be incorporated easily with these other services then we will probably go that route.

Thanks,
Jeremy

Kyle_Swidrovich

Hi Dan,

Sorry, I don't have any examples on hand.

Before you can make a request to Content Server, you need to authenticate first and get an authentication cookie.
This concept is so similar to web services that the authentication token you receive from the AuthenticateUser() method in the Authentication web service can be reused for standard web requests to Content Server's CGI/ISAPI/Servlet.

That is, if you call AuthenticateUser() and obtain the token, you can then make a request to http://yourserver/yourvirtualdir/cs.exe?func=search using the token value as the "LLCookie" cookie. This will allow you to authenticate and execute the search.

Keep in mind that cookies can expire, based on the server's security settings, so if as long as you use some high level object for HTTP traffic in .NET, it should listen to periodic Set-Cookie directives from the server meant to refresh your token.

Cheers,
Kyle

sroller

Hi Dan,

to get to know the RESTful API for search you could start with command line examples. I propose you download curl.exe from here.

Then put this two lines into a batch file and play around with it:

curl -k --cookie-jar cookies.txt -d func=ll.login -d Username=<your id> -d Password=<your pwd> https://www.your-livelink.com/your-livelink/llisapi.dll
curl -kv --cookie cookies.txt `https://www.your-livelink.com/your-livelink/llisapi.dll?func=search&where1=(\"OTCreatedByName\":\"joesixpack\")&outputformat=xml&sortBy=custom&rankby="OTObjectDate" DESC`