This topic applies only to deployments using either XenApp Services on Web Interface or "legacy PNAgent" on StoreFront.
Options such as selfservice, storebrowse, and pnabrowse enable users to connect to published resources (that is, published applications, and server desktops) through a server running a XenApp Services site. These programs can launch connections directly or can be used to create menu items through which users can access published resources. pnabrowse can also create desktop items for this purpose.
Customizable options for all users running Citrix XenApp on your network are defined in a configuration file, config.xml, which is stored on the Web Interface server. When a user starts one of these programs, it reads the configuration data from the server. After that, it updates its settings and user interface periodically, at intervals specified in the config.xml file.
The config.xml file affects all connections defined by the XenApp Services site.
A XenApp Services site may also publish a file, rather than an application or desktop. This process is referred to as publishing content, and allows pnabrowse to open the published file.
There is a limitation to the type of files that are recognized by Receiver. For the system to recognize the file type of the published content and for users to view it through Receiver, a published application must be associated with the file type of the published file. For example, to view a published Adobe PDF file using Receiver, an application such as Adobe PDF Viewer must be published. Unless a suitable application is published, users cannot view the published content.