Siebel Deployment Planning Guide > Siebel Infrastructure Planning >

Determining Network Requirements

This task is a step in Process of Infrastructure Planning.

The purpose of this infrastructure planning task is to identify the network requirements needed to support the Siebel deployment.

To determine network requirements

1. Use the information about average and peak workloads to verify that there is sufficient network bandwidth to handle network traffic to and from, as well as within, the Siebel deployment.
2. Determine whether to use data encryption. If so, then define data encryption policies. Then add data encryption protocols to the deployment plans that you outlined using Mapping Siebel Deployment Elements to Platforms.
3. Define firewall requirements. If you are creating a network DMZ, then also define the requirements for proxy servers and other items that you install in the DMZ.

   Include network address translation (NAT) and HTTPS requirements.

4. Analyze interactions and dependencies between networking components.

   For example, assume that you use HTTP with TLS (Transport Layer Security) between browsers and Siebel Application Interfaces.

5. Select port numbers for all of the network components that listen on TCP ports.

   This includes Siebel Application Interface, Siebel Servers, and server clusters. For a full description of Siebel Server components that require a port number assignment, see Siebel System Administration Guide. See also the Siebel Installation Guide for the operating system you are using.

   The default TCP port number for Siebel Application Interface-to-Siebel Server traffic is 3320. This is the port number of the Siebel Connection Broker (SCBroker); however, you can configure the port number. You cannot assign the Siebel Gateway and Siebel Servers port numbers higher than 32767.

   Also, verify that firewalls are configured to communicate with the correct TCP ports.

6. Consider any other factors that might affect networking connectivity.