Administration Console Methods and Tools for Performing Configuration Tasks

2-4 Oracle WebLogic Communications Server Administration Guide similar to the core console available in Oracle WebLogic Server 10g Release 3. All Oracle WebLogic Communication Services configuration and monitoring is provided via these nodes in the left pane of the console: ■ SipServer—configures SIP Servlet container properties and other engine tier functionality. This extension also enables you to create new partitions, and view but not modify SIP data tier partitions and replicas. See Section 3.1, Overview of SIP Container Configuration for more information about configuring the SIP Servlet container using the Administration Console. ■ Diameter—configures Diameter nodes and applications.

2.3.2 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 Oracle WebLogic Communication Services domain. Section 3.1, Overview of SIP Container Configuration provides instructions for modifying SIP Servlet container properties using WLST.

2.3.3 Additional Configuration Methods

Most Oracle WebLogic Communication Services 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.

2.3.3.1 Editing Configuration Files

You may also edit sipserver.xml, datatier.xml, diameter.xml, and approuter.xml manually. If you edit configuration files manually, you must reboot all servers to apply the configuration changes.

2.3.3.2 Custom JMX Applications

Oracle WebLogic Communication Services properties are represented by JMX-compliant MBeans. You can therefore program JMX applications to configure SIP container properties using the appropriate Oracle WebLogic Communication Services MBeans. The general procedure for modifying Oracle WebLogic Communication Services MBean properties using JMX is described in Section 3.3, 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 Oracle Fusion Middleware Communication Services Java API Reference.

2.3.3.2.1 Setting Log Levels You can set log levels by manually editing the

logging.xml file, by setting the setLoggerLevelString loggerName, Note: To learn more about using Oracle WebLogic Server Administration Console, see Getting Started with Oracle WebLogic Server Administration Console in Oracle Fusion Middleware Administrators Guide. Note: To learn more about using WLST, see Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. Shared Configuration Tasks 2-5 String logLevel MBean, or through Oracle Enterprise Manager. For more information, see Section 12.2.1, Configuring Logging . See also Oracle Fusion Middleware 2 Day Administration Guide.

2.4 Starting and Stopping Servers

Oracle WebLogic Communication Services start scripts use default values for many JVM parameters that affect performance. For example, JVM garbage collection and heap size parameters may be omitted, or may use values that are acceptable only for evaluation or development purposes. In a production system, you must rigorously profile your applications with different heap size and garbage collection settings in order to realize adequate performance. See Section 8.8, Tuning JVM Garbage Collection for Production Deployments for suggestions about maximizing JVM performance in a production domain. Because a typical Oracle WebLogic Communication Services domain contains numerous engine and SIP data tier servers, with dependencies between the different server types, you should generally follow this sequence when starting up a domain:

1. Start the Administration Server for the domain.

Start the Administration Server in order to provide the initial configuration to engine and SIP data tier servers in the domain. The Administration Server can also be used to monitor the startupshutdown status of each Managed Server. You generally start the Administration Server by using either the startWebLogic.cmd script installed with the Configuration Wizard, or a custom startup script.

2. Start SIP data tier servers in each partition.

The engine tier cannot function until servers in the SIP data tier are available to manage call state data. Although all replicas in each partition need not be available to begin processing requests, at least one replica in each configured partition must be available in order to manage the concurrent call state. All replicas should be started and available before opening the system to production network traffic. You generally start each SIP data tier server by using either the startManagedWebLogic.cmd script installed with the Configuration Wizard, or a custom startup script. startManagedWebLogic.cmd requires that you specify the name of the server to startup, as well as the URL of the Administration Server for the domain, as in: startManagedWebLogic.cmd datanode0-0 t3:adminhost:7001

3. Start engine tier servers.

After the SIP data tier servers have started, you can start servers in the engine tier and begin processing client requests. As with SIP data tier servers, engine tier servers are generally started using the startManagedWebLogic.cmd script or a custom startup script. Following the above startup sequence ensures that all Managed Servers use the latest SIP Servlet container and SIP data tier configuration. This sequence also avoids engine tier error messages that are generated when servers in the SIP data tier are unavailable. Caution: When you configure a domain with multiple engine and SIP data tier servers, you must accurately synchronize all system clocks to a common time source to within one or two milliseconds in order for the SIP protocol stack to function properly. See Section 3.5.2, Configuring NTP for Accurate SIP Timers for more information.