This figure shows the Oracle BI EE components in a single instance architecture. Java and system components communicate over HTTP. Components are represented by boxes, while databases are represented by discs. Arrows shows the path and direction of information between boxes.

HTTP Web server is connected to the SAW Protocol, which contains the Java EE Server (Weblogic) and a Webcontainer holding the BI Presentation (something) Plug-in (Java Servelet). The same HTTP Web server also connects to Oracle BI Web Client via HTTP(s).

The SAW Protocol is connected to the Oracle BI Presentation Services through port 9710. The Oracle BI Presentation Services has 8 outbound lines and one inbound line.

Each of the 8 outbound lines terminates at a Server or Service. The path of each line is as follows:

The inbound line is a SAW protocol that connects the Oracle BI Scheduler back to the Oracle BI Presentation Services at port 9710.

The Primary Cluster Controller Server connects to the Oracle BI Server at port 9701 and the Secondary Cluster Controlnet Server at port 9700, and the Oracle BI Scheduler at port 9706.

The Secondary Cluster Controlnet Server connects to the Oracle BI Server at 9701, the Primary Cluster Controller Server at port 9700, and the Oracle BI Scheduler at port 9706.

The Oracle BI Server connects to Security Service through HTTP(s), the Oracle BI Repository, and Data Sources through ODBC or Native Database Protocol. It also connects to the Oracle BI Administration Tool, which connects to the Scheduler Job Manager, which connects to the Oracle BI Scheduler through Sch Protocol at port 9705.

The Oracle BI Scheduler is connected to SMPT Server (for Deliveries), Oracle BI Presentation Services via SAW Protocol at port 9710, BI JavaHost at port 9910, and Data Sources through ODBC or Native Database Protocol.