Configuring SIP Data Tier Partitions and Replicas 4-17
7. Select a JDK to use, and click Next.
8. Select No to keep the settings defined in the source template file, and click Next.
9. Click Create to create the domain.
The template creates a new domain with two engine tier servers in a cluster, two SIP data tier servers in a cluster, and an Administration Server AdminServer. The
engine tier cluster includes the following resources and configuration:
■
A JDBC datasource, wlss.callstate.datasource, required for storing long-lived call state data. If you want to use this functionality, edit the
datasource to include your RDBMS connection information as described in Section 4.4.3.1, Modify the JDBC Datasource Connection Information
.
■
A persistence configuration shown in the SipServer node, Configuration Persistence tab of the Administration Console that defines:
– Default handling of persistence hints for both RDBMS and geographical
redundancy.
– A Geo Site ID of 2.
■
A JMS system module, SystemModule-Callstate, that includes:
– ConnectionFactory-Callstate, a connection factory required for
backing up call state data from a primary site.
– DistributedQueue-Callstate, a uniform distributed queue required
for backing up call state data from a primary site. The JMS system module is targeted to the sites engine tier cluster
■
Two JMS Servers, JMSServer-1 and JMSServer-2, are deployed to engine1-site2 and engine2-site2, respectively.
10. Click Done to exit the configuration wizard.
4.6.5 Manually Configuring Geographical Redundancy
If you have an existing replicated Oracle WebLogic Server SIP Container installation, or pair of installations, you must create by hand the JMS and JDBC resources required
for enabling geographical redundancy. You must also configure each site to perform replication. These basic steps for enabling geographical redundancy are:
1.
Configure JDBC Resources. Oracle recommends configuring both the primary and secondary sites to store long-lived call state data in an RDBMS.
2.
Configure Persistence Options. Persistence options must be configured on both the primary and secondary sites to enable engine tier hints to write to an RDBMS or to
replicate data to a geographically-redundant installation.
3.
Configure JMS Resources. A secondary site must have available JMS Servers and specific JMS module resources in order to replicate call state data from another
site.
The sections that follow describe each step in detail.
4.6.5.1 Configuring JDBC Resources Primary and Secondary Sites
Follow the instructions in Section 4.4, Storing Long-Lived Call State Data In A
RDBMS to configure the JDBC resources required for storing long-lived call states in
an RDBMS.
4-18 Oracle WebLogic SIP Server Container Administrators Guide
4.6.5.2 Configuring Persistence Options Primary and Secondary Sites
Both the primary and secondary sites must configure the correct persistence settings in order to enable replication for geographical redundancy. Follow these steps to
configure persistence:
1. Use your browser to access the URL http:address:portconsole where address is
the Administration Servers listen address and port is the listen port.
2. Click Lock Edit to obtain a configuration lock.
3. Select the SipServer node in the left pane. The right pane of the console provides
two levels of tabbed pages that are used for configuring and monitoring Oracle WebLogic Server SIP Container.
4. Select the Configuration Persistence tab in the right pane.
5. Configure the Persistence attributes as follows:
■
Default Handling : Select all to persist long-lived call state data to an
RDBMS and to replicate data to an external site for geographical redundancy recommended. If your installation does not store call state data in an
RDBMS, select geo instead of all.
■
Geo Site ID : Enter a unique number from 1 to 9 to distinguish this site from
all other configured sites. Note that the site ID of 0 is reserved to indicate call states that are local to the site in question call states not replicated from
another site.
■
Geo Remote T3 URL : For primary sites or for secondary sites that replicate
their own data to another site, enter the T3 URL or URLs of the engine tier servers that will replicate this sites call state data. If the secondary engine tier
cluster uses a cluster address, you can enter a single T3 URL, such as t3:mycluster:7001. If the secondary engine tier cluster does not use a cluster
address, enter the URLs for each individual engine tier server separated by a comma, such as
t3:engine1-east-coast:7001,t3:engine2-east-coast:7002,t3:engine3-east-c oast:7001,t4:engine4-east-coast:7002.
6. Click Save to save your configuration changes.
7. Click Activate Changes to apply your changes to the engine tier servers.
4.6.5.3 Configuring JMS Resources Secondary Site Only
