Tuesday, March 28, 2006
Busy Busy
I haven't had a chance to post much lately. I'm in the middle of a major webMethods upgrade. I have been playing around with the new Fedora 5 on the side. I'm really interested in the embedded Xen support. I'll put more out here about that and some distributed services concepts I'm toying with a little later as time becomes less of a constraint.
Wednesday, March 22, 2006
SOA Web Services Journal: Save Our Architecture @ SOA WEB SERVICES JOURNAL
There are over 492 new acronyms in this article. On the somewhat serious side it is a decent read.
Monday, March 20, 2006
Slashdot | Fedora Core 5 Available
This is the distribution that is suppose to have Xen embedded into the OS as opposed to just available as a package. It holds some promise if you believe what Redhat is saying about it. 100ms switch times is pretty impressive if it is true. For those of you who are experienced in clustering, you know the complexity that can be involved. Bringing up the whole OS container somewhere in 100ms is fast and less prone to error than traditional active/passive clustering.
Monday, March 13, 2006
Application Availability
Software design and testing is directly related to the availability of an application. We all know that already. No amount of money spent on hardware can overcome a flaw in the application. We call these undocumented features sometimes. They can be very challenging to troubleshoot in a production system.
With Integration, these challenges become more intense. Multiple systems wired together and yes even loosely coupled systems can impact each other despite what all of the analyst and software vendors tell you. The question is how to overcome this complexity and turn out reliable systems that have little to no impact on each other. Well I would love to say I have the answer but the truth is there is no one answer.
Good sunny day and rainy day testing will take you far as well as good design and good documentation. Well trained operations and application support staffs will also contribute. But in the end the combination of variables in a large integrated environment both known and unknown are just to great to overcome. There are going to be issues.
So what to do? A few of pointers from hard learned experience:
1-Educate your management and your clients; setting expectations for realistic availability is key. ie deploying your app that you designed while coding it to a single server is not going to give you 5 nines.
2-Educate your staff. It's great that you know the app but you are not available 24x7 unless of course food, sleep, vacation are not something your require.
3-Practice recovering your app. Don't know how? When it is hosed in production is not the time to learn.
4-Know what else your app depends on. This is really key in integration work. Change management is a big deal.
5-Did I mention educate your management and your clients?
Just a few thoughts for the day as the fires have finally died out.:)
With Integration, these challenges become more intense. Multiple systems wired together and yes even loosely coupled systems can impact each other despite what all of the analyst and software vendors tell you. The question is how to overcome this complexity and turn out reliable systems that have little to no impact on each other. Well I would love to say I have the answer but the truth is there is no one answer.
Good sunny day and rainy day testing will take you far as well as good design and good documentation. Well trained operations and application support staffs will also contribute. But in the end the combination of variables in a large integrated environment both known and unknown are just to great to overcome. There are going to be issues.
So what to do? A few of pointers from hard learned experience:
1-Educate your management and your clients; setting expectations for realistic availability is key. ie deploying your app that you designed while coding it to a single server is not going to give you 5 nines.
2-Educate your staff. It's great that you know the app but you are not available 24x7 unless of course food, sleep, vacation are not something your require.
3-Practice recovering your app. Don't know how? When it is hosed in production is not the time to learn.
4-Know what else your app depends on. This is really key in integration work. Change management is a big deal.
5-Did I mention educate your management and your clients?
Just a few thoughts for the day as the fires have finally died out.:)
Tuesday, March 07, 2006
SOA Pipeline | Business Management << How Software Consolidation Will End Up Squeezing You >> February 26, 2006
More and more folks are coming to this conclusion. The hype is high but the reality is low for SOA. If you have seen the mixed adoption of OOP and the partial success of EAI and you were wondering if SOA somehow made all of those issues go away, in short the answer is no. SOA is a good thing but it is not mature, not yet.
Folks that found success with OOP and EAI will probably transition well into an SOA style of architecture. Everyone else will struggle. Why? Because integration is hard (esp. real time). Developing interfaces that are abstract and reusable is hard. Convincing clients and management that spending extra time on common information models is hard. Understanding the 8 million Web Services standards well let's not even go there.
Folks that found success with OOP and EAI will probably transition well into an SOA style of architecture. Everyone else will struggle. Why? Because integration is hard (esp. real time). Developing interfaces that are abstract and reusable is hard. Convincing clients and management that spending extra time on common information models is hard. Understanding the 8 million Web Services standards well let's not even go there.
Wednesday, March 01, 2006
98% of Java developers just don't need it
Well what do you think? I've often read that 90% of Java development is servlets. I have definitely seen folks buy expensive app servers to do very basic stuff. But I've been kind of trolling the Axis support list and I can say there is more going on with Java than just servlets and basic development.
Sunday, February 26, 2006
Java EE 5 Tools Preview
To give Sun credit, they have put out a pretty good preview release of the new Java EE 5 along with a new tools preview. A couple of things I noticed were BPEL support and UML support. It's also pretty fast. It's got XML schema support like Eclipse along with a WSDL editor. I think its XML support is a little less robust (from a graphical standpoint) than the Eclipse version. But I did find at a casual quick glance that the UML support and the BPEL support were fairly easy to work with. I was even able to import the BPEL generated by the Sun tool into webMethods. It's worth a look.
Here is a screenshot of the BPEL composer:
Figure 1

Here is a screenshot of the UML editor:
Figure 2
Here is a screenshot of the BPEL composer:
Figure 1

Here is a screenshot of the UML editor:
Figure 2
Tuesday, February 21, 2006
Eclipse 3.1 with WTP 1.0
Still working on some interoperability testing with Eclipse and the new release of the WTP toolset. I found something interesting with working with the document/literal wrapped style of WSDL. Normally in you WSDL design with a document/literal wrapped style, you would have your operation name the same as your input message. And this in fact works for a large portion of the toolsets including, Axis 1.3, webMethods, .Net, and Suns Studio Creator. This does not work however with Eclipse. In Eclipse if you try and generate a proxy or a web service based off that type of WSDL, you will not get the messages deserialized into java beans. In other words instead of a method like createTicket(ServiceRequest request), you will get createTicket(arg1, arg2, arg3, arg4, arg5).
The work around I have found for this is to change the operation name into something other than the message input name. See the screenshot below. Notice that the operation name is different from the input message. With the WSDL setup like this the beans are generated correctly.

Not really the ideal thing to have to do. I'm attempting to work with the Eclipse folks to see if this is a bug or intended behavior.
The work around I have found for this is to change the operation name into something other than the message input name. See the screenshot below. Notice that the operation name is different from the input message. With the WSDL setup like this the beans are generated correctly.

Not really the ideal thing to have to do. I'm attempting to work with the Eclipse folks to see if this is a bug or intended behavior.
Friday, February 17, 2006
More on WSDL Design
This is kind of a strange thing to happen but if you run into it this might help. I was importing xml schema into some wsdl using http as the location and got a java.net.URLConnection exception when using Axis 1.3 from the command line and with Eclipse. Here is the import statement:
schemalocation="http://sn000046:8081/schemas/servicerequest.xsd"
Very common import statement, so I couldn't figure out why the error was being thrown. Turns out I was hosting the .xsd schema on an Apache Tomcat server that I haven't defined the content-type for xsd or wsdl as xml. So the response header coming back from the server had no content-type specified. Easy to fix just modify the web.xml either in the individual project or in the global conf/web.xml file.
This is why interoperability testing is important. This same wsdl consumed by other platforms ie .Net and webMethods did not have a problem with the content-type being absence.
schemalocation="http://sn000046:8081/schemas/servicerequest.xsd"
Very common import statement, so I couldn't figure out why the error was being thrown. Turns out I was hosting the .xsd schema on an Apache Tomcat server that I haven't defined the content-type for xsd or wsdl as xml. So the response header coming back from the server had no content-type specified. Easy to fix just modify the web.xml either in the individual project or in the global conf/web.xml file.
This is why interoperability testing is important. This same wsdl consumed by other platforms ie .Net and webMethods did not have a problem with the content-type being absence.
Monday, February 13, 2006
WSDL and Eclipse 3.1
I am doing some work on modular WSDL. I was looking for a good WSDL editor that was low cost as in free. Don't know how much hand coding you have tried with WSDL but it can become a bit tricky especially when trying to troubleshoot. It comes in handy to have a tool that shows you where some of your links may be off.
Altova is okay for syntax checking but to see graphical WSDL, you have to purchase a licensed copy. I had been playing around with Eclipse 3.1 and their web tools for a while doing some interoperability testing. I did not realize at the time that they had a built-in XML schema editor as well as a WSDL editor. Turns out it is not really bad for the price. They have just released version 1.0 of the web tools.
Here are a couple of screen shots to illustrate what I mean by graphical layout. In figure 1 you can see the correct linkage being made. This saves a lot of time.
Figure 1.

Figure 2 shows the import schema linked into the messages section. This is also nice in that it lets verify that your linkages are correct.
Figure 2.

Here is a site with some more good tips on using XML schemas and WSDL. I also found another site that where the authors are using modular WSDL in their design. It's a good reference if you are just getting started.
Altova is okay for syntax checking but to see graphical WSDL, you have to purchase a licensed copy. I had been playing around with Eclipse 3.1 and their web tools for a while doing some interoperability testing. I did not realize at the time that they had a built-in XML schema editor as well as a WSDL editor. Turns out it is not really bad for the price. They have just released version 1.0 of the web tools.
Here are a couple of screen shots to illustrate what I mean by graphical layout. In figure 1 you can see the correct linkage being made. This saves a lot of time.
Figure 1.

Figure 2 shows the import schema linked into the messages section. This is also nice in that it lets verify that your linkages are correct.
Figure 2.

Here is a site with some more good tips on using XML schemas and WSDL. I also found another site that where the authors are using modular WSDL in their design. It's a good reference if you are just getting started.
Subscribe to:
Posts (Atom)