Bookshelf v7.7: Configuring Firewalls for Use With SSSE

If your SSSE implementation includes firewalls between components, you must open specific ports in the firewall to allow the various parts of the implementation to communicate with each other. This topic briefly describes how to configure your firewall for use with SSSE. This task is a step in Roadmap for Installing SSSE.

Firewall Located Between PIMSI Engine and Exchange Connector

A typical location for a firewall is between a Siebel Server that hosts a PIMSI Engine and a machine that runs the Siebel Exchange Connector. If this is where your firewall is located, have the firewall administrator open the ports listed in Table 10, and configure your Siebel Server to use the same range of ports for DCOM.

Table 10. Ports for a Firewall Located Between PIMSI Engine and Exchange Connector
Traffic Type	Firewall Port to Open
DCOM NOTE: DCOM traffic requires the use of actual IP addresses. Firewalls that translate network addresses prevent proper operation. Therefore, Microsoft does not support DCOM calls that are made over Network Address Translation (NAT)-based firewalls. For more information about using DCOM with firewalls, see http://support.microsoft.com/kb/248809/en-us (Article #248809 on the Microsoft Support Web site).	Port range of your choosing, as described in the Microsoft Developer's Network article called Using Distributed COM with Firewalls (http://msdn2.microsoft.com/en-us/library/ms809327.aspx).
End Point Mapper (EPM)/ Service Control Manager (SCM)	135
LDAP	389
LDAP to Global Catalog Server	3268

Firewall Located Between Exchange Connector and Exchange Server

It is possible (but not recommended) to place a firewall between a machine that runs the Siebel Exchange Connector and the Microsoft Exchange Servers that the Exchange Connector communicates with. In this case, the firewall administrator must open additional ports, such as those as listed in Table 11. On your Siebel Server, be sure to configure corresponding port numbers and port number ranges.

Table 11. Ports for a Firewall Located Between Exchange Connector and Exchange Server
Traffic Type	Firewall Port to Open
End Point Mapper (EPM)/ Service Control Manager (SCM)	135
HTTP	80 or your designated HTTP port
LDAP	389
LDAP to Global Catalog Server	3268
MAPI to Exchange 2000/2003	Values of your choosing, as described in Article #270836 on the Microsoft Support Web site, Exchange Server Static Port Mappings (http://support.microsoft.com/kb/270836/en-us). NOTE: As described in this article, you must create registry entries on the Exchange Server machine that specify static MAPI ports.
RPC (Remote Procedure Calls)	Port range of your choosing, as described in Article #154596 on the Microsoft Support Web site, How to Configure RPC Dynamic Port Allocation to Work with Firewalls (http://support.microsoft.com/kb/154596).