REST APIs from FlexNet Licensing operations.

[Ravikiran]

Hi,

Is there any REST API service availabile as of now for 'FlexNet Licensing'.

I got the web service integration guide from below link, but it has mostly for Data Access.

https://docs.revenera.com/fno2020r2/pdf/FNO2020R2_WebServicesIntegrationGuide.pdf

Can someone clearly mention about the current status of Web Services for Licensing part from FlexNet?

Regards,

RaviKiran

[ejohnson1]

Hi @Ravikiran ,

The REST API Licensing is documented in the Cloud Monetization API Guide. Please find attached.

Assume the intent is to preview features on a LLS (or CLS) with a /preview_request and to consume features with /access_request ?

Thanks,

Eric

[Ravikiran]

Hi @ejohnson1 ,

thanks for the quick reply. After careful observation, learned that, CMAPI is not a absolute replacement for SDK. 

As an alternative way, can the SOAP based web services help providing the  complete licensing functionality, please find below link.

https://docs.revenera.com/fno2020r3sp2/soapapi/Default_frame.htm?WS-LicenseService.htm

Regards,

RaviKiran

[ejohnson1]

Hi Ravi,

The SOAP APIs are typically used in offline use cases (or operations support). 

The prime example of the offline use case is its implementation within the Customer Portal - e.g. https://flexXXXX[-uat].flexnetoperations.com/flexnet/operationsportal/logon.do

or within the Producer Portal to support an Operations / Support role.

Thanks,

Eric

[Ravikiran]

Hi @ejohnson1 ,

does that mean, there are no SOAP based web service for Licensing mechanism similar to the one provided by CMAPI. Please confirm.

Also for using the existing SOAP based web services, please refer any updated documentation.

Regards,

RaviKiran

[ejohnson1]

Hi Ravi,

Correct. The interfaces available for licensing are C, Java, .NET and REST.

There is a SOAP API (WSDL v3/ManageDeviceService / generateCapabilityResponse API) to generate / cut licenses, yet it doesn't support served clients like the above interfaces; instead it supports standalone and local license sever device types.

Thanks,

Eric

[Ravikiran]

Hi @ejohnson1 ,

needs more clarity on this.

When you say standalone, does this  mean 'node-locked' - license tightly coupled with one device?

Also when you say 'served clients', could you please elaborate what does it mean.

Does SOAP API supports standalone and LLS ? Actually we are looking for similar APIs. 

Regards,

RaviKiran

[ejohnson1]

Hi Ravi,

Standalone devices are endpoints fulfilled directly from FlexNet Operations.

Local License Server devices are similar to a light-weight version of FlexNet Operations allowing software producers and/or their customers to float / control counts of licesnes.

Cloud License Server devices are the same as a Local License Server device (same componentry), yet hosted by Revenera.

Served Client devices are endpoints fulfilled by a LLS and/or CLS.

In the Devices page of FNO, filtering capabilities like below are available to view/manage the specific devices types noted above.

And, yes, the SOAP API (generateCapabliityResponse) generates a capability response, which are license rights, yet to be processed by a device / endpoint - standalone or local license server. The SOAP API does requires FNO credentials whereas the FNE SDKs utilize the published (C, Java, .NET) API or automatically (built-in) for the LLS if connected.

[Ravikiran]

Hi @ejohnson1 ,

thanks for the explanation.

It SOAP Web services  supports local license sever and CLS clients, could you please point to respective documentation guide

1) to understand the usage and implementation of few use-cases

2) any example programs if any 

Regards,

RaviKiran

[ejohnson1]

Hi Ravi,

Can you access the online documentation from here -> https://docs.revenera.com/fno2020r3sp2/soapapi/Default_frame.htm?Default.htm

Also, please find attached an example XML request bodies successfully tested in SOAP UI for a standalone device as well as a LLS device (and  configure the attributes for your own settings - e.g. identity, deviceId, activationId).

Also, the  response will come back in the addonLicense attribute in base64 format, which can then be decoded and ultimately processed (e.g. XT Kit, FlcProcessCapabilityResponse) via the SDK API.

Thanks,

Eric