- Revenera Community
- :
- FlexNet Embedded
- :
- FlexNet Embedded Forum
- :
- Re: REST APIs from FlexNet Licensing operations.
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
REST APIs from FlexNet Licensing operations.
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
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @ejohnson1 ,
thanks for the reply, Will check the API and respond.
Actually I want to avoid SDK and implement the same using SOAP web services. As per your reply, still there is a dependency on SDK for decoding the addonLicense ...etc attributes.
Please clarify.
Regards,
RaviKiran
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi Ravi,
Yes, the response requires decoding from base64 and more importantly, the response requires processing by the SDK API.
The analogy I would use is the response is the equivalent of a gift card (e.g. Starbucks) and redeeming the card for a coffee / license is the equivalent of tapping the card (e.g. QR code decode) then receiving your coffee (processing the license via the SDK API).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
HI @ejohnson1 ,
thanks for the reply.
Since the SDK library size is more, if we use SOAP/REST the solution would be light weight. Hence, would like to reduce SDK foot print.
Regards,
RaviKiran
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi Ravi,
REST is the lightest of light weight available.
Once configured, it's a single API (access_request), which does the capability exchange and license acquisition in one go (no processing of the capability response)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @ejohnson1 ,
for using SOAP web services, can you point to the guide to understand more about the client authentication part and also which credentials to be used.
Regards,
RaviKiran
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi Ravi,
Documentation on managing users can be found in the online documentation link above in the "FlexNet Operations 2020 R3 SP2 User Guide".
In the guide, managing users is outlined as follows:
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)