Using FlexNet Operations SOAP Web Services
Any client application calling the FlexNet Operations Web Services needs the following:
| • | A Web Service client implementation containing stubs/proxies generated from the service interfaces |
| • | An environment in which to develop and run clients to Web Services |
| • | FlexNet user credentials (user ID and password) that have been assigned one or more roles with sufficient permissions to perform requested operations (See User for Executing SOAP Web Services.) |
| • | A client program that you write to connect to the service that knows |
| • | The URL to connect to the service |
| • | FlexNet user name and password |
| • | The semantics of the service methods |
| • | The purpose of the each method |
| • | The return values expected from the methods |
By appending ?wsdl to the end of the Web Service URL, you obtain an automatically generated WSDL document that describes the Web Service:
where <serviceName> is one of the base version Web Service names listed in
Note that the location for the WSDL for the Download Packaging Service differs from that mentioned above:
https://<siteID>-fno.flexnetoperations.com/flexnet/services/<version>/DownloadPackagingService/wsdl/DownloadPackagingService.wsdl.
|
Web Service |
Web Service Name |
Parent Module |
|
Product Packaging |
ProductPackagingService |
FlexNet Operations |
|
Entitlement Order |
EntitlementOrderService |
FlexNet Operations |
|
License |
LicenseService |
FlexNet Operations |
|
User Account Hierarchy |
UserAcctHierarchyService |
FlexNet Advanced Organization Management |
|
Flexnet Authentication |
FlexnetAuthentication |
FlexNet Operations |
|
Manage Device |
ManageDeviceService |
FlexNet Advanced Lifecycle Management |
|
Download Packaging |
DownloadPackagingService |
Software Delivery |
|
Usage |
UsageService |
FlexNet Usage |