FnmpXenAppAgent.exe -url http://beacon01.example.com
If you have the option to setup a staging database I would highly recommend it. It is very simple to setup and provides you an invaluable resource to validate your consumption data against actual Citrix XenApp imported data.
If you are just starting with Citrix XenApp consumption you will find it doesn't work as straight forward as you might like. You want to use this the staging DB to verify your Farms and Title list, and raw consumption against what is being put in the [dbo].[ImportedRemote* tables and compliance consumption to trace consumption all the way through the system.
Dawn covered the use case already with the -url command line option, but just to expand a little with some more detail as I’ve been through this with a client in the past couple of weeks.
The two options for getting XenApp data from the XenApp agent are as follows:
- FnmpXenAppAgent.exe -d “<connection string to Staging Database>” … [ other options]
- This is the most common way and the staging database is often located on the beacon
- The data is written to the ImportedRemote* tables in the destination DB
- Here, the agent generates an XML file with an extension of .raa
- The file is sent to the beacon uploaded via ManageSoftRL and is stored in Incoming/RemoteApplication
- The file gets uploaded to it’s parent and eventually is handled by the top tier servers where data is written to the ImportedRemote* tables of the FNMSCompliance database
So – here’s the important part: No matter which option you select above, you need a beacon which has a defined Inventory source connection of type Citrix(XenApp) to the DB where the XenApp staging data resides.
- If you chose the first option above, then the beacon just defines the connection as normal – i.e. a beacon pointing to an SQL source (staging db local to the beacon) of type Citrix(XenApp)
- The second option though, is *only applicable in an on-prem implementation of FNMS* as you need to have a beacon that can reach the FNMSCompliance database
So – my advice would be:
- If the environment is FNMS could – you have no option other than using a staging DB local to the beacon in the client environment.
- If you are fully on-prem, then you could consider the short-cut of using the .raa files – particularly if this was the only need for a staging DB otherwise. You would still need a beacon and define an inventory source connection to the FNMSCompliance database of type Citrix (XenApp). If you needed a staging db for other flows as well (business adapters, ADDM inventory etc), then I’d stick with using the staging DB as you can always utilise the staging DB for troubleshooting in general.