Citrix StoreFront 2.0 with APM

Yes, there has been quite a few successful deployments, are you having any issues with it or just asking proactively?

Thanks. Just asking proactively, as one customer of mine is planning to implement this shortly. Apparently Storefront 2.0 brings quite some changes in regard to v1.0/v1.2

Did you have any issues locating the 'include.java' file mentioned in the associated deployment guide? In our installation of Storefront 2.0 we could not find that file anywhere on the server and this appears to have negated the functionality of the entire iApp.

Instead, we ended up rolling our own solution by creating two VIPs and doing some stream editing to replace IP/hostnames with Xenapp VIP IPs. Not nearly as clean as I'd like it, but functional and low impact.

We attempted implementing both solutions using APM and the solution using the LTM twice with complete failures each time. Rolling our own seemed much more simplistic.

We have been trying to get the Citrix native receiver working with this iApp. We are using a single iApp for Storefront 2.0 as well as native receiver access. Storefront 2.0 access is working well through a browser, but when using the receiver after login the error returns "Citrix Receiver could not log you on to the store."

We are using SNAT for each Virtual Server and I'm wondering if the preservation of the client IPs is what is causing our issue. Are there any modifications on the Citrix side that need to be made in order to make this work?

I have done some tcpdumps to determine what is happening and it looks like there is a 404 error when the receiver does: POST to /Citrix/PNAgent/enum.aspx

I have been told that PNAgent is legacy for Citrix and no longer needed for storefront 2.0. I'm wondering if this is part of the issue.

Has anyone run into this? It looks like other users are experiencing similar issues with other versions of storefront: https://devcentral.f5.com/questions/ios-receiver-w-apm-storefront-12

Yes, good news, there issue has been identified and fixes produced. If you are experiencing an issue with APM 11.4.0 HF3, please open a support case and request an engineering Hotfix for BZ427743 and BZ417908. Please advise the support engineer that this hotfix has already been built and they need to escalate the case to make it available to you.

I am very happy to report that our issue is resolved. We had an artifact APM_Citrix_PNAgentProtocol (Data Group List) created before my time on the project that was causing the issue. Once removed, we are able to connect properly with the citrix receiver. Thank you for all of the pointers!

As taken from my internal blog about "Citrix ICA Proxying (aka removing the requirement for a Citrix gateway on-site) v.1.1 (TMOS 11.4.1))

2014-08-08: A year (almost) after last updating this.. there is a new step .. to support Storefront 2.0+ by default, "APM recognizes /Citrix/PNAgent/config.xml as the default URL that Citrix Receiver clients (iOS and Android) request. If your Citrix Receiver clients use a value that is different from /Citrix/PNAgent/config.xml, you must configure a data group so that APM can recognize it." (http://support.f5.com/kb/en-us/products/big-ip_apm/manuals/product/apm-citrix-integration-11-4-0/2.html Well we know that Storefront 2.0+ uses /Citrix/Store/PNAgent/config.xml so we need to add these into a special data-group that APM is hard coded to look for (yet interestingly is not auto created???) .

modify ltm data-group internal APM_Citrix_ConfigXML { records add { remote.xxx.catholic.edu.au { data /Citrix/Store/PNAgent/config.xml } } }