Configuring SIP Servlet Container Properties 2-3
2.3 Configuring Container Properties Using WLST JMX
The WebLogic Scripting Tool WLST is a utility that you can use to observe or modify JMX MBeans available on a WebLogic Server or Oracle WebLogic Server SIP Container
instance. Full documentation for WLST is available in Oracle Fusion Middleware Oracle WebLogic Scripting Tool.
Before using WLST to configure a Oracle WebLogic Server SIP Container domain, set you environment to add required Oracle WebLogic Server SIP Container classes to
your classpath. Use either a domain environment script or the setWLSEnv.sh script located in MIDDLEWARE_HOMEserverbin where MIDDLEWARE_HOME is the root of
your Oracle WebLogic Server SIP Container installation.
2.3.1 Managing Configuration Locks
Table 2–1 summarizes the WLST methods used to lock a configuration and apply
changes.
Here is an example of using the commands to modify the T1 Timer interval:
Note: Some changes you make in the Administration Console take
place immediately when you activate them. Other changes require you to restart the server or module affected by the change. These latter
changes are called non-dynamic changes. Non-dynamic changes are indicated in the Administration Console with a warning icon.
If an edit is made to a non-dynamic configuration setting, no edits to dynamic configuration settings will take effect until after you restart
the server.
For more information on using Oracle WebLogic Server Administration Console, see Oracle Fusion Middleware Administrator’s
Guide.
Table 2–2 MBean Method Summary
Method Description
activate Writes the current configuration MBean attributes the current SIP
Servlet container configuration to the sipserver.xml configuration file and applies changes to the running servers.
cancelEdit Cancels an edit session, releasing the edit lock, and discarding all
unsaved changes. This operation can be called by any user with administrator privileges, even if the user did not start the edit session.
cd Navigate the hierarchy of configuration or runtime beans.
connect Connect WLST to a WebLogic Server instance.
edit Starts an edit session.
save Writes the current configuration MBean attributes the current SIP
Servlet container configuration to a temporary configuration file. set
Set the specified attribute value for the current configuration bean. stopEdit
Releases the lock obtained for modifying SIP container properties and rolls back any pending MBean changes, discarding any temporary
files.
2-4 Oracle WebLogic SIP Server Container Administrators Guide
Example 2–1 Modifying T1 Timer Interval
connect edit
cdCustomResourcessipserverResourcesipserver setT1TimeoutInterval,505
activate
2.3.2 Locating the Oracle WebLogic Server SIP Container MBeans
All SIP Servlet container configuration MBeans are located in the serverConfig MBean tree, accessed using the serverConfig command in WLST. Within this
bean tree, individual configuration MBeans can be accessed using the path:
CustomResourcessipserverResourcesipserver For example, to browse the default Proxy MBean for a Oracle WebLogic Server SIP
Container domain you would enter these WLST commands: serverConfig
cdCustomResourcessipserverResourcesipserverProxy ls
Runtime MBeans are accessed in the custom MBean tree, accessed using the custom command in WLST. Runtime MBeans use the path:
mydomain:Location=myserver,Name=myserver,Type=mbeantype Certain configuration settings, such as proxy and overload protection settings, are
defined by default in sipserver.xml. Configuration MBeans are generated for these settings when you boot the associated server, so you can immediately browse the
Proxy and OverloadProtection MBeans. Other configuration settings are not configured by default and you will need to create the associated MBeans before they
can be accessed. See
Section 2.4.2, Creating and Deleting MBeans .
2.4 WLST Configuration
Kategori