Migrating a Custom Administrative Tool

The SA uses REST APIs (endpoints) in XML format to access and post license server data; the LLS uses REST APIs in JSON format. You can rewrite your administrative tool using the new APIs for LLS. The following table provides a reference for mapping the functionality between the XML and JSON formats of the two license servers.

API-to-API Translation Matrix

XML API for SA

JSON API for LLS

HTTP Method

/fne/xml/reservation

/api/1.0/reservationgroups
/api/1.0/reservationgroups/gid/reservations

GET

/fne/xml/setreservation

/api/1.0/reservationgroups

POST

/fne/xml/features

/api/1.0/features
/api/1.0/clients

GET

/fne/xml/features?detailed=true

/api/1.0/features
/api/1.0/clients

GET

/fne/xml/features/feature_name

/api/1.0/features
/api/1.0/clients

GET

/fne/xml/features/feature_name?detailed=true

/api/1.0/features
/api/1.0/clients

GET

/fne/xml/overages

/api/1.0/overages
/api/1.0/clients

GET

/fne/xml/devices

/api/1.0/clients

GET

/fne/xml/devices/device_name

/api/1.0/clients

GET

/fne/xml/devices/device_name (DELETE method)

/api/1.0/clients

DELETE

/fne/xml/setproperties

/api/1.0/configuration
/api/1.0/hostids
/api/1.0/hostids/selected

POST

/fne/xml/properties

/api/1.0/configuration
/api/1.0/hostids

GET

/fne/xml/errorlog

Corresponding endpoint not supported

N/A

/fne/xml/accesslog

Corresponding endpoint not supported

N/A

/fne/xml/diagnostics

/api/1.0/version

Only the server version provided (no directly corresponding endpoint supported)

GET

/fne/bin/offline-capability-request

/api/1.0/capability_request/offline

GET

/fne/bin/offline-capability-response

/api/1.0/capability_response

POST

/fne/xml/activation

/api/1.0/activation_request

POST

/fne/xml/offline-activation

/api/1.0/activation_request/offline

POST

/fne/xml/start-sync-to-fno

/api/1.0/sync_message

GET

/fne/xml/timers

Corresponding endpoint not supported

N/A

/fne/bin/capability (used by the test tool caprequestutil and the FlexNet Embedded client toolkit capabilityrequest example)

/fne/bin/capability

POST

/fne/bin/offlinesync

/api/1.0/sync_message/offline

GET

/fne/bin/offlinesyncack

/api/1.0/sync_ack/offline

POST