Goals of the Oracle WebLogic Communication Services Base Platform Load Balancer

16 Deployment Topologies for Communication Services 16-1 16 Deployment Topologies for Communication Services This chapter describes the OWLCS deployment topologies in the following sections: ■ Section 16.1, Terminology ■ Section 16.2, OWLCS Deployment Topologies ■ Section 16.3, Oracle WebLogic Communication Services Enterprise Deployment Topology

16.1 Terminology

The following terms are used in this chapter: ■ Administration Server--a special server instance within a domain to configure and manage all resources in the domain. There is just one Administration Server in a domain. ■ Domain--a logically related group of server resources ■ High Availability HA--refers to a system or component that is continuously operational for a desirable long length of time ■ JVM--Java Virtual Machine ■ Managed Server--a server instance within a domain where resources are deployed. There can be one or more managed servers within a domain. ■ Node--a physical machine ■ OWLCS Client--a client application that can connect to OWLCS server and use it’s features -Presence, Instant Messaging IM, VoIP, Presence Web Service, and Messaging Web Service. For example: Oracle Communicator.

16.2 OWLCS Deployment Topologies

OWLCS supports single-node and multi-node deployment topologies: ■ All-In-One Managed Server--All OWLCS components are deployed on a Managed Server within a domain on a physical machine. An Administration Server installed on the same domain is used to configure and manage OWLCS components. 16-2 Oracle WebLogic Communications Server Administration Guide Figure 16–1 All-in-One Managed Server See Section 16.2.1, Single-node Topologies for more information. ■ All-In-One Administration Server--All OWLCS components are deployed on an Administration Server within a domain on a physical machine. There are no managed servers. Configuration and management of OWLCS components is done using the same Administration Server. Deployment Topologies for Communication Services 16-3 Figure 16–2 All-in-One Administration Server See Section 16.2.1, Single-node Topologies for more information. ■ Enterprise Deployment--This is the minimal recommended HA topology for Enterprise Deployment for OWLCS. OWLCS components are separated as SIP Infrastructure, Services and Presence components. Each group of components is deployed within its own domain on two different machines. Figure 16–3 Enterprise Deployment See Section 16.3.1, Introduction to OWLCS Enterprise Deployment Topology for more information.