JBoss.orgCommunity Documentation
Ensure that the following requirements have been met before continuing with the install.
Downloading the source code
Subversion is used to manage its source code. Instructions for using Subversion, including install, can be found at http://svnbook.red-bean.com
Use SVN to checkout a specific release source, the base URL is http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/tools/remote-slee-connection, then add the specific release version, lets consider 2.7.0.FINAL.
[usr]$ svn co http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/tools/remote-slee-connection/2.7.0.FINAL remote-slee-connection-2.7.0.FINAL
Building the source code
Maven 2.0.9 (or higher) is used to build the release. Instructions for using Maven2, including install, can be found at http://maven.apache.org
Use Maven to build the deployable unit binary.
[usr]$ cd remote-slee-connection-2.7.0.FINAL [usr]$ mvn install
Once the process finishes you should have the JCA
mobicents-slee-remote-connection.rar directory artifact in the target/mobicents-slee-remote-connection.rar-beans
directory. Deploying the JCA connector depends on the Java EE platform used, in case of JBoss Enterprise Application Platform simply copy the directory artifact to the platform's deploy directory.
Similar process as for Section 2.2.1, “Release Source Code Building”, the only change is the SVN source code URL, which is http://mobicents.googlecode.com/svn/trunk/servers/jain-slee/tools/remote-slee-connection.
To install the tool to the JBoss Enterprise Application Platform simply copy the provided mobicents-slee-remote-connection.rar
directory into the deploy
directory of the target server profile.
For other Java EE platforms please refer to its documentation on how to deploy the JCA connector.
To uninstall the tool from the JBoss Enterprise Application Platform simply delete the mobicents-slee-remote-connection.rar
directory from the deploy
directory of the target server profile.
For other Java EE platforms please refer to its documentation on how to undeploy the JCA connector.