Overview of Configuration and Administration Tools

You can apply configuration changes using the Remote Console, using the REST API, 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 Server or App Restart Required icon appears in the Remote Console.

Note:

The administrator must restart the server when fields with Server or App Restart Required are modified.

The following sections contain more information about the configuration tools:

Remote Console

You can use the Remote Console to view or edit the Converged Application Server. The Converged Application Server configuration and monitoring is provided through the Edit Tree and the Monitoring Tree.

Under the Edit Tree or the Configuration View Tree, you can access most of the settings by clicking Custom Resources, and then sipserver, and then SIP Server.

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

REST API

You can use the REST API to retrieve runtime metrics; create, modify, or delete address-of-record entries in the Location Service; and manage configuration settings.

For information about the REST API, see the Developer Guide.

Additional Configuration Methods

Most Converged Application Server configuration is performed using either the Remote 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.
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 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 Java API Reference.