Media Server Interoperability,
HTTP/SIP Session Convergence and
BEA Tooling
Demonstration Application Installation &
Configuration Document
March 15, 2006
BEA Systems, Inc.
Demonstration Application Installation & Configuration
1
BROOKTROUT INSTALLATION & CONFIGURATION ...................................................................................... 2
2
WEBLOGIC PLATFORM 8.1 SP5 SOFTWARE DOWNLOAD AND INSTALLATION .............................................. 2
3
WEBLOGIC SIP SERVER INSTALLATION .................................................................................................... 2
4
CONFERENCE APPLICATION DEMO FILES ................................................................................................... 3
5
CREATING AND CONFIGURING SIP APPLICATION DOMAIN .......................................................................... 3
6
CREATING AND CONFIGURING SIP PROXY/REGISTRAR DOMAIN ................................................................. 9
7
EXECUTING CONFERENCE APPLICATION ................................................................................................. 10
7.1
Creating a Conference ................................................................................................................. 11
7.2
Monitoring/Conference Administration ......................................................................................... 14
31-Jul-2017
BEA Systems, Inc.
Page 1
Demonstration Application Installation & Configuration
1
Brooktrout Installation & Configuration
Please refer to Brooktrout Media Server installation and configuration documentation to install and
configure the media server.
2
WebLogic Platform 8.1 SP5 Software download and Installation
WebLogic Platform 8.1 with Service Pack 5 can be downloaded from:
http://commerce.bea.com/showproduct.jsp?family=WLP&major=8.1&minor=5
The documentation for installing WebLogic Platform 8.1 is available at:
http://edocs.bea.com/platform/docs81/install/index.html
Please install WebLogic Platform 8.1 SP5 on the machine (say application machine) that will host the
WebLogic Server SIP conferencing application.
3
WebLogic SIP Server installation
WebLogic Sip Server 2.1 can be downloaded from:
http://commerce.bea.com/showproduct.jsp?family=WLSS&major=2.1&minor=0
The documentation for installing WebLogic SIP Server is available at:
http://edocs.bea.com/wlcp/wlss21/install/quickstart.html
Please install the WebLogic SIP Server using the BEA HOME directory created by the WebLogic Platform
installation described in the previous section.
The directory structure after WebLogic Platform and WebLogic Sip Server installation should look as
follows:
31-Jul-2017
BEA Systems, Inc.
Page 2
Demonstration Application Installation & Configuration
Figure 3.1
The BEA home directory used to install WebLogic Platform is <drive:>\bea815. WebLogic Sip Server is
installed in the directory wlss210 under the BEA home directory.
4
Conference Application demo files
The conference application demonstration package contains the following files:
Filename
Description
wlss-example.jar
WebLogic template to create a WebLogic Workshop enabled SIP
domain
ConferenceApp.zip
Zip file containing the WebLogic Workshop based SIP Conference
Application including source
ConferenceApp.ear
SIP Conference Application
conference-config.xml
Configuration file used by SIP Conference Application
proxy.war
SIP proxy and registrar used by the SIP Conference Application
Table 4.1
5
Creating and Configuring SIP Application Domain
Create a new WebLogic SIP Domain using the Start menu start→Programs→BEA WebLogic SIP
Server 2.1.0→Configuration Wizard as follows:
31-Jul-2017
BEA Systems, Inc.
Page 3
Demonstration Application Installation & Configuration
Figure 5.1
The following window will be displayed.
Figure 5.2
Use the default selection to create a new WebLogic Configuration.
The conference application is built using WebLogic Workshop. As a result we have to create a WebLogic
configuration or domain that supports WebLogic Workshop and SIP applications. Presently, a template to
create such a configuration is not available out of the box. As a result, you have to use the configuration
template file: wlss-example.jar provided with the conference demo package to create your WebLogic
domain or configuration. Please copy the wlss-example.jar file to the following location.
31-Jul-2017
BEA Systems, Inc.
Page 4
Demonstration Application Installation & Configuration
<BEA_HOME>\wlss210\common\templates\domains.
If your BEA_HOME is d:\bea the directory would be as follows:
d:\bea\wlss210\common\templates\domains
After you have copied the file, click Next on the BEA WebLogic Configuration Wizard window.
The following screen will be displayed.
Figure 5.3
Select BEA “WebLogic SIP Server Domain with findme” under the Templates section and click Next.
Select default (Express) in the following screen and click on Next. Provide the Administrative Username
and Password (say weblogic and weblogic) for the WebLogic configuration in the next screen i.e.
Configure Administrative Username and Password. Click on Next. The following screen will be displayed.
31-Jul-2017
BEA Systems, Inc.
Page 5
Demonstration Application Installation & Configuration
Figure 5.4
Select Development Mode and Sun JDK as shown above and click Next. The Create WebLogic
Configuration window will be displayed. Enter a Configuration Name (say conferenceapp) and click on
Create to create your WebLogic Configuration or Domain.
If your BEA_HOME is d:\bea and configuration name is conferenceapp, the WebLogic domain will be
created under following directory:
D:\bea\user_projects\domains\conferenceapp
The files contained in this directory are as follows:
31-Jul-2017
BEA Systems, Inc.
Page 6
Demonstration Application Installation & Configuration
Figure 5.5
The startWebLogic.cmd and stopWebLogic.cmd commands may be used to start or stop the WebLogic
domain. Before you start the WebLogic domain, please make the following changes to the
startWebLogic.cmd file. This is required to setup the correct CLASSPATH for WebLogic Workshop
application. Please modify your WLS_HOME appropriately below.
1. Add the following lines after: set SERVER_NAME=myserver
if "%DEBUG_PORT%"=="" (
set DEBUG_PORT=8453
)
set WLS_HOME=D:\bea\weblogic81
set ARDIR=%WLS_HOME%\server\lib
set JAVA_DEBUG=-Xdebug -Xnoagent Xrunjdwp:transport=dt_socket,address=%DEBUG_PORT%,server=y,suspend=n -Djava.compiler=NONE
set JAVA_OPTIONS=%JAVA_OPTIONS% -ea -da:com.bea... -da:javelin... -da:weblogic...
31-Jul-2017
BEA Systems, Inc.
Page 7
Demonstration Application Installation & Configuration
2. Modify CLASSPATH as follows:
Change CLASSPATH from:
set
CLASSPATH=%WEBLOGIC_CLASSPATH%;%POINTBASE_CLASSPATH%;%JAVA_HOME%\jre\lib\rt.j
ar;%WL_HOME%\server\lib\webservices.jar;%CLASSPATH%
To:
set
CLASSPATH=%WLS_HOME%\javelin\lib\javelin.jar;%ARDIR%\weblogic_knex_patch.jar;%WLS_HOME
%\common\lib\log4j.jar;%ARDIR%\debugging.jar;%ARDIR%\knex.jar;%ARDIR%\wlw-lang.jar;
%ARDIR%\xbean.jar;%WEBLOGIC_CLASSPATH%;%POINTBASE_CLASSPATH%;%JAVA_HOME%\jr
e\lib\rt.jar;%WL_HOME%\server\lib\webservices.jar;%CLASSPATH%
3. Modify java execution command as follows:
From:
%JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% Dweblogic.Name=%SERVER_NAME% -Dweblogic.ProductionModeEnabled=%PRODUCTION_MODE%
-Djava.security.policy="%WL_HOME%\server\lib\weblogic.policy" weblogic.Server
To:
%JAVA_HOME%\bin\java %JAVA_VM% %JAVA_DEBUG% %MEM_ARGS% %JAVA_OPTIONS% Dwlw.testConsole=true -Dwlw.iterativeDev=true -Dweblogic.Name=%SERVER_NAME% Dweblogic.ProductionModeEnabled=%PRODUCTION_MODE% Djava.security.policy="%WL_HOME%\server\lib\weblogic.policy" weblogic.Server
Copy the ConferenceApp.ear application which is part of the conference application demonstration
package to the following location.
D:\bea\user_projects\domains\conferenceapp\applications
Copy the conference-config.xml xml file which is part of the conference application demonstration
package to the following location.
D:\bea\user_projects\domains\conferenceapp
31-Jul-2017
BEA Systems, Inc.
Page 8
Demonstration Application Installation & Configuration
The contents of the conference-config.xml is shown below:
<?xml version="1.0" encoding="UTF-8"?>
<conference-config xmlns="http://www.bea.com/appserver/conferencing">
<LocalAddress>172.16.38.139</LocalAddress>
<ProxyAddress>gats-sj1</ProxyAddress>
<MediaServerAddress>10.60.32.132</MediaServerAddress>
</conference-config>
The LocalAddress is the IP Address of the application machine, the machine where WebLogic domain is
created. The ProxyAddress is the IP Address of the machine where the Proxy/Register domain is located.
This is described in the next section. The MediaServerAddress is the IP Address where the Media Server
(BrookTrout SnowShore server in this case) is installed. Please update these values appropriately for
your configuration.
This completes the creation and configuration of the SIP Application domain and deployment of the SIP
Conferencing application used for the Conference demonstration.
6
Creating and Configuring SIP Proxy/Registrar Domain
Install WebLogic SIP Server 2.1 on a separate machine (say proxy machine) using the instructions
provided earlier. You do not have to install WebLogic Platform 8.1 SP5 on this separate machine. We will
be creating a new SIP domain on a separate machine for the Proxy and Registrar for simplicity only.
(Alternatively, if the SIP proxy/registrar domain is configured to listen on a separate port, instead of the
default 5060, we can host the proxy/registrar domain on the same machine as the SIP application
machine.)
Create a new SIP domain on this separate machine using the Start menu: start→Programs→BEA
WebLogic SIP Server 2.1.0→Configuration Wizard
Select the default options to create the new domain. If you have installed WebLogic SIP Server in d:\bea
and created a WebLogic Configuration with the name proxy_registrar, your domain will be located at:
D:\bea\user_projects\domains\proxy_registrar
Copy the proxy.war web application which is part of the conference application demonstration package to
the following location.
D:\bea\user_projects\domains\proxy_registrar\applications
This completes the creation and configuration of the SIP Proxy/Registrar domain and deployment of the
SIP Proxy and Registrar application used for the Conference demonstration.
31-Jul-2017
BEA Systems, Inc.
Page 9
Demonstration Application Installation & Configuration
7
Executing Conference Application
To run the Conference Application please execute the following steps.
1. Start Media Server using the media server start instructions
2. Start the WebLogic SIP Proxy/Registrar domain: proxy_registrar using startWebLogic.cmd
located in the domain directory in the proxy machine.
3. Start the WebLogic SIP Application domain: conferenceapp using startWebLogic.cmd located in
the domain directory in the application machine.
4. Start the Conference Administration web application using the following URL:
http://<application machine IP Address>:7001/WebApp/conference/index.jsp
assuming that you have WebLogic Server SIP application domain listening on port 7001 (default).
The following screen will be displayed:
Figure 7.1
31-Jul-2017
BEA Systems, Inc.
Page 10
Demonstration Application Installation & Configuration
Click on Login to log into the conference application administration console using the WebLogic
configuration administrative username and password (weblogic and weblogic if that is what you
have configured earlier). This takes you to the Conference Desktop screen as shown below:
Figure 7.2
Use Create to create a new conference and Monitor to view and/or administer conferences.
7.1 CREATING A CONFERENCE
To Create a new conference enter Conference Host name and a valid email address where the
Conference details will be mailed to as shown in Figure 7.3. You may enter multiple email
addresses separated by comma to send the conference details to multiple conferees who will be
attending the conference. The screen Figure 7.4 confirms the successful creation of a
conference. This screen provides the Conference ID and PIN for conferees to join the
conference. This information is also sent in an email to the email address provided during
conference creation as shown below:
Conference ID: sip:[email protected] Pin: 8767
31-Jul-2017
BEA Systems, Inc.
Page 11
Demonstration Application Installation & Configuration
Figure 7.3
31-Jul-2017
BEA Systems, Inc.
Page 12
Demonstration Application Installation & Configuration
Figure 7.4
You may join the conference using a SIP enabled handset or a terminal phone (e.g., Xten
eyebeam) using the Conference ID provided above and then key in the PIN when prompted for
the same.
Figure 7.5
You may use audio or video mode for connecting to the conference.
31-Jul-2017
BEA Systems, Inc.
Page 13
Demonstration Application Installation & Configuration
7.2 MONITORING/CONFERENCE ADMINISTRATION
To monitor and/or administer conferences click on Monitor on Conference Desktop screen.
Figure 7.5
This screen lists the conferences that were created. It also provides the number of conferees
presently connected to the conference.
Click on the Conference ID to obtain more details on the conference and/or remove conference,
terminate/mute conferee. The following screen (Figure 7.6) will be displayed. The Terminate and
Mute/Unmute links next to each conferee in the List of Conferees can be used to terminate,
mute/unmute a conferee respectively. You may also remove the conference by using the Remove
Conference button.
31-Jul-2017
BEA Systems, Inc.
Page 14
Demonstration Application Installation & Configuration
Figure 7.6
The Conference Application Administration console was built using simple ui widgets and is for
demonstration only. In actual implementation, more complex widgets may be used to enhance
the functionality and for better user experience.
31-Jul-2017
BEA Systems, Inc.
Page 15