Migrate from LLAPI to CWS

Hi,

I'm new to CWS and I have to migrate a client from LLAPI to CWS. My software create folders, archive document with related categories.

My question is: Have I just modify the client ? Or have I also to write some code on server CWS side?
The WS functions aviable via Web service by default give the same functionalities of LLAPI?

Thank you very much in advance

Find more posts tagged with

Comments

eLink User

CWS or EWS are SOAP based code,you will need to enable the WSDL in Tomcat or IIS which is very straightforward as the real code (oscript) is actually part of the installed base of livelink(you can copy that and make applications out in a webserver or servlet container)

Here is the main link to get started https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=45500683&objAction=browse&viewType=1

If you register at developer.opentext.com you will see yet another simplistic API doing Restful calls.(very little setup except OTDS)

Both RESTAPI and CWS can be extended by writing Oscript but your requirements are very easy to do.

Further Kyle Swidrowich has a article or a link saying capabilities of both API's and long term support of it but I like to think it simple and think REST is good for mobile and SOAP for more rugged applications.I also read that OT is coming up with a tool that can interrogate your LAPI usage and map it out to CWS calls.

.....appu appnair appunair

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

On Wed, Jan 20, 2016 at 2:38 AM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

Migrate from LLAPI to CWS Posted byMenichelli, FabrizioOn 01/20/2016 03:33 AM

Hi,I'm new to CWS and I have to migrate a client from LLAPI to CWS. My software create folders, archive document with related categories.

My question is: Have I just modify the client ? Or have I also to write some code on server CWS side?
The WS functions aviable via Web service by default give the same functionalities of LLAPI?

Thank you very much in advance

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

jdonpaul

To add to Appu's post, there is an excellent document in the Champion Toolkit section which explains equivalent LAPI to CWS calls are. it is located here:

https://knowledge.opentext.com/knowledge/llisapi.dll/Open/KBA750007

This holds true to the CWS 9.7.1. As for CS 10.0.0 and 10.5.0, you would also want to take into account what functionality has been added since then and reference the proper web services documentation for that version. The documenation can be found here:

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

Hope this helps you out.

Regards,

Jerome

Kyle_Swidrovich

Hello all,

We’ve been working on a document for many months now titled “OpenText Content Server 16 APIs Function Comparison Charts” that helps with your journey from LAPI to CWS or REST. The document provides mappings between LAPI functionality and CWS and REST functionality. It also provides rationale for moving away from LAPI and provides links to the utility patches that Appu referenced that will allow you to evaluate how LAPI is being used in your environment.

It is currently offered as supporting documentation for members of the Content Suite 16 Beta program and will become public upon the full release of the product.

The document is an ongoing work in progress, so when it becomes public, I strongly recommend subscribing to notifications for the document so you can become aware of the changes we make to it.

Regards,

Kyle

Fabrizio_Menichelli

Thank you to all for your information.

But what do you say about the performance? Are they better with LLAPI or CWS?

Thank you.

eLink User

The point is moot because if OT is removing server side oscript for lapi then your lapi calls won't work .Speed is relative because in lapi if you were hitting the lapi port it was still a piece of oscript code doing it.Like wise in WSAPI you are making use of the webserver to get to the lapi port.

I paste this info not done in a controlled way or anything like that against a very aging 971 server,with tonnes of callbacks and modules which significantly slows down the system but quite happy

29962 nodes start 2:08:14 PM end 8:45:06 PM 6 hrs 37 mins, 397 mins ie 75 nodes/min

the code was just updating a category field its replacement values came from a Oracle query so it was not all time it took to do livelink stuff.

Most of the vendors are making their older lapi tools to support CWS(Fastman,Blubaker like that) and they are all happy .Coding wise it is a big improvement .

I do not know about this but definitely REST API bulk operations might cause thread starvation as it has to return more stuff to the client than a SOAP or LAPI call.

because REST is basically like a webgui hit.One of these days I will try REST and share my experiences

.....appu appnair appunair

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

On Thu, Jan 21, 2016 at 3:26 AM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

RE Re Migrate from LLAPI to CWS Posted byMenichelli, FabrizioOn 01/21/2016 04:24 AM

Thank you to all for your information.

But what do you say about the performance? Are they better with LLAPI or CWS?

Thank you.
[To post a comment, use the normal reply function]
Topic: Migrate from LLAPI to CWS
Forum: Content Web Services Forum
Content Server: Knowledge Center

Fabrizio_Menichelli

Thank you,
but my customer is asking me an upgrade (LLAPI to CWS) for perfomance reasons, so I need to know if the performances will be better with CWS.

Thank you

Kyle_Swidrovich

It really depends on what you’re doing.

There isn’t a perfect one-to-one mapping of LAPI functions to Content Web Services.

Authentication is different.

Transactional logic is different.

There is overhead in going through a web server vs. connecting directly to the LLServer service on port 2099.

The underlying business logic is very common between LAPI and CWS.

It’s all the bits in between that can ultimately have the largest effect on total performance.

Regards,

Kyle

HFCDev

You will probably have a slight performance hit from LAPI to WS due to the fact that you have the additional layer with the web server versus going direct to the Liveli...err. Content Server port (2099). However, you gain security going to WS or REST because you can secure/encrypt your traffic using https whereas traffic going over port 2099 (including your authentication credentials) is unencrypted. Yeah, there was a LAPI over https which adds the overhead of the web server, but I don't know if you're doing that already.

Your existing app probably has to run local to Content Server due to the fact that it's unencrypted while your WS API app can be anywhere. You can also spin up additional instances of Content Server that can be dedicated to responding to WS requests, leaving your front end threads alone.

-Hugh Ferguson

Fabrizio_Menichelli

Thank you very much,

can I improve the performance of the import using pipeline or addon object handler?

Thank you.