You create an application profile to define the behavior of a particular type of network traffic. After configuring a profile, you associate the profile with a virtual server. The virtual server then processes traffic according to the values specified in the profile. Using profiles enhances your control over managing network traffic, and makes traffic-management tasks easier and more efficient.

When you create a profile for HTTPS traffic, the following HTTPS traffic patterns are allowed:

Client -> HTTPS -> LB (terminate SSL) -> HTTP -> servers

Client -> HTTPS -> LB (terminate SSL) -> HTTPS -> servers

Client -> HTTPS-> LB (SSL passthrough) -> HTTPS -> servers

Client -> HTTP-> LB -> HTTP -> servers


Log in to vCloud Air and navigate to the vCloud Edge Gateway Services UI.

See Log In and Navigate to Advanced Networking Services for information.


Click the Load Balancer tab and Application Profiles.


Click the Add (add icon) icon.

The New Profile dialog box appears.


Type a name for the profile.


(Optional) Configure the following options for the application profile:




Select the way in which you want to send requests to the server—HTTP, HTTPS, TCP, or UDP.

By default, HTTP is selected for the traffic type.

Depending on the type selected, the remaining options in the New Profile dialog are enabled or disabled.

HTTP Redirect URL

(HTTP and HTTPS) Type the URL to which you want to re-direct HTTP traffic. For example, you can direct traffic from to


Specify persistence for the profile. Persistence tracks and stores session data, such as the specific pool member that serviced a client request. This ensures that client requests are directed to the same pool member throughout the life of a session or during subsequent sessions.


The persistence options refresh depending on the type selected.

SOURCEIP persistence tracks sessions based on the source IP address. When a client requests a connection to a virtual server that supports source address affinity persistence, the load balancer checks to see if that client previously connected, and if so, returns the client to the same pool member.

(TPC Only) Microsoft Remote Desktop Protocol (MSRDP) persistence maintains persistent sessions between Windows clients and servers that are running the Microsoft Remote Desktop Protocol (RDP) service. The recommended scenario for enabling MSRDP persistence is to create a load balancing pool that consists of members running Windows Server 2003 or Windows Server 2008, where all members belong to a Windows cluster and participate in a Windows session directory.

Cookie Name

(HTTP and HTTPS) Type the cookie name. Cookie persistence inserts a cookie to uniquely identify the session the first time a client accessed the site and then refers to that cookie in subsequent requests to persist the connection to the appropriate server.


A cookie name is required when you select cookie persistence.


Select the mode by which the cookie should be inserted. The following cookie insertion modes are supported:


The edge gateway sends a cookie. When the server sends one or more cookies, the client will receive one extra cookie (the server cookies plus the edge gateway cookie). When the server does not send any cookies, the client will receive the edge gateway cookie only.


Select this option when your client does not support more than one cookie.


All browsers accept multiple cookies. But you might have a proprietary application using a proprietary client that supports only one cookie. The Web server sends its cookie as usual. The edge gateway injects (as a prefix) its cookie information in the server cookie value. This cookie added information is removed when the edge gateway sends it to the server.

App Session

For this option, the server does not send a cookie; instead, it sends the user session information as a URL. For example,;jsessionid=OI24B9ASD7BSSD, where jsessionid is the user session information and is used for the persistence. It is not possible to see the App Session persistence table for troubleshooting.

Expires in

Enter a length of time in seconds that persistence stays in effect.

Insert X-Forwarded-For HTTP header

(HTTP and HTTPS) Select Insert X-Forwarded-For HTTP header for identifying the originating IP address of a client connecting to a Web server through the load balancer.

Enable Pool Side SSL

(HTTPS Only) Select Enable Pool Side SSL to define the certificate, CAs, or CRLs used to authenticate the load balancer from the server side in the Pool Certificates tab.


(HTTPS Only) Configure the certificates to be used with the application profile:



Virtual Server Certificates

Select the certificate, CAs, or CRLs used to decrypt HTTPS traffic.

Pool Certificates

Define the certificate, CAs, or CRLs used to authenticate the load balancer from the server side.


Select Enable Pool Side SSL to enable this tab.


Select the cipher algorithms (or cipher suite) negotiated during the SSL/TLS handshake.

Client Authentication

Specify whether client authentication is to be ignored or required.


When set to required, the client must provide a certificate after the request or the handshake is canceled.

Add service monitors for the load balancer to define health checks for different types of network traffic. See Create a Service Monitor.