![]() ![]() ![]() ![]() ![]() ![]() ![]() |
This document summarizes the tasks required to install and configure a multiple-server installation of WebLogic SIP Server. It is intended for users who are already familiar with WebLogic Server installation and configuration, or for users who want to quickly set up a multiple-server configuration for demonstration or evaluation. If you are unfamiliar with installing BEA products or you want to perform automated or non-graphical installations, see Installing WebLogic SIP Server instead.
This document contains the following sections:
The quick-start installation involves performing the following steps:
The WebLogic SIP Server software must be available on all server machines that will run a WebLogic SIP Server instance. Follow these steps for the Administration Server machine and for all other machines that will run a Managed Server:
chmod a+x ./sipserver310_linux32.bin
./sipserver310_linux32.bin
(Substitute the appropriate filename for the installation program you have obtained.)
To launch the generic JAR file installation:
See Installing WebLogic SIP Server for more information about using the installation program.
All related WebLogic SIP Server instances must be members of the same administrative domain. The Configuration Wizard provided with WebLogic SIP Server contains several templates to help you create different types of domains. The templates are provides as JAR files in the WLSS_HOME
/common/templates/domains
directory. Table 2-1 describes the available templates.
Follow these steps to install a new WebLogic SIP Server domain:
cd ~/bea/sipserver31 /common/bin
./config.sh
replicateddomain.jar
, and click OK.
The WebLogic SIP Server instances you intend to use must be created within a single administrative domain, and servers in the engine and data tiers should be arranged into clusters to simplify deployment and management. If you used the Configuration Wizard to create a replicated WebLogic SIP Server domain, the domain is automatically created with default engine tier servers and data tier servers arranged into clusters; you can modify this configuration to match the number of servers you want to use in your domain. See Modifying the Default Replicated Domain.
If you used the Configuration Wizard with the sipserverdomain.jar
template, only a single server is configured. You will need to create engine and data tier servers and clusters by hand.
WARNING: | When you configure a domain with multiple engine and data tier servers, you must accurately synchronize all server system clocks to a common time source (to within one or two milliseconds) in order for the SIP protocol stack to function properly. See Configuring NTP for Accurate SIP Timers in the Configuration Guide for more information. |
The default replicated WebLogic SIP Server domain is preconfigured with five separate servers and two clusters.
You may want to modify the default replicated domain if you want to add, remove, or rename servers in either of the clusters, or to configure the network settings of individual server instances. To modify the default configuration:
cd c:\bea\user_projects\domains\replicated
startWebLogic.cmd
Note: | These quick-start instructions assume each managed server listens on a single network address. If you intend to run servers on multi-homed server hardware, or if you want to configure secure SIP transport protocols, see in Configuring Network Resources. |
In the previous section you organized the data tier servers into a cluster for administration purposes. You must also configure the datatier.xml
file to define how data tier servers are used to manage SIP application call state for your installation.
The data tier cluster can be arranged into one or more partitions. A partition consists of one or more data tier server instances that manage the same portion of the concurrent call state data. In a single-server WebLogic SIP Server installation, or in a two-server installation where one server resides in the engine tier and one resides in the data tier, all call state data is maintained in a single partition. Multiple partitions are required when the size of the concurrent call state exceeds the maximum size that can be managed by a single server instance. In most cases, the amount of call state that can be managed by a server corresponds to the Java Virtual Machine limit of approximately 1.6GB per server.
Additional servers can also be added within the same partition to manage copies of the call state data. When multiple servers are part of the same partition, each server manages a copy of the same portion of the call data, referred to as a replica of the call state. If any server in a partition fails or cannot be contacted due to a network failure, another replica in the same partition can supply the call state data to the engine tier.
Before modifying datatier.xml
, read
Configuring Data Tier Partitions and Replicas in the Configuration Guide to fully understand the role of the data tier and the format of the datatier.xml
configuration file.
To modify datatier.xml
for your domain:
datatier.xml
configuration file with a text editor. This file is part of the sipserver
application that provides WebLogic SIP Server functionality, installed in the top level of your domain directory:cd c:\bea\user_projects\domains\replicated\config\custom
notepad datatier.xml
If you installed the default replicated domain, the datatier.xml
file contains the entries shown in Listing 2-1, which defines a single partition with two replicas.
<?xml version="1.0" encoding="UTF-8"?>
<data-tier xmlns="http://www.bea.com/ns/wlcp/wlss/300">
<partition>
<name>partition-0</name>
<server-name>replica1</server-name>
<server-name>replica2</server-name>
</partition>
</data-tier>
To start the fully-configured WebLogic SIP Server domain, first start the Administration Server, then start individual Managed Servers to connect to the Administration Server. The sections that follow provide server startup instructions.
To start the Administration Server:
Note: | WebLogic SIP Server start scripts use default values for many JVM parameters that affect performance. For example, JVM garbage collection and heap size parameters may be omitted, or may use values that are acceptable only for evaluation or development purposes. In a production system, you must rigorously profile your applications with different heap size and garbage collection settings in order to realize adequate performance. See Tuning JVM Garbage Collection for Production Deployments in the Configuration Guide for suggestions about maximizing JVM performance in a production domain. |
To start the Managed Servers in your domain:
mkdir c:\myManagedServer
cd c:\myManagedServer
Note: | The Managed Server machines do not have a domain directory. Instead, they obtain their configuration by connecting to the Administration Server at startup. |
\common\bin
directory:WLSS_HOME\common\bin
\startManagedWebLogic.cmd server_name admin_url
After booting your domain, you may want to perform further administration procedures such as configuring network resources, enabling logging, or setting up security providers. For more information on these topics, see the Configuration Guide.
![]() ![]() ![]() |