Seamless Integration with webMethods
            

Igor Steficic, Croatia Insurance – We had very tightly coupled IT architecture and IT system. We were not able to quickly introduce new best of breeds into our IT ecosystem and we were not able to integrate our business partners and bring our business functionalities to our partners and clients in a timely and orderly way. We had to do something. We had to be competitive in the digital market so we had to do something to open our system to our partners, to our new solutions, to the new opportunities. That’s why we chose webMethods Integration and API platform to bring our business services to the partners, to the institutions, and incorporate their services into our IT ecosystem.

Igor Steficic, Croatia Insurance – We are using webMethods Integration server for building services and integration flows. We are using API management group of products like API Gateway and API Portals for exposing the APIs to our partners and various government and public institutions. We are using universal messaging for our processes and JDBC (?) adapter for connecting to the database...We have over 200 integration flows.

Ivana Levatic, Croatia Insurance – So, our biggest advantage is that we have a fast onboarding process for new developers. We don’t have a steep learning curve. Our developers can start working confidently in webMethods in a matter of months.

Personally for me, as an integration analyst, as a business analyst, it really helps to debug. When we get a potential bug report from users from other systems in Croatia Insurance, it’s beneficial for me to look at the service in designer and I can see what exactly is happening even though I might not be familiar with the service itself; it was a service that was developed before my time or it was a service that another business analyst was assigned to. I can open it in designer, and I can get a good grasp as to what is happening in that service, and I can help users to find out what went wrong. Sometimes, as any integration layer on the integration team, we are the mediators between systems, sometimes the bug came from the system we are integrating and it really helps us to pinpoint where exactly the bug happened and we can triage the bugs between different teams.

We are here to make sure you can integrate anything with everything.