Skip to main content

Integration Project- Micro Services Migration Story with JBoss BPM Travel Agency - Part Five

Part Five- Migrating Web Services.


This post is the fifth part of a JBoss Travel Agency Integration Demo series, and we are going to talk about how to migrate from an existing web service to JBoss Fuse. And it is so much easier then you can ever imagine. When migrating web services, we know there will be a contract already exists, it is the WSDL file. So all we have to do is just to implement this contract. If you want to know more about the micro service architecture of the demo, please see this post for more details. For now, all you have to know, it that now we are going to migrate from an already existing web service to JBoss Fuse, and then dispatch these request to difference message queue in broker, so later on the backend service can retrieve and process it.

After receiving hotel request from client, the web service will be dispatched to messaging queues. And because the result needs to go back to the client, we need to make sure the request comes back, there for we need to set the JMS to in-out to make sure it gets the return message back. Also, we need to transform the data from client to the format backend service understand, which is JSON.


OK, first things first, from the WSDL file we have, by adding the cxf-codegen maven plugin to generate the related object and services, and direct it to read the wsdl file locate in the project.
      
      
        org.apache.cxf
        cxf-codegen-plugin
        2.7.0.redhat-610379
        
          
            generate-sources
            generate-sources
            
              ${basedir}/target/generated/src/main/java
              
                
                  ${basedir}/src/main/resources/wsdl/HotelWS.wsdl
                  
                    -impl
                  
                
              
            
            
              wsdl2java
            
          
        


And then we can start setting up the web service endpoint



Rather then just a simple connection to the messaging queue, this small application needs interact with messaging a lot, so we are going to create a pool to the broker.

    
    
    


    
    


    
    


    


Take a look at the WSDL, here you see it has three services, with different inputs, so we are going to implement these services.

The first route is the universal endpoint, where it will take in the entire request, and dispatch them to the routes that actually implements the web service.


Then we go on can create the route that handles booking and cancel booking, it simply converts the input into whatever format is needed.

Booking Route

Cancel Booking Route


For available hotel request it is a bit more complex, because the web service requires a specific object to return, so here we are going to do map JSON content and turn it into the specific object.
package org.blogdemo.travelagency.hotelwsendpoint;

import java.util.Map;

import acme.service.soap.hotelws.Resort;

public class ListHotelBean {
 
 public Resort getResort(Map promotedResorts){
  Resort resort = new Resort();
  resort.setHotelId((Integer)promotedResorts.get("hotelId"));
  resort.setHotelName((String)promotedResorts.get("hotelName"));
  resort.setHotelCity((String)promotedResorts.get("hotelCity"));
  resort.setAvailableFrom((String)promotedResorts.get("availableFrom"));
  resort.setAvailableTo((String)promotedResorts.get("availableTo"));
  resort.setRatePerPerson(((Double)promotedResorts.get("ratePerPerson")));
  
  return resort;
 }
}

Register the mapping bean in camel context,
    

And lastly, the available route.


And that's it. More detail instructions are available in the slides below.



 For more detail side in BPM Suite, please click here to Eric Schabell's post.

Micro Services Migration Story with JBoss BPM Travel Agency

  Part One: Introduction and Installation
  Part Two: Moving towards Microservices
  Part Three: Retrieving Data with JDBC 
  Part Four: Persistence with JPA
  Part Five: Migrating Web Service 

Comments

Popular posts from this blog

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

jboss-devstudio-9.0.0.GA-installer-eap.jar
double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.


And select JBoss Fuse Development for the plugin,


Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.



And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …

RHTE - Supercharge your integration services

Red Hat Tech Exchange has taken place in Vietnam, Ho Chi Minh city two weeks ago, it is a great event held by Red Hat in Asia Pacific Region. It is open to all Red Hat partners who are interested in learning what Red Hat is doing recently, see what the trend of the open source world, basically it is a great event to share your knowledge and experience, to meet other enthusiastic people.

I am very fortunate to talk in this great event, to talk about the things I have been working on and even discuss it with many. Also got lots of great ideas too. So here are the slide.

My first talk was with Thomas Qvarnström about how to handle large size data in JBoss Fuse and how JBoss Data Grid can help in the situation.

Here is the agenda of the talk, we will be talk about this in the up coming webinar on 24th Sept.

Integration often involves storing, retrieving, and transforming data. Using a traditional database in your integration is likely to becomes a bottleneck that is expensive and hard to …