Core-Logic Core-Logic does not specifically target the implementation of a single application on a Citrix NetScaler.
Introduction Since the NetScaler platform in many cases is setup as a reverse proxy, the Subnet IPs (or SNIPs) configured are used as the source address in the communication between NetScaler and Backend servers.
The last couple of months we have seen lots of versions of the NetScaler comming from Citrix development.
NetScaler can process traffic in several ways, for example Layer 2 mode, Layer 3 mode and as a full (reverse) proxy, and before you go and implement there are several considerations you need to take on how you would like to get the traffic processed, some of them include: Does the NetScaler need to be transparent in my networks?
Here is an idea on how to create a Content Switch, and hook up lots and lots (and lots) of VServers based on HTTP.REQ.HOSTNAME.
Goal : Load balance ADFS 3.0 using Netscaler Prepare your ADFS 3.0 : ADFS 3.0 by default activates SNI in it’s network bindings.
The issue we are trying to resolve is that if a backend webserver returns an internal server error (500) or otherwise, you might want to provide the end user with information he (or she) can send to the helpdesk.
Digital Imaging and Communications in Medicine (DICOM) is standard that holds a protocol and is used, amongst other things, for retrieving images from medical imaging equipment.
The Content Switch (CSW) is a beautiful feature that enables you to use a single point of entry – your NetScaler – to host multiple services (like XenDesktop, XenMobile and Sharefile).