Configuring Client-Side Appliances and Client Accelerator Endpoints : Configuring client-side appliances
  
Configuring client-side appliances
1. Choose Configure > Client Appliances, and then copy the registration token.
2. Go to the appliance and log in to its Management Console.
3. Choose Optimization > SaaS: SaaS Accelerator and add these values:
– SaaS Accelerator Manager Hostname.
– SaaS Accelerator Manager Port. The client-side appliance uses port 3900 from the primary interface to communicate with SAM and the port needs to be open on the branch firewall. The field for the port number is editable but we recommend not changing the value.
– Registration Token. Paste the registration token you copied in the previous step into this field.
4. Click Register.
5. Enable SSL or TLS optimization on the appliance. For appliances running version 9.14.1 and later, TLS replaces SSL.
– Choose Optimization > SSL/TLS Main Settings.
– In the General SSL/TLS Settings section, select Enable SSL/TLS Optimization and click Apply.
6. In SAM, move this appliance to the whitelist. Newly added appliances always appear on the graylist in the Access List column. You need to move their status to the whitelist to allow acceleration.
– Choose Configure > SaaS Apps: Client Appliances, and then select the appliance serial number to display the details pane.
– Under Access List, select Whitelist from the Access list drop-down list and click Submit. For more information, see About registering client-side appliances.
7. Enable SaaS acceleration on this client-side appliance.
– Choose Optimization > SaaS: SaaS Accelerator.
– Select Enable Acceleration, and click Apply.
8. Optionally, enable proxy chaining interoperability. See Enabling and disabling proxy chaining on client-side appliances.
9. Add an in-path rule to accelerate SaaS applications. See Configuring in-path rules on client-side appliances. For more information about in-path rules, see the SteelHead User Guide.
10. Save your changes.
11. Verify the configuration by generating SaaS traffic. For details about monitoring the first connections, see Monitoring initial SaaS traffic.