Skip to main content

JBoss Fuse - File Connector with Split Pattern and JDBC connector with Error Handling - Part Two

This is the second part of the demo, "JDBC connector with Error Handling ", please take a look at the previous blog post. You can also find the finished code base here.

In the XML file, you'll find there is a VIP status, this indicates the process fee we need to charge per transaction, for DIAMOND class VIP, it's $1, $2 for GOLD and $3 for other accounts.

Using JDBC Connector, we first must create datasource setting, either within Camel context xml or in Fabric8. To make testing easy, we will set the setting in the datasource.

XML
 	
    	
    	
    	
  		
  	 
  
  	
		
  	
  
	
		
		
	
Here you will see I use the H2 Database in memory, I am using it because it's easier to setup, without the need of installing a database. If you want, you can always change it to your desire database, all you have to do is just replace the driverClassName and url, along with the ID and password to access the database. And then it's always a good idea to include an transaction manager so we can set the transaction policy. 

Before calling the jdbc component, jdbc:dataSourcePS, remember to set SQL to execute into the body. 

<setBody>
  <simple>SELECT balance from customerdemo where customerID = '${header.CustId}';</simple>
</setBody>
<to uri="jdbc:dataSourcePS?resetAutoCommit=true"/>

And we might want to capture and do something when there were error. Same as in Java programming we can specify exception policies to use and can then intercept and handle the exceptions. We can specify it by using the on Exception. After capturing the exception, we can either process it or redeliver the route again. Here is an example we use in the demo. 

    
        java.lang.Exception
        
        
            true
        
        
    

From last demo, we have process and split the XML from different bank branches into individual separate transaction. And they are group into 2 different groups, cash and transfer transaction.There are no fees when the transaction is in cash, but for Transfer, you'll find there are VIP status, this indicates the process fee we need to charge, for DIAMOND class VIP, it's $1, $2 for GOLD and $3 for other accounts.

To update the balance in database first we select to make sure we have enough balance to deduct or we will throw a not enough balance exception, which we will handle with a logging it.





Carry on from our last demo, we are going to extend the two camel route.
i) processCash





    
        
        
            SELECT balance from customerdemo where customerID = '${header.CustId}';
        
        
        
        
            UPDATE customerdemo SET balance = ${body} where customerID = '${header.CustId}';
        
        
    

Within the route you will see a java bean, it is the actual business logic to add and deduct the money from each account.


package org.blogdemo.bankdemo;

import java.util.ArrayList;
import java.util.HashMap;

import org.apache.camel.Exchange;

public class BankBean {
	int countError=0;
	
	public static final int DIAMOND_FEE = 1;
	public static final int GOLD_FEE = 2;
	public static final int NORMAL_FEE = 3;
	
	public void transfer(Exchange oldExchange, Exchange newExchange)throws Exception{
		Integer amtDeduct = ((Integer)newExchange.getIn().getHeader("amt",Integer.class));
		newExchange.getIn().setHeader("amt", amtDeduct * -1);
	}
	
	public void doBalance(Exchange oldExchange, Exchange newExchange)throws Exception{
		
		ArrayList> balanceList =(ArrayList>) newExchange.getIn().getBody(ArrayList.class);	
		HashMap result = balanceList.get(0);
		Integer newBalance = ((Integer)result.get("BALANCE")) +((Integer)newExchange.getIn().getHeader("amt",Integer.class));
		
		if("Diamond".equalsIgnoreCase(newExchange.getIn().getHeader("amt",String.class))){
			newBalance -= DIAMOND_FEE;
		}else if("Gold".equalsIgnoreCase(newExchange.getIn().getHeader("amt",String.class))){
			newBalance -= GOLD_FEE;
		}else{
			newBalance -= NORMAL_FEE;
		}
		
		if(newBalance < 0){
			throw new Exception("NOT ENOUGH BALANCE");
		}
		
		newExchange.getIn().setBody(newBalance);
		System.out.println( "--->newBalance :["+newBalance+"]" );
	} 
	
	public void doBalanceWithoutFee(Exchange oldExchange, Exchange newExchange)throws Exception{
		
		ArrayList> balanceList =(ArrayList>) newExchange.getIn().getBody(ArrayList.class);	
		HashMap result = balanceList.get(0);
		Integer newBalance = ((Integer)result.get("BALANCE")) +((Integer)newExchange.getIn().getHeader("amt",Integer.class));
		
		
		if(newBalance < 0){
			throw new Exception("NOT ENOUGH BALANCE");
		}
		
		newExchange.getIn().setBody(newBalance);
		System.out.println( "--->newBalance :["+newBalance+"] countError:["+countError+"]" );
		
	} 	
	

}


ii) doTransfer







This route is very similar with last one, but since transfer occurs between 2 accounts, so there are more select and update works to be done. Also within the route you will see a java bean, it is the actual business logic to calculate the how much to add or deduct and determine how much rate bank should charge.


    
        
        
            SELECT balance from customerdemo where customerID = '${header.CustId}';
        
        
        
        
        
            UPDATE customerdemo SET balance = ${body} where customerID = '${header.CustId}';
        
        
            SELECT balance from customerdemo where customerID = '${header.receiverId}';
        
        
        
        
        
            ${header.transfersql}  UPDATE customerdemo SET balance = ${body} where customerID = '${header.receiverId}';
        
        
    

Lastly, because we are using tables in memory, so there are some preparation needs to be done beforehand. Here is a very simple setup of creating tables and accounts in database. Also a timer that display all the account within database in log.


    
        
        
            CREATE TABLE customerdemo (customerID character varying(10) NOT NULL,vipStatus character varying(10) NOT NULL ,  balance integer NOT NULL);
        
        
    
    
        
        
            INSERT INTO customerdemo (customerID,vipStatus,balance) VALUES ('A01','Diamond',1000);
            INSERT INTO customerdemo (customerID,vipStatus,balance) VALUES ('A02','Gold',500); 
        
        
    
    
        
        
            select * from customerdemo
        
        
        
    


Here is the follow up video, please take a look at the part 1 if you have not see before. 


We can also deploy this example onto Fuse Fabric , please go to my code repo, and find the installation script, and run init.sh. 

To run the demo, in browser enter http://localhost:8181 and login with ID/PWD of admin/adminUnder Runtime, you will see list of containers, and click on the small icon on the righthand-side of the testcon container Fabric listInside the Container, under Camel tab, you will see the list of routes we have. Container Route ListClick on Endpoint on the lefthand-side, choose the file endpoint, and send the xml. Containter Endpoint SendYou will see the transfer result in the log.Container Log

Enjoy! 


Comments

Netuh said…
Hello again Christina,

I was trying to follow your tutorial and deploy this example here in my local machine.

However I got some errors. First I got a error in deploy with fabric8. The bundle creation failed due to incompatibility error.

I could workaround with this problem by adding the following lines in my pom.xml


io.fabric8
fabric8-maven-plugin
1.0.0-SNAPSHOT

http://localhost:8181/jolokia



Then the bundle is create with success, however When I create a container with the created profile. The following error appears.

Provision Exception:
org.osgi.service.resolver.ResolutionException: Unable to resolve dummy/0.0.0: missing requirement [dummy/0.0.0] osgi.identity; osgi.identity=database; type=osgi.bundle; version="[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]" [caused by: Unable to resolve database/1.0.0.SNAPSHOT: missing requirement [database/1.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.apache.commons.dbcp)(version>=1.4.0)(!(version>=2.0.0)))" [caused by: Unable to resolve org.apache.commons.dbcp/1.4.0: missing requirement [org.apache.commons.dbcp/1.4.0] osgi.wiring.package; filter:="(osgi.wiring.package=org.apache.commons.pool)"]]

Do you have a clue of the why it is not working?

thanks for the attention.
Christina Lin said…
Add Full profile in your container should solve your problem! :)

Popular posts from this blog

Red Hat Fuse - Announcing Fuse 7 Tech preview 3 release.

Red Hat Fuse 7.0 technical preview three is out today! On the pathway to become one of the best cloud-native integration platform, Fuse gives developer freedom to choose how they want to develop the integration solution, where they want to deploy it and capabilities to address new integration personas that do not have development experience.
By supporting the three major runtime, developer is free to work on the runtime of their choice.By supporting standalone and cloud deployment, it simplifies the complexity to distinguish between these environments, allowing application to deploy freely among the environment of your choice. All levels of developers are welcome, you can either dive deep into creating customize complex integration logic, or using the new low code platform to quickly build a simple integration. In this Tech Preview release you get it all.
Fuse StandaloneSpring-boot for microserviceKaraf 4 for OSGi loverJBoss EAP for JavaEE developersFuse on OpenShiftPlugins for easy co…

JBoss EAP 6 - 效能調校 (一) DataSource 的 Connection Pool

效能沒有什麼Best Practice, 反正能調整的就那些。 通常,一個程式的效能大概有70-80% 都跟程式怎麼寫的其實比較有關係。

最近我最疼愛的小貓Puji 因為膀胱結石開刀的時候過世了,心情很差請原諒我的口氣沒有很好,也沒有心情寫部落格。

Puji R.I.P.

=======================正文=======================

這個題目很多人叫我寫,可是這題目好大,這分明就是整死我咩~
所以我會分幾段慢慢寫。

JBoss 的 SubsystemDatasource WebWeb Service EJB Hibernate JMSJCAJVM 調校OS (作業系統)

先來看一下 DataSource Subsystem, DataSource 的部分主要是針對Connection Pool 做調校。

通常,程式都會需要跟資料庫界接,電腦在本機,尤其是在記憶體的運算很快,但是一旦要外部的資源連接,就是會非常的耗資源。所以現在的應用程式伺服器都會有個Pool 放一些先連接好的 資料庫connection,當程式有需要的時候就可以馬上提供,而不用花那些多餘的資源去連接資料庫。

這就是為什麼要針對Connection Pool 去做調校。

以下會討論到的參數,都是跟效能比較有關係,Datasource 還有很多參數,像是檢核connection 是否正確的,我都不會提到。如果你追求的是非常快速的效能,那我建議你一個檢核都不要加。當然,這樣就會為伺服器上面執行的程式帶來風險。這就是你要在效能與正確,安全性上面的取捨了。 (套句我朋友說的話,不可能又要馬兒好,又要馬兒不吃草的..)

最重要的調校參數就是 Connection 的 Pool 數量。(也就是那個Pool 裡面要放幾條的connection.) 這個參數是每一個應用程式都不一樣的。

min-pool-size 

Connection Pool 最少會存留的connection 數量

max-pool-size 

Connection Pool 最多可以開啓的 connection 數量

prefill

事先將connection pool 裡面建立好min-pool-size 的connection.

我的建議是觀察一下平常程式要用到的量設定為 min-pool-size 。
加上…

Fuse - Contract First API Design with Apicurio and Fuse/Camel - Part One

This is part one of my two-article series that demonstrates the approach of implementing contract-first API design using Apicurioand Red Hat Fuse.

It covers how to create an OpenAPI standard document as the contract between API providers and consumers using Apicurio. It also shows how to quickly create mock tests using Red Hat Fuse.

There are two common approaches of creating these APIs.
Code FirstContract First Coming from a old time ESB developer, these are not new. We have been doing this forever. Before, it was the WSDL that define the contract of the service. we were doing a lot more code first, for me it's simply because it's much easier for me to write couple of Java classes and generate the WSDL for my consumer. 

It's often pretty straightforward if the consumer of your application has finalized how they want the service to be like. But you and I all know this is not often the case. So I had to go back to my code, and make the changes accordingly and pray I did not …