#WSO2 Enterprise Service Bus Exploration Project IF-4050 Experimentals Services on WSO2 ESB
WSO2 ESB, as an ESB WSO2 ESB is constructed to enable communication among various applications (in this case we only tried with a few services). Here we enable some of our simple services as shown above that is registered in our WSO2 ESB.
This read me includes several section that explain this project. Sections are :
- Story
- Technical Explanation
- Exploration
In this project we choose to explore the chaining function in WSO2 ESB. The following are the story of our exploration scenario.
To test the chaining function of ESB we create a few simple services to communicate within the ESB.
####The Scene So, we have a service that serves high schools students who just have take a test (SNMPTN) to be a student of their dream universities.
In our case, we have the services as shown below. These services serve newly accepted students to check their test results and inform them to complete the payment and register to their new school.
The services are :
- Pengecekan kelulusan SNMPTN (By Fatoni)
- Pemrosesan pendaftaran ulang (by Andy)
- Pemrosesan tagihan pembayaran (by Harya)
- Service Central (by Hendy)
##Services Explanation ###Pengecekan kelulusan SNMPTN This service enable test participants to check their result by inputing their test number. Status will shown as result for inputing test number.
###Pemrosesan pendaftaran ulang pemrosesan pendaftaran ulang serve newly accepted students to register. The service will receive a set of number which represent the students test number and return the allocated faculty and student number represented by NIM for them.
###Pemrosesan tagihan pembayaran
Now, for the invoicing service we call pemrosesan tagihan pembayaran. This will generate the complete payment needed for the newly accepted students by inputing NIM. The result that'll responded by this service is number of the payment needed to pay. ####service usage /services/Cek?wsdl
The things we do is similar to the image above, we manage the communication between several services that create a function as we explained sections before.
Here is how the chaining sequence we designed for this project, as we explained the scenario above.
Each of our services now already running but, the 'chaining' part is not cleary done. There are some trouble creating the sequence in order to prove the chaining function of esb.
So in order to simulate the orchestration in ESB, temporarily we create a service central module that function to orchestrate our services. and use the WSO2 ESB as a proxy.
###Simple Content-Based Routing (CBR) of Messages
Here are our trial on creating a simple message routing using sequence in the ESB. The following will explain about our exploration in Simple Content-Based Routing (CBR) of Messages.
####Environment
we complete these test project within these environment :
- OS : Ubuntu Server 14.04 LTS 64 bit
- CPU : 4 Core Intel i7
- RAM : 4 gb
- HDD : 20gb
####ESB Main Configuration
ESB Configuration using filter mediator to route the message received from
http:/<url>/StockQuote
to the URI of the real service.
####Back-End Service Deployment (SimpleStockQuote Service)
-
Build SimpleStockQuote Service from
<wso2_home>/samples/axis2Serversrc/SimpleStockQuoteService/
-
Run axis2server.sh
<wso2_home>/samples/axis2Server/
####The Test! Now to do so, we run the client by calling
ant stockquote - Dtrpurl=http://localhost:8280/services/StockQuote
from :
<wso2_home>/samples/axis2Client
The Result
Here is what will we get :
the port 8280 is the port that used in ESB for ESB HTTP-NIO, this can be known from the configuration file located in
<wso2_home>/repository/conf/axis2/axis2.xml
- M Harya Putra 18211011@std.stei.itb.ac.id
- Andy Primawan 18211030@std.stei.itb.ac.id
- Christian Hendy 18211036@std.stei.itb.ac.id
- M Fatoni 18211042@std.stei.itb.ac.id
- Aria Dhanang 182110@std.stei.itb.ac.id