Siebel Server Sync Guide > Installing Siebel Server Sync for Microsoft Exchange Server >

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.

The appropriate placement of firewalls varies depending on the type of Exchange Connector that you are using in your Siebel deployment to communicate with Microsoft Exchange. Regardless of the type of Exchange Connector used, however, a firewall is likely to exist between the Exchange Connector host and the Microsoft Exchange Server host.

Firewall Between PIMSI Engine and Exchange Server 2010 Host

If a firewall is located between the Siebel Server that hosts a PIMSI Engine and the Microsoft Exchange Server host that the Web service Exchange Connector communicates with, then ask the firewall administrator to open ports for HTTP or HTTPS traffic as appropriate. Generally port 80 is used for HTTP traffic, and port 443 is used for HTTPS traffic.

Firewall Between PIMSI Engine and DCOM Exchange Connector

If you are using Microsoft Exchange Server 2007, a typical location for a firewall is between a Siebel Server that hosts a PIMSI Engine and a computer that runs the Siebel DCOM Exchange Connector. If this is where your firewall is located, have the firewall administrator open the ports listed in Table 8, and configure your Siebel Server to use the same range of ports for DCOM.

Table 8. Ports for a Firewall Located Between PIMSI Engine and DCOM Exchange Connector
Traffic Type
Firewall Port to Open

DCOM

DCOM traffic requires the use of 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, go to the Microsoft Support Web site at the following URL

http://support.microsoft.com

Any available port

 

End Point Mapper (EPM)/ Service Control Manager (SCM)

135

LDAP

389

LDAP to Global Catalog Server

3268

Firewall Between DCOM Exchange Connector and Exchange Server

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

Table 9. Ports for a Firewall Between DCOM Exchange Connector and Microsoft Exchange Server
Traffic Type
Firewall Port to Open

End Point Mapper (EPM)/ Service Control Manager (SCM)

135

HTTP

80 or your designated HTTP port

HTTPS

443 or your designated HTTPS port

LDAP

389

LDAP to Global Catalog Server

3268

MAPI to Exchange 2007

 

Create registry entries on the Exchange Server computer that specify static MAPI ports. For information on configuring Exchange Server static port mappings, see the following URL

http://support.microsoft.com

RPC (Remote Procedure Calls)

Port range of your choosing, as described in Article #154596, How to Configure RPC Dynamic Port Allocation to Work with Firewalls, on the Microsoft Support Web site at the following URL

http://support.microsoft.com/kb/154596

Siebel Server Sync Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.