The following are the new features in Oracle Traffic Director 11.1.1.9.0:
Support for external health check executables
Oracle Traffic Director now supports a generic health check hook-up mechanism, so that customers can write their own health check programs/scripts to monitor the health of specific origin servers. An external executable is especially useful for a protocol-level health check monitor for the origin servers.
For more information, see Section 14.3.1, "Using an External Health-Check Executable to Check the Health of a Server" in Chapter 14, "Configuring Oracle Traffic Director for High Availability".
Oracle Traffic Director on Oracle Linux Server 6
Oracle Traffic Director can now be installed on Oracle Linux Server release 6. For more information, see Oracle Traffic Director Installation Guide.
Support for custom maintenance page when origin servers offline
Oracle Traffic Director now allows you to serve a custom server pool maintenance response code, and HTML page, when all the back-end servers are detected offline. Providing this type of message is better than having a gateway time-out, or creating other resources to host static content.
For more information, see Chapter 6, "Configuring a Custom Maintenance Page" in Chapter 6, "Managing Origin-Server Pools".
Support for TLS 1.1 and TLS 1.2
Oracle Traffic Director now supports TLS 1.1 and TLS 1.2. This supports the WLS Managed Service use case, where Oracle Traffic Director provides the Load Balancer as a Service role, and acts as the primary SSL termination end point.
For more information, see Chapter 11, "Configuring SSL/TLS Ciphers for a Listener" in Chapter 11, "Managing Security".
HTTP forward proxy support in origin server pools
Oracle Traffic Director now supports an HTTP forward proxy server to be optionally associated with an origin server pool so that all member origin servers of the pool are communicated with via the configured HTTP forward proxy server. This feature supports an environment where access to intended origin servers are restricted through corporate proxy servers.
For more information, see Specifying an HTTP Forward Proxy Server in Chapter 6, "Managing Origin-Server Pools" and the create-origin-server-pool command in Oracle Traffic Director CLI Reference.
High-availability (HA) changes and support for multiple admin users for JaaS
Oracle Traffic Director includes several changes to high-availability (HA) functionality, including removal of a subnetwork restriction wherein the VIP as well as both the primary and the backup nodes have to belong to the same subnet; and, in the keep-alive or persistent connection handling subsystem added support for unicast transmission.
Monitoring enhancements
Oracle Traffic Director includes new monitored attributes for the instance, connection queue, virtual server, and origin server; changes to monitoring of the TCP proxy for SNMP; and a new failover monitoring that contains the statistics of each VIP in the server instance.
For more information, see Appendix A, "Metrics Tracked by Oracle Traffic Director".
Enabling POST keep-alive by default
Oracle Traffic Director now enables POST keep-alive by default (a default of true for always-use-keep-alive) if the origin is Oracle WebLogic Server (WLS).
Solaris IPoIB high availability (HA) support
Oracle Traffic Director can now be configured to provide high availability for IP over InfiniBand (IPoIB) on Solaris. There is no longer a restriction that Oracle Traffic Director must be installed in a global zone to provide high availability for Solaris.
Oracle Traffic Director now monitors the status of origin servers, and displays the status in the origin servers page in the user interface. Oracle Traffic Director can also show status for dynamically discovered origin servers if available and enabled.