JBoss.orgCommunity Documentation
The JBoss Communications Media Server distribution is available in two forms: Standalone and Embedded in JBoss Application Server 5. The standalone version is more preferred for carrier production deployment while JBoss Application Server 5 version is most useful for development
The JBoss Communications Media Server is available in both binary and source code distributions. The simplest way to get started with the Media Server is to download the ready-to-run binary distribution. Alternatively, the source code for the JBoss Communications Media Server can be obtained by checking it out from its repository using the Subversion version control system ( SVN ), and then built using the Maven build system. Whereas installing the binary distribution is recommended for most users, obtaining and building the source code is recommended for those who want access to the latest revisions and Media Server capabilities.
The MobicentsJBCP platform is written in Java. A working Java Runtime Environment (JRE) or Java Development Kit (JDK) must be installed prior to running the server. The required versiom must be version 5 or higher.
It is possible to run most MobicentsJBCP servers, such as the JAIN SLEE Server, using a Java 6 JRE or JDK.
Although MobicentsJBCP servers are capable of running on the Java Runtime Environment, this guide assumes the audience is mainly developers interested in developing Java-based, MobicentsJBCP-driven solutions. Therefore, installing the Java Development Kit is covered due to the anticipated audience requirements.
If the system uses 64-Bit Linux or Windows architecure, the 64-bit JDK is strongly recommended over the 32-bit version. The following heuristics should be considered in determining whether the 64-bit Java Virtual Machine (JVM) is suitable:
Wider datapath: the pipe between RAM and CPU is doubled, which improves the performance of memory-bound applications when using a 64-bit JVM.
64-bit memory addressing provides a virtually unlimited (1 exabyte) heap allocation. Note that large heaps can affect garbage collection.
Applications that run with more than 1.5 GB of RAM (including free space for garbage collection optimization) should utilize the 64-bit JVM.
Applications that run on a 32-bit JVM and do not require more than minimal heap sizes will gain nothing from a 64-bit JVM. Excluding memory issues, 64-bit hardware with the same relative clock speed and architecture is not likely to run Java applications faster than the 32-bit version.
The following instructions describe how to download and install the 32-bit JDK, however the steps are nearly identical for installing the 64-bit version.
Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun's website: http://java.sun.com/javase/downloads/index_jdk5.jsp. Click the Download link next to "JDK 5.0 Update <x>
" (where <x>
is the latest minor version release number).
The Sun website offers two download options:
A self-extracting RPM (for example, jdk-1_5_0_16-linux-i586-rpm.bin
)
A self-extracting file (e.g. jdk-1_5_0_16-linux-i586.bin
)
If installing the JDK on Red Hat Enterprise Linux, Fedora, or another RPM-based Linux system, it is recommended that the self-extracting file containing the RPM package is selected. This option will set up and use the SysV service scripts in addition to installing the JDK. The RPM option is also recommended if the MobicentsJBCP platform is being set up in a production environment.
The following procedures detail how to install the Java Development Kit on both Linux and Windows.
Procedure 3.1. Installing the JDK on Linux
Ensure the file is executable, then run it:
~]$ chmod +x "jdk-1_5_0_<minor_version>-linux-<architecture>-rpm.bin" ~]$ ./"jdk-1_5_0_<minor_version>-linux-<architecture>-rpm.bin"
If the non-RPM self-extracting file is selected for an RPM-based system, the SysV service scripts can be configured by downloading and installing one of the -compat
packages from the JPackage project. Download the -compat
package that corresponds correctly to the minor release number of the installed JDK. The compat packages are available from ftp://jpackage.hmdc.harvard.edu/JPackage/1.7/generic/RPMS.non-free/.
A -compat
package is not required for RPM installations. The -compat
package performs the same SysV service script set up that the RPM version of the JDK installer does.
Procedure 3.2. Installing the JDK on Windows
Using Explorer, double-click the downloaded self-extracting installer and follow the instructions to install the JDK.
Configuring the system for the JDK consists of two tasks: setting the JAVA_HOME
environment variable, and ensuring the system is using the proper JDK (or JRE) using the alternatives
command. Setting JAVA_HOME
generally overrides the values for java
, javac
and java_sdk_1.5.0
in alternatives
, however it is recommended to specify the value for consistency.
JAVA_HOME
Environment Variable on Generic Linux
After installing the JDK, ensure the JAVA_HOME
environment variable exists and points to the location of the JDK installation.
JAVA_HOME
Environment Variable on LinuxDetermine whether JAVA_HOME
is set by executing the following command:
~]$ echo $JAVA_HOME
If JAVA_HOME
is not set, the value must be set to the location of the JDK installation on the system. This can be achieved by adding two lines to the ~/.bashrc
configuration file. Open ~/.bashrc
(or create it if it does not exist) and add a line similar to the following one anywhere inside the file:
export JAVA_HOME="/usr/lib/jvm/jdk1.5.0_<version>"
The changes should also be applied for other users who will be running the MobicentsJBCP on the machine (any environment variables export
ed from ~/.bashrc
files are local to that user).
java
, javac
and java_sdk_1.5.0
using the alternatives
command alternatives
On systems with the alternatives
command, including Red Hat Enterprise Linux and Fedora, it is possible to choose which JDK (or JRE) installation to use, as well as which java
and javac
executables should be run when called.
As the superuser, call /usr/sbin/alternatives
with the --config java
option to select between JDKs and JREs installed on your system:
home]$ sudo /usr/sbin/alternatives --config java There are 3 programs which provide 'java'. Selection Command ----------------------------------------------- 1 /usr/lib/jvm/jre-1.5.0-gcj/bin/java 2 /usr/lib/jvm/jre-1.6.0-sun/bin/java *+ 3 /usr/lib/jvm/jre-1.5.0-sun/bin/java Enter to keep the current selection[+], or type selection number:
The Sun JDK, version 5, is required to run the java
executable. In the alternatives
information printout above, a plus (+
) next to a number indicates the option currently being used. Press Enter to keep the current JVM, or enter the number corresponding to the JVM to select that option.
As the superuser, repeat the procedure above for the javac
command and the java_sdk_1.5.0
environment variable:
home]$ sudo /usr/sbin/alternatives --config javac
home]$ sudo /usr/sbin/alternatives --config java_sdk_1.5.0
JAVA_HOME
Environment Variable on WindowsFor information on how to set environment variables in Windows, refer to http://support.microsoft.com/kb/931715.
To ensure the correct JDK or Java version (5 or higher), and that the java executable is in the PATH
environment variable, run the java -version
command in the terminal from the home directory:
home]$ java -version java version "1.5.0_16" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b03) Java HotSpot(TM) Client VM (build 1.5.0_16-b03, mixed mode, sharing)
It is not necessary to remove a particular JDK from a system, because the JDK and JRE version can be switched as required using the alternatives
command, and/or by setting JAVA_HOME
.
On RPM-based systems, uninstall the JDK using the yum remove <jdk_rpm_name>
command.
On Windows systems, check the JDK entry in the Start
menu for an uninstall option, or use Add/Remove Programs
.
The JBoss Communications Media Server either comes bundled with the JBoss Application Server or Standalone. This section details how to install the JBoss Communications Media Server that comes bundled with JBoss Application Server 5. For installation of Standalone JBoss Communications Media Server, refer to Section 3.3, “ Standalone Media Server Binary Distribution: Installing, Configuring and Running ”
Ensure that the following requirements have been met before continuing with the install.
Hardware Requirements
Once unzipped, the JBoss AS embedded Media Server binary release requires at least 110 Mb of free disk space. Keep in mind that disk space requirements may change from release to release.
The JBoss embedded Media Server and its bundled servers, JBoss, are 100% Java. The Media Server will run on the same hardware that the JBoss Application Server runs on.
Software Prerequisites
A working installation of the Java Development Kit ( JDK ) version 5 or higher is required in order to run the JBoss embedded Media Server. Note that the JBoss Application Server is a runtime dependency of the Media Server and, as mentioned, comes bundled with the binary distribution.
The latest version of the JBoss embedded Media Server is
available from
http://www.mobicents.org/mms/mms-downloads.html
. The top row of the table holds the latest version.
Click the
Download
link to start the download.
Once the requirements and prerequisites have been met, the JBoss embedded Media Server can be installed onto the system. Follow the instructions below for the operating system on which the server will reside.
For clarity, the command line instructions presented in this chapter use specific version numbers and directory names. Ensure this information is substituted with the binary distribution's version numbers and file names.
Procedure 3.3. Installing the JBoss embedded Media Server Binary Distribution on Linux
It is assumed that the downloaded archive is saved in the home directory, and that a terminal window is open displaying the home directory.
Create a subdirectory to extract the files into. For ease of identification, it is recommended that the version number of the binary is included in this directory name.
~]$ mkdir “ms-<version>
”
Move the downloaded zip file into the directory:
~]$ mv “mms-jboss-5.1.0.GA-2.0.0.BETA3.zip” “ms-<version>
”
Move into the directory:
~]$ cd “ms-<version>
”
Extract the files into the current directory by executing one of the following commands.
Java:
ms-<version>
]$ jar -xvf “mms-jboss-5.1.0.GA-2.0.0.BETA3.zip”
Linux:
ms-<version>]$ unzip "mms-jboss-5.1.0.GA-2.0.0.BETA3.zip"
Alternatively, use
unzip
-d <unzip_to_location> to extract
the zip file's contents to a location
other than the current directory.
Consider deleting the archive, if free disk space is an issue.
ms-<version>
]$ rm “mms-jboss-5.1.0.GA-2.0.0.BETA3.zip”
Procedure 3.4. Installing the JBoss embedded Media Server Binary Distribution on Windows
For this procedure, it is assumed that the
downloaded archive is saved in the
My Downloads
folder.
Create a subfolder in
My Downloads
to extract the zip file's contents into. For
ease of identification, it is recommended that
the version number of the binary is included in
the folder name. For example,
ms-<version>
.
Extract the contents of the archive, specifying the destination folder as the one created in the previous step.
Alternatively, execute the
jar -xvf
command to extract the binary distribution files
from the zip archive.
Move the downloaded zip file from
My Downloads
to the folder created in the previous
step.
Open the Windows Command Prompt and
navigate to the folder that contains the
archive using the
cd
command
Execute the
jar -xvf
command to extract the archive contents
into the current folder.
C:Users<user>My Downloadsms-<version>jar -xvf "mms-jboss-5.1.0.GA-2.0.0.BETA3.zip"
It is recommended that the folder holding the
JBoss embedded Media Server files (in this
example, the folder named
ms-
) is moved to a user-defined location for
storing executable programs. For example, the
<version>
Program Files
folder.
Consider deleting the archive, if free disk space is an issue.
C:Users<user>My Downloadsms-<version>delete "mms-jboss-5.1.0.GA-2.0.0.BETA3.zip"
The Mobicents Platform (Mobicents) is built on top of the JBoss Application Server (JBoss AS). You do not need to set the JBOSS_HOME
environment variable to run any of the Mobicents Platform servers unless JBOSS_HOME
is already set.
The best way to know for sure whether JBOSS_HOME
was set previously or not is to perform a simple check which may save you time and frustration.
At the command line, echo
$JBOSS_HOME
to see if it is currently defined in your environment:
~]$ echo $JBOSS_HOME
The Mobicents Platform and most Mobicents servers are built on top of the JBoss Application Server (JBoss AS). When the Mobicents Platform or Mobicents servers are built from source, then JBOSS_HOME
must be set, because the Mobicents files are installed into (or “over top of” if you prefer) a clean JBoss AS installation, and the build process assumes that the location pointed to by the JBOSS_HOME
environment variable at the time of building is the JBoss AS installation into which you want it to install the Mobicents files.
This guide does not detail building the Mobicents Platform or any Mobicents servers from source. It is nevertheless useful to understand the role played by JBoss AS and JBOSS_HOME
in the Mobicents ecosystem.
The immediately-following section considers whether you need to set JBOSS_HOME
at all and, if so, when. The subsequent sections detail how to set JBOSS_HOME
on Linux and Windows
Even if you fall into the category below of not needing to set JBOSS_HOME
, you may want to for various reasons anyway. Also, even if you are instructed that you do not need to set JBOSS_HOME
, it is good practice nonetheless to check and make sure that JBOSS_HOME
actually isn't set or defined on your system for some reason. This can save you both time and frustration.
JBOSS_HOME
if......you have installed the Mobicents Platform binary distribution.
...you have installed a Mobicents server binary distribution which bundles JBoss AS.
JBOSS_HOME
if you are:installing the Mobicents Platform or any of the Mobicents servers from source.
installing the Mobicents Platform binary distribution, or one of the Mobicents server binary distributions, which do not bundle JBoss AS.
Naturally, if you installed the Mobicents Platform or one of the Mobicents server binary releases which do not bundle JBoss AS, yet requires it to run, then you should install JBoss AS before setting JBOSS_HOME
or proceeding with anything else.
The JBOSS_HOME
environment variable must point to the directory which contains all of the files for the Mobicents Platform or individual Mobicents server that you installed. As another hint, this topmost directory contains a bin
subdirectory.
Setting JBOSS_HOME
in your personal ~/.bashrc
startup script carries the advantage of retaining effect over reboots. Each time you log in, the environment variable is sure to be set for you, as a user. On Linux, it is possible to set JBOSS_HOME
as a system-wide environment variable, by defining it in /etc/bashrc
, but this method is neither recommended nor detailed in these instructions.
Procedure 3.5. To Set JBOSS_HOME on Linux
Open the ~/.bashrc
startup script, which is a hidden file in your home directory, in a text editor, and insert the following line on its own line while substituting for the actual install location on your system:
export JBOSS_HOME="/home/<username>/<path>/<to>/<install_directory>"
Save and close the .bashrc
startup script.
You should source
the .bashrc
script to force your change to take effect, so that JBOSS_HOME
becomes set for the current session. Note that any other terminals which were opened prior to altering .bashrc
will need to source
~/.bashrc
as well should they require access to JBOSS_HOME
.
~]$ source ~/.bashrc
Finally, ensure that JBOSS_HOME
is set in the current session, and actually points to the correct location:
The command line usage below is based upon a binary installation of the Mobicents Platform. In this sample output, JBOSS_HOME
has been set correctly to the topmost_directory
of the Mobicents installation. Note that if you are installing one of the standalone Mobicents servers (with JBoss AS bundled!), then JBOSS_HOME
would point to the topmost_directory
of your server installation.
~]$ echo $JBOSS_HOME /home/user/
The JBOSS_HOME
environment variable must point to the directory which contains all of the files for the Mobicents Platform or individual Mobicents server that you installed. As another hint, this topmost directory contains a bin
subdirectory.
For information on how to set environment variables in recent versions of Windows, refer to http://support.microsoft.com/kb/931715.
In the Linux terminal or Windows command prompt, the JBoss embedded Media Server has started successfully if the last line of output is similar to the following (ending with “Started in 23s:648ms” ):
11:27:34,663 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started in 37s:637ms
Procedure 3.6. Running the Media Server on Linux
Change the working directory to installation directory (the one in which the zip file's contents was extracted to)
downloads]$ cd "ms-<version>"
(Optional) Ensure that the
bin/run.sh
start script is executable.
ms-<version>]$ chmod +x bin/run.sh
Execute the
run.sh
Bourne shell script.
ms-<version>]$ ./bin/run.sh
Instead of executing the Bourne shell script to
start the server, the
run.jar
executable Java archive can be executed from the
bin
directory:
ms-<version>]$ java -jar bin/run.jar
Procedure 3.7. Running the JBoss embedded Media Server on Windows
Using Windows Explorer, navigate to the
bin
subfolder in the installation directory.
The preferred way to start the JBoss embedded Media Server is from the Command Prompt. The command line interface displays details of the startup process, including any problems encountered during the startup process.
Open the Command Prompt via the Start menu and navigate to the correct folder:
C:Users<user>My Downloads> cd "ms-<version>"
Start the JBoss Application Server by executing one of the following files:
run.bat
batch file:
C:Users<user>My Downloadsms-<version>>binrun.bat
run.jar
executable Java archive:
C:Users<user>My Downloadsms-<version>>java -jar binrun.jar
Detailed instructions for stopping the JBoss Application Server are given below, arranged by platform. If the server is correctly stopped, the following three lines are displayed as the last output in the Linux terminal or Command Prompt:
[Server] Shutdown complete Shutdown complete Halting VM
Procedure 3.8. Stopping the Media Server on Linux
Change the working directory to the binary distribution's install directory.
~]$ cd "ms-<version>"
(Optional) Ensure that the bin/shutdown.sh start script is executable:
ms-<version>]$ chmod +x bin/shutdown.sh
Run the
shutdown.sh
executable Bourne shell script with the
-S
option (the short option for
--shutdown
) as a command line argument:
ms-<version>]$ ./bin/shutdown.sh -S
The
shutdown.jar
executable Java archive with the
-S
option can also be used to shut down the server:
ms-<version>]$ java -jar bin/shutdown.jar -S
Procedure 3.9. Stopping JBoss embedded Media Server on Windows
Stopping the JBoss Application Server on Windows
consists of executing either the
shutdown.bat
or the
shutdown.jar
executable file in the
bin
subfolder of the MMS for JBoss binary
distribution. Ensure the
-S
option (the short option for
--shutdown
) is included in the command line argument.
C:Users<user>My Downloadsms-<version>>binshutdown.bat -S
The
shutdown.jar
executable Java archive with the
-S
option can also be used to shut down the
server:
C:Users<user>My Downloadsms-<version>>java -jar binshutdown.jar -S
Now the server is installed, it is important to understand the layout of the server directories. An understanding of the server structure is useful when deploying examples, and making configuration changes. It is also useful to understand what components can be removed to reduce the server boot time.
The directory structure in the JBoss embedded Media Server installation directory is named using a standard structure. Table 3.1, “Directory Structure” describes each directory, and the type of information contained within each location.
Table 3.1. Directory Structure
Directory Name | Description |
---|---|
bin | Contains the entry point JARs and start-up scripts included with the Media Server distribution. |
conf | Contains the core services that are required for the server. This includes the bootstrap descriptor, log files, and the default bootstrap-beans.xml configuration file. |
deploy | Contains the dynamic deployment content required by the hot deployment service. The deploy location can be overridden by specifying a location in the URL attribute of the URLDeploymentScanner configuration item. |
lib | Contains the startup JAR files used by the server. |
log |
Contains the logs from the bootstrap
logging service. The
log
directory is the default directory into
which the bootstrap logging service
places its logs, however, the location
can be overridden by altering the
log4j.xml configuration file. This file
is located in the
/conf
directory.
|
The Media Server uses a number of XML configuration files that control various aspects of the server. In case of embedded Media Server all the files related Media Server are placed in mms-jboss-5.1.0.GA-<version>/jboss-5.1.0.GA/server/default/deploy/mobicents-media-server Table 3.2, “Core Configuration File Set” describes the location of the key configuration files, and provides a description of the
Table 3.2. Core Configuration File Set
File Name and Location | Description |
---|---|
mobicents-media-server.sar/META-INF/jboss-beans.xml |
Specifies which additional
microcontainer deployments are loaded as
part of the bootstrap phase.
bootstrap-beans.xml references other
configuration files contained in the
/conf/bootstrap/
directory. For a standard configuration,
the bootstrap configuration files
require no alteration.
|
mobicents-media-server/ann-beans.xml | Specifies the configuration for announcement access points. |
mobicents-media-server/ivr-beans.xml | Specifies the configuration for Interactive Voice Response (IVR) endpoints. |
mobicents-media-server/prelay-beans.xml | Specifies the configuration for Packet Relay endpoints. |
mobicents-media-server/cnf-beans.xml | Specifies the configuration for Conference endpoints. |
mobicents-media-server/test-beans.xml | Specifies the endpoint for test capabilities. |
mgcp-controller-service.sar/META-INF/jboss-beans.xml | Specifies the configuration for the MGCP controller. |
For information on testing the Media Server, refer to Section 3.4, “ Writing and Running Tests Against the Media Server ” .
The Mobicents Media Server either comes bundled with the JBoss Application Server or Standalone. This section details how to install the Standalone Mobicents Media Server. For installation of JBoss embedded Mobicents Media Server, refer to Section 3.2, “ JBoss Application Server 5.x.y embedded Media Server Binary Distribution: Installing, Configuring and Running ”
Ensure that the following requirements have been met before continuing with the install.
The latest version of the Standalone Media Server is
available from
http://www.mobicents.org/mms-downloads.html
. The top row of the table holds the latest version.
Click the
Download
link to start the download.
Once the requirements and prerequisites have been met, the Standalone Media Server can be installed onto the system. Follow the instructions below for the operating system on which the server will reside.
For clarity, the command line instructions presented in this chapter use specific version numbers and directory names. Ensure this information is substituted with the binary distribution's version numbers and file names.
Procedure 3.10. Installing the Standalone Media Server Binary Distribution on Linux
It is assumed that the downloaded archive is saved in the home directory, and that a terminal window is open displaying the home directory.
Create a subdirectory to extract the files into. For ease of identification, it is recommended that the version number of the binary is included in this directory name.
~]$ mkdir “ms-<version>
”
Move the downloaded zip file into the directory:
~]$ mv “mms-standalone-2.0.0.BETA3.zip” “ms-<version>
”
Move into the directory:
~]$ cd “ms-<version>
”
Extract the files into the current directory by executing one of the following commands.
Java:
ms-<version>
]$ jar -xvf “mms-standalone-2.0.0.BETA3.zip”
Linux:
ms-<version>]$unzip "mms-standalone-2.0.0.BETA3.zip"
Alternatively, use
unzip
-d <unzip_to_location> to extract
the zip file's contents to a location
other than the current directory.
Consider deleting the archive, if free disk space is an issue.
ms-<version>
]$ rm “mms-standalone-2.0.0.BETA3.zip”
Procedure 3.11. Installing the Standalone Media Server Binary Distribution on Windows
For this procedure, it is assumed that the
downloaded archive is saved in the
My Downloads
folder.
Create a subfolder in
My Downloads
to extract the zip file's contents into. For
ease of identification, it is recommended that
the version number of the binary is included in
the folder name. For example,
ms-<version>
.
Extract the contents of the archive, specifying the destination folder as the one created in the previous step.
Alternatively, execute the
jar -xvf
command to extract the binary distribution files
from the zip archive.
Move the downloaded zip file from
My Downloads
to the folder created in the previous
step.
Open the Windows Command Prompt and
navigate to the folder that contains the
archive using the
cd
command
Execute the
jar -xvf
command to extract the archive contents
into the current folder.
C:Users<user>My Downloadsms-<version>jar -xvf "mms-standalone-2.0.0.BETA3.zip"
It is recommended that the folder holding the
Standalone Media Server files (in this example,
the folder named
mms-standalone-
) is moved to a user-defined location for
storing executable programs. For example, the
<version>
Program Files
folder.
Consider deleting the archive, if free disk space is an issue.
C:Users<user>My Downloadsms-<version>delete "mms-standalone-2.0.0.BETA3.zip"
In the Linux terminal or Windows command prompt, the Standalone Media Server has started successfully if the last line of output is similar to the following
2100 [main] INFO org.mobicents.media.server.bootstrap.MainDeployer - [[[[[[[[[ Mobicents Media Server: release.version=2.0.0.BETA3 Started ]]]]]]]]]
Procedure 3.12. Running the Standalone Media Server on Linux
Change the working directory to installation directory (the one in which the zip file's contents was extracted to)
downloads]$ cd "mms-standalone-<version>"
(Optional) Ensure that the
bin/run.sh
start script is executable.
ms-<version>]$ chmod +x bin/run.sh
Execute the
run.sh
Bourne shell script.
ms-<version>]$ ./bin/run.sh
Instead of executing the Bourne shell script to
start the server, the
run.jar
executable Java archive can be executed from the
bin
directory:
mms-standalone-<version>]$ java -jar bin/run.jar
Procedure 3.13. Running the Standalone Media Server on Windows
Using Windows Explorer, navigate to the
bin
subfolder in the installation directory.
The preferred way to start the Standalone Media Server is from the Command Prompt. The command line interface displays details of the startup process, including any problems encountered during the startup process.
Open the Command Prompt via the Start menu and navigate to the correct folder:
C:Users<user>My Downloads>cd "mms-standalone-<version>"
Start the Standalone Server by executing one of the following files:
run.bat
batch file:
C:Users<user>My Downloadsmms-standalone<version>>binrun.bat
run.jar
executable Java archive:
C:Users<user>My Downloadsmms-standalone-<version>>java -jar binrun.jar
Detailed instructions for stopping the Standalone Media Server are given below, arranged by platform. If the server is correctly stopped, the following three lines are displayed as the last output in the Linux terminal or Command Prompt:
[Server] Shutdown complete Shutdown complete Halting VM
Procedure 3.14. Stopping the Standalone Media Server on Linux
Change the working directory to the binary distribution's install directory.
~]$ cd "mms-standalone-<version>"
(Optional) Ensure that the bin/shutdown.sh start script is executable:
mms-standalone-<version>]$ chmod +x bin/shutdown.sh
Run the
shutdown.sh
executable Bourne shell script with the
-S
option (the short option for
--shutdown
) as a command line argument:
mms-standalone-<version>]$./bin/shutdown.sh -S
The
shutdown.jar
executable Java archive with the
-S
option can also be used to shut down the server:
mms-standalone-<version>]$ java -jar bin/shutdown.jar -S
Procedure 3.15. Stopping Standalone Media Server on Windows
Stopping the Standalone Media Server on Windows
consists of executing either the
shutdown.bat
or the
shutdown.jar
executable file in the
bin
subfolder of the MMS for JBoss binary
distribution. Ensure the
-S
option (the short option for
--shutdown
) is included in the command line argument.
C:Users<user>My Downloadsmms-standalone-<version>>binshutdown.bat -S
The
shutdown.jar
executable Java archive with the
-S
option can also be used to shut down the
server:
C:Users<user>My Downloadsmms-standalone-<version>>java -jar binshutdown.jar -S
Now the server is installed, it is important to understand the layout of the server directories. An understanding of the server structure is useful when deploying examples, and making configuration changes. It is also useful to understand what components can be removed to reduce the server boot time.
The directory structure in the Standalone Media Server installation directory is named using a standard structure. Table 3.3, “Directory Structure” describes each directory, and the type of information contained within each location.
Table 3.3. Directory Structure
Directory Name | Description |
---|---|
bin | All the entry point JARs and start scripts included with the Media Server distribution are located in the bin directory |
conf | The conf directory contains the bootstrap descriptor, bootstrap-beans.xml by default, file for a given server configuration. This defines the core services that are fixed for the lifetime of the server. |
deploy | The deploy directory is the default location the hot deployment service looks to for dynamic deployment content. This may be overridden through the URLDeploymentScanner URLs attribute. |
lib | Contains the startup JAR files used by the server. |
log |
Contains the logs from the bootstrap
logging service. The
log
directory is the default directory into
which the bootstrap logging service
places its logs, however, the location
can be overridden by altering the
log4j.xml configuration file. This file
is located in the
/conf
directory.
|
The Standalone Media Server uses a number of XML configuration files that control various aspects of the server. Table 3.4, “Core Configuration File Set” describes the location of the key configuration files, and provides a description of the
Table 3.4. Core Configuration File Set
File Name and Location | Description |
---|---|
conf/bootstrap-beans.xml |
Specifies which additional
microcontainer deployments are loaded as
part of the bootstrap phase.
bootstrap-beans.xml references other
configuration files contained in the
/conf/bootstrap/
directory. For a standard configuration,
the bootstrap configuration files
require no alteration.
|
conf/log4j.properties |
Specifies the Apache
log4j
framework category priorities and
appenders used by the Media Server.
|
deploy/ann-beans.xml | Specifies the configuration for announcement access points. |
deploy/ivr-beans.xml | Specifies the configuration for Interactive Voice Response (IVR) endpoints. |
deploy/prelay-beans.xml | Specifies the configuration for Packet Relay endpoints. |
deploy/cnf-beans.xml | Specifies the configuration for Conference endpoints. |
deploy/test-beans.xml | Specifies the endpoint for test capabilities. |
deploy/mgcp-conf.xml | Specifies the configuration for the MGCP controller. |
For information on testing the Media Server, refer to Section 3.4, “ Writing and Running Tests Against the Media Server ” .
For information about the different kinds of tests that the Media Server provides, refer to Writing and Running Tests Against MMS .