This chapter introduces Oracle Communications Converged Application Server configuration and administration.
Converged Application Server is based on Oracle WebLogic Server, and many system-level configuration tasks are the same for both products. This guide addresses only those system-level configuration tasks that are unique to Converged Application Server, such as tasks related to network and security configuration and cluster configuration for the engine and the Coherence cache.
HTTP server configuration and other basic configuration tasks such as server logging are addressed in the Oracle WebLogic Server documentation. See "Overview of WebLogic Server System Administration" in Understanding Oracle WebLogic Server to get started.
You can apply configuration changes using the Administration Console or from the command line using the WLST utility. Changes to certain SIP Servlet container properties require a restart of the engine for the change to take affect. In such cases, a Restart may be required icon appears in the console.
The following sections contain more information about the configuration tools:
The Converged Application Server extends the WebLogic Administration Console user interface with its own configuration and monitoring pages. The Administration Console interface for Converged Application Server settings are similar to the core console available in Oracle WebLogic Server.
All Converged Application Server configuration and monitoring is provided through these nodes in the left pane of the console:
SipServer: presents SIP Servlet container properties and other engine functionality. This node is available for all domain types.
ProxyRegistrar: presents Proxy/Registrar configuration options if you have configured a proxy/registrar domain.
Diameter: presents Diameter nodes and application configuration settings if you have added Diameter support to an existing domain. For information on adding Diameter support to a Converged Application Server domain, see "About Domains and Domain Configuration" in Converged Application Server Installation Guide.
See "Accessing the Administration Console" for more information about using the console in the Oracle WebLogic Server documentation.
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 Converged Application Server domain.
See "Using WLST (JMX) to Configure Converged Application Server" for more information about modifying SIP Servlet container properties using WLST.
For general WLST information, see:
For information about WLST, see "Using the WebLogic Scripting Tool" in Understanding the WebLogic Scripting Tool.
For information about WLST commands, see "WLST Command and Variable Reference" in WLST Command Reference for WebLogic Server.
Most Converged Application 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 modify the configuration by editing configuration files.
The Converged Application Server custom resources utilize the basic domain resources defined in config.xml, such as network channels, cluster and server configuration, and Java EE resources. The config.xml file applies to all managed servers in the domain. However, standalone Converged Application Server components are configured in separate configuration files based on functionality:
sipserver.xml contains general SIP container properties and engine tier configuration settings.
coherence.xml identifies servers that participate in SIP state storage, and also defines the number of threads and partitions available in the state storage service.
diameter.xml defines Diameter nodes and Diameter protocol applications used in the domain.
See Part I, "Reference" for more information on the configuration files.
If you edit configuration files manually, you must reboot all servers to apply the configuration changes.
Converged Application Server properties are represented by JMX-compliant MBeans. You can therefore program JMX applications to configure SIP container properties using the appropriate Converged Application Server MBeans.
The general procedure for modifying Converged Application Server MBean properties using JMX is described in "Using WLST (JMX) to Configure Converged Application Server". For more information about the individual MBeans used to manage SIP container properties, see the Converged Application Server Java API Reference.
General administration and maintenance of Converged Application Server requires that you manage both WebLogic Server configuration properties and Converged Application Server container properties.
Common configuration tasks include:
Configure SIP Container Properties using the Administration Console or using WLST to perform batch configuration. See "Configuring Converged Application Server Container Properties" for more information.
Configure WebLogic Server network channels to handle SIP and HTTP traffic. See "Configuring Network Connection Settings" for more information.
Configure load balancers, proxy registrar, diameter components, or other infrastructure elements to support the Converged Application Server deployment. See "Configuring Infrastructure Components" for more information.
Deploy applications to the Converged Application Servers. See Converged Application Server Developer's Guide for more information.
Create and deploy logging Servlets to record SIP requests and responses and manage log records. See "Logging SIP Requests and Responses" for more information.