Manual Chapter :
Configuring Virtual Servers for Portal Access
Applies To:
Show Versions
BIG-IP APM
- 15.0.1, 15.0.0, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.0.1, 14.0.0
Configuring Virtual Servers for Portal Access
Defining a virtual server for portal access
You associate an access policy and a rewrite profile with the virtual server, to allow
portal access in an access policy.
For portal access, a virtual server for
an access policy, specify an IP address for a single host as the destination address.
- On the Main tab, click.The Virtual Server List screen opens.
- Click the name of the virtual server you want to modify.
- In theDestination Address/Maskfield, type the IP address for a host virtual server.This field accepts an address in CIDR format (IP address/prefix). However, when you type the complete IP address for a host, you do not need to type a prefix after the address.
- From theHTTP Profilelist, selecthttp.
- In the Access Policy area, from theAccess Profilelist, select the access profile that you configured earlier.
- To use GZIP compression with a portal access resource, from theHTTP Compression Profilelist, selecthttpcompression.
- If you are using a connectivity profile, from theConnectivity Profilelist, select the connectivity profile.
- If you are creating a virtual server to use with portal access resources in addition to remote desktops, from theRewrite Profilelist, select the defaultrewriteprofile, or another rewrite profile you created.
- If you use client SSL for this profile, from theSSL Profile (Client)list, select a client SSL profile.
- If you are using HTTPS with any portal access pages, from theSSL Profile (Server)list, selectserverssl-apm.
- If you want to provide connections to Java RDP clients for application access, allow Java rewriting for portal access, or support a per-app VPN connection that is configured on a mobile device, select theApplication Tunnels (Java & Per-App VPN)check box.You must enable this setting to make socket connections from a patched Java applet. If your applet does not require socket connections, or only uses HTTP to request resources, this setting is not required.
- If you want to provide native integration with an OAM server for authentication and authorization, select theOAM Supportcheck box.You must have an OAM server configured in order to enable OAM support.
- ClickUpdate.
Your access policy is now associated with the virtual server.