Apr 24

From time to time prospective clients ask for a proof that Java CAPS will not loose HL7 messages in the event of machine or network failure.

This note walks through the process of installing a Java CAPS 6.2 runtime on the Base OpenSolaris-based VMware Virtual Appliance, discussed in the Blog Entry “GlassFish ESB v2.x Field Notes – Preparing Basic JeOS Appliance for GlassFish ESB LB and HA Testing” at https://blogs.czapski.id.au/2010/01/glassfish-esb-v2-x-field-notes-preparing-basic-jeos-appliance-for-glassfish-esb-lb-and-ha-testing.

At the end of the Note we will have a Java CAPS 6.2 VMware Appliance with Java CAPS 6.2 Runtime infrastructure, ready to use for reliability testing, or any other purpose for which a Java CAPS 6.2 runtime appliance might be appropriate.

The Note is available at “https://blogs.czapski.id.au/wp-content/uploads/2010/04/02_Installing_JavaCAPS_6.2_on_JeOS_appliance_v1.0.0.0.pdf“.

Apr 03

For these who have an interst, here is my January 2011 CV / Resume:

https://blogs.czapski.id.au/wp-content/uploads/2011/01/Michael_Czapski_January_2011_resume_cv1.2.pdf

Apr 03

As I was going through the past entries, fixing links and uploading articles, to make sure that past posts in the new blog are working, I came across articles related to my trip for the Java One 2008 and the “launch” of the Java CAPS book. Since it is not likely that I will be getting another book in a great hurry I thought I will post some of the picures I took with my crummy phone camera 🙂

Michael Czapski with a copy oof the Java CAPS Book in the Java One 2008 bookstore

Brendan Marry, one of the co-authors, with the Java CAPS Book, in front of a shelf with a bunch of Java CAPS books

Java One 2008 feeding place - sone of the over 15 thousand people queuing to get lunch

Java One 2008 - plenary session venue

Brendan Mary with Myrna Rivera (right) in the Prentice Hall boot on teh Java One 2008 Exhibition floor. Myrna, who worked for SUn Publishing at the time, helped us a great deal in getting the book published - thanks Myrna 🙂

Java One 2008 - a walking, talking Duke mascot

Frank Kieviet (not that one could tell) delivering his part of our Java One session on implementing EAI patterns with OpenESB

Prentice Hall booth at Java One 2008 exhibition floor, featuring the Java CAPS book, amongst others 🙂

Mar 12

With the future uncertain, and things changing around me, I feel it inappropriate to have my own articles associated with the employer of the moment, whomever that may be from time to time.  As a consequence I transferred all the articles I posted from http://blogs.sun.com/javacapsfieldtech/ to my own blog site, https://blogs.czapski.id.au.

blogs.czapski.id.au is the site where I will be posting all future articles.

I declare https://blogs.czapski.id.au officially open 🙂

While I am migrating my blog to blogs.czapski.id.au some links in older posts may be broken. For as long as it works, go to the http://blogs.sun.com/javacapsfieldtech/ find the post with the identical title.
Mar 06

It is expected that business solutions, whether designed in accordance with the Service Oriented Architecture principles, or designed following any of the other accepted architectural principles, are robust, reliable and available. Robustness, reliability and availability, in this context, means not just that solutions are free of design and implementation defects but are also architected and deployed in such a way that business users can access them when needed, in spite of any failures that may occur.

In an ideal world all applications will always be available for use. In the real world this may not be possible, or may not be possible at a reasonable cost.

The document referenced below discusses resilience options available to the designers of GlassFish ESB solutions and considerations that need to be entered into when designing GlassFish ESB solutions for resilience and high availability.

The document, GlassFishESB_Solution_Resillience_Options_v0.5.pdf, is available at https://blogs.czapski.id.au/wp-content/uploads/2010/03/GlassFishESB_Solution_Resillience_Options_v0.5.pdf

Mar 06

 

I am sorry to say that as at September 2010 all these links are no longer valid – seems like somebody has been going around closing sites to make sure that HL7 standards do not get used too widely 🙁

For these who have a need, the HL7 v 2.3.1 standard document is available online at http://www.medclinic.net/HL7Specs/ as at February 24, 2010. The site does not seems to have been updated for a long time so the standard document may well be available for a while longer.

HL7 v 2.3 document is available at http://www.uhc.com.pl/teksty/HL7/, again, as at February 24, 2010.

IHE Europe has an interesting “interactive” site where HL7 can be “explored” at http://ihe.univ-rennes1.fr/HL7/.

Tagged with:
Jan 29

In the major writeup called “GlassFish ESB v2.2 Field Notes – Exercising Load Balanced, Highly Available, Horizontally Scalable HL7 v2 Processing Solutions”, at https://blogs.czapski.id.au/?p=13, in section called “WS Projects”, pages 35-36 , I discuss how NMProperties in BPEL 2.0 can be used to force the HTTP BC to send the “connection: close” HTTP header, instead of the “connection: keep-alive” HTTP header, which it sends by default. Normally this does not matter but if a load balancer is to be used as a proxy, and a round robin load balancing is desired, the “connection: keep-alive” gets in the way. Rather then closing a connection after each HTTP request/response, as HTTP protocol was designed to do, “connection: keep-alive” HTTP header indicates to the server that connection is not to be closed in anticipation of another request coming form the same source “shortly”. Since the HTTP BC does not seem to have a place where this header can be removed or changed to “connection: close”, NMProperties in BPEL have to be used to force connection closure and enable correct load balancing behavior.

Jan 29

In the major writeup, now called “CH05_WSSecurityExploration_r0.4.2.pdf”, at https://blogs.czapski.id.au/wp-content/uploads/2010/03/CH05_WSSecurityExploration_r0.4.2.pdf, in section 5.14.3, “Using WS-Addressing for Explicit Routing”, I discuss how WS-Addressing can be used to implement a variant of the “Routing Ticket” EIP Pattern. A one-way web service consumer sends a request to a request/reply web service, indicating, using WS-Addressing, the address of a one-way web service to which to send the response.

Jan 29

As I develop bigger prices of work, which have writeups associated with them, I inevitably have to solve small problems that crop up. The problems I solve I typically get written about in the corresponding writeup but may be missed by these who might need these kinds of solutions but who don’t have an interest in the major piece. For example, when writing about the HL7 HA solution, “GlassFish ESB v2.2 Field Notes – Exercising Load Balanced, Highly Available, Horizontally Scalable HL7 v2 Processing Solutions”, at https://blogs.czapski.id.au/?p=13, I had to work what host the instance of the business process was using and how to make the process instance wait for a random amount of time. I did separate writeups on these as “GlassFish ESB v2.1 – Using JavaScript Codelets to Extend BPEL 2.0 Functionality”, at https://blogs.czapski.id.au/?p=17, and “GlassFish ESB v2.1 Field Notes – JavaScript Codelets to Make BPEL Process Wait for a Random Duration Up to a Maximum number of Milliseconds”, at https://blogs.czapski.id.au/?p=16.

Here I call reader’s attention to the problem of reading values of SOAP Headers in a BPEL 2.0 process. I discussed one method in “Java CAPS 5 / 6, OpenESB, GlassFish ESB – Handling SOAP Headers in BPEL”, at https://blogs.czapski.id.au/?p=27. In the major writeup, now called “CH05_WSSecurityExploration_r0.4.2.pdf”, at https://blogs.czapski.id.au/wp-content/uploads/2010/03/CH05_WSSecurityExploration_r0.4.2.pdf, I am discussing, in passing, in Section 5.14.2, “Interacting with WS-Addressing Headers in BPEL”, a method that uses Normalized Message Properties (NMProperties) in BPEL 2.0, to access SOAP headers. While this piece discusses how to access WS-Addressing SOAP headers it is equally applicable to other SOAP headers. Similarly, in section 5.14.3, “Using WS-Addressing for Explicit Routing”, I discuss how arbitrary SOAP headers can be added and populated using NMProperties in BPEL 2.0. So if you need to manipulate SOAP header in BPEL 2.0, have a look a these sections.

The writeup, CH05_WSSecurityExploration_r0.4.2.pdf, is available at https://blogs.czapski.id.au/wp-content/uploads/2010/03/CH05_WSSecurityExploration_r0.4.2.pdf

Jan 26

In the blog entry “GlassFish ESB v2.2 Field Notes – Exercising Load Balanced, Highly Available, Horizontally Scalable HL7 v2 Processing Solutions”, at https://blogs.czapski.id.au/?p=13, I present the GlassFish ESB v2.2-based load balanced, highly available, horizontally scalable solution for HL7 v2.x delimited messaging, using both the HL7 Binding Components, Web Services and JMS in request/reply mode. The one and a half hour recording of me discussing and demonstrating this solution is available as a Flash Movie (SWF), “GFESB_LB_HA_Demo_Session SWF ” at https://blogs.czapski.id.au/wp-content/uploads/2010/03/GFESB_LB_HA_Demo_Session_SWF.swf (62.7Mb download)

preload preload preload