Welcome to the latest newsletter. Here is what I have for you in this issue:

• How to retrieve nested values from documents on Integration Server
• Refactoring Integration Server packages
• How modern CPUs work

With that let's jump into the content and I wish you all a great week.

Best wishes,
Christoph

With a little bit of Java coding you can add powerful functionality to webMethods Integration Server. This one comes from the WxConfig NG project. There it is used to validate responses for auto-setup of environment configuration.

It is a common requirement in advanced integration scenarios to retrieve values from a data structure by specifying a path there. If you are an XML person, think of something a bit like XPath (although usually not as complex).

This article shows you how to do that.

It is pretty easy to end up with Integration Server packages that are not well-organized. That is neither an indication of you being incompetent, nor of Integration Server being a bad product. It happens to everyone with every programming environment.

Fortunately, Integration Server makes it easy to change this. You can start by moving service and other assets (e.g. document types or triggers) into separate packages, without changing the namespace. And then you can gradually work on the details.

Here is an article that describes a scalable and easy-to-understand approach how to structure things. It is even compliant with the principles of DDD (Domain-Driven Design).

Wonderful video about the core component of every computer works internally. Quite different from e.g. the 6502, where I learned Assembler.