Citrix Access Suite 4 Advanced Concepts: The Official Guide in Software

Generation Quick Response Code in Software Citrix Access Suite 4 Advanced Concepts: The Official Guide

Citrix Access Suite 4 Advanced Concepts: The Official Guide
QR Code Drawer In None
Using Barcode printer for Software Control to generate, create QR image in Software applications.
QR Code ISO/IEC18004 Reader In None
Using Barcode decoder for Software Control to read, scan read, scan image in Software applications.
Fort Lauderdale
QR Printer In C#
Using Barcode creator for .NET framework Control to generate, create QR Code 2d barcode image in VS .NET applications.
Making QR Code In VS .NET
Using Barcode printer for ASP.NET Control to generate, create QR Code JIS X 0510 image in ASP.NET applications.
Redmond
Quick Response Code Drawer In VS .NET
Using Barcode generation for .NET framework Control to generate, create QR Code image in .NET applications.
QR Code ISO/IEC18004 Generation In Visual Basic .NET
Using Barcode drawer for Visual Studio .NET Control to generate, create QR Code 2d barcode image in .NET framework applications.
Password Manager Service
Drawing EAN-13 In None
Using Barcode maker for Software Control to generate, create EAN13 image in Software applications.
Barcode Creation In None
Using Barcode maker for Software Control to generate, create barcode image in Software applications.
Password Manager Service
USS Code 128 Printer In None
Using Barcode printer for Software Control to generate, create Code 128 Code Set A image in Software applications.
Bar Code Generator In None
Using Barcode creator for Software Control to generate, create barcode image in Software applications.
DFS Replication
Code39 Drawer In None
Using Barcode encoder for Software Control to generate, create Code-39 image in Software applications.
Paint EAN 128 In None
Using Barcode printer for Software Control to generate, create EAN 128 image in Software applications.
Central Store Load Balancer
Identcode Generator In None
Using Barcode encoder for Software Control to generate, create Identcode image in Software applications.
Generating DataMatrix In VS .NET
Using Barcode printer for Reporting Service Control to generate, create Data Matrix ECC200 image in Reporting Service applications.
Central Store Load Balancer
Generate UPC-A In Objective-C
Using Barcode generation for iPad Control to generate, create UCC - 12 image in iPad applications.
Barcode Encoder In .NET Framework
Using Barcode encoder for ASP.NET Control to generate, create bar code image in ASP.NET applications.
Figure 19-22 Password Manager design for XYZ
EAN13 Creator In None
Using Barcode generator for Word Control to generate, create GTIN - 13 image in Word applications.
Create Code 128 Code Set C In Java
Using Barcode encoder for Android Control to generate, create Code128 image in Android applications.
Figure 19-22 illustrates the way in which XYZ architected its Password Manager setup
Printing Code 39 Full ASCII In Objective-C
Using Barcode creation for iPhone Control to generate, create USS Code 39 image in iPhone applications.
UPC Code Generation In None
Using Barcode printer for Font Control to generate, create UPC-A image in Font applications.
Remote Presentation Server Users Through Access Gateway 41
To deploy corporate applications to remote employees, XYZ uses the Access Gateway to control access into the corporate network XYZ ensures Access Gateway redundancy by using a hardware load balancer at each site The load balancer is not represented in Figure 19-23, but it is being used to load balance the Access Gateway and Web Interface servers at each site For more details about setup recommendations for the load balancer, see the section on Access Gateway redundancy recommendations
19:
Disaster Recovery Planning and Configuration
Fort Lauderdale
Redmond
FQDN of Web Interface Load Balancer
FQDN of Web Interface Load Balancer
Secure Ticketing Authority
AGFTLXYZCOM Access Gateway
AGFTL XYZCOM Access Gateway
Secure Ticketing Authority
Remote Clients connecting to Access Gateway FQDN
Remote Clients connecting to Access Gateway FQDN
Figure 19-23 Access Gateway redundant design for XYZ
XYZ distributes the load between the two sites by training users to connect to their closest site The FQDN of the load-balanced Access Gateway machine in Fort Lauderdale is AGFTLXYZCOM and the FQDN in Redmond is AGREDXYZCOM For the site failure to be seamless, the certificates on the Access Gateway machines must be configured correctly XYZ wants to support failover from one site to the other using the same name, so *XYZCOM is used for the Access Gateway certificate names If a site failure occurs, a DNS change is required for the FQDN of the Access Gateway machine in the failed site For example, if an earthquake obliterated the Redmond data center, the administrator needs to change the AGREDXYZCOM DNS entry to point to the Access Gateway servers in Fort Lauderdale This change has no impact on users beyond waiting for their DNS cache to expire NOTE Attention must be paid to the DNS time-to-live values Even though the IP address for the DNS name is changed on the server-side, the locally cached client values must first expire before the client can use the new address IMPORTANT If XYZ is using the global server load-balancing options provided by the Citrix NetScaler Application Switch, the fully qualified domain names on the DNS servers do not need to be reconfigured
Citrix Access Suite 4 Advanced Concepts: The Official Guide
Remote User Access Using Secure Gateway and Access Gateway Advanced Access Control
XYZ uses Secure Gateway and Access Gateway Advanced Access Control to provide secure clientless access to internal applications and web content for all their partners and suppliers To meet the defined recovery objective, the site failover plan that XYZ chose requires them to have identical Secure Gateway and Access Gateway Advanced Access Control environments at each site At each site, the access farm should point only to resources at the specific site For example, the Fort Lauderdale access farm should point only to computers running Presentation Server, Active Directory, and Exchange servers in Fort Lauderdale This configuration step is important, so the access farm does not rely on any resources at the other site If a site failure occurs, everything is contained to one site This approach also requires the XYZ administrators configure each access farm to be identical, including creation of identical roles for all users at both sites Figure 19-24 outlines the setup that XYZ implemented
Internet/ Unsecure Network
First Stage DMZ
Second Stage DMZ
Secure Network
Redmond Secure Gateway Proxy
Remote clients connect to Secure Gateway FQDN
Secure Gateway
Access Farm
Internet/ Unsecure Network
First Stage DMZ
Second Stage DMZ
Secure Network
Fort Lauderdale Remote clients connect to Secure Gateway FQDN Secure Gateway Secure Gateway Proxy Access Farm
Figure 19-24 Remote user connectivity redundancy in XYZ design
19:
Disaster Recovery Planning and Configuration
XYZ uses redundant hardware load balancers at each site For more details about the setup recommendations for the load balancer, reference the section on component redundancy recommendations XYZ distributes the load between the two sites by having users connect to their local site The Secure Gateway FQDN in Fort Lauderdale is SGFTLXYZCOM, while the Redmond one is SGREDXYZCOM The XYZ user population is trained to connect to the site closest to them When setting up the Secure Gateway servers with load balancers, remember to use the proper certificate names All Secure Gateway servers in the Fort Lauderdale site are using a certificate with the same FQDN as the load balancer This configuration is true also for the Redmond site If a site failure occurs, the administrator has to change the FQDN for one site to point to the other If the Fort Lauderdale data center goes down, the administrator has to change the SGFTLXYZCOM DNS entry to the IP address of the load-balanced Secure Gateway servers in Redmond Because XYZ is using only the Navigation User interface on the Access Gateway Advanced Access Control farm, users are not impacted This user interface has no user-specific settings, so users are presented with the same UI, regardless of which side hosts the connection If XYZ was using the Access Center interface, users would notice some changes because their user-specific customizations would not be on the new access farm Users would still have access to all the same information and business tasks, but their background or CDA order might look different NOTE Attention must be paid to the DNS time-to-live values Even though the IP address for the DNS name is changed on the server side, the locally cached client values must first expire before the client uses the new address IMPORTANT If XYZ was using the global server load-balancing options provided by the Citrix NetScaler Application Switch, the fully qualified domain names on the DNS servers do not need to be reconfigured
Copyright © OnBarcode.com . All rights reserved.