Client/Server Resources

Client/server resources are enterprise applications that run over TCP/IP (including applications that use UDP). Examples include thin-client applications such as Citrix; full client/server applications such as Microsoft Outlook; Lotus Notes; SAP; and terminal servers.

You define these types of client/server applications by specifying a host name, an IP address or IP range, a subnet IP address, or a DNS domain. These resources can also be used to define a network object containing multiple Web resources (such as a domain), or to define a network object that can be used to control access based on the source of a connection request.

The below table explains the syntax used to define each of these resource types. Host names can be fully qualified or unqualified.

Resource type syntax

Resource type	Example
Domain	private.example.com
Host name	bart.private.example.com
Host IP address	192.0.34.72
IP range	192.0.34.72 - 192.0.34.74
Subnet	192.0.34.0 / 255.255.255.0

Example

In this example, a Web development team has a single Web server with three virtual Web servers, one for each stage in their development process. Each virtual Web server listens on a different port.

Rather than creating three different URL resources, the Web development team can define the Web server, which proxies traffic on all ports, as a resource type of Host name or IP (for example, webdev.yourcompany.com). In addition, they attach a single sign-on Web application profile to it, and now all three of the virtual Web servers are defined at once, and they share the same SSO profile:

webdev.yourcompany.com

webdev.yourcompany.com:8080

webdev.yourcompany.com:8443

Microsoft Outlook connects to Microsoft Exchange using an unqualified host name. When defining a Microsoft Exchange server as a resource, define it as an unqualified name (for example, CorpMail).

To use Exchange on Android or iOS devices, create a URL resource of the type ActiveSync for Exchange.