 |
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | | How to start the server
- Go to the directory where you unpackaged the server
| |
< < |
- From there run: ./bin/run.<sh|bat> -c all -b < 127.0.0.1 or your machine IP address >
| > > |
- From there run: ./bin/run.<sh|bat> ( use "-b IP_Address" if you don't want to use default 127.0.0.1)
| | |
-
- an example for Windows:
- cd c:\devtools\mobicents
| |
< < |
-
- bin\run.bat -c all -b 127.0.0.1 == bin/run.(sh|bat) -mc
- Note that Mobicents 1.2.x distros are based on JBoss Application Server 4.2 and simply executing "run -c all" is equivalent to "run -c all -b 127.0.0.1" or in other words it binds to the loopback interface by default.
| > > |
-
- bin\run.bat -b 192.168.1.1
| | | How to build and run Mobicents from source code | |
< < | How to build Mobicents 1.2.x | > > |
- To start the server execute run.sh/run.bat, as for the binary release, in $JBOSS_HOME/bin
| | | | |
< < |
- Mobicents can be built via ant or Eclipse for this project. The ant files and Eclipse project files and libraries you need are all included with the project on cvs.
- Download from cvs (make sure you don't download Mobicents to a directory containing whitespaces which will lead to classpath problems).
- Edit your environment and set up the MOBICENTS_HOME environment variable to point to the directory where you downloaded Mobicents.
- Download JBoss Application Server binary. Mobicents 1.2.x works with JBoss AS 4.2.x.
- Install JDK 1.5.
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed JBoss. You need to setup JBOSS_HOME Classpath Variable in the IDE (Preferences>Java>Buildpath)
- To start the server execute run.sh/run.bat, as for the binary release, in JBOSS_HOME/bin
How to build Mobicents 1.0.x
- Mobicents can be built via ant or Eclipse for this project. The ant files and Eclipse project files and libraries you need are all included with the project on cvs.
- Download from cvs (make sure you don't download Mobicents to a directory containing whitespaces which will lead to classpath problems).
- If you downloaded from CVS using a tag till v1_0_03_GA-d20070725-b1774, edit your environment and set up the MOBICENTS_HOME environment variable to point to the directory where you downloaded Mobicents.
- Download JBoss Application Server binary. Mobicents source till v1_0_03_GA-d20070725-b1774 works with JBoss 3.2.x, other new versions, including CVS Head, work only with JBoss 4.x.
- Install JDK 1.5.
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed JBoss. If you plan to use Eclipse with Mobicents newer than v1_0_03_GA-d20070725-b1774, then you need to setup JBOSS_HOME Classpath Variable in the IDE (Preferences>Java>Buildpath)
- To start the server execute run.sh/run.bat, as for the binary release, in JBOSS_HOME/bin
. | | | The SLEE 1.0 Technology Compatibility Kit (TCK)
- For development convenience, the TCK is included in the Mobicents CVS module along with the appropriate license files and credits to the original authors.
- The TCK is pre-configured to run against an active Mobicents server on the local machine.
Run the TCK and Custom Tests | |
< < |
- start Mobicents using "run-tck" script instead of "run" (both in $JBOSS_HOME/bin)
- cd $project_home
- ant all-tests
| > > |
- start Mobicents
- in your command line go to dir core/legacy/tests inside Mobicents maven project
- execute "ant"
| | |
- If you want to filter tests then use -Dtests= testpattern, where testpattern is a file pattern such as tests/sbb/abstractclass or tests/sbb/abstractclass/Test522Test
- Here is a full command line example, which runs one particular test - Test522Test
| |
< < | ant all-tests -Dtests=tests/sbb/abstractclass/Test522Test | > > | ant -Dtests=tests/sbb/abstractclass/Test522Test | | |
The output should be something like this: | | | Total time: 4 seconds
| |
< < |
- Some tests should fail because Mobicents already uses some JAINSLEE 1.1 APIs: SleeSignatureTest?, SecurityPermissionsTest? and Test4203Test?
| > > | | | |
- NOTE: The tests that are excluded from test runs are located in $project_home/jain-slee-1.0-tck/testsuite/jain-slee-tck-1_0.jtx
Tasks TODO | | |
- open it up goto install() and set a breakpoint there
- Run a tck test and see the server break there.
| |
< < | Using Eclipse Hot Code replacement
Eclipse supports the JVM feature to replace code in a running JVM. For this to be possible, the classes deployed in JBoss must be those compiled by Eclipse and not Ant. Follow these steps:
- do the usual ant make
- goto Project > Clean > Mobicents
- ant hotcode (run the hotcode target)
- start JBoss
Whenever you change classes while JBoss is not running in debug mode, you should run the hotcode target befor starting it.
| | | -- MudumbaiRanganathan - 25 Mar 2005
-- Main.ivelin - 01 May 2005 |
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | |
- The TCK is pre-configured to run against an active Mobicents server on the local machine.
Run the TCK and Custom Tests | |
> > |
- start Mobicents using "run-tck" script instead of "run" (both in $JBOSS_HOME/bin)
| | |
- cd $project_home
- ant all-tests
- If you want to filter tests then use -Dtests= testpattern, where testpattern is a file pattern such as tests/sbb/abstractclass or tests/sbb/abstractclass/Test522Test
| | | Total time: 4 seconds
| |
< < | | > > |
- Some tests should fail because Mobicents already uses some JAINSLEE 1.1 APIs: SleeSignatureTest?, SecurityPermissionsTest? and Test4203Test?
| | |
- NOTE: The tests that are excluded from test runs are located in $project_home/jain-slee-1.0-tck/testsuite/jain-slee-tck-1_0.jtx
Tasks TODO |
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | |
-
- an example for Windows:
- cd c:\devtools\mobicents
- bin\run.bat -c all -b 127.0.0.1 == bin/run.(sh|bat) -mc
| |
> > |
-
- Note that Mobicents 1.2.x distros are based on JBoss Application Server 4.2 and simply executing "run -c all" is equivalent to "run -c all -b 127.0.0.1" or in other words it binds to the loopback interface by default.
| | | How to build and run Mobicents from source code | |
< < | How to build Mobicents | > > | How to build Mobicents 1.2.x
- Mobicents can be built via ant or Eclipse for this project. The ant files and Eclipse project files and libraries you need are all included with the project on cvs.
- Download from cvs (make sure you don't download Mobicents to a directory containing whitespaces which will lead to classpath problems).
- Edit your environment and set up the MOBICENTS_HOME environment variable to point to the directory where you downloaded Mobicents.
- Download JBoss Application Server binary. Mobicents 1.2.x works with JBoss AS 4.2.x.
- Install JDK 1.5.
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed JBoss. You need to setup JBOSS_HOME Classpath Variable in the IDE (Preferences>Java>Buildpath)
- To start the server execute run.sh/run.bat, as for the binary release, in JBOSS_HOME/bin
How to build Mobicents 1.0.x | | |
- Mobicents can be built via ant or Eclipse for this project. The ant files and Eclipse project files and libraries you need are all included with the project on cvs.
- Download from cvs (make sure you don't download Mobicents to a directory containing whitespaces which will lead to classpath problems).
| | | -- Main.eduardomartins - 26 Sept 2007 | |
> > | -- Main.vralev - 24 Nov 2007 | | |
\ No newline at end of file |
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | |
- Download JBoss Application Server binary. Mobicents source till v1_0_03_GA-d20070725-b1774 works with JBoss 3.2.x, other new versions, including CVS Head, work only with JBoss 4.x.
- Install JDK 1.5.
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed JBoss. If you plan to use Eclipse with Mobicents newer than v1_0_03_GA-d20070725-b1774, then you need to setup JBOSS_HOME Classpath Variable in the IDE (Preferences>Java>Buildpath)
| |
< < |
- To start the server consider JBOSS_HOME the server directory and use run.sh/run.bat as for the binary release
| > > |
- To start the server execute run.sh/run.bat, as for the binary release, in JBOSS_HOME/bin
| | | .
The SLEE 1.0 Technology Compatibility Kit (TCK) |
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | |
- Download JBoss Application Server binary. Mobicents source till v1_0_03_GA-d20070725-b1774 works with JBoss 3.2.x, other new versions, including CVS Head, work only with JBoss 4.x.
- Install JDK 1.5.
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed JBoss. If you plan to use Eclipse with Mobicents newer than v1_0_03_GA-d20070725-b1774, then you need to setup JBOSS_HOME Classpath Variable in the IDE (Preferences>Java>Buildpath)
| |
> > |
- To start the server consider JBOSS_HOME the server directory and use run.sh/run.bat as for the binary release
| | | .
The SLEE 1.0 Technology Compatibility Kit (TCK) |
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | |
- Mobicents can be built via ant or Eclipse for this project. The ant files and Eclipse project files and libraries you need are all included with the project on cvs.
- Download from cvs (make sure you don't download Mobicents to a directory containing whitespaces which will lead to classpath problems).
| |
< < |
- Edit your environment and set up the MOBICENTS_HOME environment variable to point to the directory where you downloaded Mobicents.
- Download the optimal JBoss profile required for Mobicents. Alternatively you can use a standard 3.2.8 or 4.2.1 for CVS HEAD binary.
- Install JDK 1.4 But for the error: Unsupported major.minor version 49.0 during building, you may try jdk 1.5, escepcially when you build the newest source code.
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed JBoss.
- Download and install ant.
- ant make
| > > |
- If you downloaded from CVS using a tag till v1_0_03_GA-d20070725-b1774, edit your environment and set up the MOBICENTS_HOME environment variable to point to the directory where you downloaded Mobicents.
- Download JBoss Application Server binary. Mobicents source till v1_0_03_GA-d20070725-b1774 works with JBoss 3.2.x, other new versions, including CVS Head, work only with JBoss 4.x.
- Install JDK 1.5.
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed JBoss. If you plan to use Eclipse with Mobicents newer than v1_0_03_GA-d20070725-b1774, then you need to setup JBOSS_HOME Classpath Variable in the IDE (Preferences>Java>Buildpath)
. | | | The SLEE 1.0 Technology Compatibility Kit (TCK)
- For development convenience, the TCK is included in the Mobicents CVS module along with the appropriate license files and credits to the original authors.
- The TCK is pre-configured to run against an active Mobicents server on the local machine.
| |
< < | Start the Container
- Edit the JBoss shell script to increase the default memory settings and enable debugging
- Locate the following lines and make sure they set JAVA_OPTS:
JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m
JAVA_OPTS= -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n %JAVA_OPTS%
For unix environment use:
JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx512m"
JAVA_OPTS=" -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n $JAVA_OPTS"
- Start JBoss using the all configuration with IP address binding to < your machine IP address >
- cd $JBOSS_HOME/bin
- sh run.sh -c all -b < your machine IP address >
Run the TCK | > > | Run the TCK and Custom Tests | | | | |
< < |
- ant tests-slee-tck -Dtests= testpattern
- testpattern is a file pattern such as tests/sbb/abstractclass or tests/sbb/abstractclass/Test522Test
| > > |
- ant all-tests
- If you want to filter tests then use -Dtests= testpattern, where testpattern is a file pattern such as tests/sbb/abstractclass or tests/sbb/abstractclass/Test522Test
| | |
- Here is a full command line example, which runs one particular test - Test522Test
| |
< < | ant tests-slee-tck -Dtests=tests/sbb/abstractclass/Test522Test | > > | ant all-tests -Dtests=tests/sbb/abstractclass/Test522Test | | |
The output should be something like this:
Buildfile: build.xml
| |
< < | tests-slee-tck: | > > | ... | | | tests-slee-tck-internal:
[echo] slee.tck.testsuite=${slee.tck.testsuite} | | | Tips for Debugging the SLEE Container
- You can debug the container by using logging ( preferred by old hacks ) or by running a debugger. Here are some instructions on how to set up to run a debugger.
- go to $JBOSS_HOME/bin and edit run.sh or run.bat and look for the following line
| |
< < |
- rem Sun JVM memory allocation pool parameters. Uncomment and modify as appropriate.
- set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m
| | |
- rem JPDA options. Uncomment and modify as appropriate to enable remote debugging. Note suspend=y line
- set JAVA_OPTS= -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y %JAVA_OPTS%
- start jboss with these options
| | | -- Main.ivelin - 01 May 2005 | |
> > | -- Main.eduardomartins - 26 Sept 2007 | | |
|
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | |
- From there run: ./bin/run.<sh|bat> -c all -b < 127.0.0.1 or your machine IP address >
- an example for Windows:
- cd c:\devtools\mobicents
| |
< < |
-
- bin\run.bat -c all -b 127.0.0.1
| > > |
-
- bin\run.bat -c all -b 127.0.0.1 == bin/run.(sh|bat) -mc
| | | How to build and run Mobicents from source code | | |
- Mobicents can be built via ant or Eclipse for this project. The ant files and Eclipse project files and libraries you need are all included with the project on cvs.
- Download from cvs (make sure you don't download Mobicents to a directory containing whitespaces which will lead to classpath problems).
- Edit your environment and set up the MOBICENTS_HOME environment variable to point to the directory where you downloaded Mobicents.
| |
< < | | > > |
- Download the optimal JBoss profile required for Mobicents. Alternatively you can use a standard 3.2.8 or 4.2.1 for CVS HEAD binary.
- Install JDK 1.4 But for the error: Unsupported major.minor version 49.0 during building, you may try jdk 1.5, escepcially when you build the newest source code.
| | |
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed JBoss.
- Download and install ant.
- ant make
|
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | | How to build Mobicents
- Mobicents can be built via ant or Eclipse for this project. The ant files and Eclipse project files and libraries you need are all included with the project on cvs.
| |
< < |
- Download from cvs (make sure you don't download mobicents to a directory containing whitespaces which will lead to classpath problems)
| > > |
- Download from cvs (make sure you don't download Mobicents to a directory containing whitespaces which will lead to classpath problems).
- Edit your environment and set up the MOBICENTS_HOME environment variable to point to the directory where you downloaded Mobicents.
| | | | |
< < |
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed jboss
- Download and install ant
| > > |
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed JBoss.
- Download and install ant.
| | |
The SLEE 1.0 Technology Compatibility Kit (TCK) |
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | |
- Mobicents can be built via ant or Eclipse for this project. The ant files and Eclipse project files and libraries you need are all included with the project on cvs.
- Download from cvs (make sure you don't download mobicents to a directory containing whitespaces which will lead to classpath problems)
| |
< < | | > > | | | |
- Install JDK 1.4
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed jboss
- Download and install ant
|
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | |
- Mobicents can be built via ant or Eclipse for this project. The ant files and Eclipse project files and libraries you need are all included with the project on cvs.
- Download from cvs (make sure you don't download mobicents to a directory containing whitespaces which will lead to classpath problems)
| |
< < | | > > | | | |
- Install JDK 1.4
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed jboss
- Download and install ant
|
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | |
< < | Here are Some Getting Started instructions. The purpose of this document is to guide you through setting up Mobicents and the TCK so you can begin hacking. It is distilled from notes on the Mobicents Forum posted by Ralf Siedow who figured out some fine details in how to plumb mobicents to talk to the TCK.
We recently completed the SLEE 1.0 certification process and are in planning stage for the next release. In the mean while we will add more tests to complement the TCK and further stabilize the code base to prepare for 1.0 Beta release. | | |
How to install and run a Mobicents binary distribution |
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | | | |
> > | How to install and run a Mobicents binary distribution
Where to download the distro
To download the binary distribution, follow the link on the mobicents front page, which links to the latest version. It will read something like " Mobicents Suite x.y.z Released".
Once you download the server, unzip it in a new directory on your disk. Make sure the full path to the directory does not contain white spaces.
How to start the server
- Go to the directory where you unpackaged the server
- From there run: ./bin/run.<sh|bat> -c all -b < 127.0.0.1 or your machine IP address >
- an example for Windows:
- cd c:\devtools\mobicents
- bin\run.bat -c all -b 127.0.0.1
How to build and run Mobicents from source code | | | How to build Mobicents | |
< < |
- We use Eclipse for this project. The project files and libraries you need are all included with the project on cvs.
| > > |
- Mobicents can be built via ant or Eclipse for this project. The ant files and Eclipse project files and libraries you need are all included with the project on cvs.
| | | |
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | |
- cd $project_home
- ant tests-slee-tck -Dtests= testpattern
- testpattern is a file pattern such as tests/sbb/abstractclass or tests/sbb/abstractclass/Test522Test
| |
< < |
- Many tests still fail -- this is a set of instructions for potential contributors!
- try the tests under activities for example. Right click on the individual test and run it.
| > > |
- Here is a full command line example, which runs one particular test - Test522Test
ant tests-slee-tck -Dtests=tests/sbb/abstractclass/Test522Test
The output should be something like this:
Buildfile: build.xml
tests-slee-tck:
tests-slee-tck-internal:
[echo] slee.tck.testsuite=${slee.tck.testsuite}
[echo] Starting TCK with params: -batch 'testsuite ...
[echo] Excluding tests listed in file: ${slee.tck.testsuite}/jain-slee-tck-1_0.jtx
[java] Starting test suite...
[java] Test results: passed: 1
[java] Results written to C:\work\mobicents\jain-slee-1.0-tck\tckwork.
[java] Report written to C:\work\mobicents\jain-slee-1.0-tck\reports
[echo] SLEE TCK report available at C:/work/mobicents/jain-slee-1.0-tck/reports/report.html
BUILD SUCCESSFUL
Total time: 4 seconds
| | |
- NOTE: The tests that are excluded from test runs are located in $project_home/jain-slee-1.0-tck/testsuite/jain-slee-tck-1_0.jtx
Tasks TODO |
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | | -- MudumbaiRanganathan - 25 Mar 2005
-- Main.ivelin - 01 May 2005 | |
> > |
|
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | | How to build Mobicents
- We use Eclipse for this project. The project files and libraries you need are all included with the project on cvs.
- Download from cvs (make sure you don't download mobicents to a directory containing whitespaces which will lead to classpath problems)
| |
< < | | > > | | | |
- Install JDK 1.4
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed jboss
- Download and install ant
|
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | | How to build Mobicents
- We use Eclipse for this project. The project files and libraries you need are all included with the project on cvs.
- Download from cvs (make sure you don't download mobicents to a directory containing whitespaces which will lead to classpath problems)
| |
< < | | > > | | | |
- Install JDK 1.4
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed jboss
- Download and install ant
|
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | |
How to build Mobicents | |
< < |
- We use Eclipse for this project. The project files and libraries you need are all included with the project on cvs.
- Download from cvs (make sure you don't download mobicents to a directory containing whitespaces which will lead to classpath problems)
- Download jboss-3.2.6
- Install JDK 1.4
| > > | | | |
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed jboss
- Download and install ant
- ant make
|
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | |
- Run a tck test and see the server break there.
Using Eclipse Hot Code replacement | |
< < | Eclipse supports the JVM feature to replace code in a running JVM. For this to be possible the classes deployed in JBoss must be those compiled by Eclipse and not Ant. Follow this steps: | > > | Eclipse supports the JVM feature to replace code in a running JVM. For this to be possible, the classes deployed in JBoss must be those compiled by Eclipse and not Ant. Follow these steps: | | |
- do the usual ant make
- goto Project > Clean > Mobicents
- ant hotcode (run the hotcode target)
- start JBoss
| |
< < | Whenever you change classes while JBoss is not running in debug mode you should run the hotcode target befor starting it. | > > | Whenever you change classes while JBoss is not running in debug mode, you should run the hotcode target befor starting it. | | |
|
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
| |
< < | A Quick Start Guide to Mobicents | > > | A Quick Start Guide to Mobicents | | | Here are Some Getting Started instructions. The purpose of this document is to guide you through setting up Mobicents and the TCK so you can begin hacking. It is distilled from notes on the Mobicents Forum posted by Ralf Siedow who figured out some fine details in how to plumb mobicents to talk to the TCK.
We recently completed the SLEE 1.0 certification process and are in planning stage for the next release. In the mean while we will add more tests to complement the TCK and further stabilize the code base to prepare for 1.0 Beta release. | |
> > | | | | How to build Mobicents
- We use Eclipse for this project. The project files and libraries you need are all included with the project on cvs.
- Download from cvs (make sure you don't download mobicents to a directory containing whitespaces which will lead to classpath problems)
| | |
- NOTE: The tests that are excluded from test runs are located in $project_home/jain-slee-1.0-tck/testsuite/jain-slee-tck-1_0.jtx
Tasks TODO | |
< < |
- Don't take on tasks for which you don't have enough time or do not have the inclination to complete. This is a team effort. Others are depending on you.
- Here is the latest TCK results report.. Watch it as you commit changes. We MUST maintain 100% TCK compliance at ALL times.
- The data structures that track deployment dependencies need to be put into the JBoss Cache to guarantee consistent transactional isolation. - In progress. Ranga is working on this.
- We need to make the deployment transactional across multiple nodes. Assigned to Ivelin.
- We need an End to end proxy example. Assigned to Francesco Moggia. Partially complete.
- We need a more optimal transactional cache layer that takes advantage of the SLEE read-mostly semantics. Not assigned.
- We need to start experimenting with multi-threaded event routing with dynamic priority queue.
- An automated build task, which generates installer. It should allow users to pick the core SLEE engine and optional components such as RAs (SIP, Asterisk) and Services (SIP Registrar). One open source installer tool that works is lzPack.
| > > | Look at the TODO list and pick a task that you want to work on. Send a message to the contributors forum that you are interested to work on a certain task. Specify how much time you can dedicate and what portion of the task you can complete. | | | Tips for Debugging the SLEE Container
- You can debug the container by using logging ( preferred by old hacks ) or by running a debugger. Here are some instructions on how to set up to run a debugger.
|
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | |
- Don't take on tasks for which you don't have enough time or do not have the inclination to complete. This is a team effort. Others are depending on you.
- Here is the latest TCK results report.. Watch it as you commit changes. We MUST maintain 100% TCK compliance at ALL times.
- The data structures that track deployment dependencies need to be put into the JBoss Cache to guarantee consistent transactional isolation. - In progress. Ranga is working on this.
| |
< < |
- We need to make the deployment transactional across multiple nodes. Assigned to Ivelin / Jean Noel.
| > > |
- We need to make the deployment transactional across multiple nodes. Assigned to Ivelin.
| | |
- We need an End to end proxy example. Assigned to Francesco Moggia. Partially complete.
- We need a more optimal transactional cache layer that takes advantage of the SLEE read-mostly semantics. Not assigned.
- We need to start experimenting with multi-threaded event routing with dynamic priority queue.
|
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | | How to build Mobicents
- We use Eclipse for this project. The project files and libraries you need are all included with the project on cvs.
| |
< < | | > > |
- Download from cvs (make sure you don't download mobicents to a directory containing whitespaces which will lead to classpath problems)
| | |
- Download jboss-3.2.6
- Install JDK 1.4
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed jboss
| | |
- open it up goto install() and set a breakpoint there
- Run a tck test and see the server break there.
| |
< < | | > > | Using Eclipse HotCode? replacement
Eclipse supports the JVM feature to replace code in a running JVM. For this to be possible the classes deployed in JBoss must be those compiled by Eclipse and not Ant. Follow this steps:
- do the usual ant make
- goto Project > Clean > Mobicents
- ant hotcode (run the hotcode target)
- start JBoss Whenever you change classes while JBoss is not running in debug mode you should run the hotcode target befor starting it.
| | |
|
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents
Here are Some Getting Started instructions. The purpose of this document is to guide you through setting up Mobicents and the TCK so you can begin hacking. It is distilled from notes on the Mobicents Forum posted by Ralf Siedow who figured out some fine details in how to plumb mobicents to talk to the TCK. | |
< < | We are currently working our way through the TCK and developing and debugging at the same time (I guess thats what they must mean by test driven development) . In other words, don't expect the TCK tests to all pass - this is a work in progress . | > > | We recently completed the SLEE 1.0 certification process and are in planning stage for the next release. In the mean while we will add more tests to complement the TCK and further stabilize the code base to prepare for 1.0 Beta release. | | | How to build Mobicents
- We use Eclipse for this project. The project files and libraries you need are all included with the project on cvs.
| | | Tasks TODO
- Don't take on tasks for which you don't have enough time or do not have the inclination to complete. This is a team effort. Others are depending on you.
| |
< < | | > > | | | |
- The data structures that track deployment dependencies need to be put into the JBoss Cache to guarantee consistent transactional isolation. - In progress. Ranga is working on this.
- We need to make the deployment transactional across multiple nodes. Assigned to Ivelin / Jean Noel.
- We need an End to end proxy example. Assigned to Francesco Moggia. Partially complete.
|
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | |
- We need an End to end proxy example. Assigned to Francesco Moggia. Partially complete.
- We need a more optimal transactional cache layer that takes advantage of the SLEE read-mostly semantics. Not assigned.
- We need to start experimenting with multi-threaded event routing with dynamic priority queue.
| |
> > |
- An automated build task, which generates installer. It should allow users to pick the core SLEE engine and optional components such as RAs (SIP, Asterisk) and Services (SIP Registrar). One open source installer tool that works is lzPack.
| | | Tips for Debugging the SLEE Container
- You can debug the container by using logging ( preferred by old hacks ) or by running a debugger. Here are some instructions on how to set up to run a debugger.
|
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | | Tasks TODO
- Don't take on tasks for which you don't have enough time or do not have the inclination to complete. This is a team effort. Others are depending on you.
| |
< < | | > > | | | |
- The data structures that track deployment dependencies need to be put into the JBoss Cache to guarantee consistent transactional isolation. - In progress. Ranga is working on this.
- We need to make the deployment transactional across multiple nodes. Assigned to Ivelin / Jean Noel.
| |
< < |
- End to end proxy example. Assigned to Francesco Moggia.
| > > |
- We need an End to end proxy example. Assigned to Francesco Moggia. Partially complete.
- We need a more optimal transactional cache layer that takes advantage of the SLEE read-mostly semantics. Not assigned.
- We need to start experimenting with multi-threaded event routing with dynamic priority queue.
| | | Tips for Debugging the SLEE Container
- You can debug the container by using logging ( preferred by old hacks ) or by running a debugger. Here are some instructions on how to set up to run a debugger.
|
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | | JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx512m"
JAVA_OPTS=" -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n $JAVA_OPTS"
| |
< < |
- Start JBoss using the all configuration with IP address binding to 127.0.0.1
| > > |
- Start JBoss using the all configuration with IP address binding to < your machine IP address >
| | | | |
< < |
- sh run.sh -c all -b 127.0.0.1
| > > |
- sh run.sh -c all -b < your machine IP address >
| | | Run the TCK |
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | | Tasks TODO
- Don't take on tasks for which you don't have enough time or do not have the inclination to complete. This is a team effort. Others are depending on you.
| |
< < | | > > | | | |
- The data structures that track deployment dependencies need to be put into the JBoss Cache to guarantee consistent transactional isolation. - In progress. Ranga is working on this.
- We need to make the deployment transactional across multiple nodes. Assigned to Ivelin / Jean Noel.
- End to end proxy example. Assigned to Francesco Moggia.
| |
> > | Tips for Debugging the SLEE Container
- You can debug the container by using logging ( preferred by old hacks ) or by running a debugger. Here are some instructions on how to set up to run a debugger.
- go to $JBOSS_HOME/bin and edit run.sh or run.bat and look for the following line
- rem Sun JVM memory allocation pool parameters. Uncomment and modify as appropriate.
- set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m
- rem JPDA options. Uncomment and modify as appropriate to enable remote debugging. Note suspend=y line
- set JAVA_OPTS= -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y %JAVA_OPTS%
- start jboss with these options
- On Eclipse, Click on the little Run menu, then on "Debug..."
- Click on Remote Java App ( maybe double click to get a new instance and name it Mobicents )
- On the connect Tab
- for connection type, standard, socket
- for host localhost
- for port 8787
- Check Allow Termination
- on the Source tab select mobicents and jain-slee-1.0-tck(optional)
- Apply, close
- Now Click on Run menu, Debug As, Mobicents
- Ctrl+Shift+T ( brings up a list of types )
- start typing [DeploymentMBeanImpl]
- open it up goto install() and set a breakpoint there
- Run a tck test and see the server break there.
| | | |
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents | | |
- Here is a list of tests that dont work yet. Pick a test from this list, put your name next to it by editing the wiki page, roll up your sleeves, put on your programming hat and hack on it till it works!
- The data structures that track deployment dependencies need to be put into the JBoss Cache to guarantee consistent transactional isolation. - In progress. Ranga is working on this.
- We need to make the deployment transactional across multiple nodes. Assigned to Ivelin / Jean Noel.
| |
< < |
- End to end proxy example. Assigned to Francesco Moggia
| > > |
- End to end proxy example. Assigned to Francesco Moggia.
| | |
|
|
> > |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
A Quick Start Guide to Mobicents
Here are Some Getting Started instructions. The purpose of this document is to guide you through setting up Mobicents and the TCK so you can begin hacking. It is distilled from notes on the Mobicents Forum posted by Ralf Siedow who figured out some fine details in how to plumb mobicents to talk to the TCK.
We are currently working our way through the TCK and developing and debugging at the same time (I guess thats what they must mean by test driven development) . In other words, don't expect the TCK tests to all pass - this is a work in progress .
How to build Mobicents
- We use Eclipse for this project. The project files and libraries you need are all included with the project on cvs.
- Download from cvs
- Download jboss-3.2.6
- Install JDK 1.4
- Edit your environment and set up the JBOSS_HOME environment variable to point to where you installed jboss
- Download and install ant
- ant make
The SLEE 1.0 Technology Compatibility Kit (TCK)
- For development convenience, the TCK is included in the Mobicents CVS module along with the appropriate license files and credits to the original authors.
- The TCK is pre-configured to run against an active Mobicents server on the local machine.
Start the Container
- Edit the JBoss shell script to increase the default memory settings and enable debugging
- Locate the following lines and make sure they set JAVA_OPTS:
JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m
JAVA_OPTS= -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n %JAVA_OPTS%
For unix environment use:
JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx512m"
JAVA_OPTS=" -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n $JAVA_OPTS"
- Start JBoss using the all configuration with IP address binding to 127.0.0.1
- cd $JBOSS_HOME/bin
- sh run.sh -c all -b 127.0.0.1
Run the TCK
- cd $project_home
- ant tests-slee-tck -Dtests= testpattern
- testpattern is a file pattern such as tests/sbb/abstractclass or tests/sbb/abstractclass/Test522Test
- Many tests still fail -- this is a set of instructions for potential contributors!
- try the tests under activities for example. Right click on the individual test and run it.
- NOTE: The tests that are excluded from test runs are located in $project_home/jain-slee-1.0-tck/testsuite/jain-slee-tck-1_0.jtx
Tasks TODO
- Don't take on tasks for which you don't have enough time or do not have the inclination to complete. This is a team effort. Others are depending on you.
- Here is a list of tests that dont work yet. Pick a test from this list, put your name next to it by editing the wiki page, roll up your sleeves, put on your programming hat and hack on it till it works!
- The data structures that track deployment dependencies need to be put into the JBoss Cache to guarantee consistent transactional isolation. - In progress. Ranga is working on this.
- We need to make the deployment transactional across multiple nodes. Assigned to Ivelin / Jean Noel.
- End to end proxy example. Assigned to Francesco Moggia
-- MudumbaiRanganathan - 25 Mar 2005
-- Main.ivelin - 01 May 2005 |
|