BusinessObjects Enterprise Administrator's Guide

Configuring packet filtering when thick client is separated from the CMS

You can publish reports or analytic objects to BusinessObjects Enterprise by saving these objects to BusinessObjects Enterprise from within Crystal Reports or OLAP Intelligence, or by using the Import or Publishing Wizards. However, if there is a firewall between the computer running one of these thick clients and the CMS, this operation fails.

Configuring your BusinessObjects Enterprise system to support this configuration when the firewall uses packet filtering is very similar to configuring your system to support a packet filtering firewall between the application tier and the Central Management Server (CMS).

For full instructions, follow the detailed steps in Configuring packet filtering when application tier is separated from CMS but:

• Configure only the Central Management Server and the Input File Repository Server to use fixed port numbers for communication.
• Establish inbound firewall rules for communication between the Crystal Reports or OLAP Intelligence machine and the CMS and Input File Repository Server. You do not need to establish an outbound firewall rule.

Related topics:    

• "Changing the default server port numbers" on page 139