Phone:+91-810*******
Akshaya Kumar Mohanty. E-mail:
*****.****@*****.***
Professional Summary:
. Senior Software Engineer with 7 years of IT experience in software
development lifecycle in web application development and distributed
computing.
. 5 years of experience on ESB (IBM Websphere Message Broker 7.0 and
IBM Websphere MQ 7.0) and working as a EAI developer.
. Certified solution developer in WMB 7.0.
. Three years of Experience on Retail Domain .
. Experience on middleware Technologies like: (Java WebServices, IBM
Websphere Message Broker 7.0 and IBM Websphere MQ 7.0).
. Achieved Team Award for S1 CB 2.4 project for developing and
maintenance work.
. Attended Training program on Postilion Real-Time Framework and
Postilion Adaptors.
. Excellent communication, interpersonal, analysis, organizational and
leadership skills. Quick learner, versatile, adaptable and process-
oriented, with a high customer orientation.
. Involved in project communication, reporting, quality assurance,
coding, maintenance and designing.
Educational Qualification:
. MCA(2000-2003)Batch From Biju Patnaik University Of Technology,
Orissa.
Experience and Technical Skills
Operating Systems : Windows 2000/XP
Programming Languages : JAVA
J2ee Technologies : JDBC, JSP, Servlets.
Middleware Technologies : Web services, WebSphere Message Broker
7.0, WebSphere MQ 7.0
Web Technologies : HTML, Java Script, XML .
Database : Oracle, and DB2
Database Tools : Toad, SQL Station
Web Server : IBM Websphere
Bug Tracking Tools : JIRA, Clear Quest.
IDE : Eclipse, WSAD 5.1, Rational Software
Architect(RSA), WebSphere Message Broker toolkit.
Frameworks : Spring
DataMapper : iBATIS, Hybernate
Configuration Tool : ClearCase,Dimensions,
TeamPrise(TFS)
Employment History:
. April 2011 - Till date working as Senior Software Engineer in [pic]
IBM India Private Limited, Kolkata.
. July 2007 - April 2011 Worked as Software Engineer in [pic]
Target India, Bangalore.
. March 2006 - June 2007Worked as a Software Engineer in [pic] Vmoksha
Technologies, Bangalore
Project Highlights:
Employer: IBM
April 2011- Till Date
Blue Harmoney
Technologies : Web sphere MQ7.0, Web sphere Message Broker7.0,
RFHUTIL
Team Size : 25
SAP GARS will submit BP sales orders from their PTX web site. The PTX
website presents GARS inventory (used machines and feature) to the BPs and
BPs interact with SAP GARS (via IGF Msg Hub) to confirm the ordered
product, quantities and price. GARS sets the price for all products sold
on the PTX website.
Once the orders are confirmed in PTX, the IGF Msg Hub will transmit an
order file to eSH. eSH will create an quote IDOC and transmit same to SAP
CRM for quote and sales order creation. Feature orders will be processed
as MES orders; some will be history-based MES tied to a specific type /
model / serial and others will be processed as Bulk MESs where a serial# is
not provided by the BP. All machine orders will be orders as configured
machines (TMF configuration data provided by IGF Msg Hub to eSH will be
convereted via callable service to BH Cs & Vs and transmitted on the Quote
IDOC to BH - same for the MES/feature orders.
Responsibility:
. Validate, route, and then transform those messages as per project
requirement.
. Development message flow using Mapping Nodes and esql.
. Taking the performance matrix report to tune the performance of
message flow.
. Testing the end to end MB flow through middleware monitoring and
management web based tool (RFHUTIL).
. Documenting the key project information for future use for new team
members.
Employer: Target India
July 2007- April 2011
Target.com:
Date: Mar 09- April 2011
Prism to WCS
Technologies : Web sphere MQ7.0, Web sphere Message Broker7.0,
RFHUTIL
Team Size : 20
PRISM generates events when items are created and updated. IP publish job
will process the events (IP subscribed) and generates the XML message and
pushes it to IL pub-sub flow. The received input message is transformed to
WCS/CMS specific format by the IL. The transformation is done for one item
per message and then the transformed messages are batched up to generate an
output message with multiple items populated on the output queues. The
number of messages to be batched is stored in a config XML file. WCS and
CMS will consume the messages from the respective IL output queues. WCS
will process them asynchronously to update in WCS DB. CMS will update the
attributes it needs to update and send the feed back to WCS through a
separate flow. Following is a detailed description at each sub-component.
Various workflows associated with various components work in tandem to
achieve the end 2 end flows. This document details the workflows and
components in the context of the performance testing being executed.
Responsibility:
. Working with PUB-SUB Model.
. Validate, route, and then transform those messages as per project
requirement.
. Development message flows using Mapping Nodes and esql.
. Testing the end to end MB flow through middleware monitoring and
management web based tool (RFHUTIL).
. Documenting the key project information for future use for new team
members.
DVS Order Management Phase 1
Technologies : Web sphere MQ7.0, Web sphere Message Broker7.0, QPASA
Team Size : 20
Project Description:
The goal of DVS interfaces is to implement order management solution
specifically focused for DVS vendor.DVS Order Management Phase 1 is a
critical first step to enable the long term order fulfillment vision for
Target.com. The first phase of this project is to implement a new order
management solution that will provide a stable foundation for growth for
the whole network while supporting the volume and minimizing the
transaction costs of Movies, Music & Books (MMB). Future releases to this
platform will migrate the remaining DVS vendors as well as Target.com owned
facilities.
Responsibility:
. Validate, route, and then transform those messages as per project
requirement.
. Development message flow using Mapping Nodes and esql.
. Testing the end to end MB flow through middleware monitoring and
management web based tool (QPASA).
. Documenting the key project information for future use for new team
members.
Dist Common Web
Technologies : Core Java, Xml, iBatis, Web Services, Oracle, spring,
RSA 7.0, Junit.
Team Size : 6
Project Description:
The exposes common functionalities as web service operations Examples
include authenticate, authorize, get DC configuration etc., Users need to
be authenticated/authorized before using any core applications.
Responsibility:
. Involved in Middleware Technologies for development of business logic
using Web Services.
. Worked on Middleware for creation of WSDL files, Adapter and generate
of skeleton through Web services.
. Involved in testing of Operations using Junit.
. Interacting with DB using toad and SQL Station.
Supply Chain:
Date:July 07- Feb 09
DWH ATG Migration.
Technologies : CoreJava, Xml, iBatis, WebServices, Oracle, spring, RSA,
Junit.
Team Size : 6
Project Description:
DWH web application which has been implemented on ATG 7.1 needs to be
implemented on the new Java Stack. The new stack has Spring as the chosen
framework on the presentation and business services layer. Also, IOC
framework of Spring is used for wiring objects i.e., injecting dependency.
In the section below, we'll look at how components in ATG need to be re-
written in Spring. We'll look at layer specific changes namely
Presentation, Business, DAO and also miscellaneous changes.
Responsibility:
. Worked as a Team member for developing Involved in the migration from
ATG to spring.
. Worked on Middleware for creation of WSDL files, Adapter and generate
of skeleton through Web services.
. Involved in testing of Operations using Junit.
. Interacting with DB with SQL Station and Toad.
Shipping Full.
Technologies : CoreJava, Xml, iBatis, WebServices, Oracle, spring, RSA,
Junit.
Team Size : 6
Project Description:
The shipping business process begins when containers are either diverted
automatically by the sortation systems or manually moved into the non-con
staging area and scanned via radio frequency device and loaded on to the
trailer or associated to a master container for loading at a later time.
The shipping process ends when the trailer is closed and sealed, a bill of
lading is printed and shipment details have been uploaded to the host
systems. Yard Management and Transportation complete the process from the
yard to the store.
Responsibility:
. Worked as a Team member on Middleware for creation of WSDL files,
Adapter and generate of skeleton through Web services.
. Involved in testing of Operations using Junit.
. Interacting with DB with Toad and SQL Station.
Shipping Pilot
Technologies : CoreJava, Xml, iBatis, WebServices, Oracle, spring, RSA,
Junit.
Team Size : 6
Project Description:
The Pilot will be the first production application to be built using the
tech refresh architecture.Demonstrate that a representative set of
functionality currently residing in the Distribution DC applications can be
successfully built and deployed to a DC.
The screens that will be in scope for the pilot are as follows:
SCL - Scan Cutoff
SCT - Close Trailer
SNL - Load non con
SUL - Unload Trailer
SMT - Move Trailer
STF - Trailer Function Menu
SOS - Open Shipment
SFM - Shipping Function Menu
Responsibility:
. Worked as a Team member on Middleware for creation of WSDL files,
Adapter and generate of skeleton through Web services.
. Involved in testing of Operations using Junit.
. Interacting with DB with Toad.
Employer: Vmoksha Technologies March 2006 - June 2007
1
S1 Product Development and Maintenance Date: March-06 to June-07
Client : S1 Corporation, US
Skills : Web sphere, DB2, Java, J2EE, Struts, WSAD, JIRA, Clear
Case.
Team Size : 13
Project Description:
The S1 Enterprise Platform is a comprehensive Internet solution offering
banking, brokerage, insurance and bill presentment functionality as well as
one-to-one marketing capabilities, content and financial planning tools. It
provides customers with a complete, integrated picture of their financial
position in a convenient and secure location. Make financial web based
information available with normal security procedures via emerging
technologies and multiple delivery channels. The product is developed using
J2EE architecture and it is an iterative object oriented distributed
development. Functionally is divided into four major modules Personal
Banking, Business Banking, Corporate Banking, and SAM.
SAM is the workhorse behind the scenes of S1 Enterprise Corporate Banking.
It enables your customer services representatives, marketing personnel and
system administrators to seamlessly manage your Internet products and to
market and service customers. S1 Application Manager includes the ability
to perform on-behalf of transactions, set up and manage marketing
campaigns, manage bank branding, customize affiliate bank parameters,
generate system reports, set up companies, and much more.
Responsibility:
. Worked as a Team member for developing and maintenance of Corporate
Banking & SAM Modules
. Worked Extensively on Payment module.
. Worked on UI, validation framework, Action Classes and Action Forms in
Struts.
. Reproducing them in the Application, Fixing and checking in the fixes
into the appropriate code base.
Online Cash Manager
SunTrust's branding of S1's online Business Date :March-07 to
June-07
Client : S1 Corporation,USA.
Technologies : CoreJava,JSP,XSL,
DB2,Websphere,ClearCase,EP,Struts,WSAD.
Team Size : 13
Project Description:
2
This Project describes the customized branding to SunTrust's existing
Online Cash Manager(OCM) application.
It is intended for use by: S1 Professional Services Organization (PSO)
Development Team
S1 and SunTrust Technical Staff responsible for branding
SunTrust Bank's Business Unit.
Responsibility:
. Worked as a Team member for developing and maintenance of Corporate
Banking & SAM Modules
. Worked Extensively on User Interface module.
. Worked on XML, validation and changed the look and feel using XSL and
properties file for navigation purpose.
. Doing Code Reviews and self testing of the application.