Skip Headers
Oracle® Communications Converged Application Server Administrator's Guide
Release 5.1

Part Number E27704-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

1 Converged Application Server Configuration Overview

This chapter introduces Oracle Communications Converged Application Server configuration and administration. It covers the following topics:

About the Oracle WebLogic Platform

Converged Application Server is based on Oracle WebLogic Server 11g, 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 SIP data tiers.

HTTP server configuration and other basic configuration tasks such as server logging are addressed in the Oracle WebLogic Server documentation. See Oracle Fusion Middleware Getting Started With Installation for Oracle WebLogic Server to get started.

Overview of Configuration and Administration Tools

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 tier server for the change to take affect. In such cases, a Restart may be required icon appears in the console. Configuration for SIP data tier nodes cannot be changed dynamically, so you must reboot SIP data tier servers in order to change the number of partitions or replicas.

The following sections contain more information about the configuration tools:

Administration Console

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 11g.

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 tier functionality. This extension also enables you to view (but not modify) SIP data tier partitions and replicas.

  • Converged Load Balancer: presents configuration settings and monitoring pages for the activities of the converged load balancers in the implementation.

  • Diameter: presents Diameter nodes and application configuration settings.

See "Accessing the Administration Console" for more information about using the console in the Oracle WebLogic Server documentation.

WebLogic Scripting Tool (WLST)

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 WebLogic Server information, see the following documents:

  • For information about WLST, see Oracle WebLogic Scripting Tool.

  • For information about WLST commands, see WebLogic Scripting Tool Command Reference.

Additional Configuration Methods

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.

Editing Configuration Files

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.

  • datatier.xml identifies servers that participate as replicas in the SIP data tier, and also defines the number and layout of SIP data tier partitions.

  • diameter.xml defines Diameter nodes and Diameter protocol applications used in the domain.

  • approuter.xml contains the configuration for the Default Application Router (DAR) and the Custom Application Router (CAR).

  • clb-local-config.xml contains the Converged Load Balancer configuration.

The component configuration files determine the role of each server instance, such as whether they behave as SIP data tier replicas, engine tier nodes, or Diameter client nodes.

See Part IV, "Reference" for more information on the configuration files.

If you edit configuration files manually, you must reboot all servers to apply the configuration changes.

Custom JMX Applications

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 JavaDocs.

Common Configuration Tasks

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: