Mashed Articles

IBM recently published an article on the use of WS-ReliableMessaging between WebSphere 6.1 and Axis2. Most interesting I found the part on the Quality of Service of WS-RM:

• Unmanaged non-persistent tolerates network and remote system failures. You can configure Web service applications to use WS-RM with a default in-memory message store. This QoS requires minimal configuration; it is for a single server only and does not support clusters. Although this QoS allows for the re-sending of messages that are lost in the network, failure of a server results in lost messages. The default is unmanaged non-persistent.
  

• Managed non-persistent tolerates system, network, and remote system failures, but state is discarded after the messaging engine restarts. This in-memory QoS option supports clusters as well as single servers. This option uses a messaging engine to manage the sequence state, and messages are written to disk if memory is low. This QoS allows for the resending of messages that are lost in the network, and can also recover from server failure. However, a failure of the messaging engine causes message loss.

• Managed persistent tolerates system, network, and remote system failures. This QoS for asynchronous Web service invocations is recoverable. This option also uses a messaging engine and message store to manage the sequence state. Messages are persisted at the Web service requester server and at the Web service provider server, and are recoverable if the server fails. Messages that have not been successfully transmitted when a server fails can continue to be transmitted after the server restarts.

QoS of WS-RM is actually not part of any standard. Most implementations of WS-RM are non-persistent, in particular Microsoft WCF and Sun’s Metro. And that is in my opinion the major shortcoming of the WS-* story. The WS-RX committee should have made message persistence part of the WS-RM spec and/or the WS-RM Policy spec.

Anyway, IBM has a persistent implementation of WS-RM. And so has SAP: SAP doesn’t even give you the option and uses persistent WS-RM as its default. Well done by SAP, although the SAP implementation is based on an older version of the WS-RM spec (WS-RM 2005/02.)

What I don’t find are reports of the use of persistent WS-RM between stacks of different vendors, e.g. between IBM and SAP. Maybe we’ll need to have a go ourselves one day?

Why you should you choose working at home business opportunities offered by Data Processing? Data Processing is a powerful business concept for many reasons but the most obvious is for the type of income it can provide the Data Processor and also the flexibility to do this part time.

So why can’t the average person do the same? The answer is average people are already working some great Data Processing home-based businesses opportunities. Are you one of them? If not, now is an excellent time to get started.

Data Processing is a huge, thriving industry in spite of all the negative publicity it receives in the media from anti-Data Processing enthusiasts. Can you use some extra income? Most consumers would probably answer yes to this question. Everybody can use extra income every month. But where is this extra income going to come from?

One obvious solution would be is to get a second job. This option may seem to be the best solution but is really not. This is because the time you spend on your second job and the money you receive after taxes is not enough.
Of course you will have to consider your reasons for getting a second job and why you need the extra income to determine if getting a second job is really the right solution for you.

However, on the other hand, you can start working on your own part-time home-based business using Data Processing as your business opportunity. You can get started in the industry for nearly nothing. This is a big plus. Getting started in Data Processing has become so easy that anyone can get started even if you do have to give up $50 or so to invest in your start up. The key here is to simply get started then never quit.

Many legitimate Data Processing home business opportunities will allow you to get started for under $100. You can even find opportunities with little or no overhead expenses and with great support from other members as well as web based training. These companies will provide all the tools and system for you. You simply add your sweat equity, your working commitment, and persistence to the Data Processing home business opportunity.

Another important key factor is your commitment to succeed. Working for a home business Data Processing opportunity means that you should allocate about 1 to 2 hours a day posting and the return would be well worth the effort. In conclusion, Data Processing is a smart business opportunity for anyone wishing to start working at home. It cost next to nothing to get started, you get a proven system like you would if you bought a franchise opportunity, and you can be in profit in months rather than in years.

Therefore, if you desire more income while still working a 9 to 5 job, or to build your retirement income, then you should seriously consider working for a home business opportunity. This is one of the Reliable programs I have found.

Reliable Data-Processing Program
By: jbaccount
Article Directory: http://www.articledashboard.com
Reliable Data-Processing Program

JMS or Java Message Service is the basis and standard API for asynchronous, reliable messaging.

After 10 years, a new (2nd) edition of the book “Java Message Service” was recently published. Mark Richards reworked the original edition by David Chappell (ex-Sonic, now Oracle) and Richard Manson-Haefel.

Having just skimmed through the book, it did look very intersting. Obviously an extensive treatment of the API (and thus specification). But nice to see code samples based on ActiveMQ, some explanation of character encoding, use of non-JMS clients (.Net, C++), dynamic vs. administered queues, message driven beans (MDB) and Spring and Security.

Some topics that did not seem to be addressed:SOAP over JMS, REST-like access tot JMS providers, persistence mechanisms (database or file based),

Messaging solutions are still the core backbone for many ESB’s and integration solutions. The JMS API remains the standard abstration layer for both Java (ActiveMQ, SonicMQ, OpenMQ, Fiorano) and non-Java based messaging (Tibco , WebSphereMQ, SoftwareAG WebMethods, Oracle AQ) solutions.