3 Network Security

Oracle On Track communicates with external components and components within your own infrastructure. This chapter covers recommendations on how to secure your network environment.

Oracle On Track Communication Channels

Oracle On Track has two communication paths between the client and the server where messages are exchanged to update information. The client-to-server communication is called the Front Channel, and the server-to-client communication is called the Back Channel.

Oracle On Track uses the HTTP-RPC protocol to exchange messages between the client and the server. The client sends RPC messages to the server in serialized JSON or XML format. The server responds to the client using the same method, and can also send notifications to users through email and various desktop notification services such as Growl, GNTP (for Microsoft Windows systems), libnotify (for UNIX systems), and libGrowl (for Apple Mac OS X systems).

The following figure shows an overview of the Oracle On Track communication channels:

The Oracle On Track server implements a caching mechanism that reduces round trips to the database called On Track Object Cache. In a high-availability topology, the caches are cluster-aware and communicate directly with information of stored objects.

Oracle On Track High-Availability Topology

The high-availability topology for Oracle On Track consists of a WebLogic Server cluster in which multiple WebLogic Server instances run simultaneously and work together to provide increased scalability and reliability. A cluster appears to clients to be a single WebLogic Server instance. The server instances that constitute a cluster can run on the same machine, or be located on different machines.

Note:

For more information on clusters, see Oracle Fusion Middleware Using Clusters for Oracle WebLogic Server.

The Oracle On Track architecture consists of several components that communicate with each other on different tiers. The following table shows the interactions of such components and lists the default port they use to communicate:

Table 3-1 Oracle On Track Components Communication Channels

Network Connection From	Network Connection To	Type	Default Port
Oracle WebLogic Server Data Source	Database	SQLNET	1521
Orale WebLogic Server Cluster Node	Oracle WebLogic Server Cluster Node	Oracle WebLogic Server-Based Cluster Communication	No default port.
Oracle On Track Server Cache	Oracle On Track Server Cache	Oracle On Track Cache Cluster Communication	No default port.
Oracle On Track Server Back Channel Router	Oracle On Track Server Back Channel Router	Oracle On Track Back Channel Router Communication	No default port. Oracle recommends to use ports within the range from 49152 - 65535.
Oracle On Track Server	Voice Asterisk Server	Asterisk Channel Communication	The local Asterisk server uses AMI TCP port 5038.
Oracle On Track Server Application Port	Oracle On Track Server	Applications Sharing Port	For media Asterisk server, the port can be configured. But by default, SIP UDP port is 5060 and for RTP random UDP port, a range of ports is configured.

Note:

For application sharing, SRTP access from the proxy to Oracle Fusion Middleware is required. Be sure to add to your proxy a static NAT rule so that the original user's IP address and port would not be rewritten. Application sharing also supports tunneling via standard proxy servers.

Note:

For more information about Oracle WebLogic Server ports, see Oracle Fusion Middleware Administrator's Guide.

For more information on clusters, see Oracle Fusion Middleware Using Clusters for Oracle WebLogic Server.