More Related Content
What's hot (20)
Viewers also liked (18)
Similar to Subbu_WM (20)
Subbu_WM
- 1. SUBBARAO.P Phone:+91-7097342434 Email:subbup.wm@gmail.com Summary:  Having 3.5 Years of experience in WebMethods.  Hands on experience in WebMethods Integration platform 8.2/7.1.2/6.5/6.1, building B2B applications and EAI applications.  Maintain and support the production of webMethods Integration Server, B2B, EDI, and Trading Networks including trouble-shooting, performance, and problem resolution.  Experience in various webMethods Adapters (JDBC, SAP, SFDC, MQ, Flat file, and EDI).  Experience in MWS (My webMethods Server) for monitoring.  Comprehensive knowledge of software development life cycle and its phases.  Hands on experience in upgrade and Real Time Production support of WebMethods products.  Working experience on protocols like HTTP, HTTPS, FTP, SFTP, SMTP, MIME and TCP/IP.  Experience in developing and implementing web services and in depth knowledge of SOAP, and integrating with cloud based applications.  Expertise in JMS, Broker pub-sub, MQ paradigms.  Experienced in handling projects independently.  Strong debugging and problem solving skills with excellent understanding of system development methodologies, techniques and tools.  Excellent communication, interpersonal, time management and presentation skills.  Fast paced and eager learner with the ability to successfully utilize new technologies. Education: Master’s in Computer Applications under Bangalore University in Administrative Management College Bangalore in 2010. Technical Skills: Professional Experience:  Currently working as Programmer Analyst at Quinnox Consultancy Services Pvt Ltd in Mumbai from Nov 2013 to till date.  Worked as Associate Software Engineer at Sapient Corporation Pvt Ltd from JAN 2012 to OCT 2013 EAI and B2B Integration webMethods 8.2/7.1.2/6.5/6.1 (IS Developer, TN, Designer,Deployer, Broker, Monitor, MWS, Task Engine) eStandards/Doc EDI, XML, IDoc, Flat Files, SOAP XML. Adapter Types JDBC, SFDC, MQ, EDI, SAP, Flat file. Languages webMethods Flow, C, C++. Databases Oracle 7.x/8i/9i, SQL Server 2000/2005/2008 and DB2 Platforms Windows 98/2000/XP, UNIX, Linux.
- 2. Projects Profile: Project#3: Client Name : COCO COLA Duration : Jan 2014 To Till Date Project Name : CCE Team Size : 6 Role : Programmer Analyst Project Overview:  Coca-Cola Enterprises (CCE) is world’s largest bottlers ,bottle and market Coca-Cola products in Belgium, continental France, Great Britain, Luxembourg ,Netherlands, Norway, and Sweden..  There are 1200 unique trading partners, 193 Carriers, 22 Banks, 75 Bottlers trading 91 document types including 45 Tradacom document types, multiple flat file formats and XML formats run on top of webMethods which uses the common framework for B2B and A2A transactions that processes all data via Trading Networks.  The Invoices for bottles sent from the different client over the North America to the CCR and webMethods integrate it and send over to SAP for payments.  This project is responsible to provide support for the entire client(trading partners) for CCR over the world.  This project is about maintenance of existing Coca-Cola B2B and EAI architecture. Coca-Cola Enterprises is an American multinational beverage corporation and manufacturer, retailer and marketer of non-alcoholic beverage concentrates and syrups. My job as a support engineer mainly entailed maintenance of webMethods servers, fixing problems and resolving issues to ensure smooth operation of systems, keeping close eye on the systems and work proactively to avoid issues and make or suggest code changes or changes to the environment to fix an issue or accommodate new interfaces. Responsibilities:  Thoroughly monitor the interfaces and make sure data process through the system is fine  Proactive actions to be taken on noticing any issues either while monitoring or through error mails  Handling tickets of varying priority, working within the SLA to resolve the tickets to the satisfaction of the user  Interacting with business users through mail/communicator and phone to understand the issues and resolve them  Configuring new Trading Partner Agreements in Trading Networks, testing the setup and then migrating it to the Production environment to transmit Live data  Transitioning new interfaces within team amtes and creating Understanding document and SOP for the interfaces  Handling major unplanned outages as well as outages during the monthly maintenance window  Identifyng areas for automation and developing tools and services to automate handle tasks and errors which are repetitive in nature
- 3. Project #2: Project : EAI- Enhancement Release Client : Internal project to sapient Duration : Feb 2013 to Oct 2013 Role : WebMethods Developer & production support Team Size : 6 Environment : WebMethods Integration Server 7.1.2, Developer 7.1.2, Broker, Trading Network. Project Overview:  This is an internal project for sapient. Here we done some changes in EAI services which are related to Alert mechanism and feed related services. Mainly we introduced TMS (Transport Management System) into Integration layer. In TMS Person, project and client are the entities. Here we used pub-sub model for integration. Responsibilities:  Detail analysis of the Functional Design  Requirement Gathering for development  Preparation of technical design specifications for different messaging standards.  Development of the interfaces  Unit testing and code review  Technical unit testing  Technical Acceptance testing. Project#1: Project : Stellent Upgrade Client : Internal project to sapient Duration : Jan 2012 to Feb 2013 Role : WebMethods Developer & production support Team Size : 4 Environment : WebMethods Integration Server 7.1.2, Developer 7.1.2, Broker, Trading Network. Project Overview:  Stellent is a subscribing system in Integration layer. Before this Stellent subscribes only Client, Person, and Project. Present it was connected with MySQL 2005 now in this release it was moved to Oracle 11g. For this we created all the staging stables and Stored procedures in database side and in WebMethods, Adapters are refreshed for existing entities and Flow services are changed accordingly. In this release we introduced three new entities into this Stellent below are the new entities.  Allocation: For this we created all staging tables and stored procedures in Stellent. In WebMethods side created adapter connections, notification and subscribe service.
- 4. For this Allocation we used Batch insert adapter to put the data.  Vendor: This is a totally new one, for this created a canonical to publish. This is also a notification based one for this we created staging tables in Source and target. Stored procedures are also created in both sides. In WebMethods side we followed pub-sub model.  Course: OLMS (Oracle learning management System): This is the system which will maintain all the data of persons who are completed their courses. Main concern is we have to put the data in Stellent staging tables with the help of adapter connection. For this Oracle HRMS is the source system, in this system view is there which is related course. From this view we have to get the data and put the data in Stellent side. Database side: we created all the staging tables in target system and created stored procedures in source system and target system. WebMethods side: created a flow service to get the data in Source side. We will insert the data by calling a flow service which is in source side. As of now Data insertion was completed. OLMS ACK Processing: Stellent team will put the Data in ACK table after this we created a stored to procedure to get the record which is not processed. Flow service was created to give a mail with summary report. This summary report contains how many records are passed, failed and ignored. If in the case the Ack processing was not done then it will give an error mail with proper reason. Responsibilities:  Detail analysis of the Functional Design  Requirement Gathering for development  Preparation of technical design specifications for different messaging standards.  Development of the interfaces  Unit testing and code review  Technical unit testing  Technical Acceptance testing.