In blog, case studies, health check

To assure compliance and full support, companies upgrade their Citrix/SAP environments on a regular basis. More often than not, users are complaining about things being slow compared to the previous release.

health check Citrix SAP

A typical, simplified Citrix-SAP setup

Typically, the SAP teams of these companies start with improvements utilizing SAP Solution Manager to figure out the “where” and “what” inside the SAP-parts of the environment.

After some time, when users are still complaining, things tend to escalate. This is the time where companies start looking for an end-to-end health check answering questions like “Is it Citrix or SAP?” and “Suppose it is Citrix, what part of Citrix and what to do about it (i.e. what are the quick wins)?”.

This case study gives you a detailed overview about our approach and the findings.

Unpredictable behavior

The initial findings of this health check indicate suspicious network behavior in the zones between the Citrix client and the Netscaler as well as between the XenApp server and the SAP front-end.

health check Citrix SAP

The differences in user experience between the segments

When looking at the variations of the measurement values from these zones, the additional delay on the user response times varies between 500 and 4000 ms; occasionally even more as outliers tend to be 2-3 times their average values.

This makes the performance of the environment erratically and very unpredictable; hence user complaints come and go.

Full case study

This case study, which is only available as a PDF, describes the setup (part 1), the findings (part 2) and the discovery of the quick wins (part 3) of one of those Health-checks; including how this answers these questions.

Sounds interesting? Click here to receive your copy of this PDF.