Configuring JMS Resources Secondary Site Only

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

Any site that replicates call state data from another site must configure certain required JMS resources. The resources are not required for sites that do not replicate data from another site. Follow these steps to configure JMS resources: 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 Services Messaging JMS Servers tab in the left pane.

4. Click New in the right pane.

5. Enter a unique name for the JMS Server or accept the default name. Click Next to

continue. 6. In the Target list, select the name of a single engine tier server node in the installation. Click Finish to create the new Server. Configuring SIP Data Tier Partitions and Replicas 4-19 7. Repeat Steps 3-6 for to create a dedicated JMS Server for each engine tier server node in your installation.

8. Select the Services Messaging JMS Modules node in the left pane.

9. Click New in the right pane.

10. Fill in the fields of the Create JMS System Module page as follows: ■ Name : Enter a name for the new module, or accept the default name. ■ Descriptor File Name : Enter the prefix a configuration file name in which to store the JMS module configuration for example, systemmodule-callstate.

11. Click Next to continue.

12. Select the name of the engine tier cluster, and choose the option All servers in the

cluster . 13. Click Next to continue.

14. Select Would you like to add resources to this JMS system module and click

Finish to create the module. 15. Click New to add a new resource to the module.

16. Select the Connection Factory option and click Next.

17. Fill in the fields of the Create a new JMS System Module Resource as follows: ■ Name : Enter a descriptive name for the resource, such as ConnectionFactory-Callstate. ■ JNDI Name : Enter the name wlss.callstate.backup.site.connection.factory. 18. Click Next to continue.

19. Click Finish to save the new resource.

20. Select the name of the connection factory resource you just created.

21. Select the Configuration Load Balance tab in the right pane.

22. De-select the Server Affinity Enabled option, and click Save.

23. Re-select the Services Messaging JMS Modules node in the left pane.

24. Select the name of the JMS module you created in the right pane.

25. Click New to create another JMS resource.

26. Select the Distributed Queue option and click Next.

27. Fill in the Name field of the Create a new JMS System Module Resource by

entering a descriptive name for the resource, such as DistributedQueue-Callstate.

28. JNDI Name

: Enter the name Fill in the fields of the Create a new JMS System Module Resource as follows: ■ Name : Enter a descriptive name for the resource, such as ConnectionFactory-Callstate. ■ JNDI Name : Enter the name wlss.callstate.backup.site.queue. 29. Click Next to continue. 30. Click Finish to save the new resource. 4-20 Oracle WebLogic SIP Server Container Administrators Guide

31. Click Save to save your configuration changes.

32. Click Activate Changes to apply your changes to the engine tier servers.

4.6.6 Understanding Geo-Redundant Replication Behavior