Mule Proxy Component Implementation to Speed-Up Unification of Customer Infrastructure

  • Duration: 4 months
  • Industries: Telecom Industry; IT Industry
  • Services: Backend Development; Manual Testing Services; Software Reengineering, Refactoring and Modernization. Cloud Migration; Software Integration Services
  • Software Categories and Types: Integration Solutions; B2B Solutions
  • IT Architecture Paradigms and Approaches: Data Driven Testing (DDT)
  • Technical Expertise: Java Server Side Development; Research and Development (R&D); Security Enablement and Audit (digital signature, WS standards, OASIS best practices)
  • DevOps Expertise: CI/CD Basics
  • Technologies: Java Standard Edition (SE); Data Bases; Mule Runtime; Apache Log4j; JUnit / TestNG; Java; XSLT; Backend; Oracle DB; Spring; XML based technologies; XPath; Test Automation; Standards and Protocols; Mule ESB; Message Queues and Service Buses; Languages, Protocols, APIs, Network Tools; JDBC; SOAP WebServices; Java Libraries; Apache Commons; Logging Libraries
  • Team size (3):
  • 1 Project Manager
  • 2 Backend

Provided services

Backend Development, Manual Testing Services, Software Reengineering, Refactoring and Modernization. Cloud Migration, Software Integration Services


Our client is the European market leader for Telecom Management Technology. Its solutions are provided in over 42 countries and are available for over 150 carriers.


The primary project objective was to develop a proxy using Mule technology, facilitating the integration of the client’s internal system with external services. The application receives SOAP requests from the internal system or external service, processes them, and forwards them to the recipient. The app allows safely exchanging messages between two systems. And it doesn’t require any changes in the integrable services.


Our customer actively invested in the unification of their infrastructure, having a development plan for unified (reusable) components. However, the customer had an expensive support cycle for these components. The primary challenge became the necessity to develop a component that was not only easy to use but also possessed a high level of reliability. The key requirement was the ability for reuse in various scenarios, meaning it should be easily extensible. As a significant number of other components and products of the customer will be dependent on this component, we anticipated the inevitability of multiple product versions.

Project Context

  • Our team had to work in compliance with strict safety rules. There was not even direct access to the test environment: databases, servers, etc.
  • Part of the customer requirements arose and was applied at the stage of active development.
  • The rather complex and required good communication skills integration with the third-party teams, situated in other countries, was required.
Need help


To address this, we implemented a CI/CD (Continuous Integration/Continuous Deployment) process, fully automating manual operations, and trained the product owner in launching necessary CI/CD tasks. We configured the application versioning process to enhance transparency, change management, and ensure stability during the development of various application versions.

Consequently, we not only delivered the required component but also implemented a lifecycle management system for this component. This became a key factor in accelerating the unification process, fostering an optimistic outlook from the client regarding the possibilities of unification and stimulated the creation of dozens of new components.

Technological Overview

The following mechanisms were used on the project:

  • validation of SOAP messages;
  • authentication according to WS-Security specification;
  • conversion of the message into the required format.

During development, the engineers used approaches that make it easy to reorient the application for integration with other services. This has made the app universal, and significantly reduced the costs of integration with other systems.


  • All planned functionalities were implemented, and all requirements, received during the development, were applied. The client got an easily extensible, reliable component with a low-cost support cycle.
  • The application is widely used by the client and does not cause any complaints about stability and performance.
  • Comprehensive documentation on application operation was meticulously prepared.
  • The implementation of CI/CD principles in this project was successfully applied to all subsequent components. The overall time for routine operations decreased by a factor of 5.

JazzTeam Achievement

  • JazzTeam performed well during integration with third-party team, often taking the lead in synchronization activities. It made the integration process open and understandable for the customer.
  • The team has taken the initiative to profile the application and adapt it for usage with maximum loading.
  • In the conditions of close cooperation between all the teams, the clear process of manual testing was adjusted, the unit tests were created, and load testing was done.


Stack: Mule ESB, Java, Spring, Log4j, Apache commons libraries, XML, XSLT, XPath.

Infrastructure: Jenkins, SVN, Anypoint Studio.

Test Automation Libraries: JUnit.

DB: Oracle.

Protocols: HTTPS, JDBC, SOAP.

Clients about cooperation with JazzTeam

Related projects

Recent Work

    Contact Us

    What happens next?
    • 1

      Leave your project request. We will contact you and schedule a call.

    • 2

      Signing of the NDA to ensure the project info confidentiality.

    • 3

      Negotiation of your request and the required services.

    • 4

      Team forming, coordination of workstages.

    • 5

      Contract signing and project start.