4 HTTP Access and Secure Sockets Layer

HTTP access is the primary way Web applications communicate with a server. Oracle On Track uses an additional level of security by using the Secure Sockets Layer (SSL) protocol to encrypt Front-Channel and Back-Channel communications. This chapter covers the required configurations to enable SSL and lists the connections from different components that connect using this protocol.

Configuring SSL for Oracle WebLogic Server

Oracle On Track requires the SSL protocol to be enabled in production mode. In Oracle WebLogic Server, SSL is disabled by default. For more information about how to configure and enable SSL in WebLogic Server, see Oracle Fusion Middleware Securing Oracle WebLogic Server.

List of SSL Connections

The following table shows a list of On Track SSL connections to other components:

Table 4-1 Oracle On Track SSL Connections

Network Connection From	Network Connection To	SSL-enabled?	Defaul Port
Oracle On Track Client	Oracle On Track Server	Yes	443
Oracle On Track Server (Cluster instance)	Oracle On Track Server (Cluster instance)	No	No default port
Oracle On Track Server (Cluster Instance)	Oracle On Tack Object Cache (Cluster Instance)	No	No default port
Oracle On Track Server	LDAP Server	No (default). To enable, See Oracle On Track Administration Console Online Help.	389 (Non-SSL). 636 (SSL)
Oracle On Track Server	Oracle Database 11g, Oracle Real Clusters Application	No (default). To enable, see How To Configure and User Oracle JDBC Driver SSL with Oracle WebLogic Server.	1521
Oracle On Track Client	Oracle On Track Application sharing	No. Uses SRTP protocol for increased security, but optimized for RTP low latency.	9001
Oracle On Track Server	Asterisk Server	No	5060