Installation Guide

GlobalMMCS System Package

    
 

      GlobalMMCS have three packages: Core services package, H.323 package and RealStreaming package.

     After you download the globalmmcs-bin-1.0.zip file  and unzip it onto the directory GlobalMMCS-Package, you can find under this directory:

      (1) build.xml, build.properties:       They are the build files for Ant. GlobalMMCS needs Apache Ant to deploy the servers. The parameters for the deployment are defined in build.properties.

      (2) jakarta-tomcat-4.1.30.tar:      GlobalMMCS uses Apache Tomcat as the web server container.

(3)WebServer : Servelet and JSP based Global-MMCS Portal

      (4) MediaServer: Multimedia Conferencing Services

      (5) SessionServer: A/V Conferencing Session Services

      (6) H323GW: H.323 Gateway and H323 Gatekeeper Service ( Allowing H.323  clients like Polycom Via Video to connect Globalmmcs )

      (7) RealGW:  RealStreaming Gateway Service ( Produce Real streams from Conferencing A/V streams )

      (8) HelixGW: Generating SMIL description files for Helix Server

After you run Ant to make the deployment, you will find the new destination directory is generated:

Destination Directory ( assumed globalmmcs, for example )

       (1) jakarta-tomcat-4.1.30 ( Globalmmcs Web server is copied under jakata-tomcat-4.1.30/webapps/globalmmcs

       (2) media server       (3) session server  (3) h323gw  (4) realgw  (5)helixgw

Note: Web Server, Media Server  and Session Server are the core services in Global-MMCS, which must be installed. H323 package and RealStreaming package (including RealGW and HelixGW ) are supplementary services, which are optional.

Core service package ( Web server, Media server, Session server ) can be installed in both Linux and windows.

H323 package can be installed in both Linux and windows. But H323 Gateway can only run windows. H323 Gatekeeper can run on both platforms.

RealStreaming package can be installed in both Linux and windows. But RealGW only can only run on windows.

Helix DNA Server is also needed for RealStreaming service, but not included in RealStreaming package. You have to go to http://www.helixcommunity.org to download it.

    

Installation Parameters

    
 

specify the parameters in build.properties

build.properties keeps the important parameters that have to be specified by the administrator. Based on them, Ant can generate the configuration files for all the servers in Global-MMCS.

Parameters

Explaination

Examples

globalmmcs.home

the root path which GlobalMMCS is installed

On Windows: D:/GlobalMMCS

On Linux: /home/globalmmcs

 

globalmmcs.BrokerIP

NardaBroker Server IP Address:

There are serveral parameters for BrokerIP address. Currently they need to be set to the same value since we have only one Broker here

Assume we have two machines for GlobalMMCS installation: 192.2.188.100,192.2.188.101

use 192.2.188.100 as NaradaBroker

webserver.SESSIONSV_ADDR

webserver.H323GW_ADDR

webserver.SIPGW_ADDR

webserver.HelixSV_ADDR

webserver.HelixSV_PORT

webserver.RealGW_ADDR

The following parameters specify the addresses of the application servers

# Session Server, H323Gateway, SIPGateway, Helix Server & Port, RealGateway

192.2.188.100 as Session Server

192.2.188.101 as H323 Gateway

192.2.188.101 as SIP Gateway

192.2.188.101 as Helix Server

6060 as Helix Server RTSP Port

192.2.188.101 as RealStreaming Gateway

mediaserver.BrokerIP

mediaserver.ImageURLPath

 NaradaBroker IP needed by media server

 Image URL for snapshot

192.2.188.100 as NaradaBroker for media server

http://myglobalmmcs:8080/globalmmcs/images

sessionserver.BrokerIP

NaradaBroker IP needed by session server

 

192.2.188.100 as NaradaBroker for session server

h323gw.H323GateKeeperIP

h323gw.SessionServerIP

 H323Gatekeeper IP address

 Session Server IP address

192.2.188.100 as H323 Gatekeeper

192.2.188.101 as session server IP

These two arugments are defined for H.323 Gateway,which has to run in a different machine from H.323 Gatekeeper

DataBase Configuration

webserver.DATABASE_PATH

webserver.DATABASE_URL

webserver.DATABASE_DRIVE

webserver.DATABASE_USER

webserver.DATABASE_PASSWD

 These parameters specify the database server that web server need to connect.

 A DataBase Connection usually needs a 4-turple Configuration: < URL, Driver, UserID, Password>

Database connection url

Class name of the jdbc driver

Database user name

Database password

Assume you are using MySQL Server at: jdbc:mysql://globalmmcs.database/;Table name is globalmmcs; user accound and password are guest/guest,

globammcs as DataBASE_PATH

jdbc:mysql://globalmmcs.database/ as DATABASE_URL

com.mysql.jdbc.Driver as DATABASE_DRIVE

guest/guest as USER and PASSWD

RealStreaming Admin

realgw.HelixAdminUserName

realgw.HelixAdminPasswd

helixgw.HelixServerDir

 These parameters specify the Helix server administor information and home directory for the helix server for example, we have a Helix server admin account like

< myglobalmmcs, myglobalmmcs >

/home/globalmmcs/helix

 

Note: GlobalMMCS can support MySQL , Oracle database and  JBuilder Jdatastore.

    

Installation Steps

    
 

Before you start to install Global-MMCS, you have to decide how many packages are needed for your application. If you only need the core service package, you can install it in on a Linux or windows server. Please follow the instruction (1). If you need RealStreaming package, please follow the instruction (4) to install Helix server and do other installation.

If you need H.323 or RealStreaming package, you have to add another windows box. ( In next version, maybe a Linux box ). And install both of the package in both server boxes ( Linux and windows ).

H.323 gatekeeper have to run a different machine from H.323 gateway which has to run on windows. Suppose you have one Linux box and one Windows box, then run H.323 gatekeeper on Linux and H.323 gateway on Windows.

If you want to install RealStreaming package, you have to install Helix server before any installation. Because the Helix server parameters affect the setting of many compoenents in globalmmcs ( web server, session server, real gateway, helix gateway ).

Please download both producer SDK and server from https://www.helixcommunity.org, which requires accepting some licence aggrements provided by RealNetworks. In order to do that you might need to open an account on Helix Community page. Please follow instruction (3)(4) for RealStreaming package and Helix server installation.

Real gateway has to run on windows box. Suppose you have one Linux box and one Windows box, then run Real Gateway on windows box, and Helix gateway on Linux box. Note Helix gateway has to run in the same machine as Helix server.

(1)   run the Ant to install Globoal-MMCS Core Package

Just run “ant, ( Web Server, Media Server and Session Server will be installed )

(2)  run the Ant to install H323 Package

run "ant H323". ( H323 GW will be installed )

(3) run the Ant to install RealStreaming Package

Download ProducerSDK 10.0 from the following link: https://helix-producer.helixcommunity.org/downloads.htm, and put helixproducersdk_10_windows.zip under the root directory.

run "ant RealStreaming". ( RealGW and HelixGW will be installed )

(4) Install Helix DNA Server

Helix DNA Server can also be downloaded from the following link: https://helix-server.helixcommunity.org/2003/devdocs/builds.html

Please download "servinstplus" installer. After downloading the server package, please install it.

On the Linux machine, run ./servinst_nodist_linux-2.2-libc6-i586-server.bin;

On the window machine, run ./servinst_nodist_win32-i386-vc6.exe

Please follow the instructions by the installer program, write down the parameters for the helix server. Some parameters have to be specified in build.properties.

 Parameters  entry in build.properties  example
Admin User/Password realgw.HelixAdminUserName

realgw.HelixAdminPasswd

myglobalmmcs/myglobalmmcs
RTSP Port webserver.HelixSV_PORT 6060
HTTP Port helixserver.HTTPPort 8088
PNA Port helixserver.PNAPort 7070
Admin Port helixserver.AdminPort 18910
Destination helixgw.HelixServerDir /home/globalmmcs/helix

 

After installation is complete, you have to change the configuration file manually.


copy the configuration file: "default.cfg" to "
hlxserverplus.cfg" and open hlxserverplus.cfg. Go the last line of this XML file and find the part called "Receiver"

The make sure that the The RECEIVER is NOT UNCOMMENTED. If it is you can just remove the comment tags. Here is an example of this.
Also make sure that "password" is same as you admin password.

<!-- R E C E I V E R -->
<List Name="BroadcastReceiver">
<List Name="Receivers">
<!-- Uncomment the "Anyone" Receiver to begin listening for encoder feeds
on port 30001, adjust setttings to suite. -->

<!-- DELETE THIS LINE ...

<List Name="Anyone">
<Var FECLevel="20"/>
<Var UseTCPForPullBackchannel="0"/>
<Var OriginSpec="0.0.0.0/0"/>
<Var AcquisitionDataInterval="30"/>
<List Name="Security">

<Var Password="myglobalmmcs"/>

<Var Type="Basic"/>
</List>
<Var Protocol="udp/unicast"/>
<Var PullSplitEnabled="0"/>
<Var PortRange="30001-30020"/>
<Var ResendSupported="0"/>
</List>

...AND THIS LINE TO UNCOMMENT THE "Anyone" RECEIVER-->
</List>
</List>
 

(5) create database tables and prepare the data

  Global MMCS can support database including mySQL, oracle and JBuilder Jdatastore. After you specify the right parameters for database server ( < URL, Driver, UserID, Password> ) and make sure your database server is working, you can run “ant deploy.globalmmcs.database.conf”. Ant will invoke a SQL script to create four tables in your database server and add some rows into them.

     (6) UnInstall the whole package

   Just run "ant clean". The destination directory will be deleted.