Firewalls › Examples of Typical Firewall Scenarios › Example - Rich Client and Database Tier Separated From BusinessObjects Enterprise Servers by a Firewall › Configure Tiers Separated from BusinessObjects Enterprise Servers by a Firewall

Configure Tiers Separated from BusinessObjects Enterprise Servers by a Firewall

To configure tiers separated from BusinessObjects Enterprise servers by a firewall

1. Apply the following communication requirements to this example:
   • The Publishing Wizard must be able to initiate communication with the CMS on both of its ports.
   • The Publishing Wizard must be able to initiate communication with the Input File Repository Server and the Output File Repository Server.
   • The Connection Server, every Job Server child process, and every Processing Server must have access to the listen port on the reporting database server.
   • The CMS must have access to the database listen port on the CMS database server.
2. Configure a specific port for the CMS, the Input FRS, and the Output FRS. Note that you can use any free port between 1,025 and 65,535.

   The port numbers chosen for this example are listed here:

   Central Management Server

   6411

   Input File Repository Server

   6415

   Output File Repository Server

   6416

3. We do not need to configure a port range for the Job Server children because the firewall between the job servers and the database servers is configured to allow any port to initiate communication.
4. Configure Firewall_1 to allow communication to the fixed ports on the BusinessObjects Enterprise servers that you configured in the previous step. Note that port 6400 is the default port number for the CMS Name Server Port and did not need to be explicitly configured in the previous step.

Configure Firewall_2 to allow communication to the database server listen port. The CMS (on boe_2) must have access to the CMS database and the Job Servers (on boe_3) must have access to the reporting database. Note that we did not have configure a port range for job server child processes because their communication with the CMS did not cross a firewall.

1. This firewall is not NAT-enabled, so the hosts file does not need to be configured.