Daily Archives: October 9, 2006

New Google Blog Ping

Reviewing the announcements from the Google Blog last week, I came across a note about their new blog pinging service. This post is to see whether Windows Live Writer will work with it “out-of-the-box”.

Update: I tried configuring the ping URL in Tools -> Preferences to be http://blogsearch.google.com/ping/RPC2 and my URL does indeed appear in the changes feed (for the past 5 minutes), so I assume that worked. Just add that Google URL to the list of pingable endpoints in WLW.

Someone persuade me to try Firefox 2.0

Should I upgrade? FFx 2.0 RC 2 was released a few days ago. Back in the olden days, when Firebird / Firefox was being developed pre-1.0, I was an enthusiastic follower of the alpha and beta releases. These days I’m inexplicably more cautious.

Anyone else using 2.0? What extensions have you found that don’t work?

Technorati tags: , , ,

Exploring Hursley

Via eightbar:

this new flash map of the Hursley site. If you’ve never been to Hursley before, it’ll give you a good sense of the scale of the place and some of the facilities here…

Funky 🙂

PCs at risk online

Today’s Metro has a front-page scare story about how the average broadband-connected, always-on PC in the UK could be “attacked up to 50 times a night” through port scans, viruses, etc..

About seven years ago I was still on dial-up, but using Linux. I had no kind of firewall. One day I looked at the list of logged in users and discovered that there was “someone else” on my workstation. I dropped the connection, and looked through logs to find out what had gone on. In the end I found that an attack originating in Slovakia had got past a vulnerability in named (on an old, old version of RedHat by today’s standards) and allowed the attacker to wander around my hard disk for a while. That was enough to shake me up quite a lot.

Nowadays, I swear by the hardware firewall in my router. If I was to log port scans on the router, I’m sure I’d see quite a lot of them. I have up to four machines running behind the router at any one time, but broadly speaking I worry about intrusion. Two are Linux machines with basic iptables rules; the other two are XP SP2 with the inbuilt firewall or ZoneLabs. I do have Apache running, and I tend to see a lot of “dodgy” traffic which usually appears to be trying to exploit some old vulnerability in IIS.

Am I too complacent? It probably would be a good idea to monitor incoming traffic more actively. I’m probably more concerned for my family running XP on an otherwise unprotected network. It’s a scary world out there 😦

Broker round-up

If you don’t subscribe to the developerWorks WebSphere Message Broker RSS feed, you may have missed a lot of the recent announcements and articles. Even if you do, I’d like to pick out a few of the highlights.

Connecting the JMS Transport Nodes for WebSphere Message Broker v6 to Popular JMS Providers (dW article): WMB v6 has the ability to connect to any JMS 1.1-compliant provider. This article describes how you can configure the broker to connect to WMQ JMS, the WebSphere messaging provider in WebSphere Application Server v6, Tibco EMS and SonicMQ. It also describes some of the scenarios associated with the use of the JMS nodes. The article was written by Hursley’s Rich Bicheno, and Mark Kovacevich, so you know the content is coming from the experts. Very useful for any broker developer faced with the need to connect to a JMS provider.

WebSphere Message Broker V6.0 Client for WebSphere Service Registry and Repository (SupportPac IA9L): I mentioned this in my entry last week about WSRR. This is going to be important going forward. I’ll be installing it on my own broker shortly.

Managing WebSphere Message Broker Resources in a Production Environment (Redbook): after you’ve designed and developed your ESB solution, it would be nice to put it into production! The Redbook covers some of the key topics in this area – naming conventions, security, backup and recovery, basic monitoring, problem determination, etc.. I still haven’t had a chance to work all the way through the book, but the sections I’ve read so far are very good.

High Availability for WebSphere Message Broker on Distributed Platforms (SupportPac IC91): this replaces the series of SupportPacs that used to provide instructions on high availability for individual platforms. It consolidates the information into a single document which describes the setup for HACMP, Veritas Cluster Server, MC/ServiceGuard, MSCS and HA-Linux. Example scripts are included.

That’s enough for now… there is a lot of activity in the WMB space, so if you are interested in this stuff then keep an eye on the RSS feed. Lots of new information for me to absorb!

Technorati tags: , , , , , ,