Siebel Deployment Planning Guide > Application-Level Deployment Planning >

Session Communications Deployment Planning

Generally, you run Siebel Communications Server components for session communications, such as CommSessionMgr, on the same Siebel Server computers as those running Application Object Managers. In some cases, however, you must run CommSessionMgr on a different computer than the Application Object Managers. These options are described in detail, as follows.

CTI middleware generally runs on servers located at each contact center facility.

Running CommSessionMgr on Application Object Manager Computers

Generally, you run Siebel Communications Server components for session communications on the same Siebel Server computers as those running Application Object Managers. Such a topology allows the Application Object Manager load balancing mechanism to indirectly balance Communications Server load. CommSessionMgr loads are fairly light and do not, in themselves, present a reason to run this component on dedicated computers.

Set the Enable Communication parameter to True for all of the Application Object Managers to which your agents connect. If you use load balancing, then configure all of the Application Object Managers to which requests are distributed in the same way.

Running CommSessionMgr on Dedicated Computers

Sometimes you must run CommSessionMgr on a different computer than the Application Object Manager components.

CommSessionMgr must run on the same computer where the communications driver for your CTI middleware is running. If your driver requires a particular operating system, then you must install Siebel Server and run CommSessionMgr on a computer with that operating system. Communications drivers must be able to run on one of the supported Siebel Server platforms, as described in My Oracle Support Certifications.