Adventures of a service oriented architect
A while ago I created my first REST service in webMethods Integration Server. It’s quite easy to do and works correctly out of the box. Software AG managed to implement the standards quite well and I didn’t have to go through hours of configuring (like I had to with SOAP webservices). How to create a … Read more
When I started out implementing services in webMethods Integration Server, I didn’t really know how to structure my packages. I lacked the experience in what should go where and which resources are best grouped together. So I ended up with a different folder structure for all my packages. At this point, finding the resource I … Read more
One of the two main lessons I learned while SOA-fying our monolithic application was: Avoid redundancy. We started out implementing the data structures for our services by hand. This means, I had to create the same data structure over and over again in different systems. For example, a simple Webservice for reading a person from … Read more
I’ll continue my series of blog posts regarding the lessons we learned while SOA-fying our monolithic Adabas/Natural application with a more technical lesson: SOAP is dead. This may be a harsh statement, taking into account that we started out with Webservices based on SOAP and at the moment our whole infrastructure is based on it. … Read more
Another lesson we learned while making our legacy application ready for a service-oriented architecture, is this: Test everything. When I started out writing Flow services in webMethods Integration Server (IS), there was no (nice) way of automatically testing them. Although we were told multiple times by consultants, that there would be a test framework for … Read more
One of the lessons we learned while SOA-fying our legacy application (an Adabas/Natural monolith, that is almost 20 years old) is: Make use of diversity. When we designed the central interface for our service modules, we made sure that developers with different backgrounds worked together on the design team. For example, we had older and … Read more
My talk for Software AG’s Innovation World 2015 in Las Vegas got accepted and is already visible on the agenda: Lessons Learned from SOA-fying a Monolithic Legacy Application. How do you modernize a monolithic legacy application to meet the requirements of today’s service-oriented world? In this talk, Stefan Macke shares his insights from SOA-fying a … Read more
Universal Messaging is the default messaging component used by webMethods Integration Server. Here is a short tutorial how you can test JMS processing using SoapUI and HermesJMS. SOAPUIDIR points to the installation directory of SoapUI, e.g. C:\Program Files\SmartBear\SoapUI-5.1.3. NIRVANADIR points to the installation directory of Nirvana, e.g. C:\SoftwareAG\nirvana. Setup Universal Messaging First of all you … Read more
In newer versions of the webMethods suite, you can install multiple instances of Integration Server into a single installation. Some central packages will be re-used in every instance. However, administration of the instances may be a bit harder, as these packages have to be updated manually, e.g. in case of a version update or fix … Read more
Today we had a problem with one of our Natural FUsers. When trying to add new sources with ftouch, we got the following error message: user@server ~ $ ftouch fuser=22,173 lib=ACC sm -b -d FTOUCH UTILITY V 6.3.13 PL 0 Software AG 2012 Error : Mass update could not be started. Return code 82 received. … Read more