In WSO2 API Manager it is possible to add workflow extensions for events such as user registration, application creation, API subscription etc. There are several standard workflows provided in API Manager, you can read documentation here. In this post I want to show how to customize a BPEL process
In this post I will show how to write a simple CXF based JAX-WS service using WSO2 Developer Studio and how to deploy it in WSO2 API Manager. My service will use API Manager carbon user store to get an email of a specific user. Open Developer Studio dashboard (I’m
Sunday I arrived at IBM Interconnect 2015. IBM has decided to combine the 3 conferences – Impact, Pulse and Innovate into one Conference. IBM Interconnect- The Premier Cloud Computing & Mobile Conference. It started Sunday with the Business Partner Summit. Monday the real conference started.
A customer of mine had the requirement to send an email every time a task is created for a user. Rather than polluting our process with an email activity we decided to use the built in functionality IBM BPM provides. When a user logs in
After having looked into Vagrant, it became clear that Puppet and Chef are “the” tools to do the structured and repeatable configuration of machines. I picked the recent book “Learning Chef” to learn and experiment a bit. Tools The book uses the recent Chef Development Kit which should gradually replace the tool called Knife.
After looking a bit into Docker, I went on to look into Vagrant, another well-known tool to provision and configure virtual machines. To learn about Vagrant, I read the book “Vagrant: Up and Running“. This O’Reilly book is well-written and the examples all work. While
The holiday period between Christmas and New Year is an ideal period to catch up on some reading and experimenting. Devops and tools such as Docker, Vagrant, Chef, Puppet and Ansible were on my radar for a while. So finally some time to dive into
One of the clients that I’m working for discovered a problem with a SOAP web service querying an LDAP. The service could contain a ‘*’ in plain text in possibly different fields in the message. When the service is called it uses the ‘*’ as a
We were implementing a bulk-data transfer from SAP into an Oracle database. Easily upwards of 15 000 materials were being uploaded to the database via a stored procedure (company policy). Normally we like this approach because it decouples PI from the database’s underlying table structure, but
While re-reading the Microservices article by Martin Fowler, I was triggered by the following footnote #7: We can’t resist mentioning Jim Webber’s statement that ESB stands for “Egregious Spaghetti Box”. I viewed the presentation – from 2008 – in which Jim Webber and Martin Fowler
“Micro Services” is a new buzzword in world of IT architects. As it talks about application components communicating over a network and contains “services”, it probably has something to do with SOA and integration. So I had to look into it. Let’s bulletize the description
As an integration consultant I work almost daily with XML messages. In my opinion in order to work efficiently with XML you need to have XML schemas. XML schemas makes it possible to validate your messages (including those hard to find typo’s in mappings), they
