Firewalls › Understand Communication Between BusinessObjects Enterprise Components › Communication Between BusinessObjects Enterprise Components › Requirements for Communication Between BusinessObjects Enterprise Components

Requirements for Communication Between BusinessObjects Enterprise Components

Deployments of BusinessObjects Enterprise must conform to these general requirements.

1. Every BusinessObjects Enterprise server must be able to initiate communication with every other BusinessObjects Enterprise server on that server's Request Port.
2. The CMS uses two ports. Every BusinessObjects Enterprise server, BusinessObjects Enterprise rich client, and the web application server that hosts the BusinessObjects Enterprise SDK must be able to initiate communication with the CMS on both of its ports.
3. Every job server child process must be able to initiate communication with the CMS on both of its ports.
4. Rich clients must be able to initiate communication with the Request Port of the Input and Output File Repository Servers.
5. If Web Intelligence rich clients use Auditing, they must be able to initiate communication with the Request Port of the Adaptive Processing Servers that hosts the Client Auditing Proxy Service.
6. In general, the web application server that hosts the BusinessObjects Enterprise SDK must be able to initiate communication with the Request Port of every BusinessObjects Enterprise server.

   Note: The web application server only needs to communicate with BusinessObjects Enterprise servers that are used in the deployment. For example, if Crystal Reports is not being used, the web application server does not need to communicate with the Crystal Reports Processing Servers.

7. Job Servers use the port numbers that are specified with the -requestJSChildPorts <port range> command. If no numbers are specified in the command line, the servers use random port numbers. To allow a job server to communicate with an FTP or mail server on another computer either open all of the ports in the range specified by -requestJSChildPorts on your firewall, or add the job server child process as an exception for your firewall.
8. The CMS must be able to initiate communication with the CMS database listen port.
9. The Connection Server, most Job Server child process, and every Processing Server must be able to initiate communication with the reporting database listen port. Each database vendor uses a different listen port. For example, MySQL uses 3306 by default.