Skip to main content

Write your own service and deploy into Axis2

In this blog, i’m going to implement a simple service “OderProcessingService”, with 2 operations “getPrice” and “update”; and then deploy it into axis2.

 Step 1: Get your environment ready

  1. Download and install Java. Set the JAVA_HOME environment variable to the pathname of the directory into which you installed the JDK release.
  2. Download and install Tomcat to the a directory [CATALINA_HOME]; you can access its service at http://localhost:8080
  3. Download the newest version of Axis2; WAR distribution and Standard distribution
  4. Install Axis2 WAR distribution on Tomcat; drop the .war file at CATALINA_HOME\webapps and restart Tomcat; make sure the deployment accessing http://localhost:8080/axis2
  5. Install Axis2 standard distribution; upzip the distribution to a directory; [AXIS2_HOME]
  6. Add all .jar files in AXIS2_HOME\lib\* to the CLASSPATH
Step 2: Create the service
package com.wso2.orderprocessing.service;

import java.util.HashMap;
import java.util.Map;

public class OrderProcessingService {
   
   private Map<String, Double> orderMap = new HashMap<String, Double>(0);
   
   public double getPrice(String symbol) {
       Double price = (Double) orderMap.get(symbol);
       if(price != null){
           return price.doubleValue();
       }
       return 42.00;
    }

    public void update(String symbol, double price) {
      orderMap.put(symbol, new Double(price));
    }    
}
Step 3: Create the service.xml
<?xml version="1.0" encoding="UTF-8"?>
<service name="OrderProcessingService" scope="application">
    <description>
       Order Processing Service
    </description>
   
    <parameter name="ServiceClass">com.wso2.orderprocessing.service.OrderProcessingService</parameter>
   
    <operation name="getPrice">
       <messageReceiver class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
    </operation>
    <operation name="update">
       <messageReceiver class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/>
    </operation>    
</service>
services.xml file informs the axis about the service.
Step 4: Package the service

Service need to be packaged in a certain format in order to deploy in Axis2.
[The package must be a .jar file with the compiled Java classes and a META-INF folder which holds the services.xml file. The jar file can be name .aar to distinguish it as an Axis2 service archive. The file name before ".aar" should be the name of the service]


1. Compile the service and put it on the target folder
2. Copy services.xml file to META-INF folder
3. Create .aar file >> jar -cvf OrderProcessingService.aar *
Step 5: Deploy the service

Copy the OrderProcessingService.aar file to CATALINA_HOME/webapps/axis2/WEB-INF/services/ and restart the tomcat

Go to the http://localhost:8080/axis2/services/listServices URL then you can see the OrderProcessingService listed there as follows


    Labels:

    Comments

    Post a Comment

    Popular posts from this blog

    How to generate random unique number in SOAP UI request

    eg 1: ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} eg 2: ${=java.util.UUID.randomUUID()} ${=java.util.UUID.randomUUID()} ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf
    Post a Comment
    Read more

    Tips on using environment variables in WSO2 Integration Cloud

    Environment variables allow you to change an application's internal configuration without changing its source code. Let’s say you want to deploy the same application in development, testing  and production environments. Then database related configs and some other internal configurations may change from one environment to another. If we can define these configurations as an environment variables we can easily set those without changing the source code of that application. When you deploy your application in WSO2 Integration Cloud, it lets you define environment variables via the UI. Whenever you change the values of environment variables, you just need to redeploy the application for the changes to take effect. Predefined environment variables Key Concepts - Environment Variables   provides you some predefined set of environment variables which will be useful when deploying applications in WSO2 Integration Cloud. Sample on how to use environment variables ...
    Post a Comment
    Read more

    WSO2 ESB communication with WSO2 ESB Analytics

    This blog post is about how & what ports involved when connecting from WSO2 ESB to WSO2 ESB Analytics. How to configure: This document explains how to configure it https://docs.wso2.com/display/ESB500/Prerequisites+to+Publish+Statistics Let's say we have WSO2 ESB  and WSO2 ESB Analytics packs we want to run in same physical machine, then we have to offset one instance.  But we don't want to do that since WSO2 ESB Analytics by default come with the offset. So WSO2ESB will run on 9443 port, WSO2 ESB Analytics will run on 9444 port WSO2 ESB publish data to the WSO2 ESB Analytics via thrift. By default thrift port is 7611 and corresponding ssl thrift port is 7711 (7611+100), check the data-bridge-config.xml file which is in analytics server config directory .  Since we are shipping analytics products with offset 1 then thrift ports are 7612 and ssl port is 7712. Here, ssl port (7712) is used for initial authentication purposes of data publisher ...
    Post a Comment
    Read more