Showing results for 
Show  only  | Search instead for 
Did you mean: 


Bypassing the Flexera gateway can make the intergration between App Broker and FNMS simpler on occasstion


This article will explain how to bypass the gateway and reasons not to bypass the gateway


As stated earlier the Flexera Gateway can sometimes cause extra complications to the integration.  The only reason that you need to keep the gateway is you are integrating App Broker with Admin Studio .  Admin Studio does not have a way to directly connect to App Broker, so the gateway must be used so that Admin Studio knows the location of the App Portal web service.  FNMS does not know anything about App Broker , and it never connects to App Portal, so the gateway is not used and can be bypassed. 

Here are the steps to bypass the Flexera Gateway

1) Remove the entry for Flexera Service Gateway Server Name within Site Management | Admin | Settings | Flexera Integration
2) Click Save to apply changes.
3) Access App Portal database and run the following query:

          update dbo.WD_AppSettings
          set Value = ‘True’
          where KeyName = ‘ShowFSGEndPoints’

4) perform an iisreset
5) Restart the browser, and go to Flexera Integration again. At the bottom of the page you should now see "endpoint URLs" exposed.

6) The FlexNet Manager Suite Service Url should be similar to the following. The other endpoint URL's do not need to be set:

           http://<fnms serverName>/ManageSoftServices/ComplianceAPIService/ComplianceAPIService.asmx


Was this article helpful? Yes No
No ratings
Level 4

But Appbroker connects to FNMS.  THis is very confusing article.  

Version history
Last update:
‎Apr 13, 2022 09:35 AM
Updated by: