SUMMARY:

• Smart - working skilled Professional with 17 years of experience in Software Development
• 10+ years as an application Integrator, Application Architect, SDLC System Design, Business Process automation.
• 14+ years in Java/J2SE/J2EE; 9 years in SOA/EAI.
• Designed and Developed Enterprise Architecture, Policies and Standards.
• Designed and Developed SOA, EAI, J2EE, Web Services and workflow based solutions for cost reduction, integration with disparate systems and efficiency improvements.
• Working effectively with Stakeholders(business and technical folks)
• Technical Design authority and Assurance (Architecture reviews, Design and Code Reviews); ensuring adherence to IT strategy, Architecture, Policies and Standards.
• Decisions for Architecting, Designing, Building and Management of small/large scale service/components based Enterprise Business Solutions.
• Enterprise Architecture Models(Business, Applications, Data and Technology).
• Risk Identification and Management.
• Working complex problems through to simple solutions recognizing synergies and options;
• Researching new technologies that can drive innovation.

PROFESSIONAL EXPERIENCE:

Confidential

Application Architect

• As an Application Architect, responsible for implementing POCs for their pub-sub solution and Confidential of their legacy applications to Amazon cloud using Jboss Fuse ESB and Spring Batch.
• Proposed solution for Pub-Sub consists of Jboss based Fuse ESB with fabric containers as elastically expandable layers. Each layer will host one concern of the overall pub-sub solution using fuse out-of-the box configurable feature profiless.
• In the pub-sub solution all that applications ALE, OTTO, EPM and OM that needs to communicate using pub-sub model are deployed as web services in a fabric containers that are defined using fuse CXF profile to host the web services.
• Broker layer that is profiled with ActiveMQ profile is the communication bridge between applications using MEP will run in another fuse fabric container that can expand automatically in Amazon cloud environment.
• Orchestration of applications and interaction of applications with external systems or users are done using in another fuse fabric layer profiled with fuse out-of-the box configuration feature Camel.
• This layer will have endpoints, connection points, routes, flows, and transformation logic for messages that are exchange between applications.
• This layered approach of using the containers for each concern in the overall solution gives the flexibility for the runtime environment in Amazon cloud to expand automatically.
• Confidential solution using spring batch will run in Amazon cloud, consists of 3 main components, Web services to upload files in CSV format and create Batch Jobs, Spring Batch Application running as web component to process the CSV files and create complex Json file for the target application, and the FTP Component that delivers that final Json file to target applications.
• Amazon EC2 instance is used to run the Spring Batch and web services to upload and process the files.
• Amazon S3 is used to store user or applications to upload files. EBS is used for local storage in EC2. Tomcat for hosting web services and running Spring Batch application to process the CSV.
• Other options, MangoDB and RDS are explored to store intermediate data before generating the target Jason.

Environment: Java, J2EE, Struts, Jboss Fuse, Active MQ, Fabric Server, JMS, CXF, CAMEL, REST, Tomcat, AWS, EC2, S3, Spring Batch, Spring Scheduling.

Confidential,New Jersey

Application Architect/Interface Lead

• As an Interface lead/Architect, responsible for working with different application teams to understand the requirements and issues with existing architecture and define a new architecture that address all views of the architecture logical view, deployment view, process view and physical view of the cass interface applications.
• Identified different design and architecture flaws in existing poorly performed interface applications, and provided different architectural solution that can be workable in all stages or phases of the system using reusable common code, loosely coupled components, flexible deployment model.
• Applied layered architecture to separate the technical concerns between the applications that use different data processing methodologies.
• Implemented Hadoop (MapReduce, Hive, Hbase and Yarn)technologies to process flat files (text files) with millions and millions of records from the partners and the legacy systems in the conversion efforts for the Curam Application implementation.
• Defined a runtime view of a system that will have minimal impact on each other when one system on maintenance or a failed status.
• Defined and developed components that can be extendable with minimal efforts when system goes future changes.

Environment: Java,J2EE, JSP, Struts, Curam, Advantage, IBM Web Sphere Application Server, IBM Business Process Server, Web Sphere Process Server(WPS), IBM Integration Developer, Business Objects, Web Sphere Enterprise Service Bus, Service Security, SAML,Web Sphere Message Queue, Advantage, AIX, Spring Batch, Spring Scheduling.

Confidential, CA

• As an Interface lead, responsible for working with different application teams to understand the requirements and needs, and define an architecture for middle ware layer ESB that will orchestrate the interdependent applications, and provide transformation, routing and load-balancing needs of upstream and down-stream applications.
• Defined failover and High Available architecture to support 24/7 system availability SLA for batch and online applications.
• Utilized MQ clustering feature to support load balancing the high volume through batch jobs using HA setup.
• Utilized Multithreading to improve the through put.
• Defined a runtime view of a system that will minimal impact on each other when one system on maintenance or a failed status.
• Defined and developed components that can be extendable with minimal efforts when system goes future changes.
• Utilized different applications protocols(FTP,SFTP,HTTP,HTTPS) to integrate different applications and worked with different

Environment: Edifes, IBM Web sphere message broker, IBM Web Sphere Application Server, IBM Business Process Server, Web Sphere Process Server(WPS), IBM Integration Developer, Business Objects, Web Sphere Enterprise Service Bus, Web Sphere Message Broker, AIX, Spring Batch, Spring Scheduling,Java,J2EE, JSP,Struts.

Confidential, Roseville, CA

Interface and Integration Architect

• Involved in this project from the beginning of the RFP in defining the Design and Architecture of the System.
• Provided the design solution that includes end-to-end Process Flow, Web Services definitions/message formats/System Alerts/SLAs, integration services using Curam, IBM Business Integration Services, Advantage Payroll Systems.
• Creation of Data Services using IBMs Web Sphere Process Server to receive the updates from the downstream systems Case Management Curam Application, Adavantage Payroll system and Business Objects Batch Process and deliver it to the external partners using IBMs Adapters.
• Provided the use case analysis and Object Oriented Analysis on the system requirements to derive domain model and use the domain model to customize the Curam Cots package to State of California’s Case Management System requirements.
• Develop Technical Road Maps using the estimates and technical requirements analysis.
• Work Allocation to Developers.
• Creation of Technical Policies and Standards.
• Reporting to Application Services team Directors, Deputy Directors.

Environment: Java, J2EE, JSP, Struts, Curam, Advantage, IBM Web Sphere Application Server, IBM Business Process Server, Web Sphere Process Server(WPS), IBM Integration Developer, Business Objects, Web Sphere Enterprise Service Bus, Web Sphere Message Queue, Advantage, AIX, Spring Batch, Spring Scheduling.

Confidential,Camp Hill,PA

Application Interface Lead

• Working with BA’S to understand the BCBSMA Health Care Reforms System requirements, Participating in creating and reviewing business requirements.
• Developing the technical requirements in interfacing the MA’s state sub connecter enrollment system for receiving the enrollment X12 files.
• Writing interface components using Seebeyond JCAPS product such as ETD, JCDS, Connector components as eWays, JMS queues, Defining the XSD for input data structure and building input and output data parse components using the Seebeyond JCAPS integrator product. This involves writing interfaces for ftp application, Mainframe, Oracle, MQ Series etc.
• Defining the common exception handling data structure using xsd and building interface components to interface with common exception handling system incase of exception happens in the business system.
• Building business process tracking system and writing interfaces to interact with common tracking system from business application such as Health Care Reforms and Blue Quote plus.
• Rewriting the existing seebeyond 4.5.3 interfaces in to Seebeyond’s latest version JCAP 512 by creating OTD and JCD, connectivity mapping, environment profiles and deploying them in to the JCAPS environment and Understanding the business requirements and interacting with business analysts for more clarification.
• Writing common business logic outside the seebeyonds integration development to facilitate the reusability of the some of the common tasks in the system. And also provide more prove more flexibility in the unit testing process using java Junit API.
• Developing JAVA frame work for some of common business tasks for scheduling and real-time business process to avoid the future conversion efforts when version of vendor product changes.
• Defining and configuring logical host and domains. Creating Deployment Profiles
• Writing junit test cases to test common and reusable business components out side the Seebetond. Deploying and Seebeyond components in the registry host using Enterprise Manager.

Environment: Java, J2EE, Struts, JCA, Web Sphere, JCAPS 5.1.2, Seebeyond 453, Oracle, MQ Series, ESB,WMB,AIX, Spring, Hibernate.

Application Interface Designer

Confidential, NC

• Building the prototypes from high level requirements, Pototyiping the requrements, Demonstrating and getting approvals from Business users. Gathering comments and using them to finalize the detailed design requirements and generating artifact documents. Participate in the technical review sessions and get the sign off on the requirements from architects.
• Building data services for downstream applications using Web Services. This includes web services for publishing message in Web Sphere MQ ESB using Canonical Message format.
• Create a frame work to route Canonical Message to appropriate subscribed applications. This includes routing, subscribing and monitoring the Canonical Message flow.
• Identifying proper framework for error handling and tracking business process flow that can be used across all the subsystem for
• Building interfaces for Blue Squared real-time and batch process from design documents by creating interfacing component for MQ Series, FTP, JMS, Oracle, DB2 applications.
• Designed, Modeled and created Message Models, Message Nodes, Message flows in Message Broker Environment for Blue Square interfaces. Created runtime environment using Execute Groups to host and run Web Sphere Message Broker Message flow applications.
• Building Web Services for Common interface and expose them by deploying them in the Apache AXIS engine.
• Develop Business work flow logic in the java to facilitate the work flow between all the interfaces using the business requirements.
• Providing the estimate and making the time line document and presenting them to users. Phase out the products in to smaller deliverables as per their inputs and expectations and getting sign off at each deliverable status.
• Working with the business analysis team, q/a team, operations teams and other groups in order to implement the application and Services.
• Upgrading to major releases and service packs.
• Mentoring other Co-developers.
• Designed and developed Work Force Web Authentication Interface.
• Designed and Developed Supplemental Factor User Interface Using RAD 6.0 and Struts Framework.

Environment: SOA,WSAD,RAD 6.0, Websphere 5.1, Struts MVC, Seebyond 4.5.3,MQ Series/Web Sphere Message Queue, Web Sphere Message Broker, ESB, Java/J2EE, JSP, Struts, Hibernate.

Confidential, MI

• Web based auto financing system for auto dealers, funded by Ford, Chrysler, Toyota, and GM.
• Designed XML service for J2EE system, which involves capturing the contract worksheet data into the Java objects, converting into the XML schemas using castor and publishing it into Seebeyond JMS queue asynchronously.
• Built middle-ware interface using ‘Seebeyond’ to process the XML message published into the Seebeyond Queues using XML Service. This involves signing the XML message using the Dsig application, creating and sending the SOAP message over HTTPS using Seebeyond HTTP e*Way. This HTTP call involves servlet call which publishes the message into the Finance Source's JMS Queues. Designed the Inbound Application Interface, to process messages from Finance source.
• Designed and developed Test Tool called Simulation Finance Source using Jakarta Struts, JSP, J2EE, Websphere, Seebeyond