|
|
The following sections provide an overview of how to configure and manage WebLogic SIP Server deployments:
WebLogic SIP Server is based on the award-winning WebLogic Server 9.2 application server, and many system-level configuration tasks are the same for both products. This manual addresses only those system-level configuration tasks that are unique to WebLogic SIP Server, such as tasks related to network and security configuration and cluster configuration for the engine and data tiers.
HTTP server configuration and other basic configuration tasks such as server logging are addressed in the WebLogic Server 9.2 Documentation.
The SIP Servlet container, data tier replication, and Diameter protocol features of WebLogic SIP Server are implemented in the WebLogic Server 9.2 product as custom resources. A pair of custom resources, sipserver and datatier, implement the engine tier SIP Servlet container functionality and data tier replication functionality. In production deployments, both resources are generally installed. Specialized deployments may use only the sipserver resource in conjunction with a SIP-aware load balancer, as described in
Alternate Configurations.
Another custom resource, diameter, provides Diameter base protocol functionality, and is required only for deployments that utilize one or more Diameter protocol applications.
The WebLogic SIP Server custom resource assignments are visible in the domain configuration file, config.xml, and should not be modified. Listing 2-1 shows the definitions for each resource. Note that the sipserver and datatier resources must each be targeted to the same servers or clusters; in Listing 2-1, the resources are deployed to both the engine tier and data tier cluster.
<custom-resource>
<name>sipserver</name>
<target>BEA_DATA_TIER_CLUST,BEA_ENGINE_TIER_CLUST</target>
<descriptor-file-name>custom/sipserver.xml</descriptor-file-name>
<resource-class>com.bea.wcp.sip.management.descriptor.resource.SipServerResource</resource-class>
<descriptor-bean-class>com.bea.wcp.sip.management.descriptor.beans.SipServerBean</descriptor-bean-class>
</custom-resource>
<custom-resource>
<name>datatier</name>
<target>BEA_DATA_TIER_CLUST,BEA_ENGINE_TIER_CLUST</target>
<descriptor-file-name>custom/datatier.xml</descriptor-file-name>
<resource-class>com.bea.wcp.sip.management.descriptor.resource.DataTierResource</resource-class>
<descriptor-bean-class>com.bea.wcp.sip.management.descriptor.beans.DataTierBean</descriptor-bean-class>
</custom-resource>
<custom-resource>
<name>diameter</name>
<target>BEA_ENGINE_TIER_CLUST</target>
<deployment-order>200</deployment-order>
<descriptor-file-name>custom/diameter.xml</descriptor-file-name>
<resource-class>com.bea.wcp.diameter.DiameterResource</resource-class>
<descriptor-bean-class>com.bea.wcp.diameter.management.descriptor.beans.ConfigurationBean</descriptor-bean-class>
</custom-resource>
The WebLogic SIP Server custom resources utilize the basic domain resources defined in config.xml, such network channels, cluster and server configuration, and J2EE resources. However, WebLogic SIP Server-specific resources are configured in separate configuration files based on functionality:
sipserver.xml configures SIP container properties and general WebLogic SIP Server engine tier functionality.datatier.xml identifies servers that participate as replicas in the data tier, and also defines the number and layout of data tier partitions.diameter.xml configures Diameter nodes and Diameter protocol applications used in the domain.
Keep in mind that the domain configuration file, config.xml, defines all of the Managed Servers available in the domain. The sipserver.xml, datatier.xml, and diameter.xml configuration files included in the sipserver application determines the role of each server instance, such as whether they behave as data tier replicas, engine tier nodes, or Diameter client nodes.
Configuration changes to SIP Servlet container properties can be applied dynamically to a running server by using the Administration Console SIP Servers node or from the command line using the WLST utility. Configuration for data tier nodes cannot be changed dynamically, so you must reboot data tier servers in order to change the number of partitions or replicas.
The Diameter protocol implementation is implemented as a custom resource separate from the SIP Servlet container functionality. The Diameter configuration file configures one or more Diameter protocol applications to provide Diameter node functionality. WebLogic SIP Server provides the Diameter protocol applications to support the following node types:
The Diameter custom resource is deployed only to domains having servers that need to act as Diameter client nodes or relay agents, or to servers that want to provide HSS simulation capabilities. The actual function of the server instance depends on the configuration defined in the diameter.xml file.
See Configuring Diameter Client Nodes and Relay Agents in Configuring Network Resources for instructions to configure the Diameter Web Application in a WebLogic SIP Server domain. See Using the IMS Sh Interface (Diameter) in Developing Applications with WebLogic SIP Server for more information about using the Sh profile API.
WebLogic SIP Server provides several mechanisms for changing the configuration of the SIP Servlet container:
WebLogic SIP Server provides Administration Console extensions that allow you to modify and SIP Servlet container, SIP Servlet domain, and Diameter configuration properties using a graphical user interface. The Administration Console extensions for WebLogic SIP Server are similar to the core console available in WebLogic Server 9.2. All WebLogic SIP Server configuration and monitoring is provided via these nodes in the left pane of the console:
The WebLogic Scripting Tool (WLST) enables you to perform interactive or automated (batch) configuration operations using a command-line interface. WLST is a JMX tool that can view or manipulate the MBeans available in a running WebLogic SIP Server domain. Configuring Engine Tier Container Properties provides instructions for modifying SIP Servlet container properties using WLST.
Most WebLogic SIP Server configuration is performed using either the Administration Console or WLST. The methods described in the following sections may also be used for certain configuration tasks.
You may also edit sipserver.xml, datatier.xml, and diameter.xml by hand, following the respective schemas described in the Configuration Reference Manual.
If you edit configuration files by hand, you must manually reboot all servers to apply the configuration changes.
WebLogic SIP Server properties are represented by JMX-compliant MBeans. You can therefore program JMX applications to configure SIP container properties using the appropriate WebLogic SIP Server MBeans.
The general procedure for modifying WebLogic SIP Server MBean properties using JMX is described in Configuring Container Properties Using WLST (JMX) (WLST itself is a JMX-based application). For more information about the individual MBeans used to manage SIP container properties, see the WebLogic SIP Server Javadocs.
General administration and maintenance of WebLogic SIP Server requires that you manage both WebLogic Server configuration properties and WebLogic SIP Server container properties. These common configuration tasks are summarized in Table 2-1.
Configuring Digest Authentication in Configuring Security
|
|
|