Skip to main content

Auto Deploy SIP RA

7 replies [Last post]
ivelin
Offline
Joined: 2003-07-13

Ranga has not been able to auto deploy the sip ra. I will look at the issue and post progress on this thread.

> Ivelin,
>
> I was not able to get your deployer to work with the proxy. We need the
> following functionality:
>
> 1. Dependency resolution ( ie. install sipra types, sipra and then proxy
> in that order). You mentioned this is specified in
> conf/jboss-service.xml but I cant see how. Maybe its obvious but I dont
> see it. In any case an example would help and to make this truly useful,
> the SIP Proxy and all its dependencies auto deploying would be nice.
>
> 2. Auto start the service after deploy.
>
> If you could please test the ability to install the proxy from auto
> deploy and provide this functionality. I have not been able to do so.
>
> Regards,
>
> Ranga
>

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
mranga
Offline
Joined: 2003-06-06

I am in the meanwhile converting the handy jmx client contribution of Buddy Bright - ie. SleeCommandLineInterface to run from ant rather than a platform dependent batch file. I am converting the ant target - proxydeploy to do this. Note that it appears SLEE extensions to ant are already part of the Open Cloud contribution to EclipseSlee so perhaps we can start to use thse in ant scripts for test automation -- good stuff! Thanks again to OC and Cath.

Ranga

ivelin
Offline
Joined: 2003-07-13

One of the issues is fixed. The sipra script now generates a single deployable - sip-ra.jar instead of the two before: sip-ra-type.jar and sip-local-ra.jar.

ant sipradeploy

now generates sip-ra.jar and copies it to server/all/deploy-mobicents

then it invokes the shell scripts to create entities and activate them.

I am moving on to automating the activation as part of the deployment.

Ivelin

ivelin
Offline
Joined: 2003-07-13

The SIP RA auto deploy is complete. Dropping a self contained RA jar in deploy-mobicents automatically installs the components, creates an RA Entity, activates it and creates link to it.

The RA shell scripts are no longer needed. See the sipradeploy ant task. It's much simpler.

The main java code of this feature is SleeDeployer.

Moving on to SIP service auto deployment.

Ivelin

ivelin
Offline
Joined: 2003-07-13

Service auto deploy is also completed. I am seing problems with the following method in BaseProxySBB.

public void onTimerEvent(TimerEvent timerEvent, ActivityContextInterface aci) {
try {
UdpForwarder udpForwarder =
(UdpForwarder) Naming.lookup("rmi://localhost:2000/UdpForwarder");
String host = SipConfigImpl.getRealHost();
int port = SipConfigImpl.getRealPort();
Ping ping = new Ping( host, port);
Ping lastPing = udpForwarder.handlePing(ping);
SipConfigImpl.setLastPing(ping);

} catch ( Exception ex ) {
// bad things happened when sending ping.
SipConfigImpl.setLastPing(null);
System.out.println("bad things happened");
}
}

It is not clear why there is hard coded lookup to RMI on port 2000. Dependency on external components should probably not be part of the default bahaviour of a service.

Ivelin

ivelin
Offline
Joined: 2003-07-13

Auto deployment is ready for your evaluation. Both RAs and Services are not automatically activated.

There is a new simple ant task sipdeploy, which generates RA and proxy service jars and copies them to deploy-mobicents. This way we can distribute mobicents with SIP services, which are automatically deployed when the server starts up.

To try it out, start the JBoss server and run

ant sipdeploy

observe the log file how components are deployed and activated.

It is important to note that the jar files residing in deploy-mobicents are deployed in the order that the native operating system discovers them. The SleeDeployer does not currently track or resolve dependencies between components between different jars. Therefore their names should be chosen carefully.

Feedback is welcome.

Ivelin

leondo
Offline
Joined: 2005-01-18

Hello Ranga and Ivelin,

I have noticed few problem with auto deployment:

1. Once you deployed, you cann't deploy again w/ the newer version

2. The Ant clean doesn't clean the RA and Proxy jar files in deploy-mobicents directory.

Leon Do

ivelin
Offline
Joined: 2003-07-13