Tuesday, July 24, 2007

HTTP Ping-test with assemblies.

Justin Mason blogged about an interesting use of Jaiku for http-ping testing. It has an open-API, SMS testing etc. We are currently just rolling out our new assembly framework, so I thought can I do the ping-test easily in assemblies. As it is I can. So here is all the working code for the assembly.

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans" xmlns:beans="http://www.springframework.org/schema/beans" xmlns:cc="http://www.capeclear.com/assembly/10">

<cc:assembly id="CapeClearAssembly">
<cc:staticfile-in input-file="myfile.txt" id="staticFile"
routes-to="httpCheck"
>
<cc:schedule cron="0/10 * * ? * *"/>
</cc:staticfile-in>

<cc:http-out id="httpCheck" endpoint="http://dink.capeclear.com/"/>

<cc:xmpp-out id="xo" endpoint="xmpp:someOperator@gmail.com"
username="someUser" password="somePassword"
server="talk.google.com" domain="gmail.com"/>

<cc:send-error id="sendError" routes-to="xo"/>
</cc:assembly>
</beans>


It sets up a static-file event (running every 10 seconds according to a cron schedule). This event creates a static message which is routed to a HTTP-out transport (see routes-to attribute of static-file-in). The http-out transport is used to ping some URL (in this case dink.capeclear.com). If this ping fails, then an error handler (sendError) is automatically invoked. This sendError command routes a message to GoogleTalk IM (xmpp-out).

The result is that if dink.capeclear.com is not available, someone gets an IM message on googleTalk.


Powered by ScribeFire.

Monday, July 02, 2007

BT ends eight-year SOA effort- starts Phase 2.


Techworld.com - BT nearing end of SOA project reports on how BT has completed an eight year SOA project - to SOA-ify it's core systems. Headline items:

  • Core systems weren't what the business process said they were when they actually looked.
  • 20% reduction in IT Staff.
  • 2,000 IT Staff redeployed from internal to customer-facing projects - now that the internal API's are defined.
  • 160 core SOA capabiltiies (each with 5-15 operations).
  • IT Staff Bonuses now in terms of SOA-re-use.
They reckon that now that they are all SOA, it should be much quicker to roll out new services that work in terms of these core capabilities (customer account management, provisioning).




Powered by ScribeFire.