Tools & Consulting for the webMethods® platform

Tools & Consulting for the webMethods® platform

Coming up: Next generation configuration management for webMethods Integration Server

The successor of WxConfig is about to land. During my time at Software AG I built WxConfig and made it the leading configuration management system for webMethods Integration Server. Now is the time for a new chapter.

It is time for an even better configuration management solution for webMethods Integration Server. Over a period of more than 15 years I had developed WxConfig and made it the so far best configuration management solution. It was a great experience and I learned a ton, not only about Integration Server and what great a platform it is. But also about the conceptual side of configuration management. You would be surprised how many facets there are to it.

Now is the time to bring things to the next level.

The new configuration management will have extended capabilities for containers to support cloud-native architectures. And of course it will have many of the great features that people have come to like from its predecessor.

  • New: Landscape management
  • New: Ease-of-use for Containers and orchestration platforms like Kubernetes and OpenShift
  • Web UI for developer productivity and operations staff
  • Compliance coverage through logging and auditing
  • Multi-environment and OS support

You can see, that many exciting things are coming. If you want to be sure to not miss anything, please follow me on LinkedIn or use the contact form below to subscribe to the update mailings. The contents will be the same for  both channels.

Migration path for WxConfig

Probably the most important aspect for many users of Integration Server will be the migration path from WxConfig. Here are the highlights:

  • Side-by-side operations: You can install the new solution next to WxConfig and they will work together nicely.
  • No big-bang migration: Choose the steps that fit best with your existing code, release plan and other organizational aspects. You can start with smaller packages, get familiar with things, and take it from there at the pace you want.
  • Automatic updates of your Flow services: No need to manually change your code. Instead the necessary updates will be applied for you.

If you have further questions, please send an email or use the contact form below.

Get in touch

Please use the form below to get in touch.



Leave a Reply

Your email address will not be published. Required fields are marked *

On Key

Related Posts

Microservices and code reuse for integration platforms

Today I want to write about a software development approach I was able to put into practice a few years ago. I was myself very much surprised how well things worked out, and especially how fast I was able to see tangible benefits for the business side.

Custom logging with Log4j on Integration Server

Every serious IT system needs proper logging. This article describes how I use Log4j v2 with webMethods Integration Server. There is no need to change anything on the system, just install the package and it works.

External Java libraries in webMethods Integration Server

To get most out of your Integration Server you will sooner or later need to leverage the functionality of existing Java libraries. Common examples are Log4j or Apache POI (for working with Excel or Word files). Here is a short guide for this.

Running webMethods Integration Server in containers

Organizations are moving from traditional deployments to containers and Kubernetes to increase business agility. This article discusses a lot of topics that are relevant to actually reach the goal of faster delivery of value to the business through software. Because if you do it wrong, you just end up with yet another technology stack. And, as always, technology is not your biggest challenge.