Context
Commercial loan applications go through credit scoring and evaluation before a decision is made. New services producing that data had to reach the existing Java backends and the decision engine. webMethods Integration Server sits between them as the enterprise service bus.
New service
→webMethods flow service (ESB)
→Java / Spring Boot backend
→Oracle DB
or
Decision engine: credit scoring
My role
I built the webMethods flow services and developed the Spring Boot services on the receiving end, so I worked on the whole path from consuming the data to handing it over for persistence or decisioning.
What I did
- Built flow services in webMethods Designer that consume data from the new services and map it to the contracts the backends expect.
- Worked with SOAP contracts defined in WSDL and XSD alongside REST endpoints.
- Routed messages to the right Java backend using both synchronous and asynchronous communication.
- Developed and maintained the Spring Boot microservices that persist the data in Oracle or pass it to the decision engine for credit scoring and evaluation.
- Tested services with SoapUI and Postman, and traced defects along the flow to resolve incident records.
Outcome
New services feed the existing backends and the commercial loan decision engine through a single integration layer, instead of each one wiring itself directly to every backend.
Details are generalised to respect client confidentiality. No customer data is shown.