OT Roadmap for Web Services

Hi,

Can someone from OpenText confirm or deny the following rumour I heard today: That going forward, support for Web Services would be dropped an instead, all developers would switch to using the REST API as defined over at developer.opentext.com???

Given that WS is essentially a Representative STate API, I find that a little bit weird. Also, when looking, I found many rec man functions done in WS but not in REST or are they coming?

Thanks in advance

-Hugh Ferguson

Find more posts tagged with

Comments

Kyle_Swidrovich

Hi Hugh,

In-product support for Content Web Services is not going away any time soon (at least 5 years).

What has happened is our development investment is targeted towards improving the REST API coverage and performance, leaving the Content Web Services API relatively static with very infrequent changes.

I’ll let Tracy Caughell or Pat Fennessy (product management for RM) speak to plans for further RM-specific REST API coverage.

Cheers,

Kyle

Tracy_Caughell

Hi Hugh.

The RM coverage in REST API is a work in progress. We initially are focusing on the functions required to support our own implementations in the SmartUI, and this will continue to be advanced in the foreseeable future.

I second Kyle in that the WebServices will continue to be supported from an RM perspective too.

Tracy

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: Monday, May 29, 2017 12:10 PM
To: eLink Recipient <devnull@elinkkc.opentext.com>
Subject: RE OT Roadmap for Web Services

RE OT Roadmap for Web Services

Posted by Swidrovich, Kyle On 05/29/2017 12:09 PM

Hi Hugh,

In-product support for Content Web Services is not going away any time soon (at least 5 years).

I’ll let Tracy Caughell or Pat Fennessy (product management for RM) speak to plans for further RM-specific REST API coverage.

Cheers,

Kyle

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

Ferdinand Prantl

I have not heard, that SOAP WS should get less attention in future. I do not expect it, as long as SOAP WS remains the most ofteh used B2B standard.

When you choose a B2B API, which is the recommended scenario for SOAP WS, you usually check criteria like target platform integration, SSO support, available features, support in development tools, productivity in complicated scenarios etc.

REST API is usually chosen for a single simple scenario, where the disadvantage of development tool support or less functionality is not noticeable.

I would not worry about rumors, unless the whole world goes other direction.